Ported more information from old wiki page

Author: terriko

index.html

@@ -10,7 +10,8 @@
 <nav class="fixed-nav-bar">
   <div id="menu" class="menu">
     <ul class="menu">
-      <li style="float:left"><a href="index.html">Python in GSoC</a>
+      <li style="float:left"><a href="#"><img src="python-logo-45px.png"
+alt="Python logo" height="45px" /></a>
       <li><a href="#schedule">Deadlines</a></li>
       <li><a href="#ideas">Project Ideas</a></li>
       <li><a href="#mentors">Mentors</a></li>
@@ -24,18 +25,20 @@
 <div class="content">
 <a name="about" />
 <h1>Google Summer of Code 2017 @ the Python Software Foundation</h1>
+<img src="python-powered-h-140x182.png" alt="Python powered" height="182" width="140" />
 
-<p><a href="http://python.org">Python</a> is a popular high-level programming language. It is a general-purpose
-language used by scientists, developers, and many others who want to get
-things done quickly and effectively.
+<p><a href="http://python.org">Python</a> is a popular high-level programming
+language. It is a general-purpose language used by scientists, developers,
+and many others who want to work more quickly and integrate systems more
+effectively.
 
-<p><a href="http://code.google.com/soc/">Google Summer of Code</a> is a global
-program that offers post-secondary students an opportunity to be paid for
-contributing to an open source project over a three month period. Since 2005,
-the Python Software Foundation has served as an "umbrella organization" to a
-variety of Python-related projects, as well as sponsoring projects related to
-the development of the Python language.  It is our intention to apply again
-for the 2017 season!
+<p><a href="http://code.google.com/soc/">Google Summer of Code</a> (GSoC) is
+a global program that offers post-secondary students an opportunity to be
+paid for contributing to an open source project over a three month period.
+Since 2005, the Python Software Foundation has served as an "umbrella
+organization" to a variety of Python-related projects, as well as sponsoring
+projects related to the development of the Python language.  It is our
+intention to apply again for the 2017 season!
 
 <p>The 2017 PSF GSoC coordinator is TerriOda. (terri on Freenode IRC, terrioda
 at gmail.com, but please email gsoc-admins(at)python(dot)org if you wish to
@@ -46,6 +49,44 @@ <h1>Google Summer of Code 2017 @ the Python Software Foundation</h1>
 (florianf on IRC), Kushal Das (kushal on IRC) and Stephen Turnbull
 (yaseppochi on IRC)
 
+<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>Stop by #python-gsoc on irc.freenode.net to chat and ask questions in
+realtime.  </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>Do plan to stay for a while if you want answers on IRC</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 Feb
+29th). 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 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.</p>
+
+<p>There are some great resources at http://irchelp.org/ if you need help
+finding a client or learning how to use IRC.
+
+<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" />
 <h2>Getting Started</h2>
 
@@ -175,7 +216,96 @@ <h2>Getting Started</h2>
 
 <a name="students" />
 <h2>Students</h2>
