Contributions page #519
Merged
Contributions page #519
Conversation
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
We get a lot of questions about where to start with the TAG or a WG. This page is a great location for us to start supporting people with an easier path into the groups. @techmaharaj and I put together a draft of something we could add here to get started. Signed-off-by: Abby Bangser <[email protected]>
abangser
requested review from
AloisReitbauer,
AlexsJones,
thschue,
joshgav,
lianmakesthings,
kgamanji,
justincormack and
angellk
as code owners
✅ Deploy Preview for tag-app-delivery ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Great work! Thanks for taking this on 👏 |
lianmakesthings
approved these changes
Dec 17, 2023
There is an intention to introduce more community blogs onto the TAG website. This is being particularly pushed by the platforms WG where it is an emergent space and we would like an opportunity to explore some of the ideas with a lower barrier to entry. This will also enable more inclusion as we will encourage and support new voices without requiring 6-12 months of editing. This page is meant to introduce a baseline requirement for all TAG contributions. If this content is approved, it is expected that the WG Platforms will release a blog which further extends this to match the way that WG in particular would like to work with new authors. Signed-off-by: Abby Bangser <[email protected]>
|
Thank you for the rapid review @lianmakesthings !! I have added another commit so will wait for more reviews. I was thinking of making this commit on a new PR, but decided it is connected enough to add here. I can of course pull it out if it is more controversial. This commit is thanks in large part to @earth2marsh and will help us continue to support new authors with more transparency and clarity on what it means to contribute! |
joshgav
approved these changes
Dec 19, 2023
There was a problem hiding this comment.
Thank you for this @abangser and @techmaharaj!
LGTM when you're happy with it!
joshgav
added
website
|
Awesome! Given the double review I am inclined to merge now and update later. For example, we may extend this to include taxonomy descriptions as mentioned in #518 but I think that is likely a month out so not necessary to hold this PR up for that. Thanks all both for the contributions and speedy reviews! |
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Dec 19, 2023
We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modeled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Signed-off-by: Abby Bangser <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Dec 20, 2023
We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modeled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Dec 20, 2023
We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modeled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Dec 20, 2023
We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modeled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Dec 20, 2023
We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modelled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]>
hhiroshell
added a commit
to hhiroshell/tag-app-delivery
that referenced
this pull request
Dec 20, 2023
c.f. cncf#519 Signed-off-by: Hiroshi Hayakawa <[email protected]>
abangser
added a commit
that referenced
this pull request
Dec 21, 2023
* Introduce more guidance on getting start contributing We have made awesome strides by introducing more contributing guides to the website in #519. This closes #495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modelled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]> Co-authored-by: Atulpriya Sharma <[email protected]>
joshgav
pushed a commit
that referenced
this pull request
Jan 9, 2024
* add Japanese contents * copy the English contents to the Japanese directory * translate website/config.toml and website/i18n/ja.toml * Introduce taxonomy for blog pages under content/ja. c.f. #518 * translate the titles of each page and the descriptions of second-level pages * translate the top page of the website * translate "Initiative " to 「取り組み」 * add contributions pages to the jp contents c.f. #519 * Copy new en blog contents to content/ja/ c.f. #523 * correct the omission in the translation of 'packaging'. * translate "TAG App Delivery" to 「TAG Appデリバリー」 * translate "TAG App Delivery" to 「TAG Appデリバリー」 * remove the "url" property to prevent overwriting the default language with the translated version. * translate descriptions of each page to jp. * fix for slack channel name c.f. hhiroshell@f3a4854 --------- Signed-off-by: Hiroshi Hayakawa <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Jan 11, 2024
* Contributions page We get a lot of questions about where to start with the TAG or a WG. This page is a great location for us to start supporting people with an easier path into the groups. @techmaharaj and I put together a draft of something we could add here to get started. Signed-off-by: Abby Bangser <[email protected]> * Introduce blog contribution standards There is an intention to introduce more community blogs onto the TAG website. This is being particularly pushed by the platforms WG where it is an emergent space and we would like an opportunity to explore some of the ideas with a lower barrier to entry. This will also enable more inclusion as we will encourage and support new voices without requiring 6-12 months of editing. This page is meant to introduce a baseline requirement for all TAG contributions. If this content is approved, it is expected that the WG Platforms will release a blog which further extends this to match the way that WG in particular would like to work with new authors. Big thanks to @earth2marsh for putting together the key points for this policy! Signed-off-by: Abby Bangser <[email protected]> --------- Signed-off-by: Abby Bangser <[email protected]>
abangser
added a commit
to abangser/tag-app-delivery
that referenced
this pull request
Jan 11, 2024
* Introduce more guidance on getting start contributing We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modelled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]> Co-authored-by: Atulpriya Sharma <[email protected]>
abangser
pushed a commit
to abangser/tag-app-delivery
that referenced
this pull request
Jan 11, 2024
* add Japanese contents * copy the English contents to the Japanese directory * translate website/config.toml and website/i18n/ja.toml * Introduce taxonomy for blog pages under content/ja. c.f. cncf#518 * translate the titles of each page and the descriptions of second-level pages * translate the top page of the website * translate "Initiative " to 「取り組み」 * add contributions pages to the jp contents c.f. cncf#519 * Copy new en blog contents to content/ja/ c.f. cncf#523 * correct the omission in the translation of 'packaging'. * translate "TAG App Delivery" to 「TAG Appデリバリー」 * translate "TAG App Delivery" to 「TAG Appデリバリー」 * remove the "url" property to prevent overwriting the default language with the translated version. * translate descriptions of each page to jp. * fix for slack channel name c.f. hhiroshell@f3a4854 --------- Signed-off-by: Hiroshi Hayakawa <[email protected]>
sysnet4admin
pushed a commit
to sysnet4admin/tag-app-delivery
that referenced
this pull request
Feb 24, 2024
* Contributions page We get a lot of questions about where to start with the TAG or a WG. This page is a great location for us to start supporting people with an easier path into the groups. @techmaharaj and I put together a draft of something we could add here to get started. Signed-off-by: Abby Bangser <[email protected]> * Introduce blog contribution standards There is an intention to introduce more community blogs onto the TAG website. This is being particularly pushed by the platforms WG where it is an emergent space and we would like an opportunity to explore some of the ideas with a lower barrier to entry. This will also enable more inclusion as we will encourage and support new voices without requiring 6-12 months of editing. This page is meant to introduce a baseline requirement for all TAG contributions. If this content is approved, it is expected that the WG Platforms will release a blog which further extends this to match the way that WG in particular would like to work with new authors. Big thanks to @earth2marsh for putting together the key points for this policy! Signed-off-by: Abby Bangser <[email protected]> --------- Signed-off-by: Abby Bangser <[email protected]> Signed-off-by: Hoon Jo <[email protected]>
sysnet4admin
pushed a commit
to sysnet4admin/tag-app-delivery
that referenced
this pull request
Feb 24, 2024
* Introduce more guidance on getting start contributing We have made awesome strides by introducing more contributing guides to the website in cncf#519. This closes cncf#495 by introducing both a detailed blog post and an accompanying issue template which can support organising people's thoughts and provide the TAG with more information to support new ideas. This is heavily modelled after the sandbox template but of course needs to be much more light weight. One thing that has been removed but may need to be re-added is a reference to who owns IP from any contribution. Big thanks to @techmaharaj for a lot of the content and the first review of this PR. Signed-off-by: Abby Bangser <[email protected]> Co-authored-by: Atulpriya Sharma <[email protected]> Signed-off-by: Hoon Jo <[email protected]>
sysnet4admin
pushed a commit
to sysnet4admin/tag-app-delivery
that referenced
this pull request
Feb 24, 2024
* add Japanese contents * copy the English contents to the Japanese directory * translate website/config.toml and website/i18n/ja.toml * Introduce taxonomy for blog pages under content/ja. c.f. cncf#518 * translate the titles of each page and the descriptions of second-level pages * translate the top page of the website * translate "Initiative " to 「取り組み」 * add contributions pages to the jp contents c.f. cncf#519 * Copy new en blog contents to content/ja/ c.f. cncf#523 * correct the omission in the translation of 'packaging'. * translate "TAG App Delivery" to 「TAG Appデリバリー」 * translate "TAG App Delivery" to 「TAG Appデリバリー」 * remove the "url" property to prevent overwriting the default language with the translated version. * translate descriptions of each page to jp. * fix for slack channel name c.f. hhiroshell@f3a4854 --------- Signed-off-by: Hiroshi Hayakawa <[email protected]> Signed-off-by: Hoon Jo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We get a lot of questions about where to start with the TAG or a WG. This page is a great location for us to start supporting people with an easier path into the groups.
@techmaharaj and I put together a draft of something we could add here to get started.