FYI - LLVM migration to Git and GitHub has started

Dimitry Andric dim at
Wed Nov 13 19:38:41 UTC 2019

The main reason the LLVM project/foundation moved to GitHub is that they 
rather sucked at hosting their own infrastructure, and that was mainly 
caused by it not being one of their goals.  Now they are also moving in 
the direction of moving the whole lot to GitHub, including issue 
tracking and reviewing.

Bugzilla has many more features than GitHub's rather anemic issue 
tracker, but it is extremely dated software, and is considered 
user-hostile (or should I say millenial-hostile? :) these days.  So most 
people on the LLVM lists appear to be in favor of moving to the GitHub 
issue tracker.

For reviews they use Phabricator like we do, but in that area is less 
consensus, as many people feel GitHub's pull request model is inferior 
to Phabricator's review workflow.  I guess it mostly depends on your 
preferences, and the complexity of your reviews.

Having said all that, my personal opinion is that it is not wise to 
outsource all your crown jewels to some commercial closed source party. 
GitHub may look pretty, and be very fashionable with the Cool Kids, but 
there have been some instances of censorship, bad decisions, etc.  And 
they could close down your project at any time, for any reason, if they 
feel like it.


P.S.: Yes, I'm also on GitHub, and I signed away my soul to Microsoft. 
Multiple times, even!

On 2019-11-13 19:29, Warner Losh wrote:
> Vendor branches break. Our work flow breaks. Some committers have "terms of
> service" wrt de-platforming. The release engineer won't be able to build
> releases due to SVN integration. Just moving to github is non-starter at
> the moment. It won't happen without careful planning. Planning that's on
> going at the moment.
> LLVM didn't "just move to github" either. They had a significant transition
> period. We are studying their move to speed our transition to git.
> Warner
> On Wed, Nov 13, 2019 at 9:29 AM Ilya Bakulin <ilya at> wrote:
>> So with that new Github feature in mind, if we all move FreeBSD main repo
>> to Github tomorrow, what will break for us?
>> What does Github not give us that we absolutely need?
>> On Tue, Oct 22, 2019 at 6:45 PM Ed Maste <emaste at> wrote:
>>>  From the llvm development mailing list:
>>>> We're getting ready to start migrating to GitHub.  SVN will be
>>>> moved to read-only now and we'll
>>>> begin the process of turning on GitHub commit access.
>>> A few additional points I found in another thread that are probably of
>>> interest to the FreeBSD/git community:
>>>> Just in the last week, the GitHub team completed the "Require Linear
>>>> History" branch protection, which means we can now enforce linear
>>>> history server side and do not need the git-llvm script to do this.
>>> and later:
>>>> GitHub only supports pre-receive hooks in their Enterprise Server
>>> edition,
>>>> which isn't a good option for us, because we would need to self-host
>> it.
>>> _______________________________________________
>>> freebsd-git at mailing list
>>> To unsubscribe, send any mail to "freebsd-git-unsubscribe at"
>> _______________________________________________
>> freebsd-git at mailing list
>> To unsubscribe, send any mail to "freebsd-git-unsubscribe at"
> _______________________________________________
> freebsd-git at mailing list
> To unsubscribe, send any mail to "freebsd-git-unsubscribe at"

More information about the freebsd-git mailing list