Skip to content

Commit 57ff1c3

Browse files
lwasserlwasser
authored
Blog: New ed blog pyos updates sept 2022 (pyOpenSci#79)
Announcing the organization move and my being full time on pyOS!! yahoo!!
1 parent 66554c5 commit 57ff1c3

File tree

4 files changed

+135
-6
lines changed

4 files changed

+135
-6
lines changed

‎_pages/blog.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,14 @@
22
layout: archive
33
permalink: /blog/
44
title: "pyOpenSci Blog"
5+
excerpt: "Here we will both post updates about pyOpenSci and also highlight contributors. We will also highlight new packages that have been reviewed and accepted into the pyOpenSci ecosystem."
6+
header:
7+
overlay_color: "#666"
8+
overlay_filter: 0.6
59
author_profile: true
610
---
711

8-
## pyOpenSci Blog
12+
## Recent pyOpenSci Posts!
913

1014
{% comment %}
1115
{% include base_path %}

‎_posts/2019-10-25-welcome-to-pyopensci.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,12 @@ layout: single
33
title: "Welcome to the pyOpenSci Blog!"
44
excerpt: "pyOpenSci is a community organization devoted to the development of robust open source Python software to support science."
55
author: "Leah Wasser"
6+
permalink: blog/welcome-to-pyopensci/
7+
header:
8+
overlay_filter: 0.6
9+
overlay_color: "#333"
610
categories:
7-
- package-review
11+
- updates
812
---
913

1014
## Welcome To PyOpenSci!

‎_posts/2019-12-03-agu-2019-pyopensci-events.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ header:
88
overlay_color: "#333"
99
caption:
1010
categories:
11-
- events
11+
- updates
12+
- blog-post
1213
---
1314

1415

‎_posts/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md

Lines changed: 123 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,128 @@
11
---
22
layout: single
3-
title: "Big Changes for pyOpenSci - an update from the new executive director, leah wasser, what's next?"
3+
title: "Big Changes for pyOpenSci: an update from the new Executive Director, Leah Wasser, what's next?"
44
excerpt: "pyOpenSci has recently transitioned to a fiscal sponsor and has a new executive director - Leah Wasser. Learn more about our goals over the next few years and how to get involved with the community."
55
author: "Leah Wasser"
6+
permalink: /blog/new-executive-director-leah-wasser
7+
header:
8+
overlay_color: "#666"
9+
overlay_filter: 0.6
610
categories:
7-
- pyopensci-updates
8-
---
11+
- updates
12+
- blog-post
13+
---
14+
15+
16+
## pyOpenSci is now an independent community organization
17+
18+
I am thrilled to announce that pyOpenSci is now a fiscally sponsored project of
19+
[Community Initiatives](https://communityin.org/our-projects/support-a-project/)! This means that pyOpenSci now serves the community of
20+
scientific Python users and open source software maintainers. pyOpenSci is not
21+
affiliated with any specific organization. I (Leah) will now be devoting ALL of my
22+
(work :grin: ) time to the pyOpenSci project full time as the official Executive Director.
23+
24+
## pyOpenSci’s current funding and structure
25+
26+
I am grateful for two years of funding from the Sloan Foundation to
27+
support this effort. Once I acquire additional funding, I
28+
will be able to hire more staff to grow the organization. I am working with a
29+
board of two right now: Tracy Teal (chair) and Karen Cranston. They both bring
30+
tremendous experience building and supporting The Carpentries, among other
31+
efforts; Tracy and Karen will guide me in propelling pyOpenSci forward. I also am
32+
working with two incredible editors that have been crucial in supporting peer
33+
review: [David Nicholson](https://nicholdav.info/) and Ivan Ogasawara. In the upcoming months we will
34+
recruit more editors to support our open source software review process.
35+
Finally, I am also continuing to coordinate with and learn from the
36+
well-established and successful [rOpenSci](https://www.ropensci.org).
37+
rOpenSci has a strong precedent for open, community-driven peer review. Our
38+
community has a lot to learn from rOpenSci. I am grateful for their
39+
continued support.
40+
41+
## pyOpenSci is not just peer review of open source software
42+
Peer review is critical to the pyOpenSci mission. But I have pyOpenSci bigger
43+
and broader aspirations for pyOpenSci, too. There are several organizational
44+
goals supported by the Sloan Foundation grant that we will be working on over
45+
the next few years:
46+
* Create and grow a diverse and supportive community around a dynamic and
47+
open peer review process and Python open science skills. Diversity is important and we plan to bake diversity focused programs into all of pyOpenSci activities from the beginning.
48+
* Streamline and improve the quality of smaller Python Scientific Open Source software tools that support scientific workflows: think api wrappers, spatial data tools and domain specific tools rather than Numpy and Pandas.
49+
* We do this through peer review which not only assess code quality, testing infrastructure and CI setup. Our peer review also evaluates tool usability, documentation clarity and ensures alignment with community accepted standards for Python packaging.
50+
* One way our peer review process fosters usability of the tools is by ensuring documentation includes vignettes that showcase tool functionality and provide easy quickstarts for users.
51+
* Once tools are accepted into our ecosystem, we will track tool maintenance and find new maintainers, or support sunsetting as it makes sense to ensure users aren't left hanging.
52+
* Through peer review we will also address redundancy in tool functionality across the scientific Python ecosystem.
53+
* Create a model to support peer review within domain specific subcommunities. We will begin our work here with the Pangeo community. Here, we will support a peer review process with community-specific standards applied on top of ours to ensure tool consistency.
54+
* Provide training and mentorship in skills needed to contribute to open source. These skills are not just for open source. They are also fundamental to good open science practices and will support career trajectories in open science too.
55+
* Grow support for maintainers. A critical component of this effort will be a communication campaign around the importance of open source to science.
56+
57+
### We will also continue to curate our partnership with the Journal of Open Source Software (JOSS).
58+
Package maintainers can still submit a package to us if they wish to publish with
59+
JOSS. Our partnership supports a "fast track" review in JOSS if its functionality
60+
fits their scope and requirements. Once a package is accepted by pyOpenSci, if
61+
the package fits into the JOSS scope our review will be accepted by JOSS. A package
62+
author then only needs to write a paper for JOSS, and they will be "dual"
63+
published with us and JOSS. This, friends, is a win-win!
64+
65+
## Who does pyOpenSci serve?
66+
pyOpenSci supports software tools for open science and domain specific
67+
scientific projects. These tools and packages can act as glue that holds a
68+
research community together, but they haven't always received as much support
69+
as the foundational frameworks that are widely used (e.g. Pandas, numpy, scipy).
70+
We also support scientists using these tools and will empower folks like you
71+
with the skills needed to both contribute to Open Source and improve your open
72+
science workflows! In the long term these skills will be invaluable in your
73+
data intensive career trajectory!
74+
75+
## pyOpenSci is about collaboration - not reinventing the wheel
76+
Collaborations with existing efforts are critical. I welcome any feedback from
77+
you regarding groups that we should be engaging with! I will also need help
78+
finding reviewers and editors, mentors to support training efforts and voices to
79+
spread the word about the project.
80+
81+
## And… what's the timeline?
82+
Unless I figure out how to create numerous robot clones of myself, please know
83+
that all of the above won’t happen immediately. I am currently the sole
84+
employee of the organization and this is my second week. But never fear - we
85+
will accomplish a lot in the next two years and look forward to and will greatly
86+
value support from some of you along the way!
87+
88+
## Stay in touch!
89+
There are many ways to stay in touch with our project. Once I have a road map
90+
for activities developed, I will communicate this here on our
91+
[website](https://www.pyopensci.org/), [on Twitter](https://www.twitter.com/pyopensci)
92+
and [on discourse](https://pyopensci.discourse.group/).So be sure to
93+
follow [@pyOpenSci on Twitter](https://www.twitter.com/pyopensci) and sign
94+
up for Discourse!
95+
96+
## What can you do now?
97+
There are a few ways to get involved with us now.
98+
99+
1. [You can sign up to be a reviewer by filling out our reviewer form](https://forms.gle/B6zAukLCvJot5nws6). If you do this, we will reach out to you if a package is submitted that suits your background and interests!
100+
* We will also be growing our editorial board in the upcoming months. Once you have reviewed for us you are eligible to be considered as an editor. We will be posting more about this process in the upcoming months.
101+
1. Our open peer review process is running! If you have a package that you are working on, [you can submit it to our peer review process](https://github.com/pyOpenSci/software-review/issues).
102+
* You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/aims-and-scope.html).
103+
* If you have a package that you wish to submit but need some guidance, you can also submit a presubmission inquiry or a request for help here.
104+
2. You can [follow us on twitter](https://www.twitter.com/pyopensci) to keep tabs on our progress.
105+
106+
If you want to stay in touch with me, feel free to follow me on
107+
([twitter: @leahawasser](https://www.twitter.com/leahawasser)). Or connect with
108+
me on [GitHub](https://www.github.com/lwasser).
109+
110+
## pyOpenSci was built with support from numerous community members
111+
I would be remiss if I didn't take a moment to thank the huge suite of community
112+
members who participated in early meetings and discussions surrounding pyOpenSci.
113+
Please note that this list is not comprehensive and likely misses folks who
114+
attended discussions held at the SciPy Conference a few years prior to my involvement and those
115+
whose names I am missing on meeting notes. Feel free to reach out and ask for
116+
corrections as needed! Max Joseph, Jenny Palomino, Kylen Solvik, Chris Holdgraf,
117+
Paige Bailey, Luiz Irber,
118+
Arfon Smith, Leonardo Uieda, Filipe Fernandes, Carson Farmer, Neil Chue Hong,
119+
Joe Hamman, Ryan Abernathy, Lindsey Heagy, Mike Trizna, Noam Ross, Karthik Ram,
120+
Martin Skarzynski, Levi Wolf, Daniel Chen, Ivan Ogsawara, David Nicholson, Tania Allard,
121+
Kirstie Whitaker, Sander van Rijn, Philip Meier, Moritz Lurig ... and so many
122+
more!
123+
124+
I am so excited to be leading this effort and look forward to keeping in touch
125+
with everyone and supporting the community as pyOpenSci grows.
126+
127+
More to come... soon!
128+

0 commit comments

Comments
 (0)