5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/172
More details: https://github.com/nodejs/summit/issues/172
- 6 participants
- 31 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/154
More details: https://github.com/nodejs/summit/issues/154
- 11 participants
- 27 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
Slides: https://docs.google.com/presentation/d/1SemAifhI1IloVJnR1gyuQZsB6A-nAME9_iC5qwgMHHc/edit?usp=sharing
Slides: https://docs.google.com/presentation/d/1SemAifhI1IloVJnR1gyuQZsB6A-nAME9_iC5qwgMHHc/edit?usp=sharing
- 9 participants
- 28 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/153
So far our user experience was partially meh, when it comes to deprecation warnings. We often struggle with deprecations due to our very heterogeneous users. There is often a gap in the requirements for e.g., CLI users, big companies that want the most reliable and safe way doing things, individuals who e.g., write a small script and so on. Most important though: we mainly reach the wrong people when printing our deprecation warnings. In general there are lots of pros and cons with deprecations.
That's why I would like to brainstorm what we could do to:
* reach the right people
* improve the average experience for all users
* still have a good way to improve the Node.js code base
So far I already thought about e.g., using a Node.js survey to gather further data and to figure out what our users actually believe and also about add an option to opt-into providing data when it comes to deprecations or other usage data.
This is very likely not an easy task and I ask not only Node.js collaborators to join but people who e.g., have run into deprecation warnings before, who found them distracting, great, weird and people who have e.g., strict requirements in companies. I believe we need a lot more feedback on this topic! If anyone has a lot of experience in this field, great, please join this session!
More details: https://github.com/nodejs/summit/issues/153
So far our user experience was partially meh, when it comes to deprecation warnings. We often struggle with deprecations due to our very heterogeneous users. There is often a gap in the requirements for e.g., CLI users, big companies that want the most reliable and safe way doing things, individuals who e.g., write a small script and so on. Most important though: we mainly reach the wrong people when printing our deprecation warnings. In general there are lots of pros and cons with deprecations.
That's why I would like to brainstorm what we could do to:
* reach the right people
* improve the average experience for all users
* still have a good way to improve the Node.js code base
So far I already thought about e.g., using a Node.js survey to gather further data and to figure out what our users actually believe and also about add an option to opt-into providing data when it comes to deprecations or other usage data.
This is very likely not an easy task and I ask not only Node.js collaborators to join but people who e.g., have run into deprecation warnings before, who found them distracting, great, weird and people who have e.g., strict requirements in companies. I believe we need a lot more feedback on this topic! If anyone has a lot of experience in this field, great, please join this session!
- 11 participants
- 1:01 hours
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/165
More details: https://github.com/nodejs/summit/issues/165
- 10 participants
- 47 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
MDN Web Docs and frameworks content — what makes sense in 2019?
MDN Web Docs and frameworks content — what makes sense in 2019?
- 6 participants
- 40 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/148
More details: https://github.com/nodejs/summit/issues/148
- 13 participants
- 47 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/161
In this session, we will be discussing Node.js Collection and our Social Media Presence.
There are many things which need feedback and new ideas on how we can improve our process.
* How can we improve our Node.js Collection review/publish process.
* How we drive Social Media Chair initiative.
* How we can improve diversity/inclusivity in the content we publish.
* Which kind of feedback we should get from users regularly.
* Creative ideas to increase engagement on social channels (use of ( video, live streams, etc).
.
.
and many more.
More details: https://github.com/nodejs/summit/issues/161
In this session, we will be discussing Node.js Collection and our Social Media Presence.
There are many things which need feedback and new ideas on how we can improve our process.
* How can we improve our Node.js Collection review/publish process.
* How we drive Social Media Chair initiative.
* How we can improve diversity/inclusivity in the content we publish.
* Which kind of feedback we should get from users regularly.
* Creative ideas to increase engagement on social channels (use of ( video, live streams, etc).
.
.
and many more.
- 7 participants
- 1:06 hours
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/openjs-foundation/cross-project-council/issues/125
Slides: https://docs.google.com/presentation/d/10yn888MFKFZDlPLKvNcCOTX0PiY1Vsp1P_AcLT6m5xk/edit?usp=sharing
More details: https://github.com/openjs-foundation/cross-project-council/issues/125
Slides: https://docs.google.com/presentation/d/10yn888MFKFZDlPLKvNcCOTX0PiY1Vsp1P_AcLT6m5xk/edit?usp=sharing
- 14 participants
- 45 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/144
More details: https://github.com/nodejs/summit/issues/144
- 3 participants
- 19 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/diagnostics/issues/295
More details: https://github.com/nodejs/diagnostics/issues/295
- 3 participants
- 43 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/155
More details: https://github.com/nodejs/summit/issues/155
- 7 participants
- 60 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/open-standards/issues/18#issuecomment-492309790
More details: https://github.com/nodejs/open-standards/issues/18#issuecomment-492309790
- 8 participants
- 43 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/website-redesign/issues/155
Level-setting
* Pace of progress picked up quickly, would be good to see if we’re still functioning well
* Recap of the process so far and future plans.
Introduction to the machine and improve onboarding docs
* Workshop to get new people on board. We're not teaching React/Gatsby. We're teaching people about how we implemented nodejs.dev
* In the process improve onboarding docs
* Nice to have: Get good first issues in the issue queue and use as walkthroughs
Collaboration
* with core docs contributors: How we want to tackle API docs
* with i18n: How to best consume localized API docs"
More details: https://github.com/nodejs/website-redesign/issues/155
Level-setting
* Pace of progress picked up quickly, would be good to see if we’re still functioning well
* Recap of the process so far and future plans.
Introduction to the machine and improve onboarding docs
* Workshop to get new people on board. We're not teaching React/Gatsby. We're teaching people about how we implemented nodejs.dev
* In the process improve onboarding docs
* Nice to have: Get good first issues in the issue queue and use as walkthroughs
Collaboration
* with core docs contributors: How we want to tackle API docs
* with i18n: How to best consume localized API docs"
- 3 participants
- 34 minutes
5 Jun 2019
OpenJS Foundation Collaborator Summit, Berlin, 2019
More details: https://github.com/nodejs/summit/issues/164
A breakout session for members of the i18n WG to cover how we can continue to push forward efforts like:
* l10n: CommComm Initiatives for internationalizing the API docs, and the website redesign project.
* Intl in Node.js: How the i18n WG can focus on supporting current Intl development in node core, and get more folks to help out with the core WG.
* The i18n WG's role in ECMA 402: How we can scale the i18n WG's involvement and support for tc39 in ECMA 402, and what the current needs are that Node.js representatives can fulfill for pushing JavaScript's Intl specification forward.
More details: https://github.com/nodejs/summit/issues/164
A breakout session for members of the i18n WG to cover how we can continue to push forward efforts like:
* l10n: CommComm Initiatives for internationalizing the API docs, and the website redesign project.
* Intl in Node.js: How the i18n WG can focus on supporting current Intl development in node core, and get more folks to help out with the core WG.
* The i18n WG's role in ECMA 402: How we can scale the i18n WG's involvement and support for tc39 in ECMA 402, and what the current needs are that Node.js representatives can fulfill for pushing JavaScript's Intl specification forward.
- 10 participants
- 1:02 hours
