Skip to content
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

TAG Documentation Update: TAG Network #42

Closed
riaankleinhans opened this issue Jul 5, 2024 · 7 comments · Fixed by cncf/toc#1395 · May be fixed by #45
Closed

TAG Documentation Update: TAG Network #42

riaankleinhans opened this issue Jul 5, 2024 · 7 comments · Fixed by cncf/toc#1395 · May be fixed by #45

Comments

@riaankleinhans
Copy link
Contributor

This issue supports updating the TAG README, Charter and moving documents to the TAG’s Gdrive. The work will be tracked in the TOC Tracking issue #1366.

The following points should be addressed:

  • PR updating TAG repo README in accordance to the template
  • PR removing TAG repo charter
  • PR updating TAG charter in the TOC repo charter folder according to the template
    The aim of this update is to ensure that no information is lost from the TAG’s repo level charter.
  • Move all TAG related shared documents ( Like meeting notes and slides ) to the [email protected] drive for the TAG.
    The aim of this update is to ensure no documents get lost in private or company accounts. Reach out to @riaankleinhans for assistance on that.
@riaankleinhans riaankleinhans changed the title TAG Documentation Update: TAG Security TAG Documentation Update: TAG Network Jul 5, 2024
@riaankleinhans
Copy link
Contributor Author

Created a PR to add TAG Network identifiers in the landscape.yml file to the projects listed on the TAG Network README.
This would allow of updating the README according to the temple, omitting listed projects and adding a filtered TAG Network landscape link.

@rohitsrma
Copy link

Hello @riaankleinhans, I would like to work on this issue. Would it be alright if I address one point at a time and create a PR for each? For example, the first step could be to arrange the README file according to the template.

@riaankleinhans
Copy link
Contributor Author

Hello @riaankleinhans, I would like to work on this issue. Would it be alright if I address one point at a time and create a PR for each? For example, the first step could be to arrange the README file according to the template.

Thank you @rohitsrma for the offer. This issue is spread over a few repos and I already have it as a work in progress locally. Should push PRs before the end of this week.

@riaankleinhans
Copy link
Contributor Author

Hello @riaankleinhans, I would like to work on this issue. Would it be alright if I address one point at a time and create a PR for each? For example, the first step could be to arrange the README file according to the template.

Thank you @rohitsrma for the offer. This issue is spread over a few repos and I already have it as a work in progress locally. Should push PRs before the end of this week.

@rohitsrma I could guide you on addressing this issue if you are still open to it.
The work in the TOC repo is created in #1395

What remain to be done here is:

  • Update the README according to the template
  • You could also refer to the competed README update linked here

@nicholasjackson @ZackButcher @leecalcote for comment here as well

@rohitsrma
Copy link

Hello @riaankleinhans, I would love to work on this, but it looks like there is already a PR up.

@riaankleinhans
Copy link
Contributor Author

riaankleinhans commented Aug 13, 2024

Hello @riaankleinhans, I would love to work on this, but it looks like there is already a PR up.

Yes, This PR is done. But there is more work to be done over here
Look at the context, review all the PRs already created, review the templates.
Would be great if you want to pick up one of the other TAG's updates.

@rohitsrma
Copy link

Hello @riaankleinhans, I would love to work on this, but it looks like there is already a PR up.

Yes, This PR is done. But there is more work to be done over here
Look at the context, review all the PRs already created, review the templates.
Would be great if you want to pick up one of the other TAG's updates.

Thank you! I'll go through these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants