Next steps from Advocacy Deep dive
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 550
- Forks
- 31
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 1
Description
-
Ambassador program
- set parameters and then trust them by promoting their content
- Need a champion
- Need to set up rewards
- find the good way to nominate people
- first batch from invite only
- use next meeting to doc 0.1
- Jean/Marco to lead discussion at collaborator summit
-
Messaging around the governance of the project Scope etc.
-
Corporate Node.js usage stories/studies
- 1/month
- Help identify people
- Have blog post from people
- Maybe some from collaborators
- Have some with companies, all on github: issue to validate the extract then PR
Contributor guide
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 by reviewing the issue's three discussion areas: the ambassador program, governance messaging, and corporate Node.js usage stories. No files, tests, entry points, or concrete acceptance criteria are named, so the scope and definition of done would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100