Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the AMP Project? #2

Open
mnot opened this issue Sep 18, 2018 · 6 comments
Open

What is the AMP Project? #2

mnot opened this issue Sep 18, 2018 · 6 comments
Assignees

Comments

@mnot
Copy link

mnot commented Sep 18, 2018

People more-or-less understand AMP the effort and what it's attempting to do.

However, as an entity, it's not clear what the scope of the effort controlled by this governance model is.

So, more crispness around the goals of the project will help people understand what it is and what to expect from it.

E.g., what are AMP's goals? Will the project be producing software, specifications, or both? Will it ever be "done"?

@mnot
Copy link
Author

mnot commented Sep 18, 2018

I.e., what is being governed?

@mrjoro mrjoro self-assigned this Oct 10, 2018
@mrjoro
Copy link
Member

mrjoro commented Oct 10, 2018

Hi @mnot; this is a good question. :)

From a more technical perspective, the AMP Project encompasses the contents of a GitHub organization which includes software, documentation, the project’s marketing website, and specifications, including those that define expectations for the AMP ecosystem, and design docs.

For a slightly more philosophical take, I generally point people toward's AMP's vision and mission.

@tobie we've talked a bit about this in the past; do you have anything else you'd add here?

@tobie
Copy link
Collaborator

tobie commented Oct 10, 2018

There are a few extra assets worth considering once we move the project to a foundation:

  • any trademarks, original designs, etc.
  • the ampproject.org domain name.
  • the associated CDN which hosts the JS files.

@tobie
Copy link
Collaborator

tobie commented Oct 10, 2018

In his review @triblondon made the following comment which seems strongly related to this issue:

Define what AMP 'is', legally: Define the legal status of AMP. In the blog post accompanying this governance model, it says "Additionally, we’re exploring moving AMP to a foundation in the future". So currently, decisions made 'by AMP' are expressing the will of what entity? And when it does move to a foundation, of course it is equally important to document that structure.

@mnot
Copy link
Author

mnot commented Oct 12, 2018

is it an explicit goal for the specifications that the AMP project produces to be standardised by an external body?

@mrjoro
Copy link
Member

mrjoro commented Oct 21, 2019

With AMP joining the OpenJS Foundation I expect there will be more crispness over what "AMP" is, since it has to be clear what is actually moving (as discussed in the OpenJS Foundation onboarding checklist).

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

No branches or pull requests

3 participants