That is not accurate, I have mentioned and probably others as well that changing the name of the project would be disruptive to users. Users are used to using the malhar project and its artifacts a certain way and this would cause them immediate confusion followed by consternation and then changes that could extend beyond their application such as documentation etc.
Second the project has been around for quite some time and has reached a version 3.x, the second part of the proposed change is to reset it back to 1.0-SNAPSHOT. I don't think that is accurate for the project and the maturity it would portray to the users. Not to get subjective but there are operators in malhar that are best of the breed when it comes to streaming functionality they achieve. Third think about all the changes it would need, code, project infrastructure such as github repo and jira project, documentation, website etc and the time all the developers have to spend to adapt to this. Wouldn't we want to spend this time doing something more productive. I would think changing a project name and resetting the version is a big deal and should be done if there something big to gain for the project by doing this. What is the big gain we achieve to justify all this consternation? If we want to increase adoption, one of the things we need to do is to provide users with a platform that behaves in an expected and stable manner. Thanks On Wed, Aug 23, 2017 at 8:09 AM Vlad Rozov <vro...@apache.org> wrote: > All -1 are technically void at this point as justification given are why > project may continue without modifications and not why the modification > must not be done. Whether we proceed with the vote or with the > discussion, arguments should be what are pros and cons of a code change, > not that the project may continue without them. The same should apply > not only to the current set of changes, but to all future discussions. > > Thank you, > > Vlad > > On 8/23/17 06:54, Thomas Weise wrote: > > The discussion already took place [1]. There are two options under vote > out > > of that discussion and for the first option there is a single -1. Use of > -1 > > during voting (and veto on PR) when not showing up during the preceding > > discussion is problematic. > > > > Thomas > > > > [1] https://lists.apache.org/thread.html/bd1db8a2d01e23b0c0ab98a785f6ee > > 9492a1ac9e52d422568a46e5f3@%3Cdev.apex.apache.org%3E > > > > On Wed, Aug 23, 2017 at 1:58 AM, Justin Mclean <jus...@classsoftware.com > > > > wrote: > > > >> Hi, > >> > >> Votes are only valid on code modifications with a reason. [1] > >> > >> However it looks to me that there’s not consensus and which way forward > is > >> best I would suggest cancelling the vote and having a discussion of the > >> benefit or not of making the change. > >> > >> Thanks, > >> Justin > >> > >> 1. https://www.apache.org/foundation/voting.html > > > Thank you, > > Vlad >
