A shame it would be and sad for those of us who have put a lot of effort into the project. But not surprising to have reached this point at all. We should face reality or not?
The crux of the matter is that Apache projects are community first and not a parking lot for code bases. Apex code base was great few years ago and there was nothing like it but then also nobody knew because it wasn't open source. Data processing is a super fast moving space. Apex code base stalled and advantages Apex once had are all but gone. Now it has fallen quite far behind other options out there, including Apache projects with vibrant communities that include enthusiastic contributors and users committed to return something for what they take. Users of Apex are all but invisible. It is irrelevant if someone has a fork in the backyard. What matters is activity that everyone can follow and the give and take that can lead to growth. The Apex project started as marketing campaign of a failed vendor and though few of us were hoping that would change over time, it didn't. What reasons are there to adopt Apex today? * No support for k8s as deployment platform (doesn't even support latest YARN version) * No UI * No observability story * No plans to support Java 11 (new LTS version) * ... And most importantly no community to change any of that. One can deny the ground reality and continue to pretend there is life in Apex. But as it stands, all roads lead to attic. Without contributions and releases I don't see why we should prolong this march. There were few announcements for related work, but no follow-through. I would vote for attic, but would be pleasantly surprised to see reasons not to. Thomas On Mon, Jan 7, 2019 at 9:50 PM Atri Sharma <a...@linux.com> wrote: > I agree. > > The project, IMO, still has hopes for survival since it is well > respected for its capabilities. Putting it in attic basically kills it > off completely. > > I would vote against it, atleast for now > > On Tue, Jan 8, 2019 at 9:54 AM Pramod Immaneni > <pramod.imman...@gmail.com> wrote: > > > > I would like to point out that there is no agreement among the project > PMCs > > that the project should go to attic, not many are for it and quite a few > > oppose it. If a PMC member or committer cannot or does not wish to > > participate at any time, they can choose to remain inactive, there is no > > obligation. If someone feels strongly that they rather not remain > inactive > > while being part of the project they can choose to resign, although that > > would be largely regrettable. Jan end sounds reasonable for the > submission > > although it’s outcome should not determine the future of the project. > > > > Thanks > > > > On Mon, Jan 7, 2019 at 6:09 PM Vlad Rozov <vro...@apache.org> wrote: > > > > > Let’s agree on ETA (by end of January?) for the contribution. Also, one > > > contribution in several months is not sufficient to keep project > active, > > > IMO. Anybody else, especially other PMCs? > > > > > > Thank you, > > > > > > Vlad > > > > > > > > > > On Jan 7, 2019, at 12:06, Pramod Immaneni <pramod.imman...@gmail.com > > > > > wrote: > > > > > > > > Yes, I have an operator that I am trying to get clearance on before > > > > submitting. Will likely need a maven server to host a dependency > that's > > > not > > > > on central. > > > > > > > > Thanks > > > > > > > > On Mon, Jan 7, 2019 at 9:08 AM Vlad Rozov <vro...@apache.org> wrote: > > > > > > > >> Does anyone plan to contribute to the project in the near future? > > > >> Otherwise, I plan to submit a vote to move the project to Apache > attic. > > > >> > > > >> Thank you, > > > >> > > > >> Vlad > > > > > > > > > > > > > > > > -- > > > > Thanks, > > > > Pramod > > > > http://ts.la/pramod3443 > > > > > > -- > > Thanks, > > Pramod > > http://ts.la/pramod3443 >
