1
1
---
2
2
layout : single
3
3
title : " pyOpenSci beginner-friendly sprints at PyCon US 2024"
4
- excerpt : " pyOpenSci holds beginner-friendly sprints with the goal of making new contributors feel welcome. Learn about our last sprint at PyCon US 2024 and tips we use to make sprints accessible to more people."
4
+ excerpt : " pyOpenSci holds beginner-friendly sprints with the goal of making new contributors feel welcome. Learn about our latest sprint at PyCon US 2024, and tips we use to make sprints accessible to more people."
5
5
author : " Leah Wasser"
6
6
permalink : /blog/pyopensci-pyconus-2024-sprints.html
7
7
header :
@@ -24,7 +24,7 @@ In previous posts, I talked about:
24
24
within the scientific Python community] ( python-packaging-friends-dont-let-friends-package-alone.html ) .
25
25
26
26
Here, I will share with you what we have learned at pyOpenSci through holding
27
- beginner-friendly sprints over the past 2 years.
27
+ beginner-friendly sprints over the past two years.
28
28
Specifically, I want to
29
29
explore the varied motivations and barriers associated with contributions to
30
30
Open Source, and how pyOpenSci is addressing them.
@@ -38,19 +38,19 @@ Open Source, and how pyOpenSci is addressing them.
38
38
* By setting up infrastructure such as project boards and tagging issues as beginner-
39
39
friendly, you are on your way towards a beginner-friendly sprint.
40
40
* Be prepared to support people who are newer to Git and GitHub.
41
- * Create opportunities for beginners to contribute to documentation. The beginner lense
41
+ * Create opportunities for beginners to contribute to documentation. The beginner lens
42
42
reviewing your docs is critical to
43
43
ensuring the documentation is usable! Documentation contributions can also be
44
- implemented completely on GitHub without needing to use the command line.
44
+ implemented entirely on GitHub without needing to use the command line.
45
45
</div >
46
46
47
- ## pyOpenSci's PyCon US 2024 Sprint
47
+ ## pyOpenSci's [ PyCon US 2024] ( https://us.pycon.org/2024/ ) Sprint
48
48
49
- I've been running pyOpenSci sprints for about 2 years now. This year was my second year
50
- leading a PyCon US sprint for pyOpenSci. I've learned a lot! While last year we had 2
49
+ I've been running pyOpenSci sprints for about two years now. This year was my second year
50
+ leading a PyCon US sprint for pyOpenSci. I've learned a lot! While last year we had two
51
51
sprinters, this year we had a tremendous turnout of 18 people from several countries
52
52
and across the United States for our 1-day sprint. This resulted in over 35 issues and
53
- pull requests where volunteers helped fix issues on our website, in our tutorials, and
53
+ pull requests, where volunteers helped fix issues on our website, in our tutorials, and
54
54
in our packaging and peer review guidebooks. Many long-standing issues and bugs were
55
55
fixed thanks to this wonderful Python community.
56
56
@@ -65,13 +65,13 @@ that we've learned at pyOpenSci about running beginner-friendly sprints.
65
65
66
66
If you haven’t been to a sprint before, it’s an experience every open source
67
67
enthusiast should have. Sprints are where people come together to work on a
68
- project. The word sprint can be used in a professional development setting. This might describe a team of developers working
68
+ project. The word sprint can also be used in a professional development setting. This might describe a team of developers working
69
69
together to release a new feature. For the volunteer open source community, sprints often mean volunteers
70
70
helping maintainers work on various parts of a project. And it's important to keep in mind that often the maintainers are
71
- also volunteers.
71
+ also volunteers themselves .
72
72
73
73
### What do people sprint on for pyOpenSci?
74
- pyOpenSci is a non profit organization that is devoted to building diverse and
74
+ pyOpenSci is a nonprofit organization that is devoted to building diverse and
75
75
inclusive community that supports making science more open and collaborative.
76
76
Among other things that we do, we run [ open peer review of scientific Python software] ( /about-peer-review/index.html ) .
77
77
@@ -81,8 +81,8 @@ community driven beginner-friendly
81
81
[ Python packaging resources] ( https://www.pyopensci.org/python-package-guide/ ) and
82
82
[ tutorials] ( https://www.pyopensci.org/python-package-guide/tutorials/intro.html ) .
83
83
High quality learning resources also require maintenance and review.
84
- As such we always need a mixture of packaging experts and those newer to packaging
85
- to catch errors and points of confusion.
84
+ As such, we always need a mixture of packaging experts and those newer to packaging
85
+ to help catch errors and identify points of confusion.
86
86
87
87
As the Executive Director and Founder of pyOpenSci, I created most of our
88
88
pyOpenSci GitHub infrastructure to support our mission. While I cherish times
@@ -94,7 +94,7 @@ big and small. These contributions propel the pyOpenSci mission of making scienc
94
94
more open and collaborative forward.
95
95
96
96
97
- ## Barriers to contribute to open source
97
+ ## Barriers in contributing to open source
98
98
99
99
While sprints are a great way to engage the community in
100
100
supporting an organization's (or a project's) mission, there are many barriers for contributors to consider.
0 commit comments