my First PreSubmission Inquiry

[isabelizimm]

Version submitted:
Target repository:
Author handle:
Submitting Author: Name (@isabelizimm)
Package Name: mypackage
One-Line Description of Package: doing very cool things
Repository Link (if existing):
Editor-in-Chief: @isabelizimm

---

Code of Conduct & Commitment to Maintain Package

• I agree to abide by pyOpenSci's Code of Conduct 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.

Description

• Include a brief paragraph describing what your package does:

Community Partnerships

We partner with communities to support peer review with an additional layer of
checks that satisfy community requirements. If your package fits into an
existing community please check below:

• Pangeo
  • My package adheres to the Pangeo standards listed in the pyOpenSci peer review guidebook

Scope

• Please indicate which category or categories this package falls under:

Scope

• Please indicate which category or categories.
  Check out our package scope page to learn more about our
  scope. (If you are unsure of which category you fit, we suggest you make a pre-submission inquiry):

  • Data retrieval
  • Data extraction
  • Data processing/munging
  • Data deposition
  • Data validation and testing
  • Data visualization
  • Workflow automation
  • Citation management and bibliometrics
  • Scientific software wrappers
  • Database interoperability

Domain Specific & Community Partnerships

- [ ] Geospatial
- [ ] Education
- [ ] Pangeo
- [ ] Unsure/Other (explain below)

• Explain how and why the package falls under these categories (briefly, 1-2 sentences). Please note any areas you are unsure of:

• Who is the target audience and what are the scientific applications of this package?

• Are there other Python packages that accomplish similar things? If so, how does yours differ?

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

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

[pyosbot]

Hey @isabelizimm 👋 welcome to pyOpenSci’s scientific Python peer review process!

We’ve seen your message. Someone from our editorial team will get back to you within the next week about this submission.
In the meantime, feel free to check out our packaging guide or feel free to ask questions on our Discourse forum.

[pyosbot]

The submission template is missing the following values: version-submitted, target-repository, author-handle

[isabelizimm]

@pyosbot set @isabelizimm as eic

[pyosbot]

Done! eic is now @isabelizimm

[isabelizimm]

@pyosbot add @isabelizimm as editor

[pyosbot]

Assigned! @isabelizimm is now the editor

[isabelizimm]

^^^ i think it should not assign as an editor for pre-submissions?

[isabelizimm]

@pyosbot remove editor

[pyosbot]

Editor removed!

[isabelizimm]

^^ also an oops, no editors were ever assigned

[isabelizimm]

@pyosbot add @isabelizimm as eic

[pyosbot]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@pyosbot help

[isabelizimm]

okay, i dont think im going to remember the difference for add/set. maybe have both?

[isabelizimm]

@pyosbot add checklist for @isabelizimm

[pyosbot]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@pyosbot help

[isabelizimm]

@pyosbot help

[pyosbot]

Hello @isabelizimm, here are the things you can ask me to do:

# List all available commands
@pyosbot help

# Show our community Code of Conduct and Guidelines
@pyosbot code of conduct

# Allow editors to move the review to EiC checks
@pyosbot assign eic

# Post the editor response template
@pyosbot editor response

# Replies to package accepted
@pyosbot package accepted

# Get a list of all editors's GitHub handles
@pyosbot list editors

# Assign a user as the editor of this submission
@pyosbot assign @username as editor

# Remove the editor assigned to this submission
@pyosbot remove editor

# Add to this issue's reviewers list
@pyosbot add @reviewer-login as reviewer

# Remove from this issue's reviewers list
@pyosbot remove @reviewer-login from reviewers

# Label issue with: 2/seeking-reviewers. Remove labels: 1/editor-assigned
@pyosbot seeking reviewers

# Label issue with: 3/reviewer(s)-assigned. Remove labels: 1/editor-assigned, 2/seeking-reviewers
@pyosbot reviewers assigned

# Label issue with: 4/review-in-awaiting-changes. Remove labels: 1/editor-assigned, 2/seeking-reviewers, 3/reviewer(s)-assigned
@pyosbot reviews are in

# Label issue with: 5/awaiting-reviewer-response. Remove labels: 1/editor-assigned, 2/seeking-reviewers, 3/reviewer(s)-assigned, 4/review-in-awaiting-changes
@pyosbot author response complete

# Label issue with: 7/under-joss-review. Remove labels: 4/review-in-awaiting-changes
@pyosbot begin joss

# Label issue with: 9/joss-approved. Remove labels: 7/under-joss-review
@pyosbot joss approved

# Set a value for version
@pyosbot set v1.0.0 as version

# Set a value for archive
@pyosbot set 10.5281/zenodo.7158585 as archive

# Set a value for eic
@pyosbot set @username as eic

# Remind an author, a reviewer or the editor to return to a review after a 
# certain period of time (supported units days and weeks)
@pyosbot remind @reviewer in 2 weeks

# Perform checks on the repository
# Optionally, it can be run on a non-default branch 
@pyosbot check repository
@pyosbot check repository from branch custom-branch-name

[isabelizimm]

@pyosbot code of conduct
@pyosbot list editors

[pyosbot]

Here's the pyOpenSci Community Code of Conduct: https://www.pyopensci.org/governance/CODE_OF_CONDUCT

[isabelizimm]

what if its not the first part? @pyosbot code of conduct