Thanks for setting this up, it is a huge improvement to the project. I would recommend using GitHub issues at https://github.com/gem5/gem5 instead (currently disabled) because many more people will be familiar with it, more people already have an account there, the Google Pagerank will likely be higher, it would keep "(a mirror of) the code closer to the issues", does not require "explicitly applying to Atlassian for having a free instance", and because the simplicity of the system tends to make it better suited for open source projects.
I would also recommend, if possible, that such project choices be discussed publicly on the dev mailing list before a decision is made. While the management committee has the final word, and was presumably involved, it might be good to get a feel for how the community in general feels about the possibilities. In any case, any bug tracking system is better than none, and already a huge improvement, thanks a lot. ________________________________ From: gem5-dev <gem5-dev-boun...@gem5.org> on behalf of Bobby Bruce <bbr...@ucdavis.edu> Sent: Wednesday, November 13, 2019 6:40 PM To: gem5-dev@gem5.org <gem5-dev@gem5.org> Subject: [gem5-dev] Introducing the gem5 Jira Issue Tracking System Dear all, I’m happy to announce the new gem5 Jira issue tracking system: https://gem5.atlassian.net .In the spirit of gem5's open, collaborative philosophy, this is publicly facing instance; allowing anyone to view and creates issues. At UC Davis, we've been using Jira for about two weeks now and are happy with what the current setup offers. I'm aware some on this mailing are more familiar with Jira than us, so I'd be happy to hear feedback on how to better setup and configure it. Please feel free to "play around" with Jira for a while to see what it's capable of and what may be improved. From now on, https://gem5.atlassian.net should be the first-stop for those reporting bugs in gem5. Though discussions on the gem5-dev mailing list are fine, we would appreciate it if bugs, big or small, could be logged in Jira so they may be triaged and scheduled for fixing in the current or later releases of gem5. Likewise, we are more than happy for suggested improvements and new features to be added as tasks. Even those that may seem small and trivial are worthwhile adding. At UC Davis we are beginning to redirect students, keen to contribute to gem5, to Jira and have them allocate themselves tasks. Therefore, easy, introductory tasks are beneficial. It would be appreciated if those who frequently contribute to gem5 could browse the Jira instance regularly, use it to notify others of what they are working on (by assigning themselves tasks), and share knowledge through the system (we find that commenting on tasks is a good way to share knowledge). As a final note, I wish to take this opportunity to thank Atlassian for their generous support of gem5, and the open source community in general. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
