|
| 1 | +# OpenJS Foundation Standards Working Group Meeting 2023-08-22 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: Meeting was not recorded. |
| 6 | +* **GitHub Issue**: https://github.com/openjs-foundation/standards/issues/255 |
| 7 | + |
| 8 | +## Present |
| 9 | + |
| 10 | +* Brian Kardell (@bkardell) |
| 11 | +* Hemanth HM (@hemanth) |
| 12 | +* Chris de Almeida (@ctcpip) |
| 13 | +* Robin Ginn (@rginn) |
| 14 | +* Jory Burson (@jorydotcom) |
| 15 | +* Richard Gibson (@gibson042) |
| 16 | +* Rick Markins (@rxmarbles) |
| 17 | +* Ethan Arrowood (@Ethan-Arrowood) |
| 18 | +* Jordan Harband (@ljharb) |
| 19 | +* Tobie Langel (@tobie) |
| 20 | +* Lea Verou (@leaverou) |
| 21 | + |
| 22 | +## Agenda |
| 23 | + |
| 24 | +### Announcements |
| 25 | + |
| 26 | +FYI: APAC-friendly TC39-TG3 meetings is tonight at 01 UTC |
| 27 | + |
| 28 | +* Extracted from **cross-project-council-agenda** labeled issues and pull requests from the **openjs-foundation org** prior to the meeting. |
| 29 | + |
| 30 | +### Liaison Reports |
| 31 | + |
| 32 | +* Template for liaison reports #252 [#252](https://github.com/openjs-foundation/standards/issues/252) |
| 33 | + |
| 34 | +### openjs-foundation/standards Agenda |
| 35 | + |
| 36 | +* Create 2023.08.08_meeting_notes.md #257 [#257](https://github.com/openjs-foundation/standards/pull/257) |
| 37 | + - please review! |
| 38 | + |
| 39 | +* update active members #254 [#254](https://github.com/openjs-foundation/standards/pull/254) |
| 40 | + - Merged! |
| 41 | + |
| 42 | +* Check Standards WG agrees to migrate to a Collab Space #253 (https://github.com/openjs-foundation/standards/issues/253) |
| 43 | + - Difference is decision-making authority. No real difference except name. |
| 44 | + - Ref: https://github.com/openjs-foundation/cross-project-council#openjs-collaboration-spaces |
| 45 | + - We would update our charter to call it a collab space and clarify what items we have |
| 46 | + |
| 47 | +* Travel request for Jordan Harband for TC39 #40 [#40](https://github.com/openjs-foundation/community-fund/pull/40) |
| 48 | + - Agreed, assuming Jordan’s amount was factored into the forecasting |
| 49 | + |
| 50 | +* Document Guidance for requesting travel funds for Standards WG-related activities #256 [#256](https://github.com/openjs-foundation/standards/issues/256) |
| 51 | + - Chen. is a champion of a proposal that is benefitting Node. Chen. is a valued member of the TSC. It is clarified that this approval is a one-time approval and not an ongoing approval for future travel |
| 52 | + - We can create/identify some eval criteria. Is this person a community member/leader? Are they presenting the work they have been doing? How will it drive impact? Are they reasonably geographically located? |
| 53 | + - Concern: let’s make sure that the process doesn’t overly favor what looks like high-level impact. Lea’s example of the work of design reviews. Need to make sure the process also works for “Work” |
| 54 | + - An after-event report may not be the most useful activity. |
| 55 | + - What are the travel commitments assumed for participation - e.g. W3C TAG nominees are expected to travel to most of the meetings as part of the nomination process. |
| 56 | + - Staff and CPC are working on processes and guidelines. Considering putting a cap on the expense totals. |
| 57 | + - Proposal - Signal prioritization of standards WG-related travel that are connected to work items that will be discussed |
| 58 | + - Action Item: Create a scope/bucket that defines what kinds of travel fund requests we will be considering/recommending for funding for 2024, and attempt to frontload what those expense requests will be. Need to consider the variables (cost, proximity of location, urgency of requests, deadlines, how long in advance the event was announced/known) Consider recommending things like, asking people to share expenses with another organization. |
| 59 | + - Action Item - Talk to Samina about whether Ecma could create and support a travel fund, and put it on the ExeCom meeting agenda |
| 60 | + - Action Item - Understand from Ben what the balance of the fund |
| 61 | + |
| 62 | +* W3C TPAC 11-15 September 2023 - Break out session? #231 [#231](https://github.com/openjs-foundation/standards/issues/231) |
| 63 | + - Closed |
| 64 | + |
| 65 | +* WIP - Improvements toward Addressing #173 [#240](https://github.com/openjs-foundation/standards/pull/240) |
| 66 | + - Noted that Tobie and Jordan are in alignment a this point |
| 67 | + |
| 68 | +Tabled for time |
| 69 | + |
| 70 | +* Update MEMBER_REPRESENTATION.md [#239](https://github.com/openjs-foundation/standards/pull/239) |
| 71 | + |
| 72 | +* Define terms for SME Participation [#173](https://github.com/openjs-foundation/standards/issues/173) |
| 73 | + |
| 74 | +## Q&A, Other |
| 75 | + |
| 76 | +## Upcoming Meetings |
| 77 | + |
| 78 | +* **Calendar**: <https://calendar.openjsf.org> |
| 79 | + |
| 80 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 81 | + |
0 commit comments