For observability-related releases/plugins, there should be an accessible description that clearly describes the scope and value proposition of each release. For this purpose, business language should be used that emphasises less the technical specifications. All this in conjunction with a Quick Start Guide to use it standalone and/or in conjunction with Greenhouse.
Objectives
Why is it necessary?
What is it for?
What does it do?
How can I use it?
What are the dependencies?
What is it not?
How can it be expanded?
Where can I contribute?
Context
For observability-related releases/plugins, there should be an accessible description that clearly describes the scope and value proposition of each release. For this purpose, business language should be used that emphasises less the technical specifications. All this in conjunction with a Quick Start Guide to use it standalone and/or in conjunction with Greenhouse.
Objectives
Why is it necessary? What is it for? What does it do? How can I use it? What are the dependencies? What is it not? How can it be expanded? Where can I contribute?