-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for SIG OpenTelemetry on Mainframe #1687
Conversation
Hi @rrschulze. Can you include the standard staffing section from the template? https://github.com/open-telemetry/community/blob/main/project-template.md#staffing--help-wanted |
- Included number of contributors we foresee - Clarified scope of tracks beyond the implementation of the code instrumentation SDK for Cobol - Detailed approach enhancements of the semantic conventions.
I confirm to contribute to this SIG. |
I confirm to contribute to this SIG. I’m Jack T. Jia and currently working for IBM. |
I confirm to contribute to this SIG. - Aaron Young, Broadcom |
Hello @rrschulze, could you please invite me to the mentioned slack channel. PS: I'm a mainframer representing only myself. |
@v1gnesh it is the Slack channel #otel-mainframes in the CNCF Slack workspace. If you're not yet a member of the Slack workspace, you'll need to join it first and then you can become a member of the channel #otel-mainframes yourself. |
It seems to be... broken? openmainframeproject/tac#535 (comment) |
working through CLA discussion within Rocket, but plan to participate |
I confirm to contribute to this SIG. Muruganandam (Anand) Somasundaram, IBM. |
@rrschulze Am I still supposed to see the cert warning in the slack workspace? |
what cert warning are you seeing? you should be able to sign up with any email you wish |
I confirm to contribute to this SIG. - David Dai, Rocket Software |
@dyladan - what is the right escalation path for issues accessing CNCF Slack? https://servicedesk.cncf.io/? |
That would be my best guess |
@v1gnesh https://slack.cncf.io is just a redirect to https://communityinviter.com/apps/cloud-native/cncf, can you try that directly instead? |
Reconciling meeting updates and discussions with this issue. We discussed this in the October GC / TC meeting. The TC is supportive of the mainframe effort given that it doesn’t stretch existing OTel technical leadership, who are already slammed with semantic convention stabilization. This means:
I will be the GC sponsor for this project, and I think that @alolita and @dyladan plan to participate to some extent. As for next steps, we should get weekly meetings planned and put onto the calendar, and then we should get to work. |
We need at least one more review and approval. Who can help with it? |
Let me know when the meeting schedule is set; I want to cross-post to the Open Mainframe Project Community calendar |
can you fix the spell checking CI by adding the unknown words to https://github.com/open-telemetry/community/blob/main/.cspell.yaml? |
@jmertic we will start the weekly meetings for the SIG OpenTelemetry on Mainframe next Tuesday, January 16, at 10:00 am PT. Please see the OpenTelemetry calendar. |
Hi Folks! Sorry about the delayed response. Thrilled to see this SIG for OpenTelemetry on mainframe platforms defining sem conventions take off. I plan to participate in the discussions and reviews. Also I support @mtwo in sponsoring this SIG. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Thanks for the suggestions @trask @tigrannajaryan
This is the proposal for a work group and project focusing on enhancing OpenTelemetry to support the Mainframe. For details, please see the proposal in projects/mainframe.md.
Resolves #1686.