-
Notifications
You must be signed in to change notification settings - Fork 205
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
Introduce more guidance on getting start contributing #523
Conversation
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]>
✅ Deploy Preview for tag-app-delivery canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to go. Left minor suggestions.
Co-authored-by: Atulpriya Sharma <[email protected]> Signed-off-by: abangser <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this! Thanks so much for your work.
One thing: the "Getting started with contributing in WG Platforms" doesn't seem to show up in the deploy preview. Not sure what's going on there. Maybe I'm missing something.
Very detailed with encouraging guidance. Looks great to me! |
c4a9558
to
025e8d5
Compare
Doh! @lianmakesthings I made an assumption that it would take some time to get reviews so I post-dated it to Dec 22. This meant it wouldn't show up on the blog. I just updated the date to today and confirmed locally that it shows up now. I expected a preview deploy to occur again but it keeps coming up as canceled 🤔 This may need to be either on trust or verified locally. So sorry! |
Signed-off-by: Abby Bangser <[email protected]>
025e8d5
to
aee724e
Compare
No worries. Maybe you could just put the PR in draft mode if you're not ready for an "official" review yet. I tend to try to get reviews out of the way asap, so maybe I'm just too quick (or too thorough 😂 ) |
This was definitely ready for review. I just didn't realise that was how the dates worked :til: So there are two things I guess... 1) is the content reasonable and 2) does it show up on the site. Unfortunately the preview deploy isn't coming up for my change and I am not sure why not. So for #2 it unfortunately can only be validated locally 😢 |
@joshgav @cjyabraham I remember you were trying to figure out why new commits in a PR don't trigger a rebuild of the deploy preview. Did you come to any solutions? |
The deploy preview is here: https://deploy-preview-523--tag-app-delivery.netlify.app/blog/contributing-to-wg-platforms/ I'm not sure why netlify is reporting that the deploy is cancelled since it is built and seems up-to-date to me. You can find the link to deploy previews by inspecting a commit and clicking on "Details": |
c.f. cncf#523 Signed-off-by: Hiroshi Hayakawa <[email protected]>
* 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]>
* 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]>
* 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]>
* 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]>
* 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]>
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.