Skip to content
Open
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions .github/ISSUE_TEMPLATE/help-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ assignees: ''

## What is this?

To make the review process easier and to help you maintain your package, pyOpenSci requires testing, continuous integration, and full documentation for packages submitted for review (read more [here][PackagingGuide]. We want to make this as easy as possible for newcomers, so if you'd like some help in prepping your package you can submit this request and we'll assign someone to help you out!
To make the review process easier and to help you maintain your package, pyOpenSci requires testing, continuous integration, and full documentation for packages submitted for review (read more [in our Python packaging guide][PackagingGuide]. We want to make this as easy as possible for newcomers, so if you'd like some help in prepping your package you can submit this request and we'll assign someone to help you out!

Before submitting a request, check out our [Packaging Guide][PackagingGuide]. The answers to your questions might be there already.

Expand Down Expand Up @@ -54,11 +54,7 @@ Repository Link (if existing):
- Any other questions or issues we should be aware of?:


**P.S.** Have feedback/comments about our review process? Leave a comment [here][Comments]


[PackagingGuide]: https://www.pyopensci.org/python-package-guide/

[PackageCategories]: https://www.pyopensci.org/software-peer-review/about/package-scope.html

[Comments]: https://pyopensci.discourse.group/
17 changes: 11 additions & 6 deletions .github/ISSUE_TEMPLATE/presubmission-inquiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,17 @@ EiC: TBD
- [ ] I agree to abide by [pyOpenSci's Code of Conduct][PyOpenSciCodeOfConduct] during the review process and in maintaining my package after should it be accepted.
- [ ] I have read and will commit to package maintenance after the review as per the [pyOpenSci Policies Guidelines][Commitment].

## Development Best Practices & GenerativeAI Use Disclosure

- [ ] This package has a public development history spanning 3-6 months, with commits distributed over time that reflect **iterative, thoughtful development.**
- [ ] All code in this package has been **carefully reviewed by a human**. Its implementation is also understood by the authors submitting the package.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we shorten this? OR we can link to more about this. perhaps remove the translation piece

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd keep this as-is. There was a decent chunk of folks who didn't look at links present, this forces acknowledgement.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coatless Does Leah's version below look ok to you? Still includes the bit about communication written by human, but links to our peer-review guide for the translation details.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure; but, I'll revoice that the more links present across multiple guides the less likely the submitters are going to go to them. Again, these are built-in to the template meaning that unless they copy & paste the URL to visit or switch to preview mode and click it's highly unlikely that these documents will be reviewed.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). [See more](llms & translation)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to section in guide on translation and communication

- [ ] **Generative AI tools were used to develop and maintain this package.**

### Please list the tools and frameworks that you used below (Examples include Claude Code, Cursor, OpenClaw, ChatGPT, VSCode + Copilot)

### Describe the nature and scope of support that LLMs provided. Examples include code generation, autocomplete, documentation development, refactoring, test development

Comment thread
lwasser marked this conversation as resolved.
## Description

- Include a brief paragraph describing what your package does:
Expand Down Expand Up @@ -62,18 +73,12 @@ existing community please check below:

- Any other questions or issues we should be aware of:


**P.S.** Have feedback/comments about our review process? Leave a comment [here][Comments]


[PackageCategories]: https://www.pyopensci.org/software-peer-review/about/package-scope.html

[Conduct]: https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html

[Commitment]: https://www.pyopensci.org/software-peer-review/our-process/policies.html#after-acceptance-package-ownership-and-maintenance

[Comments]: https://pyopensci.discourse.group/

[PangeoCollaboration]: https://www.pyopensci.org/software-peer-review/partners/pangeo

[pangeoWebsite]: https://www.pangeo.io
Expand Down
15 changes: 11 additions & 4 deletions .github/ISSUE_TEMPLATE/submit-software-for-review.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,17 @@ Date accepted (month/day/year): TBD
- [ ] I agree to abide by [pyOpenSci's Code of Conduct][PyOpenSciCodeOfConduct] during the review process and in maintaining my package after should it be accepted.
- [ ] I have read and will commit to package maintenance after the review as per the [pyOpenSci Policies Guidelines][Commitment].

## Development Best Practices & GenerativeAI Use Disclosure

Comment thread
lwasser marked this conversation as resolved.
- [ ] This package has a public development history spanning 3-6 months, with commits distributed over time that reflect **iterative, thoughtful development.**
- [ ] All code in this package has been **carefully reviewed by a human**. Its implementation is also understood by the authors submitting the package.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). We embrace the use of LLMs for translation and grammar correction. We prefer honest interactions over ones that prioritize perfect language and grammar. As little aid from a LLM as possible.
- [ ] All communication on this issue will be written by a human (someone on your maintainer team). [Learn more]()

- [ ] **Generative AI tools were used to develop and maintain this package.**

### Please list the tools and frameworks that you used below (Examples include Claude Code, Cursor, OpenClaw, ChatGPT, VSCode + Copilot)

### Describe the nature and scope of support that LLMs provided. Examples include code generation, autocomplete, documentation development, refactoring, test development

## Description
Comment thread
lwasser marked this conversation as resolved.

- Include a brief paragraph describing what your package does:
Expand Down Expand Up @@ -117,8 +128,6 @@ Confirm each of the following by checking the box.
submission and improve our peer review process. We will also ask our reviewers
and editors to fill this out.

**P.S.** Have feedback/comments about our review process? Leave a comment [here][Comments]

## Editor and Review Templates

The [editor template can be found here][Editor Template].
Expand All @@ -143,8 +152,6 @@ The [review template can be found here][Review Template].

[Review Template]: https://www.pyopensci.org/software-peer-review/appendices/templates.html#peer-review-template

[Comments]: https://pyopensci.discourse.group/

[PangeoCollaboration]: https://www.pyopensci.org/software-peer-review/partners/pangeo

[pangeoWebsite]: https://www.pangeo.io
Expand Down
8 changes: 2 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,10 @@ Over time we also hope to address the issue of multiple packages that have overl
## How to submit a package for review

To submit your package for peer review, you can open a GitHub issue:

1. [Click here to start a presubmission inquiry - if you are unsure of whether your package is in scope for us you may want to click here to open an issue.](https://github.com/pyOpenSci/software-review/issues/new?assignees=&labels=0%2Fpresubmission&template=presubmission-inquiry.md&title=)
2. [Click here to submit your package for peer review.](https://github.com/pyOpenSci/software-review/issues/new?assignees=&labels=1%2Feditor-checks%2C+New+Submission%21&template=submit-software-for-review.md&title=)


## Why submit a package to pyOpenSci?
There are [numerous benefits to submitting your package to us for review](https://www.pyopensci.org/peer-review-guide/about-peer-review/review-benefits.html?highlight=benefits)including:

Expand Down Expand Up @@ -49,10 +49,6 @@ Peer review is a valuable way to boost your data science skills. If you are inte
* 📖 [What are the benefits of peer review?](https://www.pyopensci.org/peer-review-guide/about-peer-review/review-benefits.html)
* 📖 [Why is software peer review important](https://www.pyopensci.org/peer-review-guide/about-peer-review/intro.html#why-does-the-scientific-community-need-software-peer-review)


## Need help? Have questions?
If you need help with Python packaging, have questions about our review process, or just want to reach out, we encourage you to [post on our discourse forum](https://pyopensci.discourse.group/c/coding-help/10). We love to hear from the community.

## 👥 Our community 👥
Our community is growing.

Expand All @@ -63,7 +59,7 @@ Our community is growing.

## Contributors ✨

Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key/)):

<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore-start -->
Expand Down