Merge remote-tracking branch 'upstream/main' into blog-post

Author: PreciousOritsedere

Pipfile.lock

@@ -0,0 +1,5 @@
+_model: redirect
+---
+target: https://docs.google.com/document/d/1ylCkTMq1tsxGCn1baq_59I8p82gFKWj24iLXSwEFc0Q/edit?usp=sharing
+---
+_discoverable: no

content/aaron/contents.lr

@@ -5,5 +5,6 @@ name: Anna Tumadóttir
 md5_hashed_email: c6b98be141f57ce877a7ae10595b0ae0
 ---
 about:
-[Anna](https://creativecommons.org/author/annacreativecommons-org/) is Director
-of Product at Creative Commons. She's `@Anna` on the [CC Slack](/community/).
+Anna is the [Chief Operating Officer
+(COO)](https://creativecommons.org/author/annacreativecommons-org/) at Creative
+Commons. She's `@Anna` on the [CC Slack](/community/).

content/blog/authors/annatuma/contents.lr

@@ -5,10 +5,10 @@ _template: page-with-toc.html
 title: Open Source Work Programs: Applicant Guide
 ---
 description:
-CC participates in open source work programs such as GSoC and Outreachy. Both
-CC staff and community members are welcome to lead projects. Details about
-specific programs and rounds are listed in the [Overview page](/programs); this
-page serves as a general guide to applicants.
+CC participates in open source work programs such as Google Summer of Code
+(GSoC) and Outreachy. Both CC staff and community members are welcome to lead
+projects. Details about specific programs and rounds are listed in the
+[Overview page](/programs); this page serves as a general guide to applicants.
 ---
 body:
 
@@ -31,46 +31,49 @@ Here are some resources:
 [outreachyguide]: https://www.outreachy.org/docs/applicant/
 
 
-### Understand CC
+### Understand Creative Commons
 
-Your first step should be to understand Creative Commons and what we do. We're
+Your first step should be to understand Creative Commons and what we do. We are
 not simply an open source software project like many other work program
-organization. We're a nonprofit organization and we have a lot of different
+organization. We are a nonprofit organization and we have a lot of different
 programs – technical, legal, educational, public policy, organizational, and
-more. You can start reading about us at our [official
-website](https://creativecommons.org/) and you can find plenty of information
-through searching about us. You'll need to know a decent amount about us in
-order to help us effectively.
+more. You can start reading about us at our primary website
+([CreativeCommons.org][ccorg]) and you can find plenty of information through
+searching about us. You'll need to know a decent amount about us in order to
+help us effectively.
 
 If you have a question about how we work, our programs, our licenses, or
-anything like that, please don't hesitate to ask!
+anything like that, please don't hesitate to ask (join the community)!
+
+[ccorg]: https://creativecommons.org/
 
 
 ### Join the Community
 
-[Join the `#cc-dev-workprograms` channel on the CC Slack or the CC Developers
-mailing list](/community/) as early as possible to introduce yourself and get
-feedback on your ideas. All our project leads will be on Slack and respond to
-emails on the mailing list and it is better to post there rather than
-contacting them individually. Feel free to ask questions!
+[Join the `#cc-dev-workprograms` channel on the CC Slack][slack] as early as
+possible to introduce yourself and get feedback on your ideas. All our project
+leads are on Slack. Please ask your questions on the channel instead of via
+direct message. This lets other commuinity members learn and participate.
+
+[slack]: /community/#slack
 
 
 ### Pick a Project
 
-Your next step should be to pick a particular project that you're interested in
-working on. The [Overview page](/programs/) will cover the current
-work program rounds and link to related project ideas.
+Your next step should be to pick a particular project that you are interested
+in working on. The [Overview page](/programs/) will cover the current work
+program rounds and link to related project ideas.
 
-Once you pick the project you're interested in, make sure to learn about the
-project thoroughly. You're going to be spending three months working on the
-project and you'll need to understand what the work entails so that you can
+Once you pick the project you are interested in, make sure to learn about the
+project thoroughly. You are going to be spending three months working on the
+project and you will need to understand what the work entails so that you can
 plan the work out ahead of time and submit a strong application. The project
-descriptions are quite short so we expect you to do a lot of work here duron
-your own taking those descriptions and fleshing them out into a more detailed
-project plan and implementation timeline.
+descriptions are quite short so we expect you to do a lot of work here on your
+own. You will need to take the project description and expand it out into a
+more detailed project plan and implementation timeline.
 
 The project leads are here to help you. We expect you to have a lot of
-questions along the way and we're happy to answer them.
+questions along the way and we are happy to answer them.
 
 
 ### Contribute!
@@ -99,7 +102,7 @@ before you submit your final application. For more details, see the
 
 ### Why contribute?
 
-Contributions are for you to get a sense of what it's like to contribute to an
+Contributions are for you to get a sense of what it is like to contribute to an
 open source project (getting used to the GitHub workflow, interacting with
 other contributors, etc.) and for us to see a sample of your work/skills. If we
 are impressed by your contributions, we are more likely to select you as an
@@ -117,7 +120,7 @@ contribution guidelines (not all of them will have them).
 If you're applying via Outreachy, remember to record your contribution via the
 Outreachy website! You can record contributions even if you have not yet
 received feedback on them or if they have not been merged--our project leads
-are busy so we can be slow to provide feedback.
+are busy so they can not always provide immediate feedback.
 
 
 ### Contributing Documentation
@@ -164,24 +167,33 @@ proposals (even if you're applying for Outreachy). Here are some examples:
 
 ### Template
 
+[projecttemplate]: https://docs.google.com/document/d/18LWuA_iTSGSeRFtpVQdfOoz1G30ZgJg-_K0lNSQBYd0/edit
+
+
+#### Google Summer of Code (GSoC)
+
 You must use **[our work program project template][projecttemplate]** to create
-your application. Please make sure that your project leads have comment
+your GSoC application. Please make sure that your project leads have comment
 permissions before you share your document with them.
 
-If you are applying for Outreachy, please link to the project proposal document
-created using this template from your final Outreachy application.
 
-[projecttemplate]: https://docs.google.com/document/d/18LWuA_iTSGSeRFtpVQdfOoz1G30ZgJg-_K0lNSQBYd0/edit
+#### Outreachy
+
+**[Our work program project template][projecttemplate]** is not strictly
+required, but it is an effective tool that allows you to receive draft feedback
+from the project lead. Please make sure that your project leads have comment
+permissions before you share your document with them. Applications that include
+a link to [our work program project template][projecttemplate] are preferred.
 
 
 ## Contacting Project Leads
 
 All the CC project leads are on [Slack](/community/). **Please use public
 channels on Slack as the primary method of communication.** Public channels are
 better than direct messages because it allows any available project lead (or
-even another applicant) to answer your questions and interact with you. It also
-allows other applicants who have the same questions to benefit from the answers
-the project lead is giving you.
+even another applicant and contributors) to answer your questions and interact
+with you. It also allows other applicants and contributors who have the same
+questions to benefit from the answer.
 
 **Please ask project leads specific questions.** We don't know how to help you
 get started unless we know what you have questions about. People come from a
@@ -190,9 +202,8 @@ may be totally different than the things that someone else has questions about.
 Please give us as much information as possible, the more you tell us, the
 better we can help you.
 
-Remember that the project leads are busy – we've got full-time jobs or other
-commitments. It's good to follow up if you don't get a response, but wait a
-couple of days first.
+Remember that the project leads are busy. It is good to follow up if you don't
+get a response, but wait a couple of business days first.
 
 **Please refrain from addressing project leads as "sir" or "ma'am". We prefer
 to be addressed by our first names or usernames.**
@@ -207,11 +218,11 @@ Here are a few things we consider when selecting work program contributors:
   demonstration of your skills.
 - **Community involvement**: One of our major goals is to build an active
   development community and attract long-term contributors. We see engaging in
-  the community, whether it's asking questions, helping other students,
+  the community, whether it is asking questions, helping other students,
   contributing code, filing bugs, or whatever else, as a sign that you're
   genuinely interested in our work.
-- **Contributions**: We appreciate seeing your contributions, they help us
-  gauge your ability to orient yourself to a new codebase, or the quality of
+- **Contributions**: We appreciate seeing your contributions! They help us
+  gauge your ability to orient yourself to a new codebase or the quality of
   your writing. Contribution quality is instrumental in giving us the
   confidence that you have the skills necessary to implement your proposal.
 - **Communication skills and initiative**: These are essential to completing a

content/programs/applicant-guide/contents.lr

@@ -0,0 +1,46 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Automating Quantifying the Commons
+---
+problem:
+The Quantifying the Commons project has seen excellent additions led by student
+developers. However, the scope of previous projects did not include automation
+or combined reporting.
+---
+expected_outcome:
+Add automation of data gathering and report generation so that our reports
+quantifying the commons are never more than 3 months out of date.
+---
+contributor_tasks:
+The contributor will need to architect a data flow, formalize data formats,
+automate data gathering, and automate reporting. Challenges include quota
+limits that may require multi-day/multi-step data gathering, deciding on plain
+text vs binary data formats, and secret management. Knowledge of numpy and
+matplotlib python libraries will be very helpful.
+---
+application_tips:
+- Engage with the repository (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/quantifying](https://github.com/creativecommons/quantifying):
+  Quantifying the Commons
+- [[Feature\] Automate Data Gathering and Analysis/Rendering · Issue
+  #22](https://github.com/creativecommons/quantifying/issues/22)
+---
+skills_recommended:
+- Git
+- GitHub Actions
+- Python
+---
+lead:
+- Timid Robot
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-git skill-github-actions skill-python