From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Thomas Danckaert <post@thomasdanckaert.be>,
alex.sassmannshausen@gmail.com, pjotr2016@thebird.nl,
guix-devel@gnu.org
Subject: Re: FOSDEM 2018 Guile devroom
Date: Thu, 19 Oct 2017 11:05:56 +0200 [thread overview]
Message-ID: <87efpz33te.fsf@elephly.net> (raw)
In-Reply-To: <874lqvoakm.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hello!
>
> [- guile-devel]
>
> Thomas Danckaert <post@thomasdanckaert.be> skribis:
>
>> Just to get everybody excited: https://fosdem.org/2018/schedule
>> includes (among others) devrooms for
>>
>> - “Package Management”
>>
>> - “HPC, Big Data and Data Science”
>>
>> - “Distributions”
>>
>> - “Containers”
>>
>> - “Config Management”
>>
>> -“Free Java”
>
> Awesome. These tracks are good opportunities to reach out to people who
> otherwise wouldn’t hear about Guix(SD). Given how many people were in
> the Guile/Guix devroom last year, I’m sure we could afford to have one
> talk in each track. ;-) Let’s synchronize!
“Free Java” is an interesting name for a devroom track. I guess I could
talk about freedom problems with the Java culture of never building
software recursively from source, and introduce how we’re approaching
this problem in Guix.
The Java bootstrap could also be demonstrated in that talk.
(Does anyone know how this is done in Debian? Do they actually build
all of their Java packages from source?)
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-10-19 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 20:34 FOSDEM 2018 Guile devroom Manolis Ragkousis
2017-10-06 19:15 ` Ricardo Wurmus
2017-10-18 15:15 ` Thomas Danckaert
2017-10-19 7:34 ` Ludovic Courtès
2017-10-19 9:05 ` Ricardo Wurmus [this message]
2017-10-19 20:25 ` Ludovic Courtès
2017-10-25 19:20 ` Efraim Flashner
2017-10-25 19:24 ` Efraim Flashner
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=87efpz33te.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=alex.sassmannshausen@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=pjotr2016@thebird.nl \
--cc=post@thomasdanckaert.be \
/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.