Re: [crypto] On Java 6, really?

On 6/14/16, 1:23 AM, "Gary Gregory" <garydgreg...@gmail.com> wrote: >On Tue, Jun 14, 2016 at 1:21 AM, Gangumalla, Uma ><uma.ganguma...@intel.com> >wrote: > >> Then next release(after 1.0.0) must be a major release you mean? >> If there are no pot

Re: [crypto] On Java 6, really?

Then next release(after 1.0.0) must be a major release you mean? If there are no potential users looking for JDK 1.6, dropping now should be good idea IMO. I also remembered that we wanted to mark 1.0.0 release as Alpha right? (just a question) Regards, Uma On 6/14/16, 12:27 AM, "Sun, Dapeng"

Re: [crypto] The standard indentation is 4 spaces per indent

>This is Commons, AND this is brand new code, so in my mind there is no "original" formatting style to respect. 4 spaces per indent like the rest of the project please. Remember that Commons is a SINGLE project. Hopefully we won't have to argue about too much about this... [Uma] Thanks Gary for

Re: [CRYPTO] Switch from JNI to JNA

This is awesome. Thanks Haifeng for driving towards 1st release. Regards, Uma On 4/26/16, 6:27 PM, "Chen, Haifeng" wrote: >Thanks folks. >An alpha release is a good suggestion! I am checking with the Spark guys >as to the Spark 2.0 code freeze timeline and check whether

Re: [crypto] The standard indentation is 4 spaces per indent

I am ok with a JIRA and type could be task for the reasons Sebb mentioned below. But I prefer to keep 2 spaces if others also ok who is going to involve in development. I assume most of Hadoop devs would have set their indentation 2 already in their IDEs. So, here also most of them would involve

Re: [CRYPTO] Switch from JNI to JNA

As we plan to have release sooner, marking release ALPHA tagged make sense IMO. Regards, Uma On 4/25/16, 7:02 PM, "sebb" wrote: >On 26 April 2016 at 02:56, Chen, Haifeng wrote: Sounds like a tough time schedule. It's only one week until May. >>

Re: [CRYPTO] Git repository requested

e- >> From: Benedikt Ritter [mailto:brit...@apache.org] >> Sent: Friday, April 15, 2016 3:48 PM >> To: Commons Developers List <dev@commons.apache.org> >> Subject: Re: [CRYPTO] Git repository requested >> >> I have added both of you to the commons-developers list.

Re: [CRYPTO] Git repository requested

up project website >>> - work on an initial release under Apache Commons coordinates >>> >>> >>> -Original Message- >>> From: Benedikt Ritter [mailto:brit...@apache.org] >>> Sent: Monday, April 11, 2016 12:30 AM >>> To: Commons Developers Lis

Re: [CRYPTO] Git repository requested

[1]. I've created the new repository request with the >"import initial code base"-option set to the chimera github repo. Infra >now >needs proof of the software grant by Intel. > >Uma, can you take care of this? > >Regards, >Benedikt > >[1] >https://issues.apa

Re: [CRYPTO] Git repository requested

Great. Thanks a lot, Benedikt for taking forward. :-) Regards, Uma On 4/9/16, 12:51 AM, "Benedikt Ritter" wrote: >Hi, > >I've just created a request for creating the crypto git repository [1]. >I'll keep you updated on the state of the request. > >Benedikt > >[1]

Re: [DISCUSS][CHIMERA] Name for the new component

Just collected all the proposed names here for tracking purpose at single place: Apache Commons Crypto Apache Commons Crypto Libs Apache Commons Crypto Extensions Apache Commons AES Apache Commons AES Libs Apache Commons AES Extensions Apache Commons Crypto Wrapper Apache Commons Crypto Helper

Re: [VOTE] Accept Chimera as new Apache Commons Component

>I am also worried about the JNI stuff, but I think a new group of developers would be good for this community. Thanks Oliver for your opinion. Yes, handful of members in this below community are really very good at JNI and Java. Also we would consider to explore on JNA stuff which was

Re: [VOTE] Accept Chimera as new Apache Commons Component

