From: Brett Gilio <brettg@posteo.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org, janekke@gnu.org, bandali@gnu.org
Subject: Re: [Proposal] The Formal Methods in GNU Guix Working Group
Date: Mon, 16 Dec 2019 21:27:30 -0600 [thread overview]
Message-ID: <874kxzzl5p.fsf@posteo.net> (raw)
In-Reply-To: <141B1FAE-6518-4E0C-8E69-C96BCB540545@lepiller.eu> (Julien Lepiller's message of "Mon, 16 Dec 2019 09:47:55 +0100")
Julien Lepiller <julien@lepiller.eu> writes:
> OCaml stuff can easily be imported with guix import opam. I know coq
> packages use a separate opam repository, so it would be nice if the
> importer could take an optional parameter to indicate a custom opam
> repository url. I'm not sure the coq repo is converted to opam 2 yet
> though.
To my knowledge the Coq repo is not compliant with OPAM 2 quite
yet. Maybe this has changed since I last checked, but I would be more
than happy to ask upstream if this is still the case. I think working on
an importer for those modified OPAM->Coq packages would be a fantastic
start to that problem.
> I can see the benefits of formal methods and benefits of guix, but
> what does guix provide or could provide to formal method people
> specifically? Is it "only" the nice guarantees it gives to any
> programer, or is there something else? Maybe the question is why does
> it matter more to fm people than to other programmers?
I think it is a combination of what every other programmer is offered,
and the possibilities offered by what bootstrapping has to offer for
creating a machine from "nothing". There is still a lot of unknowns
here, but I speculate that there is definitely more to be found as the
concept progresses. I think your question is valid, and should likely be
a central thesis to the working group; "What does Guix offer to the
formal methods community that it could specifically benefit from?"
> I think we're still a small community, so we can continue talking
> about it on the main channel. We're trying to avoid dividing
> information, that's why we allow any language on tge channel, instead
> of having separate chans for each language. We also always hear about
> bootstrapping or the hpc effort on the main channel. Let's talk about
> fm :). You can count me in.
Agreed, lets not separate the community. Keep the communication
integrated. Though, I wonder if maybe I could draft an article for the
Guix website blog; or maybe we could organize our goals somewhere? I am
not quite sure what the best option here is. For example, one of the
goals is a possible bootstrapping compiler for ML that I mentioned
before, that would be dedicated to the GNU project in a similar fashion
to Jan's GNU Mes (which, thank you Jan for the supportive
messages). Combine this on maybe working out a bootstrap for OCaml,
creating an importer for Coq, working on some more programming
research-related questions in the context of Guix and suddenly we have
ourselves a trifecta of big questions that need to be articulated
_somewhere_ so we can retain some scope. Maybe Guix needs a wiki similar
to the wishlist, but dedicated to working groups? I really have no
idea. Just something, somewhere to centralize our goals.
Regardless, thank you for the supportive voice Julien. I am glad to have
your support.
--
Brett M. Gilio <brettg@posteo.net>
GNU Guix, Contributor <https://guix.gnu.org/>
next prev parent reply other threads:[~2019-12-17 3:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 0:59 [Proposal] The Formal Methods in GNU Guix Working Group Brett Gilio
2019-12-16 8:47 ` Julien Lepiller
2019-12-16 9:22 ` Julien Lepiller
2019-12-17 3:29 ` Brett Gilio
2019-12-27 18:56 ` Ludovic Courtès
2019-12-27 22:33 ` Brett Gilio
2019-12-27 23:37 ` Ludovic Courtès
2019-12-28 2:59 ` Brett Gilio
2019-12-30 21:34 ` Ludovic Courtès
2019-12-31 10:17 ` Brett Gilio
2020-01-02 22:11 ` Ludovic Courtès
2020-01-03 23:49 ` Amin Bandali
2020-01-15 21:59 ` Ludovic Courtès
2020-01-13 19:27 ` Maxim Cournoyer
2019-12-28 7:20 ` Amin Bandali
2019-12-28 11:28 ` Vicente Eduardo
2019-12-29 8:09 ` Jan Nieuwenhuizen
2019-12-17 3:27 ` Brett Gilio [this message]
2019-12-16 19:46 ` zimoun
2019-12-16 20:10 ` Julien Lepiller
2019-12-17 3:40 ` Brett Gilio
2019-12-27 23:56 ` Ludovic Courtès
2019-12-28 2:55 ` Brett Gilio
2019-12-17 3:38 ` Brett Gilio
2019-12-16 23:04 ` Jack Hill
2019-12-17 1:33 ` John Soo
2019-12-17 3:49 ` Brett Gilio
2019-12-17 3:48 ` Brett Gilio
2019-12-21 6:48 ` Amin Bandali
2019-12-21 23:59 ` Brett Gilio
2019-12-28 0:02 ` Ludovic Courtès
2019-12-27 23:54 ` Ludovic Courtès
2019-12-28 3:06 ` Brett Gilio
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 19:17 Alexandru-Sergiu Marton
2020-02-12 12:02 Orians, Jeremiah (DTMB)
2020-02-12 14:16 ` zimoun
2020-02-12 14:38 ` Svante Signell
2020-02-12 14:48 ` Jan Nieuwenhuizen
2020-02-12 20:59 ` Bengt Richter
2020-02-13 12:13 ` Orians, Jeremiah (DTMB)
2020-02-13 12:07 ` Orians, Jeremiah (DTMB)
2020-02-15 16:10 ` zimoun
2020-02-18 11:17 ` Orians, Jeremiah (DTMB)
2020-02-21 14:47 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kxzzl5p.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=bandali@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janekke@gnu.org \
--cc=julien@lepiller.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).