-
Notifications
You must be signed in to change notification settings - Fork 628
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
Present OpenMetrics to TOC #110
Comments
If I hear no issues from the @cncf/toc by the end of this week, I will schedule you for June 19th |
I might have a scheduling conflict on that date, but it should work out. Will be able to tell next week, but you are free to schedule and if all else fails, I will reschedule. |
@RichiH does June 5th work better? let me know, we're flexible |
June 19th is most likely better; remind me at what UTC time this will happen, please. |
8am PT = 3pm UTC I believe June 19th it is! |
Sgtm
Sent by mobile; please excuse my brevity.
…On Wed, May 9, 2018, 01:01 Chris Aniszczyk ***@***.***> wrote:
8am PT = 3pm UTC I believe
June 19th it is!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#110 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAuEIxZVfZ0hpGZbNHeMbOgl3-jVOgxxks5twiO6gaJpZM4TsZk2>
.
|
Scheduled for June 19th |
Who, what, why?
OpenMetrics aims to evolve the Prometheus exposition format into its own standard to help adoption. The project is currently nearing technical completion after which we will write the specs and Internet Draft to publish an RFC.
This effort has been ongoing for well over a year with healthy buy-in from CNCF TOC, especially @monadic , the community, and several companies.
The main pool of active contributors is coming from Prometheus team, Google, and Uber.
Cloud-Native & CNCF Alignment
We support the goals of CNCF and have a combined track record of more than a person-decade working on furthering these practices. We see the scope of OpenMetrics going beyond "just" CNCF, hopefully changing the legacy space as well.
The text was updated successfully, but these errors were encountered: