loopbackio / loopbackio/loopback-governance
LoopBack/OpenJS Foundation onboarding
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Originated from https://github.com/openjs-foundation/project-status/issues/79.
Since I don't have write access to that repo, it might be easier that the checklist is copied here and we can update the progress.
- Adopt the OpenJS Foundation Code of Conduct
- we adopted Contributor Covenant. Oustanding items:
- need a openjsf affiliated email address for reporting
- need to add CoC in all
loopbackiorepos. (See: https://github.com/loopbackio/loopback-governance/issues/17)
- we adopted Contributor Covenant. Oustanding items:
- Update project CoC reporting methods to include OpenJS Foundation escalation path
- same todos as above
- List official domains that the project commits to transfer to the OpenJS Foundation following graduation
- Identify and document other core project infrastructure
- see private repo https://github.com/loopbackio/project-contacts
- Adopt either the Contributor License Agreement (CLA) or the Developer Certificate of Origin (DCO)
- adopted CLA or DCO before joining OpenJS Foundation
-
Add or Update Governance.md document (required for Impact stage)- not applicable. We're in "at large" stage
- Confirm required files in place (CODE_OF_CONDUCT.md, LICENSE.md)
- CODE_OF_CONDUCT.md
- LICENSE.md
- Publish Project Charter on website or GitHub (see charter template) (See: https://github.com/loopbackio/loopback-governance/issues/22)
- PR in progress. There's also an existing governance page but not extensive as the project charter template.
- Update legal copyright notice on GitHub
- in progress.
- Add copyright notices for project website footers to project website openjs-foundation/project-status#86
- Add OpenJS Foundation logo to project website (See: https://github.com/openjs-foundation/artwork/pull/14)
- Add Project logo to OpenJS Foundation website
- Add Project to the CPC repo's README.md as an Incubating project
- List trademarks the project commits to transfer to the OpenJS Foundation following graduation
- If project is using crowdfunding platforms, add disclaimer to platforms - not applicable
- Identify individuals from the project to join the CPC
- Document project and foundation contacts for:
- marketing & social media (in private repo https://github.com/loopbackio/project-contacts)
- infrastructure (in private repo https://github.com/loopbackio/project-contacts)
- legal/governance help (in private repo https://github.com/loopbackio/project-contacts)
- Publish security policy (see PROJECT_SECURITY_REPORTING)
- have security reporting in loopback-next. Outstanding:
- Need an openjsf affiliated email address for reporting (Done:
security@loopback.io) - add the same reporting md to all repos in
loopbackioorg. https://github.com/loopbackio/loopback-governance/issues/24
- Need an openjsf affiliated email address for reporting (Done:
- have security reporting in loopback-next. Outstanding:
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
Review the remaining checklist items, especially the Project Charter linked to loopback-governance#22 and the legal copyright notice, alongside the existing pages/en/contrib/Governance.md and the linked charter template. Confirm which items are still outstanding and update the checklist when the charter, copyright notice, and other onboarding requirements are complete.
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
- 25/100