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: content/internships/intern-guide/contents.lr
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Once the internship starts, here's what we expect of you:
27
27
* Work 30-40 hours per week (or agree on a different plan with your mentor ahead of time).
28
28
* Push code to GitHub frequently. Commit early and often.
29
29
* Be available on Slack whenever you are working and post at least once a (work)day to talk about what you're working on that day.
30
-
* Write a short update on your work **every two weeks** and post it to the CC technical blog ([instructions are here(/community/write-a-blog-post)).
30
+
* Write a short update on your work **every two weeks** and post it to the CC technical blog ([instructions are here](/community/write-a-blog-post)). To get a sense of how these posts are written and how the projects evolved, you can read entries done by previous [Outreachy](https://opensource.creativecommons.org/blog/categories/outreachy/) or [Google Summer of Code](https://opensource.creativecommons.org/blog/categories/gsoc/) interns.
31
31
* Attend your weekly check-in with your mentor and any other meetings.
32
32
* Be proactive about asking for help, especially when you're stuck.
33
33
* Ensure that you're on track to delivering your project at the end of the work period. If you're not on track, talk with your mentor to come up with a new plan for the project well before the deadline.
0 commit comments