Skip to content

Commit d7aa80b

Browse files
authored
Merge pull request creativecommons#694 from creativecommons/20230203-project-ideas
Update project ideas list
2 parents d9396b8 + 16908ab commit d7aa80b

File tree

8 files changed

+228
-231
lines changed

8 files changed

+228
-231
lines changed

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

-59
This file was deleted.

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

-54
This file was deleted.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Automating Quantifying the Commons
6+
---
7+
problem:
8+
The Quantifying the Commons project has seen excellent additions led by student
9+
developers. However, the scope of previous projects did not include automation
10+
or combined reporting.
11+
---
12+
expected_outcome:
13+
Add automation of data gathering and report generation so that our reports
14+
quantifying the commons are never more than 3 months out of date.
15+
---
16+
contributor_tasks:
17+
The contributor will need to architect a data flow, formalize data formats,
18+
automate data gathering, and automate reporting. Challenges include quota
19+
limits that may require multi-day/multi-step data gathering, deciding on plain
20+
text vs binary data formats, and secret management. Knowledge of numpy and
21+
matplotlib python libraries will be very helpful.
22+
---
23+
application_tips:
24+
- Engage with the repository (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/quantifying](https://github.com/creativecommons/quantifying):
30+
Quantifying the Commons
31+
- [[Feature\] Automate Data Gathering and Analysis/Rendering · Issue
32+
#22](https://github.com/creativecommons/quantifying/issues/22)
33+
---
34+
skills_recommended:
35+
- Git
36+
- GitHub Actions
37+
- Python
38+
---
39+
lead:
40+
- Timid Robot
41+
---
42+
difficulty: Medium
43+
---
44+
size: Large (~350 hours)
45+
---
46+
filter_value: difficulty-medium skill-git skill-github-actions skill-python
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: CC Legal Tools: Machine Readable Layer
6+
---
7+
problem:
8+
The CC Legal tools consist of three parts, the legal code, the deed (simple
9+
language description), and the machine readable. The machine readable layer has
10+
received the least recent development. It is out of date and there are
11+
unresolved issues.
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+
Stretch goal: Extend the CC Legal Tools App to generate deterministic plain
18+
text versions of 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 RDF XML
22+
files. The generated RDF XML files must be deterministic and well organized and
23+
based on current RDF specifications. Application updates must include test
24+
coverage.
25+
26+
Stretch goal: Extend the CC Legal Tools App to generate plain text versions.
27+
The generated plain text versions must be deterministic and match the
28+
formatting of the manual versions (except where improvements are desired).
29+
Application updates must include test coverage. Additional stretch goals
30+
include adding markdown format generation and interfacing/collaborating with
31+
SPDX.
32+
---
33+
application_tips:
34+
- Engage with the CC Legal Tools repositories (issues, pull requests)
35+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
36+
- [Applicant Guide](/programs/applicant-guide/)
37+
---
38+
resources:
39+
- [creativecommons/cc-legal-tools-app](https://github.com/creativecommons/cc-legal-tools-app/):
40+
License and public domain dedication management application for Creative
41+
Commons
42+
- [creativecommons/cc-legal-tools-data](https://github.com/creativecommons/cc-legal-tools-data):
43+
License and public domain dedication data for Creative Commons
44+
- **ccREL (RDF/XML)**
45+
- [Describing Copyright in RDF - Creative Commons Rights Expression
46+
Language](https://creativecommons.org/ns/)
47+
- [CC REL - Creative Commons](https://wiki.creativecommons.org/wiki/CC_REL) (CC
48+
Public Wiki)
49+
- [creativecommons/ccrel](https://github.com/creativecommons/ccrel)
50+
- [ccREL: The Creative Commons Rights Expression
51+
Language](https://opensource.creativecommons.org/ccrel/)
52+
- [creativecommons/ccrel-guide](https://github.com/creativecommons/ccrel-guide)
53+
- [CC REL by Example](https://opensource.creativecommons.org/ccrel-guide/)
54+
- **Plain text format**
55+
- [Plaintext versions of Creative Commons 4.0 licenses - Creative
56+
Commons](https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/)
57+
- [Plaintext versions of Creative Commons licenses and CC0 - Creative
58+
Commons](https://creativecommons.org/2011/04/15/plaintext-versions-of-creative-commons-licenses-and-cc0/)
59+
---
60+
skills_recommended:
61+
- Django
62+
- Git
63+
- Python
64+
- RDF
65+
- XML
66+
---
67+
lead:
68+
- Timid Robot
69+
---
70+
difficulty: High
71+
---
72+
size: Large (~350 hours)
73+
---
74+
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,50 @@
1+
_model: project-idea
2+
---
3+
_hidden: yes
4+
---
5+
title: Modernize CC Resource Archive
6+
---
7+
problem:
8+
The Resources Archive has an outdated visual setup, and needs functionality
9+
fixes and improvements.
10+
---
11+
expected_outcome:
12+
Upgrade the look & feel to match current CC aesthetics, using the internal
13+
Design System (Vocabulary). Codebase is running current and standards compliant
14+
technology implementations. Entire site builds as static files on GH pages.
15+
Generate clear documentation of codebase and functionality.
16+
---
17+
contributor_tasks:
18+
Contributor will refactor codebase to fix resource submission, use current
19+
semantic, accessible, and standards compliant HTML, CSS, and JavaScript to
20+
match the current visual aesthetic of Creative Commons sites. Improve the
21+
overall UX for finding, submitting, and accessing resources. Ensure the site
22+
functions as a static and stable Jekyll site hosted on GH Pages as static
23+
files. Final implementation will have clear documentation drafted within the
24+
codebase for future maintainability.
25+
---
26+
application_tips:
27+
- Engage with the repository (issues, pull requests)
28+
- Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
29+
- [Applicant Guide](/programs/applicant-guide/)
30+
---
31+
resources:
32+
- [creativecommons/cc-resource-archive](https://github.com/creativecommons/cc-resource-archive): CC Resource Archive
33+
- [Jekyll](https://jekyllrb.com/)
34+
- [GH Pages](https://pages.github.com/)
35+
---
36+
skills_recommended:
37+
- Git
38+
- JavaScript
39+
- Jekyll
40+
- HTML (Semantic & Accessible)
41+
- CSS (Structured & Accessible)
42+
---
43+
lead:
44+
- Sara
45+
---
46+
difficulty: Medium
47+
---
48+
size: Large (~350 hours)
49+
---
50+
filter_value: difficulty-medium skill-git skill-javascript skill-jekyll skill-html skill-css

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

-55
This file was deleted.

0 commit comments

Comments
 (0)