Topics

02.19 News You Can Use & CPC Updates


Jory Burson
 

 
 
 
 
 
News You Can Use
 
 
 
 
 
 
 
 
 

Greetings, my funny valentines... hope you are all having an amazing week! <3 jory

📆 Upcoming Events & Meeting Reminders

NEXT CPC MEETING: Tuesday, February 25th @ 5:00 PM UTC

NEXT COLLAB SUMMIT PLANNING MEETING: Tuesday, February 25th @ 6:00 PM UTC

NEXT STANDARDS WG MEETING: Tuesday, February 25th @ 7:00 PM UTC

OPEN OFFICE HOURS: Thursday, February 27th @ 7:00 PM UTC

Subscribe to our public calendar

📰 Announcements & FYIs

The OpenJS World CFP Closes Friday, 2/21!. As a reminder, the event is June 23-24th in Austin, Texas, and you are highly encouraged to submit a talk. Event registration opens Friday.

Collab Summit Updates - We're actively planning OpenJS Collab Summit, an event immediately following OpenJS World for project maintainers and contributors. Get involved on the /summit repo, in #collabsummit on Slack, or by following up with me directly. Next Up: Planning the program!

New: OpenJS Office Hours -Joe Sepi, our CPC director, is trialing office hours to support open source contributors who may be interested in getting involved with foundation projects. The goal for these sessions is to orient people, intro them to the communities, and draw in a diverse group of open source javascript enthusiasts. Tell your friends, or join him on Thursday, 2.27!

New Slack Channels: #cross-project-council-github & #npm If you find it hard to keep up with the comments, PRs and goings on in the CPC repo, you can now join this new slack channel to see the latest updates right in Slack. Also, our friends at npm have been active with their open RFC program and now have a spot in our slack workspace for you to pop in, ask questions, or just say hello!


🗒 Meeting Notes & Recaps

CPC MEETING RECAP
Meeting Notes | Recording | GH issue

  • We started with an issue from the /summit repo, #249, Travel Fund Questions for Project Community Members. This issue was brought to ensure that qualifications are clear to projects about who can qualify for the travel fund. Michael briefly described the issue and the group discussed getting it added to the travel fund document. Joe suggested getting a PR open for discussion on this and encouraged others to comment.
  • Relatedly, Michael shared that he had landed a PR on the travel fund policy that had been open the requisite number of days. The change allows projects to request special allocations from the Fund.
  • Next, Joe introduced, #465 OpenJS Office Hours. This stems from an experiment Joe ran in the Fall with success, and again last week. Each time, the people on the call came away with action items. The idea is to figure out how to extrapolate this for other projects and increase contributions to them. Further, we hope to to surface needs from the community to OpenJS leadership, etc.
  • On issue #432, Start a Code of Conduct Team, Joe suggested that this can be closed because we had successfully held our first call and proposed an initial group of panelists. Michael also suggested that there might be interest in working on "phase two" – extensions of the MVP, but agreed the issue could likely be closed.
  • Michael then introduced #469, Populate the Code Of Conduct Panel. This issue is a follow-up activity to 432. Since we have landed the first draft of the Code of Conduct policy, we need to appoint and empower the team who will drive this moving forward. Jory will be reaching out the Impact project reps to get their appointees.
  • Brian Warner had few updates to #414, Add Foundation-wide copyright guidance. Both Tobie and Brian have been out of pocket and hope to be able to attend to this soon. Those with questions in the meantime are encouraged to reach out to Brian.
  • Issue #386, was decided to be rebased and landed assuming the vote totals were correct. Michael will then take it to the board for a vote.
  • On #379, CoC proposal to stage 3, was landed as the criteria had been made
  • #326, Responsible security disclosures, there were three identified action areas based on progress from Marcin, which include the bug bounty and hackerone programs. Myles reported that he was not aware of any progress. These are not blockers but rather program features we would like to scale for the entire foundation. The team are looking to understand the ways different projects are handling these kinds of programs to see what can be done for the broader benefit. Those interested are encouraged to get involved in https://github.com/nodejs/security-wg.
  • On #185, Add admin policy docs, there was no meaningful update.
  • We closed #96, draft proposal: language for project exit clause, because a previous PR that was merged in had addressed it (#313).
  • There was no update for #90, Project Directed Funding, Michael gave a short update as he thought there was some agreement and possible movement or news to share. Brian reported that there was some meaningful agreement on the ability for organizations to donate funds to specific projects, but there has not yet been any agreement on the position of crowdfunding. Documentation of these agreements is needed and a vote is still needed.
  • We then moved on to discuss issues from other repos. From the standards repo #58, Chartering the standards team, Myles reported that the work is active and there is additional work to do in the standards repo, based on the way Node has done chartering in the past. Myles asked about the documentation needs from the CPC and suggested that there is a need for a related PR on the CPC repo. Joe reported that the Node WG document is part of the admin policy docs that need to be ported over. Michael stated that it would be good to have a concrete set of things it would be doing (such as sending CPC representatives to standards meetings). The next step is opening a PR against the CPC repo with this documentation.
  • Also from the standards repo, #43, Joining the Unicode Consortium, Michael reported that the request had been sent to the board. Legal is now reviewing the terms and conditions. We expect to turn this around quickly assuming there are no other questions. Relatedly, Brian reported that the vote completed for the org to join OSI and the application will be completed soon.
 
 
         
 
🔗 Handy-Dandy Links
 
twitter @openjsf
github github.com/openjs-foundation
youtube OpenJSF YouTube Channel
 
 
 



--