TSC Meeting #28 2020-07-29 20:00 UTC

[rudygalfi]

Agenda

• Discuss adding a message to support Black Lives Matter on amp.dev (PR as context: add #BlackLivesMatter banner amp.dev#4235)
• Review TSC issue backlog
• Review TSC-tagged issues (toggle to "open" after checking for recently "closed" items)

@ampproject/tsc

@tobie Can you specify AC attendees?

[rudygalfi]

I've added a topic to the agenda. I'd like to discuss adding a message to support Black Lives Matter to amp.dev (this was suggested by a community member).

[rudygalfi]

Notes:

• Discuss adding a message to support Black Lives Matter on amp.dev (PR as context: add #BlackLivesMatter banner amp.dev#4235)
  • Clarifying scope of proposal: Is it just a banner? Does it link out?
    • Varying implementations
  • Does TSC own decisions like this?
    • OpenJS Foundation transition is complete, so it shouldn’t be Google
    • Where does this kind of policy get set?
    • We should clarify which body sets these kinds of policies?
      • Outreach WG should be empowered to set these kinds of things and FYI to TSC, including in this instance.
  • Should this kind of thing be just reactive, or should proposals in any circumstance be brought to the TSC?
    • It’s OK to just FYI. We should trust until trust is broken.
    • Outreach WG has delegated authority to handle matters like these and provide an FYI to the TSC.
    • Outreach WG should look to document in some place
• Review TSC issue backlog
  • We merged the PR to add Kasiana’s name to the TSC list
• Review TSC-tagged issues (toggle to "open" after checking for recently "closed" items)
  • Open source storybook-addon-amp meta#57
    • This seems to have followed the process outlined by the TSC for new repos being created.
    • TSC acknowledged as FYI