You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 @isaacsOSS Risk & Compliance
The ask
Discuss how to best assist in bringing useful / actionable insights to the @nodejs/package-maintenance team.
The text was updated successfully, but these errors were encountered:
I think one of the things we've discussed as well is how we help enterprises understand their dependencies on packages, motivate support for those packages and how we make it easy for them to work to help maintain those packages.
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.
The text was updated successfully, but these errors were encountered: