Remember that to vote -1 it is necessary to provide justification, so I’d like to see the justifications and the plan from those who do not want to move Apex to the attic. I am also not very happy that my past efforts will be placed in the attic, but let’s face the reality. It is not that I don’t want to be involved in the project, but as the PMC I am responsible for maintaining the correct state of the project and with the current level of contributions, IMO, it belongs the the attic.
Thank you, Vlad > On Jan 9, 2019, at 09:02, Pramod Immaneni <pramod.imman...@gmail.com> wrote: > > What would be the purpose of such a vote? From the discussions it is quite > apparent that there is a significant, possibly majority view that project > shouldn’t go to attic. The same could be reported to the board, can’t it? > Like I also said if you or others don’t like where the project is at and > feel it is a dead end, you don’t have to continue to be involved with the > project and that’s your prerogative. Let others who want to continue, take > it forward, why try to force your will on to everyone. > > Thanks > > On Wed, Jan 9, 2019 at 8:43 AM Vlad Rozov <vro...@apache.org> wrote: > >> 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 >>>> >> >> -- > Thanks, > Pramod > http://ts.la/pramod3443
