+1, need to take this as a way to reduce cost of submitting code by new contributors, along with the fact that this is a must do.
Thks Amol E:[email protected] | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com *Join us at Apex Big Data World Mt View <http://www.apexbigdata.com/mountain-view.html>, April 4, 2017!* [image: http://www.apexbigdata.com/san-jose-register.html] <http://www.apexbigdata.com/san-jose-register.html> On Wed, Mar 29, 2017 at 10:27 AM, Pramod Immaneni <[email protected]> wrote: > It will be good to mention in the guidelines, known compatible licenses and > incompatible ones. Additional guidelines on what are the general > characteristics of a compatible license e.g., free to use, no restriction > of making code open etc.. because there may be depdencies that don't use > well known licenses but still fit the bill of a compatible license. > > Thanks > > On Wed, Mar 29, 2017 at 9:43 AM, Thomas Weise <[email protected]> wrote: > > > +1 in general more attention to licensing is needed and we may need to > > update the contributor guidelines also. > > > > Can you create a JIRA with fix version set to 3.8.0 ? > > > > > > On Wed, Mar 29, 2017 at 9:34 AM, Vlad Rozov <[email protected]> > > wrote: > > > > > There are few samples and the benchmark application in Malhar that > depend > > > on libraries licensed under Category X. All such dependencies need to > be > > > either optional, be replaced with libraries that are compatible with > > Apache > > > license or be removed. Any newly introduced dependency should be either > > > compatible with the Apache license or be optional. > > > > > > Thank you, > > > > > > Vlad > > > > > > > > >
