all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: [Proposal] The Formal Methods in GNU Guix Working Group
Date: Fri, 03 Jan 2020 18:49:13 -0500	[thread overview]
Message-ID: <87eewg5cee.fsf@gnu.org> (raw)
In-Reply-To: <87blrlse36.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 4472 bytes --]

Hi Ludo’, all,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello!
>
> (Cc: maintainers.)
>
> Brett Gilio <brettg@gnu.org> skribis:
>
>> Dec 30, 2019 3:34:22 PM Ludovic Courtès :
>>
>>> Guix-HPC is “institutional”, that’s part of the reason behind this.
>>> Regarding gitlab.inria.fr, that’s because it used to be hosted at Inria.
>>> Also, is a channel developed
>>> by colleagues at Inria, so it’s more convenient to have it there.
>>
>>
>> Hey Ludo, thanks for the explanation.
>>
>> It makes sense why Guix-HPC lives somewhere else. Given this, what
>> do you propose for initiating the conversation on where the formal
>> methods haunt page should live with the other maintainers? I
>> personally think the repository should live on Savannah, but the
>> address needs to be discussed.
>
> It’s fine to host the repo on Savannah: we can ask for a new repo 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’ll happily accept patches from folks who aren’t
  Guix contributors via mailing list.  And I’d 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).

- Larger projects or ones that don’t 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.

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.

>
> 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 “open source” to describe it, and probably avoiding institution
> logos and such (I don’t think there’s 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’t expect anything less. :-)

As for institution logos, agreed.  If it ever comes such time that we
absolutely “have to” consider that, I’ll be sure to check with you and
the other Guix maintainers, fellow GNU webmasters, and of course rms.

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; à la ci.guix.gnu.org.  For
what it’s worth, I’ve seen the FM abbreviation for Formal Methods used
fairly commonly around the community.

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?

>
> Maintainers, what do you think?
>
> Anyway, step #1 is to get a web page ready.  :-)
>
> Ludo’.

I’ll work on putting one together over the next couple of days. :-)

Best,
amin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

  reply	other threads:[~2020-01-03 23:49 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eewg5cee.fsf@gnu.org \
    --to=bandali@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.