workshopper / workshopper/javascripting
Lead Maintainers wanted
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.9k
- Forks
- 1k
- Avg merge
- 14h 47m
- Merged PRs (30d)
- 1
Description
Moving the workshoppers under the workshopper org umbrella means that there is no longer a signal of who the implicit "lead maintainer" (i.e., the original author) is. I'd love to have a small group of people who are invested in the future of javascripting to volunteer to join a javascripting lead maintainers team. We'll make a GitHub team to list the volunteers.
@sethvincent, as the original author, would you like to continue in this role?
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 with the issue's request and its maintainer question; no source file or test is identified. Done means volunteers are confirmed and a GitHub javascripting lead maintainers team is created and listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100