Re: [gentoo-dev] Migrate to Phabricator

[Michał Górny]

On Mon, 18 Apr 2016 13:44:00 +0200
Jonas Jelten <jj@××××××.net> wrote:

> Phabricator is a fun adventure game: http://phabricator.org/
>
> It provides a tightly coupled set of project management tools.
> https://phacility.com/phabricator/
>
> Many bigger projects (e.g. blender, mediawiki, ...) started using
> phabricator, it could also be very beneficial for gentoo.
>
> https://secure.phabricator.com/w/usage/companies/
> https://secure.phabricator.com/w/usage/not/
>
> Wikimedia elaborates about the migration:
>
> https://blogs.gnome.org/aklapper/2014/12/17/welcome-phabricator/
> https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla
>
> https://wiki.blender.org/index.php/Dev:Doc/Tools/Phabricator/Migration
>
> Migrating would contradict the apparent goal of integrating github more
> tightly, but still we could consider to use Phabricator instead,
> especially to dump bugzilla.
>
> If we come to the conclusion we are a really serious business, we must
> set up the "Serious Business Edition", for the most serious businesses.
>
> Still, I hope we can go with the Awesome Edition :P

This has been suggested already, and if I recall correctly, someone
even set up an instance for testing. Others have already explained to
you most of the 'big' problems with phabricator which make it pretty
much a useless pseudo-enterprise toy.

And before this diverts into discussion about another toy: I'd like
appreciate if we really considered tools that can be better, not worse.
I can agree that our Bugzilla is quite slow for some reason. Still, it
is reasonably fast.

Most of the tools suggested so far are either terribly slow by
themselves (poor design), terribly buggy (error conditions don't happen
after all, do they?), can't handle big git repositories such as our
(become terribly slow) and/or are completely unmaintainable.

Now, if you can find a good tool that is feature-par with Bugzilla, is
fast even under load (no, PHP is not), can handle errors gracefully, is
accessible (like, works without JavaScript enabled), is maintainable
and -- after all -- has some real advantage over what we have now,
please speak of it.

As a side note, few things that are not advantages:

* performing magic operations based on commit messages (which make
  commit messages reliant on software used, and likely breaking any
  other software used in the future),

* software committing to the repository for us (security reasons,
  commit signing etc.).

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>