doc: dec 17 2019 notes (#435)

Closes: #429

meetings/2019-12-17.md

@@ -0,0 +1,86 @@
+# OpenJS Foundation Cross Project Council Meeting 2019-12-17
+
+## Links
+
+* **Recording**: http://www.youtube.com/watch?v=Lzj7y2IgOHI
+* **GitHub Issue**: https://github.com/openjs-foundation/cross-project-council/issues/429
+
+## Present
+
+* Dylan Schiemann
+* Christian Bromann (@bromann)
+* Jory Burson
+* Brian Warner
+* Rachel Romoff
+* Robin Ginn
+* Tobie Langel (@tobie)
+* Myles Borins (@MylesBorins)
+* Kris Borchers (@kborchers)
+* Joe Sepi (@joesepi)
+
+## Agenda
+
+### Announcements
+
+*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
+
+* WebdriverIO: project charter review [#424](https://github.com/openjs-foundation/cross-project-council/issues/424)
+
+  * Discussion about charter approval process. Decision was made to keep the process as lightweight as possible and not require a formal vote.  
+
+* Mocha: project charter review [#419](https://github.com/openjs-foundation/cross-project-council/issues/419)
+
+
+* Add Foundation-wide copyright guidance [#414](https://github.com/openjs-foundation/cross-project-council/pull/414)
+
+Jory: had session at collab summit; wanted clarification if this PR is meant to be guide or shouldn’t change/set in stone policy
+Brian: its a guide; hope its clear but can make it clearer. Changing it does not change policy. If IP policy needs to change this isn’t the place to have it, changes in IP needs to go to board. But this is a living document that can be updated and modified and a good place to work through ip policy implementation
+Tobie: desire for direction for simplest implementation
+Brian: seems the ask: put simple stuff at top and deeper stuff below the fold
+Tobie: implementation as frictionless as possible; prescriptive about the baseline to implement
+Brian: thumbs up
+Tobie: I’m happy to help work through this document with you (Brian)
+Tobie: Myles mentioned an FAQ which could be helpful
+
+
+* Add a copy of the Contributor Covenant CoC text [#413](https://github.com/openjs-foundation/cross-project-council/pull/413)
+
+Agreement that the CoC should be inlined.
+
+* Kicking off an OpenJS Foundation project landscape [#411](https://github.com/openjs-foundation/cross-project-council/issues/411)
+
+* Github Admin [#409](https://github.com/openjs-foundation/cross-project-council/issues/409)
+
+* adds proposal for charter submission & review per #200 [#405](https://github.com/openjs-foundation/cross-project-council/pull/405)
+
+
+* Point of contact for onboarding [#400](https://github.com/openjs-foundation/cross-project-council/issues/400)
+
+* onboarding meta questions [#398](https://github.com/openjs-foundation/cross-project-council/issues/398)
+
+* Add post-graduation checklist [#386](https://github.com/openjs-foundation/cross-project-council/pull/386)
+
+* doc: move COC proposal to stage 3 [#379](https://github.com/openjs-foundation/cross-project-council/pull/379)
+
+
+* Clarify Travel Fund status & process [#377](https://github.com/openjs-foundation/cross-project-council/issues/377)
+
+* 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)
+
+### openjs-foundation/project-onboarding
+
+* Communication channel between CPC and AMP infra WG [#31](https://github.com/openjs-foundation/project-onboarding/issues/31)
+* Checklist deadline for Collab Summit graduation [#30](https://github.com/openjs-foundation/project-onboarding/issues/30)
+
+
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.