From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: [Proposal] The Formal Methods in GNU Guix Working Group Date: Wed, 15 Jan 2020 22:59:40 +0100 Message-ID: <87d0bknzxv.fsf@gnu.org> References: <87tv616q5s.fsf@posteo.net> <141B1FAE-6518-4E0C-8E69-C96BCB540545@lepiller.eu> <878smxegxp.fsf@gnu.org> <87tv5ls8kj.fsf@gnu.org> <871rspe3x3.fsf@gnu.org> <875zi1qhoc.fsf@gnu.org> <87o8vp1os4.fsf@gnu.org> <87blrlse36.fsf@gnu.org> <87eewg5cee.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:470:142:3::10]:59797) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irqhk-00064X-4Z for guix-devel@gnu.org; Wed, 15 Jan 2020 17:00:01 -0500 In-Reply-To: <87eewg5cee.fsf@gnu.org> (Amin Bandali's message of "Fri, 03 Jan 2020 18:49:13 -0500") 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-mx.org@gnu.org Sender: "Guix-devel" To: Brett Gilio Cc: guix-devel@gnu.org, GNU Guix maintainers Hi Amin & Brett, Amin Bandali skribis: >> It=E2=80=99s fine to host the repo on Savannah: we can ask for a new rep= o under >> the Guix umbrella, the downside being that access control will be the >> same as for the other repos (we can only grant access to all the repos >> or none of them.) If you plan to open it more to formal methods people >> that do not yet contribute to Guix, it might be easier to use a separate >> repo. You tell us! >> > > Right. Thinking about this, as I see it right now I think our use cases > for repos fall roughly into two categories: > > - Closely Guix-related or small standalone things: this could be things > like the Haunt sources for our site, or a Guix channel for additional > package definitions, or anything closely related to Guix and/or small > enough to fit under the Guix umbrella just fine. For these, we should > be able to get by with a very small number of repos in the short and > long term. Initially, we will only have one such repository, say, > guix/guix-fm.git or guix/formal-methods.git, with its purpose being > mainly to keep the sources for the site. > > For these repos we=E2=80=99ll happily accept patches from folks who are= n=E2=80=99t > Guix contributors via mailing list. And I=E2=80=99d imagine once they = have > contributed enough patches, we could work out getting them commit > access, especially if their gathered knowledge/experience extends to > Guix directly (e.g. in form of familiarity with package definitions > and writing them). Sounds good to me. > - Larger projects or ones that don=E2=80=99t quite fit the scope of Guix:= for > these, we might indeed consider registering separate Savannah projects > rather than putting them under the Guix project. I think the proposed > bootstrapping ML compiler could be an example of such project. Yes. > All that said, I do wish Savannah supported finer access control at the > project level. I just asked a fellow Savannah hacker for his opinion on > whether implementing that would be possible and feasible with the > current underlying infrastructure in mind. I suppose it would be hard and not necessarily advisable given that Savane is no longer actively developed, AIUI. >> As for the domain name: I think it would be fine to use >> formal-methods.guix.gnu.org as long as the web site follows GNU and Guix >> policy, which mostly means referring only to free software, avoiding the >> phrase =E2=80=9Copen source=E2=80=9D to describe it, and probably avoidi= ng institution >> logos and such (I don=E2=80=99t think there=E2=80=99s any written policy= but I would >> personally find it out of place on gnu.org.) Anyway, the two of you are >> webmasters so you probably know this better than I do. IOW, if you want >> to flatter your employers and labs, you might want to opt for a separate >> web site. :-) >> > > Most certainly; I wouldn=E2=80=99t expect anything less. :-) > > As for institution logos, agreed. If it ever comes such time that we > absolutely =E2=80=9Chave to=E2=80=9D consider that, I=E2=80=99ll be sure = to check with you and > the other Guix maintainers, fellow GNU webmasters, and of course rms. Sure, sounds good to me! (Note that rms doesn=E2=80=99t have a say here, t= hough.) > As for the domain name, I think formal-methods.guix.gnu.org is a bit of > a mouthful to type or say on a regular basis, and I think an abbreviated > fm.guix.gnu.org would be more convenient; =C3=A0 la ci.guix.gnu.org. For > what it=E2=80=99s worth, I=E2=80=99ve seen the FM abbreviation for Formal= Methods used > fairly commonly around the community. Alright, I like expressive phrases like =E2=80=98call-with-current-continua= tion=E2=80=99 but I=E2=80=99m fine with =E2=80=9Cfm=E2=80=9D nonetheless. ;-) > Lastly, I think it would be nice to have a guix-fm@gnu.org address for > Guix-FM. Rather than a full-fledged Mailman list, I think a simple > alias, like with guix-hpc@gnu.org, will suffice. Thoughts? Yeah, I guess a simple alias is enough for things that don=E2=80=99t fit on guix-devel (guix-hpc@gnu.org is very low traffic, mostly for when one needs to reach out to the usual HPC suspects.) Let us know when you have a web page ready. Then you=E2=80=99re welcome to= send a patch against maintenance.git for =E2=80=98bayfront.scm=E2=80=99 (DNS con= fig and probably web site as well.) Thanks! Ludo=E2=80=99.