-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of github.com:ampproject/amphtml
- Loading branch information
Showing
169 changed files
with
6,655 additions
and
3,620 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
--- | ||
name: Release tracking issue | ||
about: Create a tracking issue for a new AMP release (to be used by release on-duty | ||
engineers) | ||
title: "\U0001F684 Release tracking issue for release <RELEASE_NUMBER>" | ||
labels: 'Type: Release' | ||
assignees: '' | ||
|
||
--- | ||
|
||
# Release tracking issue | ||
|
||
<!-- | ||
Note to onduty: | ||
Use this issue to track a release from the initial canary release build through | ||
production. The community uses this issue to keep track of what is going on | ||
with the release so please keep this issue up to date: | ||
- As you reach each stage of the release, check the appropriate checkbox and replace <CL submit time> with the "Submitted" text from the corresponding CL, e.g. "2:49 PM, Jul 25, 2018 UTC-4". | ||
- If you need to perform cherry picks, add new checkboxes here (by editing this | ||
issue), making sure to use the release number for the new build. Link the | ||
release number to the GitHub tag page the first time a given release number | ||
appears in the checkboxes. | ||
- Add any updates that may be of interest to the community (such as delays) as | ||
comments on this issue, including after the release is pushed to production. | ||
- Keep the title of the issue updated to reflect whether this issue is tracking | ||
the Canary or the build in Production. | ||
Note: remove the backticks (``) from the link. | ||
--> | ||
|
||
- [x] Release `[<RELEASE_NUMBER>](https://github.com/ampproject/amphtml/releases/tag/<RELEASE_NUMBER>)` is cut as a new canary release | ||
- [ ] Release <RELEASE_NUMBER> pushed to dev channel (<CL submit time>) | ||
- [ ] Release <RELEASE_NUMBER> pushed to 1% (<CL submit time>) | ||
- [ ] Release <RELEASE_NUMBER> pushed to production (<CL submit time>) | ||
|
||
<!-- | ||
If you perform cherry picks, add/update the checkboxes above as needed e.g. | ||
- [ ] Release `[<CHERRY_PICK_RELEASE_NUMBER>](...)` created with cherry picks. | ||
- [ ] Release <CHERRY_PICK_RELEASE_NUMBER> pushed to Dev Channel | ||
--> | ||
|
||
See the [release documentation](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md) for more information on the release process, including how to test changes in the Dev Channel. | ||
|
||
If you find a bug in this build, please file an [issue](https://github.com/ampproject/amphtml/issues/new). If you believe the bug should be fixed in this build, follow the instructions in the [cherry picks documentation](https://bit.ly/amp-cherry-pick). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,49 +1 @@ | ||
# The AMP open source project code of conduct | ||
|
||
All members, committers and volunteers in this community are required to act according to the following code of conduct. We encourage you to follow these guidelines, which help steer our interactions, keep the AMP Project a positive, growing project and community and provide and ensure a safe environment for everyone. | ||
|
||
## Responsible and enforcing this code of conduct | ||
|
||
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact us immediately: contact Malte Ubl (malte.ubl+coc@gmail.com) or Dima Voytenko dimav+coc@google.com. We are here to help you. Your reports will be taken seriously and not dismissed or argued with. | ||
|
||
## What we believe in and how we act | ||
|
||
- We are committed to providing a friendly, safe and welcoming environment for everyone, regardless of gender, sexual orientation, personal ability or disability, ethnicity, religion, level of experience, set of skills or similar personal characteristics. | ||
- Our community is based on mutual respect, tolerance, and encouragement. | ||
- We believe that a diverse community where people treat each other with respect is stronger, more vibrant and has more potential contributors and more sources for ideas. We aim for more diversity. | ||
- We are kind, welcoming and courteous to everyone. | ||
- We’re respectful of others, their positions, their skills, their commitments and their efforts. | ||
- We’re attentive in our communications, whether in person or online, and we're tactful when approaching differing views. | ||
- We are aware that language shapes reality. Thus, we use inclusive, gender-neutral language in the documents we provide and when we talk to people. When referring to a group of people, we aim to use gender-neutral terms like “team”, “folks”, “everyone”. (For details, we recommend [this post](https://modelviewculture.com/pieces/gendered-language-feature-or-bug-in-software-documentation)). | ||
- We respect that people have differences of opinion and criticize constructively. | ||
|
||
## Don't | ||
|
||
- Don’t be mean or rude. | ||
- Don’t discriminate against anyone. Although we have phrased the formal diversity statement generically to make it all-inclusive, we recognize that there are specific attributes that are used to discriminate against people. In alphabetical order, some of these attributes include (but are not limited to): age, culture, ethnicity, gender identity or expression, national origin, physical or mental difference, politics, race, religion, sex, sexual orientation, socio-economic status, and subculture. We welcome people regardless of these or other attributes. | ||
- Sexism and racism of any kind (including sexist and racist “jokes”), demeaning or insulting behaviour and harassment are seen as direct violations to this code of conduct. Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, inappropriate physical contact, and unwelcome sexual attention. | ||
- On IRC, Slack and other online or offline communications channels, don't use overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all. | ||
- Unwelcome / non-consensual sexual advances over IRC or any other channels related with this community are not okay. | ||
- Derailing, tone arguments and otherwise playing on people's desires to be nice are not welcome, especially in discussions about violations to this code of conduct. | ||
- Please avoid unstructured critique. | ||
- Likewise, any spamming, trolling, flaming, baiting or other attention-stealing behaviour is not welcome. | ||
|
||
## Consequences for violations of this code of conduct | ||
|
||
If a participant engages in any behavior violating this code of conduct, the core members of this community may take any action they deem appropriate, including warning the offender or expulsion from the community, exclusion from any interaction and loss of all rights in this community. | ||
|
||
## Decisions about consequences of violations | ||
|
||
Decisions about consequences of violations of this code of conduct are being made by this community's core committers and will not be discussed with the person responsible for the violation. | ||
|
||
## For questions or feedback | ||
|
||
If you have any questions or feedback on this code of conduct, we're happy to hear from you: amphtml-coc@googlegroups.com (Private group; posts are not publicly visible; access is limited to selected committers) | ||
|
||
## Thanks for the inspiration | ||
|
||
This code of conduct is based on the [Hoodie Community Code of Conduct](http://hood.ie/code-of-conduct/), with permission. | ||
|
||
## License | ||
|
||
This page is licensed as [CC-BY-NC](http://creativecommons.org/licenses/by-nc/4.0/). | ||
See https://github.com/ampproject/meta/blob/master/CODE_OF_CONDUCT.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
/** | ||
* Copyright <%= YEAR %> The AMP HTML Authors. All Rights Reserved. | ||
* | ||
* Licensed under the Apache License, Version 2.0 (the "License"); | ||
* you may not use this file except in compliance with the License. | ||
* You may obtain a copy of the License at | ||
* | ||
* http://www.apache.org/licenses/LICENSE-2.0 | ||
* | ||
* Unless required by applicable law or agreed to in writing, software | ||
* distributed under the License is distributed on an "AS-IS" BASIS, | ||
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.