Rewriting Getting Started, other info

terriko · terriko · commit 50e09b483722 · 2017-09-14T16:32:49.000-07:00
diff --git a/index.html b/index.html
@@ -17,6 +17,7 @@
       <li><a href="#ideas">Project Ideas</a></li>
       <li><a href="#mentors">Mentors</a></li>
       <li><a href="#students">Students</a></li>
+      <li><a href="#contact">Contact</a></li>
       <li><a href="#gettingstarted">Getting Started</a></li>
       <li><a href="#about">About</a></li>
     </ul>
@@ -40,8 +41,7 @@ <h1>Google Summer of Code 2018 @ the Python Software Foundation</h1>
 organization" to a variety of Python-related projects, as well as sponsoring
 projects related to the development of the Python language.
 
-<div class="warning"><strong>
-<p>It is our
+<div class="warning"><strong>It is our
 intention to apply to participate in GSoC for the 2018 season.</strong>  However, we won't
 know which orgs will be participating and what projects they want until February 2018, and
 we won't know if we're accepted until Febuary 2018ish either.  While you're waiting, check
@@ -59,10 +59,10 @@ <h1>Google Summer of Code 2018 @ the Python Software Foundation</h1>
 <ul>
 	<li>James Lopeman (meflin on IRC)</li>
 	<li>John Hawley (warthog9 on IRC)</li>
-   <li>Matt (Botanic on IRC)</li>
+   <li>Matthew Lagoe (Botanic on IRC)</li>
 </ul>
 
-<p>We also have a great group of advisors and "org admins emeritus" who may be available
+<p>We also have a great group of advisors and "org admins emeritus" who may be able
 to help you:
 
 <ul>
@@ -71,58 +71,6 @@ <h1>Google Summer of Code 2018 @ the Python Software Foundation</h1>
 	<li>Stephen Turnbull (yaseppochi on IRC)</li>
 </ul>
 
