Merge pull request #96 from openjs-foundation/meeting-notes-201905

Add meeting notes

meeting-notes/2020.04.07_meeting_notes.md

@@ -0,0 +1,55 @@
+# OpenJS Foundation Standards Team Meeting 2020-04-07
+
+## Links
+
+* **Recording**:
+* **GitHub Issue**: $GITHUB_ISSUE$
+
+## Present
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+
+
+## Agenda
+
+No issue for this: Content for OpenJS
+Would like to do a blog post introducing the first chartered WG
+Also a quarterly update post
+How to track the content that we would want to report on
+Who do we delegate this to - in order to get it done
+Shouldn’t be a heavy lift
+Mike Samuel volunteers to help with producing this
+Start a Hack.md to collaborate on announcement doc
+“Here’s how a project I worked on” - ground the relevance
+What would the call for action be?
+Call for projects to get involved
+Calendar
+AI to Jory to talk to Brian about groups.io
+AMA for the Standards WG? July is the next opening
+Other standards related topics to cover on the blog?
+Recaps of meetings or “this is what it was like” 
+Richard sync with Rachel 
+
+News - approval from OSI has been received
+Myles & Brian figuring out what is needed for the affiliate membership and how we participate
+
+
+
+### Announcements
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+
+
+## 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.05.05_meeting_notes.md

