Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! It's great to have Chimera to be part of Apache Commons.
>>[ Emmanuel Bourg] Define the scope of the project? Do we go after Bouncy >>Castle and aim for an equivalent feature set? Agree to make a clear scope of the project. The original Chimera scope is not go after a Bouncy Castle style of library. It targets the gap between the application and the under cipher implementations. For example, applications uses a lot of InputStream/OutputStream or Channel concepts to read / write a stream of data. Application can share these Crypto streams/channel implementations abstracting various input and output types. Chimera also targets to very important performance optimizations on AES which is used worldwide. I suggest this module to be still lightweight and clear in involving, which is the same ideology of Apache Commons. >> [Uma] Here I would like to introduce Haifeng, who lead the efforts in >> Chimera github project. Thanks Uma for introduction. >> [Uma] Me and Haifeng had some discussion yesterday for the list to get >> commit prevs. May be he could probably get list. Then I think Commons PMC >> can make a decision on it. Chimera has 5 long standing contributors on github. We can also invite those who contributed the HDFS encryption feature (HDFS-6134 and HADOOP-10150) to continue participate the involution of this project if they want. Thanks, Haifeng -----Original Message----- From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com] Sent: Sunday, February 21, 2016 3:07 AM To: Commons Developers List <dev@commons.apache.org> Subject: Re: [crypto][chimera] Next steps Hi Benedikt, Thank you for the Next steps discussion. I thought of pinging you on this :-) Here I would like to introduce Haifeng, who lead the efforts in Chimera github project. I think Apache Commons Crypto looks good and self descriptive IMO. I am +1 Me and Haifeng had some discussion yesterday for the list to get commit prevs. May be he could probably get list. Then I think Commons PMC can make a decision on it. >move code to an Apache repo (probably git?!) +1 for git >- setup maven build If this point is just about maven build alone, then we should set up Jenkins CI build boat as well right, may be we can add this point? Regards, Uma On 2/20/16, 8:29 AM, "Gary Gregory" <garydgreg...@gmail.com> wrote: >Who are the committers comming along for this component? > >Do we have enough of them? > >I like Apache Commons Crypto. > >Gary >On Feb 20, 2016 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
