From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Call for project proposals: Guix and Outreachy
Date: Thu, 08 Feb 2018 17:23:55 +0100 [thread overview]
Message-ID: <87mv0j78mc.fsf@elephly.net> (raw)
In-Reply-To: <87zi4jvbgg.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Andreas Enge <andreas@enge.fr> skribis:
>
>> quite a list of interesting ideas!
>>
>> On Wed, Feb 07, 2018 at 08:51:10AM +0100, Gábor Boskovits wrote:
>>> 10. provide user interface to our build farm where we could request building a
>>> specific package.
>>
>> This is one specific feature, but could be framed into a more general
>> project of creating a web frontend to cuirass, with a number of subtasks
>> (one thing that we use a lot on hydra: with one click, restart the build
>> of all packages that failed previously).
>>
>> As in Ricardo's suggestion, this would appeal to diverse competences,
>> in guile, javascript, databases and interface design. So I think something
>> interesting and useful would certainly come out of it.
>
> Agreed! Actually one thing is adding more /api/* HTTP entry points.
> Another one is writing the Web frontend. Each of these could be a
> project on its own, I think.
>
> Thoughts?
>
> Ricardo, should we draft something on this topic?
Our problem at this point is to recruit mentors. Whoever submits the
project proposal on the Outreachy website[1] applies to become a mentor.
This is then either approved or declined by Ludovic or myself.
The project idea sounds good, but we really need a mentor who feels
responsible for this project and who will be able to guide an intern
throughout the application phase and the three-month internship between
from May to August.
I would be very happy if someone who is willing to oversee this project
would write a draft and submit it on the Outreachy website[1].
I volunteer to be a co-mentor for when the main mentor needs a free
weekend or something like that, but I can only assist, not lead the
project.
[1]: https://www.outreachy.org/communities/cfp/gnu-guix/submit-project/
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-08 16:24 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
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 [this message]
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=87mv0j78mc.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@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.
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.