Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
From: "Chen, Haifeng" <haifeng.chen@intel.com>
To: Commons Developers List <dev@commons.apache.org>
Subject: RE: [crypto][chimera] Next steps
Thread-Topic: [crypto][chimera] Next steps
Thread-Index: AQHRa9ACQA5pbKN60EKP+imQynGD8p80mgaAgAAsAACAAotnMA==
Date: Mon, 22 Feb 2016 02:28:39 +0000
Message-ID: 
 <3E657120E422654A9EB626F537B8AA91141020BC@shsmsx102.ccr.corp.intel.com>
References: 
 <CAB917RKp_Nk=rVVSG0VAkHuoxeN8aZ0iJegY29eVCHAnH_rhHw@mail.gmail.com>
 <CACZkXPxC6OSyt1BAwdqEJ1SqoSM_u7AGJpJzWypwckQx4euBzg@mail.gmail.com>
 <D2EDF612.C3AE%uma.gangumalla@intel.com>
In-Reply-To: <D2EDF612.C3AE%uma.gangumalla@intel.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! It's =
great to have Chimera to be part of Apache Commons.=20

>>[ 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 n=
ot go after a Bouncy Castle style of library. It targets the gap between th=
e application and the under cipher implementations. For example, applicatio=
ns uses a lot of InputStream/OutputStream or Channel concepts to read / wri=
te a stream of data. Application can share these Crypto streams/channel imp=
lementations abstracting various input and output types. Chimera also targe=
ts to very important performance optimizations on AES which is used worldwi=
de. I suggest this module to be still lightweight and clear in involving, w=
hich is the same ideology of Apache Commons.

>> [Uma] Here I would like to introduce Haifeng, who lead the efforts in Ch=
imera github project.
Thanks Uma for introduction.

>> [Uma] Me and Haifeng had some discussion yesterday for the list to get c=
ommit prevs. May be he could probably get list. Then I think Commons PMC ca=
n make a decision on it.
Chimera has 5 long standing contributors on github. We can also invite thos=
e 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.gangumalla@intel.com]=20
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
:-)
 =20
 Here I would like to introduce Haifeng, who lead the efforts in Chimera gi=
thub project.=20
=20
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 pre=
vs. 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 Jenkin=
s CI build boat as well right, may be we can add this point?

Regards,
Uma=20

On 2/20/16, 8:29 AM, "Gary Gregory" <garydgregory@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" <britter@apache.org> wrote:
>
>> Hi,
>>
>> I'd like to discuss the next steps for moving the Chimera component=20
>>to  Apache Commons. So far, none of the other PMC members has=20
>>expressed his or  her thoughts about this. If nobody brings up=20
>>objections about moving the  component to Apache Commons, I'm assuming=20
>>lazy consensus about this.
>>
>> So the next steps would be:
>> - decide on a name for the new component (my proposal was Apache=20
>> 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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org