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
{{ message }}
This repository has been archived by the owner on Jan 10, 2020. It is now read-only.
Today @dshaw and I led the first meeting of a new group of enterprise Node.js adopters that is organizing with the specific purpose of providing feedback to the core project on the priorities, pain points, etc.
@dshaw will be working to get a draft charter together either as a part of the user-feedback initiative or as a separate WG under the @nodejs/community-committee.
The next meeting of this group shall be schedule for mid to late January.
The text was updated successfully, but these errors were encountered:
@dshaw I think the name advisory-group may end up being problematic because it assumes that this will be the only advisory group, which may be true, but very well may not. Can we go for a long and descriptive name instead: enterprise-advisory-group?
Today @dshaw and I led the first meeting of a new group of enterprise Node.js adopters that is organizing with the specific purpose of providing feedback to the core project on the priorities, pain points, etc.
The meeting minutes for this first meeting are captured here: https://docs.google.com/document/d/1DfqSNwmGtRUNDCn-a-UDlux02LDxkcDGfYXXOl-8PE0/edit
@dshaw will be working to get a draft charter together either as a part of the user-feedback initiative or as a separate WG under the @nodejs/community-committee.
The next meeting of this group shall be schedule for mid to late January.
The text was updated successfully, but these errors were encountered: