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
Following up on the first tooling user feedback session, we want to gather points of discussion for future sessions.
From #38, these were the original questions from the first session:
Describe how your Tooling leverages Node.js.
Why do you use Node.js for Tooling?
What's working in the Node.js tooling ecosystem?
What isn't working in the Node.js tooling ecosystem?
What's new that could impact Node.js?
We didn't have enough time to cover everything we wanted to--and give everyone a chance to speak--so future sessions should be more limited in scope.
I'll use this issue to gather ideas, and distill them into a "living document" of sorts (a Markdown document, living in this repo) to be used going forward.
cc @dshaw@bnb to confirm I understood this correctly. 😄
ALSO, PLEASE UNDERSTAND: This issue isn't a platform for discussion; we're just making a rough list of topics to discuss.
Following up on the first tooling user feedback session, we want to gather points of discussion for future sessions.
From #38, these were the original questions from the first session:
We didn't have enough time to cover everything we wanted to--and give everyone a chance to speak--so future sessions should be more limited in scope.
I'll use this issue to gather ideas, and distill them into a "living document" of sorts (a Markdown document, living in this repo) to be used going forward.
cc @dshaw @bnb to confirm I understood this correctly. 😄
ALSO, PLEASE UNDERSTAND: This issue isn't a platform for discussion; we're just making a rough list of topics to discuss.