From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: We need an RFC procedure [Re: Services can now have a default value] Date: Sun, 23 Apr 2017 11:52:50 +0000 Message-ID: <20170423115250.b3irapvp57ar6w3i@abyayala> References: <877f2gksbs.fsf@gnu.org> <8737d32abz.fsf@zancanaro.id.au> <87bmrr4ghh.fsf@gnu.org> <874lxjnzyx.fsf@zancanaro.id.au> <87bmrp8lk6.fsf@gnu.org> <8737d1nxbd.fsf@zancanaro.id.au> <20170422004634.4oedqmsebpctjqk4@abyayala> <878tmsud8m.fsf@elephly.net> <20170422100811.mr3t5rgh6n44xvdk@abyayala> <87pog4gihe.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40086) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2G4b-000304-Nm for guix-devel@gnu.org; Sun, 23 Apr 2017 07:53:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d2G4Y-0007xr-M9 for guix-devel@gnu.org; Sun, 23 Apr 2017 07:53:01 -0400 Content-Disposition: inline In-Reply-To: <87pog4gihe.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel , Carlo Zancanaro Ludovic Court=C3=A8s transcribed 1.7K bytes: > Hi ng0, >=20 > ng0 skribis: >=20 > > Let's take this thread, starting at > > "https://lists.gnu.org/archive/html/guix-devel/2017-04/msg00329.html"= . > > Ludovic worked on something, pushed it, did some changes to the relev= ant > > documentation but further examples in the documentation which are now > > affected weren't fixed with the push. We spent time answering questio= ns > > about broken configurations, assuming everyone who uses GuixSD now an= d > > in the future has a fairly competent knowledge of Guile, explaining c= hanges > > which could have been avoided - or at least reduced in frequency of q= uestions > > asked - by changing examples. >=20 > I think there=E2=80=99s a misunderstanding. This change is what starte= d the > discussion we=E2=80=99re having with Carlo, but it is a compatible chan= ge: > GuixSD configs that previously worked still do. Yep, sorry. I figured out that much after having my GuixSD based mailserv= er running. Cause and Reaction, okay... but what I've asked about still stan= ds on its own, it would be better if certain changes are discussed and we co= me up with a solid system of announcing changes in case they should break so= mething. I like how Gentoo and Archlinux solved it. > Thus I don=E2=80=99t think anyone spent time =E2=80=9Canswering questio= ns about broken > configurations=E2=80=9D in this case. For the same reason, examples in= the doc > that were valid before are still valid after the change. >=20 > > If Ludovic would've presented this change before applying it, it woul= d've > > been one of the obvious problems: don't just document the change, cha= nge > > further documentation sections which rely on this. This way we don't = have > > a documentation which presents people examples but contradicts itself= later > > on. >=20 > What part of the documentation contradicts itself? I=E2=80=99m confuse= d. None, the message you initially wrote about the change could've been less implicit. Like "In addition to $OLD you can now write $NEW, $OLD is still valid and will work". > As for posting the change before applying it, I should do more of that. > I=E2=80=99ve taken the bad habit of pushing what I consider as =E2=80=9C= simple=E2=80=9D changes > directly to the repo, but perhaps the criteria should be reconsidered. > :-) >=20 > Thoughts? >=20 > Ludo=E2=80=99. >=20 --=20 PGP and more: https://people.pragmatique.xyz/ng0/