4 ms·
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
by awalton 9y ago
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.
- xkarga00 9y agoWhat's your solution?
- awalton 9y agoI 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).
- zem 9y agoif 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/]
- pas 9y agoWhat's the problem with a pull request?
- yjftsjthsd-h 9y agoProbably that PRs aren't quite part of git, so every service has their own implementation.