04.16 News You Can Use & CPC Updates

Jory Burson

News You Can Use


 📚read any good books lately? would love some recommendations in Slack!

📆 Upcoming Events & Meeting Reminders

NEXT CPC MEETING: Tuesday, April 21 @ 4:00 PM UTC


NEXT STANDARDS WG MEETING: Tuesday, April 21 @ 6:00 PM UTC


OPEN OFFICE HOURS: Thursday, April 23 @ 5:00 PM UTC

PUBLIC BOARD MEETING: Friday, April 24 @ 6:00 PM UTC

Subscribe to our public calendar

📰 Announcements & FYIs

🎉 Congrats on the new release, jQuery! 10+ years strong, jQuery is still the most-used JavaScript library on the web. This week, the team announced the release of jQuery 3.5.0. Team Leads Timmy Willison and Dave Methvin keep it compatible and secure, and the web owes them a debt of gratitude - we're grateful for all the team's work and proud that jQuery is an Impact project at the OpenJS Foundation!

💬 Project News? Let us help get the word out! The Foundation marketing committee is eager to help projects spread the word about new releases, project plans, blog posts, meetings, or anything really. Join us in the #pr-marketing channel in Slack or reach out to Rachel or Jory!

📣 New voting CPC representatives announced: Congratulations to Chris Hiller (Mocha) and Tobie Langel (AMP), who have been elected voting members on behalf of Growth, At Large, and Incubating projects for this year. We're also grateful to Kris Borchers, Nick O'Leary, Anton Molleda, Eemeli Aro, and Chris Hiller for serving last year. You can see the complete list of voting members here.

🗺 OpenJS World & Collab Summit Updates: We plan to announce OpenJS World speaker selections next week, so be on the lookout for that. We've also been diligently working through a revised plan for the conference and hope to be able to communicate that soon. Please continue to check and let us know if you have any questions. The Collab Summit planning team is also working hard on a new plan and welcomes anyone who would like to participate!

📺 Catch our next AMA with Node-RED! Join us Wednesday, May 6 for the next AMA series with Node-RED. Use this form to ask a question, and then tune in on YouTube Wednesday at 16:00 UTC!

🗒 Meeting Notes & Recaps

Meeting Notes | Recording | GH issue

  • We started with issue #513, Updates to requirements of potential new Regular Members, which adds clarity to the Regular Member role & expectations. The goal of the revision is to make expectations and responsibilities more clear for potential CPC members. Joe has turned an ongoing discussion about this into a PR.
  • Issue #504, Voting Members chosen by Regular members, will be completed based on the timeline identified in the issue.
  • #502, add code of conduct and moderation information to, was closed after Brian showed that it was live and made a few tweaks.
  • #501, Self-managed maintainer directory + mailing lists on, had some discussion about public vs. private repos since the data included email addresses. The conclusion was to go the private repo route, and Tierney volunteered to work with Brian on some clever solutions for sharing the data securely.
  • Issue #488, Call for nominations for voting CPC reps, is closed pending the merge of PR #519, announcing that Chris Hiller and Tobie Langel have been elected to these posts. Congrats again!
  • Issue #474, OpenJS Collaboration Network, did not have any updates.
  • Issue #414 Add Foundation-wide copyright guidance, had a brief update and Tobie reported that he had some work to push this week.
  • PR #386 Add Post-Graduation Checklist has been approved by the Board and will land and close.
  • Issue #326 Responsible security disclosures did not get an update this week.
  • On issue #469, Populate the Code Of Conduct Panel, one of the questions that has continued to arise from projects seeking clarity is what the role of the panel is meant to be. Robin and Jory reported on the folks they had reached out directly to, and also on what the function of this panel is based on current understanding. Unfortunately we ran out of time before concluding this topic or being able to move on to the related issue, #503, How do we keep Code of Conduct up to date without upstreaming our modifications to it.
🔗 Handy-Dandy Links
twitter @openjsf
youtube OpenJSF YouTube Channel