-
Notifications
You must be signed in to change notification settings - Fork 54
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
Comments
I.e., what is being governed? |
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? |
There are a few extra assets worth considering once we move the project to a foundation:
|
In his review @triblondon made the following comment which seems strongly related to this issue:
|
is it an explicit goal for the specifications that the AMP project produces to be standardised by an external body? |
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). |
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"?
The text was updated successfully, but these errors were encountered: