Our product development team is working through some discovery right now. A question that came up was, “what’s the lifecycle of a package from a package’s perspective? It gets created, it gets maintained, it gets forked, it gets renamed, it gets put down...what do all those transitions look like? Who’s involved?”
We’re wondering about that especially someone who has, at the very least, had one project be relatively successful, and another one that they either transferred ownership of or abandoned, especially if they abandoned it due to not caring about it anymore.
Is there someone in here who’s had or seen that experience up close? Or any writing you all have seen that really makes the process + pain clear? We’d love to learn more.
Top comments (2)
I could say a lot about this but wanted to get a few thoughts published before I forget to comment!
Lastly, I think lifecycle is an interesting topic and I've given examples of how both PyPI and GitHub address at least part of how developers can sunset projects without just erasing their existence.
Related topics of interest:
That Django package comparison chart is neat! I hadn't seen that before. I think the closest thing I've seen to that is the Ruby Toolbox.