All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: Xorg Members List <members@x.org>,
	"mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
	xorg-devel <xorg-devel@lists.x.org>,
	 "wayland-devel@lists.freedesktop.org"
	<wayland-devel@lists.freedesktop.org>,
	nouveau <nouveau@lists.freedesktop.org>,
	 dri-devel <dri-devel@lists.freedesktop.org>,
	IGT development <igt-dev@lists.freedesktop.org>,
	 amd-gfx list <amd-gfx@lists.freedesktop.org>
Cc: board@x.org
Subject: Re: [Nouveau] Help needed for EVoC/GSoC/Outreachy
Date: Thu, 05 Aug 2021 16:22:40 -0400	[thread overview]
Message-ID: <fbe03a5f99edfe119ffcdc47de5b7baf8e84549e.camel@redhat.com> (raw)
In-Reply-To: <5a2b5d77c100a21b3d9e4eb0048c36a94cd1e4ea.camel@redhat.com>

Hi everyone! I got some questions from someone that made me realize that
there's a couple of things that I forgot to mention here that might be
useful for folks to know regarding being a mentor:

* "Who decides what project and what student?"
  It's up to the student to come up with ideas for what they want to work on,
  although we will occasionally have a list of potential project ideas that
  students are welcome to use or draw inspiration from. Since X.org participates
  as a foundation, pretty much any of the projects under the X.org umbrella are
  allowed to do this if they're willing to come up with mentors. As for who the
  mentors are, that's really all just up to who's volunteering for it on a given
  project.
  As for how we decide what students we accept, that decision is usually made
  based off the quality of their project proposal along with whether a student
  seems self-sufficient enough to accomplish said project. Most students who
  come to us with a project idea already typically fall into this category. The
  final decision for this is typically made by the student's proposed mentor
  and/or our volunteer GSoC/Outreachy/EVoC admin.
* "I assume this is international?"
  X.org tries to make our student outreach programs as international as
  possible. GSoC covers most of the world, but there are definitely some areas
  it doesn't cover - which is why we've ran EVoC in the past, so that students
  in areas that wouldn't be eligible for GSoC would still have a chance at
  participating in a project. Outreachy also helps fill this gap, as I don't
  believe they have the same kind of international restrictions that GSoC does.
* What is the expected result, a grading?
  Yes.

On Wed, 2021-07-14 at 16:32 -0400, Lyude Paul wrote:
> Hi! As some of you might already be aware, after helping out X.org
> project the previous years with regards to student outreach, Trevor
> decided to retire from this position in hopes that someone else will be
> able to step up and take on these responsibilities. As such, we're
> trying to find people who would be willing to volunteer their time to
> help out with getting us involved once again in student outreach
> programs.
> 
> In the past, X.org has been active in the GSoC program, occasionally
> Outreachy, and our own EVoC program. As of 2021 though, GSoC decided to
> shorten the amount of time allocated for a student to work on their
> project. This unfortunately posed some problems for
> X.org/freedesktop.org as a lot of the potential work that would have
> been good for us to have students working on wouldn't really fit within
> the new GSoC timeframe. While it's certainly possible that there will be
> projects that come up in the future which do fit into this new timeline,
> we think it'd be a good idea to step up our involvement again with
> Outreachy where the program is a good bit more flexible then GSoC. We've
> also had pretty good experience working with the Outreachy candidates
> we've had in the past.
> 
> The other main topic of discussion is around the fact that our own
> program, EVoC, hasn't really had anyone available to volunteer to help
> run it for a while now. For those who aren't aware, EVoC is a program
> similar to Google Summer of Code that X.org started running with much
> more relaxed requirements then GSoC/Outreachy in order to help fill the
> gaps for any exceptional cases with students who would otherwise be left
> out by the requirements for GSoC/Outreachy. Typically though, EVoC is
> usually considered the last resort after a student has tried getting
> into GSoC/Outreachy.
> 
> So, the two biggest things that we need are:
> * Admin volunteer(s)
> * Mentors, mentors, mentors! We really need these the most.
> 
> So, what responsibilities would being an admin for this entail?
> 
> * Fielding questions from potential GSoC/EVoC/Outreachy participants.
>   Most of these students are just looking for simple details of how
>   these programs work and are looking for project ideas. Responding to
>   these inquiries is mostly just a matter of pointing students to
>   various pages on our wiki or replying with form/stock replies. Most of
>   the students at this phase expect to be handed a project and a mentor,
>   and therefore end up learning that they will need to come up with
>   their own project and mentor.
> * For the small handful of students that make it to the next phase and
>   figure out a project idea, they then need to find a mentor. Usually
>   the admin will help out by taking a look at who proposed the project
>   idea, and/or looking through commit messages and mailing list history
>   to try to find someone who would be a good fit and willing to mentor
>   the student. Sometimes this happens quickly, and sometimes it requires
>   poking a lot of people - and occasionally, there might not always be a
>   mentor to be found.
> * If we have a student, project, and mentor then the next step is having
>   the student write up a proposal. Many students start out with
>   over-simplified proposals, so a lot of this work is just gently
>   nudging students and getting them to refine their work items into a
>   week-by-week synopsis. There's usually a good bit of back and forth
>   with the student's proposal, and occasionally the mentor may be
>   involved with this step.
> * The admin then works with the student to come up with a timeline for
>   their work, taking into account any vacation time the student may
>   have, along with coordinating the frequency/type of meetings that
>   will happen between the student and the mentor. If the mentor is
>   unable to attend all of these meetings, it's usually up to the admin
>   to check in with the student to see how they are progressing and
>   potentially provide them tips if they get stuck.
> 
> As for being a mentor, it's pretty much as simple as it sounds: you work
> with students who have projects to help familiarize them with the
> project at hand, help them out wherever needed, check in on their
> progress, and guide them along the way towards reaching their project
> goal along with grading their work.
> 
> Please help spread the word on this, and contact anyone you know who
> might be involved with this! We'll be happy to provide more information
> on how you can get started. Remember, folks like myself wouldn't be in
> this community without projects like GSoC :).
> 

