Skip to content
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

Add blog post about the mainframe priorities survey #6072

Open
wants to merge 27 commits into
base: main
Choose a base branch
from

Conversation

rrschulze
Copy link

Fixes #6045

Adds a blog post to promote the OpenTelemetry on Mainframe Priorities Survey created by the Mainframe SIG. The blog has been previously published by the Open Mainframe Project here.

@rrschulze rrschulze requested a review from a team as a code owner January 24, 2025 13:37
@opentelemetrybot opentelemetrybot requested a review from a team January 24, 2025 13:38
@github-actions github-actions bot added the blog label Jan 24, 2025
Copy link
Contributor

@chalin chalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's fix the build. See inline for suggested fixes to the front matter.

content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
@opentelemetrybot opentelemetrybot requested a review from a team January 24, 2025 14:04
Copy link
Contributor

@tiffany76 tiffany76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One front matter fix that might help the build, along with some Markdown and copy edits. Thanks!

content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
@opentelemetrybot opentelemetrybot requested a review from a team January 25, 2025 06:32
Copy link
Member

@mx-psi mx-psi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SIG Contributor Experience will be running a survey from February 3rd until March 3rd. We delayed our survey to not overlap with the Developer Experience survey. Would it be possible to delay this survey until March 3rd? I understand that this is a delay of several weeks, but I would like to avoid overlapping surveys if possible

@rrschulze
Copy link
Author

@mx-psi the survey is in-fact in-flight already, as it was set up also together with the Open Mainframe Project (blog, survey).

The plan of this PR to have the same blog published via the OpenTelemetry webpage to also obtain responses from the OpenTelemetry community. The objective so far was to close the survey on 15th of February as we'd like to be in a position to discuss results at the SHARE conference at the end of February as is one of the major mainframe conferences.

@rrschulze
Copy link
Author

Any advice how to fix the error for check "Links / BUILD and CHECK LINKS (pull_request)"? From what I understand it relates to updates of the file static/refcache.json. Is there a command which triggers to include newly added URLs from the new blog content?

@mx-psi
Copy link
Member

mx-psi commented Jan 27, 2025

@mx-psi the survey is in-fact in-flight already, as it was set up also together with the Open Mainframe Project (blog, survey).

The plan of this PR to have the same blog published via the OpenTelemetry webpage to also obtain responses from the OpenTelemetry community. The objective so far was to close the survey on 15th of February as we'd like to be in a position to discuss results at the SHARE conference at the end of February as is one of the major mainframe conferences.

Alright, sounds like it can't be delayed then

@svrnm
Copy link
Member

svrnm commented Jan 27, 2025

Any advice how to fix the error for check "Links / BUILD and CHECK LINKS (pull_request)"? From what I understand it relates to updates of the file static/refcache.json. Is there a command which triggers to include newly added URLs from the new blog content?

We can fix that via automation: https://opentelemetry.io/docs/contributing/pr-checks/

But we can do this before merging the PR.

@rrschulze
Copy link
Author

@svrnm let me look at fixing it based on the doc.

@opentelemetrybot opentelemetrybot requested a review from a team January 29, 2025 05:32
@rrschulze
Copy link
Author

I think, I got stuck with setup issues for hugo trying to resolve the "Links / BUILD and CHECK LINKS (pull_request)" check. Current message I get indicates missing Font-Awesome.

"Error: failed to load modules: module "github.com/FortAwesome/Font-Awesome" not found in "/Users/rschulze/Documents/GitHub/opentelemetry.io/themes/github.com/FortAwesome/Font-Awesome"; either add it as a Hugo Module or store it in "/Users/rschulze/Documents/GitHub/opentelemetry.io/themes".: module does not exist".

@svrnm Is there an easy path to resolve the failed check? If possible, I'd like to go for it and defer resolving my environment issues.

@svrnm
Copy link
Member

svrnm commented Jan 29, 2025

/fix:all

@opentelemetrybot
Copy link
Collaborator

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13028648672

@svrnm
Copy link
Member

svrnm commented Jan 29, 2025

@rrschulze the issue you see is most likely caused by a missing npm install run. I triggered the GitHub action to fix it.

@opentelemetrybot
Copy link
Collaborator

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

@svrnm
Copy link
Member

svrnm commented Jan 30, 2025

@chalin can you check if your change requests have been applied?

---
title: OpenTelemetry on Mainframe Priorities Survey
linkTitle: Mainframe Priorities Survey
date: 2025-01-24
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
date: 2025-01-24
date: 2025-01-30

let's keep this open until we set the right date.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rrschulze let's keep this open until we decide on a final schedule, might push out to tomorrow, so I want to ensure that we have the right date set.

Copy link
Contributor

@chalin chalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See inline for suggested copyedits.

content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
content/en/blog/2025/otel-mainframe-priorities-survey.md Outdated Show resolved Hide resolved
static/refcache.json Outdated Show resolved Hide resolved
@opentelemetrybot opentelemetrybot requested a review from a team January 30, 2025 12:34
@chalin
Copy link
Contributor

chalin commented Jan 30, 2025

/fix:all

@opentelemetrybot
Copy link
Collaborator

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13052550364

@opentelemetrybot
Copy link
Collaborator

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

rrschulze and others added 26 commits January 30, 2025 08:11
Co-authored-by: Patrice Chalin <[email protected]>
@opentelemetrybot
Copy link
Collaborator

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

Copy link
Contributor

@chalin chalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All checks are passing, and we now have a link to the original post. LGTM ✨

@chalin
Copy link
Contributor

chalin commented Jan 30, 2025

@svrnm - this is ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

New Blog Post: OpenTelemetry on Mainframe Priorities Survey
6 participants