Skip to content

Commit 008921d

Browse files
sendilkumarnsendilkumarn
authored
chore: add meeting notes for past meetings (#112)
1 parent c75d3b6 commit 008921d

4 files changed

+243
-0
lines changed

‎meeting-notes/2020.07.14_meeting_notes.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# OpenJS Foundation Standards Working Group Meeting 2020-07-14
2+
3+
## Links
4+
5+
* **Recording**:
6+
* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/99
7+
8+
## Present
9+
10+
* Joe Sepi (@joesepi)
11+
* Donovan Buck (@dtex)
12+
* Jordan Harband (@ljharb)
13+
* Myles Borins (@MylesBorins)
14+
* Brian Kardell (@bkardell)
15+
* Robin Ginn
16+
* Mike Samuel
17+
18+
19+
20+
21+
22+
## Agenda
23+
24+
### Announcements
25+
26+
*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
27+
28+
### openjs-foundation/standards
29+
30+
* Discuss necessity or lack thereof, of having a chairperson for the team. Discussed the possibility of a “chore wheel”.
31+
32+
33+
* MBS: We could explore automating the transfer of notes from the Google doc to the repo. Might be worth looking into.
34+
35+
* MBS: TC-39 deadline for discussion is upcoming and it’s a good time to take a look at proposals that are up for advancement
36+
37+
* JBN: TC-53 is meeting tomorrow
38+
39+
* BKL shares announcement from Igalia: I work for Igalia and we work on all the open source web browsers. Tons of companies participate in creating web standards, Igalia helps gets them implemented. We thought it would be good if groups could collaborate and prioritize things to implement. We’ve identified 6 that anyone can go and contribute to help get the feature implemented. We hope this experiment will help start some healthy discussions about how the web can move forward.
40+
41+
https://www.igalia.com/open-prioritization/
42+
43+
## Q&A, Other
44+
45+
## Upcoming Meetings
46+
47+
* **Calendar**: https://calendar.openjsf.org
48+
49+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
50+
51+

‎meeting-notes/2020.08.25_meeting_notes.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# OpenJS Foundation Standards Working Group Meeting 2020-08-25
2+
3+
## Links
4+
5+
* **Recording**:
6+
* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/104
7+
8+
## Present
9+
10+
* Jory Burson
11+
* Robin Ginn
12+
* Myles Borins
13+
* Mike Samuel
14+
* Richard Gibson
15+
* Donovan Buck
16+
* Eemeli Aro
17+
* Sendil Kumar
18+
* Mike Samuel
19+
20+
* OpenJS Foundation Cross Project Council
21+
* OpenJS Foundation Project Maintainers
22+
* OpenJS Foundation Board of Directors
23+
24+
25+
26+
## Agenda
27+
28+
### Announcements
29+
30+
*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
31+
32+
### openjs-foundation/standards
33+
34+
* Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102)
35+
36+
What gap do we fill?
37+
How do we track / continue to support?
38+
Distinction between representing the project (Node) vs. the foundation (all of OpenJS)
39+
Action: Create venue for soliciting feedback
40+
Action: Documenting proposal process
41+
Action: Similar for W3C votes
42+
Action: Check in with Gus!
43+
44+
* Meeting time (Ad Hoc, raised from CPC meeting)
45+
* CPC meetings are alternating with an earlier meeting time as an experiment
46+
* back to back with CPC meeting is probably ideal
47+
*
48+
49+
* TC53 Meeting Update
50+
* working on first specification(s) - first draft expected in about a month
51+
* After first draft we would love to get feedback from the broader community - need to identify which projects would be interested
52+
* Robin happy to use marketing resources to help share information
53+
54+
* Check with Ben on Unicode Blog
55+
56+
57+
* Chore Wheel Items
58+
Agenda
59+
Triage
60+
Meeting reminders to people
61+
Hosting
62+
Notes taking
63+
64+
* Make 2021 Strategy Meeting - file issue
65+
* Note about the word “Member”
66+
67+
68+
## Q&A, Other
69+
70+
## Upcoming Meetings
71+
72+
* **Calendar**: https://calendar.openjsf.org
73+
74+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
75+
76+

