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
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
29
29
excerpt: "Software peer review, similar to the review of scientific papers, is a process where scientists vet software code, documentation and infrastructure. pyOpenSci leads an [open peer review process](https://www.pyopensci.org/software-peer-review/our-process/how-review-works.html) run by a community of dedicated volunteers. Reviews are supportive and fully transparent with the shared goal of improving the quality, usability and maintainability of the software that is driving open science.
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
38
38
excerpt: "Our partnership with JOSS means that you don't have to choose between pyOpenSci and JOSS. Simply submit your package to pyOS for review. If your package is accepted and in scope for JOSS, it will be fast-tracked through JOSS' review process. "
alt: "Light purple image that says software Peer Review. On the image is a woman at a laptop with a pyOpenSci logo on it and a cup of coffee next to her. There is a very light flower in the bottom right hand corner. "
22
22
title: "We Run Software Peer Review"
23
23
excerpt: "We review Python packages and software with the goal of helping scientists build better, discoverable and usable software. <br><br>
@@ -27,7 +27,7 @@ peer-review:
27
27
<i class='fa-solid fa-check-double'></i> Submit a package today for review today. <br>
28
28
<i class='fa-solid fa-check-double'></i> Apply to become a reviewer. <br>
alt: "Light purple image with a bunch from different backgrounds of stick figure people in a slightly darker color. The text on the image at the top says Community Partnerships"
title: "We Break Down Python Packaging Painpoints"
43
43
alt: Light purple image that says python packaging guide and below it says simplifying python packaging. The background is a grey laptop with a hand looking down at the laptop the above.
alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
12
12
excerpt: "Our catalog of vetted open source tools makes it easier for scientists to find the trusted tools that they need to develop their open science workflows."
13
13
title: "Help scientists find the open science tools that they need"
@@ -17,9 +17,9 @@ scientists:
17
17
overview:
18
18
- excerpt: "pyOpenSci creates resources to help you navigate the Python packaging ecosystem with ease. Our materials are community developed and go through extensive technical and pedagogical review."
alt: "An image showing a bunch of hands holding up a sign that says Community Developed. the background is dark purple with a few green decorative items."
22
-
title: "Our development process: Community-developed Python tutorials for scientists"
alt: "A graphic with a light yellow background that says essential collaboration skills for scientists - using GitHub. On the right there is a man and a woman sitting at a tall table with laptops working."
33
33
excerpt: "Through the [Better Software for Science Fellowship](https://bssw.io/pages/bssw-fellowship-program) we will be developing lessons focused on teaching core GitHub collaboration skills needed for both contributing to open source software and for working in an open science team environment.
Copy file name to clipboardExpand all lines: _posts/2025-03-05-pyOpenSci-first-open-science-festival.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,8 +73,10 @@ Using the interactive platform SpatialChat rather than a traditional online plat
73
73
We kicked the event off on Monday, October 28, with a morning of KeyNote talks headlined by **Eric Ma, Melissa Mendonça, and Rowan Cockett**. The Monday talks aligned perfectly with the training events held Tuesday through Friday. The talks set the stage for a truly engaging week of learning together.
<img src="{{ post.url | relative_url }}/images/python-packaging/github-action-environment-pypi.png" alt="Screenshot of the GitHub settings interface showing the ‘Environments’ section with configuration options for ‘pypi.’ The ‘Deployment protection rules’ section is visible, with ‘Required reviewers’ enabled and two reviewers listed: ‘lwasser’ and ‘willingc.’ Other options such as ‘Prevent self-review’ and ‘Wait timer’ are present but not enabled.">
110
+
</picture>
109
111
<figcaption>
110
112
GitHub environment settings for “pypi,” displaying deployment protection rules with required reviewers configured for workflow approvals.
111
113
</figcaption>
@@ -123,8 +125,10 @@ A Trusted Publisher setup creates a secure link between PyPI and your repository
123
125
Using a Trusted Publisher combined with a locked-down environment eliminates the need to store sensitive tokens as GitHub secrets. It also removes the need to refresh and update tokens periodically to avoid token leaks or theft issues.
<img src="{{ post.url | relative_url }}/images/python-packaging/trusted-publisher-pypi-github.png" alt="A workflow diagram showing GitHub Actions building distribution files (sdist and wheel), publishing them securely to PyPI, represented as a warehouse. The diagram includes a lock icon emphasizing security, with the pyOpenSci logo in the top-left corner.">
131
+
</picture>
128
132
<figcaption>
129
133
Example of the PyPI Trusted Publisher form, used to securely link a GitHub repository with PyPI for publishing Python packages. Trusted Publisher reduces the risk of token theft and improves overall security.
0 commit comments