nodejs / nodejs/package-maintenance
Engaging Enterprise teams to better understand challenges at scale
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Background
As part of the @nodejs/user-feedback Initiative, we've kicked off a work stream to better engage with large Enterprise teams, with the goal to enable a two-way channel of value-sharing and feedback between large corporations and the node community.
The value of engaging is to capture the context of large teams in large organizations (200+ devs, 1000+ applications) around slower operations, compliance demands, training and knowledge sharing, as well as varying levels of maturity of their technology practices.
A great recent examples such context: Security and Compliance needs in Enterprise as told by @isaacs OSS Risk & Compliance
The ask
Discuss how to best assist in bringing useful / actionable insights to the @nodejs/package-maintenance team.
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 entry points are named. Start by reviewing the issue background and the linked OSS Risk & Compliance post, then determine how enterprise feedback could produce useful, actionable insights for the package-maintenance team; done means an agreed engagement approach or concrete next steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100