public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Google Summer of Code (GSoC) 2022!
Date: Wed, 9 Mar 2022 01:25:02 +0000	[thread overview]
Message-ID: <MW4PR11MB582171FFEEE9DEE61C665319CD0A9@MW4PR11MB5821.namprd11.prod.outlook.com> (raw)

Hi Everyone,

I am pleased to announce that TianoCore has been accepted to participate in GSoC 2022! GSoC applications will start rolling in on April 4th, so now we need some volunteers to be mentors. Thank you to all who have volunteered! Mentors will need to be able to commit to the following:

* Generally, we prefer mentors who have been long term contributors to the TianoCore project
* During the GSoC contributor application period (April 4 - April 19), mentors need to be available to help review GSoC applications.
* On average, we expect each GSoC contributor will need roughly 5 hours of help each week during the 12 week development period (June 13 - September 4). I know that most people here have day jobs (including myself) so I'd like to assign 2 mentors per student whenever possible, this will reduce the time investment to ~2.5 hours per week.
* The GSoC contributor and their mentors should meet for 30min at absolute minimum on a weekly basis. The mentors should be able to make themselves available for more time if the contributor requires additional mentoring. In general, mentors should help their contributors succeed.
* Help the GSoC contributors get involved the rest of the TianoCore community. A lot of times, contributors have no prior open source experience and can at times be shy. One of the goals for GSoC is to give contributors new experiences and exposure to the open source community. Mentors should help contributors present their project at one of the TianoCore Design Meetings and help them solicit feedback from other community members on the mailing list.
* Mentors will need to write up 2 evaluations (July and August) for the GSoC contributors they are mentoring.

If you are interested in participating as a GSoC contributor (aka student) this year, feel free to introduce yourself on the mailing list and discuss potential project proposals.

If you are interested in mentoring, please send me an off-list/private email.

Thanks!
Nate

                 reply	other threads:[~2022-03-09  1:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list 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=MW4PR11MB582171FFEEE9DEE61C665319CD0A9@MW4PR11MB5821.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox