Merge pull request creativecommons#664 from creativecommons/outreachy-2022-dec-project-ideas

Outreachy 2022 Dec project ideas

Author: TimidRobot

content/blog/authors/sara/contents.lr

@@ -0,0 +1,12 @@
+username: sara
+---
+name: Sara Lovell
+---
+md5_hashed_email:
+---
+about:
+Sara is the Full-Stack Engineer at [Creative Commons][creativecommons]. She is
+`@sara` on [CC Slack](/community/) and [possumbilities][github] on GitHub.
+
+[creativecommons]: https://creativecommons.org/author/saracreativecommons-org/
+[github]: https://github.com/possumbilities

content/programs/applicant-guide/contents.lr

@@ -50,9 +50,9 @@ anything like that, please don't hesitate to ask!
 
 [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 mentors 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!
+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!
 
 
 ### Pick a Project
@@ -116,8 +116,8 @@ 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 mentors are
-busy so we can be slow to provide feedback.
+received feedback on them or if they have not been merged--our project leads
+are busy so we can be slow to provide feedback.
 
 
 ### Contributing Documentation
@@ -148,10 +148,10 @@ of work here to turn those into a feasible plan and timeline for a complete
 project that you can ship during the work program.
 
 **This is not something you should be working on in isolation.** We expect you
-to have a lot of questions for the mentors along the way as you try and
+to have a lot of questions for the project leads along the way as you try and
 understand the project, come up with ideas, evaluate feasibility, etc. We also
-expect you to come up with a first draft and get feedback from mentors before
-you submit the final application on the program's official site.
+expect you to come up with a first draft and get feedback from project leads
+before you submit the final application on the program's official site.
 
 We suggest reading some articles on writing good Google Summer of Code
 proposals (even if you're applying for Outreachy). Here are some examples:
@@ -165,23 +165,23 @@ proposals (even if you're applying for Outreachy). Here are some examples:
 ### Template
 
 You must use **[our work program project template][projecttemplate]** to create
-your application. Please make sure that your mentors have comment permissions
-before you share your document with them.
+your 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
 
 
-## Contacting Mentors
+## 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 mentor is giving you.
+the project lead is giving you.
 
 **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

content/programs/contents.lr

@@ -63,6 +63,8 @@ We will apply for the December 2022 interships.
 
 | Name | Pronouns | Slack Username |
 | ---- | -------- | -------------- |
+| [Sara][authorsara] | she/her | `@sara` |
 | [Timid Robot][authortimidrobot] | they/them | `@Timid Robot` |
 
+[authorsara]: /blog/authors/sara/
 [authortimidrobot]: /blog/authors/TimidRobot/

content/programs/lead-guide/contents.lr

@@ -12,23 +12,26 @@ page serves as a general project lead guide.
 ---
 body:
 
+
 ## Considerinng Being a Project Lead?
 
-Leading a project or mentorship is a serious commitment but a very rewarding
-experience. If you're trying to decide whether to be a project lead, please
-read the following documents:
-- [Google Summer of Code mentor
-  guide](https://google.github.io/gsocguides/mentor/)
-- Outreachy [mentor role description](https://www.outreachy.org/mentor/#mentor)
-  and [mentor expectations][outmentorexpect]
-- [Outreachy Mentor FAQ](https://www.outreachy.org/mentor/mentor-faq/)
+Leading a project is a serious commitment but a very rewarding experience. If
+you're trying to decide whether to be a project lead, please read the following
+documents:
+- Google Summer of Code (GSoC) [mentor guide][gsocmentor]
+- Outreachy [mentor role description][outmentorrole], [mentor
+  expectations][outmentorexpect], and [mentor FAQ][outmentorfaq]
 
 If you'd like to be a project lead but don't have a specific project in mind,
 email the [CC Developers mailing list](/community/) and let us know what your
 skillset and availability is. We'll see if we have a project you can help out
 with. If you'd like to propose a project, read on.
 
+[gsocmentor]: https://google.github.io/gsocguides/mentor/
+[outmentorrole]: https://www.outreachy.org/mentor/#mentor
 [outmentorexpect]: https://www.outreachy.org/docs/internship/#mentor-expectations
+[outmentorfaq]: https://www.outreachy.org/mentor/mentor-faq/
+
 
 ## Proposing a Project
 
@@ -52,12 +55,13 @@ _**[Project Title]**_
 - **Technical Skills**: _What technical skills will this project need?_
 - **Difficulty**: _How technically difficult is this project? Options: High,
   Medium, Low_
-- **Size**: _Large (~350 hours) or Medium (~175 hours)._
+- **Size**: _Options: Large (~350 hours) or Medium (~175 hours)._
 
 Please note that project ideas should be related to an existing CC open source
 project or website and should be clearly scoped out. They should be doable in
 three months by a contributor with very little prior experience.
 
+
 ## Application Period
 
 Once the initial application period opens, things get chaotic for a little bit
@@ -78,6 +82,7 @@ Some tips:
   because there are far too many people, so help them help themselves.
 - Prepare general documentation/frequently asked questions ahead of time.
 
+
 ### Draft Application
 
 You should encourage applicants to share drafts of the application with you
@@ -87,18 +92,21 @@ understanding of the project, the project plan, timeline, and deliverables
 match what you had in mind and is feasible (keeping in mind that they may be
 new to all this and may not get things done as quickly).
 
+
 ## Work Program Period
 
+
 ### Preparing
 
 Before the work program period begins:
-- Talk to your backup lead/secondary mentor ahead of your time to create a plan
-  for how to collaborate:
+- Talk to your backup lead ahead of your time to create a plan for how to
+  collaborate:
   - Who will be repsonsible for what?
   - How will checkins and notes work?
-- If your project affects or involves anyone else at CC that's not
-  leading/mentoring the project, talk to them about how they would like to be
-  involved and come up with a plan to collaborate.
+- If your project affects or involves anyone else at CC that's not leading the
+  project, talk to them about how they would like to be involved and come up
+  with a plan to collaborate.
+
 
 ### Post-Announcement
 
@@ -112,9 +120,9 @@ Once the selected contributors have been announced:
   fix these items before any work is actually started.
 - have an introductory call with the contributor and get to know each other. ask
   them questions about themselves and talk about yourself too.
-- set up regular meetings: a weekly video call for the mentors to check-in with
-  the contributor, and a monthly call with the cc program coordinator to check
-  in with the contributor.
+- set up regular meetings: a weekly video call for the project lead to check-in
+  with the contributor, and a monthly call with the cc program coordinator to
+check in with the contributor.
 - create a document to keep any project information and notes. this document
   should be shared with the program coordinators.
    - the “final” implementation plan and weekly milestones (“final” because it
@@ -140,11 +148,12 @@ Once the selected contributors have been announced:
 - ensure that the contributor has permissions to push to the appropriate GitHub
   repository.
 
+
 ### During the Work Program
 
 During the work program:
 - Attend your weekly check-in.
-   - Take good notes so that your backup mentor can pick up where you left off
+   - Take good notes so that your backup lead can pick up where you left off
      easily if you’re unavailable.
    - Make sure the contributor is on-track with their weekly milestones and if
      not, work with them to figure out why and come up with a plan.
@@ -159,7 +168,7 @@ During the work program:
   they are often not experienced with the work they are doing and may not know
   to ask for help or may be stuck on something that they cannot articulate very
   well.
-- Ask for feedback on your mentorship every few weeks.
+- Ask for feedback as the project lead every few weeks.
 - Find an opportunity to invite your contributor to present their work at CC’s
   all staff meeting. It is up to you when you’d like to do this.
 - Make sure you're familiar with the program timeline and submit your required
@@ -178,4 +187,4 @@ During the work program:
    - your contributor is not communicating enough or misses a check-in.
    - you have concerns or even just a bad feeling about something.
    - you have feedback or questions about any part of the program process.
-   - you'd like feedback about how your mentoring is going
+   - you'd like feedback about how your role as project lead is going

content/programs/project-ideas-collection/add-plain-text-format-to-cc-legal-tools/contents.lr

@@ -0,0 +1,56 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Add plain text format to CC Legal Tools
+---
+problem:
+Plain text formats for the 4.0 licenses and the CC0 public domain dedication
+were created using a manual process ([Plaintext versions of Creative Commons
+licenses and CC0 - Creative Commons][blogplaintext]).  Only the English
+versions of the legal tools were formatted as plain text.  Additionally, that
+manual creation process was not without errors and is not sustainable.
+
+[blogplaintext]: https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/
+---
+expected_outcome:
+Extend the CC Legal Tools App to generate deterministic plain text versions of
+the 4.0 licenses and the CC0 public domain dedication.
+---
+contributor_tasks:
+The contributor will need to extend the CC Legal Tools App to generate plain
+text versions. The generated plain text versions must be deterministic and
+match the formatting of the manual versions (except where improvements are
+desired). Application updates must include test coverage. Stretch goals include
+Markdown format generation and interfacing/collaborating with SPDX.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/cc-legal-tools-app][cc-legal-tools-app]: License and public
+  domain dedication management application for Creative Commons
+- [creativecommons/cc-legal-tools-data][cc-legal-tools-data]: License and
+  public domain dedication data for Creative Commons
+- [Plaintext versions of Creative Commons licenses and CC0 - Creative
+  Commons][blogplaintext]
+
+[cc-legal-tools-app]: https://github.com/creativecommons/cc-legal-tools-app
+[cc-legal-tools-data]: https://github.com/creativecommons/cc-legal-tools-data
+[blogplaintext]: https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/
+---
+skills_recommended:
+- Djano
+- Git
+- Python
+---
+lead:
+- Timid Robot
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-django skill-git skill-python

content/programs/project-ideas-collection/add-rdf-xml-format-to-cc-legal-tools/contents.lr

@@ -0,0 +1,54 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Add RDF XML format to CC Legal Tools
+---
+problem:
+The CC Legal Tools App is currently using legacy RDF files for the machine
+readable layer of the legal tools. Those files are out of date and contain a
+few errors and omissions. This technical debt also prevents future work to
+improve the machine readable layer of the CC Legal Tools.
+---
+expected_outcome:
+Extend the CC Legal Tools App to generate deterministic RDF XML files for all
+of the legal tools.
+---
+contributor_tasks:
+The contributor will need to extend the CC Legal Tools App to generate RDF XML
+files. The generated RDF XML files must be deterministic and well organized and
+based on current RDF specifications. Application updates must include test
+coverage. Stretch goals include planning any breaking changes and working on a
+static API.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/cc-legal-tools-app][cc-legal-tools-app]: License and public
+  domain dedication management application for Creative Commons
+- [creativecommons/cc-legal-tools-data][cc-legal-tools-data]: License and
+  public domain dedication data for Creative Commons
+- [Describing Copyright in RDF - Creative Commons Rights Expression Language][describerdf]
+
+[cc-legal-tools-app]: https://github.com/creativecommons/cc-legal-tools-app
+[cc-legal-tools-data]: https://github.com/creativecommons/cc-legal-tools-data
+[describerdf]: https://creativecommons.org/ns/
+---
+skills_recommended:
+- Djano
+- Git
+- Python
+- RDF
+- XML
+---
+lead:
+- Timid Robot
+---
+difficulty: High
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-high skill-django skill-git skill-python skill-rdf skill-xml

content/programs/project-ideas-collection/modernize-termination-of-transfer-wp-plugin/contents.lr

@@ -0,0 +1,55 @@
+_model: project-idea
+---
+_hidden: yes
+---
+title: Modernize termination-of-transfer WordPress plugin
+---
+problem:
+Due to its current setup and structure it is difficult to install from the
+codebase directly into a WordPress installation (i.e. via Composer).
+Additionally, the codebase has sections that need to be checked and updated to
+current coding standards and best practices.
+---
+expected_outcome:
+The plugin’s structure and setup follows current development standards, increasing maintainability and ease-of-use.
+---
+contributor_tasks:
+The contributor will restructure the repo, adjusting any necessary code to meet
+current WordPress plugin development standards, and best practices for PHP and
+Javascript (follow appropriate ECMAScript standards), while creating a
+directory structure that allows the codebase to be deployed into a standard
+WordPress installation.
+---
+application_tips:
+- Engage with the CC Legal Tools repositories (issues, pull requests)
+- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
+- [Applicant Guide](/programs/applicant-guide/)
+---
+resources:
+- [creativecommons/termination-of-transfer][termination-of-transfer]
+- [[Feature] Convert repository / codebase to a WordPress plugin that can be
+  installed via composer #127][issue127]
+- [Introduction to Plugin Development][wp-plugin-dev]
+- [MDN Web Docs: ECMAScript Standards][mdm-ecma-standards]
+- [PHP-FIG: PSR-1][psr1]
+
+[termination-of-transfer]: https://github.com/creativecommons/termination-of-transfer
+[issue127]: https://github.com/creativecommons/termination-of-transfer/issues/127
+[wp-plugin-dev]: https://developer.wordpress.org/plugins/intro/
+[mdm-ecma-standards]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/JavaScript_technologies_overview#standardization_process
+[psr1]: https://www.php-fig.org/psr/psr-1/
+---
+skills_recommended:
+- Git
+- JavaScript
+- PHP
+- WordPress
+---
+lead:
+- Sara
+---
+difficulty: Medium
+---
+size: Large (~350 hours)
+---
+filter_value: difficulty-medium skill-git skill-javascript skill-php skill-wordpress