doc: add missing notes

Closes: openjs-foundation#353
Closes: openjs-foundation#381
Closes: openjs-foundation#395
Closes: openjs-foundation#401
Closes: openjs-foundation#408
Closes: openjs-foundation#412
Closes: openjs-foundation#416

meetings/2019-10-22.md

@@ -0,0 +1,103 @@
+# OpenJS Foundation Cross Project Council Meeting 2019-10-22
+
+## Links
+
+* **Recording**:  https://www.youtube.com/watch?v=_DX3l-K8ud4
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/353
+
+## Present
+
+* Joe Sepi (@joesepi)
+* Even Stensberg (@evenstensberg)
+* Sendil Kumar (@sendilkumarn)
+* Nick O’Leary (@knolleary)
+* Manil Chowdhury (@keywordnew)
+* Jory Burson (@jorydotcom)
+* Tobie Langel (@tobie)
+* Myles Borins (@MylesBorins)
+* Kris Borchers (@kborchers)
+* Michael Dawson (@mhdawson)
+* Anton Molleda (@molant)
+* Bernard Lin (@concoquere, observer)
+* Matteo Collina
+* Robin Ginn
+* Rachel
+* Brian Warner
+* Eemeli Aro (@eemeli)
+
+
+## Agenda
+
+### Announcements
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+* Jory: Reminder that standards WG meeting is this afternoon.
+* Jory: Please submit proposal for collab summit 
+* Manil: How to submit a proposal for the Summit (approx 20 mins for barebones proposal)
+
+Go to the issues tab of the Summit repo: https://github.com/openjs-foundation/summit/issues/new/choose
+Choose the Summit Topic Proposal template and click Get Started
+Fill in the title and sections
+
+### Board updates
+
+* No concerns from Board on Travel fund proposal, landed as stage 3.
+* Update on project progression, email vote underway, hope to close soon. 
+* Board meeting this Friday. No issues on board to bring up. Please let Michael
+  know if you have anything that should be added.
+
+### openjs-foundation/cross-project-council
+
+* Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331)
+  * Proposal to move issues for onboarding for separate repo
+  * Jory has looked a bit a some tooling. What do we need to optimize for.
+  * Joe try to survive without tool?
+  * Tobie, private repo.
+  * Michael do review in private part of meeting each week for tracking SLA’s etc
+    Then private repo works.
+  * More discussion …
+  * Joe proposed we do weekly check in the CPC meeting private section and
+     create private repo.
+     * Sounds like we have consensus on that.  Need somebody to 
+       * Create private repo
+       * Create initial issues in that private repo
+       * Ensure we schedule private section for each meeting
+       * Ask foundation staff to bring update on where we are on each of the 
+         projects versus SLA’s and next steps so we can review in the meeting each 
+         week.
+
+
+* Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326)
+  * Waiting on Security WG team member to work on draft.
+
+* Can CPC member also be champion?  [352](https://github.com/openjs-foundation/cross-project-council/issues/352)
+
+  * LJHarb - seems more natural to be separate.
+  * Even - also means that you have multiple people.  Re-assuring that you have multiple people
+     on the same page. Separate makes its clear.
+  * Michael, my thoughts were along the same lines, not strong feeling, but was leaning towards
+    being separate is better.
+  * Matteo, agree, makes it clearer. Main concern was to clarify this in the doc so that applicants
+    Know.  Only downside is that is add a bit more work/process but probably worth it.  Leaning
+    towards separate being best as well.
+  * Tobie, quite likely from viewpoint of somebody who cannot be both, can look unfair.
+  * Even, having 2 separate people helps build trust as well.
+  * Consensus in meeting was that it should be 2 separate people.
+* JQuery infra meeting met last week. 
+  * Talked about some critical issues related to JQuery. Not necessarily generalizable to other
+     Projects but some  
+
+* Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115)
+
+  * Link to draft services menu posted on the issue.  Jory will create PR so that we can 
+    progress toward landing in the repo.
+
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://nodejs.org/calendar
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

