[Numpy-discussion] Migrating issues to GitHub
Sat Feb 11 14:44:20 CST 2012
This is good feedback.
It looks like there are 2 concerns:
1) no way to add attachments --- it would seem that gists and indeed other github repos solves that problem.
2) You must be an admin to label an issue (i.e. set it as a bug, enhancement, or so forth).
This second concern seems more of a problem. Perhaps this is something that can be brought up with the github developers directly. Not separating issue permissions from code permissions seems rather unfortunate, and creates work for all admins.
On the other hand, it might force having an admin who is paying regular attention to the issues which is not necessarily a bad thing.
So, despite the drawback, it seems that having issues on Trac and having code-conversations on those issues happening separately from the pull-request conversations is even less optimal.
On Feb 11, 2012, at 2:06 PM, Benjamin Root wrote:
> On Saturday, February 11, 2012, Travis Oliphant <email@example.com> wrote:
> > How to people feel about moving the issue tracking for NumPy to Github? It looks like they have improved their issue tracking quite a bit and the workflow and integration with commits looks quite good from what I can see.
> > Here is one tool I saw that might help in the migration: https://github.com/trustmaster/trac2github
> > Are there others?
> > -Travis
> This is probably less of an issue for numpy, but our biggest complaint about the github tracker for matplotlib is the inability for users to add attachments.
> The second complaint is that it is awkward to assign priorities (has to be done via labels). Particularly, users can not apply labels themselves.
> Mind you, neither of these complaints were enough to completely preclude mpl from migrating, but it should be taken into consideration.
> Ben Root _______________________________________________
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion