From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: some questions about GUIX
Date: Wed, 30 Dec 2015 00:10:39 +0100 [thread overview]
Message-ID: <8760zg26mo.fsf@gnu.org> (raw)
In-Reply-To: <87a8otax38.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 29 Dec 2015 20:11:55 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Sam Halliday <sam.halliday@gmail.com> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>>> Guix’s build daemon uses containers to perform isolated builds:
>>>
>>> http://www.gnu.org/software/guix/manual/html_node/Features.html
>>
>> Interesting. I wonder if you wouldn't benefit from a docker / drone
>> network, just as a distribution mechanism for your own build farm. It
>> would be a shame to expend effort on that since it is somewhat something
>> of a solved problem (and purely a DevOps matter, not a user concern).
>
> Work is under way to distribute build artifacts over GNUnet. Currently
> it is already possible to share build results over HTTP. Ideally,
> package building is a distributed effort. (We aren’t there yet.)
There’s also the offloading mechanism, which may be closer to what Sam
was mentioning:
https://www.gnu.org/software/guix/manual/html_node/Daemon-Offload-Setup.html
>>>> * Issue tracker / comm channels
>>>>
>>>> Will you be continuing to use debbugs, savannah and mailing lists going
>>>> forward or would you consider moving to a modern community management
>>>> system like gitlab?
>>>
>>> I hear the appeal of GitLab and the like. However, as was recently
>>> discussed on guix-devel, while I think we must find ways to improve our
>>> workflows (for instance, tracking patches is becoming tricky), I don’t
>>> see us moving to one of those web-based approaches for several reasons:
>>>
>>> https://lists.gnu.org/archive/html/guix-devel/2015-12/msg00429.html
>>
>> I've never used GitLab, but I understand that it is free software. The
>> thread above seems to suggest that it is proprietary.
>
> There are two variants AFAIU; the hosted GitLab service uses the
> proprietary version.
Right, gitlab.com runs “GitLab EE”, which is proprietary.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-12-29 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 15:36 some questions about GUIX Sam Halliday
2015-12-29 15:00 ` Ludovic Courtès
2015-12-29 15:40 ` Sam Halliday
2015-12-29 19:11 ` Ricardo Wurmus
2015-12-29 19:46 ` Leo Famulari
2015-12-29 23:10 ` Ludovic Courtès [this message]
2015-12-29 23:35 ` Sam Halliday
2015-12-31 9:50 ` Ricardo Wurmus
2015-12-30 13:36 ` Sam Halliday
2015-12-31 2:02 ` Leo Famulari
2015-12-31 2:17 ` Leo Famulari
2015-12-31 12:46 ` Sam Halliday
2016-01-01 14:45 ` Ludovic Courtès
2015-12-31 9:30 ` Ricardo Wurmus
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=8760zg26mo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.