meetings/2019-10-29.md

@@ -0,0 +1,66 @@
+# OpenJS Foundation Cross Project Council Meeting 2019-10-29
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=u5YJMq399-M
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/381
+
+## Present
+
+* Joe Sepi (@joesepi)
+* Even Stensberg(@evenstensberg)
+* Michael Dawson (@mhdawson)
+* Chris Hiller (@boneskull)
+* LJHarb
+* Anton Molleda (@molant)
+* Brian Warner
+* Myles Borins (@MylesBorins)
+* Tierney Cyren
+* Timothy Willison (@timmywil)
+* Christian Bromann (@christian-bromann)
+* Eemeli Aro (@eemeli)
+
+
+* doc: move COC proposal to stage 3 [#379](https://github.com/openjs-foundation/cross-project-council/pull/379)
+  * Moderation team from the AMP project have indicated that they will review
+    and give us some feedback/comments.
+  * Waiting for that before moving forward.
+
+* Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331)
+  * Agreed last week to create public/private repositories to track 
+  * Joe has created the public repo, moved over Node onboarding issue
+  * Started to create repo but org needs to be upgraded first
+  * Joe, -> could move over the obvious public onboarding issues, should move 
+    over project board as well?  Michael, sounds good.  No objections from those
+    in the meeting.  
+
+* Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326)
+  * Michael followed up with Marcin and he’s indicated that he hopes to publish a draft
+    For discussion this week.
+
+
+* Add impact and consumers of the project to new project template    [#306](https://github.com/openjs-foundation/cross-project-council/pull/306)
+  * Myles will give it another review.
+
+* Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115)
+  * Joe has some WIP for moving the Node.js docs over as a baseline
+  * Issues waiting on the board
+     * project directed funding discussed in last board meeting and
+       understood that we need to address some aspects for some projects coming in.
+     * Guidance on usage of logos etc should be able to proceed now that IP policy has been
+       Approved.
+     * Question about CLA being signed both for company and individual (both at the same
+        time), Brian to ask, believes it will have been considered but does not have answer
+        off the top of his head.
+  * Items to discuss with the board is empty
+  * onboarding board
+    * Walked through a number of issues
+
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

meetings/2019-11-05.md

