Child pages
  • Maintainers
Skip to end of metadata
Go to start of metadata

What is a maintainer?

All the committers own the Kafka code base and should be committed to making it all as good as possible. But we want to ensure that major areas have at least one person (and preferably two) who act as the defacto owners for each logical subsystem. The responsibilities of a maintainer are the following:

  • Review code contributions that effect your area as promptly as possible
  • Provide the final word on API design for this system
  • Act as the point-of-contact for questions from users and other committers that relate to this system
  • Have a hygene-related roadmap of items to help make this area of the code base shiny and beautiful. This includes the following:
    • Code quality: prettiness, readability, etc
    • Documentation
    • Test coverage and test quality
  • Help triage bugs related to your area of expertise

Subsystem Maintainers

System

Packages

Maintainers

Notes

Producer (java, scala)

kafka.producer, kafka.javaapis

Jun, Neha, Jonathan, Joestein

 

Consumer (java, scala)

kafka.consumer, kafka.javaapis

Neha, Joel, Jonathan

 

Network Layer

kafka.network

jay, Neha, Joel

 

Log

kafka.message, kafka.log

jay, Jun, Prashanth

 

Replication

kafka.controller,kafka.server

Neha, Jun, Prashanth

 

Command Line Tools

 

Joestein, Jonathan

 

System Tests

/system_tests

Joestein

 

API layer

kafka.server.KafkaApis, kafka.api

Jun, Joel, Joestein

This includes the protocol definition for each of the APIs as well as the request logic in KafkaApis.

  • No labels

1 Comment

  1. Anonymous

    I just wanted to comment on your blog and say I really enjoyed reading your blog here. It was very informative and I also digg the way you write! Keep it up and I'll be back soon to find out more mate.sterling silver rings