-- 
Cheers,
 Lyude Paul (she/her)
 Software Engineer at Red Hat


WARNING: multiple messages have this Message-ID
From: Lyude Paul <lyude@redhat.com>
To: Xorg Members List <members@x.org>,
	"mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
	xorg-devel <xorg-devel@lists.x.org>,
	 "wayland-devel@lists.freedesktop.org"
	<wayland-devel@lists.freedesktop.org>,
	nouveau <nouveau@lists.freedesktop.org>,
	 dri-devel <dri-devel@lists.freedesktop.org>,
	IGT development <igt-dev@lists.freedesktop.org>,
	 amd-gfx list <amd-gfx@lists.freedesktop.org>
Cc: board@x.org
Subject: Re: Help needed for EVoC/GSoC/Outreachy
Date: Thu, 05 Aug 2021 16:22:40 -0400	[thread overview]
Message-ID: <fbe03a5f99edfe119ffcdc47de5b7baf8e84549e.camel@redhat.com> (raw)
In-Reply-To: <5a2b5d77c100a21b3d9e4eb0048c36a94cd1e4ea.camel@redhat.com>

Hi everyone! I got some questions from someone that made me realize that
there's a couple of things that I forgot to mention here that might be
useful for folks to know regarding being a mentor:

* "Who decides what project and what student?"
  It's up to the student to come up with ideas for what they want to work on,
  although we will occasionally have a list of potential project ideas that
  students are welcome to use or draw inspiration from. Since X.org participates
  as a foundation, pretty much any of the projects under the X.org umbrella are
  allowed to do this if they're willing to come up with mentors. As for who the
  mentors are, that's really all just up to who's volunteering for it on a given
  project.
  As for how we decide what students we accept, that decision is usually made
  based off the quality of their project proposal along with whether a student
  seems self-sufficient enough to accomplish said project. Most students who
  come to us with a project idea already typically fall into this category. The
  final decision for this is typically made by the student's proposed mentor
  and/or our volunteer GSoC/Outreachy/EVoC admin.
* "I assume this is international?"
  X.org tries to make our student outreach programs as international as
  possible. GSoC covers most of the world, but there are definitely some areas
  it doesn't cover - which is why we've ran EVoC in the past, so that students
  in areas that wouldn't be eligible for GSoC would still have a chance at
  participating in a project. Outreachy also helps fill this gap, as I don't
  believe they have the same kind of international restrictions that GSoC does.
* What is the expected result, a grading?
  Yes.

