Page History

This page describes a proposed Kafka Improvement Proposal (KIP) process for proposing a major change to Kafka.

...

...

Getting Started

If this is your first time contributing:

1. Sign up for the Developer mailing list dev@kafka.apache.org . The instructions to sign up are here: http://kafka.apache.org/contact
2. Create a wiki ID (https://cwiki.apache.org/confluence/signup.action)

...

2. Create a Jira ID (It's a different system than the wiki) (https://issues.apache.org/jira/secure/Signup!default.jspa)
3. Send an email to the dev mailing list (dev@kafka.apache.org) containing your wiki ID and Jira ID requesting permissions to contribute to Apache Kafka.

...

Purpose

We want to make Kafka a core architectural component for users. We also support a large number of integrations with other tools, systems, and clients. Keeping this kind of usage health requires a high level of compatibility between releases — core architectural elements can't break compatibility or shift functionality from release to release. As a result each new major feature or public api has to be done in a way that we can stick with it going forward.

...

1. Click

   Create from template
   templateName 54329345 templateId 54329345 title KIP-NEXT: Insert Title Here buttonLabel Create KIP

   . Take the next available KIP number and give your proposal a descriptive heading. e.g. "KIP 42: Allow Infinite Retention With Bounded Disk Usage".
2. Fill in the sections as described above
3. Also add an entry to the table 84082795 (for Streams API KIPs, please also add it to Kafka Streams sub page).
4. Start a [DISCUSS] thread on the Apache mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] KIP-{your KIP number} {your KIP heading} and the body contains a link to your new KIP. The discussion should happen on the mailing list, not on the wiki, since the wiki comment system doesn't work well for larger discussions. In the process of the discussion you may update the proposal. You should let people know the changes you are making. When you feel you have a finalized proposal 
5. Once the proposal is finalized call a [VOTE] to have the proposal adopted. These proposals are more serious than code changes and more serious even than release votes. The criteria for acceptance is lazy majority. The vote should remain open for at least 72 hours.
6. Please update the KIP wiki page, and the index below, to reflect the current stage of the KIP after a vote. This acts as the permanent record indicating the result of the KIP (e.g., Accepted or Rejected). Also report the result of the KIP vote to the voting thread on the mailing list so the conclusion is clear.

...