From owner-freebsd-git@freebsd.org Wed Nov 13 19:38:40 2019 Return-Path: Delivered-To: freebsd-git@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F0BEB1B9829 for ; Wed, 13 Nov 2019 19:38:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from springbank.echomania.com (springbank.echomania.com [IPv6:2a01:7c8:aab2:81::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "springbank.echomania.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Cw0039FLz4ck9 for ; Wed, 13 Nov 2019 19:38:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) X-Virus-Scanned: Debian amavisd-new at springbank.echomania.com Received: from [IPv6:2001:470:7a58:0:9cf:6f1f:fa:40dc] (unknown [IPv6:2001:470:7a58:0:9cf:6f1f:fa:40dc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by springbank.echomania.com (Postfix) with ESMTPSA id C4EE958019B; Wed, 13 Nov 2019 20:38:30 +0100 (CET) Subject: Re: FYI - LLVM migration to Git and GitHub has started To: Warner Losh , Ilya Bakulin Cc: freebsd-git@freebsd.org References: From: Dimitry Andric Message-ID: <35a9c9f9-ee24-6172-6109-0cd4df5a79e8@FreeBSD.org> Date: Wed, 13 Nov 2019 20:38:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47Cw0039FLz4ck9 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.918,0]; ASN(0.00)[asn:20857, ipnet:2a01:7c8::/32, country:NL]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2019 19:38:41 -0000 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. -Dimitry 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 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 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. >>> http://lists.llvm.org/pipermail/llvm-dev/2019-October/136106.html >>> >>> 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. >>> http://lists.llvm.org/pipermail/llvm-dev/2019-October/135912.html >>> >>> 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@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-git >>> To unsubscribe, send any mail to "freebsd-git-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-git@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-git >> To unsubscribe, send any mail to "freebsd-git-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-git@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-git > To unsubscribe, send any mail to "freebsd-git-unsubscribe@freebsd.org" >