-
Notifications
You must be signed in to change notification settings - Fork 18
Draft Blog post for Enterprise Focus Group #123
Comments
@ahmadnassri can we do a bullet point outline of what we want in this again? |
@ahmadnassri just wanted to followup on this. maybe @mhdawson remembers what exactly we want for this article. :) |
maybe this format will help: What is it? Who’s it for? (Intended audience): What’s the primary message you want that audience to come away with?: Summary of project (any more details on the above): |
hey @ahmadnassri any progress yet? :P |
@ladyleet what I remember is that it was to re-introduce the concept, talk about next steps/next meeting. |
@ladyleet updated with details. |
notes from today's meeting #131
|
thank you for this @ahmadnassri ! |
@ahmadnassri thoughts on this draft? feel free to edit or talk about what needs to be added, etc. https://docs.google.com/document/d/1TYaj3E-3ojHZ6IIWTzbgWYabDmQnK8EF6LvmKPn480c/edit |
Hi, are we sure we want this name "Node Enterprise Feedback Group" ? In my opinion we will create confusion with the current User Feedback. Why not only Node Enterprise, or Node Enterprise Advisory (the old name)? Thanks |
In terms of the name how about 'Enterprise User Feedback sub-group', with the sub-group being the signal that it's its part of the larger user feedback working group. |
Added some comments on the doc @ladyleet |
How about:
|
hey all! i put this through editing internally. check it out? |
Discuss the "Why" "What" & "How" for introducing the Enterprise context.
Outline
What is Enterprise Feedback Group
Who’s it for?
Primary Message
Summary of project
The growth and success of Node.js is in large part, due to the contribution of passionate individuals, as part of the daily efforts at work in large enterprise companies. Those businesses benefit from both the individual effort and the success of Node.js itself, a more engaged conversation with businesses themselves and the technology leaders of those business, will only result in further maximizing the ROI for their already deep investments in Node.js
using my own blurb here, from a panel on Open Source in Enterprise as reference for those key points:
The text was updated successfully, but these errors were encountered: