leap-stc / leap-stc/leap-stc.github.io
Add whats new section?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I am thinking of doing a regular slack post of what is new with LEAP-Pangeo and I think it would be nice to keep a changelog here too.
We could either do that as sort of release notes (more automatic but hidden on the gh page) or as an actual page on the docs (more manual labor but would be more visible?).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
First confirm with maintainers whether the changelog should be GitHub release notes or a page in the documentation, and define who will maintain it and how often it should be updated. The issue names no files, tests, or documentation entry point, so completion criteria need to be agreed before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100