3 ms·

What's your solution?

• awalton 9y ago
  I don't really have many issues with bug management on GNOME (that pain really goes to the bigger multi-module maintainers and the reassigning of bugs to the right places in the stacks), but for code review I'd probably just replace Splinter with a standalone instance of Review Board and call it good enough for the time being - basically waiting for someone to come up with an integrated code review/issue tracker that isn't tied to their company's infrastructure (Hello Google), is standalone installable and manageable (sorry GitHub) and doesn't impose a pull model on patch pushers (goodbye GitLab).
  • newsat13 9y ago
    GitHub EE is standalone installable.
    • awalton 9y ago
      GitHub EE is not in consideration.
      • mintplant 9y ago
        ...because it is, of course, proprietary software, and this is the GNOME project we're talking about.
• zem 9y ago
  if i had to pick something, i would at the least give phabricator a serious look to see how it stacked up against gitlab [https://www.phacility.com/phabricator/ https://www.phacility.com/phabricator/]
  • pedroms 9y ago
    Before coming up with this proposal, they evaluated GitLab and Phabricator: https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure/ https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure...
    • zem 9y ago
      thanks, that was a more interesting read than the posted article