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
Copy file name to clipboardExpand all lines: commcall.qmd
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ We create a event page in our website under Community Calls to share the main in
27
27
28
28
The event page is shared through our communications channels:
29
29
30
-
***Newsletter:** Our newsletter has around 2500 registered readers. We shared all upcoming community calls in our HQ section and the resources (like video, articles and slides) after the call.
30
+
***Newsletter:** Our newsletter reaches a large audience (>1000 opens per month). We shared all upcoming community calls in our HQ section and the resources (like video, articles and slides) after the call.
31
31
32
32
***Social Media:** Before the call, we use social media posts to announce the theme and raise awareness. We set the same agenda for all community calls: a "Save the date" announcement a month before, a reminder one week before the event, one day before the event and one hour before the call.
33
33
During the community call, we live-post under a dedicated hashtag (#translathon and #rohackathon2025), sharing screenshots, participant quotes, and quick updates to capture the energy of the event. After the call, we post highlights and linked to the [recap blog](/blog/2025/01/24/coworking-hackathons/), while beginning a countdown to the hackathon.
|**Main Goal**| Help participants make their **first contributions** to FOSS projects, usually through coding or documentation. | Help participants make their **first contributions** to translations/localizations of FOSS documentation or websites. |
Copy file name to clipboardExpand all lines: index.qmd
+41-5Lines changed: 41 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,53 @@ toc: false
6
6
# Preface
7
7
:::
8
8
9
-
## **Community-Driven Open Source:<br>Enabling First-Time Contributors to Open Source Projects** {-}
9
+
Over the last decade, [rOpenSci](https://ropensci.org) has played a pivotal role in diversifying the open research software community by integrating new developers from underrepresented communities and enabling newcomers to become regular contributors to our federation of scientific software via various engagement channels.
10
+
In 2024 we piloted a new program to support first-time contributors to open source projects.
10
11
11
-
Over the last decade, [rOpenSci](https://ropensci.org) has played a pivotal role in diversifying the open research software community by integrating new developers from underrepresented communities and transforming newcomers into regular contributors to our federation of scientific software via various engagement channels.
12
+
**Making your first contribution to open source can be both empowering and yet very intimidating.**
12
13
13
-
To further this work, in 2024 we proposed to pilot a new program designed to support sustainability for scientific software packages by recruiting and mentoring contributors and co-maintainers, using community calls and coworking sessions (mini-hackathons and mini-translathons) to provide a structured yet flexible environment to onboard new participants to open-source projects in real-time.
14
+
Steinmacher et al.[^1] identified 13 social barriers preventing newcomers from making their first contributions to open source software projects, including barriers related to Reception, Communication, and Orientation. We consider that most of these barriers are, in one way or another, related to:
15
+
16
+
1. How easy it is to get set up to make a contribution
17
+
18
+
2. How easy it is to find a task to start with
19
+
20
+
3. How warmly first contribution is received
21
+
22
+
Therefore, to encourage and empower contributors, we created a new type of community event which supports specifically first-time contributors to open source software and translation projects.
23
+
Our goal was to create an inclusive and supportive environment, which would result in a positive learning experience and empower participants to continue contributing.
24
+
25
+
We designed and piloted this new community event format based on pairing
26
+
[community calls](https://ropensci.org/commcalls) to introduce the topics,
27
+
and specialized hands-on [coworking](https://ropensci.org/coworking) sessions (mini-translathons and mini-hackathons) to give opportunities for participation.
28
+
29
+
rOpenSci **Community Calls** are 1-hour online events with 2-5 speakers, 1 moderator, and include 20-40 minutes of discussion/Q&A.
30
+
These calls serve to strengthen connections between members of the rOpenSci community, teach technical and social topics, bring different stakeholders’ perspectives to light, and identify unmet needs on a topic.
31
+
Video, transcripts, notes and summaries of all our calls are published.
32
+
We have hosted over 40 calls over the last 10 years and attract a global audience with representation from academia, government, non-profit, and industry.
33
+
We have also started holding these events in Spanish (as of 2023) and Portuguese (as of 2024) to expand global accessibility.
34
+
35
+
**Coworking** sessions are informal, online, gatherings held once a month in rotating timezones.
36
+
Each session features a different theme and Community Host with expertise in that theme, facilitated by rOpenSci staff.
37
+
At these events, participants meet other scientific software developers and experts, cowork on their own projects, and/or ask questions and receive guidance as they work.
38
+
After each session we publish shared notes and resources.
39
+
We have hosted over 40 sessions since 2021.
40
+
41
+
This book presents the experiences and lessons learned through our [pilot events](pilot.html),
42
+
an [overview](event-overview.html) of how to run these kinds of events,
43
+
and specific details on how to run the [community calls](commcall.html),
44
+
[mini-translathons](translathon.html), and [mini-hackathons](hackathon.html).
45
+
In the Appendices we share examples and templates useful for running these events.
14
46
15
-
This book presents the lessons learned and the organization details of these events.
16
47
While instructions and notes are presented within an rOpenSci context, we hope that they are clear enough
17
48
that they could be adapted as a model for use in other organizations.
18
-
The format has been designed to be scalable across our federation of scientific open source software and we hope will serve as a model for maintainers to replicate in recruiting contributors and co-maintainers.
49
+
The format has been designed to be scalable across our federation of scientific open source software and serves as a model for maintainers to replicate in recruiting contributors and co-maintainers.
50
+
51
+
We hope this book will inspire and empower you to run your own events to support first-time contributors to open source software and translation projects.
52
+
53
+
[^1]: Igor Steinmacher, Tayana Conte, Marco Aurélio Gerosa, and David Redmiles. 2015. Social Barriers Faced by Newcomers Placing Their First Contribution in Open Source Software Projects. In Proceedings of the 18th ACM Conference on Computer Supported Cooperative Work & Social Computing (CSCW '15). Association for Computing Machinery, New York, NY, USA, 1379–1392. <https://doi.org/10.1145/2675133.2675215>
19
54
55
+
### Contributions to this book
20
56
If you find any errors or things that need clarification, we would be grateful if you opened an issue or pull request in the repository for this book.
21
57
22
58
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License.
0 commit comments