‎meeting-notes/2020.09.08_meeting_notes.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
# OpenJS Foundation Standards Working Group Meeting 2020-09-08
2+
3+
## Links
4+
5+
* **Recording**:
6+
* **GitHub Issue**: $GITHUB_ISSUE$
7+
8+
## Present
9+
10+
* OpenJS Foundation Cross Project Council
11+
* OpenJS Foundation Project Maintainers
12+
* OpenJS Foundation Board of Directors
13+
14+
Brina Kardell
15+
Myles Borins
16+
Eemeli
17+
Jory Burson
18+
Donovan Buck
19+
Jordan Harband
20+
21+
## Agenda
22+
23+
### Announcements
24+
25+
*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
26+
27+
### openjs-foundation/standards
28+
29+
* Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102)
30+
31+
* TPAC Breakout proposals - Discussion regarding ongoing things at W3C, and how OpenJS and W3C can work together. Will be revisited at the end of October. BK will share a schedule and breakouts for TPAC event (https://www.w3.org/wiki/TPAC/2020/GroupMeetings
)
32+
33+
* Possible role for OpenJS Foundation in helping to maintain/steward proposal polyfills for new language features. MDN had been moving towards pointing to NPM packages instead of including polyfills on MDN pages. Not sure what will happen at MDN going forward so can OpenJS help with this? BK will open a new issue for discussion (tag with “standards-agenda”).
34+
35+
* Discussion of opportunities to share information from standards bodies activities with member projects. No role for OpenJS to have early discussion of notes prior to their public release, as attendees will need an opportunity to ensure their words are fairly represented. DB will open a new issue for discussion (tag with “standards-agenda”).
36+
37+
* WICG is creating a new way to create proposals. Might be interesting to various projects (https://github.com/WICG/proposals)
38+
39+
* Discussion around set of “Getting started” resources for community members who are interested.
40+
41+
## Q&A, Other
42+
43+
RG: Re-iterates importance of agendas and notes as they pertains to foundation.
44+
MB: Reminds the group that in the event of little or no events on agenda, we can always cancel.
45+
46+
## Upcoming Meetings
47+
48+
* **Calendar**: https://calendar.openjsf.org
49+
50+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
51+
52+

‎meeting-notes/2020.10.06_meeting_notes.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# OpenJS Foundation Standards Working Group Meeting 2020-10-06
2+
3+
## Links
4+
5+
* **Recording**:https://www.youtube.com/watch?v=34DxEp4x2lk&ab_channel=OpenJSFoundation
6+
* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/108
7+
8+
## Present
9+
10+
* Joe Sepi (@joesepi)
11+
* Robin Ginn
12+
* Myles Borins
13+
* Mike Samuel
14+
* Brian Kardell
15+
* Mike Champion
16+
* Jordan Harband
17+
* Richard Gibson
18+
* Jory Burson
19+
* Donovan Buck (@dtex)
20+
21+
22+
## Agenda
23+
24+
### Announcements
25+
26+
*Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting.
27+
28+
### openjs-foundation/standards
29+
30+
* A home for reference-implementation polyfills [#106](https://github.com/openjs-foundation/standards/issues/106)
31+
BK: Currently in the standards dev process, proposal go from speculative idea polyfill to a “true” polyfill to patch browsers that haven’t added the functionality. Currently there is no way to ensure those polyfills don’t fall subject or bit rot. We need an easy way for those communities to submit their polyfills to a place where they will be maintained and can be shared with the community. That’s the gist. There’s a lot to work out yet.
32+
JH: I am one of the people that maintains widely used JS polyfills. There really isn’t a community that needs collecting and managing. These tend to be “single-maintainer” projects. Unless the foundation is removing obstacles for the maintainers I’m skeptical about this as an idea. Secondly, JS spec implementations already link to polyfills, but makes an effort to not endorse or choose a preferred solution.
33+
BK: There is definitely some conversation to be had about “blessing” a polyfill.
34+
JH: The long term challenge isn’t around creating a polyfill while people are excited about a proposal. Long term maintenance (after browsers start shipping) is the real problem.
35+
JB: So this may not address the needs of polyfill maintainers unless long term maintenance is an added benefit.
36+
MS: Agree with JH. Long-term maintenance is super important.
37+
JH: I think a project that provides tests would be embraced. There isn’t an easy way to run 262 tests against anything that’s not a browser. That’s a problem I’d love to see solved that would definitely help.
38+
MS: So, to restate, being able to run tests on a bunch of different platforms would be helpful.
39+
JH: Many projects out there, whether they be polyfills, transpilers, etc could benefit from the ability to run conformance tests.
40+
JB: Maybe this is a good thing for us to talk about on a higher level.
41+
BK: One of the things we could do is provide a means for actually running tests. I support this.
42+
MB: My gut on this, based on our charter, is that this is something better suited for the collaboration network. I’m not saying this work isn’t important or worthy, but for the sake of our meetings we should be facilitating discussion.
43+
BK: I agree. We have heard from W3C and individual developers about this, so I brought this issue to see if we can facilitate some actual action.
44+
MB: I think the goos path forward would be to set up a Collaboration Space and see if some traction can be established there.
45+
46+
Action Item: Jory and Brian to speak with Micheal Dawson about initializing a space for “Polyfillers”
47+
48+
* Proposals for TC39 [#102](https://github.com/openjs-foundation/standards/issues/102)
49+
50+
FYI - prepping for 2021 Standards strategy session - what questions do we want to try to answer?
51+
* How do we communicate to the broader community - how do we make member projects more aware of what we’re doing?
52+
* Can we poll the projects - how would you like to be represented, how would you like to get involved, etc?
53+
* How do the projects imagine this working?
54+
55+
56+
## Q&A, Other
57+
58+
## Upcoming Meetings
59+
60+
* **Calendar**: https://calendar.openjsf.org
61+
62+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
63+
64+

0 commit comments

Comments
 (0)