unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Participating in the next Outreachy round of internships?
Date: Sun, 28 Jul 2019 19:15:23 +0200	[thread overview]
Message-ID: <877e8284ic.fsf@elephly.net> (raw)
In-Reply-To: <878ssigr8j.fsf@nckx>


Tobias Geerinckx-Rice <me@tobias.gr> writes:

>> My schedule is quite confused at the moment, but I would be
>> interested in
>> serving as a community coordinator this time. However i am not sure
>> what
>> does it involve. Could you send a message with the details, so that
>> I can
>> find out if I can manage that?
>
> That would be great, considering your previous experience as a mentor.

I second this.

> If it wouldn't work out, I'm also interested in coordinating, but
> would also like to know more about what's expected (from me & from my
> schedule).

The Outreachy website displays this paragraph to explain what the role
of the coordinator entails:

   Each internship project must be associated with a free and open
   source software community participating in Outreachy. That community
   provides funding for interns, either directly from community funds,
   or by finding a company or foundation to sponsor interns. Each
   community has one or more coordinators, who review submitted
   projects, approve mentors, and generally provide a communication link
   between the mentors and Outreachy organizers.

There’s a short list of duties here:
https://www.outreachy.org/mentor/#coordinator

It’s really just about ensuring that there are mentors, that they
propose projects (this is not like GSoC where a rough idea somewhere in
a Wiki is sufficient), that the proposed projects are suitable, that
there really still are mentors after the projects have been approved,
etc.  Much of the work happens *before* the internship begins.

Coordinators are also expected to help mentors reach decisions regarding
interns.  Being familiar with Outreachy from the inside due to past
experience as a mentor will come in handy, but it is not absolutely
required.

--
Ricardo

      reply	other threads:[~2019-07-28 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28  9:47 Participating in the next Outreachy round of internships? Ricardo Wurmus
2019-07-28 13:30 ` Gábor Boskovits
2019-07-28 14:37   ` Tobias Geerinckx-Rice
2019-07-28 17:15     ` Ricardo Wurmus [this message]

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=877e8284ic.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).