|
To clarify the last line of the original post, replies should be on
the mailing list - not on the Gist. In the two proposed workflows, the primary difference is with the two issue trackers. Anything extra in the workflows could be used with both issue trackers without many problems, though some of the extras are better suited for one tracker over the other. Right now we are set up in Bugzilla, though we have been using GitHub as well over the summer (when the development code base was on GitHub). Bugzilla is the primary bug tracker for GNOME projects, which is why we were previously using it for managing the tickets. It currently has quite a few tickets which are referencing the old version of MouseTrap which need to be closed off. It is not tied to a specific repository and is designed to be a mostly-standalone bug tracker, though it does have a patch review system built in that has been used in the past. In order to go back to using Bugzilla as the bug tracker, we wouldn't have to do change a lot from our previous workflow. Patches would still be expected to contain a single commit, following the GNOME standards, and the code could optionally be mirrored on GitHub for code review to be moved there if we wanted. GitHub is what we have been using as a bug tracker over the summer. As the development code base was sitting on GitHub, it made sense to move everything to there, including ticket management and code review, as it allowed everything to be centrally located. Because GitHub forced everything to be centrally located, we didn't have to worry as much about where things should be, and we knew exactly where to go to get the latest code, list of tickets to work on, or code that was waiting to be reviewed. Without everything being centrally located, as it currently is with tickets in Bugzilla, the code base with GNOME, and the wiki also with GNOME, the usefulness of GitHub's ticket tracker and pull requests comes into question. GitHub really excels in a "Fork-Commit-Pull Request" workflow, which allows GitHub to handle merging code contributed by others as well as automatically closing off tickets automatically once it is merged into the main branch. This would require moving the code base to GitHub from GNOME, which would cut GNOME out of the equation almost entirely, leaving only the Wiki (which could be moved) and the mailing list under the GNOME systems. So, as far as I can see, the question comes down to cutting out GNOME and using GitHub, or keeping GNOME in the picture and using Bugzilla for tickets. -- Kevin Brown |