TAG Observability Wiki - Githubissues

AnaisUrlichs commented 10 months ago

As mentioned on Slack, lots of the information shared in conversations and written chats is getting lost. Separately, whitepapers need a long time to be created and become outdated or only get updated by a small group of people. (This is partially due to the formal nature of a whitepaper.) https://cloud-native.slack.com/archives/CTHCQKK7U/p1699643328722899?thread_ts=1699583604.842659&cid=CTHCQKK7U

There are lots of open issues for the whitepaper and I wonder if those could be addressed faster if people were not asked to contribute to a whitepaper but to a wiki.

Additionally, it would be great to have a place where professionals in the space can share their knowledge and use case "solutions"/approaches. These might be based on informal conversations, formal discussions, or use cases - such as those presented at KubeCon.

Difference to Observability Whitepaper:

More dynamic -- the Wiki can be based on multiple more minor discussions and informal working groups
Rather than focusing on explanations and theory, the wiki could be more centred around use cases and CNCF projects as well as locations where additional information can be found i.e. the goal should not be to repeat already available information but to make resources more accessible. I would think of it as an "evolving document".

To me, this seems aligned with the scope of the TAG; by formalising conversations and working towards contributions to the Wiki, it is easier to identify gaps, curate information, educate and inform users etc.

Maybe people in the TAG already thought about something similar, or there have already been conversation related etc. 🙂

kenfinnigan commented 10 months ago

Thanks for raising this concern @AnaisUrlichs.

I'd be interested in hearing your thoughts whether what you've described would fit within the Observe k8s WG that the TAG operators?

AnaisUrlichs commented 10 months ago

Hi @kenfinnigan -- I guess it could be one of the objectives to kick-start a Wiki, define goals, and processes so that people outside the working group also know how to contribute? Ideally, the Wiki should survive the working group -- it could be under the repo proposed/worked on

I mean these are all my takes, I am sure some people have different ideas and I would love to hear them, too

caioroscelly commented 10 months ago

Hi. Hope you are good.

I wrote this after some research and wanted to hear your toughts on the TAG Observability landing page.

https://cloud-native.slack.com/archives/CTHCQKK7U/p1700249237274639

cncf / tag-observability

TAG Observability Wiki #150