Hey board members, There is a longish thread on the Apache Samza mailing list on the relationship between Kafka and Samza and whether they wouldn't make a lot more sense as a single project. This raised some questions I was hoping to get advice on.
Discussion thread (warning: super long, I attempt to summarize relevant bits below): http://mail-archives.apache.org/mod_mbox/samza-dev/201507.mbox/%3ccabyby7d_-jcxj7fizsjuebjedgbep33flyx3nrozt0yeox9...@mail.gmail.com%3E Anyhow, some people thought "Apache has lot's of sub-projects, that would be a graceful way to step in the right direction". At that point others popped up and said, "sub-projects are discouraged by the board". I'm not sure if we understand technically what a subproject is, but I think it means a second repo/committership under the same PMC. A few questions: - Is that what a sub-project is? - Are they discouraged? If so, why? - Assuming it makes sense in this case what is the process for making one? - Putting aside sub-projects as a mechanism what are examples where communities merged successfully? We were pointed towards Lucene/SOLR. Are there others? Relevant background info: - Samza depends on Kafka, but not vice versa - There is some overlap in committers but not extensive (3/11 Samza committers are also Kafka committers) Thanks for the advice! -Jay