@@ -0,0 +1,135 @@
+# OpenJS Foundation Cross Project Council Meeting 2019-11-05
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=DfaoH8lKR6Q
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/395
+
+## Present
+
+* Michael Dawson(@mhdawson)
+* Brian Warner (@brianwarner)
+* Joe Sepi (@joesepi)
+* Chris Hiller (@boneskull)
+* Jory Burson (@jorydotcom)
+* Nick O’Leary (@knolleary)
+* Kris Borchers (@kborchers)
+* Rachel Romoff (@rromoff)
+* Anton Molleda (@molant)
+* Tobie Langel (@tobie)
+* Tierney Cyren
+* Robin Ginn
+* Eemeli Aro
+
+## Agenda
+
+### Announcements
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+* Come to Node + JS Interactive, it’s awesome, tell your friends!
+* Project Onboarding issues have been moved to the Project Onboarding Repository
+* Node CommComm AMA tomorrow morning
+
+### openjs-foundation/cross-project-council
+
+* Collab Summit sessions [#390](https://github.com/openjs-foundation/cross-project-council/issues/390)
+
+Session ideas for CPC related topics? Such as transition process, emeritus projects, standards wg session, etc.
+MD: these are good specific things we can work on together. Should we also have some blue-sky conversations?
+JS: Good suggestion. Should these be separate submissions? 
+MD: Do we know how big (long) each session is? (we don’t know)
+MD: Do we want working sessions, or do we want sessions new people can join, as that might impact the number, the flow, etc?
+JB: they were an hour in Berlin. 
+TL: I don’t know if I’ll be able to make it, but something I’d like to cover is earmarking funds for projects. 
+JB: will we have enough info from the board to hold a session on funding?
+MD: It will come down to how much progress is made. 
+JS: Let’s reach out to collab summit friends and see what kind of time block we can get.
+MD: I think that makes sense. We’ll want to make sure we capture what we want to do for the collab summit agenda.
+JS: we can also take advantage of the Community Corners to promote/have conversations about CPC items.
+MD: Should we have a “I’m on the CPC, AMA” sticker we can wear so people can identify us and ask questions. (good idea)
+JS: I will take the AI to reach out to the summit team and get the info we need, and craft a plan.
+
+* Update contact email for new project proposals [#389](https://github.com/openjs-foundation/cross-project-council/pull/389)
+
+Email addresses that new project proposals go to, concern that there is a possibility that there will be people who should not be on the reply. 
+
+Whoever is on the operations alias should reply acknowledging receipt *and* make sure the application is complete. Ideal if this step could also assign an application manager.
+
+TL: also, projects are also collaborating with multiple people on the application and this should be taken into consideration as well.  
+
+* request: Review CommComm Charter Update [#383](https://github.com/openjs-foundation/cross-project-council/issues/383)
+
+Request: Please review. 
+JS: How did we do this for the TSC?
+MD: We should be able to go ahead with a good number of +1s, and a time-box. Probably good to send it to the board for an FYI.
+JB: Note that it is not required to send project charters to the Board.
+KB: right this should just be an FYI, we aren’t looking for approval.
+MD: should we choose that time? It’s 14 days for governance changes. 
+JB/JS: that sounds good.
+
+* Will land 14 days from now unless there are objections.  Please review and +1 if appropriate
+  * Michael will send FYI to board.
+
+* doc: move COC proposal to stage 3 [#379](https://github.com/openjs-foundation/cross-project-council/pull/379)
+
+TL: We have a meeting later today (for AMP’s onboarding WG)
+MD: Do we want to make this the official process and then change, or do we want to address these questions as substantive?
+TL: I can bring this up on today’s call. Happy also to do a joint discussion meeting.
+(Group organizes a joint conversation with interested parties: Tierney, Joe, Jory, Michael)
+
+* Administering Project Applications [#331](https://github.com/openjs-foundation/cross-project-council/issues/331)
+
+Process for monitoring basic SLA and staying on top of project applications. 
+We decided to create a private and public repo, but are waiting on the private repo. 
+Jory moved tickets over today. 
+We can probably close this when the project onboarding process settles a little more.
+
+* Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326)
+  * PR open for guidance to maintainers in nodejs/package-maintenance repo
+    * https://github.com/nodejs/package-maintenance/pull/277
+  * Will be basis for OpenJS recommendations so waiting for it to be reviewed
+    gain consensus first.
+
+* Mailing lists for projects [#324](https://github.com/openjs-foundation/cross-project-council/issues/324)
+
+This was a generally available information issue that we are happy to set up mailing lists for projects if they want. Another question is which people should be on maintainer mailing lists, and so there was an idea to create project-specific mailing lists for maintainers. We are close to having a firmer idea of what we want to do here. See lists.openjsf.org. If you’re just looking for an alias we can set that up as well. We’ve been talking about if we just want a single email to reach all the maintainers at once. 
+
+EA: {didn’t catch the idea}
+MD: is this also in our services menu?
+BW: yes, it should be.
+MD: can it be delegated to the project? 
+BW: it depends on what infra is being used. I can create a list and delegate moderation/management of that list in groups io. (not with aliased emails)
+JS: Can we close this issue?
+
+
+* Add impact and consumers of the project to new project template [#306](https://github.com/openjs-foundation/cross-project-council/pull/306)
+
+JS: We got the last +1s based on feedback we were looking for so this should be good to merge. Any concerns? (none)
+
+* Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115)
+
+Admin docs and Infra work are in progress
+Three items waiting on the board - funding, CLA bot, style guide.
+Trademark guidelines and style guide should be addressed shortly. 
+IMpacting style, we’ve been fielding questions about a standard header or footer for project website. They idea is that projects can incorporate this on their own websites and have a standard footer. This is on its way. 
+JB: we need to bear in mind that not all projects have websites. What notices need to go where if there is no website?
+BW: Those questions will have to go back to the board/legal
+EA: Would OpenJSF provide project feeds for projects who don’t have blogs/places to post updates etc?
+RR: We have a draft plan for how we can scale this for project. We haven’t solidified this yet but working with Robin to get those done. 
+BW: A lightweight answer is the twitter handle/other social properties. 
+JB: You can let us know about this in Slack (#pr-marketing)
+BW: We should get more of this documentation up
+MD: Rachel is working on getting this documentation but together, like the infra services plan but for marketing. 
+RR: Correct!
+
+Break for Private session at 12:52
+
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

meetings/2019-11-12.md

@@ -0,0 +1,77 @@
+# OpenJS Foundation Cross Project Council Meeting 2019-11-12
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=OEUKPkZCvaw
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/401
+
+## Present
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+Jory Burson (@jorydotcom)
+Tierney C (@bnb)
+Rachel Romoff (@rromoff)
+Christopher Hiller (@boneskull)
+Timmy Willison (@timmywil)
+Even Stensberg (@evenstensberg)
+Ruy Adorno (@ruyadorno)
+Tobie Langel (@tobie)
+
+
+
+## Agenda
+
+### Announcements
+Jory asked for collab summit sessions as we enter into Node+JS Interactive season
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+### openjs-foundation/cross-project-council
+
+* onboarding meta questions [#398](https://github.com/openjs-foundation/cross-project-council/issues/398)
+Where should onboarding topics live? This process should be documented in the repo.
+Jory, Brian, and Tobie to speak further to move this forward.
+
+* Collab Summit sessions [#390](https://github.com/openjs-foundation/cross-project-council/issues/390)
+Next step, more input on what sessions the CPC wants to run, and who from the CPC would like to lead these sessions. Please share input on the issue.
+
+* request: Review CommComm Charter Update [#383](https://github.com/openjs-foundation/cross-project-council/issues/383)
+For questions or concerns, please comment or reach out to Tierney
+
+* doc: move COC proposal to stage 3 
+[#379](https://github.com/openjs-foundation/cross-project-council/pull/379)
+
+File an issue for a process for changing the CoC in the future
+
+Notes from the Ad Hoc CoC Meeting: https://docs.google.com/document/d/1wCZMnfwJnDF9l4sUq0BD5JI-mbPCtQnPfVHmvge_ZWs/edit
+
+* Administering Project Applications 
+[#331](https://github.com/openjs-foundation/cross-project-council/issues/331)
+Last update was we had a public onboarding repo, and looking into a private repo. 
+Private repo has been requested from GitHub and we are waiting.  Jory to check with Brian on the capability to create private repo.
+
+* Responsible security disclosures [#326](https://github.com/openjs-foundation/cross-project-council/issues/326)
+
+* Post-Bootstrap work to be managed by CPC [#115](https://github.com/openjs-foundation/cross-project-council/issues/115)
+
+Gone through board, checked off relevant issues and checkboxes that are completed.
+
+*Checklist deadline for Collab Summit graduation
+[openjs-foundation/project-onboarding#30](https://github.com/openjs-foundation/project-onboarding/issues/30)
+Voting is relatively quick and happens asynchronously. That said there’s still a lot of blocked issues (e.g. the Code of Conduct changes discussed before) that are going to make it really difficult to graduate by the Collab Summit.
+
+* Communication channel between CPC and AMP infra WG [openjs-foundation/project-onboarding#31](https://github.com/openjs-foundation/project-onboarding/issues/31)
+CPC do decide which communication channel is preferred between dedicated mailing list and foundation Slack.
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+
+