update meetings notes (#68)

Closes: #65
Closes: #63
Closes: #61

meeting-notes/2020.01.28_meeting_notes.md

@@ -0,0 +1,77 @@
+# OpenJS Foundation Standards Team Meeting 2020-01-28
+
+## Links
+
+* **Recording**: http://www.youtube.com/watch?v=KkKCCs9QIY4
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/61
+
+## Present
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+* Sendil Kumar N (@sendilkumarn)
+* Myles Borins (@MylesBorins)
+* Jory
+* Eemeli Aro (@eemeli)
+* Mike
+* Jordan Harband (@LJHarb)
+* Richard
+
+## Agenda
+
+### Announcements
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+* TC39 next week in Sunny HI
+
+### openjs-foundation/standards
+
+* Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58)
+
+* Was briefly presented at today’s CPC meeting. Example used: OSI membership.
+* No concerns or objectives, the ball is in our court to create a charter and bring it to the CPC for review and approval 
+* Theoretically similar to the project chartering process for project onboarding
+Getting the process together and figuring it out - 
+Mike: how can I help?
+Myles: I’ll open a PR with the template charter, we should review and comment; I think we need true consensus before we go to the CPC for sign-off
+* Discussion about ensuring the charter and the governance docs are well aligned
+Mike: PRs take awhile for people to incorporate edits - can we start with a gdoc for faster iteration?
+Myles we can do that esp for getting the first pass done. Let’s make a doc and drop it in teh issue
+Mike: makes a link & drops it 
+Jory: do the docs from /Admin have any bearing on this?
+Myles: I don’t think so. Kindof seems like the working groups in Node just have governance docs. We have 90% of what the Node Admin reqs have, just a couple of things missing
+Are we a working group of the CPC or a different autonomous entity?
+Eemeli: I think its simplest if we are under the CPC
+Myles: I think these issues would go to the CPC and only go to the board if we were unhappy with the results 
+Myles: should we amend our gov. Docs and take this to the CPC?
+Group: +1
+Myles: I’ll take the AI
+
+* governance: getting permission to attend meetings [#56](https://github.com/openjs-foundation/standards/pull/56)
+
+* do we need to require the person to be a member / representative of the standards wg?
+Should attend a standards wg meeting as requested
+Should be a member of one of our project communities
+Discussion of the purpose of the group (node modules wg example)
+Empowering the projects to participate
+The ask is for projects to report their participation
+There is a bit of internal conflict; we need to be able to serve projects and provide a consistently applied process
+What’s the minimum process? We shouldn’t introduce a regression.
+What are the simplest steps? File an issue & tell us about it. If you want to rep the foundation that would require approval.
+
+* Joining the Unicode Consortium [#43](https://github.com/openjs-foundation/standards/issues/43)
+
+* Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6)
+
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+

meeting-notes/2020.02.25_meeting_notes.md

@@ -0,0 +1,56 @@
+# OpenJS Foundation Standards Team Meeting 2020-02-25
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=6gVlu3rBm0g
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/63
+
+## Present
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+* Joe Sepi
+* Mike Samuel (@mikesamuel)
+* Jory Burson
+* Jordan Harband (@LJHarb)
+* Myles Borins
+* 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.
+
+
+
+### openjs-foundation/standards
+
+* Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58)
+
+The thing we need to land is the document about who can go to meetings, etc.  (#56)
+Need to get the WG docs added from Admin (some of which Joe has started) - Joe will work on this before next CPC meeting.  (#443)
+Joe - would you like to break up this work into separate PRs?
+That’s not necessary - whoever wants to do the work should just do it’
+Mike: what kind of help (copy editing, etc), what should I be looking at?
+Converting language from ‘Node’ Foundation, etc
+Joe: I would like to make progress on this before the next meeting
+
+* governance: getting permission to attend meetings [#56](https://github.com/openjs-foundation/standards/pull/56)
+
+Myles: have had some suggestions from Eemeli
+
+Myles: 
+
+* Standards-related Travel Budget Clarification [#6](https://github.com/openjs-foundation/standards/issues/6)
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+

meeting-notes/2020.03.10_meeting_notes.md

@@ -0,0 +1,89 @@
+# OpenJS Foundation Standards Team Meeting 2020-03-10
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=ZNo-Thqz_wc
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/65
+
+## Present
+
+* Myles Borins (@MylesBorins)
+* Jory Burson (@jorydotcom)
+* Robin Ginn (@rginn)
+* Brian Kardell (@bkardell)
+* Sendil Kumar N (@sendilkumarn)
+* Jordan Harband (@LJHarb)
+* 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.
+
+### openjs-foundation/standards
+
+* Participation in the Unicode MessageFormat WG [#64](https://github.com/openjs-foundation/standards/issues/64)
+  * Robin: Legal team approved. Waiting for final approval from the consortium.
+  * Myles: Relatedly, is there any updated on the OSI?
+  * Robin: This is in a similar state, no status update at the moment. Will checkin with OSI.
+  * AI: remove the agenda label.
+* Standards-related Travel Budget Clarification - [#6](https://github.com/openjs-foundation/standards/issues/6)
+  * Jory: The issue is stale. We moved past other conversations. 
+  * Myles: Projects may sign in to vouch for travel. The CPC will eventually approve the travel request. 
+  * AI: remove the agenda label. 
+* Request to attend TC39 as OpenJS delegate [#66](https://github.com/openjs-foundation/standards/issues/66)
+  * Myles: Gus attended TC39 before (both remotely and in-person). He is technically on-boarded. Appreciate that he took part in the process.  Does anyone have objections?
+  * Jordan: No objections. (he is qualified). Gus is not a regular member, can he attend?
+  * Myles: Empower those who want to attend.
+  * Jordan: Thanks.
+  * Jory: Encourage other folks to do. Getting early feedback and sharing this will be awesome.
+  * Myles:  Do you (Richard) think it is reasonable to ask the delegate representation to be permanent? 
+  * Richard: There is a lot of value in those. If Gus wanted to attend regularly that makes sense. It is also nice if he wants to focus.  
+  * Jordan: Even with one delegate it makes sense. If there are multiple delegates they have to coordinate between them but it is also good to have. 
+  * Myles: Some of this topics might be sensitive, it would have been better to do it privately first. Explore the governance and make it part of the process for this discussion.
+  * AI: Edit Governance to accommodate the above text. 
+* Chartering the standards team [#58](https://github.com/openjs-foundation/standards/issues/58)
+  * Myles: CPC is in process to review. There is a PR in CPC (https://github.com/openjs-foundation/cross-project-council/pull/443). Once that lands. 
+  * The scope is outlined here - https://hackmd.io/kkjTah1XTh2-ubcKLxQD4Q. Review this and make a PR. 
+  * Myles: going through the https://hackmd.io/kkjTah1XTh2-ubcKLxQD4Q
+  * Jordan: preference for the 1st paragraph
+  * Removed the second para
+  * Myles: Does anyone object to the responsibility? 
+  * (all): none
+  *    ---
+  * Eemeli: Should we preemptively include Michael Dawson’s Working Group initiative. Meeting about effectively creating WG and be in charge of the space for standards. 
+  * Myles: It is about more ad-hoc groups. Standards is one of those areas. What is the relationship between that group and our group. In WASM, CG is where work happens and WG is administrative. It might be premature for us to document. It might be possible if Standards WG is spin up, we might then draft something on how both should work.
+  * Eemeli: ---
+  * Myles: Maybe a good litmus test, would anyone will be concerned about affiliation with a group for direct engagement
+  * Robin: Can you elaborate more on the direct engagement
+  * Brian: You have to clear when you are representing the foundation. Wearing multiple hats.
+  * Myles: describing the spaces (when there is a difference of opinions and disagreements). This group is responsible for facilitating that.
+  * Jordan: delegates from the same company disagreed and they handled it beforehand. But it did not happen correctly in the past.
+  * Robin: It has to be open and transparent. 
+  * Brian: Perhaps one aspect, gauge and provide opportunities for internal consensus seeking. We don’t have any example or any possible process. It would be pretty powerful if we have single voice
+  * Myles: People having individual voices is also important. Each of these hats is extremely important and we should facilitate that.
+  * Richard: Do we have any thoughts on the mechanism?
+  * Myles: ---
+  * Richard: OpenJS sends multiple delegates and they focus on different items.
+  * Myles: It is situational here.  (explaining with a few examples)
+  * Myles: may be there is an educational angle here. (ordering the resp.)
+  * Myles: the scope document will live in the CPC not in standards. (going through the member-expectations document)
+  * Myles: create an auto populated issue template from member expectations.
+  * Brian: W3C has the AC role. It seems it will be good if some of them come to standards Group. 
+  * (No objections for the edited document)
+  * Myles: Will @ the standards team when the document is PR’ed into the CPC. (no objections).
+
+
+## Q&A, Other
+
+ No questions :)
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+
+