This is a live document that will be constantly updated to match the proposed agenda.
A collaborator summit is a mix of presentations and interactive sessions lead by the Teams, Working Groups, and Projects that participate in the summit. For interactive sessions, our time is best served if a the team/working groups/project participate in good numbers (quorum etc).
We can change everything, so if you think a better structure will suit us better, let us know in #202, or just send a PR!
✨ We're excited for Node.js' 6th round of collaboration IRL! Even better, we're excited that folks from the JSF will be joining us for the first time! ✨
Attendees must register HERE
Montreal Convention Centre, Montreal, Palais des congrès de Montréal, Montréal, Canada
- Both Days: 1000 - 1800
Link to join slack: https://communityinviter.com/apps/js-foundation/join-openjs-foundation-on-slack . Once you join the OpenJS Foundation Slack Workspace, you can participate in any of the public channels. If you are new to Slack, you can view a full list of available channels by clicking the “Channels” link on the left.
We will have 3 room on both days. All three room will have Zoom Id to join remotely and hopefully, sessions will be recorded.
- Room 510AC : ~ 120 People
- Room 513EF : ~ 70 People
- Room 512DH : ~ 45 People
Please submit your feedback about what you liked and how can we improve it next time. Form Link
Time | Room 510AC | Room 513EF | Room 512DH |
---|---|---|---|
Zoom (ask any organizer for login credentials to start the zoom meeting) | https://zoom.us/j/173804425 | https://zoom.us/j/349852956 | https://zoom.us/j/680085630 |
1000 | Introduction | ||
1030 | Node.js Streams Promise Support 216 | Node.js Community Committee: OKR building 203 | Node.js Release working group 195 |
1130 | npm open rfc meeting 197 | Node.js Community Committee: OKR building 203 | I'm a lawyer in the Google Open Source Programs office AMA 220 |
1230 | 🍍 Lunch | ||
1330 | An Update on Unflagged ES Modules in Node.js 207 | Node.js Collection & Social Media 198 | Joint session Board, CPC, and community members 228 |
1430 | previous session continues | Roadshows and Events for OpenJS Projects 211 | previous session continues |
1530 | ☕️ coffee break | ||
1600 | QUIC In-Depth 185 | Node.js Community Committee: OKR building 203 | AMP Infrastructure Working Group 226 |
1630 | Marcomm Support: What's available and how to get plugged in: Getting projects connected to marketing resources from the Open JSF | previous session continues | |
1700 | Package Maintenance working group session 209 | previous session continues | Code Of Conduct |
1800 | END OF DAY 1 - Happy Hour Sponsored by Netflix - right outside of room 510 A and B |
To speak/present a topic/do a session, please open a issue in repo. Check #184 for more details.
Time | Room 510AC | Room 513EF |
---|---|---|
Zoom (ask any organizer for login credentials to start the zoom meeting) | https://zoom.us/j/173804425 | https://zoom.us/j/349852956 |
1000 | Making single-company projects more open 218 | CPC Breakout Sessions (TBD based on Friday's breakout planning) 199 |
1030 | previous session continues | |
1100 | Streams - Node.js 196 | previous session continues |
1130 | previous session continues | previous session continues |
1230 | 🍍 Lunch | |
1330 | Node.js diagnostics 206 | previous session continues |
1430 | Node.js Tooling Group Meeting 194 | |
1530 | ☕️ coffee break | |
1800 | ENDING NOTE |
To speak/present a topic/do a session, please open a issue in repo. Check #184 for more details.
The social media hashtag for OpenJS Collab Summit is #OpenJSCollabSummit
- Eva Howe (@evahowe)
- Jory (@jorydotcom)
- Tracy Lee (@ladyleet)
- Waleed Ashraf (@waleedashraf)
- Manil Chowdhury (@keywordnew)
Anyone can come, but we will not be explicitly on boarding at Collab Summit Montreal. Conversations can move fast as working groups have a lot of context. This instance does not include a morning of Code + Learn, the session that guides people through contributing to the project.
Working groups will put together a brief schedule so that people can familiarize themselves before folks get onsite, having the general collaborator discussions, and then dive into breakout sessions.
Attendees must register HERE
It would be fantastic if each one of the breakouts is facilitated by a person who will be responsible to "run" the breakout and do a quick presentation at the end. This person would also set outcomes from the breakout to optimally leverage our time together. There is a facilitator guide available here.
There are funds available for any Individual Member of the Node.js Foundation to receive travel funds to Collab Summit. Membership is free for active collaborators. Sign up HERE.
PLEASE follow the instructions for application to receive travel funds HERE.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members.
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to block temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at report@nodejs.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
To learn more about the process of how moderators enforce the Code of Conduct, review the Moderation Policy and Requesting Moderation.
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available HERE
Appendix A: The report@nodejs.org Alias
Note: At the current time, all email sent to the report@nodejs.org email alias is copied to all members of the Node.js Moderation Team.
✨ Super stoked to see everyone in December! ✨