> I wish GitHub had a proper UI for deprecating/abandoning projects
Would this be equivalent to implementing the dislike button for Facebook, which we know will be never implement?
I'm currently indexing most of the popular repositories on GitHub (500+ stars) so they can be searched by commits, diffs, etc. and what I've noticed is:
- GitHub hosts a lot and I mean lots of repositories.
- People fork popular repositories like crazy but the vast majority do nothing with their forks.
Would making it easier to deprecate or make it more noticeable that a repo has been abandoned be good for GitHub? Don't get me wrong, GitHub is the current leader for hosting Git repositories and the number of active repositories is still quite significant, but if you dig deeper, you'll find a considerable amount of unused/never touched repos.
From GitHub's point of view, I really don't see any benefits for implementing such a UI, much like it makes no sense for Facebook to implement a dislike button.
Would this be equivalent to implementing the dislike button for Facebook, which we know will be never implement?
I'm currently indexing most of the popular repositories on GitHub (500+ stars) so they can be searched by commits, diffs, etc. and what I've noticed is:
- GitHub hosts a lot and I mean lots of repositories.
- People fork popular repositories like crazy but the vast majority do nothing with their forks.
Would making it easier to deprecate or make it more noticeable that a repo has been abandoned be good for GitHub? Don't get me wrong, GitHub is the current leader for hosting Git repositories and the number of active repositories is still quite significant, but if you dig deeper, you'll find a considerable amount of unused/never touched repos.
From GitHub's point of view, I really don't see any benefits for implementing such a UI, much like it makes no sense for Facebook to implement a dislike button.