On Wed, 2021-07-14 at 16:32 -0400, Lyude Paul wrote:
> Hi! As some of you might already be aware, after helping out X.org
> project the previous years with regards to student outreach, Trevor
> decided to retire from this position in hopes that someone else will be
> able to step up and take on these responsibilities. As such, we're
> trying to find people who would be willing to volunteer their time to
> help out with getting us involved once again in student outreach
> programs.
> 
> In the past, X.org has been active in the GSoC program, occasionally
> Outreachy, and our own EVoC program. As of 2021 though, GSoC decided to
> shorten the amount of time allocated for a student to work on their
> project. This unfortunately posed some problems for
> X.org/freedesktop.org as a lot of the potential work that would have
> been good for us to have students working on wouldn't really fit within
> the new GSoC timeframe. While it's certainly possible that there will be
> projects that come up in the future which do fit into this new timeline,
> we think it'd be a good idea to step up our involvement again with
> Outreachy where the program is a good bit more flexible then GSoC. We've
> also had pretty good experience working with the Outreachy candidates
> we've had in the past.
> 
> The other main topic of discussion is around the fact that our own
> program, EVoC, hasn't really had anyone available to volunteer to help
> run it for a while now. For those who aren't aware, EVoC is a program
> similar to Google Summer of Code that X.org started running with much
> more relaxed requirements then GSoC/Outreachy in order to help fill the
> gaps for any exceptional cases with students who would otherwise be left
> out by the requirements for GSoC/Outreachy. Typically though, EVoC is
> usually considered the last resort after a student has tried getting
> into GSoC/Outreachy.
> 
> So, the two biggest things that we need are:
> * Admin volunteer(s)
> * Mentors, mentors, mentors! We really need these the most.
> 
> So, what responsibilities would being an admin for this entail?
> 
> * Fielding questions from potential GSoC/EVoC/Outreachy participants.
>   Most of these students are just looking for simple details of how
>   these programs work and are looking for project ideas. Responding to
>   these inquiries is mostly just a matter of pointing students to
>   various pages on our wiki or replying with form/stock replies. Most of
>   the students at this phase expect to be handed a project and a mentor,
>   and therefore end up learning that they will need to come up with
>   their own project and mentor.
> * For the small handful of students that make it to the next phase and
>   figure out a project idea, they then need to find a mentor. Usually
>   the admin will help out by taking a look at who proposed the project
>   idea, and/or looking through commit messages and mailing list history
>   to try to find someone who would be a good fit and willing to mentor
>   the student. Sometimes this happens quickly, and sometimes it requires
>   poking a lot of people - and occasionally, there might not always be a
>   mentor to be found.
> * If we have a student, project, and mentor then the next step is having
>   the student write up a proposal. Many students start out with
>   over-simplified proposals, so a lot of this work is just gently
>   nudging students and getting them to refine their work items into a
>   week-by-week synopsis. There's usually a good bit of back and forth
>   with the student's proposal, and occasionally the mentor may be
>   involved with this step.
> * The admin then works with the student to come up with a timeline for
>   their work, taking into account any vacation time the student may
>   have, along with coordinating the frequency/type of meetings that
>   will happen between the student and the mentor. If the mentor is
>   unable to attend all of these meetings, it's usually up to the admin
>   to check in with the student to see how they are progressing and
>   potentially provide them tips if they get stuck.
> 
> As for being a mentor, it's pretty much as simple as it sounds: you work
> with students who have projects to help familiarize them with the
> project at hand, help them out wherever needed, check in on their
> progress, and guide them along the way towards reaching their project
> goal along with grading their work.
> 
> Please help spread the word on this, and contact anyone you know who
> might be involved with this! We'll be happy to provide more information
> on how you can get started. Remember, folks like myself wouldn't be in
> this community without projects like GSoC :).
> 

-- 
Cheers,
 Lyude Paul (she/her)
 Software Engineer at Red Hat


  reply	other threads:[~2021-08-05 20:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 20:32 Lyude Paul
2021-07-14 20:32 ` Lyude Paul
2021-07-14 20:32 ` Lyude Paul
2021-08-05 20:22 ` Lyude Paul [this message]
2021-08-05 20:22   ` Lyude Paul

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=fbe03a5f99edfe119ffcdc47de5b7baf8e84549e.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=board@x.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=members@x.org \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=wayland-devel@lists.freedesktop.org \
    --cc=xorg-devel@lists.x.org \
    --subject='Re: [Nouveau] Help needed for EVoC/GSoC/Outreachy' \
    /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

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.