Skip to content

Latest commit

 

History

History
45 lines (34 loc) · 1.92 KB

PROCESS.md

File metadata and controls

45 lines (34 loc) · 1.92 KB

Process Document

This document captures some of the administrative processes used to manage the AC in accordance with its working mode.

Stakeholder Input Process

Steps to take when an AC work item has been identified:

  • New issue is raised by stakeholder
  • Brought to the AC for discussion
  • The AC identifies clear desired outcomes for the issue
  • Issue is assigned to a champion (if no champion signs up, the issue is closed until a champion steps up)
  • Champion brings issue to the TSC and/or the relevant Working Groups (WG), either by filing an issue or joining a meeting
  • Champion drives the issue to resolution in collaboration with TSC/WG and stakeholder
  • Issue is brought back to the AC which recognizes desired outcomes have been reached, approves alternative outcomes, or suggests remediations
  • Issue resolution is documented
  • Resolution is published on the AMP blog

Adding or Removing AC Members

Steps to take when bringing in (or saying farewell) to AC reps:

Onboarding Checklist

  • Add member to AC mailing list
  • Add member to ampproject organization on GitHub
  • Add member to AC team on GitHub
  • Add member to recurring meeting calendar invite
  • Update /meta-ac README
  • Update Roster Spreadsheet
  • Add member to the meeting notes template
  • Add member to the AMP Slack Workspace and the #amp-ac channel
  • Invite member for an onboarding meeting to get up to speed on current AC activities
  • Once added, send welcome email to the AC list for introductions

Off-boarding Checklist

  • Remove member from AC mailing list
  • Remove member from AC team on GitHub
  • Remove member from recurring meeting calendar invite
  • Update /meta-ac README
  • Update Roster Spreadsheet
  • Remove member from the meeting notes template
  • Farewell & contact update email for AC reps to maintain friendships/connections