From: ng0 <ngillmann@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Some questions regarding GuixSD
Date: Fri, 30 Sep 2016 16:47:39 +0000 [thread overview]
Message-ID: <87lgy95o7o.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87intdmkvm.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi!
>
> ng0 <ngillmann@runbox.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>>>> 4) Is GnuNET integration already working?
>>>
>>> No.
>>
>> It's a bit of a stretch (in time), but I've applied for funding
>> yesterday and one of the 3 ideas is to push gnunet integration further,
>> to aid the live-system I am working on. I say 'stretch' because this is
>> a topic which requires some preparing contributions and then lots of
>> testing and diving deeper into the core of Guix :)
>> So if all goes well, I know around december if I qualified with my idea
>> for funding and can almost worry-free hack on this for another 6
>> months.
>> It's like Google Summer of Code, only a bit longer. I'll very optimistic
>> and say that my internal documented goal for basic gnunet-filesystem
>> integration for guix is summer / autumn 2017.
>
> That would be awesome!
>
> I really hope a regular release cycle will be running for GNUnet by
> then, because that’s currently quite a showstopper IMO.
I think Christian mentioned some tasks which need to be done to make
this happen. Maybe you could get in touch with him about this and ask
how Guix and GNUnet can cooperate with this?
If only cuiras could produce tarballs (or run additional tasks which
lead to tarballs) for other systems to use, that would be a great
option.
> Good luck with your application!
>
> Ludo’.
>
Thanks!
--
next prev parent reply other threads:[~2016-09-30 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 1:09 Some questions regarding GuixSD dian_cecht
2016-09-30 8:18 ` Ludovic Courtès
2016-09-30 12:07 ` ng0
2016-09-30 16:07 ` Ludovic Courtès
2016-09-30 16:47 ` ng0 [this message]
2016-09-30 19:50 ` dian_cecht
2016-09-30 19:46 ` dian_cecht
2016-10-01 1:50 ` 宋文武
2016-10-01 2:19 ` dian_cecht
2016-10-01 3:42 ` 宋文武
2016-10-01 8:42 ` ng0
2016-10-02 13:14 ` Ludovic Courtès
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=87lgy95o7o.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=help-guix@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.
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).