Project status update: development is resuming

[gaelreyrol]

Hello everyone,

First and foremost, I want to sincerely apologize for the extended period of inactivity on this project. Life and work priorities shifted, and I was unable to dedicate the time this bundle and its community deserved. I know many of you reached out with questions, bug reports, feature requests, and even pull requests — and the silence on my end was not acceptable. I'm sorry.

I want to especially acknowledge and thank everyone who took the time to engage with this project over the past year:

• @DZunke — Thank you for your kind words and thoughtful inquiry about the project's future in Project Status Inquiry & Thanks #205. Your message was a real motivator to pick things back up.
• @garak — The suggestion to replace Guzzle with Symfony HTTP Client in Replace Guzzle with Symfony HTTP Client #198 makes total sense and is on my radar.
• @ToshY — Thank you for both the honest question about a stable release timeline ([Question] Is there an ETA for an initial stable release? #192) and the detailed Monolog bug report ([Bug] Installing opentelemetry bundle breaks existing Monolog config #193). Both are appreciated and will be addressed.
• @kochen — The request for a Symfony Flex recipe (Add recipe to symfony/recipes-contrib #176) and the incomplete trace report (Messenger Instrumentation - Trace seems incomplete #190) are noted and will be looked into.
• @jvocampings — Thank you for the detailed investigation into the Messenger root span issue (Messenger Instrumentation - The root span seems never ended #172) and especially for the WIP pull request (feat(Instrumentation/Messenger): implement worker and middleware instrumentation #173) to improve Messenger instrumentation. I will review it.
• @AtCliffUnderline — The withOptions span attributes issue (Attributes in http client instrumentation ignoring options passed through withOptions #160) is a valid concern, and I appreciate the offer to contribute a PR.
• @Kaspiman — Enriching traces with HTTP response information (Enrich the trace with information from the HTTP-response in TraceableResponse #114) is a good idea that I'll consider.
• @GeoDpto — Thank you for the Kafka transport implementation PR (feat(OpenTelemetry/Transport): implement Kafka transport #196). Async communication with the collector is an important use case and I will review it.

What's next

Development is officially resuming. Here is what you can expect:

1. CI is green again — I've already merged chore: update dependencies, CI, and tracing sem conv across codebase #206 which updates dependencies, CI pipelines, and tracing semantic conventions across the codebase.
2. Issue triage — I will go through all open issues and PRs, prioritize them, and provide feedback.
3. PR reviews — Open pull requests (feat(Instrumentation/Messenger): implement worker and middleware instrumentation #173, feat(OpenTelemetry/Transport): implement Kafka transport #196) will be reviewed.
4. Bug fixes — Known bugs ([Bug] Installing opentelemetry bundle breaks existing Monolog config #193, Messenger Instrumentation - The root span seems never ended #172, Messenger Instrumentation - Trace seems incomplete #190, Attributes in http client instrumentation ignoring options passed through withOptions #160) will be investigated and fixed.
5. Path to stable release — I will update milestones and provide a clearer roadmap toward a v1.0.0 release.

I can't promise a specific timeline yet, but I can promise that this project is not abandoned and that I will be actively working on it going forward.

Thank you all for your patience, your contributions, and your interest in this bundle.