add blog post announcing proposed changes/oteps for stability work#8208
Conversation
|
One point that is not mentioned on the blog, but it is important to help users navigate the project is repositories structure.
It would be great if we could follow the same pattern across all languages. |
|
I wonder if this post should emphasize more that all these are proposals that (I think and hope) need to be properly discussed with maintainers and contributors before they are finalized, and that the way they end up being implemented may change based on discussions with all the stakeholders of the project. |
There was a problem hiding this comment.
Big change. Personally, I love this idea. 🙌
I think this aligns very well with the the idea behind the JS SIG's focus-topic selection criteria - having backing for something like this on a project-wide level AND having this communicated so publicly sounds like it has the potential to be a huge boost to stabilization efforts.
evan-bradley
left a comment
There was a problem hiding this comment.
Mostly just wordsmithing suggestions right now, thanks for putting this together!
|
notes from gc call
|
- Add 'and lack of stability' to complexity statement - Change 'own your own instrumentation' to 'publish and maintain your own instrumentation' - Remove 'not as well-defined as the earlier proposals' language - Clarify that epoch releases don't require changing component versioning/release cadence
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
- Change "Our Goals" from emphasis to heading (MD036) - Rename duplicate "Background" headings to be unique (MD024) - Rename duplicate "Goals and Objectives" headings to be unique (MD024)
Add deprioritize, incentivized, and rollouts to dictionary.
Move spelling exceptions from global dictionary to page-local to avoid affecting other files.
8295e6f to
5be7064
Compare
mtwo
left a comment
There was a problem hiding this comment.
@austinlparker the new intro resolves my concerns, thanks for doing all of the legwork on this - I know that it wasn't easy
alolita
left a comment
There was a problem hiding this comment.
Thanks @austinlparker for patiently looking at the feedback on this post and incorporating :-) This post reads well #ShipIt
tiffany76
left a comment
There was a problem hiding this comment.
A few tiny fixes, but otherwise good to go. 🚀
chalin
left a comment
There was a problem hiding this comment.
See inline comments, they suggest changing to today's date, and other front-matter cleanup.
Otherwise I defer to others for a full review.
Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com>
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com> Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com>
|
🙌 |
…pen-telemetry#8208) Co-authored-by: Juliano Costa <julianocosta89@outlook.com> Co-authored-by: Damien Mathieu <42@dmathieu.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> Co-authored-by: Evan Bradley <11745660+evan-bradley@users.noreply.github.com> Co-authored-by: Severin Neumann <severin.neumann@altmuehlnet.de> Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com> Co-authored-by: Ted Young <ted@tedsuo.com> Co-authored-by: Juraci Paixão Kröhling <juraci@ollygarden.com> Co-authored-by: Patrice Chalin <pchalin@gmail.com> Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com> Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
Adds a blog from the GC discussing proposed changes to stability and future project work/direction. cc @open-telemetry/governance-committee
Preview: https://deploy-preview-8208--opentelemetry.netlify.app/blog/2025/stability-proposal-announcement/