loopbackio / loopbackio/loopback-governance
Create a project charter
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the closest thing we have to a Project Charter is the [loopback.io governance page](https://github.com/loopbackio/loopback.io/blob/726641e87455e8632131567fb178528e85e91cd8/pages/en/contrib/Governance.md), of which is outdated.
As part of the [OpenJS Foundation (OpenJSF) onboarding requirements](https://github.com/loopbackio/loopback-governance/issues/16), we need to create a Project Charter, typically based on the [template provided by OpenJSF](https://github.com/openjs-foundation/cross-project-council/blob/8874993a95ab9511efb43e4eb61b71485db6ce19/PROJECT_CHARTER_TEMPLATE.md).
- [ ] Create a canonical Project Charter document in this Git repository
- [ ] Update existing docs with overlapping information to point to the aforementioned canonical Project Charter document
- [ ] [loopback.io governance page](https://github.com/loopbackio/loopback.io/blob/726641e87455e8632131567fb178528e85e91cd8/pages/en/contrib/Governance.md)
- [ ] [`loopback-next` readme team section](https://github.com/loopbackio/loopback-next/blob/9c6c674fe5e9953978a942139d8d052b2e11b86e/README.md#team)
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
Start with the OpenJSF PROJECT_CHARTER_TEMPLATE.md and compare it with the existing loopback.io Governance.md page. Create the canonical Project Charter in this repository, then update the loopback.io governance page and the loopback-next README team section to point to it. Done means all listed checklist items are complete and overlapping information directs readers to the canonical document.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100