You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributors.html
+2-2
Original file line number
Diff line number
Diff line change
@@ -278,7 +278,7 @@ <h2 class="content-head content-head-ribbon is-center">What do I need to know to
278
278
<li><strong>You should be comfortable communicating your ideas to others in
279
279
public.</strong> Most projects
280
280
have public mailing lists and would prefer if you use them, and Python GSoC contributors are also
281
-
required to blog about their work over the summer. You can use a pseudonym (nickname)
281
+
required to write about their work over the summer. You can use a pseudonym (nickname)
282
282
if
283
283
that works best for you. Google will need to know who you are to pay you, but we just
284
284
need something to call you.<br/><br/>
@@ -291,7 +291,7 @@ <h2 class="content-head content-head-ribbon is-center">What do I need to know to
291
291
</ul>
292
292
<br/>
293
293
<br/>
294
-
These answers can be very short (Under 100 words) or longer depending on what you want to say. The idea is that these blog posts serve as your weekly check-ins with the org admins and help show the wider Python community what kind of work our GSoC contributors are doing.
294
+
These answers can be very short (Under 100 words) or longer depending on what you want to say. The idea is that these posts serve as your weekly check-ins with the org admins and help show the wider Python community what kind of work our GSoC contributors are doing.
295
295
</li>
296
296
<li><strong>You probably want some experience with version control.</strong> We have a lot
0 commit comments