2023 deadlines, other website updates

Author: terriko

contributors.html

@@ -471,6 +471,7 @@ <h2 class="content-head is-center">Where can I find information about previous y
                         <li><a href="http://python-gsoc.org/2019">Python GSoC 2019</a></li>
                         <li><a href="http://python-gsoc.org/2020">Python GSoC 2020</a></li>
                         <li><a href="http://python-gsoc.org/2021">Python GSoC 2021</a></li>
+                        <li><a href="http://python-gsoc.org/2022">Python GSoC 2022</a></li>
 
                     </ul>
                 </div>

deadlines.html

@@ -86,12 +86,12 @@
             <div class="content">
                 <div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
                     <h2 class="content-head content-head is-center">Dates and Deadlines</h2>
-                    <p>In general, Python will ask mentors to do things before the <a href="https://developers.google.com/open-source/gsoc/timeline?hl=en">Google
+                    <p>In general, Python will ask mentors to do things 48h before the <a href="https://developers.google.com/open-source/gsoc/timeline?hl=en">Google
                             deadline</a>. This allows our admins
                         time to make sure that evaluations, etc. are complete and ready for Google when their deadline
                         comes.
                         (The whole organization gets penalized if anyone's late, so we make sure that doesn't happen
-                        unfairly.)
+                        Gunfairly.)
                         Contributor deadlines are exactly as Google tells you, although getting things done earlier is never a
                         bad
                         idea!</p>
@@ -101,32 +101,27 @@ <h2>Mentor and Sub-Org admin deadlines</h2>
 					<ul>
 
 
-								<li>Nov. 28, 2022 - GSoC End date</li>
+								<li>February 5, 2023 - Deadline for sub-orgs who wish to appear on our organization application. </li>
+                <li>February 22, 2023 - Python knows if it has been accepted as a GSoC mentoring organization.  If we don't get in, all further deadlines are moot!</li>
+                <li>Feburary 25, 2023 - Deadline for sub-orgs who applied separately but did not get accepted who want to join Python (assuming we get in)</li>
+                <li>March 20, 2023 - Contributor application period begins</li>
+                <li>April 25, 2023 - Proposal rankings due to Python</li>
+                <li>May 4, 2023 - Accepted Contributor projects announced</li>
+                <li>July 12, 2023 - Midterm evaluations due to Python (standard schedule)</li>
+                <li>September 2, 2023 - Final evaluations due to Python (standard schedule)</li>
+                <li>September 25, 2023 - Initial GSoC 2023 results announced</li>
+                <li>November 11, 2023 - Final evaluations due to Python (extended deadline)
+
 
 
 					</ul>
 
                     <h2>Blogging schedule (Contributor Deadlines)</h2>
-                    <p>Every week, contributors are asked to post something about their project on their <a href="https://blogs.python-gsoc.org/en/">blogs</a>.  This helps the python community learn about the work contributors are doing and also helps the org admins make sure that contributors still on track to pass and don't need help.  There are two types of things that contributors post: blog posts, which are longer descriptions of the work they're doing, and weekly check ins, which answer a few short questions as a sort of status report.  These are due every Monday during the GSoC period, and the schedule is listed below as a list and as a calendar at the bottom of the page that you can export and add to your own calendar.</p>
+                    <p>Every week, contributors are asked to post something about their project on their <a href="https://blogs.python-gsoc.org/en/">blogs</a>.  This helps the python community learn about the work contributors are doing and also helps the org admins make sure that contributors still on track to pass and don't need help.  We expect at least a weekly check-in, but longer posts are welcome if you have an interesting problem or result to discuss.</p>
+
+                    <p>Blog posts are due every Monday during the GSoC period, and the schedule is listed below as a list and as a calendar at the bottom of the page that you can export and add to your own calendar.</p>
                     <ul>
