From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Call for project proposals: Guix and Outreachy
Date: Fri, 26 Jan 2018 12:53:37 +0100 [thread overview]
Message-ID: <874ln896pq.fsf@gmail.com> (raw)
In-Reply-To: <87fu6y27re.fsf@elephly.net>
Hi Ricardo,
Ricardo Wurmus writes:
> on behalf of the Guix community I submitted an application for this
> project to participate in Outreachy, an internship project for people
> from sections of the population that are commonly underrepresented in
> the world of free software development.
>
> Our application is currently undergoing review. If accepted we will
> fund one intern for the upcoming internship period between May and
> August.
This is great news — well done for taking the initiative.
> The Guix community already has a landing page on the Outreachy website:
>
> https://www.outreachy.org/communities/cfp/gnu-guix/
>
> You can already submit project proposals on this page, which Ludo and I
> would review and approve. Please consider becoming a co-mentor for a
> project to make our ongoing participation in Outreachy a success.
I have read through the documentation and I believe I would be able to
commit to the duties of being a mentor / co-mentor.
I would be happy to send more details of where I believe my relative
strengths and weaknesses in this project would be. I couldn't see an
appropriate place for that on the outreachy website — would it be best
to discuss this by email with you two? Or on list?
> Feel free to discuss project ideas right here before submitting an
> official proposal. Project ideas for the Google Summer of Code are
> equally valid for an Outreachy internship.
Wrt to project ideas, if I understand the target audience right, I would
propose perhaps as one project a strengthening of the Guile tooling
around Guix.
Starter tasks could be helping to package and review existing packages
of Guile software for Guix.
Actual project tasks could revolve around developing a nice Guile build
system for Guix.
First steps would be perhaps to enhance the gnu-build-system with
additional phases for Guile specific tasks (setting the Guile site path
correctly, ensuring guile dependencies are propagated inputs…)
A second step might be a simplified Guile build system, which does not
rely on autotools infrastructure. I believe this was discussed in the
past: it would be a "beginners build system" for *Guile only* packages
for quick and easy sharing in the Guix community.
Finally we might look at first steps to generate guix package recipes
from guile projects. A first step might be a well-defined script that
generates a new project filetree, and writes a guix.scm file within it
that contains a Guix recipe using the beginners guile build system.
What do you think?
Alex
next prev parent reply other threads:[~2018-01-26 18:18 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 [this message]
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
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=874ln896pq.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=guix-devel@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.