GitHub Maintainer Feedback Group
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
👋
GitHub is in the process of putting together a new OS Maintainer Feedback Group. We are asking a few different OS projects, of a variety of scales and types, to each pick two representatives for a one year "term".
During this year, we will hold regular calls, collect feedback, report on progress, and hopefully send a lot of swag. We will also be exploring hosting "soft skills" workshops online that any member of these projects can attend, and looking into other things that help maintainers beyond improvements of GitHub products, depending on the feedback of this group. The overall commitment shouldn't be more than an hour or so a month, and we hope that together we can greatly improve the lives of Maintainers.
Could you help us find 2 folks on the Node project who can make the 1 year commitment to working with us?
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
No files, tests, or code entry points are mentioned. Read the issue body and assess whether the Node project can nominate two representatives for GitHub's one-year Maintainer Feedback Group commitment; done means identifying and confirming two participants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100