Re: [DISCUSS] YuniKorn Proposal
Hi Craig, In answer to your question: *If Apache does incubate and graduate Yunikorn as a top level project, we would require Cloudera to commit to recognize Yunikorn as an Apache project in all of its materials. Otherwise, there would be confusion in the market about whether Yunikorn was an Apache project or a Cloudera project. It cannot be both.If Cloudera can commit to not using Yunikorn to describe its own project once it graduates and becomes an Apache project, ok.If not, the Apache project will need to find a new name.* -- Cloudera can commit to using Apache YuniKorn if/when the YuniKorn project graduates. Thank you, Casey *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager t. (949) 201-3201 NOTICE: Prepared by a member of the Cloudera legal team. This message and any attachments may contain confidential and/or privileged information of Cloudera, Inc. and/or its affiliates. If you have received this communication in error, please advise the sender by reply email and immediately delete this message and any attachments without copying, reviewing, or disclosing the contents. Thank you for your cooperation. On Mon, Jan 6, 2020 at 1:05 PM Wangda Tan wrote: > + @Casey to answer the question since Casey may not > subscribe to incubator emails. > > Thanks > > On Sat, Dec 21, 2019 at 7:01 PM Craig Russell > wrote: > >> Hi Casey, >> >> > On Dec 20, 2019, at 10:31 AM, Casey wrote: >> > >> > Hi Folks, >> > >> > Cloudera does not have a trademark on YuniKorn; we do use the name in a >> few >> > places with a quick look. So there's no trademark assignment needed, >> but >> > if there is something else you'd like us to do related to any ownership >> > interest, please let me know. >> >> If Apache does incubate and graduate Yunikorn as a top level project, we >> would require Cloudera to commit to recognize Yunikorn as an Apache project >> in all of its materials. >> >> Otherwise, there would be confusion in the market about whether Yunikorn >> was an Apache project or a Cloudera project. It cannot be both. >> >> If Cloudera can commit to not using Yunikorn to describe its own project >> once it graduates and becomes an Apache project, ok. >> >> If not, the Apache project will need to find a new name. >> >> Regards >> Craig >> > >> > Regards, >> > Casey >> > >> > *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts >> Manager >> > t. (949) 201-3201 >> > >> > NOTICE: Prepared by a member of the Cloudera legal team. This message >> and any >> > attachments may contain confidential and/or privileged information of >> Cloudera, >> > Inc. and/or its affiliates. If you have received this communication in >> > error, please advise the sender by reply email and immediately delete >> this >> > message and any attachments without copying, reviewing, or disclosing >> the >> > contents. Thank you for your cooperation. >> > >> > >> > On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan wrote: >> > >> >> Added Casey Valk from Cloudera legal team to the thread to answer the >> >> question regarding trademark of YuniKorn. >> >> >> >> Best, >> >> Wangda >> >> >> >> On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan wrote: >> >> >> >>> Hi Justin/Craig, >> >>> >> >>> Thanks for sharing these information, very helpful. >> >>> >> >>> I think Cloudera doesn’t own the trademark and name. Checking with >> >>> cloudera legal now and will keep the thread posted. >> >>> >> >>> Thanks >> >>> >> >>> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean < >> jus...@classsoftware.com> >> >>> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> Again thanks for your replies. >> >>>> >> >>>>> *"The initial committers are from several relevant Apache projects >> who >> >>>> are >> >>>>> interested in YuniKorn and committed to giving guidance, suggestions >> >>>> to the >> >>>>> project, help to grow the community; and if possible, participants >> in >> >>>> code >> >>>>> development."* >> >>>>> >> >>>>> They're aware of the PPMC requirements, I don't think there's any >> >>>> surprise >> >>>>> to proposed initial committers. >> >>>> >> >>>> That great. A long way off but just be aware that if these people are >> >>>> listed on the graduation proposal for PMC members and they have not >> been >> >>>> active in the project that may delay graduation. >> >>>> >> >>>>> We have already got SGA (Software Grant Agreement) from Cloudera, >> I'm >> >>>> not >> >>>>> sure if we need to attach the SGA now, before vote or so. Is there >> any >> >>>>> additional documentation needed apart from SGA. >> >>>> >> >>>> No you don’t need to submit an SGA before voting on the proposal, >> what >> >>>> we need is a clear indication that your name is unlikely to change >> and that >> >>>> it’s Cloudera intent to hand over rights to the name.The name would >> not >> >>>> need to be transferred until graduation. >> >>>> >> >>>> Thanks, >> >>>> Justin >> >>> >> >>> >> >> Craig L Russell >> c...@apache.org >> >>
Re: [DISCUSS] YuniKorn Proposal
Hi Folks, Cloudera does not have a trademark on YuniKorn; we do use the name in a few places with a quick look. So there's no trademark assignment needed, but if there is something else you'd like us to do related to any ownership interest, please let me know. Regards, Casey *Cassandra L. Valk* | Open Source License Analyst / Sr. Contracts Manager t. (949) 201-3201 NOTICE: Prepared by a member of the Cloudera legal team. This message and any attachments may contain confidential and/or privileged information of Cloudera, Inc. and/or its affiliates. If you have received this communication in error, please advise the sender by reply email and immediately delete this message and any attachments without copying, reviewing, or disclosing the contents. Thank you for your cooperation. On Fri, Dec 20, 2019 at 1:22 PM Wangda Tan wrote: > Added Casey Valk from Cloudera legal team to the thread to answer the > question regarding trademark of YuniKorn. > > Best, > Wangda > > On Tue, Dec 17, 2019 at 10:56 PM Wangda Tan wrote: > >> Hi Justin/Craig, >> >> Thanks for sharing these information, very helpful. >> >> I think Cloudera doesn’t own the trademark and name. Checking with >> cloudera legal now and will keep the thread posted. >> >> Thanks >> >> On Tue, Dec 17, 2019 at 2:34 PM Justin Mclean >> wrote: >> >>> Hi, >>> >>> Again thanks for your replies. >>> >>> > *"The initial committers are from several relevant Apache projects who >>> are >>> > interested in YuniKorn and committed to giving guidance, suggestions >>> to the >>> > project, help to grow the community; and if possible, participants in >>> code >>> > development."* >>> > >>> > They're aware of the PPMC requirements, I don't think there's any >>> surprise >>> > to proposed initial committers. >>> >>> That great. A long way off but just be aware that if these people are >>> listed on the graduation proposal for PMC members and they have not been >>> active in the project that may delay graduation. >>> >>> > We have already got SGA (Software Grant Agreement) from Cloudera, I'm >>> not >>> > sure if we need to attach the SGA now, before vote or so. Is there any >>> > additional documentation needed apart from SGA. >>> >>> No you don’t need to submit an SGA before voting on the proposal, what >>> we need is a clear indication that your name is unlikely to change and that >>> it’s Cloudera intent to hand over rights to the name.The name would not >>> need to be transferred until graduation. >>> >>> Thanks, >>> Justin >> >>
Re: Don't forget to un-incubate
Thanks Greg, I'm on it; been a busy week. Sorry about that. Best, Casey On Fri, Apr 28, 2017 at 4:11 PM, Greg Stein wrote: > Apache Metron, > > You need to move to a TLP. It has been over a week since the Board meeting, > and Infrastructure has not seen any tickets filed to perform your move. > > I'd suggest stopping your 0.4.0 release and deal with moving to TLP status. > > Cheers, > Greg Stein > Infrastructure Administrator, ASF > > > On Wed, Apr 19, 2017 at 8:48 PM, John D. Ament > wrote: > > > Dear Fineract, Metron and CarbonData PMCs > > > > First of all, congratulations on your graduations today. > > > > I want to put out an early reminder that you should complete your > > un-incubation steps. Some of the infra steps require a director to hit a > > button, which may not have happened yet. However from the foundation's > > point of view you are graduated. You may be working on some publicity of > > the event with Sally, or expecting some follow up discussion, but that's > > it, you're done in the incubator. I would like to ask you (specifically > > the new chairs, but anyone on the new PMCs could as well) to complete > your > > post-incubation steps found at [1]. > > > > Regards, > > > > John > > > > [1]: http://incubator.apache.org/guides/graduation.html#unincubate > > >
[RESULT] [VOTE] Apache Metron podling Graduation
The vote passes with 8 binding +1s, 3 non-binding +1's Thanks to all the people who voted; the Metron community appreciates your support. Results: +1 (binding): * Josh Elser * Joe Witt * Taylor Goetz * John Ament * Julian Hyde * Suneel Marthi * Billie Rinaldi * Jake Farrell +1 (non-binding): * Larry McCay * Debo Dutta * Pierre Smits
[VOTE] Apache Metron podling Graduation
Hi Everyone, I propose that we graduate Apache Metron (incubating) from the incubator. The full text of the proposal is below, with requisite modifications applied from the discussion thread. The discuss thread can be found at https://lists.apache.org/thread.html/e5d106456b28562bdc947624c6f33e3281297dfd3803aab3d171bbad@%3Cgeneral.incubator.apache.org%3E Best, Casey Resolution: Establish the Apache Metron Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a security analytics platform for big data use cases. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Metron Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Metron Project be and hereby is responsible for the creation and maintenance of software related to: (a) A mechanism to capture, store, and normalize any type of security telemetry at extremely high rates. (b) Real time processing and application of enrichments (c) Efficient information storage (d) An interface that gives a security investigator a centralized view of data and alerts passed through the system. RESOLVED, that the office of "Vice President, Apache Metron" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Metron Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Metron Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Metron Project: PPMC by Affiliation: Hortonworks: Sheetal Dolas (sheetal_dolas) Ryan Merriman (rmerriman) Larry McCay (lmccay) P. Taylor Goetz (ptgoetz) Nick Allen (nickallen) David Lyle (lyle) George Vetticaden (gvetticaden) James Sirota (jsirota) Casey Stella (cstella) Michael Perez (mperez) Kiran Komaravolu (kirankom) Vinod Kumar Vavilapalli (vinodkv) Cisco: Debo Dutta (ddutta) Discovery Gerdes (discovery) Rackspace: Oskar Zabik (smogg) Andrew Hartnett (dev_warlord) Paul Kehrer (reaperhulk) Sean Schulte (sirsean) B23: Mark Bittmann (mbittmann) Dave Hirko (dbhirko) Brad Kolarov (bjkolly) Mantech: Charles Porter (cporter) Ray Urciuoli (rurcioli) Fogbeam Labs: Phillip Rhodes (prhodes) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella be appointed to the office of Vice President, Apache Metron, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Metron PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Metron Project; and be it further RESOLVED, that the Apache Metron Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Metron podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Metron podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [DISCUSS] Apache Metron podling Graduation
The discussion seems to have died down enough that I feel comfortable opening up a new VOTE thread. Thanks everyone who has contributed; I know that the Metron community appreciates the feedback and discussion. Best, Casey On Mon, Mar 27, 2017 at 1:48 PM, Casey Stella wrote: > Thanks Dave; I think that we all appreciate the concerns around > insulating the project from a single sponsor. The fact that we do take > the ASF processes seriously is one of the things that makes the community > comforted, I think. I appreciate the diligence in ensuring that we have > our ducks in a row from that perspective. > > Best, > > Casey > > On Mon, Mar 27, 2017 at 1:36 PM, Dave Fisher > wrote: > >> Hi, >> >> Thank you for the answers. >> >> I am all for graduation if Metron. >> >> Regards, >> Dave >> >> Sent from my iPhone >> >> > On Mar 27, 2017, at 10:25 AM, Casey Stella wrote: >> > >> > Hi Dave, >> > >> > To clarify, we have 24 PPMC members, of which 12 are >> Hortonworks-affiliated >> > and 12 are not. We have 6 additional committers who are not PPMC >> members. >> > Some of them are affiliated and some of them are not. For the purpose of >> > this, we only captured the affiliations of the PPMC members. >> > >> > I did some quick analysis of the git log and found the following: >> > >> > % Commits by Hortonworkers: 79% >> > >> > % Contributors affiliated to Hortonworks: 42% >> > >> > In associating affiliation, I am being as generous as possible and >> > including people who I know to work at Hortonworks who may or may not >> be in >> > the engineering organization. I know that some of these people are >> > contributing to Metron in their spare time as independent open source >> > contributions. >> > >> > >> > Best, >> > >> > Casey >> > >> >> On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher >> wrote: >> >> >> >> >> >> >> >> Sent from my iPhone >> >> >> >>> On Mar 24, 2017, at 9:03 PM, John D. Ament >> >> wrote: >> >>> >> >>>> On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz >> >> wrote: >> >>>> >> >>>> To be honest, I don't know, but I don't see it as a problem. >> >>>> >> >>>> I will admit upfront that I am a Hortonworks employee, so there is >> >>>> potential for bias. But I always try to wear the right hat, even >> when my >> >>>> position may not please my employer. >> >>>> >> >>>> As a mentor (to this and other podlings), I try to instill that ethic >> >>>> during incubation and thereafter. >> >>>> >> >>>> In the Metron community I see some that share that ethic. They >> selected >> >> a >> >>>> PMC Chair that gets it and I trust will serve the project well in >> that >> >> role. >> >>>> >> >>>> Yes, the project is Hortonworks-heavy. But I think they are doing >> things >> >>>> right in terms of the Apache Way. I also intend to participate in the >> >> PMC >> >>>> to help ensure it remains that way. >> >>>> >> >>>> >> >>> Agreed - from what I have seen, Hortonworks as a company understands >> the >> >>> Apache Way and is able to ensure that it is held in open source >> projects. >> >>> I see no concerns with Metron graduating. >> >> >> >> Sure, but the question is not about whether or not HortonWorks >> understands >> >> the Apache Way. It is what happens to Metron if HortonWorks is no >> longer >> >> interested in the project? >> >> >> >> Given the experience with OpenOffice I think we need to always ask >> this. >> >> >> >> Regards, >> >> Dave >> >> >> >>> >> >>> >> >>>> -Taylor >> >>>> >> >>>> >> >>>>> On Mar 24, 2017, at 8:15 PM, Dave Fisher >> >> wrote: >> >>>>> >> >>>>> This is a list of 24 of which 12 are Hortonworks. >> >>>>> >> >>>>> Can we assume that the other 12 of which 6 are PPMC are >> unaffiliated?
Re: [DISCUSS] Apache Metron podling Graduation
Thanks Dave; I think that we all appreciate the concerns around insulating the project from a single sponsor. The fact that we do take the ASF processes seriously is one of the things that makes the community comforted, I think. I appreciate the diligence in ensuring that we have our ducks in a row from that perspective. Best, Casey On Mon, Mar 27, 2017 at 1:36 PM, Dave Fisher wrote: > Hi, > > Thank you for the answers. > > I am all for graduation if Metron. > > Regards, > Dave > > Sent from my iPhone > > > On Mar 27, 2017, at 10:25 AM, Casey Stella wrote: > > > > Hi Dave, > > > > To clarify, we have 24 PPMC members, of which 12 are > Hortonworks-affiliated > > and 12 are not. We have 6 additional committers who are not PPMC members. > > Some of them are affiliated and some of them are not. For the purpose of > > this, we only captured the affiliations of the PPMC members. > > > > I did some quick analysis of the git log and found the following: > > > > % Commits by Hortonworkers: 79% > > > > % Contributors affiliated to Hortonworks: 42% > > > > In associating affiliation, I am being as generous as possible and > > including people who I know to work at Hortonworks who may or may not be > in > > the engineering organization. I know that some of these people are > > contributing to Metron in their spare time as independent open source > > contributions. > > > > > > Best, > > > > Casey > > > >> On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher > wrote: > >> > >> > >> > >> Sent from my iPhone > >> > >>> On Mar 24, 2017, at 9:03 PM, John D. Ament > >> wrote: > >>> > >>>> On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz > >> wrote: > >>>> > >>>> To be honest, I don't know, but I don't see it as a problem. > >>>> > >>>> I will admit upfront that I am a Hortonworks employee, so there is > >>>> potential for bias. But I always try to wear the right hat, even when > my > >>>> position may not please my employer. > >>>> > >>>> As a mentor (to this and other podlings), I try to instill that ethic > >>>> during incubation and thereafter. > >>>> > >>>> In the Metron community I see some that share that ethic. They > selected > >> a > >>>> PMC Chair that gets it and I trust will serve the project well in that > >> role. > >>>> > >>>> Yes, the project is Hortonworks-heavy. But I think they are doing > things > >>>> right in terms of the Apache Way. I also intend to participate in the > >> PMC > >>>> to help ensure it remains that way. > >>>> > >>>> > >>> Agreed - from what I have seen, Hortonworks as a company understands > the > >>> Apache Way and is able to ensure that it is held in open source > projects. > >>> I see no concerns with Metron graduating. > >> > >> Sure, but the question is not about whether or not HortonWorks > understands > >> the Apache Way. It is what happens to Metron if HortonWorks is no longer > >> interested in the project? > >> > >> Given the experience with OpenOffice I think we need to always ask this. > >> > >> Regards, > >> Dave > >> > >>> > >>> > >>>> -Taylor > >>>> > >>>> > >>>>> On Mar 24, 2017, at 8:15 PM, Dave Fisher > >> wrote: > >>>>> > >>>>> This is a list of 24 of which 12 are Hortonworks. > >>>>> > >>>>> Can we assume that the other 12 of which 6 are PPMC are unaffiliated? > >>>>> > >>>>> What percentage of the commits are coming from Hortonworks affiliated > >>>> contributors? > >>>>> > >>>>> Thanks, > >>>>> Dave > >>>>> > >>>>>> On Mar 23, 2017, at 8:39 PM, Casey Stella > wrote: > >>>>>> > >>>>>> Of course, very fair question. Also, yes, the we have 36 committers > >> as > >>>> all > >>>>>> PPMC members are committers. > >>>>>> > >>>>>> The affiliations are as follows: > >>>>>> > >>>>>> Hortonworks: > >>>>>> * Sheetal Dolas
Re: [DISCUSS] Apache Metron podling Graduation
Hi Dave, To clarify, we have 24 PPMC members, of which 12 are Hortonworks-affiliated and 12 are not. We have 6 additional committers who are not PPMC members. Some of them are affiliated and some of them are not. For the purpose of this, we only captured the affiliations of the PPMC members. I did some quick analysis of the git log and found the following: % Commits by Hortonworkers: 79% % Contributors affiliated to Hortonworks: 42% In associating affiliation, I am being as generous as possible and including people who I know to work at Hortonworks who may or may not be in the engineering organization. I know that some of these people are contributing to Metron in their spare time as independent open source contributions. Best, Casey On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher wrote: > > > Sent from my iPhone > > > On Mar 24, 2017, at 9:03 PM, John D. Ament > wrote: > > > >> On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz > wrote: > >> > >> To be honest, I don't know, but I don't see it as a problem. > >> > >> I will admit upfront that I am a Hortonworks employee, so there is > >> potential for bias. But I always try to wear the right hat, even when my > >> position may not please my employer. > >> > >> As a mentor (to this and other podlings), I try to instill that ethic > >> during incubation and thereafter. > >> > >> In the Metron community I see some that share that ethic. They selected > a > >> PMC Chair that gets it and I trust will serve the project well in that > role. > >> > >> Yes, the project is Hortonworks-heavy. But I think they are doing things > >> right in terms of the Apache Way. I also intend to participate in the > PMC > >> to help ensure it remains that way. > >> > >> > > Agreed - from what I have seen, Hortonworks as a company understands the > > Apache Way and is able to ensure that it is held in open source projects. > > I see no concerns with Metron graduating. > > Sure, but the question is not about whether or not HortonWorks understands > the Apache Way. It is what happens to Metron if HortonWorks is no longer > interested in the project? > > Given the experience with OpenOffice I think we need to always ask this. > > Regards, > Dave > > > > > > >> -Taylor > >> > >> > >>> On Mar 24, 2017, at 8:15 PM, Dave Fisher > wrote: > >>> > >>> This is a list of 24 of which 12 are Hortonworks. > >>> > >>> Can we assume that the other 12 of which 6 are PPMC are unaffiliated? > >>> > >>> What percentage of the commits are coming from Hortonworks affiliated > >> contributors? > >>> > >>> Thanks, > >>> Dave > >>> > >>>> On Mar 23, 2017, at 8:39 PM, Casey Stella wrote: > >>>> > >>>> Of course, very fair question. Also, yes, the we have 36 committers > as > >> all > >>>> PPMC members are committers. > >>>> > >>>> The affiliations are as follows: > >>>> > >>>> Hortonworks: > >>>> * Sheetal Dolas (sheetal_dolas) > >>>> * Larry McCay (lmccay) > >>>> * P. Taylor Goetz (ptgoetz) > >>>> * Ryan Merriman (rmerriman) > >>>> * James Sirota (jsirota) > >>>> * Casey Stella (cstella) > >>>> * David Lyle (lyle) > >>>> * Nick Allen (nickallen) > >>>> * George Vetticaden (gvetticaden) > >>>> * Vinod Kumar Vavilapalli (vinodkv) > >>>> * Kiran Komaravolu (kirankom) > >>>> * Michael Perez (mperez) > >>>> > >>>> Cisco: > >>>> * Debo Dutta (ddutta) > >>>> * Discovery Gerdes (discovery) > >>>> > >>>> Rackspace: > >>>> * Oskar Zabik (smogg) > >>>> * Andrew Hartnett (dev_warlord) > >>>> * Paul Kehrer (reaperhulk) > >>>> * Sean Schulte (sirsean) > >>>> > >>>> B23: > >>>> * Mark Bittmann (mbittmann) > >>>> * Dave Hirko (dbhirko) > >>>> * Brad Kolarov (bjkolly) > >>>> > >>>> Mantech: > >>>> * Charles Porter (cporter) > >>>> * Ray Urciuoli (rurcioli) > >>>> > >>>> Fogbeam Labs: > >>>> * Phillip Rhodes (prhodes) > >>>> > >>>> > >>>> > >>>> > >>>> > >&g
Re: [DISCUSS] Apache Metron podling Graduation
Well, the metron community appreciates your +1 as a sign of goodwill. ;) On Fri, Mar 24, 2017 at 1:11 AM, Niclas Hedhman wrote: > Sorry, I probably didn't read the subject line, and draw wrong conclusion > when seeing the proposed resolution... > > On Fri, Mar 24, 2017 at 12:19 PM, Dave Fisher > wrote: > > > This is not a VOTE thread. There is a misstatement to clear up. What part > > of the maturity model is ongoing? > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Mar 23, 2017, at 5:05 PM, Niclas Hedhman > wrote: > > > > > > +1 (binding) > > > > > >> On Fri, Mar 24, 2017 at 2:32 AM, Casey Stella > > wrote: > > >> > > >> Hi Everyone, > > >> > > >> The incubating Apache Metron community believes it is time to graduate > > >> to TLP. > > >> > > >> Apache Metron entered incubation in December of 2015. Since then, > we've > > >> overcome technical challenges to remove Category X dependencies, and > > >> made 3 releases. Our most recent release contains binary convenience > > >> artifacts. We are a very helpful and engaged community, ready to > answer > > >> all questions and feedback directed to us via the user list. Through > our > > >> time in incubation we've added a number of committers and promoted > some > > >> of them to PPMC membership. We are actively pursuing others. While we > do > > >> still have issues to address raised by means of the maturity model, > all > > >> projects are ongoing processes, and we believe we no longer need the > > >> incubator to continue addressing these issues. > > >> > > >> To inform the discussion, here is some basic project information: > > >> > > >> Project status: > > >> http://incubator.apache.org/projects/metron.html > > >> > > >> Project website: > > >> https://metron.incubator.apache.org/ > > >> > > >> Project documentation: > > >> https://cwiki.apache.org/confluence/display/METRON/Documentation > > >> > > >> Maturity assessment: > > >> > > >> https://cwiki.apache.org/confluence/display/METRON/ > > >> Apache+Project+Maturity+Model > > >> > > >> Community Vote to Graduate: > > >> > > >> https://lists.apache.org/thread.html/540378e2773b1b2ce2af498e56a643 > > >> 5e547c04948a6b496b9a4ffc71@%3Cdev.metron.apache.org%3E > > >> > > >> DRAFT of the board resolution is at the bottom of this email > > >> > > >> Proposed PMC size: 24 members > > >> > > >> Total number of committers: 6 members > > >> > > >> > > >> 516 commits on develop > > >> 34 contributors across all branches > > >> > > >> dev list averaged ~650 msgs/month for the last 3 months > > >> > > >> > > >> Resolution: > > >> > > >> Establish the Apache Metron Project > > >> > > >> WHEREAS, the Board of Directors deems it to be in the best > > >> interests of the Foundation and consistent with the > > >> Foundation's purpose to establish a Project Management > > >> Committee charged with the creation and maintenance of > > >> open-source software, for distribution at no charge to the > > >> public, related to a security analytics platform for big data use > cases. > > >> > > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > >> Committee (PMC), to be known as the "Apache Metron Project", > > >> be and hereby is established pursuant to Bylaws of the > > >> Foundation; and be it further > > >> > > >> RESOLVED, that the Apache Metron Project be and hereby is > > >> responsible for the creation and maintenance of software > > >> related to: > > >> (a) A mechanism to capture, store, and normalize any type of security > > >> telemetry at extremely high rates. > > >> (b) Real time processing and application of enrichments > > >> (c) Efficient information storage > > >> (d) An interface that gives a security investigator a centralized view > > >> of data and alerts passed through the system. > > >> > > >> RESOLVED, that the office of "Vice President, Apache Metron" be > > &
Re: [DISCUSS] Apache Metron podling Graduation
Right you are, this is not a VOTE thread. That would be premature at this stage until a robust discussion happens here. Regarding the maturity model, we have self-assessed our readiness based on the Apache Maturity model at https://cwiki.apache.org/confluence/display/METRON/Apache+Project+Maturity+Model On Fri, Mar 24, 2017 at 12:19 AM, Dave Fisher wrote: > This is not a VOTE thread. There is a misstatement to clear up. What part > of the maturity model is ongoing? > > Regards, > Dave > > Sent from my iPhone > > > On Mar 23, 2017, at 5:05 PM, Niclas Hedhman wrote: > > > > +1 (binding) > > > >> On Fri, Mar 24, 2017 at 2:32 AM, Casey Stella > wrote: > >> > >> Hi Everyone, > >> > >> The incubating Apache Metron community believes it is time to graduate > >> to TLP. > >> > >> Apache Metron entered incubation in December of 2015. Since then, we've > >> overcome technical challenges to remove Category X dependencies, and > >> made 3 releases. Our most recent release contains binary convenience > >> artifacts. We are a very helpful and engaged community, ready to answer > >> all questions and feedback directed to us via the user list. Through our > >> time in incubation we've added a number of committers and promoted some > >> of them to PPMC membership. We are actively pursuing others. While we do > >> still have issues to address raised by means of the maturity model, all > >> projects are ongoing processes, and we believe we no longer need the > >> incubator to continue addressing these issues. > >> > >> To inform the discussion, here is some basic project information: > >> > >> Project status: > >> http://incubator.apache.org/projects/metron.html > >> > >> Project website: > >> https://metron.incubator.apache.org/ > >> > >> Project documentation: > >> https://cwiki.apache.org/confluence/display/METRON/Documentation > >> > >> Maturity assessment: > >> > >> https://cwiki.apache.org/confluence/display/METRON/ > >> Apache+Project+Maturity+Model > >> > >> Community Vote to Graduate: > >> > >> https://lists.apache.org/thread.html/540378e2773b1b2ce2af498e56a643 > >> 5e547c04948a6b496b9a4ffc71@%3Cdev.metron.apache.org%3E > >> > >> DRAFT of the board resolution is at the bottom of this email > >> > >> Proposed PMC size: 24 members > >> > >> Total number of committers: 6 members > >> > >> > >> 516 commits on develop > >> 34 contributors across all branches > >> > >> dev list averaged ~650 msgs/month for the last 3 months > >> > >> > >> Resolution: > >> > >> Establish the Apache Metron Project > >> > >> WHEREAS, the Board of Directors deems it to be in the best > >> interests of the Foundation and consistent with the > >> Foundation's purpose to establish a Project Management > >> Committee charged with the creation and maintenance of > >> open-source software, for distribution at no charge to the > >> public, related to a security analytics platform for big data use cases. > >> > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management > >> Committee (PMC), to be known as the "Apache Metron Project", > >> be and hereby is established pursuant to Bylaws of the > >> Foundation; and be it further > >> > >> RESOLVED, that the Apache Metron Project be and hereby is > >> responsible for the creation and maintenance of software > >> related to: > >> (a) A mechanism to capture, store, and normalize any type of security > >> telemetry at extremely high rates. > >> (b) Real time processing and application of enrichments > >> (c) Efficient information storage > >> (d) An interface that gives a security investigator a centralized view > >> of data and alerts passed through the system. > >> > >> RESOLVED, that the office of "Vice President, Apache Metron" be > >> and hereby is created, the person holding such office to > >> serve at the direction of the Board of Directors as the chair > >> of the Apache Metron Project, and to have primary responsibility > >> for management of the projects within the scope of > >> responsibility of the Apache Metron Project; and be it further > >> > >> RESOLVED, that the persons listed immediately below be and > >> hereby
Re: [DISCUSS] Apache Metron podling Graduation
Of course, very fair question. Also, yes, the we have 36 committers as all PPMC members are committers. The affiliations are as follows: Hortonworks: * Sheetal Dolas (sheetal_dolas) * Larry McCay (lmccay) * P. Taylor Goetz (ptgoetz) * Ryan Merriman (rmerriman) * James Sirota (jsirota) * Casey Stella (cstella) * David Lyle (lyle) * Nick Allen (nickallen) * George Vetticaden (gvetticaden) * Vinod Kumar Vavilapalli (vinodkv) * Kiran Komaravolu (kirankom) * Michael Perez (mperez) Cisco: * Debo Dutta (ddutta) * Discovery Gerdes (discovery) Rackspace: * Oskar Zabik (smogg) * Andrew Hartnett (dev_warlord) * Paul Kehrer (reaperhulk) * Sean Schulte (sirsean) B23: * Mark Bittmann (mbittmann) * Dave Hirko (dbhirko) * Brad Kolarov (bjkolly) Mantech: * Charles Porter (cporter) * Ray Urciuoli (rurcioli) Fogbeam Labs: * Phillip Rhodes (prhodes) On Thu, Mar 23, 2017 at 9:34 PM, P. Taylor Goetz wrote: > > > > On Mar 23, 2017, at 7:38 PM, John D. Ament > wrote: > > > >> On Thu, Mar 23, 2017 at 3:10 PM P. Taylor Goetz > wrote: > >> > >> As a mentor, I fully support Metron's graduation. The community has > come a > >> long way, learned to make solid releases, build a sustainable community, > >> and follow the Apache Way. > >> > >> One minor nit: The paddling status page is missing a few Apache IDs, > but I > >> see them in the resolution, so it's an easy fix. > >> > >> > > Paddlings are always out of sync :-P > > > > One other nit - I'm not sure why you only have 6 committers. I think you > > mean 30 committers (all PMC members are committers). Can you provide the > > associations of PMC members and employers? > > Metron PPMC, > > Can you respond? I feel this is a valid question. > > -Taylor > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[DISCUSS] Apache Metron podling Graduation
Hi Everyone, The incubating Apache Metron community believes it is time to graduate to TLP. Apache Metron entered incubation in December of 2015. Since then, we've overcome technical challenges to remove Category X dependencies, and made 3 releases. Our most recent release contains binary convenience artifacts. We are a very helpful and engaged community, ready to answer all questions and feedback directed to us via the user list. Through our time in incubation we've added a number of committers and promoted some of them to PPMC membership. We are actively pursuing others. While we do still have issues to address raised by means of the maturity model, all projects are ongoing processes, and we believe we no longer need the incubator to continue addressing these issues. To inform the discussion, here is some basic project information: Project status: http://incubator.apache.org/projects/metron.html Project website: https://metron.incubator.apache.org/ Project documentation: https://cwiki.apache.org/confluence/display/METRON/Documentation Maturity assessment: https://cwiki.apache.org/confluence/display/METRON/Apache+Project+Maturity+Model Community Vote to Graduate: https://lists.apache.org/thread.html/540378e2773b1b2ce2af498e56a6435e547c04948a6b496b9a4ffc71@%3Cdev.metron.apache.org%3E DRAFT of the board resolution is at the bottom of this email Proposed PMC size: 24 members Total number of committers: 6 members 516 commits on develop 34 contributors across all branches dev list averaged ~650 msgs/month for the last 3 months Resolution: Establish the Apache Metron Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a security analytics platform for big data use cases. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Metron Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Metron Project be and hereby is responsible for the creation and maintenance of software related to: (a) A mechanism to capture, store, and normalize any type of security telemetry at extremely high rates. (b) Real time processing and application of enrichments (c) Efficient information storage (d) An interface that gives a security investigator a centralized view of data and alerts passed through the system. RESOLVED, that the office of "Vice President, Apache Metron" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Metron Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Metron Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Metron Project: PPMC: Mark Bittmann (mbittmann) Sheetal Dolas (sheetal_dolas) Debo Dutta (ddutta) Discovery Gerdes (discovery) Andrew Hartnett (dev_warlord) Dave Hirko (dbhirko) Paul Kehrer (reaperhulk) Brad Kolarov (bjkolly) Kiran Komaravolu (kirankom) Larry McCay (lmccay) P. Taylor Goetz (ptgoetz) Ryan Merriman (rmerriman) Michael Perez (mperez) Charles Porter (cporter) Phillip Rhodes (prhodes) Sean Schulte (sirsean) James Sirota (jsirota) Casey Stella (cstella) Ray Urciuoli(rurcioli) Vinod Kumar Vavilapalli (vinodkv) George Vetticaden (gvetticaden) Oskar Zabik (smogg) David Lyle (lyle) Nick Allen (nickallen) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella be appointed to the office of Vice President, Apache Metron, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Metron PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Metron Project; and be it further RESOLVED, that the Apache Metron Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Metron podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Metron podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5
A quick addendum for the record. I created JIRAs (and patches where easy to do) for the issues that Josh pointed out: - Remove the overreaching rat exclusions from the build ( https://issues.apache.org/jira/browse/METRON-768) - Clean up the license (https://issues.apache.org/jira/browse/METRON-767, PR at https://github.com/apache/incubator-metron/pull/478) Also, because I know this was a comment in a previous RC's voting (from John Ament), I want to point out that we did remove the old release from the dist area when we promoted 0.3.1 ( https://dist.apache.org/repos/dist/release/incubator/metron/). Thanks again for all who looked at our release. If I could send you cookies, I would. :) On Wed, Mar 15, 2017 at 4:05 PM, Casey Stella wrote: > This vote passes with 3 binding +1's: > * Taylor Goetz > * Josh Elser > * Billie Rinaldi > > Thanks to all reviewers. > > On Wed, Mar 15, 2017 at 4:02 PM, P. Taylor Goetz > wrote: > >> +1 (binding) >> >> - signature checks out >> - DISCLAIMER exists >> - L&N look good >> - “incubating” in package name >> - can build from source (had to skip tests) >> >> -Taylor >> >> > On Feb 27, 2017, at 1:53 PM, Casey Stella wrote: >> > >> > This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating >> > >> > Full list of changes in this release: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 >> > -incubating/CHANGES >> > >> > The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating: >> > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> > git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc5-incubating >> > >> > The source archive being voted upon can be found here: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 >> > -incubating/apache-metron-0.3.1-rc5-incubating.tar.gz >> > >> > Other release files, signatures and digests can be found here: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 >> > -incubating/ >> > >> > The release artifacts are signed with the following key: >> > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> > git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e >> ;hb=refs/tags/ >> > apache-metron-0.3.1-rc5-incubating >> > >> > The book associated with this RC is located at >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 >> > -incubating/book-site/index.html >> > >> > Please vote on releasing this package as Apache Metron 0.3.1-RC5 >> incubating >> > >> > When voting, please list the actions taken to verify the release. >> > >> > Recommended build validation and verification instructions are posted >> here: >> > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds >> > >> > >> > This vote will be open for at least 72 hours. >> > >> > [ ] +1 Release this package as Apache Metron 0.3.1-RC5 incubating >> > >> > [ ] 0 No opinion >> > >> > [ ] -1 Do not release this package because... >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5
This vote passes with 3 binding +1's: * Taylor Goetz * Josh Elser * Billie Rinaldi Thanks to all reviewers. On Wed, Mar 15, 2017 at 4:02 PM, P. Taylor Goetz wrote: > +1 (binding) > > - signature checks out > - DISCLAIMER exists > - L&N look good > - “incubating” in package name > - can build from source (had to skip tests) > > -Taylor > > > On Feb 27, 2017, at 1:53 PM, Casey Stella wrote: > > > > This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating > > > > Full list of changes in this release: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 > > -incubating/CHANGES > > > > The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. > > git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc5-incubating > > > > The source archive being voted upon can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 > > -incubating/apache-metron-0.3.1-rc5-incubating.tar.gz > > > > Other release files, signatures and digests can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 > > -incubating/ > > > > The release artifacts are signed with the following key: > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. > > git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d > 9c260ba55e;hb=refs/tags/ > > apache-metron-0.3.1-rc5-incubating > > > > The book associated with this RC is located at > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 > > -incubating/book-site/index.html > > > > Please vote on releasing this package as Apache Metron 0.3.1-RC5 > incubating > > > > When voting, please list the actions taken to verify the release. > > > > Recommended build validation and verification instructions are posted > here: > > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds > > > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Metron 0.3.1-RC5 incubating > > > > [ ] 0 No opinion > > > > [ ] -1 Do not release this package because... > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5
This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating Full list of changes in this release: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 -incubating/CHANGES The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc5-incubating The source archive being voted upon can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 -incubating/apache-metron-0.3.1-rc5-incubating.tar.gz Other release files, signatures and digests can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 -incubating/ The release artifacts are signed with the following key: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/ apache-metron-0.3.1-rc5-incubating The book associated with this RC is located at https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5 -incubating/book-site/index.html Please vote on releasing this package as Apache Metron 0.3.1-RC5 incubating When voting, please list the actions taken to verify the release. Recommended build validation and verification instructions are posted here: https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds This vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Metron 0.3.1-RC5 incubating [ ] 0 No opinion [ ] -1 Do not release this package because...
[RESULT] [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4
The vote was cancelled and the RC was retracted due to a build issue. Vote Summary: +1 (binding) - John D. Ament
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4
Hi all, Unfortunately, the Metron community has decided to retract this release candidate. We were bitten by an issue with one of our dependencies handles its dependencies (see https://github.com/maxmind/GeoIP2-java/issues/77 for the morbidly curious). As such, our build no longer works and we decided to pull back the RC and fix the build and re-cut a fresh RC. Thanks for your patience. Casey On Thu, Feb 16, 2017 at 1:38 PM, Casey Stella wrote: > Ha, yes indeed John :) > > On Wed, Feb 15, 2017 at 16:43 John D. Ament wrote: > >> +1 release contents look good. >> >> Please don't forget as a part of >> https://issues.apache.org/jira/browse/METRON-589 I'll be expecting to see >> you remove 0.3.0 once 0.3.1 is published. >> >> John >> >> On Wed, Feb 15, 2017 at 10:21 AM Casey Stella wrote: >> >> > This is a call to vote on releasing Apache Metron 0.3.1-RC4 incubating >> > >> > Full list of changes in this release: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. >> > 1-RC4-incubating/CHANGES >> > >> > The tag/commit to be voted upon is apache-metron-0.3.1-rc4-incubating: >> > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> > git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc4-incubating >> > >> > The source archive being voted upon can be found here: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. >> > 1-RC4-incubating/apache-metron-0.3.1-rc4-incubating.tar.gz >> > >> > Other release files, signatures and digests can be found here: >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. >> > 1-RC4-incubating/ >> > >> > The release artifacts are signed with the following key: >> > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> > git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d >> 9c260ba55e;hb=refs/tags/ >> > apache-metron-0.3.1-rc4-incubating >> > >> > The book associated with this RC is located at >> > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. >> > 1-RC4-incubating/book-site/index.html >> > >> > Please vote on releasing this package as Apache Metron 0.3.1-RC4 >> incubating >> > >> > When voting, please list the actions taken to verify the release. >> > >> > Recommended build validation and verification instructions are posted >> here: >> > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds >> > >> > >> > This vote will be open for at least 72 hours. >> > >> > [ ] +1 Release this package as Apache Metron 0.3.1-RC4 incubating >> > >> > [ ] 0 No opinion >> > >> > [ ] -1 Do not release this package because... >> > >> >
Re: Machine Learning in METRON
Hi Martin and David, I certainly do take your point about the documentation being hosted in github. This is why, as of the release being voted on presently in incubator-general, we gather the readme's into a coherent set of webpages versioned by release and will be publishing them to the website (for the curious, you can see it at https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC4-incubating/book-site/index.html for the current release candidate being voted on). On the first page is documentation about building the product. I think you are right though; we should make the current release documentation front-and-center on the webpage. That being said, I appreciate your taking the time to dig through our docs and apologize if it was difficult. If you have any other impressions or suggestions that you'd like to share, we would love to have them on any of our podling-specific mailing lists. Thanks again, Casey On Sat, Feb 18, 2017 at 6:53 PM, David Jencks < david_jen...@yahoo.com.invalid> wrote: > I know nothing whatsoever about metron, but poking around the metron > website I found > Dev VM Install <https://cwiki.apache.org/confluence/display/METRON/Dev+ > VM+Install> > leading to https://github.com/apache/incubator-metron/tree/master/ > metron-deployment/vagrant/full-dev-platform which appears to have build > instructions… > cd incubator-metron > mvn clean package -DskipTests > I tend to think that if this project actually does love its community it > would make some information about how to check out the code and build > really really extremely blatantly obvious from the front page of the > website and also explain why the instructions I found are at GitHub rather > than apache. > > david jencks > > > On Feb 18, 2017, at 6:28 PM, Martin Gainty wrote: > > > > Casey/Sergio: > > > > > > i appreciate the plethora of documentation on maintaining > licenses..looking for doc on > > how to build metron? > > > > can i assume these preliminary steps: > > > > > > compile? > > > > jar? > > > > build binary for vm? > > > > yaml deploy to vm? > > > > re: certs/keys to coordinate to security config.. if so where to acquire > cert(s)/key(s)? > > > > > > Martin > > __ > > > > > > > > > > From: Casey Stella mailto:ceste...@gmail.com>> > > Sent: Friday, February 17, 2017 9:30 AM > > To: general@incubator.apache.org <mailto:general@incubator.apache.org> > > Subject: Re: Machine Learning in METRON > > > > Oh, one more thing. There's a small, but important typo in the email > > address for the mailing list by Sergio: it's > > u...@metron.incubator.apache.org (subscribe by sending an email to > > user-subscr...@metron.incubator.apache.org) > > > > On Fri, Feb 17, 2017 at 6:26 AM, Casey Stella > wrote: > > > >> Just wanted to chime in and reinforce that you should engage with the > >> Metron community as Sergio says. We love our community and are happy to > >> help where we can. :) > >> > >> Casey > >> > >> On Fri, Feb 17, 2017 at 1:21 AM, Sergio Fernández > >> wrote: > >> > >>> Hi, > >>> > >>> you can find the documentation at > >>> http://metron.incubator.apache.org/documentation/ > > Apache Metron (Incubating) Documentation<http://metron. > incubator.apache.org/documentation/ <http://metron.incubator. > apache.org/documentation/>> > > metron.incubator.apache.org <http://metron.incubator.apache.org/> > > The Quick Start installation fully automates the provisioning and > deployment of Apache Metron (Incubating) and all necessary prerequisites on > a single, virtualized ... > > > > > > > >>> > >>> You should better reach the folks directly at > >>> us...@metron.incubator.apache.org (subscribed sending fist a mail to > >>> users-subscr...@metron.incubator.apache.org). > >>> > >>> Cheers, > >>> > >>> On Feb 17, 2017 10:13, "Savakh S" wrote: > >>> > >>>> Hello, > >>>> > >>>> I saw METRON can do machine learning analysis but I didn't find this > >>>> feature when I installed the product. Could you please explain me more > >>>> about ML in METRON ? > >>>> > >>>> Many thanks. > >>>> > >>>> BR > >
Re: Machine Learning in METRON
Oh, one more thing. There's a small, but important typo in the email address for the mailing list by Sergio: it's u...@metron.incubator.apache.org (subscribe by sending an email to user-subscr...@metron.incubator.apache.org) On Fri, Feb 17, 2017 at 6:26 AM, Casey Stella wrote: > Just wanted to chime in and reinforce that you should engage with the > Metron community as Sergio says. We love our community and are happy to > help where we can. :) > > Casey > > On Fri, Feb 17, 2017 at 1:21 AM, Sergio Fernández > wrote: > >> Hi, >> >> you can find the documentation at >> http://metron.incubator.apache.org/documentation/ >> >> You should better reach the folks directly at >> us...@metron.incubator.apache.org (subscribed sending fist a mail to >> users-subscr...@metron.incubator.apache.org). >> >> Cheers, >> >> On Feb 17, 2017 10:13, "Savakh S" wrote: >> >> > Hello, >> > >> > I saw METRON can do machine learning analysis but I didn't find this >> > feature when I installed the product. Could you please explain me more >> > about ML in METRON ? >> > >> > Many thanks. >> > >> > BR >> > >> > >
Re: Machine Learning in METRON
Just wanted to chime in and reinforce that you should engage with the Metron community as Sergio says. We love our community and are happy to help where we can. :) Casey On Fri, Feb 17, 2017 at 1:21 AM, Sergio Fernández wrote: > Hi, > > you can find the documentation at > http://metron.incubator.apache.org/documentation/ > > You should better reach the folks directly at > us...@metron.incubator.apache.org (subscribed sending fist a mail to > users-subscr...@metron.incubator.apache.org). > > Cheers, > > On Feb 17, 2017 10:13, "Savakh S" wrote: > > > Hello, > > > > I saw METRON can do machine learning analysis but I didn't find this > > feature when I installed the product. Could you please explain me more > > about ML in METRON ? > > > > Many thanks. > > > > BR > > >
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4
Ha, yes indeed John :) On Wed, Feb 15, 2017 at 16:43 John D. Ament wrote: > +1 release contents look good. > > Please don't forget as a part of > https://issues.apache.org/jira/browse/METRON-589 I'll be expecting to see > you remove 0.3.0 once 0.3.1 is published. > > John > > On Wed, Feb 15, 2017 at 10:21 AM Casey Stella wrote: > > > This is a call to vote on releasing Apache Metron 0.3.1-RC4 incubating > > > > Full list of changes in this release: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. > > 1-RC4-incubating/CHANGES > > > > The tag/commit to be voted upon is apache-metron-0.3.1-rc4-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. > > git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc4-incubating > > > > The source archive being voted upon can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. > > 1-RC4-incubating/apache-metron-0.3.1-rc4-incubating.tar.gz > > > > Other release files, signatures and digests can be found here: > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. > > 1-RC4-incubating/ > > > > The release artifacts are signed with the following key: > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron. > > > git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/ > > apache-metron-0.3.1-rc4-incubating > > > > The book associated with this RC is located at > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. > > 1-RC4-incubating/book-site/index.html > > > > Please vote on releasing this package as Apache Metron 0.3.1-RC4 > incubating > > > > When voting, please list the actions taken to verify the release. > > > > Recommended build validation and verification instructions are posted > here: > > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds > > > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Metron 0.3.1-RC4 incubating > > > > [ ] 0 No opinion > > > > [ ] -1 Do not release this package because... > > >
[VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4
This is a call to vote on releasing Apache Metron 0.3.1-RC4 incubating Full list of changes in this release: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 1-RC4-incubating/CHANGES The tag/commit to be voted upon is apache-metron-0.3.1-rc4-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc4-incubating The source archive being voted upon can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 1-RC4-incubating/apache-metron-0.3.1-rc4-incubating.tar.gz Other release files, signatures and digests can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 1-RC4-incubating/ The release artifacts are signed with the following key: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/ apache-metron-0.3.1-rc4-incubating The book associated with this RC is located at https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 1-RC4-incubating/book-site/index.html Please vote on releasing this package as Apache Metron 0.3.1-RC4 incubating When voting, please list the actions taken to verify the release. Recommended build validation and verification instructions are posted here: https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds This vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Metron 0.3.1-RC4 incubating [ ] 0 No opinion [ ] -1 Do not release this package because...
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1
This vote passed with +1s (all binding) Billie Rinaldi Stian Soiland-Reyes Julian Hyde Justin Mclean John D. Ament Thanks, Casey On Mon, Nov 28, 2016 at 1:57 PM, Casey Stella wrote: > Hi Stian, > > We can clarify the licensing around Stix in the next release, no problem. > It is my understanding that it is 3-clause BSD. > > Casey > > On Wed, Nov 23, 2016 at 12:48 PM, Stian Soiland-Reyes > wrote: > >> My vote: +1 (binding) >> >> +1 git tag matches src (commit >> 7aea4ba35d1a931d72898bffd9725be3075fe8ca) (except site/ and .git*) >> +1 .asc signatures match, key in KEYS >> +0 .sha/.md5 hashes correct - could these have more conventional >> format and filenames? >> -0 Vote email didn't reference hash values or dist.apache.org SVN >> revision number (I assume r16997) >> +0 No need for DISCLAIMER or LICENSE within dist folder >> +1 apache- and -incubator in file/folder-name >> +1 DISCLAIMER present in archive >> +1 NOTICE present in archive with attributions (you don't need the >> indentation) >> +1 LICENSE present. (first newline missing, indentation wrong on first >> line. Very long line in extension) >> -0 STIX BSD license not included, URL is wrong. >> +1 mvn apache-rat:check >> -1 mvn install crashes my X server (!) (See below) >> +1 No unexpected binaries (except test data, serialized from Hadoop?) >> >> >> For the next release vote, could you include either the git commit ID >> (not just tag) or the hash of the source archive? for archival >> purposes? >> >> For the next release's LICENSE, download >> http://www.apache.org/licenses/LICENSE-2.0.txt and add at the end your >> extensions about the Stix project as you have already, except perhaps >> wrap the long lines. >> >> For the next release, could you include the STIX license as it was at >> the point of importing? A link like >> > available under a BSD license. For details, see >> http://stix.mitre.org/about/termsofuse.html >> >> This is not enough long term as the license is not versioned and can >> change later - in fact the URL already redirects to >> http://stixproject.github.io/about/ which points to >> http://stixproject.github.io/legal/ which points back to /about/ - and >> so I can't find the actual STIX license to verify this. >> >> Add it as a file like licenses/STIX.LICENSE.txt and refer to that from >> the top level LICENSE and the file headers. (don't remove the old >> file headers, just augment) >> >> >> My +1 vote assumes this STIX license is a BSD-3-clause or 2-Clause, if >> it is a BSD-4 clause it is NOT open source or compatible and my vote >> would be -1. >> >> >> For the hashes I would have preferred the style: >> >> apache-metron-0.3.0-rc1-incubating.tar.gz.sha1 containing: >> 080a54dd02cfe9fa91cd92305726443302ef250e >> apache-metron-0.3.0-rc1-incubating.tar.gz >> >> apache-metron-0.3.0-rc1-incubating.tar.gz.md5 containing: >> 1cc8ecfac074d5667845b835e28f6403 apache-metron-0.3.0-rc1-incuba >> ting.tar.gz >> >> ..or Maven-compatible without the spaces, filename or newline (no >> spacing within the hash value) >> >> >> (You may fix the hashes for this RC before you svn mv on dist) >> >> >> >> Below details about test failures only: >> >> >> >> The unit tests of metron-analytics/metron-maas-service crashes my X >> server on Ubuntu 16.04 with Nvidia drivers..! Not sure why it would >> touch X? >> >> It happens right after it says once "Found endpoint >> biggieubuntu:someport" (my hostname). -- sorry it crashed a bit too >> fast to check the port number! >> >> mvn clean install -DskipTests works though, so I won't fail this >> particular vote. >> >> >> I had a similar problem with mvn clean install within >> >> docker run -it maven:3-jdk-8 bash >> >> (which take a while in metron-maas-service) - that does a lot of >> echo-endpoint things, but then fails with >> >> Found endpoints: dummy:1.0 @ http://c6ced9e36c5e:1500 serving: >> apply=echo >> Cleaning up... >> Killing 1413 from 1413 ?00:00:00 dummy_rest.sh >> 2016-11-23 17:33:23,070 ERROR [Thread[Thread-615,5,main]] >> delegation.AbstractDelegationTokenSecretManager >> (AbstractDelegationTokenSecretManager.java:run(659)) - >> ExpiredTokenRemover received java.lang.InterruptedException: sleep >> interrupted >> 2016-11-23 17:33:23,183 ERROR [Thread[Thread-
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1
Hi Stian, We can clarify the licensing around Stix in the next release, no problem. It is my understanding that it is 3-clause BSD. Casey On Wed, Nov 23, 2016 at 12:48 PM, Stian Soiland-Reyes wrote: > My vote: +1 (binding) > > +1 git tag matches src (commit > 7aea4ba35d1a931d72898bffd9725be3075fe8ca) (except site/ and .git*) > +1 .asc signatures match, key in KEYS > +0 .sha/.md5 hashes correct - could these have more conventional > format and filenames? > -0 Vote email didn't reference hash values or dist.apache.org SVN > revision number (I assume r16997) > +0 No need for DISCLAIMER or LICENSE within dist folder > +1 apache- and -incubator in file/folder-name > +1 DISCLAIMER present in archive > +1 NOTICE present in archive with attributions (you don't need the > indentation) > +1 LICENSE present. (first newline missing, indentation wrong on first > line. Very long line in extension) > -0 STIX BSD license not included, URL is wrong. > +1 mvn apache-rat:check > -1 mvn install crashes my X server (!) (See below) > +1 No unexpected binaries (except test data, serialized from Hadoop?) > > > For the next release vote, could you include either the git commit ID > (not just tag) or the hash of the source archive? for archival > purposes? > > For the next release's LICENSE, download > http://www.apache.org/licenses/LICENSE-2.0.txt and add at the end your > extensions about the Stix project as you have already, except perhaps > wrap the long lines. > > For the next release, could you include the STIX license as it was at > the point of importing? A link like > > available under a BSD license. For details, see > http://stix.mitre.org/about/termsofuse.html > > This is not enough long term as the license is not versioned and can > change later - in fact the URL already redirects to > http://stixproject.github.io/about/ which points to > http://stixproject.github.io/legal/ which points back to /about/ - and > so I can't find the actual STIX license to verify this. > > Add it as a file like licenses/STIX.LICENSE.txt and refer to that from > the top level LICENSE and the file headers. (don't remove the old > file headers, just augment) > > > My +1 vote assumes this STIX license is a BSD-3-clause or 2-Clause, if > it is a BSD-4 clause it is NOT open source or compatible and my vote > would be -1. > > > For the hashes I would have preferred the style: > > apache-metron-0.3.0-rc1-incubating.tar.gz.sha1 containing: > 080a54dd02cfe9fa91cd92305726443302ef250e > apache-metron-0.3.0-rc1-incubating.tar.gz > > apache-metron-0.3.0-rc1-incubating.tar.gz.md5 containing: > 1cc8ecfac074d5667845b835e28f6403 apache-metron-0.3.0-rc1- > incubating.tar.gz > > ..or Maven-compatible without the spaces, filename or newline (no > spacing within the hash value) > > > (You may fix the hashes for this RC before you svn mv on dist) > > > > Below details about test failures only: > > > > The unit tests of metron-analytics/metron-maas-service crashes my X > server on Ubuntu 16.04 with Nvidia drivers..! Not sure why it would > touch X? > > It happens right after it says once "Found endpoint > biggieubuntu:someport" (my hostname). -- sorry it crashed a bit too > fast to check the port number! > > mvn clean install -DskipTests works though, so I won't fail this > particular vote. > > > I had a similar problem with mvn clean install within > > docker run -it maven:3-jdk-8 bash > > (which take a while in metron-maas-service) - that does a lot of > echo-endpoint things, but then fails with > > Found endpoints: dummy:1.0 @ http://c6ced9e36c5e:1500 serving: > apply=echo > Cleaning up... > Killing 1413 from 1413 ?00:00:00 dummy_rest.sh > 2016-11-23 17:33:23,070 ERROR [Thread[Thread-615,5,main]] > delegation.AbstractDelegationTokenSecretManager > (AbstractDelegationTokenSecretManager.java:run(659)) - > ExpiredTokenRemover received java.lang.InterruptedException: sleep > interrupted > 2016-11-23 17:33:23,183 ERROR [Thread[Thread-595,5,main]] > delegation.AbstractDelegationTokenSecretManager > (AbstractDelegationTokenSecretManager.java:run(659)) - > ExpiredTokenRemover received java.lang.InterruptedException: sleep > interrupted > 2016-11-23 17:33:23,193 ERROR [Thread[Thread-591,5,main]] > delegation.AbstractDelegationTokenSecretManager > (AbstractDelegationTokenSecretManager.java:run(659)) - > ExpiredTokenRemover received java.lang.InterruptedException: sleep > interrupted > 2016-11-23 17:33:38,159 ERROR [Curator-TreeCache-1] > curator.ConnectionState (ConnectionState.java:checkTimeouts(200)) - &
Re: [VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1
Hi all, Thanks for pointing out the branding issues. The website is updated to refer to the apache release page. There is also a JIRA <https://issues.apache.org/jira/browse/METRON-591> (with accompanying PR <https://github.com/apache/incubator-metron/pull/373> on github) to correct the branding issue on the website. I will see to it that the twitter page gets the appropriate parenthetical as well. Best, Casey On Thu, Nov 24, 2016 at 2:47 PM, John D. Ament wrote: > That's an issue. Want to let them know directly that their website needs > fixing? > > On Nov 24, 2016 1:00 PM, "Justin Mclean" wrote: > > > Hi, > > > > > RE Justin - that's a potential issue, but is also how github works. > > > > It may be how GitHub works but it is IMO against release policy > especially > > as on their site they link to GitHub and not the Apache release area. > > > > Thanks, > > Justin > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
[VOTE] Releasing Apache Metron (incubating) 0.3.0-RC1
This is a call to vote on releasing Apache Metron 0.3.0-RC1 incubating Full list of changes in this release: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 0-RC1-incubating/CHANGES The tag/commit to be voted upon is apache-metron-0.3.0-rc1-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=shortlog;h=refs/tags/apache-metron-0.3.0-rc1-incubating The source archive being voted upon can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 0-RC1-incubating/apache-metron-0.3.0-rc1-incubating.tar.gz Other release files, signatures and digests can be found here: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3. 0-RC1-incubating/ The release artifacts are signed with the following key: https://git-wip-us.apache.org/repos/asf?p=incubator-metron. git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/ apache-metron-0.3.0-rc1-incubating Please vote on releasing this package as Apache Metron 0.3.0-RC1 incubating When voting, please list the actions taken to verify the release. Recommended build validation and verification instructions are posted here: https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds This vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Metron 0.3.0-RC1 incubating [ ] 0 No opinion [ ] -1 Do not release this package because...
Re: [VOTE] Releasing Apache Metron 0.2.1BETA-RC2
Hey Josh, Thanks for looking so carefully again. Regarding the metron-common jar, could you be more specific how it's not correct? We placed a licenses file[1] in the META-INF directory for all of the jars which bundle components that have blurbs mentioning the permissive licenses. Is there something that we missed? 1. https://github.com/apache/incubator-metron/blob/master/metron-platform/metron-common/src/main/resources/META-INF/LICENSE is the one for metron-common On Thu, Oct 6, 2016 at 12:32 AM, Josh Elser wrote: > +1 (binding) > > * xsums/sigs OK (I think this is the second release, I think both from > Metron, where firefox butchers the SHA xsum -- I have no idea why though. > wget is fine) > * L&N are OK. Some extra cruft in LICENSE file, but the main content is > there. > * Can build from source > * Found no binaries in source-release > * DISCLAIMER is present > * KEYS is appropriate > > Other observations: > > * Kudos to Justin on catching StixExtractorTest.java > * Looks like the version in the pom is 0.2.1BETA, but I would have > expected to see 0.2.1BETA-incubating. > * Nit: contents of the source-release artifact could also be named > similarly. It's "incubator-metron-Metron_0.2.1BETA_rc2", I would expect > to see something like "apache-metron-0.2.1BETA-incubating". > * I picked out one JAR generated by the source release and inspected it > for proper L&N > (metron-platform/metron-common/target/metron-common-0.2.1BETA.jar) > and it does not appear to be correct to me. It would be good to have this > on your radar to verify across the board -- make sure that L&N inside the > artifacts your source-release creates (shaded JARs) is properly licensed > just like the source-release is. > * What's going on with the Metron Ambari Management Pack? It has a > different version than the rest of the code (Metron Ambari Management Pack > 1.0.0.0-SNAPSHOT). Is this intentional? > > - Josh > > > James Sirota wrote: > >> This is a call to vote on releasing Apache Metron 0.2.1BETA-RC2 incubating >> >> Full list of changes in this release: >> >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 1BETA-RC2-incubating/CHANGES >> >> The tag/commit to be voted upon is Metron_0.2.1BETA_rc2: >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.g >> it;a=commit;h=3e278cdc2c60d6d193d53157512c68b2a3ed58de >> >> The source archive being voted upon can be found here: >> >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 1BETA-RC2-incubating/apache-metron-0.2.1BETA-RC2-incubating.tar.gz >> >> Other release files, signatures and digests can be found here: >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 1BETA-RC2-incubating/ >> >> The release artifacts are signed with the following key: >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.g >> it;a=blob;f=KEYS;h=c11bcb9b7385b4d155501aa097afd890f1070a18; >> hb=3e278cdc2c60d6d193d53157512c68b2a3ed58de >> >> >> Please vote on releasing this package as Apache Metron 0.2.1BETA-RC2 >> incubating >> >> When voting, please list the actions taken to verify the release. >> Recommended build validation and verification instructions are posted >> here: >> https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds >> >> This vote will be open for at least 72 hours. >> >> [ ] +1 Release this package as Apache Metron 0.2.0BETA-RC2 incubating >> [ ] 0 No opinion >> [ ] -1 Do not release this package because... >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Releasing Apache Metron 0.2.0BETA-RC3
Josh, You are of course correct on all points. - We neglected to be careful about the implications of binary bundling and transitive dependencies (JIRA <https://issues.apache.org/jira/browse/METRON-374>). - It's a good idea to use ephemeral ports on our integration test components (JIRA <https://issues.apache.org/jira/browse/METRON-375>). - We should correct the issues with the webpage (JIRA <https://issues.apache.org/jira/browse/METRON-376>) Regarding Findbugs, if you open up the pom <http://central.maven.org/maven2/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.pom> from com.google.code.findbugs:jsr305-1.3.9 the ASLv2 is referenced. That being said, it's pretty clear that findbugs itself is lgpl, so I am also confused. Regardless, a more careful inspection and handling of our transitive dependencies is obviously called for. Thanks for the careful attention. :) Casey On Wed, Aug 17, 2016 at 1:27 AM, Josh Elser wrote: > +1 with reservations (binding) > > * DISCLAIMER present > * LICENSE/NOTICE seem reasonable > * xsums/sigs OK > * Can build from source > * Unit tests pass (after I stopped my local hbase instance, maybe you > could use random ports from the ephemeral range for your test services > instead of the default service ports) > * Integration tests didn't (I stopped after a failure in > BulkLoadMapperIntegrationTest) > * Tag is deployed and matches VOTE > * Overly aggressive RAT exclusions, but it passes and seems ok. Would > strongly recommend you prune this list in the future to make sure you don't > start shipping files which do not have a license header. You presently have > many exclusions for files which don't even exist in the codebase. > > Reservations: > > It is important to make sure that not only is the source-release artifact > properly licensed, but the resulting artifacts that source-release creates > are also properly licensed (in other words: the jars your build creates). > > Your shaded jars are not correctly licensed. For example, you include > org.abego.treelayout:org.abego.treelayout.core:jar:1.0.1 in > metron-common-0.2.0BETA.jar which is 3-clause BSD licensed, yet the > contained META-INF/LICENSE file has no mention of this. I also see a number > of CDDL licensed jars being included. > > The most worrisome artifact I see included is > com.google.code.findbugs:jsr305-1.3.9 in multiple artifacts > (metron-pcap-backend-0.2.0BETA.jar for one). This artifact befuddles me > because it is completely unclear whether it is GPL'ed or ASLv2 (last I > checked, documentation was not clear at all). Ironically, you also have > com.github.stephenc.findbugs:findbugs-annotations:jar:1.3.9-1 included > which is a clearly ASLv2 licensed implementation of the same spec (we won't > get into me asking "why" both are included *winks*). > > I don't think you need to fix these for this release, but you should make > an effort to do this before your next release. Yes, it sucks. Yes, you're > not the only one who has done it/will do it again. > > Branding: > > Took a look at your website too. > > * Your required ASF navigation links are not present > http://www.apache.org/foundation/marks/pmcs.html#navigation > * Incubator disclaimer and logo are present (yay) > * Noticed "Ambari" and not "Apache Ambari" on > http://metron.incubator.apache.org/documentation/. Would be good to make > sure you're using proper names for ASF projects. > > > > James Sirota wrote: > >> This release is exactly the same as RC2, but the Mozilla licensed file >> was removed so it doesn’t cause problems for us on the incubator general >> boards. We no longer use it so we just removed it. >> >> This is a call to vote on releasing Apache Metron 0.2.0BETA-RC3 incubating >> >> Full list of changes in this release: >> >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 0BETA-RC3-incubating/CHANGES >> >> The tag/commit to be voted upon is Metron_0.2.0BETA_rc3: >> >> <https://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> git;a=commit;h=75642001803396e8884385b0fc297a2312ead3eb>http >> s://git-wip-us.apache.org/repos/asf?p=incubator-metron. >> git;a=commit;h=75642001803396e8884385b0fc297a2312ead3eb >> >> The source archive being voted upon can be found here: >> >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 0BETA-RC3-incubating/apache-metron-0.2.0BETA-RC3-incubating.tar.gz >> >> Other release files, signatures and digests can be found here: >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.2. >> 0
Re: [VOTE] Releasing Apache Metron 0.2.0BETA-RC2
Ok, fair points. The discussion was within the project's mailing list here <https://mail-archives.apache.org/mod_mbox/incubator-metron-dev/201603.mbox/%3CCAPpQHK1+n9y3VJNHnR2rHpK4fyqQm3p=do3m6LuWf+0Z=4c...@mail.gmail.com%3E> rather than a discussion with legal. As such, we're going to do the work to remove that reference data and cut a new release candidate. Thanks for the attention again. :) Best, Casey On Mon, Jul 11, 2016 at 10:11 AM, Justin Mclean wrote: > Hi, > > > < > https://github.com/STIXProject/stixproject.github.io/blob/master/LICENSE>. > > If you think it's clearer, we can pull it into its own file and mention > it > > in the LICENSE for next release > > Sounds fine to me. > > > Regarding the effective_tld_names.dat, we had this discussion last > release > > and believe that they are reference data and should be considered > > acceptable. > > The nothing that I can see in the legal answered questions to say that > Category B “reference data” in text form is acceptable. > > Was this discussed on legal discuss? Is there a JIRA anywhere saying it’s > OK to make a source release containing those files? > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Releasing Apache Metron 0.2.0BETA-RC2
Thanks for the careful attention, Justin. Regarding the sample data for the StixExtractorTest.java, that came from here <https://github.com/STIXProject/stixproject.github.io/blob/master/getting-started/sample-walkthrough/IP_Watchlist-1.2.xml> and I considered it to be 3-clause BSD licensed due to the underlying project license here <https://github.com/STIXProject/stixproject.github.io/blob/master/LICENSE>. If you think it's clearer, we can pull it into its own file and mention it in the LICENSE for next release (JIRA here <https://issues.apache.org/jira/browse/METRON-297>). Regarding the effective_tld_names.dat, we had this discussion last release and believe that they are reference data and should be considered acceptable. We did note them in the LICENSE here <https://github.com/apache/incubator-metron/blob/master/LICENSE#L205>. The rationale around why we think they should be acceptable as per category B is as follows: - It's reference data, so not source code, so I feel that the category B wording was trying to make the distinction between source code and non-src code (i.e. "binary/object" in their language) - It's not source code, so paragraph 3 shouldn't apply, but even so, it has not changed since the last release - It's currently only supported for a legacy enrichment adapter, but will be removed next release as we found a better way of doing things. Thoughts? Best, Casey On Fri, Jul 8, 2016 at 10:45 PM, Justin Mclean wrote: > Hi, > > -1 (binding) until MPL licensed source issue resolved. > > I checked: > - name contains incubating > - signatures and hashes good > - DISCLAIMER exists > - LICENSE is OK, but look to be missing one permissive license? and > assuming its ok it would be best if the MPL was in another file. > - NOTICE is OK (but perhaps requires a notice from MPL?) > - All ASF source file have apache header > - No unexpected binary files > - Can compile from source > > For the license I think this file [1] may incorrectly have an apache > header. I’m also unsure of it’s license, but it’s likely to be permissive > [2] and needs to be mentioned in LICENSE. Can you fix this in the next > release please. > > There is a more serious issue in that the source includes MPL licensed > files.[4][5][6] This is a category B license [3] and as such files under > these terms can only included in binary form, but they plain text. They are > not small (10,000 lines) and given they contain list of domain name it > seems likely they they would change so I don’t think the last paragraph in > [3] applies either. It would also be a good idea to list where they come > from. > > Thanks, > Justin > > 1. > ./metron-platform/metron-data-management/src/test/java/org/apache/metron/dataloads/extractor/stix/StixExtractorTest.java > 2. http://stixproject.github.io/legal/ > 3. http://www.apache.org/legal/resolved.html#category-b > 4. > ./metron-platform/metron-common/src/test/resources/effective_tld_names.dat > 5. > ./metron-platform/metron-enrichment/src/main/resources/effective_tld_names.dat > 6. > ./metron-platform/metron-parsers/src/test/resources/effective_tld_names.dat > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] release of Metron_0.1BETA_rc7
Sorry, wrong quote: For small amounts of source that is directly consumed by the ASF product at > runtime in source form, and for which that source is unmodified and > unlikely to be changed anyway (say, by virtue of being specified by a > standard), inclusion of appropriately labeled source is also permitted. An > example of this is the web-facesconfig_1_0.dtd, whose inclusion is mandated > by the JSR 127: JavaServer Faces specification. > On Thu, Apr 7, 2016 at 2:58 PM, Casey Stella wrote: > Hey Daniel, > > Thanks for looking at it. Yes, that reference file is licensed under MPL > and as per the instructions at > http://www.apache.org/legal/resolved.html#category-b: > >> By attaching an appropriate and prominent label to the distribution, and >> requiring an explicit action by the user to get the reciprocally-licensed >> source, users are less likely to be unaware of restrictions significantly >> different from those of the Apache License. > > > We added what we considered appropriate language to the LICENSE. See > https://github.com/apache/incubator-metron/blob/Metron_0.1BETA_rc7/LICENSE#L306 > > If we didn't do that right, let us know and we'll change it PDQ. > > Thanks, > > Casey > > On Thu, Apr 7, 2016 at 2:54 PM, Daniel Gruno wrote: > >> I ran it through my usual compliance check, which yielded: >> >> Non-compliant license (Mozilla Public License/2.0) found in >> >> incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat >> >> Non-compliant license (Mozilla Public License/2.0) found in >> >> incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat >> >> Non-compliant license (Mozilla Public License/2.0) found in >> >> incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat >> >> This seems to be a -1 to me, but I'm open to being told otherwise :) >> >> With regards, >> Daniel. >> >> >> On 04/07/2016 08:49 PM, James Sirota wrote: >> > This is a call to vote on releasing Apache Metron 0.1BETA-RC7 >> > >> > Full list of changes in this release: >> > >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/CHANGES >> > >> > The tag/commit to be voted upon is Metron_0.1BETA_rc7: >> > >> > >> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=commit;h=ad3866bdf4b6233950e7803c3c3141f0f859e994 >> > >> > The source archive being voted upon can be found here: >> > >> > >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/apache-metron-0.1BETA-RC7-incubating.tar.gz >> > >> > Other release files, signatures and digests can be found here: >> > >> > >> https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/ >> > >> > The release artifacts are signed with the following key: >> > >> > >> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=blob_plain;f=KEYS;hb=dc59e37e402bd868aeac7ab42a0cc9c51ccae3c2 >> > >> > The Nexus staging repository for this release will be created after >> this vote has been passed. >> > >> > Please vote on releasing this package as Apache Metron 0.1BETA-RC7. >> > >> > Reference to the Metron PPMC vote can be found here: >> > >> http://mail-archives.apache.org/mod_mbox/incubator-metron-dev/201604.mbox/%3C0DFDA611-5C6E-43FB-A64E-291DD2B02413%40hortonworks.com%3E >> > >> > When voting, please list the actions taken to verify the release. >> > >> > Recommended build validation and verification instructions are posted >> here: >> > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds >> > >> > This vote will be open for at least 72 hours. >> > [ ] +1 Release this package as Apache Metron 0.1BETA-RC7 >> > [ ] 0 No opinion >> > [ ] -1 Do not release this package because... >> > >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] release of Metron_0.1BETA_rc7
Hey Daniel, Thanks for looking at it. Yes, that reference file is licensed under MPL and as per the instructions at http://www.apache.org/legal/resolved.html#category-b: > By attaching an appropriate and prominent label to the distribution, and > requiring an explicit action by the user to get the reciprocally-licensed > source, users are less likely to be unaware of restrictions significantly > different from those of the Apache License. We added what we considered appropriate language to the LICENSE. See https://github.com/apache/incubator-metron/blob/Metron_0.1BETA_rc7/LICENSE#L306 If we didn't do that right, let us know and we'll change it PDQ. Thanks, Casey On Thu, Apr 7, 2016 at 2:54 PM, Daniel Gruno wrote: > I ran it through my usual compliance check, which yielded: > > Non-compliant license (Mozilla Public License/2.0) found in > > incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-Common/src/test/resources/effective_tld_names.dat > > Non-compliant license (Mozilla Public License/2.0) found in > > incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-Topologies/src/main/resources/effective_tld_names.dat > > Non-compliant license (Mozilla Public License/2.0) found in > > incubator-metron-Metron_0.1BETA_rc7/metron-streaming/Metron-MessageParsers/src/test/resources/effective_tld_names.dat > > This seems to be a -1 to me, but I'm open to being told otherwise :) > > With regards, > Daniel. > > > On 04/07/2016 08:49 PM, James Sirota wrote: > > This is a call to vote on releasing Apache Metron 0.1BETA-RC7 > > > > Full list of changes in this release: > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/CHANGES > > > > The tag/commit to be voted upon is Metron_0.1BETA_rc7: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=commit;h=ad3866bdf4b6233950e7803c3c3141f0f859e994 > > > > The source archive being voted upon can be found here: > > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/apache-metron-0.1BETA-RC7-incubating.tar.gz > > > > Other release files, signatures and digests can be found here: > > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/ > > > > The release artifacts are signed with the following key: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=blob_plain;f=KEYS;hb=dc59e37e402bd868aeac7ab42a0cc9c51ccae3c2 > > > > The Nexus staging repository for this release will be created after this > vote has been passed. > > > > Please vote on releasing this package as Apache Metron 0.1BETA-RC7. > > > > Reference to the Metron PPMC vote can be found here: > > > http://mail-archives.apache.org/mod_mbox/incubator-metron-dev/201604.mbox/%3C0DFDA611-5C6E-43FB-A64E-291DD2B02413%40hortonworks.com%3E > > > > When voting, please list the actions taken to verify the release. > > > > Recommended build validation and verification instructions are posted > here: > > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds > > > > This vote will be open for at least 72 hours. > > [ ] +1 Release this package as Apache Metron 0.1BETA-RC7 > > [ ] 0 No opinion > > [ ] -1 Do not release this package because... > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] releasing Apache Metron 0.1BETA-RC7
Regarding what changed between RC6 and RC7, it was just a PR to correct the snort URL issue, from teh changelog: METRON-92: Snort has moved their release artifacts, breaking deployment (dlyle65535 via cestella) closes apache/incubator-metron#65 On Tue, Apr 5, 2016 at 4:54 PM, P. Taylor Goetz wrote: > James, > > I’m a bit confused. There’ve been a number of votes on the dev@ list, but > only one that was closed with a RESULT (rc5). I voted on rc6, but it seems > that rc was abandoned without ever being CANCELED. The labels/links in the > message below don’t match (RC6 != RC7) — which I imagine is just a > copy/paste error, but it makes it confusing trying to figure out what > exactly we’re reviewing. The vote on RC7 also hasn’t run for 72 hours yet. > > Also, when starting an IPMC release vote, please provide a link to the > RESULT email. > > Please CANCEL this vote on general@, and we can sort things out on > dev@metron. > > -Taylor > > > On Apr 5, 2016, at 4:15 AM, James Sirota > wrote: > > > > This is a call to vote on releasing Apache Metron 0.1BETA-RC7 > > > > Full list of changes in this release: > > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/CHANGES > < > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC6-incubating/CHANGES > > > > > > The tag/commit to be voted upon is Metron_0.1BETA_rc7: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=commit;h=ad3866bdf4b6233950e7803c3c3141f0f859e994 > > > > The source archive being voted upon can be found here: > > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/apache-metron-0.1BETA-RC7-incubating.tar.gz > < > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC6-incubating/apache-metron-0.1BETA-RC6-incubating.tar.gz > > > > > > Other release files, signatures and digests can be found here: > > > > > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC7-incubating/ > < > https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC6-incubating/ > > > > > > The release artifacts are signed with the following key: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-metron.git;a=blob_plain;f=KEYS;hb=dc59e37e402bd868aeac7ab42a0cc9c51ccae3c2 > > > > The Nexus staging repository for this release will be created after this > vote has been passed. > > > > > > Please vote on releasing this package as Apache Metron 0.1BETA-RC7. > > > > When voting, please list the actions taken to verify the release. > > Recommended build validation and verification instructions are posted > here: > > https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds > > > > This vote will be open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Metron 0.1BETA-RC7 > > [ ] 0 No opinion > > [ ] -1 Do not release this package because... > >