+1 (non-binding) +common-dev@hadoop On 3/21/16, 6:59 PM, "Gangumalla, Uma" <uma.ganguma...@intel.com> wrote: >+1 (non-binding) > > >Regards, >Uma > >On 3/21/16, 1:45 AM, "Benedikt Ritter" <brit...@apache.org> wrote: > >>Hi al

Re: [VOTE] Accept Chimera as new Apache Commons Component

+1 (non-binding) Regards, Uma On 3/21/16, 1:45 AM, "Benedikt Ritter" wrote: >Hi all, > >after long discussions I think we have gathered enough information to >decide whether we want to accept the Chimera project as a new Apache >Commons component. > >Proposed name: Apache

Re: [crypto][chimera] Next steps

eam in Apache Hadoop) Regards, Uma On 3/7/16, 5:20 PM, "Gangumalla, Uma" <uma.ganguma...@intel.com> wrote: >Dear all, Sorry for the delay. Working out on the proposal document, we >will get it posted here soon. > >Regards, >Uma > > >On 2/26/16, 1:26 PM,

Re: Request to add into Apache Commons Wiki contributors group

to check is it ok to create section in Apache Commons Wiki for ³New Component Proposal² section and from there to proposals page? Or we we track in commons site itself for the consistency? Please some one confirm this for me. Regards, Uma On 3/15/16, 2:00 PM, "Gangumalla, Uma" &l

Re: Request to add into Apache Commons Wiki contributors group

Hi Stefan, Thanks a lot. Regards, Uma On 3/15/16, 12:57 PM, "Stefan Bodewig" <bode...@apache.org> wrote: >Hi Uma > >On 2016-03-15, Gangumalla, Uma wrote: > >> I would like to post Apache Commons Crypto proposal in Apache Commons >> Wiki page. Fo

Request to add into Apache Commons Wiki contributors group

Hi, I would like to post Apache Commons Crypto proposal in Apache Commons Wiki page. For this could you please add me into Wiki contributors group? user: umagangumalla Regards, Uma - To unsubscribe, e-mail:

Re: [crypto][chimera] Next steps

gt;G > >On Fri, Feb 26, 2016 at 12:47 PM, Gangumalla, Uma ><uma.ganguma...@intel.com> >wrote: > >> >> Ok. Thanks Benedikt. We would get the proposal document ready soon. >> Also one question, shall we rename the package to org.apache.* in >>Chimera >>

Re: [crypto][chimera] Next steps

po and that you wanted to close the >>quote. >> >>G >> >>On Fri, Feb 26, 2016 at 12:47 PM, Gangumalla, Uma >><uma.ganguma...@intel.com> >>wrote: >> >>> >>> Ok. Thanks Benedikt. We would get the proposal document ready soon. >&g

Re: [crypto][chimera] Next steps

imera/Apache Crypto. >> Yes, current implementation will fallback to JCE Cipher if native is not >> available. >> >> [Uma] we would fix up IP issues if any sooner. If you see all the code >> file license header is with Apache License files. >> The current repo and pack

Re: [crypto][chimera] Next steps

Thanks all for the valuable feedbacks and discussions. Here are my replies for some of the questions.. [Mark wrote] It depends. I care less about the quality of the code than I do about the community that comes with it / forms around it. A strong community can fix code issues. Great code can't

Re: [crypto][chimera] Next steps

ry" <garydgreg...@gmail.com> wrote: >All files should follow the Commons Maven naming scheme to make it easy to >reach from Maven, Ivy and so on. > >This will be commons-crypto-1.0.jar for example. > >Gary > >On Mon, Feb 22, 2016 at 1:06 PM, Gangumalla, Uma ><

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. [uma]Ha. This avoids multiple jars versions issues. Agreed IMO. >I think at a minimum, we should include the version

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

Re: Chimera as new component in Apache Commons

, "Benedikt Ritter" <brit...@apache.org> wrote: >Hello Uma, > >welcome to the Apache Commons dev list. It's great to see that two >projects >get together to share code via Apache Commons. > >2016-02-16 22:36 GMT+01:00 Gangumalla, Uma <uma.ganguma...@intel.com>: &

Chimera as new component in Apache Commons

Hi Devs, Recently we worked with Spark community to implement the shuffle encryption. While implementing that, we realized some/most of the code in Apache Hadoop encryption code and this implementation code have to be duplicated. This leads to an idea to create separate reusable library,