- Determine how we will vote our 👍/👎
- Determine what we will need or want to know or have addressed
- Future handling of documenting or tracking confidential work items or decisions
Reminder of who is next in the rotation
🎉 @tonyganch
- PR a revision to the first warning response and @ the working group
- Create a PR about the policy around leaves
- PR a revision to the first warning response and @ the working group
- Update leave policy to include GitHub org modifications
- OpenJS vote: simple majority
- OpenJS vote: What do we need to know?
- What would affect the Community and Safety Working Group?
- Assumption: the foundation would allow us to operate independently, no structural changes
- Assumption: vote is only to pursue the option, not to finalize the decision
- What do we want to have answered by the end of the "quiet period"
- Are there any organizational imperatives imposed by the foundation? Board of directors? Responsibilities of working group chairs?
- We'll probably think of more after the presentation on Monday
- Meeting note system
- Publish the unredacted meeting notes to the private repository
- At next meeting, agree on items to redact and then publish to public repository
- Old meeting notes?
- Decision: Aspirationally, we'll redact and publish the old meeting notes from the Google doc to the public repository
- @sofianguy
- @lee-dohm
- @codebytere
- @jkleinsc
- @groundwater