TSC Meeting #2 2019-01-16

[cramforce]

Agenda

• [wg-codeofconduct] Publishing a year end transparency report generated by the CoC WG and approved by the TSC and any other parties.

• Finalize code review requirements Collaborator / OWNER status requirements #3

• Decision making process for new working groups. Example Splits the Ads & analytics Working Group into two WGs meta#21

• Non-technical work and TSC intersection (marketing / outreach)

• First in-person meeting!

• Visibility of mailing list (ampproject.org currently only allows org-private, may be able to change that)

• Approval of the WG initial membership

  • Suggestion for approvers group: Start with Fascilitators of existing groups + @jridgewell
  • Malte: Let's talk about our role in membership going forward.

Minutes

[cramforce]

CC @ampproject/tsc

[paularmstrong]

Can we also discuss our first in-person meeting for 2019? Some ideas were floated around, but nothing was finalized. Looking to get a more concrete heads-up for planning/travel.

[cramforce]

Added to Agenda. Also related: As of today folks can register for AMP Conf (y'all don't need to do this, just FYI) https://www.ampproject.org/amp-conf/

[nainar]

CoC WG has a topic to add to the agenda:

Publishing a year end transparency report generated by the CoC WG and approved by the TSC and any other parties.

[mrjoro]

I'd propose adding approval of the WG initial membership to the agenda. The facilitators are adding the proposed initial membership to the WG GitHub teams by the end of day tomorrow (2019-01-15).

[rudygalfi]

@cramforce There have been a couple additional proposals for agenda items from @nainar and @mrjoro. Should these two items both be incorporated into update #4 (comment)?

[rudygalfi]

I've incorporated @nainar's and @mrjoro's agenda topic suggestions into the agenda.

[nainar]

The CoC WG issue re:transparency reports can be found here: ampproject/wg-codeofconduct#4

[cramforce]

Minutes

[wg-codeofconduct] Publishing a year end transparency report generated by the CoC WG and approved by the TSC and any other parties.

• Proposal presented by @nainar, Google
• Anonymize the report
• We should publish transparency report even if we do little to nothing.
• Next step: Create an issue in wg-codeofconduct with the proposal and provide TSC with a link

Finalize code review requirements #3

• Change after previous meeting: Addition of "Reviewer status" rules: "Alternatively it may also be granted after 10 high quality reviews of complex PRs and a +1 from 1 reviewer."
• Do we have a define process written up for someone to get new status once they feel they have met the requirements?
• Not in there yet.
• Suggestion: File an issue. Malte will update the text.
• All good to proceed

Non-technical work and TSC intersection (marketing / outreach)

• Examples: AMP Conf is being executed by Google marketing team; these folks are not part of open-source process. New website. Publishing case studies.
• Fedora is a good model to study. David could study and set us up with contacts.
• Proposal: roll this kind of thing into a new working group
• How can non-technical people achieve the transparency we expect?
• Idea: Before new events, send a heads up to see if there's an interest to fund, help host.
• We have an outreach working group.
• Malte and Rudy to engage with Google folks impacted by this, share this meeting's discussion and suggest bringing a proposal back to TSC.

First in-person meeting [of the year]!

• Most of us attending AMP Conf
• Should do a panel?
• We've previously done leadership panels
• Need a moderator
• Have reps from WGs in the panel?
• For now, target AMP Conf for in-person meeting. (Update: All can attend)
• Reserve Tues 16th

Visibility of mailing list (ampproject.org currently only allows org-private, may be able to change that)

• Is it possible to change visibility of mailing list for GSuite account to public? Might need to contact GSuite admin.
• Public view, public post, invite-only membership

Approval of the WG initial membership

• wg-approvers still needs more members
• Proposal to add Facilitators of existing groups + @jridgewell (Approved)
• wg-amp4email only has 1 member
• Ask someone from Gmail to join
• Rename wg-ui to wg-ui-and-a11y
• Approved by the TSC
• Decision making process for new working groups. Example ampproject/meta#21
• Roll over to next time

[aghassemi]

Renaming wg-ui to wg-ui-and-a11y is now completed across GitHub and Slack.