-to be filled out
+<p>GSoC is basically an open source apprenticeship: students will be paid by
+Google to work under the guidance of mentors from an open source community.
+It's a really great opportunity to build new skills, make connections in your
+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.
+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.
+
+<p>To apply, you need to <a href="#ideas">take a look at the mentoring
+organizations and the ideas that they are willing to sponsor</a>. Typically,
+you'll choose one of their ideas and work with a mentor to create a project
+proposal that's good for both you and your chosen open source community.
+Sometimes, projects are open to new ideas from students, but if you propose
+something new make especially sure that you work with a mentor to make sure
+it's a good fit for your community. Unsolicited, undiscussed ideas are less
+likely to get accepted.
+
+<p>Note that Python is an "umbrella organization" which means that our team is
+actually a group of python projects that work together to do Google Summer of
+Code. If you're going to apply with us, you'll need to choose from one of
+those teams, because that defines which mentors will be helping you with your
+applications.  <strong>Applications without any sub-org and mentor to
+evaluate them will be rejected.</strong>  You can work with more than one
+sub-org while you're figuring out what you want to do, but you can only
+accept one job offer.
+
+Here's some resources so you can read up more on how to be an awesome
+student:
+<ul>
+<li><a
+href="http://write.flossmanuals.net/gsocstudentguide/what-is-google-summer-of-code/">The
+GSoC student Guide</a> -- This is a guide written by mentors and former
+students.  It covers many questions that most students ask us.  Please read
+it before asking any questions on the mailing list or IRC if you can!  New
+students in particular might want to read the section <a
+href="http://write.flossmanuals.net/gsocstudentguide/am-i-good-enough/">Am I
+Good Enough?</a></li>
+
+<li><a
+href="https://developers.google.com/open-source/gsoc/resources/">Google's
+list of resources</a> -- Note especially the <a
+href="https://developers.google.com/open-source/gsoc/faq">Frequently Asked
+Questions</a> (FAQ) which does in fact answer 99% of the questions we get on
+the main GSoC IRC channel.</li>
+
+<li>Python's <a
+href="https://wiki.python.org/moin/SummerOfCode/Expectations">SummerOfCode/Expectations</a> also talks about what Python in particular
+is looking for in its students.</li>
+
+<li>Python's <a
+href="https://wiki.python.org/moin/SummerOfCode/FrequentlyAskedQuestions">SummerOfCode/FrequentlyAskedQuestions</a> answers the questions that we
+most often get about Python's projects. You might want to see <a
+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> or <a
+href="https://wiki.python.org/moin/SummerOfCode/FrequentlyAskedQuestions#How_many_slots_does_python_get.3F__How_many_does_project_.24x_get.3F">How many slots does Python get?</a>
+</ul>
+
+<h3>How do I apply?</h3>
+
+Short application checklist:
+<ol>
+<li>Read the links and instructions given on this page -- All of it! we've tried to give you all the
+information you need to be an awesome student applicant.
+
+<li>Choose a sub-org (<a href="#ideas">check the list here</a>)
+
+<li>Talk to your prospective mentors about what they expect of student
+applicants and get help from them to refine your project ideas. Listening to
+your mentors' recommendations is very important at this stage!</li>
+
+<li>Prepare a patch for that sub-org</li>
+
+<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>	 Submit your application to Google before the deadline.  We actually
+recommend you submit a few days early in case you have internet problems or
+the system is down. Google does not extend this deadline, so it's best to be
+prepared early! You can edit your application up until the system
+closes.</li>
+</ol>
+
+<div class="warning"><strong>Communication</strong> is probably the most
+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>
 
 <a name="mentors" />
 <h2>Mentors</h2>

style.css

@@ -1,62 +1,79 @@
 .fixed-nav-bar {
-  position: fixed;
-  top: 0;
-  left: 0;
-  z-index: 8888;
-  width: 100%;
-  height: 50px;
-  background-color: #f0f0f0;
-  border-bottom: 4px solid #2955a3;
+	position: fixed;
+	top: 0;
+	left: 0;
+	z-index: 8888;
+	width: 100%;
+	height: 50px;
+	background-color: #d9d9d9;
+	border-bottom: 4px solid #2955a3;
 }
 .content {
-  margin-top: 60px;
+	margin-top: 60px;
+	margin-left: 2em;
 }
 
 .sitename {
-  display: inline-block;
-  margin-right: 20px;
-  margin-left: 10px;
+	display: inline-block;
+	margin-right: 20px;
+	margin-left: 10px;
 }
 a.sitename, a:visited.sitename {
-  color: #f0f0f0;
+	color: #f0f0f0;
 }
 
 .menu ul {
-  list-style-type: none;
-  margin: 0;
-  padding: 0;
-  overflow: hidden;
-  height: 50px;
+	list-style-type: none;
+	margin: 0;
+	padding: 0;
+	overflow: hidden;
+	height: 50px;
 }
 
 .menu li a {
-  display: block;
-  margin: 0;
-  padding: 8px 16px;
-  height: 50px;
-  text-decoration: none;
-  color: #2955a3;
+	display: block;
+	margin: 0;
+	padding: 8px 16px;
+	height: 50px;
+	text-decoration: none;
+	color: #2955a3;
 }
 .menu li {
-  display: inline;
-  float: right;
-  height: 50px;
-  margin: 0;
-  font-size: 1.5em;
+	display: inline;
+	float: right;
+	height: 50px;
+	margin: 0;
+	font-size: 1.5em;
 }
 
 .menu li a:hover {
-  background-color: #ffb100;
-  color: white;
-  height: 50px;
-  margin: 0;
+	background-color: #ffb100;
+	color: white;
+	height: 50px;
+	margin: 0;
 }
 
 h1 {
-	font-size: 1.2em;
+	font-size: 1.5em;
 }
-h2 {
+h1, h2, h3 {
+	padding-top: 50px;
+	color: #2955a3;
 }
-
 li {
-  padding-bottom: .5em;
+	padding-bottom: .5em;
+}
+
+div.warning {
+	border: 1pt solid #E5E5E5;
+	background-color: #F9F9FF;
+	color: black;
+
+	margin: 10pt 30pt 10pt 30pt;
+	background-repeat: no-repeat;
+	background-position: 8px 8px;
+	min-height: 45px;
+	padding: 10px 10px 10px 64px;
+
+	background-image: url("warning.png");
+}