This section includes documentation for contributing to the Fuchsia API Surface and the IDK.
Technically, it may be more appropriate to call this the “IDK Contributor Guide”, as the APIs and libraries that make up the API Surface are first added to the IDK, which is then turned into an SDK distribution. However, colloquially and in code, we almost exclusively say “the SDK”. Regardless, if you‘re looking to “change the SDK” in some way, you’re probably in the right place.
To contribute to the Fuchsia API Surface, do the following:
Evaluate whether your change is large or small.
If you have a small, incremental change to the API, contribute your change by completing the steps in Create a change in Gerrit, as you would for any Fuchsia source code change.
If you have a large change to the API, that is, a change that significantly expands on the function of the API or modifies the API extensively, do the following:
Request a code review from an API council member. Select your API council reviewer based on the area of the Fuchsia API that you're modifying. For a list of API council members and their areas of focus, see Membership in the Fuchsia API Council Charter.
partner
categoryFor 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.
To request an API Calibration, fill out this form: goto.google.com/fuchsia-api-calibration-request.
If you don‘t have access to that form, send an email to api-council@fuchsia.dev indicating the specific library or libraries you’d like to promote, and the API council will follow up with next steps.