loopbackio / loopbackio/loopback-governance
Process related discussions - 1H 2022
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Some initiatives that were brought up during the maintainers' call. Trying to capture here and hopefully we can make some progress this year:
- [ ] Enable FOSSA license scanning - proposed by @achrinza
- status: needs review and vote from TSC, see #12 . Action taker: @dhmlau @raymondfeng @marioestradarosa
- [x] OpenJS Foundation onboarding
- status: needs to follow up on the email addresses for security reporting - Action taker: @dhmlau
- [x] User reference process documentation and improvement
- status: will work towards getting PR #14 landed.
- [x] Copy blog posts from strongloop.com to loopback.io
- status: ? . Action taker: @hacksparrow
- [ ] community call vs maintainers call?
- whether we want to open up the maintainers call to the wider community, or have a separate call with the community?
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 open checklist items, especially the FOSSA proposal and maintainers-call question, and review #12 plus PR #14 for context. Done means the remaining initiatives have recorded decisions and updated statuses; this issue is not a focused code task.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100