Good morning,

The current process of KIPs needs to be improved. There are at least a
handful of open KIPs with existing PRs that are in a purgatory state. I
understand that people are busy, but if you are going to gatekeep Kafka
with this process, then it must be responsive. Even if the community
decides they do not want the change, the KIP should be addressed and closed
out.

The entire wiki page is a graveyard of unresponded KIPs. For some changes,
it takes a nontrivial amount of effort to put together the wiki page and
one has to essentially write the code implementation hoping that it will be
pulled into the codebase. This is very frustrating as an external developer
to have put in the work and then effectively be ignored.

We have to maintain a custom build because KIPs are not debated, voted on,
or merged in a timely manner.

Knowles

Reply via email to