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
<h3><ahref="#conslidate-implement-vocabulary-design-system-across-websites">Consolidate and implement Vocabulary design system across ancillary</a></h3>
140
+
<h3><ahref="#quantifying">Improving Quantifying the Commons</a></h3>
<h2><aname="conslidate-implement-vocabulary-design-system-across-websites">Consolidate and implement Vocabulary design system across ancillary</a></h2>
154
+
<h2><aname="quantifying">Improving Quantifying the Commons</a></h2>
155
155
<divclass="project-container">
156
156
<divclass="project-summary">
157
157
<h5>Difficulty</h5>
158
158
<p>Medium</p>
159
159
<h5>Size</h5>
160
-
<p>Large (~350 hours)</p>
160
+
<p>Large (~350 hours, ~12 weeks)</p>
161
161
<h5>Skills recommended</h5>
162
162
<ul>
163
-
<li>CSS</li>
164
-
<li>Django</li>
163
+
<li>APIs</li>
165
164
<li>Git</li>
166
-
<li>HTML</li>
167
-
<li>JavaScript</li>
168
-
<li>Lektor</li>
165
+
<li>GitHub Actions</li>
166
+
<li>Python</li>
169
167
</ul>
170
168
171
169
<h5>Project Lead</h5>
172
170
<ul>
173
-
<li>Sara</li>
171
+
<li>Timid Robot</li>
174
172
</ul>
175
173
176
174
</div>
177
175
<divclass="project-description">
178
176
<h3>The Problem</h3>
179
-
<p><p>The new design system, Vocabulary, has been implemented to varying degrees
180
-
across several Creative Commons web entities, versioning and features do not
181
-
have full parity and each implementation merits a further investigation,
182
-
course correction, expansion, and cleanup.</p>
177
+
<p><p>The Quantifying the Commons project has seen excellent additions led by student
178
+
developers and contributors. A couple of data sources have been automated, but many more remain.</p>
183
179
</p>
184
180
<h3>Expected Outcome</h3>
185
-
<p><p>Ancillary CC websites implement the current versions and features of the latest
186
-
Vocabulary codebase in a consistent and stable manner. Necessary new features
187
-
are identified, built, and implemented upstream into Vocabulary itself where
188
-
relevant, localized features are implemented into the codebase of each project
189
-
where necessary.</p>
181
+
<p><p>Add automated data fetching, processing, and reporting of new sources.</p>
190
182
</p>
191
183
<h3>Contributor Tasks</h3>
192
-
<p><p>Identify and catalog features present on current sites, but missing within
193
-
Vocabulary. Document migration paths between conflicting or missing UX patterns.
194
-
Rewrite and/or refactor the codebase of each ancillary site, maintaining its
195
-
original function, while implementing the Vocabulary design system; migrating
196
-
implementations from NPM dependency chains to more simplistic static code, where
197
-
needed; building out new features as necessary locally or within the Vocabulary
198
-
codebase itself. Using simple, standards-compliant, and accessible HTML, CSS,
199
-
and minimal JavaScript.</p>
184
+
<p><p>The contributor will need to adapt or improve the data flow. New sources should
185
+
utilize the existing codebase as much as possible and ensure improvements are
186
+
implemnted consistently across sources. Challenges include quota limits that
187
+
may require multi-day/multi-step data gathering, incomplete source
188
+
documentation, and ensuring data is reported clearly. Knowledge of numpy and
189
+
matplotlib python libraries will be very helpful.</p>
200
190
</p>
201
191
<h3>Application Tips</h3>
202
192
<p><ul>
203
-
<li>Engage with the ancillary sites and Vocabulary repositories (issues, pull requests)</li>
193
+
<li>Engage with the repository (issues, pull requests)</li>
204
194
<li>Be helpful and welcoming (e.g. answer other contributors’ questions on Zulip)</li>
0 commit comments