-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated community documents #37
Conversation
Added pysat code of conduct.
Added guidelines for contributing to pysatMadrigal.
Added a zenodo json file.
Fixed bug when setting options in the setup.cfg file.
Added a pull request template.
Added issue templates for bugs, features, and questions.
Added a file manifest.
Removed unneeded line from the manifest.
Renamed testing requirements files to better describe their contents.
Updated travis to use requirements files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @aburrell. Looks good to me. I did raise a question for you to consider but I'll leave the outcome to you. Cheers.
- [ ] My changes generate no new warnings | ||
- [ ] I have added tests that prove my fix is effective or that my feature works | ||
- [ ] New and existing unit tests pass locally with my changes | ||
- [ ] Any dependent changes have been merged and published in downstream modules |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we still have a downstream check for a pysat* package?
Personally it seems to me that the check should be for upstream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, we can't break anything upstream, so I don't think we need a check there. While at the moment there isn't anything downstream from here, it's possible that analysis packages could rely on instrument methods in the future. So that is why I am keeping it here :)
Added missing community documents, addressing #2. Also added a .zenodo.json file, updated setup configuration and travis.yml to comply with up-to-date methods used in pysatSpaceWeather.