---
breadcrumbs:
- - /blink
  - Blink (Rendering Engine)
- - /blink/guidelines
  - Guidelines and Policies
page_name: blink-api-owners-requirements
title: Blink API OWNERS Requirements
---

## Requirements for API owners

### <table>
### <tr>

    ### <td>Chromium contributor in good standing, with a commitment to <a
    href="/blink">Blink’s mission</a>: To improve the open web through technical
    innovation and good citizenship</td>

*   ### <td>The person's organizational affiliations must be compatible
            with API owners service as regards <a
            href="/developers/contributing-code/external-contributor-checklist">CLA
            status</a></td>

    ### <td>Commitment of 1-2 hours per week to review intents, in addition to
    the API owners meetings</td>

    ### <td>Demonstrated understanding of the Blink Launch Process \[Evidence:
    Shipped APIs following this process\]</td>

        ### <td>Internalized the principles and emulated them. \[Evidence: links
        to their own Intents with discussion threads highlighting how things
        like interop, compat were tackled\]</td>

    ### <td>Demonstrated knowledge and ability to review Web Platform features.
    \[Evidence example: Input/guidance on 10+ blink intent threads over the past
    6 months\]</td>

### </tr>
### </table>

### Optional, but desirable qualifications

### <table>
### <tr>

    ### <td>Mentored other teams through the API process. \[Evidence: Mentorship
    feedback/notes, links to threads they chimed in on, that were not their own
    intents\]</td>

    ### <td>Contributed to improving the API process. \[Evidence: Process
    improvement proposals, process documentation\]</td>

    ### <td>Experience navigating disagreements/contention. \[Evidence: Examples
    of such discussions on any public forums, not necessarily Blink
    intents\]</td>

### <td>Becoming an API Owner</td>

*   ### <td>Candidates that meet the qualifications can be nominated by
            a current API owners to the rest of the API owners group.</td>
*   ### <td>A candidate may also self-nominate via communication to
            blink-api-owners@chromium.org (a mailing list with only the API
            owners subscribed to it), or to one or more of the API owners.</td>
*   ### <td>The nomination should include an explanation as to why the
            candidate meets the criteria above, including links to evidence to
            that effect.</td>
*   ### <td>A nominee will be appointed to be an API owners once the
            nomination gets 3 LGTMs and no objections.</td>
*   ### <td>Once the nomination is approved, an email will be sent to
            the blink-dev mailing list announcing it. If it is rejected, a
            private email with explanation will be sent to the nominee.</td>
*   ### <td>Consideration of nominations will happen in a timely
            manner.</td>

### </tr>
### </table>
