Reminder to council members: API Calibration is required to promote APIs to partner!

19 views
Skip to first unread message

Hunter Freyer

unread,
Jul 20, 2023, 11:39:08 AM7/20/23
to api-council, Miguel Flores, Jocelyn Dang
Per the docs:

For an API to be included in the Fuchsia SDK in the partner, partner_internal, or public SDK category, it must clear two hurdles: there must be a ready and willing customer, and the API must have gone through API calibration.

I've recently seen a couple CLs where APIs were added to the SDK without going through calibration. Please make sure this doesn't happen going forward!

I admit that the system is currently rather brittle and opaque, and I'd like to improve that. But for now, it's on each individual API council member to make sure we take a good last look at any API before we open it up to a much larger audience.

Thanks,
Hunter

Christopher Anderson

unread,
Jul 20, 2023, 12:29:15 PM7/20/23
to Hunter Freyer, api-council, Miguel Flores, Jocelyn Dang
If those are easy reverts I advocate for following our standard policies of reverting them until they can go through proper review.

--
You received this message because you are subscribed to the Google Groups "api-council" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-council...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/api-council/CAMkOBfsB2ti-PxXhh%3D%2BxDABf9r2e4KrXJAozADrU8aqMShX9Qg%40mail.gmail.com.

Fabio D'Urso

unread,
Jul 24, 2023, 9:27:34 AM7/24/23
to api-council, Christopher Anderson, api-council, Miguel Flores, Jocelyn Dang, Hunter Freyer
I've reverted fxrev.dev/879252 as advised, and created a reland (fxrev.dev/888491) to be submitted after API calibration.

Fabio

Reply all
Reply to author
Forward
0 new messages