You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to perform a comprehensive cleanup and update of the docs folder in our OpenTelemetry Python repository. This task was discussed in our recent SIG meeting(JUL 25), and it's crucial for maintaining the quality and relevance of our documentation.
Current situation:
Some documents in the docs folder are outdated
There's a mix of documents used in new documentation and legacy content
Some Python doc files are present and tested but not published(and looks will not publish anymore)
Potential inconsistencies between our repo docs and opentelemetry.io documentation
Proposed actions:
Thoroughly review all documents in the docs folder
Compare our repo docs with the opentelemetry.io documentation
Identify and retain valuable, up-to-date content
Remove outdated or unused documents
Ensure all published Python doc files are relevant and current
Next steps:
Categorize documents as:
Up-to-date and in use
Needs updating
Obsolete and can be removed
Unpublished but potentially useful
Discuss findings in upcoming SIG meetings
Create follow-up issues for specific cleanup tasks or updates
This cleanup will improve the maintainability of our documentation and ensure that users have access to current, relevant information.
Note: This may require multiple steps and discussions. Follow-up issues will be created as needed to address specific aspects of this cleanup process.
We need to perform a comprehensive cleanup and update of the docs folder in our OpenTelemetry Python repository. This task was discussed in our recent SIG meeting(JUL 25), and it's crucial for maintaining the quality and relevance of our documentation.
Current situation:
Proposed actions:
Next steps:
This cleanup will improve the maintainability of our documentation and ensure that users have access to current, relevant information.
Note: This may require multiple steps and discussions. Follow-up issues will be created as needed to address specific aspects of this cleanup process.
And I would love to implement these.🤓
/cc @emdneto @lzchen
The text was updated successfully, but these errors were encountered: