all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Call for project proposals: Guix and Outreachy
Date: Wed, 07 Feb 2018 10:58:28 +0100	[thread overview]
Message-ID: <871shxunnf.fsf@elephly.net> (raw)
In-Reply-To: <CAE4v=pg_OHBEYROBcQ+MBHLXM3eyvNy6pG=nVtFXi9Ng2AGDJQ@mail.gmail.com>


Hi Gábor,

thanks for your ideas.

> 1. port guix to RISCV - I currently feel I could not mentor this
> though.

I have a feeling that this may not be suitable for a three-month
internship because we don’t even have the RISC-V toolchain yet.
Building these things takes a long time, so it can be quite discouraging
for a new contributor to work on this.

> 2. write a JVM inmplementation in guile to stabilize our java
> bootstrap path

This is quite a lot of work and not really suited for new contributors.
I like the idea, though, and think that eventually some of us should
give it a try.

> 3. rewrite more things currently provided by bootstrap binaries in
> guile to reduce our bootsrap binary base.

This seems good, as it consists of many independent sub-projects.  On
the other hand: we already have a couple of implementations that are
just not used in Guix at this point.  For example, there are a couple of
Guile implementations of tar out there (I remember Mark H Weaver posted
one some years ago), and there’s even a Bash interpreter out there
(written by Rutger).

> 9. get guix publish to work on some solution, that allows us to share
> pre-built packages outside our local network - I have a feeling that this
> could speed up development on core-updates and feature branches.

Do you mean publishing to GNUnet?

> 10. provide user interface to our build farm where we could request
> building a specific package.

A user interface to the build farm would generally be useful.  I don’t
see how it would keep someone busy for three months, but I think this
proposal is worth fleshing out.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-02-07  9:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 21:59 Call for project proposals: Guix and Outreachy Ricardo Wurmus
2018-01-26 11:53 ` Alex Sassmannshausen
2018-01-27  2:01   ` pelzflorian (Florian Pelz)
2018-01-27 11:45     ` Alex Sassmannshausen
2018-01-28 16:42   ` Ricardo Wurmus
2018-01-29 11:11     ` Alex Sassmannshausen
2018-02-06 22:05 ` Ricardo Wurmus
2018-02-07  7:51   ` Gábor Boskovits
2018-02-07  9:58     ` Ricardo Wurmus [this message]
2018-02-07 10:45       ` Gábor Boskovits
2018-02-08 13:47       ` Ludovic Courtès
2018-02-07 10:57     ` Andreas Enge
2018-02-08 13:48       ` Ludovic Courtès
2018-02-08 16:23         ` Ricardo Wurmus
2018-02-08 19:26           ` Gábor Boskovits
2018-02-08 19:58             ` Ricardo Wurmus
2018-02-10  7:08               ` Gábor Boskovits
2018-02-10  3:06     ` Chris Marusich
2018-02-10  6:52       ` Gábor Boskovits
2018-02-10 10:12       ` Ricardo Wurmus
2018-02-07 10:52   ` Andreas Enge

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=871shxunnf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@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.