-<a name="contact"></a>
-<h2>Getting in Touch</h2>
-
-<ul>
-<li>Please note that Python has a <a
-href="https://www.python.org/psf/codeofconduct/">Community Code of Conduct</a> and mentors and
-students working with the PSF are asked to abide by it as members of the
-Python community.</li>
-<li>Sign up to the <a
-href="https://mail.python.org/mailman/listinfo/gsoc-general">gsoc-general(at)python.org</a>
-mailing list to get updates, reminders, and to discuss questions.</li>
-
-<li><a
-href="http://webchat.freenode.net/?channels=python-gsoc">#python-gsoc on
-irc.freenode.net</a> is our IRC channel.  IRC is an older realtime chat protocol very
-popular among open source projects, and it's worth learning to use it and getting a
-dedicated client if
-you're going to be involved in open source long term.  Please remember to
-stick around a while for an answer, as many open source people use IRC for
-work and aren't always available to respond immediately.</li>
-<ul>
-<li>There are some great resources at http://irchelp.org/ if you need help finding a
-client or learning how to use IRC. </li>
-<li>We are working on IRC-Zulip integration so that people without IRC clients will have a
-nice web interface, but this isn't working yet.</li>
-</ul>
-
-<li>Found a typo?  Want to improve this page? <a
-href="https://github.com/python-gsoc/python-gsoc.github.io">The source code
-is on GitHub and we welcome pull requests!</a></li>
-
-</ul>
-
-<p>Please try to read all the information on this page before
-asking a question.  We have tried to answer a lot of common questions in
-advance!</p>
-
-<p><strong>Don't forget to be patient</strong>: Our mentors generally have day-jobs and
-are not always paying attention to IRC (especially during GSoC off-season: expect more
-active mentors after Google's announcement of organizations). Please ask questions
-directly on channel (you don't need to introduce
-yourself or say hi first) and please be patient while waiting for an answer.
-You could wind up waiting an hour or much longer for "realtime" answers if all the
-mentors are in meetings at work or otherwise occupied. If you can't stay that
-long, stay as long as you can and then send email to the mailing list instead
-so mentors have some way to reach you.  We try to answer emails within 48h.</p>
-
-<p><strong>For mentors</strong>: All the gsoc admins can be reached at
-gsoc-admins(at)python(dot)org if you have questions about participating.
-(Students should email gsoc-general(at)python.org with all of their
-questions, unless they are of a sensitive personal nature.)
-
 <a name="gettingstarted"></a>
 <h2>Getting Started</h2>
 
@@ -131,34 +79,37 @@ <h2>Getting Started</h2>
 
 <ol type="1"><li><strong>Choose an
 organization to work with.</strong>
-<br />Python is a huge community, but almost all of our projects are organized into
-"sub-orgs" that use python.  You'll need to select one of those to work with for GSoC.
-<br />See &quot;<a class="https"
+<br />Open source is a huge community, with hundreds of thousands of projects written in
+Python alone.  If you want any sort of mentoring or help, it's best to choose a specific
+piece of software as a starting point.
+See &quot;<a class="https"
 href="https://wiki.python.org/moin/SummerOfCode/FrequentlyAskedQuestions#How_do_I_choose_a_project_or_a_sub-org.3F">How
 do I choose a project or a sub-org?</a>&quot;  if you need help choosing.
-Don't forget, you can try working with more than one organization to see
-which one suits you best!
 
 <ul>
-<li>Experience with *any* open source group will help you prepare for GSoC.
-If you decide to write an application for GSoC you'll need to choose from our
-list of registered sub-orgs, but you can experiment before you get to the
-application stage.</li>
+<li>You don't have to stick with the first project you choose!  It's very common for open
+source folk to contribute casually to many projects, have a smaller number they spend
+more time on, and move from project to project as their interests change.  Don't waste
+time on decision paralysis!
+
+<li>Experience with *any* open source group will help you prepare for GSoC or be a better
+general open source contributor.</li>
 
-<li>Asking mentors to choose your project for you
+<li>Asking mentors or community members to choose your project for you
 typically leaves a bad first impression, especially since mentors probably
-don't know you well enough to help guide you to a good choice.  At least try
+don't know you well enough to help guide you to a good choice and are very tired of being
+asked by hundreds of students every year.  At least try
 to narrow down your choices a bit on your own, or let them know enough about
 what you like and don't like so they can help.</li>
 
-<li>Look through <a
-href="http://python-gsoc.org/2017">our list of
-GSoC 2017 sub-orgs</a> to get a sense of who might participate in 2018.  <a
-href="#ideas">Our ideas list</a> will be updated as soon as orgs tell us
-they're interested in participating this year. If your favourite org isn't on
-the list and you'd like them to be, contact them directly!  Assuming Google
-accepts us, we'll accept sub-orgs until <a href="#schedule">the dates listed in
-our schedule</a>.</li>
+<li>GSoC specific: If you want to be accepted for a GSoC internship, you will need to
+choose from <a href="#ideas">our list of registered sub orgs</a> (If that's not ready when
+you look, you can check out <a href="http://python-gsoc.org/2017/#ideas">the list from
+2017 to see who might be participating again</a>, but check the final list before
+submitting an application).  Applications that don't relate to an
+accepted sub-org will be rejected because we don't have mentors available.  If your
+favourite group isn't on the list, please contact them to see if they would like to
+participate.
 
 </ul>
 </li>
@@ -167,16 +118,19 @@ <h2>Getting Started</h2>
 Join the mailing list, IRC channel, or any other communication channels the
 developers use.  Listen, get to know the people involved, and ask questions.
 Not sure where to find that contact info?  Each sub-org for Python has their
-information listed <a href="#ideas">in the ideas list</a>.
+information listed <a href="#ideas">in the ideas list</a> once they're signed up, but
+a quick websearch will usually turn up a project's home page and preferred methods of
+contact too.
 
 <ul>
 <li>If you want to make the best
 first impression, DO NOT start emails with &quot;Dear Sir.&quot;  Python has
-many mentors who are female and/or prefer other forms of address.  Try
-&quot;Dear developers&quot; if  you're sending a general email, or use
-whatever name they use on their email if you're addressing a specific person.
-Culturally speaking, first names or chosen nicknames are fine for most open
-source projects. </li>
+many mentors who prefer other forms of address (for example, many mentors are female!) and
+"Sir" is often seen as an impolite way to exclude many valued members of our community.
+You can skip the salutation entirely, try &quot;Dear developers&quot; if  you're sending a
+general email, or use whatever name they use on their email if you're addressing a
+specific person.  Culturally speaking, first names or chosen nicknames are fine for most
+open source projects. </li>
 
 <li><strong>DO</strong> ask your question in public.  Being able
 to participate in the open is a signal to developers that you're ready to
@@ -186,7 +140,8 @@ <h2>Getting Started</h2>
 
 <li><strong>DON'T</strong> Ask to
 ask.  Just get right to the point and ask your question without asking if
-you're allowed to ask a question first.  See <a class="https"
+you're allowed to ask a question first.  You don't need to introduce yourself
+in most communities.  See <a class="https"
 href="https://wiki.python.org/moin/SummerOfCode/FrequentlyAskedQuestions#What_does_.22don.27t_ask_to_ask.22_mean.3F">What
 does &quot;don't ask to ask?&quot; mean?</a> for more explanation. </li></ul></li>
 
@@ -206,15 +161,6 @@ <h2>Getting Started</h2>
 project.  A few fixed bugs with code accepted upstream will make your
 application look great! </li>
 
-<li>Some projects
-have beginner-friendly &quot;bite-sized&quot; bugs listed in the OpenHatch
-search engine, found here: <a class="http"
-href="http://openhatch.org/search/">http://openhatch.org/search/</a> but many
-do not, so try searching for tags like "easy" or "beginner" in your project's
-bug tree.  Remember, competition for easy bugs is very high during GSoC so
-it can be hard to find one that's flagged.  If you don't see anything, read
-through the bugs and choose a few that sound like something you can fix.</li>
-
 <li>Having trouble figuring out which
 bugs are beginner-friendly?  Try searching for terms like &quot;easy&quot; in
 the bug tracker.  Or just choose a bug that sounds easy to you and try to get
@@ -225,6 +171,11 @@ <h2>Getting Started</h2>
 people can't help, sometimes they will be able to suggest another bug which
 would be more beginner-suitable. </li>
 
+<li>Remember, competition for easy bugs is very high during GSoC so
+it can be hard to find one that's flagged.  If you don't see anything, read
+through the bugs and choose a few that sound like something you can fix. What's easy for
+you may not be easy for everyone, so take advantage of that.</li>
+
 <li>Other &quot;easy&quot; bug ideas: look for typos
 and fix them.  Set up new tests -- even if your project decides they don't
 need the first one you write, the practice of writing test cases will be
@@ -257,6 +208,60 @@ <h2>Getting Started</h2>
 candidates, and being helpful makes your community a better place! </li>
 </ol>
 
+<a name="contact"></a>
+<h2>Getting in Touch</h2>
+
+<ul>
+<li>Please note that Python has a <a
+href="https://www.python.org/psf/codeofconduct/">Community Code of Conduct</a> and mentors and
+students working with the PSF are asked to abide by it as members of the
+Python community.</li>
+<li>Sign up to the <a
+href="https://mail.python.org/mailman/listinfo/gsoc-general">gsoc-general(at)python.org</a>
+mailing list to get updates, reminders, and to discuss questions.</li>
+
+<li><a
+href="http://webchat.freenode.net/?channels=python-gsoc">#python-gsoc on
+irc.freenode.net</a> is our IRC channel.  IRC is an older realtime chat protocol very
+popular among open source projects, and it's worth learning to use it and getting a
+dedicated client if
+you're going to be involved in open source long term.  Please remember to
+stick around a while for an answer, as many open source people use IRC for
+work and aren't always available to respond immediately.</li>
+<ul>
+<li>There are some great resources at http://irchelp.org/ if you need help finding a
+client or learning how to use IRC. </li>
+<li>We are working on IRC-Zulip integration so that people without IRC clients will have a
+nice web interface, but this isn't working yet.</li>
+</ul>
+
+<li>Found a typo?  Want to improve this page? <a
+href="https://github.com/python-gsoc/python-gsoc.github.io">The source code
+is on GitHub and we welcome pull requests!</a></li>
+<li>To talk with people from a specific sub-org, <a href="#ideas">check their ideas
+page listing</a>.
+</ul>
+
+<p>Please try to read all the information on this page before
+asking a question.  We have tried to answer a lot of common questions in
+advance!</p>
+
+<p><strong>Don't forget to be patient</strong>: Our mentors generally have day-jobs and
+are not always paying attention to IRC (especially during GSoC off-season: expect more
+active mentors after Google's announcement of organizations). Please ask questions
+directly on channel (you don't need to introduce
+yourself or say hi first) and please be patient while waiting for an answer.
+You could wind up waiting an hour or much longer for "realtime" answers if all the
+mentors are in meetings at work or otherwise occupied. If you can't stay that
+long, stay as long as you can and then send email to the mailing list instead
+so mentors have some way to reach you.  We try to answer emails within 48h.</p>
+
+<p><strong>For mentors</strong>: All the gsoc admins can be reached at
+gsoc-admins(at)python(dot)org if you have questions about participating.
+(Students should email gsoc-general(at)python.org with all of their
+questions, unless they are of a sensitive personal nature.)
+
+
 
 <a name="students"></a>
 <h2>Students</h2>
@@ -266,7 +271,7 @@ <h2>Students</h2>
 community, get experience working with a larger and often distributed team,
 learn, and, of course, get paid.
 
-<p>Students are expected to work at least 40 hours a week on their GSoC project.
+<p>Students are expected to work around 40 hours a week on their GSoC project.
 This is essentially a full-time job. Ideally, you should not attempt to do
 another internship, job, or full-time schooling while you're doing GSoC.
 
@@ -341,7 +346,8 @@ <h3>How do I apply?</h3>
 
 <li>Set up a blog where you will keep track of your GSoC progress</li>
 
-<li>Write your application (with help from your mentors!)</li>
+<li>Write your application (with help from your mentors!)  Make sure to include the
+sub-org name in the title so your mentors can find it in the system.</li>
 
 <li>	 Submit your application to Google before the deadline.  We actually
 recommend you submit a few days early in case you have internet problems or
@@ -354,16 +360,18 @@ <h3>How do I apply?</h3>
 important part of the application process. Talk to the mentors and other
 developers, <em>listen</em> when they give you advice,
 and demonstrate that you've understood by incorporating their feedback into
-what you're proposing. </div>
+what you're proposing. We reject a lot of students who haven't listened to mentor
+feedback.</div>
 
 <a name="mentors"></a>
 <h2>Mentors</h2>
 <p>Interested in volunteering with the Python Software Foundation?
 
 <p><strong>The biggest job is mentoring students</strong>: Mentoring a
 student as a primary mentor can be a pretty big time commitment (we recommend
-around 0-10 hours a week for the 3 months of the program) but it's a very
-rewarding chance to basically give a student an open source apprenticeship.
+around 0-10 hours a week for the 3 months of the program, with more time at the beginning
+and less once the student learns to work independently) but it's a very
+rewarding chance to give a student an open source apprenticeship.
 We mentor in teams, so if all you can handle is a few code reviews or taking
 over for a week while someone's on vacation, we'd still love your help.
 
@@ -385,6 +393,7 @@ <h2>Mentors</h2>
 <p><strong>If you'd like to volunteer, get in touch with a sub-org admin or
 email the Python org admins at gsoc-admins(at)python(dot)org </strong></p>
 
+<a name="sub-orgs"></a>
 <h3>Sub-orgs</h3>
 <p>To participate under the Python umbrella, a sub-org must do the following:
 
@@ -408,6 +417,12 @@ <h3>Sub-orgs</h3>
 href="https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate">Here's a template.</a> Getting a really great page
 sometimes takes a few rounds of revisions; Meflin will work with you to make
 sure your page is ready!
+
+<li>Be able to handle <a href="#schedule">meeting deadlines</a> and following both Google
+and Python's rules.  We try to send important reminders for big deadlines, but we only
+have limited volunteer time for nagging and cajoling.  Groups that cause repeated problems
+may be asked to take time off to limit volunteer burnout.
+
 </ol>
 
 <p>We can't promise to take everyone who meets those criteria, but we do try to
@@ -433,7 +448,8 @@ <h2>Project Ideas</h2>
 your favourite Python-based project will be participating, ask them and
 encourage them to sign up!</p>
 
-<p>If you represent a python-based sub-org and want to be added to the list, contact
+<p>If you represent a python-based sub-org and want to be added to the list, <a
+href="#sub-orgs">read up on what it takes to participate</a>, contact
 gsoc-admins(at)python.org to get an ideas page review, and when it's ready
 you can <a href="https://github.com/python-gsoc/python-gsoc.github.io">make a
 pull request or file an issue on GitHub</a>.
@@ -459,6 +475,10 @@ <h2>Schedule</h2>
 href="https://calendar.google.com/calendar/ical/uhambjin8qdb9af4vt03c4djg4%40group.calendar.google.com/public/basic.ics">Python
 GSoC calendar in ical format</a>
 
+<iframe
+src="https://calendar.google.com/calendar/embed?height=400&amp;wkst=1&amp;bgcolor=%23FFFFFF&amp;src=uhambjin8qdb9af4vt03c4djg4%40group.calendar.google.com&amp;color=%23AB8B00&amp;ctz=America%2FLos_Angeles"
+style="border-width:0" width="800" height="400" frameborder="0" scrolling="no"></iframe>
+
 </div>
 </body>
 </html>
