On Sun, Feb 27, 2011 at 8:32 AM, Darren Dale <dsdal...@gmail.com> wrote: > If we are not convinced that github issues provides > everything we need, I think we should provide feedback to the github > devs and stick with sourceforge for the time being.
Here is a copy of a message I just sent to supp...@github.com. If you have other specific concerns, please let me know, and I will pass them along if I hear back from someone at github.: Hello, Thank you for all your great work on github. I am one of the developers of the matplotlib project (matplotlib.github.com). We recently converted our svn repositories to git, and started hosting them at github. This weekend I worked on testing migrating the issues from the sourceforge tracker (see https://github.com/darrendale/mpl-issues), but we have some concerns about the usability of the github issue tracker: * Our project produces graphical output, so the ability to attach files (like images and test scripts) to an issue is of critical importance to our project. * We would miss the ability to file tickets through the browser without signing in to github. * Having to repeatedly request "more" to see all the tickets is rather painful * We would miss the ability to assign a ticket to a developer. Creating a label for a developer is not seen to be enough. It would be nice if we could actually assign a developer to an issue, and from then on only the developer would receive emails concerning activity on the issue, unless others requested notifications. * It would be nice if people could register/unregister to receive notifications when there is activity on a specific issue that affects them. * It would be nice to be able to mark issues as pending after they are committed, and mark them as closed when publicly released, along with the release version(s) which addressed the problem (this latter feature would be brilliant if github had project management features) * It would be nice to mark an issue as a duplicate, automatically linking to the appropriate issue and registering the reporter for updates on the open issue I have made the case to the other devs that the benefits of github issues integration with the rest of the site is compelling, but at the end of the day, some of these features are too important to us to migrate to github issues at this time. Concerning the websites, in general I like the gh-pages and myproject.github.com solutions. However, the matplotlib documentation is generated from RestructuredText using Sphinx. The resulting html is about 80 MB, and has a lot of graphics and examples. We would rather not track changes to this generated content, since we already track changes to the (much smaller) source: it takes up additional space and takes a long time to upload to the server. Finally, I was hoping that you might consider adding some project management features to github. About a year ago, I migrated a project (github.com/python-quantities) from Launchpad. I like github much better, but miss some of Launchpad's project management features. For instance, it would be nice if we could specify and schedule an upcoming release at github (which could be used to integrate with pending issue closures), and then once we create the corresponding tag in git, github creates a new directory in an official releases downloads area (perhaps along with .zip and .tgz files). Also, the release graph at a projects main page at Launchpad was nice. I hope this doesn't seem too critical, I just wanted to give some constructive feedback. Thank you again for all you've done! Best regards, Darren Dale ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
