Hacker News Reader

Comment by awalton | Hacker News Reader

Not convinced GitLab is the solution, but I'm definitely convinced GitHub isn't.

Not as active in GNOME these days, so my vote is not really a vote... but I do have my own reservations about both "Git-Wrapped" solutions, especially if they start requiring pull requests.

Splinter/Bugzilla is definitely not a long-term code review solution though, so something really has to give there.

View on HN

What's your solution?

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).

GitHub EE is standalone installable.

GitHub EE is not in consideration.

...because it is, of course, proprietary software, and this is the GNOME project we're talking about.

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/]

Before coming up with this proposal, they evaluated GitLab and Phabricator: https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure...

thanks, that was a more interesting read than the posted article

What's the problem with a pull request?

Probably that PRs aren't quite part of git, so every service has their own implementation.

Reply on news.ycombinator.com