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

Blog post: 2024 in review #5775

Merged
merged 29 commits into from
Dec 17, 2024
Merged

Conversation

svrnm
Copy link
Member

@svrnm svrnm commented Dec 12, 2024

As discussed on Monday during the SIG call here is a draft for a year in review blog post for SIG Comms

@github-actions github-actions bot added the blog label Dec 12, 2024
@opentelemetrybot opentelemetrybot requested a review from a team December 12, 2024 11:44
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.

Nice! First round of comments, see inline. 🙏

@chalin
Copy link
Contributor

chalin commented Dec 13, 2024

I think that it might be better to organize this blog as follows. After the introductory paragraph, the top-level sections should be the following:

  • Highlights, with subsections like
    • Multilingual: six languages and counting!
    • Information Architecture rework
  • Analytics
  • Community

Move current sections as subsection of these top-level sections, as appropriate.

@chalin chalin force-pushed the year-in-review-2024 branch from 94377f5 to 18e262c Compare December 13, 2024 15:12
@opentelemetrybot opentelemetrybot requested a review from a team December 13, 2024 15:13
@chalin
Copy link
Contributor

chalin commented Dec 13, 2024

I also think that we should have a section "For authoring contributors" and in there mention "new" tools or techniques or existing ones that have increased in use, such as code-excerpt functionality. WDYT?

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.

Thanks for writing this post, @svrnm! I can't believe how quickly you pulled it all together. It's fantastic! I touched up the wording, but otherwise looks great to me!

@svrnm
Copy link
Member Author

svrnm commented Dec 16, 2024

Move current sections as subsection of these top-level sections, as appropriate.

Let me see if/how I can restructure it.

I also think that we should have a section "For authoring contributors" and in there mention "new" tools or techniques or existing ones that have increased in use, such as code-excerpt functionality. WDYT?

That's a good one, let me think about that one as well!

@svrnm svrnm marked this pull request as ready for review December 16, 2024 09:26
@svrnm svrnm requested a review from a team as a code owner December 16, 2024 09:26
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.

Thanks for the co-authorship 🙏. The suggestions below fix the build, so let me merge the suggested changes and we can work from there.

Btw, how best can we collaborate on finalizing this post?

@opentelemetrybot opentelemetrybot requested a review from a team December 16, 2024 14:11
@chalin chalin force-pushed the year-in-review-2024 branch from 7f45ae4 to 97114b4 Compare December 16, 2024 14:16
@opentelemetrybot opentelemetrybot requested a review from a team December 16, 2024 14:19
@chalin chalin force-pushed the year-in-review-2024 branch from a5623a0 to 765091c Compare December 16, 2024 15:47
@opentelemetrybot opentelemetrybot requested a review from a team December 16, 2024 15:47
@chalin chalin marked this pull request as draft December 16, 2024 17:21
@chalin
Copy link
Contributor

chalin commented Dec 16, 2024

Move current sections as subsection of these top-level sections, as appropriate.

Let me see if/how I can restructure it.

I also think that we should have a section "For authoring contributors" and in there mention "new" tools or techniques or existing ones that have increased in use, such as code-excerpt functionality. WDYT?

That's a good one, let me think about that one as well!

I've marked this as Draft, as I work on the reorg (as we agreed on Slack).

@chalin chalin force-pushed the year-in-review-2024 branch from 87b16fd to ff3ea4f Compare December 16, 2024 17:24
@chalin chalin marked this pull request as ready for review December 16, 2024 19:58
@chalin chalin force-pushed the year-in-review-2024 branch 2 times, most recently from cf12080 to f19b68c Compare December 16, 2024 20:03
@chalin
Copy link
Contributor

chalin commented Dec 16, 2024

/easycla is stuck, but otherwise, call checks are currently green.

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.

Tiny fixes...LGTM!

@chalin
Copy link
Contributor

chalin commented Dec 17, 2024

Tiny fixes...LGTM!

@tiffany76 - thank you for the careful review and catching those. I've accepted all of your suggestions.

@chalin chalin force-pushed the year-in-review-2024 branch from b40a57f to 645d2b2 Compare December 17, 2024 12:03
@svrnm svrnm enabled auto-merge December 17, 2024 14:22
@svrnm svrnm added this pull request to the merge queue Dec 17, 2024
Merged via the queue into open-telemetry:main with commit abe215c Dec 17, 2024
17 checks passed
@svrnm svrnm deleted the year-in-review-2024 branch December 17, 2024 14:32
ymotongpoo pushed a commit to ymotongpoo/opentelemetry.io that referenced this pull request Jan 2, 2025
Signed-off-by: svrnm <neumanns@cisco.com>
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com>
Co-authored-by: Patrice Chalin <pchalin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants