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

CNCF TOC: State of the Ecosystem Assessment - Due by November 1st, 2024 #182

Open
angellk opened this issue Aug 29, 2024 · 3 comments
Open
Assignees

Comments

@angellk
Copy link

angellk commented Aug 29, 2024

Each TAG is being asked by the CNCF TOC to provide an assessment summary of their domain, due by November 1st, 2024.

Intent

The intent of this assessment is to ascertain where the ecosystem is nearing comprehensiveness, where there are opportunities of innovation, and to redirect focus of community members to active areas of interest and need by projects and adopters.

Our Request

We ask each TAG:

  • Prepare a 1 page document that addresses the prompt questions below.
  • Engage your WGs to provide no more than 3-5 sentences that address the prompt questions.
  • WG responses are in addition to the 1 page document covering the breadth of the TAG
  • Please provide the information no later than November 1st 2024.

The TOC will review these reports prior to KubeCon North America and develop a plan of action for public review before the end of the calendar year.

Why?

The resulting State of the ecosystem will become a public report to the community and will serve to guide the TOC in restructuring our advisory groups and their working groups to address the problems of today and tomorrow against the realities of current contributions and participation in our groups and projects.

Prompt Questions

  1. How do you see the completeness of the ecosystem in your specific domain? Are there any specific areas not properly covered by the projects in our ecosystem?
  2. How do you see the alignment between different projects in the specific domain of your TAG (with examples)? And do you see close alignments with projects in other domains?
  3. Are there particular challenges in the TAG’s area, both current and foreseen for the upcoming years?
  4. Do you see areas of overlap with other TAGs or individual WGs? If so, which ones?
  5. How do you see the overall status of project health?
  6. How do you see the overall trend of innovation and new projects or capabilities in your domain?
  7. For each WG in your TAG,
    • Has their initial purpose been completed?
    • Are the WG’s artifacts and deliverables a service provided to projects or the TOC? I.e. security reviews, governance reviews, etc.
    • Has the WG reassessed its progress towards its initial goals?
    • Is there an updated timeline for the WG to accomplish its goals?
    • Does the WG feel additional effort and focus needs to be conducted to close gaps of their sub-domain within the ecosystem?
@raravena80 raravena80 self-assigned this Sep 4, 2024
@angellk
Copy link
Author

angellk commented Sep 15, 2024

@raravena80 Could you please help set up a check point on this with TAG leads and TOC liaisons for first week of October?

@raravena80
Copy link
Collaborator

@angellk can you specify what a 'checkpoint' is? (meeting? async doc? anything? something else? what are other TAGs doing?) Thx.

@angellk
Copy link
Author

angellk commented Sep 20, 2024

Hi @raravena80 - this can either be discussed during the leads meeting mentioned in slack, or an async draft review.

TAGs will be reminded to share drafts with their TOC liaisons during the October 1st public meeting.

cc: @cathyhongzhang @dims

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

No branches or pull requests

2 participants