Skip to content

Commit 1569845

Browse files
committed
update publish date and unnecessary/pedantic whitespace cleanup
1 parent 480dfd6 commit 1569845

File tree

1 file changed

+40
-41
lines changed
  • content/blog/entries/2026-01-22-My-outreachy-journey

1 file changed

+40
-41
lines changed
Lines changed: 40 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,29 @@
11
title: Quantifying the Commons: My Journey so far with outreachy
22
---
33
categories:
4-
open-source
54
collaboration
65
community
6+
open-source
77
quantifying-the-commons
88
---
99
author: Oreoluwa
1010
---
11-
pub_date: 2023-01-22
11+
pub_date: 2023-01-21
1212
---
1313
body:
1414

1515
Hi there! My name is Oreoluwa, from Nigeria. I am an Outreachy intern at
16-
Creative Commons for the December 2025 cohort. My project involves improving and
17-
expanding Quantifying the commons. In this post, I will share my progress and
18-
key takeaways from the first half of my internship.
16+
Creative Commons for the December 2025 cohort. My project involves improving
17+
and expanding Quantifying the commons. In this post, I will share my progress
18+
and key takeaways from the first half of my internship.
1919

2020
## Project overview
2121

2222
Quantifying the commons aims to track and analyse the trends of the creative
23-
commons legal tools. Who is using these legal tools, where, why, how? We want to
24-
measure the impact of these tools. For the past 25 years, efforts have
25-
been made by the organisation to democratize knowledge and content on the
26-
internet. We want to identify our growth, gaps and areas for development.
23+
commons legal tools. Who is using these legal tools, where, why, how? We want
24+
to measure the impact of these tools. For the past 25 years, efforts have been
25+
made by the organisation to democratize knowledge and content on the internet.
26+
We want to identify our growth, gaps and areas for development.
2727

2828
### A brief history I learnt about
2929

@@ -55,56 +55,55 @@ interruption. I integrated a workflow that checks if an output has been
5555
generated previously to avoid regeneration or running of script continuously,
5656
when we have an output already.
5757

58-
#### Another script requirement is making the script idempotent
58+
#### Another script requirement is making the script idempotent
5959

6060
Making the script idempotent means executing the python scripts multiple times
61-
and still get the same output. Before my work on the project, the report scripts
62-
usually append it sections to the readme using the `update_readme()` function and
63-
this allows the order of outputs to change. For example when I run a script, I
64-
can get A-B-C but when I run it again maybe in the next quarter. I could get
65-
B-C-A, we don't want it like that. It should be predictable and consistent
66-
across quarters. But now,it inserts the sections alphabetically to the right
67-
position regardless of how the python scripts were executed. So we get A-B-C in
68-
quarter 1 and A-B-C in quarter 2.
61+
and still get the same output. Before my work on the project, the report
62+
scripts usually append it sections to the readme using the `update_readme()`
63+
function and this allows the order of outputs to change. For example when I run
64+
a script, I can get A-B-C but when I run it again maybe in the next quarter. I
65+
could get B-C-A, we don't want it like that. It should be predictable and
66+
consistent across quarters. But now,it inserts the sections alphabetically to
67+
the right position regardless of how the python scripts were executed. So we
68+
get A-B-C in quarter 1 and A-B-C in quarter 2.
6969

70-
#### Documentation on the project
70+
#### Documentation on the project
7171

7272
Improving contributors experience is a big part of the project. During the
73-
Outreachy contribution phase, new contributors kept on asking the same questions
74-
over and over again because there were some lack of information in the
75-
documentation. Timid Robot and I tried to identify areas that were lacking
76-
clarity and we put in more context into the sides of the documentation.
77-
73+
Outreachy contribution phase, new contributors kept on asking the same
74+
questions over and over again because there were some lack of information in
75+
the documentation. Timid Robot and I tried to identify areas that were lacking
76+
clarity and we put in more context into the sides of the documentation.
7877

7978
#### Completing the three stages of report for existing scripts
8079

8180
Previous contributions had incomplete stages of report for a particular data
8281
source. I worked on completing the process and report stage for the Openverse
8382
data source. This required understanding the data fetched and what meaningful
84-
data or insight can be beneficial for the different teams in the organisation.
85-
86-
### Current status
83+
data or insight can be beneficial for the different teams in the organisation.
8784

88-
I am currently working on completing the process and report stage for other data
89-
sources. Then I expand the project by adding new data sources for reporting. An
90-
iterative task for me is to check for areas in the code that might need
91-
improvement or better ways of doing things in the codebase.
85+
### Current status
9286

87+
I am currently working on completing the process and report stage for other
88+
data sources. Then I expand the project by adding new data sources for
89+
reporting. An iterative task for me is to check for areas in the code that
90+
might need improvement or better ways of doing things in the codebase.
9391

94-
### Collaboration with mentors
92+
### Collaboration with mentors
9593

9694
My favorite part of this project is my weekly meetup with my mentors, I get to
97-
ask questions, get ideas on ways I could improve something or solve a problem. I
98-
also get to review work done by my mentors, which allows me to learn from their
99-
approaches and imbibe them into my contributions.
95+
ask questions, get ideas on ways I could improve something or solve a problem.
96+
I also get to review work done by my mentors, which allows me to learn from
97+
their approaches and imbibe them into my contributions.
10098

101-
### Key takeways
99+
### Key takeways
102100

103101
Open source has been one of the coolest experiences in my tech journey. It has
104102
helped me expand my skill set, as I picked up new programming languages along
105-
the way. I learned to easily identify optimal solutions, especially when working
106-
within constraints or limitations that could affect outcomes. Through this, I
107-
realized the importance of building the simplest possible architecture first,
108-
and then gradually adding components as the solution evolves.
103+
the way. I learned to easily identify optimal solutions, especially when
104+
working within constraints or limitations that could affect outcomes. Through
105+
this, I realized the importance of building the simplest possible architecture
106+
first, and then gradually adding components as the solution evolves.
109107

110-
I am excited to embark on the next half! I hope to make more impact on this project.
108+
I am excited to embark on the next half! I hope to make more impact on this
109+
project.

0 commit comments

Comments
 (0)