On 23 February 2016 at 07:34, Benedikt Ritter <brit...@apache.org> wrote: > I'm confused. None of the other PMC members has expressed whether he or she > want's the see Chimera/crypto joining Apache Commons, yet we're already > discussing how JNI bindings should be handled. > > I'd like to see: > 1) a clear statement whether Chimera/crypto should become part of Apache > Commons. Do we need a vote for that?
Yes, of course. However that decision clearly depends on at least some of the design aspects of the code. If it were written entirely in C or Fortran, it would not be a suitable candidate. > 2) Discuss a plan on how to do that (I've described a possible plan [1]) > 3) After that is clear: discuss design details regarding the component. Some design details impact on the decision. Indeed even for pure Java code the code quality has a bearing on whether Commons would/could want to take it. Would we want a large code base with no unit-tests, no build mechanism, and no comments? > Thanks! :-) > Benedikt > > [1] http://markmail.org/message/74j4el6bpfpt4evs > > 2016-02-23 3:03 GMT+01:00 Xu, Cheng A <cheng.a...@intel.com>: > >> At this point, it has just Java interfaces only. >> >> -----Original Message----- >> From: Colin P. McCabe [mailto:cmcc...@apache.org] >> Sent: Tuesday, February 23, 2016 1:29 AM >> To: Hadoop Common >> Cc: Commons Developers List >> Subject: Re: [crypto][chimera] Next steps >> >> I would highly recommend shading this library when it is used in >> Hadoop and/or Spark, to prevent version skew problems between Hadoop >> and Spark like we have had in the past. >> >> What is the strategy for handling JNI components? I think at a >> minimum, we should include the version number in the native library >> name to avoid problems when deploying multiple versions of Chimera. >> This is something that has been problematic in Hadoop with >> libhadoop.so. >> >> Is this library going to have Scala interfaces as well as Java ones, >> or just Java? >> >> cheers, >> Colin >> >> On Sat, Feb 20, 2016 at 3:15 AM, Benedikt Ritter <brit...@apache.org> >> wrote: >> > Hi, >> > >> > I'd like to discuss the next steps for moving the Chimera component to >> > Apache Commons. So far, none of the other PMC members has expressed his >> or >> > her thoughts about this. If nobody brings up objections about moving the >> > component to Apache Commons, I'm assuming lazy consensus about this. >> > >> > So the next steps would be: >> > - decide on a name for the new component (my proposal was Apache Commons >> > Crypto) >> > - move code to an Apache repo (probably git?!) >> > - request a Jira project >> > - setup maven build >> > - setup project website >> > - work on an initial release under Apache Commons coordinates >> > >> > Anything missing? >> > >> > Regards, >> > Benedikt >> > >> > -- >> > http://home.apache.org/~britter/ >> > http://twitter.com/BenediktRitter >> > http://github.com/britter >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > http://home.apache.org/~britter/ > http://twitter.com/BenediktRitter > http://github.com/britter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
