It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.
back
2 comments
You could also say that everyone moving to GitHub is leading to a dangerous centralized monoculture that evaluates software quality based on how well it fits GitHub's conventions.
git is still git - people don't even need a github account to have full functionality.
How many Github projects accept git format-patch submissions? There's functionality beyond the basic DVCS commands.
In Go's case, we will be using Gerrit (elsewhere) for accepting submissions. GitHub will only be used as a source code mirror, wiki and issue tracker.
Wait wait wait... no pull requests? There's no way you could just hook up PR's to gerrit? Using github just as a mirror seems to defeat the entire purpose of github, which is to encourage more community members to contribute.
Having migrated projects from GitHub to/from Bitbucket and internal git servers - which is a 10 minute job at most - I'm not terribly worried about this.
Moving to git is great, moving to github can be terrible for some projects that are more collaborative, as if you want to change someones PR you cannot..
You can makes changes to a PR that you didn't open.
If you want to change the title, edit/delete comments, close the PR, assign a person or labels then you'll need the proper permissions.
If you want to make changes to the code you'll need to have push access to the same repo (which is usually the case if you're on the same team because then you don't need to use forks). Otherwise you can always amend the commit(s) before merging them into master.
Better still you can fork the PR and open a PR to the PR :)
What if the repo is /me/myproject and you are trying to fork /contributor/myproject? What will your fork be named?
They're using Gerrit for code review, where you can modify patches submitted by other people.