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: Sat, 28 Dec 2019 01:02:25 +0100 Message-ID: <87k16hco6m.fsf@gnu.org> References: <87tv616q5s.fsf@posteo.net> <877e2qqilt.fsf@gnu.org> <8736ddcjs8.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]:33750) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikzYr-0007VX-JL for guix-devel@gnu.org; Fri, 27 Dec 2019 19:02:30 -0500 In-Reply-To: <8736ddcjs8.fsf@gnu.org> (Brett Gilio's message of "Sat, 21 Dec 2019 17:59:19 -0600") 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: Brett Gilio Cc: guix-devel@gnu.org, bandali@gnu.org Hi Brett, Brett Gilio skribis: > 1. Just as the bootstrappability and guix-hpc projects have their own > websites documenting their efforts, I think it would be nice to have > https://fm.guix.gnu.org/ which would host a Haunt-generated > website. This website would be hosted in the Savannah project structure > for GNU Guix. This would document who is active in the coordination and > oversight of this working group, and would express a clear and mutual > relationship with the GNU Guix / Guix System project. Like I wrote in another message, the only question will be the domain name, but other than that it sounds great. > 2. Perhaps we should adopt a particular tag for the Guix Debbugs > tracker, so as to be able to clearly delineate that this particular > patch or bug is in relation with the formal methods working > group. Maybe something like [FM]. I=E2=80=99d say let=E2=80=99s figure it out when it becomes an issue. :-) > 3. It was suggested that maybe a #guix-fm IRC channel might be useful, > but we have had a mixed bag of opinions on this. I personally think that > keeping everything together is the better solution, but I'd still like > to hear acceptance or criticism of this idea. Keeping everything on #guix for now sounds like the right thing to me. > 4. A lot of documenting working group milestones (Working on a Coq > sub-importer for OPAM, writing a bootstrapping compiler for SML97, > doing regular packaging duties for formal methods projects, > communicating upstream about distribution package quality, and perhaps > even trying to do formal methods work via synthesis in GNU Guile / GNU > Guix would be likely best expressed on the mailing list, and the > https://fm.guix.gnu.org/ website, but this likely rests in the hands of > the GNU Guix maintainers, of which I am not. > > 5. Additionally, maybe making an introductory post on the > https://guix.gnu.org/ blog about the preliminary goals of the working > group, after having our own subdomain established, would be a good way > to attract some attention to the project by distributing links to it on > HackerNews, Reddit, and Formal Methods/Functional Programming-related > mailing lists. Sounds like a great plan to me! Ludo=E2=80=99.