This was extracted (@ 2017-09-21 15:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings
Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We released 0.11.0.0 on Jun. 28, 2017, which includes 32 KIPs, over 400 bug fixes and improvements, and more than 700 pull requests. The main features in this release include exactly-once semantic, new admin apis, request quotas, etc. We are actively working on new features such as JBOD, delegation tokens and improvements of the controller. The next release will be 1.0.0, a big milestone in Kafka. Community =========== Lots of activities in the mailing list. We have 2474 subscribers in the user mailing list, up 44 in the last 3 months. We have 1705 emails in the user mailing list in the last 3 months, about the same as 1736 in the previous cycle. We have 1003 subscribers in the dev mailing list, up 24 in the last 3 months. We have 6526 emails in the dev mailing list in the last 3 months, up from 6248 in the previous cycle. We elected one new committer, Damian Guy on Jun. 9, 2017. We elected two new PMC members, Ismael Juma on Jul. 5, 2017 and Jason Gustafson on Jul. 11, 2017. We plan to have a 1-day Kafka Summit in SF on Aug 28. Releases =========== 0.11.0.0 was released on Jun. 28, 2017.
Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We released 0.10.2.0 on Feb. 21, 2017, which includes new features such as session window and global table in streams, client compatibilty, multiple listeners in the same security protocol and SASL/SCRAM. We released 0.10.2.1 on Apr. 26, 2017, which includes 29 critical bug fixes. We are actively working on new features such as exactly-once semantic, admin apis, request quotas, and controller improvement for the next release. Community =========== Lots of activities in the mailing list. We have 2427 subscribers in the user mailing list, up 89 in the last 3 months. We have 1824 emails in the user mailing list in the last 3 months, about the same as 1833 in the previous cycle. We have 977 subscribers in the dev mailing list, up 54 in the last 3 months. We have 6779 emails in the dev mailing list in the last 3 months, up from 6066 in the previous cycle. We elected one new committer, Rajini Sivaram on Apr. 22, 2017. We last elected a new PMC member Gwen Shapira on Aug. 17, 2016. We held a 1-day Kafka Summit in NY on May 8. It's a success with 24 technical sessions and more than 500 attendees. Releases =========== 0.10.2.1 was released on Apr. 26, 2017.
Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We released 0.10.1.1, which fixes 30 critical issues. We are in the process of releasing 0.10.2.0, which includes new features such as session window and global table in streams, client compatibilty, multiple listeners in the same security protocol and SASL/SCRAM. This is our second time-based release and we expect it to be released on time as well. We are actively working on new features such as exactly-once semantic, admin apis, and better JBOD support. Community =========== Lots of activities in the mailing list. We have 2324 subscribers in the user mailing list, up 79 in the last 3 months. We have 1954 emails in the user mailing list in the last 3 months, up from 1630 in the previous cycle. We have 912 subscribers in the dev mailing list, up 44 in the last 3 months. We have 6537 emails in the dev mailing list in the last 3 months, up from 5156 in the previous cycle. We elected one new committer, Grant Henke on Jan. 10, 2017. We last elected a new PMC member Gwen Shapira on Aug. 17, 2016. We had several Kafka meetups in various cities in this quarter. One feedback from the community is that it's a bit hard to find an answer by searching the Apache mailing list. We are wondering if Apache has considered some sort of integration with things like Stack Overflow that does a better job at Q/A. Releases =========== 0.10.1.1 was released on Dec. 19, 2016.
Apache Kafka is a distributed streaming platform for efficiently storing and processing a large number of records in real time. Development =========== We switched to a time-based release model and plan to do a release every 4 months. We released 0.10.1.0 which includes new features such as interactive queries, time-based seek, replication quotas, and quota by user. We plan to do the next release in Feb, 2017. Community =========== Lots of activities in the mailing list. We have 2243 subscribers in the user mailing list, up 48 in the last 3 months. We have 1718 emails in the user mailing list in the last 3 months, slightly down from 1912 in the previous cycle. We have 871 subscribers in the dev mailing list, up 18 in the last 3 months. We have 5355 emails in the dev mailing list in the last 3 months, up from 5318 in the previous cycle. We elected two new committers, Jason Gustafson and Jiangjie Qin, on Sep. 6 and Oct, 31, 2016, respectively. We elected a new PMC member Gwen Shapira on Aug.17, 2016. We had several Kafka meetups in various cities in this quarter. Releases =========== 0.10.1.0 was released on Oct. 20, 2016.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released 0.10.0.0 which includes new features such as Kafka stream, rack-awareness support, and native support of timestamp in the message. We also did a bug fix release 0.10.0.1 which fixed 53 issues in 0.10.0.0. We are actively working on new features such as admin apis, queryable state in Kafka stream, replication throttling, etc. Community =========== Lots of activities in the mailing list. We have 2187 subscribers in the user mailing list, up 129 in the last 3 months. We have 2043 emails in the user mailing list in the last 3 months, up from 1839 in the previous cycle. We have 852 subscribers in the dev mailing list, up 72 in the last 3 months. We have 5631 emails in the dev mailing list in the last 3 months, down from 6291 in the previous cycle, mostly because 0.10.0.0 has been released. We last elected a new committer Ismael Juma on Apr. 26, 2016. We are voting on a new PMC member right now. We had several Kafka meetups in various cities in this quarter. Releases =========== 0.10.0.0 and 0.10.0.1 were released on May. 24 and Aug. 10, 2016, respectively.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released 0.9.0.1 that fixes more than 70 critical issues in 0.9.0.0. We are actively working on the 0.10.0.0 release which includes new features such as Kafka stream, rack-awareness support, and native support of timestamp in the message. A release candidate of 0.10.0.0 is being voted on. Community =========== Lots of activities in the mailing list. We have 2050 subscribers in the user mailing list, up 192 in the last 3 months. We have 1952 emails in the user mailing list in the last 3 months, up from 1377 in the previous cycle. We have 777 subscribers in the dev mailing list, up 80 in the last 3 months. We have 6845 emails in the dev mailing list in the last 3 months, up from 5378 in the previous cycle. We last elected a new committer Ismael Juma on Apr. 26, 2016. We had the very first Kafka Summit on Apr. 26, 2016. It'a one-day conference that attracted more than 500 people. Releases =========== 0.9.0.1 was released on Feb. 19, 2016.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released 0.9.0.0, which include the following major features: (1) a new java-based consumer; (2) authorization (through ssl and sasl) and authentication; (3) quotas; (4) Kafka connect: a framework for copying data into and out of Kafka. We are actively working on critical bug fixes from 0.9.0.0 and new features such as KStream. Community =========== Lots of activities in the mailing list. We have 1828 subscribers in the user mailing list, up 148 in the last 3 months. We have 1513 emails in the user mailing list in the last 3 months, up from 1197 in the previous cycle. We have 687 subscribers in the dev mailing list, up 51 in the last 3 months. We have 5779 emails in the dev mailing list in the last 3 months, up from 5344 in the previous cycle. We last elected a new committer Ewen Cheslack-Postava on Dec. 8, 2015. Releases =========== 0.9.0.0 was released on Nov. 24, 2015.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We just rolled out RC 1 for the 0.9.0.0 release, which include the following major features: (1) a new java-based consumer; (2) authorization (through ssl and sasl) and authentication; (3) quotas; (4) Kafka connect: a framework for copying data into and out of Kafka. Community =========== Lots of activities in the mailing list. We had several Kafka improvement proposals post the 0.9.0 release. We last elected a new committer Sriharsh Chintalapani on Sep. 21, 2015. We had Kafka meetups in Austin, Los Angeles, and London this quarter. Releases =========== 0.8.2.2 was released on Sep. 13, 2015.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We are actively developing multiple features in the next release. These include (1) a new java-based consumer; (2) security (authorization and authentication); (3) quotas; (4) a framework for copying data into and out of Kafka; (5) a stream processing api integrated with Kafka. Community =========== Lots of activities in the mailing list. kafka-user has 435, 278, 86 emails in Feb, Mar and Apr, respectively (down from 453 in Apr). kafka-dev has 1532, 800, 402 emails in May, Jun and Jul, respectively (down from 2001 in Apr). We last elected a new committer Gwen Shapira on Jul. 6, 2015. We also added Guozhang Wang to pmc on Jun. 10, 2015. We had two Kafka meetups in the bay area on May 19 and Jun. 16. Releases =========== 0.8.2.1 was released on Mar. 11, 2015.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8.2.1, which fixes 4 critical issues in 0.8.2.0. The highlights in the 0.8.2.x releases include (1) a java-based new producer, which provides better performance and a cleaner api; (2) a more scalable Kafka-based offset storage management; (3) automated leader balancing and controlled shutdown; (4) delete topic support; (5) more than 200 bug fixes and improvements. We are actively developing a new java-based consumer and the security support in trunk. Community =========== Lots of activities in the mailing list. kafka-user has 768, 776, 453 emails in Feb, Mar and Apr, respectively (up from 665 in Jan). kafka-dev has 1742 1854, 2001 emails in Feb, Mar and Apr, respectively (up from 1632 in Jan). We last elected a new committer Guozhang Wang on Nov. 19, 2014. We had two Kafka talks and a meetup in ApacheCon 2015. We had a Kafka meetup in Mountain View, California on Mar. 24, 2015. Releases =========== 0.8.2.1 was released on Mar. 11, 2015.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8.2.0. The highlights in this release include (1) a java-based new producer, which provides better performance and a cleaner api; (2) a more scalable Kafka-based offset storage management; (3) automated leader balancing and controlled shutdown; (4) delete topic support; (5) more than 200 bug fixes and improvements. We are actively developing a new java-based consumer and the security support in trunk. Community =========== Lots of activities in the mailing list. kafka-user has 550, 464, 665 emails in Nov, Dec and Jan, respectively (up from 563 in Oct). kafka-dev has 1214, 881, 1632 emails in Nov, Dec and Jan (about the same as 1633 in Jul). We last elected a new committer Guozhang Wang on Nov. 19, 2014. We had a Kafka meetup in Mountain View, California on Jan. 27, 2015. Releases =========== 0.8.2.0 was released on Feb. 3, 2015.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8.2 beta. The highlights in this release include (1) a java-based new producer, which provides better performance and a cleaner api; (2) a more scalable Kafka-based offset storage management; (3) automated leader balancing and controlled shutdown; (4) delete topic support; (5) more than 100 bug fixes and improvements. We expect to release 0.8.2 final by end of Nov. Community =========== Lots of activities in the mailing list. kafka-user has 431, 383, 563 emails in Aug, Sep and Oct, respectively (up from 429 in Jan). kafka-dev has 1129, 1257, 1633 emails in Aug, Sep and Oct (about the same as 1357 in Jul). A new committer is being voted now. The voting thread was started on Nov 11, 2014. Releases =========== 0.8.2 beta was released on Oct 27, 2014.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We continue to stablize two main features for the 0.8.2 release. The first one is Kafka-based offset management, which allows consumer offsets to be stored in a more scalable way. The second one is the new producer, which provides better performance and a cleaner api. We expect to release 0.8.2 in a month or two. We also finalized the api and the design for the new consumer and started the development. This feature is intended for the 0.9.0 release. Community =========== Lots of activities in the mailing list. kafka-user has 422, 560, 429 emails in May, June and July, respectively (up from 388 in Apr). kafka-dev has 789, 610, 1357 emails in May, June and July (sligtly higher than 1272 in Apr). We had a Kafka meetup in June. We last elected two committers in Oct. 2013 and are actively grooming new potential committers. Releases =========== 0.8.1 was released on Mar 21, 2014 and 0.8.1.1 was released on Apr 29, 2014.
pache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8.1 and 0.8.1.1, which include a few improved admin tools and new features like log compaction. We are currently stablizing the new producer, which provides better performance and a cleaner api. We are finalizing the api and the design for the new consumer. Community =========== Lots of activities in the mailing list. kafka-user has 480, 450, 388 emails in Feb, Mar and Apr, respectively (slightly less than 538 in Jan). kafka-dev has 1120, 1047, 1272 emails in Feb, Mar and Apr (slightly less than 540 in Jan). There were three Kafka related talks in ApacheCon 2014. We last elected two committers in Oct. 2013. Releases =========== 0.8.1 was released on Mar 21, 2014 and 0.8.1.1 was released on Apr 29, 2014. Infra =========== The recent Apache mail server issue impacted many projects. I am sure there will be some post-mortem on how to prevent this in the future. Could the post-mortem results be shared with all PMCs?
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8.0 and have since improved existing admin tools. An 0.8.1 release branch has been created and we intend to release 0.8.1 in a few weeks. We are actively working on a new version of the producer client, which provides better performance and a cleaner api. After that, we expect to rewrite the consumer client for the same reasons. Community =========== Lots of activities in the mailing list. kafka-user has 538, 461, 436 emails in Jan, Dec and Nov, respectively (slightly less than 582 in Oct). kafka-dev has 540, 509, 540 emails in Jan, Dec and Nov (slightly less than 581 in Oct). At least one Kafka talk is submitted to ApacheCon 2014. We last elected two committers in Oct. 2013. Releases =========== 0.8.0 was released on Dec 3, 2013.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We have fixed critical bugs and improved the tools since the Kafka 0.8 beta1 (supports intra-cluster replication). We are in the process of releasing 0.8.0 final. Next, we will be focusing on stablizing trunk and releasing 0.8.1 (including various server side performance improvements). After that, we will start improving the client library. An initial design is in the wiki. Community =========== Lots of activities in the mailing list. kafka-user has 665, 278, 582 emails in Jul, Jun and May, respectively (up from 425 in Jul). kafka-dev has 581, 509, 595 emails in Oct, Sep and Aug (up from 290 in Apr). Two new Kafka committers were elected: David Arthur and Sriram Subramanian. Releases =========== 0.8.0 final release candidate 3 is being voted now.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We released Kafka 0.8 beta1 (supports intra-cluster replication). We have updated the website with documentation and our new logo. We are fixing critical bugs in the 0.8 branch and expect to release the 0.8 final version soon. Community =========== Lots of activities in the mailing list. kafka-user has 425, 442, 421 emails in Jul, Jun and May, respectively (up from 390 in Apr). kafka-dev has 290, 290, 562 emails in Jul, Jun and May (down from 567 in Apr since 0.8 dev is winding down). There are patches being contributed by non-committers. No committers added yet since graduation. Last committer was added in May, 2012. Releases =========== 0.8.0 beta1: released on Jun. 27, 2013 0.8.0 final release is expected in three weeks
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We are in the final phase of testing Kafka 0.8 (supports intra-cluster replication). We have updated the related docs and expect to release 0.8 beta in a couple weeks. Community =========== Lots of activities in the mailing list. kafka-user has 390, 357, 174 emails in Apr, Mar and Feb, respectively (up from 243 in Jan). kafka-dev has 567, 565, 457 emails in Apr, Mar and Feb (down from 804 in Jan since 0.8 dev is winding down). There are patches being contributed by non-committers. Releases =========== 0.7.2: released Oct. 11, 2012 0.8.0 beta: expected to release in two weeks
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We found a few more blocker issues while testing Kafka 0.8 (supports intra-cluster replication). The 0.8 release is likely delayed to Mar or Apr. Community =========== Lots of activities in the mailing list. kafka-user has 243 emails in Jan. (up from 241 in Dec). kafka-dev has 804 emails in Dec (up from 498 in Dec). We accepted a few more patches from non-committers. There will be a Kafka presentation in ApachCon 2013 in Feb. Infrastructure =========== This is the third month since Kafka became a top-level project. All infra work is now done.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== We are actively testing Kafka 0.8 (supports intra-cluster replication) and fixing blocking issues that show up. We expect to release 0.8 towards the end of Jan. Community =========== Lots of activities in the mailing list. kafka-user has 241 emails in Dec (down from 335 in Nov, mostly due to the holidays). kafka-dev has 498 emails in Dec (up from 448 in Nov). More patches are being contributed by non-committers. Infrastructure =========== This is the second month since Kafka became a top-level project. Apache infra has helped us migrate the website and move from svn to git.
Apache Kafka is a distributed pub/sub system for efficiently collecting and delivering a large number of messages to both offline and online systems. Development =========== Kafka 0.8 (supports intra-cluster replication) is in the final debugging stage. We gave out a trivial version on Nov 26. We expect to release 0.8 in Jan. 2013. Community =========== Lots of activities in the mailing list. kafka-user has 335 emails in Nov (up from 236 in Oct). kafka-dev has 448 emails in Nov (down from 758 in Oct, mostly because of fewer active jiras). There will be a Kafka presentation (introducing 0.8 features) in ApacheCon in Feb., 2013. Infrastructure =========== This is the first month since Kafka became a top-level project. Apache infra has helped us migrate the svn repository and the mailing list, and is in the process of migrating our website.
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to a distributed publish/subscribe stream
processing framework.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Kafka Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Kafka Project be and hereby is
responsible for the creation and maintenance of software
related to a distributed publish/subscribe stream processing
framework; and be it further
RESOLVED, that the office of "Vice President, Apache Kafka" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Kafka Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Kafka Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Kafka Project:
* Jun Rao <junrao@apache.org>
* Jay Kreps <jkreps@apache.org>
* Neha Narkhede <nehanarkhede@apache.org>
* Jakob Homan <jghoman@apache.org>
* Joel Koshy <jjkoshy@apache.org>
* Prashanth Menon <prashanthmenon@apache.org>
* Joe Stein <joestein@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jun Rao
be appointed to the office of Vice President, Apache Kafka, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Kafka PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Kafka Project; and be it further
RESOLVED, that the Apache Kafka Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Kafka podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Kafka podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7C, Establish the Apache Kafka Project, was
approved by Unanimous Vote of the directors present.
(introduced to Apache incubator on Jul 4, 2011)
Kafka provides an extremely high throughput distributed publish/subscribe
messaging system. Additionally, it supports relatively long term persistence
of messages to support a wide variety of consumers, partitioning of the
message stream across servers and consumers, and functionality for loading
data into Apache Hadoop for offline, batch processing.
Three most important issues to address in the move towards graduation:
None.
Previously, there was some concern about the diversity of the project
that we believe has been addressed:
- The project now has active committers from four companies
- and continues to receive patches from other contributors from various
institutions.
We are considering whether to pursue graduation immediately or focus
exclusively on the development of 0.8.
Any issues that the Incubator PMC or ASF Board might wish/need to be aware of:
None.
How has the community developed since the last report:
- The mailing list continues to be very active with bug reports, patch
submissions, feature requests and use cases.
[(Apr,May,Jun): kafka-users (151, 261, 251); kafka-dev (142, 195, 380)].
- Added two new committers.
- Conducted the first Kafka user group meeting with over 50 attendees
(archived video link available here: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+papers+and+presentations).
This was a very successful event that gave users and contributors an
opportunity to meet and discuss Kafka usage at various companies, ongoing
development efforts, feature requests, etc.
- Received and reviewed several major patches (including contributions from
non-committers).
How has the project developed since the last report:
- Intra-cluster replication (KAFKA-50)
- Considerable progress has been made on the design and implementation of
this much-anticipated feature.
- Regular status updates are being sent out on the kafka-dev mailing list.
- Another significant project that is under discussion and development is
the consumer redesign (KAFKA-364) and consumer coordinator implementation
(KAFKA-264).
- Released Kafka 0.7.1 in June. This is the second Kafka release since its
introduction to Apache incubator
Signed off by mentor: Alan Cabrera
Shepherd: Matt Franklin
(introduced to Apache incubator on Jul 4, 2011) Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. A list of the most important issues to address in the move towards graduation - Invite diverse new active committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None How has the community developed since the last report? - Added a new committer. Continued contribution to source code in fixes and features and continued activity on the mailing lists. How has the project developed since the last report? - Work was begun on 0.8 release which includes our replication feature and also requires a breaking change for existing consumers/producer to the wiring protocol. Signed off by mentor: cdouglas, adc
(introduced to Apache incubator on Jul 4, 2011) Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. A list of the most important issues to address in the move towards graduation 1. Invite diverse new active committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We incurred significant overhead during our first release; see http://apache.markmail.org/message/rsxjgrrufc6khlqy?q=list:org%2Eapache%2Eincubator%2Egeneral+from:%22junrao%22 for reference. Firstly, there is no good example to follow for a new podling. Secondly, the licensing rules are complex and the documentation is not enough for a new podling to understand. This gets more complicated since different IPMC members have different views and apply those rules slightly differently. This delays releases and causes overhead to the team. We hope that some of these things can be addressed to make the process easier to other projects. How has the community developed since the last report? Activities in the mailing list increased 4x since the last report. Several patches from non-committers have been submitted, reviewed and committed. How has the project developed since the last report? We have successfully completed the first release of Kafka after joining the incubator. This releases adds the end-to-end compression feature and mirroring support in Kafka. In addition to this, it also fixes more than 40 issues.
Introduced to Apache incubator on Jul 4, 2011 Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. A list of the most important issues to address in the move towards graduation 1. Successful podling release. 2. Invite diverse new active committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Not at this time. How has the community developed since the last report? Mailing list traffic for July-August-September[12th] (user: 40, 65, 19; dev: 116, 371, 63) both show healthy growth trends. Qualitatively the -dev discussion has trended away from topics like "how should we configure Jira?" to "What's the best way to deal with multiple language bindings?". Several patches were submitted by first time contributors. How has the project developed since the last report? The general theme over the past month has been polish: fixing bugs, better unit tests, getting log levels right, build system cleanup etc.
Introduced to Apache incubator on Jul 4, 2011 Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. A list of the most important issues to address in the move towards graduation 1. Successful podling release. 2. Invite diverse new active committers Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Not at this time. How has the community developed since the last report? Mailing list traffic for July-August-September[12th] (user: 40, 65, 19; dev: 116, 371, 63) both show healthy growth trends. Qualitatively the -dev discussion has trended away from topics like "how should we configure Jira?" to "What's the best way to deal with multiple language bindings?". Several patches were submitted by first time contributors. How has the project developed since the last report? The general theme over the past month has been polish: fixing bugs, better unit tests, getting log levels right, build system cleanup etc.
(introduced to Apache incubator on Jul 4, 2011) Kafka provides an extremely high throughput distributed publish/subscribe messaging system. Additionally, it supports relatively long term persistence of messages to support a wide variety of consumers, partitioning of the message stream across servers and consumers, and functionality for loading data into Apache Hadoop for offline, batch processing. A list of the three most important issues to address in the move towards graduation 1. Package, document and release at least one Apache Incubator release. 2. Develop a strong community with organizational diversity. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Just get started. The mailing list is pretty active, including people other than the initial committers. How has the project developed since the last report? * Moved everything (svn, website, mailing list, jira, wiki) in Kafka to Apache. CCLA from LinkedIn filed with Apache. * The end-to-end compression feature is almost complete. * Received various patches from 3 different companies, including dynamic topic discovering for cross-cluster mirroing, mx4j support, .net client, etc.