Without concrete details of what will be committed (support for k8s, hadoop 3.x, kafka 2.x, etc) and what requirements in code submission needs to be relaxed (well written java code, consistent code style, successful build with passing unit tests in CI, providing unit test, etc) the statements below are way too vague. Note that I started this e-mail thread with the intention to see what contributions the community may expect. Without concrete details of the future contribution, I’ll submit a vote by end of January.
Thank you, Vlad > On Jan 9, 2019, at 00:47, priyanka gugale <pri...@apache.org> wrote: > > I do believe and know of some work done in private forks by people. There > could be couple of reasons why it didn't go public. One could be high bar > for code submission (I don't have references at hand but that's general > feeling amongst committers) and other could be lack of motivation. > > Let's try to put some efforts to re-survive the work, motivate committers, > and take hard decisions later if nothing works. A product like Apex / > Malhar definitely deserves to survive. > > -Priyanka > > On Wed, Jan 9, 2019 at 12:07 PM Atri Sharma <a...@apache.org> wrote: > >> The reason for a private fork was due to potential IP conflicts with >> my current organization. I am working to get approvals and clearances, >> and post that, shall publish the said effort. >> >> On Wed, Jan 9, 2019 at 12:02 PM Justin Mclean <jus...@classsoftware.com> >> wrote: >>> >>> Hi, >>> >>>> I have a private fork for an experimental project. It might be open >>>> sourced in a couple of months. >>> >>> I’m curious, if you don’t mind answering a couple of questions: >>> >>> As you are a committer on this project is there any reason that this >> work wasn’t done in public fork or even better on a branch of the Apex >> repo? Why would a delay of a couple of months be required? If it’s “it >> might be” what realistically are the chances of that happening? >>> >>> Thanks, >>> Justin >> >> -- >> Regards, >> >> Atri >> Apache Concerted >>
