-
Notifications
You must be signed in to change notification settings - Fork 482
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
Umbrella issue: open-source ready #433
Comments
One other thing - badges - seems to be a generally accepted thing to do. Thoughts? |
For the What do we want for branch protection -- currently needs 1 approval and green tests for merge. I guessing we should also make sure that only certain project owners can push the go ahead for a merge? |
I suggest this add/edit
If we require a CHANGELOG.md, it would be less work on us if it be automatically generated as part of the release process by filling in the names of all the commits since the last release, there must be some tool to do that (I have an old one I wrote that does that if needs be). We can always edit it by hand afterward if we like. github pages are pretty good, but I do like ReadTheDocs, if only to avoid the monoculture. Badges are great, everybody likes them, they give you a quick information at a glance. Can't believe I didn't think of that. :-P |
CI business covered by #388 |
Closing as we have now released. |
Here are a bunch of outstanding tasks that we need to do to align with common OSS ways of working:
CONTRIBUTING.md
and consolidate all READMEs (egrequirements/README.md
) herepyproject.toml
.gitattributes
to manage our use of Jupyter notebookswindows-latest
#458)Consider use of GitHub packages for CI artifacts (Docker image?)Not doing, see Umbrella issue: improving the health of our test suite #388README.md
coverage
publicly visiblepyproject.toml
)Addwe will not add this - see Add Changelog action #472CHANGELOG.md
(or something equivalent)The text was updated successfully, but these errors were encountered: