GNOME's Development Infrastructure Requirements

General

• Not too much work to deploy and maintain
• Freely licensed
• Good user experience for new contributors: needs to look good, have clear workflows, UI for most of the tasks.
• Integration with GNOME user accounts through Kerberos/OpenID
• Nice to have:
  • CLI tool similar to git-bz
  • CI integration
  • Anti-spam integrated

Code hosting

• Browse GNOME modules
• UI for common operations; should support standard GNOME workflows (rebase on master, branch for releases)
• Search by commit/commit message
• Nice to have:
  • Code search
  • Per module commit access
  • Image and PDF previews

Issue tracking

• Milestones (e.g. releases)
• Keywords
• Subscribe to issues or projects
• Code Review
• Move issues between projects
• Search for issues in all GNOME modules
• Statistics and reports
• Nice to have:
  • Inline images

Conclusion

GNOME's issue tracking requirements are relatively simple, in that the project doesn't do a lot of people or team management through its issue tracker, and issues aren't grouped in complex ways. A good code review solution is important though.

Much of the new functionality that the project seeks concerns code hosting, including UI for common operations, search, and a better browsing experience.

Integration between code hosting and issue tracking is another high priority. This includes features like management of issues from commits and cross-referencing between commits and issues.