Skip to content
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

Closed
11 of 13 tasks
nenb opened this issue Jul 14, 2023 · 5 comments
Closed
11 of 13 tasks

Umbrella issue: open-source ready #433

nenb opened this issue Jul 14, 2023 · 5 comments
Assignees
Labels

Comments

@nenb
Copy link
Contributor

nenb commented Jul 14, 2023

Here are a bunch of outstanding tasks that we need to do to align with common OSS ways of working:

  • Add CONTRIBUTING.md and consolidate all READMEs (eg requirements/README.md) here
  • Fix licence in pyproject.toml
  • Update branch protections and repository settings
  • Add .gitattributes to manage our use of Jupyter notebooks
  • Extend CI to all common platforms (partially complete, see Expand CI to Include windows-latest #458)
  • Consider use of GitHub packages for CI artifacts (Docker image?) Not doing, see Umbrella issue: improving the health of our test suite #388
  • Update landing page README.md
  • Clarify our versioning policy
  • Add build and release to CI (this can be separate to PyPI upload, it tags the release on GitHub)
  • Clarify where we will host our docs. If using ReadTheDocs, complete necessary configuration
  • Make coverage publicly visible
  • Determine project keywords (relevant for repo and for pyproject.toml)
  • Add CHANGELOG.md (or something equivalent) we will not add this - see Add Changelog action #472
@nenb nenb self-assigned this Jul 14, 2023
@blythed
Copy link
Collaborator

blythed commented Jul 14, 2023

One other thing - badges - seems to be a generally accepted thing to do. Thoughts?

@blythed
Copy link
Collaborator

blythed commented Jul 14, 2023

For the CONTRIBUTING.md I started using the inbuilt wiki functionality. I'm guessing the CONTRIBUTING.md is standard though?

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?

@rec
Copy link
Contributor

rec commented Jul 14, 2023

I suggest this add/edit

  • Create a list of supported platforms and minimum specs
  • Extend CI to all supported platforms

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

@blythed
Copy link
Collaborator

blythed commented Jul 14, 2023

CI business covered by #388

@nenb
Copy link
Contributor Author

nenb commented Aug 3, 2023

Closing as we have now released.

@nenb nenb closed this as completed Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants