9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Google Summer of Code 2015
Date: Thu, 19 Feb 2015 19:13:35 -0500	[thread overview]
Message-ID: <0314019C-E3DE-443A-AD2E-97B2FEC6725C@9srv.net> (raw)

(Resending (with tweaks) to get around moderation.)

Things are underway for this summer. The org application period is open, closing tomorrow, and ours is in, with a few tweaks pending. A few things to note, the first one could use lots of help:

• As always, the most important part of the application is the ideas page. This year's is at:

	http://www.plan9.bell-labs.com/wiki/plan9/gsoc-2015-ideas/index.html

I've just started updating it, and there's plenty to do. If you have an idea you'd be possibly willing to mentor or backup-mentor, *please* add it here. Provide enough detail that an interested student could get a decent idea of the scope of the project and what's involved. The more relevant information you can provide, the better. If the info for that project gets larger than a paragraph, it probably makes sense to create a wiki page dedicated to the idea; see the idea "Replace language for wikifs" for a good example of that. If the wiki is a challenge, email me what the entry should be and I'll take care of it.

In the GSoC feedback sessions every year, this page is always the main thing used to separate various otherwise-promising orgs out. Take a look.

• If you travel in circles with students, start telling them about the program and why they should want to work with us. You might point them at our Student Expectations, at
	http://www.plan9.bell-labs.com/wiki/plan9/GSoC_Student_Expectations/index.html
I'm reviewing those, but I don't expect significant changes.

• If you're an established community member, consider whether you'd be interested in mentoring. Take a look at our Mentor's Expectations at
	http://www.plan9.bell-labs.com/wiki/plan9/GSoC_Mentor_Expectations/index.html
and feel free to ask me or anyone else who's participated in the past questions - I'm sure everyone would be willing to talk.

• Prior-year mentors, it would be particularly helpful if you could take a look at those two previous pages and let me know (via the plan9-gsoc group preferably, or off-list) if you think anything needs changing. I think these expectations (which are more or less the same as the past 2-3 years, with small refinements) have served us pretty well, but would obviously be interested in other opinions.

• Also, if you're not on them and would like to contribute actively, we have two relevant Google Groups worth joining: plan9-gsoc and plan9-gsoc-mentors. The mentor's list is for mentors, backup mentors, and similar folks helping out; the other list is for anyone interested in helping out or following along on the GSoC-specific discussions more closely.

Let me know if you have any other questions. If you have real-time questions, I'm in #plan9 and #plan9-gsoc most of the time.
Anthony


-- 
You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code Mentors list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plan9-gsoc-mentors+unsubscribe@googlegroups.com.
To post to this group, send email to plan9-gsoc-mentors@googlegroups.com.
Visit this group at http://groups.google.com/group/plan9-gsoc-mentors.
For more options, visit https://groups.google.com/d/optout.


                 reply	other threads:[~2015-02-20  0:13 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-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=0314019C-E3DE-443A-AD2E-97B2FEC6725C@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).