[chore][docs/component-stability.md] Add documentation requirements for components based on their stability level

[mx-psi]

Description

Adds requirements for documentation for different stability levels.

I expect many of these will be done through automation over time :)

Link to tracking issue

Fixes #11852

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.78%. Comparing base (6740a28) to head (2a7b85e).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11871      +/-   ##
==========================================
+ Coverage   91.72%   91.78%   +0.05%     
==========================================
  Files         463      462       -1     
  Lines       24862    24893      +31     
==========================================
+ Hits        22804    22847      +43     
+ Misses       1674     1664      -10     
+ Partials      384      382       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[julianocosta89]

I like that!
One thing to point out. We do not mention that this documentation needs to be on opentelemetry.io.

Did I assume this correctly?

To me, the official OTel docs is where all documentation should be, and not under the component repo.

[mx-psi]

One thing to point out. We do not mention that this documentation needs to be on opentelemetry.io.

I think the documentation should eventually be mirrored on opentelemetry(.)io but I would really want the control over it to be in the hands of the Collector SIG. If it's in another repository that's a huge barrier to people updating the docs. Can you file an issue on the opentelemetry(.)io tracker and ping me there? We can discuss it with them and see how to go about this

[julianocosta89]

One thing to point out. We do not mention that this documentation needs to be on opentelemetry.io.

I think the documentation should eventually be mirrored on opentelemetry(.)io but I would really want the control over it to be in the hands of the Collector SIG. If it's in another repository that's a huge barrier to people updating the docs. Can you file an issue on the opentelemetry(.)io tracker and ping me there? We can discuss it with them and see how to go about this

Awesome!
I also think having 2 repos is a pain. We are currently struggling with that in the Demo repo, and I feel that this would also impact the documentation of the Collector components.

Ideally the component codeowners would create a markdown or something, and that would be mapped properly in the docs.
Let's see what the doc team says. I'll open an issue there.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[mx-psi]

@open-telemetry/collector-approvers this is waiting for a review :)