From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2 Subject: Re: Some suggestion about "Contributing" documents. Date: Tue, 11 Apr 2017 08:19:24 -0400 Message-ID: <864lxv2l2r.fsf@gmail.com> References: <871sszzf6h.fsf@163.com> <58EC9F5A.1090004@crazy-compilers.com> <20170411094007.5nj74ulmaqu7sj3z@abyayala> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cxulf-0001iQ-9b for guix-devel@gnu.org; Tue, 11 Apr 2017 08:19:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cxulc-0000MU-1i for guix-devel@gnu.org; Tue, 11 Apr 2017 08:19:31 -0400 Received: from mail-qt0-x234.google.com ([2607:f8b0:400d:c0d::234]:33750) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cxulb-0000Ly-Ti for guix-devel@gnu.org; Tue, 11 Apr 2017 08:19:27 -0400 Received: by mail-qt0-x234.google.com with SMTP id m36so26376377qtb.0 for ; Tue, 11 Apr 2017 05:19:26 -0700 (PDT) In-Reply-To: <20170411094007.5nj74ulmaqu7sj3z@abyayala> (ng0's message of "Tue, 11 Apr 2017 09:40:07 +0000") 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: Hartmut Goebel Cc: guix-devel@gnu.org On 04/11/2017 at 09:40 ng0 writes: > Can you come up with an chapters, subchapters, + briefly described / > expected content map? This might help to work on it. > > Hartmut Goebel transcribed 0.5K bytes: >> Am 11.04.2017 um 07:28 schrieb Feng Shu: >> > "Contributing" document is hard to be understood i think. >> > In my opinion, "Contributing" part of document should split >> > two sub parts: >> > >> > 1. I am a guix core developer >> > >> > 2. I Just want to add a new apps's "define-public" >> >> Good idea. I'd even put the "add a new apps" part first since this is >> what more people will do more often. >> >> -- >> Regards >> Hartmut Goebel >> >> | Hartmut Goebel | h.goebel@crazy-compilers.com | >> | www.crazy-compilers.com | compilers which you thought are impossible | >> >> ISTM this should organized around an assumed "normal" pattern-of-use. e.g., starting from assumption that Guix or GuixSD is already installed and we use Guix to simplify the steps. Callouts should be provided if any steps differ between for Guix or GuixSD users. In this case a outline might look like ... 7 Contributing - Setting up a Guix build from Git - git checkout - tool chain setup - sample: system.scm - sample: user.scm - first guix build - hacking steps - modify an existing package - hacking steps - add new package - hacking steps - Submitting Patches:: Share your work. - For guix core developers - Install Guix from source - Run Guix Before It Is Installed:: Hacker tricks.