llvm dev - Feb 2017 - Using Phabricator for all LLVM development

Has anyone considered moving all LLVM development over to Phabricator?

Phabricator includes

- Code review (Differential)
- A bug tracker (Maniphest)
- Project management software
- A wiki (Phriction)
- Many more applications

LLVM already has a Phabricator instance.

I guess it doesn't make sense to move fully to phabricator, if we are
considering moving to github soon.

Piotr



2017-02-09 15:49 GMT+01:00 Demi Obenour via llvm-dev <
llvm-dev at lists.llvm.org>:
> Has anyone considered moving all LLVM development over to Phabricator?
>
> Phabricator includes
>
> - Code review (Differential)
> - A bug tracker (Maniphest)
> - Project management software
> - A wiki (Phriction)
> - Many more applications
>
> LLVM already has a Phabricator instance.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170209/059a13f2/attachment.html>

On Thu, Feb 09, 2017 at 04:02:31PM +0100, Piotr Padlewski via llvm-dev
wrote:
> I guess it doesn't make sense to move fully to phabricator, if we are
> considering moving to github soon.
I don't believe github offers any advantage over phabricator and
bugzilla. Frankly, it is much worse than the alternatives for anything
but hosting a git repository. By the same reasoning, I prefer bugzilla
over phabricator for the purpose of managing bugs.

Joerg