From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79848 invoked by alias); 13 Nov 2016 00:59:05 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 79835 invoked by uid 89); 13 Nov 2016 00:59:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*Ad:U*kawa, 2.3, gitlab, gitlabcom X-HELO: aibo.runbox.com Received: from aibo.runbox.com (HELO aibo.runbox.com) (91.220.196.211) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 13 Nov 2016 00:58:53 +0000 Received: from [10.9.9.211] (helo=mailfront11.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1c5j8F-0003gS-C0 for kawa@sourceware.org; Sun, 13 Nov 2016 01:58:51 +0100 Received: from 70-36-239-8.dsl.dynamic.fusionbroadband.com ([70.36.239.8] helo=toshie.bothner.com) by mailfront11.runbox.com with esmtpsa (uid:757155 ) (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) id 1c5j86-0000O1-He for kawa@sourceware.org; Sun, 13 Nov 2016 01:58:42 +0100 From: Per Bothner Subject: proposal: move Kawa from Subversion to git on gitlab.com To: Kawa mailing list Message-ID: <87fe287f-2aa8-3462-ceeb-66e3982ddaeb@bothner.com> Date: Sun, 13 Nov 2016 00:59:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-q4/txt/msg00052.txt.bz2 Now that Kawa 2.2 has been released, the focus of development will be in the "invoke" branch. That can't be merged into the trunk yet because it requires MethodHandles, so it does not work on Java 5, Java 6, or (more importantly) Android. (I'm considering how best to handle platforms without MethodHandles, but nothing has been decided or coded yet.) So it will be easier if we're using something that handles branches better than Subversion. We talked about moving to Git, and I think that makes sense. The idea would be to switch to Git, and then immediately make a quick Kawa 2.3 release. There are multiple host options, though: * GitHub - not as Free Software-friendly; FSF disapproved. * Savannah - not a lot of functionality; run by (too few) volunteers. * Pagure (from RedHat) - too new, too small. * Self-host (either GitLab CE or Gogs) - better branding using own domain name (maybe git.kawa-lang.org), but not worth the extra work. That leaves GitLab as the most plausible candidate. What do people think about that? This would only affect version control and (presumably the issue tracker. The website, the ftp site, and the mailing list are separate issues. -- --Per Bothner per@bothner.com http://per.bothner.com/