Here's my view of it # GitHub:
## Advantages - Really nice interface. Friendly to people reporting issues. - Integrates nicely with pull requests. You can automatically close issues when a pull request is merged just by putting "closes #nnnn" in the commit message. You can use the hub tool to convert issues into pull requests. - GitHub is where we have everything else, so it would make things easier to find. - Formatting in Markdown. - You can edit your comments. - There is better momentum in GitHub than Google Code. The latter feels like a dying product these days. - They have a good API. - We could move issues for subprojects closer to the code (like SymPy Live and SymPy Gamma). ## Disadvantages - GitHub's search really sucks. This is in two ways. First, the search itself doesn't seem to be very accurate. I think this is improving, but for instance, previously, when I searched for "jordan" I got zero search results, instead of https://github.com/sympy/sympy/pull/677, which was what I was looking for. Secondly, it is very hard to use labels effectively, because you can only do a positive search with them. I think you should be able to do something like "label:GCI" to find all issues with the GCI label, but I tried this and it didn't work. If it could be demonstrated how to do advanced searches using labels, I would be much more sold on it, because we have over 1100 open issues in Google Code and using labels is the only effective way to find the one I am looking for. - There are no attachments, other than images. This isn't really an issue for us, but it's worth noting. - Some advanced features, like the ability to automatically assign labels when other labels are used, require that exactly one of some set of labels is attached to an issue (like a priority), or automatically CC people on given labels, do not exist (but do exist in Google Code). Another nice one that we use quite a bit is the ability to "block" an issue on other issues. # Google Code ## Advantages - We are already there. Staying there requires no work. - They have very nice advanced features, some of which I mentioned above. - They have very good search. - All our places in the code and commit history that reference issue numbers point to Google Code issues. The numbers would change if we migrated. ## Disadvantages - The UI is not the friendliest, especially to new reporters. - It can be confusing that the issues are on Google Code but everything else is on GitHub. - People might not find the Google Code issue tracker. - People still occasionally attach patches to Google Code issues, but I think if they used the GitHub issue tracker, then they would see better to contribute using pull requests. - The Google Code API and Google tools really suck. So basically, my biggest gripes are: - Lack of advanced features in GitHub. I'm probably the only person who uses these things, but it is nice that I am able to use them to effectively search through our issue list for an issue I remembered. - Migrating is difficult, and I haven't had the time to look into it. To be honest, I think I can learn to live with the GitHub search. In the worst case, I'll have to write some tool using their API to do the searches for me. The biggest hurdle is the actual migration. I'd like to maintain as much metadata as possible, including who made comments, inter-issue links, and labels. Aaron Meurer On Tue, Sep 17, 2013 at 10:27 PM, Matthew Rocklin <[email protected]> wrote: > I'd like an enumeration of advantages of each. > > My gut preference is to integrate everything under github. But this is > based on a desire for fewer websites to visit rather than a deep > understanding of the relative merits. > > > On Tue, Sep 17, 2013 at 7:29 PM, Aaron Meurer <[email protected]> wrote: >> >> The Google Code tracker should be preferred, for now. >> >> I had opened the GitHub issue tracker as an experiment, to see if it >> attracted more issue reports. I had been debating whether to move our >> issues to the GitHub tracker. Unfortunately, I haven't had the time to >> play around with the migration tools I found, so it stalled. >> >> There are advantages to each tracker. I suppose since the cat is out >> of the bag so to speak, it would be nice to get some community input >> on this. I can enumerate what I think are the advantages/disadvantages >> of each if you would like. >> >> Also, if anyone wants to play with a migration script, just create an >> empty repo on GitHub and try migrating the issues to there. I can >> point out the scripts that I found so far if anyone wants to give it a >> go. It's honestly not much more than you would find from the first few >> pages of a Google search, though. >> >> Aaron Meurer >> >> On Tue, Sep 17, 2013 at 6:28 PM, G B <[email protected]> wrote: >> > Are the issue trackers from Github and code.google coordinated? Which >> > is the preferred one to use? >> > >> > Thanks! >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "sympy" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an email to [email protected]. >> > To post to this group, send email to [email protected]. >> > Visit this group at http://groups.google.com/group/sympy. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sympy. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
