2016-02-11 20:05 GMT+01:00 Christoffer Holmstedt <christoffer.holmstedt@...400...>:

2016-02-11 8:07 GMT+01:00 Krzysztof Kosiński <tweenk.pl@...400...>:
2016-02-10 22:45 GMT-08:00 Bryce Harrington <bryce@...961...>:
> On Tue, Feb 09, 2016 at 11:55:28AM +0100, joakim@...1974... wrote:
>> Bryce Harrington <bryce@...961...> writes:
>> > On Fri, Feb 05, 2016 at 09:16:36AM -0800, mathog wrote:
>> >> On 05-Feb-2016 05:40, Eduard Braun wrote:
>> >> > In general I would avoid splitting the code repository from the bug
>> >> > tracker as those two are closely related and often intertwined. It
>> >> > hinders efficiency a lot when tracking bugs elsewhere.
>> >>
>> >> I agree with that - everything in one place.  Moving to git is fine so
>> >> long as the entire history of the project makes the transition, all the
>> >> bugs, all the revisions, and so forth.  There shouldn't be anything
>> >> "left behind" on launchpad.  Not that I have any idea how one would go
>> >> about doing this sort of migration, never having used git except to
>> >> download entire projects for a local build.
>
> I'll throw out another thing maybe worth considering is Phabricator
>
>     http://phabricator.org/
>
> This is a very powerful platform, and highly customizable, providing an
> integrated solution for bugs, patchreview, and a heap of other stuff as
> well as git hosting.  I've had some limited experience using it on
> Enlightenment and Wayland, and it gets very high marks from people who
> use it.

Thanks for the link Bryce, I was looking around for JIRA alternatives for non-Inkscape stuff and phabricator seems like a good candidate.
 

I've been able to look into Phabricator and run a local test environment for some time now and for sure Phabricator is really powerful. The downside is as you say Bryce it would take a lot of configuration and administration to set up properly for our needs, especially when it comes to bug tracking. It might be worth it but I don't think so. Phabricator is more for bigger organizations which requires alot of flexibility between different projects, teams and workflows.

The biggest drawback as I see it is the requirement to use "arc" command line tool when you want to use the code review features of the platform. I really see it as an annoying extra step when I just want to push a git branch to remote repository for review, even sending email with linux kernel patches is easier, straight from git cli.

At the moment Gitlab + Jenkins seems to be the best option if we want to host our code and CI ourselves.

Regards
--
Christoffer Holmstedt