Hi Marcelo, Thanks for your reply. As a committer on the project, you *can* VETO code. For sure. Unfortunately you don’t have a binding vote on adding new PMC members/committers, and/or on releasing the software, but do have the ability to VETO.
That said, if that’s not your intent, sorry for misreading your intent. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA WWW: http://irds.usc.edu/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Marcelo Vanzin <van...@cloudera.com> Date: Friday, March 18, 2016 at 3:24 PM To: jpluser <mattm...@apache.org> Cc: "dev@spark.apache.org" <dev@spark.apache.org> Subject: Re: SPARK-13843 and future of streaming backends >On Fri, Mar 18, 2016 at 2:12 PM, chrismattmann <mattm...@apache.org> >wrote: >> So, my comment here is that any code *cannot* be removed from an Apache >> project if there is a VETO issued which so far I haven't seen, though >>maybe >> Marcelo can clarify that. > >No, my intention was not to veto the change. I'm actually for the >removal of components if the community thinks they don't add much to >the project. (I'm also not sure I can even veto things, not being a >PMC member.) > >I mainly wanted to know what was the path forward for those components >because, with Cloudera's hat on, we care about one of them (streaming >integration with flume), and we'd prefer if that code remained under >the ASF umbrella in some way. > >-- >Marcelo
