unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix Outreachy project looking for co-mentor
Date: Wed, 26 Sep 2018 20:00:32 +0200	[thread overview]
Message-ID: <875zyst9z3.fsf@elephly.net> (raw)
In-Reply-To: <87wor81n2c.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hello!
>
> Gábor Boskovits <boskovits@gmail.com> skribis:
>
>> we are looking for co-mentors to the 2018 December round of the Outreachy
>> project.
>>
>> We have one project proposal approved:
>> Create user video documentation for GNU Guix.
>
> Nice!
>
> I encourage people on this list to volunteer to co-mentor this project:
> increasing our bus factor¹ is important (really!) and so is bringing
> people from diverse backgrounds to the project, and this is a nice
> project that can make a big difference for Guix.

I agree.  This video documentation project is very different from other
GSoC or Outreachy projects of the past in that they don’t really require
programming skills.  This makes it easier for mentors as well.

If you are a contributor to Guix and you are familiar with how to use
Guix and what sets it apart from related systems you might be able to
co-mentor this project.  If you aren’t sure feel free to get in touch
with Gábor and me (even off-list).

> Among the other ideas that were thrown on IRC was that of a GNOME
> Software backend.  If people have an interest in this, we can still dig
> a bit and formalize it.  Thoughts?

For that project I think it would be advisable to get in touch with the
maintainers of GNOME Software to better understand what would need to be
done on their side.  I’d feel uncomfortable starting a project for
Outreachy unilaterally without having a liaison on the GNOME side.

For internships we need to make sure that we control enough of the
variables that could lead to failure.  I think this may not be possible
if the work happens on a foreign code base with a developer community
that we aren’t yet part of.

This is doable, but it requires more than the usual preparation by a
potential mentor.

--
Ricardo

  reply	other threads:[~2018-09-26 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  9:36 Guix Outreachy project looking for co-mentor Gábor Boskovits
2018-09-26 12:05 ` Ludovic Courtès
2018-09-26 18:00   ` Ricardo Wurmus [this message]
2018-09-27 13:51     ` Ludovic Courtès
2018-09-27 15:18       ` Gábor Boskovits
2018-09-27 15:30         ` Ludovic Courtès
2018-09-27 16:00           ` Ricardo Wurmus
2018-09-27 21:31             ` Björn Höfling

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=875zyst9z3.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).