@@ -0,0 +1,80 @@
+# OpenJS Foundation Standards Working Group Meeting 2020-05-05
+
+## Links
+
+* **Recording**:
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/87
+
+## Present
+
+* Myles Borins (@MylesBorins)
+* Sendil Kumar N (@sendilkumarn)
+* Brian Kardell (@bkardell)
+* Mike Samuel (@mikesamuel)
+* Jordan Harband (@ljharb)
+* Donovan Buck (@dtex)
+
+## 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
+
+* Nominate OSI Representative [#89](https://github.com/openjs-foundation/standards/issues/89)
+Scope is not well known
+Myles self nominated.  Cross posted to CPC.
+Robin why is this limited to standards?
+Myles: charter includes “manage relationships with standards organizations”
+Jordan: who do we want to reach who is not in standards WG and would be appropriate nominee?
+Jory: ok to cross post.  If projects are paying attention to one [GH project] it’s probably CPC
+Robin: Is OSI just a “standards organization”?
+Myles: [If CPC wants to undelegate] do we need to massage the standards charter.  CPC should be careful before acting on something that seems to have been delegated.
+Jordan: Robin, what is OSI
+Robin: Interactions with OSI include things unrelated to technical standards making
+Brian: It's sometimes a little hard to say "what is an SDO" it is listed on http://www.openstandards.net/viewOSnet2C.jsp?showModuleName=Organizations for example and W3C was created with the view that it wouldn't be an SDO, but it is largely seen as one.
+Myles: OSI may be on the line.  There may be other organizations which are on the line but which Standards WG wants to manage, and seek CPC approval for delegation of additions.  A list would clarify.
+Jory: Nomination will remain open for a week.
+
+* Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84)
+
+Current discussion is over thematic disagreement over individual autonomy, for example to block consensus
+Relationship between the Foundation as a Member Trade org, and its membership / expectations for participation in an SDO
+Action Item: if people expressed opinions last meeting or have thoughts from this meeting, please add them to issue #84.
+Myles: actions taken by delegates on behalf of OpenJS Fdn should be “built on a bed of consensus”
+Jordan: my experience from TC39 is people are clearly balancing their own opinions and their organizational duties.  Some employers put people on leash, but it’s not infrequent for people to say “my opinion is ...; my employer wants …”
+Jordan: power to block comes from procedures
+Myles: blocking is voting
+Jordan disagrees with framing
+Mike Samuel: Need rigorous facility for assessing / building consensus or opinions (see comment) but ultimately have to trust delegates to advance their understanding of the consensus and deal with repeated failure to represent consensus after the fact.
+Brian: Blocking seems a discrete question so we can build a process specifically for that.
+Robin: I spoke up last week supporting Myles.
+Jordan: Any action has to be justified after the fact.  In TC39, most actions are blocking.  Not advocating for lack of accountability; just for not constraining actions [in unforeseen situations?].  The perception of blocking as a hammer does not match my experiences with TC39 specifically; blocking is often a good thing since the organization biases towards not changing the language.
+
+* Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83)
+
+* Collect info from standards meeting attendees [#81](https://github.com/openjs-foundation/standards/issues/81)
+
+https://hackmd.io/vj30p217SZa8U3KLZTVXOg?view
+
+* Craft the Standards Working Group Mission statement [#80](https://github.com/openjs-foundation/standards/issues/80)
+
+Mike Samuel submitted related PR: https://github.com/openjs-foundation/standards/pull/88
+
+The Standards Working Group actively monitors evolving standards to educate projects about developments that might affect them, and helps projects formulate standards strategies and advance them before standards bodies.
+
+
+
+
+
+## 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.05.19_meeting_notes.md

@@ -0,0 +1,70 @@
+# OpenJS Foundation Standards Working Group Meeting 2020-05-19
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=W7s2B1xBgwA
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/90
+
+## Present
+
+* Jory Burson (@jorydotcom)
+* Jordan Harband (@ljharb)
+* Eemeli Aro (@eemeli)
+* Donovan Buck (@dtex)
+* Mike Samuel	 (@mikesamuel)
+* Robin Ginn (@rginn)
+* Joe Sepi (@joesepi)
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+
+
+## Agenda
+
+### Announcements
+
+Jory:
+* Open Office Hours this Thursday
+* Marketing meeting after this meeting
+* Board meeting this Friday
+* OpenJS World and Collab Summit is in about 4 weeks. Projects: submit sessions for summit; everyone register for event.
+
+*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
+
+### openjs-foundation/standards
+
+* Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84)
+* Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83)
+* Collect info from standards meeting attendees [#81](https://github.com/openjs-foundation/standards/issues/81)
+
+
+
+* Craft the Standards Working Group Mission statement [#80](https://github.com/openjs-foundation/standards/issues/80)
+Ship related PR
+
+Standards Blog Post - Ship it
+
+Collab Summit Sessions
+
+Private email list discussion: Legal recommends against it
+Private discussions should be held verbally
+Suggest language such as “discussion ensued over X”
+
+Unicode Consortium
+Waiting on official acceptance from the Org - check in with 
+Talk to Rafael RE participation
+
+
+
+
+## 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.06.02_meeting_notes.md

@@ -0,0 +1,48 @@
+# OpenJS Foundation Standards Working Group Meeting 2020-06-02
+
+## Links
+
+* **Recording**:
+* **GitHub Issue**: $GITHUB_ISSUE$
+
+## Present
+
+* OpenJS Foundation Cross Project Council
+* OpenJS Foundation Project Maintainers
+* OpenJS Foundation Board of Directors
+
+
+
+## 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
+
+* New relationship with Unicode Consortium
+https://github.com/openjs-foundation/standards/issues/43
+
+We were accepted as associate members
+Ben Michel would like to participate as well
+Discussion with Steven & Ben: Bookmarking this to continue the conversation effectively for next time
+Idea to do a presentation on the Unicode Consortium & the other member orgs
+Invite Alolita to come present
+
+* \[TC39\] Potentially blocking "Module Attributes" proposal [#91](https://github.com/openjs-foundation/standards/issues/91)
+
+* Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84)
+
+* Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83)
+
+
+
+
+## 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.06.16_meeting_notes.md

@@ -0,0 +1,75 @@
+# OpenJS Foundation Standards Working Group Meeting 2020-06-16
+
+## Links
+
+* **Recording**:
+* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/94
+
+## Present
+* Mike Samuel (@mikesamuel)
+* Myles Borins (@MylesBorins)
+* Jordan Harband (@LJHarb)
+* Ben Michel (@obensource)
+* Sendil Kumar (@sendilkumarn)
+
+
+
+## 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
+
+* Discuss foundation TC39 delegate expectations [#84](https://github.com/openjs-foundation/standards/issues/84)
+
+Myles: There’s a difference of opinions at the moment, such that I don’t think we’re going to reach consensus. We’ll need to move forward with people acting in good faith in the position they have. There’s so much going on that we don’t have time to discuss every single issue.
+
+It’s possible that someone can raise an issue as a pre-meeting, potentially topics that are controversial, which we can come to consensus on before moving forward with a meeting.
+
+How much consensus do we need before moving on with decisions under general agreement without getting into too much process? The blocks in tc39 are very particular to a specific organization, in OpenJS – we need to answer the questions as to how we want to do this in our own regard.
+
+Brian: We’re very in the weeds on what you can or can’t do. If you’re in the room and you can wear multiple hats, you can speak up all along the way and be very clear as to which hat you’re wearing at the time. So, how do we communicate, and can we build consensus? Are there ways that we can come to consensus on with a wider voice of the openjs community. I agree with Myles.
+
+Sendil: I agree too. Bringing the discussions down before going to any particular standards body is good. If we need to we can formalize it later rather than discussing it now.
+
+Eemeli: We haven’t been clear – there ought to be an expectation on delegates for them to actively let us know what’s going on in other bodies. Tc39 is the only one we’ve only been actively discussing hear in the standards WG. Are there other things we need to talk about in the Standards group right now?
+
+Brian: We’ve had multiple areas of interest across many standards bodies. For example, I’ve been involved in the CSS WG – and we care about it, but we can’t bring all the concerns of that body to this group.
+
+Sendil: Is there any historic precedent for us, and/or any info as to how we can operate in this way? In the past, was there a standards body that has been through this before? Can we leverage their experience? 
+
+Robin: Many organizations will have this in order to make business decisions across orgs, etc.
+
+Myles: At google we had pre meetings like this, and this is a good way to handle this sort of thing. Maybe we can have people sign up for a mailing list where we are setting up clarity for anyone and any project who wants to be involved. Our reps who represent OpenJS need to focus on representing the foundation and the consensus that we’ve built to those organizations.
+
+Robin: Our staff can help with the community resources, and we’d love to stay informed on what’s happening and where change is needed.
+
+Donovan: We don’t have guidelines for delegates. Is there a document for expectations of delegates anywhere? Communicating through email lists, etc, is what I’d expect of delegates.
+
+Sendil: If we can extend our document to reflect that, it would be a good decision.
+
+Brian: We also have i18n, and 402, and Embedded, and other things in ECMA etc, and other stuff delegates are interested in – testing, privacy, ietf, etc. Do we need a single catch all list for everything? Are we working on expectations for tc39 as a starting point?
+
+Myles: I hope that a lot of the guidance that we have should be clear across orgs. We should have a document about how we support organizations. We could have a folder or structure to reflect in documenting our interactions with each org. What’s the decision making, how do you get involved with a project. Maybe we could use our Wiki for this?
+
+Brain: But how do we keep up with standards and projects, do we do a pre meeting, etc? We don’t want a firehose?
+
+Ben: What’s our scope per standards body that we wish to discuss at each Standards meeting? In other words, how much & what does our Foundation care about needing to know?
+
+Myles: What is appropriate, what makes sense? Maybe there’s something we need to formalize with this Liaison role? Something we can surface per liaison, and within the foundation – what is the way we represent what matters per organization to the Foundation?
+
+If you represent a standards body here within the Standards WG, are a liaison, etc: please add your name to this list.
+
+* Request to participate in TC39 as OpenJS delegate [#83](https://github.com/openjs-foundation/standards/issues/83)
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Calendar**: https://calendar.openjsf.org
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+
+