Skip to content

Commit fdba07a

Browse files
lwasserlwasser
authored
ENH: new blog post - pyOpenSci @ RSE23 BoF (#282)
* ENH: new blog on rse meeting draft * Enh: add RSE blog post
1 parent cf89643 commit fdba07a

9 files changed

+317
-0
lines changed

‎_drafts/2023-10-31-rse-2023-common-pyos-questions.md

+94
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
layout: single
3+
title: "Questions about pyOpenSci - RSE meeting 2023"
4+
excerpt: "Here you will find answers to two of the most common questions that people ask about pyOpenSci. These questions were asked at our birds of a feather session at the 2023 Research Software Engineer meeting."
5+
author: "Leah Wasser"
6+
permalink: /blog/common-pyOpenSci-questions-rse-2023.html
7+
header:
8+
overlay_color: "#666"
9+
overlay_filter: 0.6
10+
categories:
11+
- blog-post
12+
- community
13+
toc: true
14+
comments: true
15+
---
16+
17+
In [a previous post](/pyOpenSci-research-software-2023.html), I discussed some of the issues that Research Software Engineers
18+
(RSE) encounter in the Python packaging ecosystem. The issues were brought up
19+
in a Birds of a Feature community session that I lead at the RSE meeting in
20+
Chicago.
21+
22+
Here, i'll address the two most common questions that we get about
23+
pyOpenSci as asked in the RSE meeting.
24+
25+
## How is pyOpenSci different from JOSS?
26+
27+
One of the most common questions I get is:
28+
29+
> What is the difference between pyOpenSci and JOSS?
30+
31+
The short answer to this is that our organizations have different,
32+
but complementary goals. Hence our partnership.
33+
34+
JOSS's core goal is to provide the critical academic credit to software maintainers for developing tools. As such they are a publisher and publication is an end-point for a maintainer. Once a package is published in JOSS, it gains a CROSS-REF doi which is citable and attached to your ORCID-id.
35+
36+
pyOpenSci's core goal is to support maintainers through the process of both developing and maintaining software. We also care about long term maintenance of software. As such, once accepted into our ecosystem, pyOpenSci package maintainers become an integral part of our community. pyOpenSci will build relationships with them. And we will watch tools over time to ensure tools in our growing catalog are maintained over time.
37+
38+
If they become unmaintained we will either archive / sunset the project in our catalog and/or try to help find a new maintainer for the tool.
39+
40+
| pyOpenSci | JOSS |
41+
| ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
42+
| Is a diverse community focused on both running peer review, developing Python packaging guidelines and mentorship and training. | Is a organization with a community-driven review and publication process |
43+
| Cares about long-term maintenance of software and partners with JOSS for academic credit | Cares about academic credit for software and is a publication end-point |
44+
| Reviews software that drives open science- broad scope | reviews software that is explicitly determined to be "research". As such has a more narrow scope. |
45+
| Supports community-affiliated review | Has a fixed review process because it operates as a Journal publication |
46+
47+
The good news is that you don't have to chose between us!
48+
49+
### pyOpenSci-JOSS partnership for the win
50+
51+
<figure>
52+
<a href="/images/peer-review/peer-review-partners-process.png"><img src="/images/peer-review/peer-review-partners-process.png" alt="Image showing our peer review process.Broadly, there are 4 boxes at the top that show the process where first a maintaining submits a tool for review. then the package is reviewed by 2 reviewers. When a package is accepted, ie becomes a part of our ecosystem and then can move on to be published by JOSS if it is in scope for JOSS."></a>
53+
<figcaption>Through our partnership with JOSS you can be reviewed by pyOpenSci and then published by JOSS (if in scope) via our review. Thus if you are interested in both maintained, high quality Python software and also long term maintenance of tools, this partnership is for you!</figcaption>
54+
</figure>
55+
56+
Through our partnership with JOSS, a maintainer can both get
57+
support and contribute back to the growing pyOpenSci community. But they can also receive the software publication and associated academic credit that is so important.
58+
59+
In the above image you may notice that we also run a affiliated package partnership program. We get
60+
questions about that program often so i'll discuss that next.
61+
62+
## pyOpenSci's partnership program with domain-specific software communities
63+
64+
pyOpenSci runs an affiliated package [partnership program with domain specific Python communities](https://www.pyopensci.org/partners.html).
65+
66+
We have a partnership program where we add an additional layer to our review where through a single end-to-end review process, a package can become:
67+
68+
1. part of our ecosystem
69+
2. published by JOSS
70+
3. an affiliated package for pyOpenSci
71+
72+
Some of the communities that we are currently speaking with include:
73+
74+
- astropy
75+
- scverse
76+
- PyHeliophysics
77+
- Sunpy
78+
- plasmapy
79+
80+
<figure>
81+
<a href="/images/pyos-partnerships.png">
82+
<img src="/images/pyos-partnerships.png" alt="Image with text that reads - affiliated package partnerships. It then has logos of the astropy, scverse, PyHeliophysics, Sunpy and plasmapy communities. Below it says says your community here. ">
83+
</a>
84+
<figcaption>Add caption.
85+
</figcaption>
86+
</figure>
87+
88+
Questions we received around our partner community program
89+
90+
### Can a package that doesn't make the affiliated "standard" and is thus rejected from a partnership community or a package that doesn't want to go through JOSS< only pyOpenSci still become a part of the community?
91+
92+
The answer to that is YES and yes. just because a package is submitted to pyOpenSci doesn't mean you HAVE to move forward with a publication. Further if your tool doesn't make the affiliated package cut, you can still be accepted into the pyOpenSci ecosystem
93+
94+
in that regard it's a win-win situation for maintainers so submit to us regardless of their goals associated with JOSS or becoming an affiliated package with a partner community.

0 commit comments

Comments
 (0)