-						
-							<li>July 4, 2022 - Weekly Blog Post Due 3</li>
-						
-							<li>July 11, 2022 - Weekly Blog Post Due 3</li>
-						
-							<li>July 18, 2022 - Weekly Blog Post Due 3</li>
-						
-							<li>July 25, 2022 - Weekly Blog Post Due 4</li>
-						
-							<li>Aug. 1, 2022 - Weekly Blog Post Due 5</li>
-						
-							<li>Aug. 8, 2022 - Weekly Blog Post Due 8</li>
-						
-							<li>Aug. 15, 2022 - Weekly Blog Post Due 8</li>
-						
-							<li>Aug. 22, 2022 - Weekly Blog Post Due 8</li>
-						
-							<li>Aug. 29, 2022 - Weekly Blog Post Due 9</li>
+					            <li>We're still working out the 2023 blogging schedule, check back later for dates!</li>	
 
                     </ul>
 

index.html

@@ -174,7 +174,7 @@ <h3 class="content-subhead">
                             Try to fix a bug.
                         </h3>
                         <p>
-                            Many projects have these tagged as "easy" "bite-size" or
+                            Many projects have these tagged as "good first issue" "easy" "bite-size" or
                             "beginner-friendly" -- do a search to see what comes up. Competition for the easiest
                             ones can be fierce, so don't be afraid to try something harder if you think
                             you might know what to do.
@@ -295,6 +295,7 @@ <h3 class="content-subhead content-head-ribbon">
                                 feedback. If your mentors tell you that a project idea won't work for them, you're
                                 probably not going to get accepted unless you change it.
                             </p>
+                            <p>More tips are available in our <a href="contributors.html">contributor's guide and FAQ</a>.
                         </div>
                         <div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
                             <h3 class="content-subhead content-head-ribbon">
@@ -327,6 +328,7 @@ <h3 class="content-subhead content-head-ribbon">
                                     to know in advance.
                                 </li>
                             </ol>
+                            <p>We also provide an <a href="https://github.com/python-gsoc/python-gsoc.github.io/blob/master/ApplicationTemplate.md">application template</a> to help you get started.
                         </div>
                     </div>
                 </div>
@@ -444,7 +446,7 @@ <h3 class="content-subhead content-head-ribbon">
                             <i class="fa fa-crown"></i>
                             Org admins
                         </h3>
-                        <p>The 2022 Python Software Foundation (PSF) org admin team:</p>
+                        <p>The 2023 Python Software Foundation (PSF) org admin team:</p>
                         <ul>
                             <li>Terri Oda (terri on IRC) - focus areas: figurehead, making final decisions,
                                 website/documentation
@@ -475,7 +477,7 @@ <h3 class="content-subhead content-head-ribbon">
                     </div>
                 </div>
             </div>
-     
+ 
             <!-- Other -->
             <div class="content">
                 <h2 class="content-head is-center">Other Stuff</h2>

mentors.html

@@ -375,7 +375,7 @@ <h4 style="color: white;">1. Project name</h4>
 
                                                     <li><strong>Project Length</strong>:  Medium size projects should take about 
                                                         175 hours to complete while large projects should take about 350 hours to 
-                                                        complete, you should put if the project idea would me a medium or a large 
+                                                        complete, you should put if the project idea would be a medium or a large 
                                                         project.
 
                                                 </ul>
@@ -386,6 +386,15 @@ <h4 style="color: white;">2. Project name</h4>
                                                     other
                                                     order, ideas
                                                     should be ordered approximately from easiest to hardest.
+																								<p>If you're open to other
+project ideas from contributors, say so and make sure there's a clear path for
+contributors to discuss ideas with mentors before submitting an application.
+Otherwise, we've found that you'll get a lot of project ideas that aren't
+suitable for GSoC: too small, too large, bad fit for the project, no mentors
+interested in taking them on, etc.  You may have an open discussion thread in
+your bug tracker/forums, a chat channel or mailing list, or contact info for a
+mentor who's open to discussing new ideas in private.</p>
+
 
                 </div>
             </div>