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
@@ -155,14 +155,14 @@ <h1>Quantifying the Commons: My Journey so far with outreachy</h1>
155
155
-->
156
156
157
157
<div><p>Hi there! My name is Oreoluwa, from Nigeria. I am an Outreachy intern at
158
-
Creative Commons for the December 2025 cohort. My project involves improving and
159
-
expanding Quantifying the commons. In this post, I will share my progress and
160
-
key takeaways from the first half of my internship.</p>
158
+
Creative Commons for the December 2025 cohort. My project involves improving
159
+
and expanding Quantifying the commons. In this post, I will share my progress
160
+
and key takeaways from the first half of my internship.</p>
161
161
<h2id="project-overview">Project overview</h2><p>Quantifying the commons aims to track and analyse the trends of the creative
162
-
commons legal tools. Who is using these legal tools, where, why, how? We want to
163
-
measure the impact of these tools. For the past 25 years, efforts have
164
-
been made by the organisation to democratize knowledge and content on the
165
-
internet. We want to identify our growth, gaps and areas for development.</p>
162
+
commons legal tools. Who is using these legal tools, where, why, how? We want
163
+
to measure the impact of these tools. For the past 25 years, efforts have been
164
+
made by the organisation to democratize knowledge and content on the internet.
165
+
We want to identify our growth, gaps and areas for development.</p>
166
166
<h3id="a-brief-history-i-learnt-about">A brief history I learnt about</h3><p>After watching a documentary recommended by my mentor. I learnt about a great
167
167
man called Aaron Schwartz who is also known as internet's own boy. He believed
168
168
knowledge should be free and accessible to everyone. His ideas helped inspire
@@ -184,38 +184,39 @@ <h2 id="progress-so-far">Progress so far</h2><h3 id="aligning-the-project-better
184
184
generated previously to avoid regeneration or running of script continuously,
185
185
when we have an output already.</p>
186
186
<h4id="another-script-requirement-is-making-the-script-idempotent">Another script requirement is making the script idempotent</h4><p>Making the script idempotent means executing the python scripts multiple times
187
-
and still get the same output. Before my work on the project, the report scripts
188
-
usually append it sections to the readme using the <code>update_readme()</code> function and
189
-
this allows the order of outputs to change. For example when I run a script, I
190
-
can get A-B-C but when I run it again maybe in the next quarter. I could get
191
-
B-C-A, we don't want it like that. It should be predictable and consistent
192
-
across quarters. But now,it inserts the sections alphabetically to the right
193
-
position regardless of how the python scripts were executed. So we get A-B-C in
194
-
quarter 1 and A-B-C in quarter 2.</p>
187
+
and still get the same output. Before my work on the project, the report
188
+
scripts usually append it sections to the readme using the <code>update_readme()</code>
189
+
function and this allows the order of outputs to change. For example when I run
190
+
a script, I can get A-B-C but when I run it again maybe in the next quarter. I
191
+
could get B-C-A, we don't want it like that. It should be predictable and
192
+
consistent across quarters. But now,it inserts the sections alphabetically to
193
+
the right position regardless of how the python scripts were executed. So we
194
+
get A-B-C in quarter 1 and A-B-C in quarter 2.</p>
195
195
<h4id="documentation-on-the-project">Documentation on the project</h4><p>Improving contributors experience is a big part of the project. During the
196
-
Outreachy contribution phase, new contributors kept on asking the same questions
197
-
over and over again because there were some lack of information in the
198
-
documentation. Timid Robot and I tried to identify areas that were lacking
196
+
Outreachy contribution phase, new contributors kept on asking the same
197
+
questions over and over again because there were some lack of information in
198
+
the documentation. Timid Robot and I tried to identify areas that were lacking
199
199
clarity and we put in more context into the sides of the documentation.</p>
200
200
<h4id="completing-the-three-stages-of-report-for-existing-scripts">Completing the three stages of report for existing scripts</h4><p>Previous contributions had incomplete stages of report for a particular data
201
201
source. I worked on completing the process and report stage for the Openverse
202
202
data source. This required understanding the data fetched and what meaningful
203
203
data or insight can be beneficial for the different teams in the organisation.</p>
204
-
<h3id="current-status">Current status</h3><p>I am currently working on completing the process and report stage for other data
205
-
sources. Then I expand the project by adding new data sources for reporting. An
206
-
iterative task for me is to check for areas in the code that might need
207
-
improvement or better ways of doing things in the codebase.</p>
204
+
<h3id="current-status">Current status</h3><p>I am currently working on completing the process and report stage for other
205
+
data sources. Then I expand the project by adding new data sources for
206
+
reporting. An iterative task for me is to check for areas in the code that
207
+
might need improvement or better ways of doing things in the codebase.</p>
208
208
<h3id="collaboration-with-mentors">Collaboration with mentors</h3><p>My favorite part of this project is my weekly meetup with my mentors, I get to
209
-
ask questions, get ideas on ways I could improve something or solve a problem. I
210
-
also get to review work done by my mentors, which allows me to learn from their
211
-
approaches and imbibe them into my contributions.</p>
209
+
ask questions, get ideas on ways I could improve something or solve a problem.
210
+
I also get to review work done by my mentors, which allows me to learn from
211
+
their approaches and imbibe them into my contributions.</p>
212
212
<h3id="key-takeways">Key takeways</h3><p>Open source has been one of the coolest experiences in my tech journey. It has
213
213
helped me expand my skill set, as I picked up new programming languages along
214
-
the way. I learned to easily identify optimal solutions, especially when working
215
-
within constraints or limitations that could affect outcomes. Through this, I
216
-
realized the importance of building the simplest possible architecture first,
217
-
and then gradually adding components as the solution evolves.</p>
218
-
<p>I am excited to embark on the next half! I hope to make more impact on this project.</p>
214
+
the way. I learned to easily identify optimal solutions, especially when
215
+
working within constraints or limitations that could affect outcomes. Through
216
+
this, I realized the importance of building the simplest possible architecture
217
+
first, and then gradually adding components as the solution evolves.</p>
218
+
<p>I am excited to embark on the next half! I hope to make more impact on this
0 commit comments