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

How can we get bloggers to contribute content back to OTel docs/readme? #48

Open
2 tasks
reese-lee opened this issue Jun 20, 2024 · 3 comments
Open
2 tasks

Comments

@reese-lee
Copy link
Member

reese-lee commented Jun 20, 2024

  • Goal: To be able to link back to an official OTel resource (single source of truth), and help increase quality and depth of OTel docs and blogs
  • Good resources to search for content: O11y.news, Observability360, monitoring.love

To figure out:

  • What kind of cadence? -- We will need to review the content before recommending they be reposted to OTel site
  • How to do rotation?
@reese-lee reese-lee converted this from a draft issue Jun 20, 2024
@avillela avillela moved this to Todo in End User SIG Jun 20, 2024
@avillela
Copy link
Contributor

Related PR: open-telemetry/community#2162

@danielgblanco
Copy link
Contributor

Are we talking about end-user bloggers, that use OTel within their stack? Or maintainers? If it's the former, I think most of the time folks just don't know how easy it'd be for them to publish a blog on the OTel site.

@avillela
Copy link
Contributor

avillela commented Jul 15, 2024

Yes, mostly aimed at end-user bloggers. When we first logged this issue, I would've said that getting them to just x-post their blog posts on the OTel blog would've been good enough, but I found out recently that the comms SIG is really trying to prioritize docs content over blog content (see "Documentation or Blog Post" in the blog contribution page). So the question is, how can we support them to make this happen?

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

No branches or pull requests

3 participants