Skip to content

Proposal for the initial set of AMP Working Groups#13

Merged
mrjoro merged 6 commits intomasterfrom
mrjoro-wg-initial
Jan 7, 2019
Merged

Proposal for the initial set of AMP Working Groups#13
mrjoro merged 6 commits intomasterfrom
mrjoro-wg-initial

Conversation

@mrjoro
Copy link
Copy Markdown
Member

@mrjoro mrjoro commented Nov 26, 2018

As described in AMP's new governance model (#1), the Technical Steering Committee (TSC) is responsible for creating Working Groups and describing each Working Group's mandate.

This PR proposes the initial set of Working Groups for the TSC to create. The proposal is based on the informal groups that currently operate in the AMP open source project.

A facilitator is also proposed for each Working Group. The person who currently has the most familiarity with each Working Group's area of responsibility is proposed as the facilitator for that Working Group.

The governance model indicates that the TSC also sets the initial membership of each Working Group. For now this proposal only designates the facilitators. The full initial membership of each Working Group will be specified separately.

/cc @cramforce @lannka @choumx @dvoytenko @rsimha @pbakaus @jridgewell @newmuis @aghassemi @spacedino @Gregable @cramforce

@jpettitt
Copy link
Copy Markdown

jpettitt commented Nov 26, 2018

Can we add:

Access Control and Subscriptions

  • Responsible for user specific controlled access to AMP content (amp-subscriptions, amp-access and related extensions)
  • Facilitator: @jpettitt

@mrjoro
Copy link
Copy Markdown
Member Author

mrjoro commented Nov 27, 2018

@jpettitt I've added the Access control & subscriptions WG.

@aghassemi
Copy link
Copy Markdown
Contributor

LGTM

@lannka
Copy link
Copy Markdown

lannka commented Nov 28, 2018

LGTM

Copy link
Copy Markdown
Member

@cramforce cramforce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please hold submission until after the first TSC meeting.

@mrjoro
Copy link
Copy Markdown
Member Author

mrjoro commented Dec 10, 2018

At the request of the TSC I've added a Code of Conduct Working Group (facilitated by @nainar) and a Viewers Working Group (facilitated by @ericfs).


AMP’s Working Groups are:

* **Access control and subscriptions.**
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider replace this list with a search query like wg- into the repository view, so that this auto-updates to the list of active groups. (Or use the project topic feature)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the search query, would this just be a link that people would click to see the repos, e.g. like https://github.com/ampproject?utf8=%E2%9C%93&q=meta&type=&language=

I can do this once we get the repos set up, assuming we're going with per-WG repos.


* **Access control and subscriptions.**
* Responsible for user specific controlled access to AMP content (amp-subscriptions, amp-access and related extensions)
* Facilitator: @jpettitt
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Document this in the working group README. Ideally there is a WG Readme template.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both the WG description and the facilitator?

If we switch to a link to the repo search query, we'll need to put whatever info we want to appear in the repo description. We may not need it in the README as well if we do that.

Copy link
Copy Markdown
Member

@cramforce cramforce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides lots of comments, the actual list is approved by the TSC

@mrjoro
Copy link
Copy Markdown
Member Author

mrjoro commented Jan 7, 2019

I'll merge this in now so we can move forward with getting the WGs set up. I filed #19 to track changing where we document the Working Groups.

@mrjoro mrjoro merged commit c359d50 into master Jan 7, 2019
@mrjoro mrjoro deleted the mrjoro-wg-initial branch January 7, 2019 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants