Updated the contributor strategy calendar link. #311
Merged
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
…me of the wording after the link so that it makes more sence. Signed-off-by: dankingkong <[email protected]>
|
Hi @carolynvs, fixed the Contributor Strategy calendar link and made my first PR using git with the terminal. Dan |
carolynvs
approved these changes
Jan 24, 2023
|
No problem, glad I can help.
I am keen to keep practicing and learning new skills with Git and making
contributions. If you have any more low level issues that I can help
with let me know.
I have also completed the Kubernetes and Cloud Native Essentials (LFS250)
course and I'd be keen to start getting into some low level K8's
contributes.
Dan 🙂
…On Wed, Jan 25, 2023 at 4:34 AM Carolyn Van Slyck ***@***.***> wrote:
Merged #311 <#311>
into main.
—
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3R5TELZ7GLRT5NDUHF72KDWT7ZBFANCNFSM6AAAAAAUEM3YS4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@dankingkong Would you be interested in helping to kick start our glossary of terms related to how CNCF and its projects are organized? |
|
This looks interesting, I'm currently doing an internship with ii Limited,
so I will have a chat with Riaan and Hippie about helping with this issue.
Cheers
Dan
…On Wed, Jan 25, 2023 at 11:15 AM Carolyn Van Slyck ***@***.***> wrote:
@dankingkong <https://github.com/dankingkong> Would you be interested in
helping to kick start our glossary of terms related to how CNCF and its
projects are organized?
#140 <#140>
—
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3R5TEIZY4MNT4YV6OETVJLWUBIABANCNFSM6AAAAAAUEM3YS4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi Carolyn,
I will have a crack at working on issue #140
<#140> for you.
Thanks
Dan
On Wed, Jan 25, 2023 at 11:51 AM Daniel King ***@***.***>
wrote:
… This looks interesting, I'm currently doing an internship with ii Limited,
so I will have a chat with Riaan and Hippie about helping with this issue.
Cheers
Dan
On Wed, Jan 25, 2023 at 11:15 AM Carolyn Van Slyck <
***@***.***> wrote:
> @dankingkong <https://github.com/dankingkong> Would you be interested in
> helping to kick start our glossary of terms related to how CNCF and its
> projects are organized?
>
> #140 <#140>
>
> —
> Reply to this email directly, view it on GitHub
> <#311 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A3R5TEIZY4MNT4YV6OETVJLWUBIABANCNFSM6AAAAAAUEM3YS4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
Great, thank you! 🎉 Please let me know if you have questions and just ask on that issue. I realize that this is a larger and less well-defined task so some decisions will need to be made as you work on it. |
|
Hi Carolyn,
I have been working on the glossary. I have cloned the Cloud Native
Glossary and I am using it as a template. We have a public holiday on
Monday, so I will continue to work on it on Tuesday 1st Jan.
Cheers
Dan
…On Thu, Jan 26, 2023 at 7:40 AM Carolyn Van Slyck ***@***.***> wrote:
Great, thank you! 🎉 Please let me know if you have questions and just
ask on that issue. I realize that this is a larger and less well-defined
task so some decisions will need to be made as you work on it.
—
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3R5TEMBAFHP3K5WDR3CPADWUFXQHANCNFSM6AAAAAAUEM3YS4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@dankingkong Please keep in mind that the glossary should be located on our existing site. If you start off from a clone of another website, it will be difficult to integrate that into ours. I suggest starting with making a new Hugo section named glossary in https://github.com/cncf/tag-contributor-strategy/tree/main/website/content and then create an index page that explains the scope of the glossary and then start defining some of our initial suggested terms. Focus on the content first, and then the web design as that part is easy to get stuck on. |
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.
Updated the link as per #197
Contributor Strategy calendar has been updated.
I also noticed that some of the wording after the calendar links was not needed, so I have deleted that so its less confusing.