From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: Guix package incubator (later a channel) Date: Mon, 6 Feb 2017 19:09:23 +0000 Message-ID: <20170206190923.GA3592@mail.thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42805) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1caoiO-0007RX-Ae for guix-devel@gnu.org; Mon, 06 Feb 2017 14:12:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1caoiL-0003sV-5D for guix-devel@gnu.org; Mon, 06 Feb 2017 14:12:40 -0500 Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: rekado@elephly.net Cc: guix-devel@gnu.org Hi all, After yesterday's FOSDEM discussion I propose to set up a 'Guix incubator' git tree using Gitlab. The master branch will track the main Guix master but project can run on forked trees and branches. The idea is to have patches prepared by new committers or by people who simply prefer to use a web-based git environment. Each of these trees can become a guix channel - once we have channels to support that. It won't hamper the normal process since ready patches still get compiled and submitted through the mailing list (ML). In fact it may help scale the review process by getting peer reviewers involved. The idea is that we have an incubator environment before the ML which allows for playful learning and tracking of patches that may (or may not) make it into main line. I think it is very important to have a low barrier to entry when it comes to submitting package recipes. Gitlab may help. I'll take the lead and maybe I'll start submitting my own patches again ;) How about using http://notabug.org/? Will they be happy to host us and is that the best place for gitlab? Pj.