Skip to content

Commit 9e47023

Browse files
committed
add project ideas
1 parent 5799eaf commit 9e47023

File tree

4 files changed

+229
-0
lines changed
  • content/programs/project-ideas-collection

4 files changed

+229
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Add plain text format to CC Legal Tools
6+
---
7+
problem:
8+
Plain text formats for the 4.0 licenses and the CC0 public domain dedication
9+
were created using a manual process ([Plaintext versions of Creative Commons
10+
licenses and CC0 - Creative Commons][blogplaintext]). Only the English
11+
versions of the legal tools were formatted as plain text. Additionally, that
12+
manual creation process was not without errors and is not sustainable.
13+
14+
[blogplaintext]: https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/
15+
---
16+
expected_outcome:
17+
Extend the CC Legal Tools App to generate deterministic plain text versions of
18+
the 4.0 licenses and the CC0 public domain dedication.
19+
---
20+
contributor_tasks:
21+
The contributor will need to extend the CC Legal Tools App to generate plain
22+
text versions. The generated plain text versions must be deterministic and
23+
match the formatting of the manual versions (except where improvements are
24+
desired). Application updates must include test coverage. Stretch goals include
25+
markdown format generation and interfacing/collaborating with SPDX.
26+
---
27+
application_tips:
28+
- Engage with the CC Legal Tools repositories (issues, pull requests)
29+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
30+
- [Applicant Guide](/programs/applicant-guide/)
31+
---
32+
resources:
33+
- [creativecommons/cc-legal-tools-app][cc-legal-tools-app]: License and public
34+
domain dedication management application for Creative Commons
35+
- [creativecommons/cc-legal-tools-data][cc-legal-tools-data]: License and
36+
public domain dedication data for Creative Commons
37+
- [Plaintext versions of Creative Commons licenses and CC0 - Creative
38+
Commons][blogplaintext]
39+
40+
[cc-legal-tools-app]: https://github.com/creativecommons/cc-legal-tools-app
41+
[cc-legal-tools-data]: https://github.com/creativecommons/cc-legal-tools-data
42+
[blogplaintext]: https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/
43+
---
44+
skills_recommended:
45+
- Djano
46+
- Git
47+
- Python
48+
---
49+
lead:
50+
- Timid Robot
51+
---
52+
difficulty: Medium
53+
---
54+
size: Large (~350 hours)
55+
---
56+
filter_value: difficulty-medium skill-django skill-git skill-python
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Add RDF XML format to CC Legal Tools
6+
---
7+
problem:
8+
The CC Legal Tools App is currently using legacy RDF files for the machine
9+
readable layer of the legal tools. Those files are out of date and contain a
10+
few errors and omissions. This technical debt also prevents future work to
11+
improve the machine readable layer of the CC Legal Tools.
12+
---
13+
expected_outcome:
14+
Extend the CC Legal Tools App to generate deterministic RDF XML files for all
15+
of the legal tools.
16+
---
17+
contributor_tasks:
18+
The contributor will need to extend the CC Legal Tools App to generate RDF XML
19+
files. The generated RDF XML files must be deterministic and well organized and
20+
based on current RDF specifications. Application updates must include test
21+
coverage. Stretch goals include planning any breaking changes and working on a
22+
static API.
23+
---
24+
application_tips:
25+
- Engage with the CC Legal Tools repositories (issues, pull requests)
26+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
27+
- [Applicant Guide](/programs/applicant-guide/)
28+
---
29+
resources:
30+
- [creativecommons/cc-legal-tools-app][cc-legal-tools-app]: License and public
31+
domain dedication management application for Creative Commons
32+
- [creativecommons/cc-legal-tools-data][cc-legal-tools-data]: License and
33+
public domain dedication data for Creative Commons
34+
- [Describing Copyright in RDF - Creative Commons Rights Expression Language][describerdf]
35+
36+
[cc-legal-tools-app]: https://github.com/creativecommons/cc-legal-tools-app
37+
[cc-legal-tools-data]: https://github.com/creativecommons/cc-legal-tools-data
38+
[describerdf]: https://creativecommons.org/ns/
39+
---
40+
skills_recommended:
41+
- Djano
42+
- Git
43+
- Python
44+
- RDF
45+
- XML
46+
---
47+
lead:
48+
- Timid Robot
49+
---
50+
difficulty: High
51+
---
52+
size: Large (~350 hours)
53+
---
54+
filter_value: difficulty-high skill-django skill-git skill-python skill-rdf skill-xml
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Modernize termination-of-transfer WordPress plugin
6+
---
7+
problem:
8+
Due to its current setup and structure it is difficult to install from the
9+
codebase directly into a WordPress installation (i.e. via Composer).
10+
Additionally, the codebase has sections that need to be checked and updated to
11+
current coding standards and best practices.
12+
---
13+
expected_outcome:
14+
The plugin’s structure and setup follows current development standards, increasing maintainability and ease-of-use.
15+
---
16+
contributor_tasks:
17+
The contributor will restructure the repo, adjusting any necessary code to meet
18+
current WordPress plugin development standards, and best practices for PHP and
19+
Javascript (follow appropriate ECMAScript standards), while creating a
20+
directory structure that allows the codebase to be deployed into a standard
21+
WordPress installation.
22+
---
23+
application_tips:
24+
- Engage with the CC Legal Tools repositories (issues, pull requests)
25+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
26+
- [Applicant Guide](/programs/applicant-guide/)
27+
---
28+
resources:
29+
- [creativecommons/termination-of-transfer][termination-of-transfer]
30+
- [[Feature] Convert repository / codebase to a WordPress plugin that can be
31+
installed via composer #127][issue127]
32+
- [Introduction to Plugin Development][wp-plugin-dev]
33+
- [MDN Web Docs: ECMAScript Standards][mdm-ecma-standards]
34+
- [PHP-FIG: PSR-1][psr1]
35+
36+
[termination-of-transfer]: https://github.com/creativecommons/termination-of-transfer
37+
[issue127]: https://github.com/creativecommons/termination-of-transfer/issues/127
38+
[wp-plugin-dev]: https://developer.wordpress.org/plugins/intro/
39+
[mdm-ecma-standards]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/JavaScript_technologies_overview#standardization_process
40+
[psr1]: https://www.php-fig.org/psr/psr-1/
41+
---
42+
skills_recommended:
43+
- Git
44+
- JavaScript
45+
- PHP
46+
- WordPress
47+
---
48+
lead:
49+
- Sara
50+
---
51+
difficulty: Medium
52+
---
53+
size: Large (~350 hours)
54+
---
55+
filter_value: difficulty-medium skill-git skill-javascript skill-php skill-wordpress
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Refactor CC meta search
6+
---
7+
problem:
8+
The legacy CC meta search site doesn’t match the current visuals of the rest of
9+
CC web entities, and it’s built on PHP which requires a more complex hosting
10+
setup that can’t reside somewhere that supports simple static output (like
11+
GitHub pages). Additionally the code is set up in a legacy fashion, is not
12+
semantic, may contain accessibility issues, and contains broken meta searches.
13+
---
14+
expected_outcome:
15+
Simplify and modernize the codebase and requirements of the legacy CC meta
16+
search, improve functionality, and update the visuals to match current CC
17+
standards and norms.
18+
---
19+
contributor_tasks:
20+
Rewrite the application, maintaining its original function, as a static site
21+
on GitHub pages, using semantic, standards-compliant, and accessible HTML, CSS,
22+
and JavaScript. Update the visual aesthetic and overall appearance to better
23+
correspond with other current CC web entities.
24+
---
25+
application_tips:
26+
- Engage with the CC Legal Tools repositories (issues, pull requests)
27+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
28+
- [Applicant Guide](/programs/applicant-guide/)
29+
---
30+
resources:
31+
- [creativecommons/search][repo-search]: Legacy Creative Commons Search, no
32+
longer under development
33+
- [oldsearch.creativecommons.org][oldsearch]
34+
- [MDN Web Docs: Semantics][mdm-semantics]
35+
- [MDN Web Docs: HTML][mdm-html]
36+
- [MDN Web Docs: JavaScript][mdm-javascript]
37+
- [WAVE Report for “oldsearch.creativecommons.org”][wave-report]
38+
- [About GitHub Pages][about-ghpages]
39+
40+
[repo-search]: https://github.com/creativecommons/search
41+
[oldsearch]: https://oldsearch.creativecommons.org/
42+
[oldsearch]: https://oldsearch.creativecommons.org/
43+
[mdm-semantics]: https://developer.mozilla.org/en-US/docs/Glossary/Semantics
44+
[mdm-html]: https://developer.mozilla.org/en-US/docs/Web/HTML
45+
[mdm-javascript]: https://developer.mozilla.org/en-US/docs/Web/JavaScript
46+
[wave-report]: https://wave.webaim.org/report#/https://oldsearch.creativecommons.org/
47+
[about-ghpages]: https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages
48+
---
49+
skills_recommended:
50+
- CSS
51+
- Git
52+
- GitHub Pages
53+
- HTML
54+
- JavaScript
55+
- JSON
56+
---
57+
lead:
58+
- Sara
59+
---
60+
difficulty: Medium
61+
---
62+
size: Large (~350 hours)
63+
---
64+
filter_value: difficulty-medium skill-css skill-git skill-githubpages skill-html skill-javascript skill-json

0 commit comments

Comments
 (0)