Search results

ADD DOCUMENTATION AROUND HOW TO ARCHIVE A PACKAGE

Status: Open.

#306 In pyOpenSci/software-peer-review;

· lwasser opened on Dec 18, 2024

chore: troubleshoot htmlproofer failures

infrastructure

Status: Open.

#304 In pyOpenSci/software-peer-review;

· willingc opened on Nov 14, 2024

fix: update text around our on-hold process for packages where a maintainer hasn't responded in a period of time

Status: Open.

#299 In pyOpenSci/software-peer-review;

· lwasser opened on Oct 2, 2024

Bad link: 2i2c cloud native formats link

Status: Open.

#298 In pyOpenSci/software-peer-review;

· lwasser opened on Jul 22, 2024

Add wording for adding, removing labels for package issues

Status: Open.

#295 In pyOpenSci/software-peer-review;

· yeelauren opened on Jun 28, 2024

We need more clear language around author submission and adding new features

Status: Open.

#291 In pyOpenSci/software-peer-review;

· lwasser opened on Jun 13, 2024

Add instruction on when to add org label

Status: Open.

#289 In pyOpenSci/software-peer-review;

· pllim opened on May 23, 2024

Update web page after Astropy APE

Status: Open.

#268 In pyOpenSci/software-peer-review;

· willingc opened on Dec 15, 2023

Notes from an editor dogfooding a review

enhancementNew feature or requestNew feature or request

review-process-update

Status: Open.

#267 In pyOpenSci/software-peer-review;

· sneakers-the-rat opened on Dec 14, 2023

Need system for volunteering to review and tracking reviewers in pool like JOSS

Status: Open.

#265 In pyOpenSci/software-peer-review;

· sneakers-the-rat opened on Dec 5, 2023

Add language in the editor guide about finding reviewers - 1 domain 1 can be usability etc

Status: Open.

#260 In pyOpenSci/software-peer-review;

· lwasser opened on Nov 8, 2023

Add comment about organization-wide CoC / contributing to EiC checklist

Status: Open.

#259 In pyOpenSci/software-peer-review;

· NickleDave opened on Nov 3, 2023