I strongly agree with Derick on this matter. Le lundi 15 novembre 2021, 12:06:54 CET Nikita Popov a écrit : > For better or worse, GitHub is where nearly all open-source projects are > hosted, which means that pretty much anyone involved in open-source has an > account there and is familiar with the workflows.
I do think that this is for worse, and that this situation exists because of decision like the one PHP is about to make. Saying we should use github because other projects use it is part of the problem. If PHP makes the switch we are encouraging other projects to do the same as well. We would be actively participating in this centralisation. > It is also where PHP > hosts it's repos and where we accept pull requests. Which I also think is a problem. A smaller one because of how git is distributed, but still annoying. The decision to move to github for the repositories was done in a hurry because of a security issue. It was the right decision to answer to the urgency of the situation back then I think, but it should not be used as a reason to go deeper down the rabbit hole. > An alternative issue > tracker has to compete not just on technical grounds, but also on > integration, familiarity and network-effect. For an open-source project, > these aspects are quite important when it comes to interaction with casual > contributors. > > Working at JetBrains, proposing YouTrack instead of GH issues has certainly > crossed my mind -- there is no doubt that at a technical level, it's a much > better bug tracker than GH issues. But that's simply not the right question > to ask. The right question is whether, given our rather simple > requirements, is it sufficiently better to overshadow the other benefits of > GitHub issues for an open-source project? I don't think so. We just need GH > issues to be "good enough" for our purposes, and I think that at this point > it is. > > I'll also mention that the discussion about this migration has been going > on for six months, and in that time all I've ever seen are vague mentions > of alternatives, but nobody has provided any in-depth analysis that goes > beyond a simple name drop. I went through the trouble of providing a > detailed evaluation of how the GitHub issues migration will look like, > while the alternatives are still at the state of "Phabricator is a thing" > (ooops, it actually isn't -- it managed to be discontinued while the > discussion was going on!) I would like to suggest gitlab.com, which does provide hosting for free for opensource projects: https://about.gitlab.com/solutions/open-source/ Anyone with a github account can use it to log in. It should be easy to migrate to any other gitlab instance if needed. There are even plans to one day have federation over gitlab instances. Not anytime soon, but likely sooner than github which is only hosted by Microsoft. Côme -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
