You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ellison Anne Williams <ea...@gmail.com> on 2016/08/24 17:16:53 UTC
[VOTE] Apache Pirk 0.1.0-incubating Release
Hi All,
The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed; it is
a source-only release (no binary artifacts). We kindly request that the
IPMC now vote on the release.
The PPMC vote thread is located here:
https://lists.apache.org/thread.html/f9321c1ce45c4f696639ecac2eac6acdcfbff6a669281941c9c06742@%3Cdev.pirk.apache.org%3E
The artifacts can be downloaded here: https://repository.apache.org/content/
repositories/orgapachepirk-1002
The artifacts have been signed with key 1FD8849B found in the KEYS file:
https://dist.apache.org/repos/dist/dev/incubator/pirk/KEYS
All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'.
You can view the release notes here: https://issues.apache.
org/jira/secure/ReleaseNote.jspa?projectId=12320320&version=12338109
Please vote accordingly:
[ ] +1, accept as the official Apache Pirk 0.1.0-incubating release
[ ] -1, do not accept as the official Apache Pirk 0.1.0-incubating release
because...
The vote will run for at least 72 hours.
Thanks!
Ellison Anne
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Suneel Marthi <sm...@apache.org>.
Posting my vote from dev@ here
+1 binding
On Wed, Aug 24, 2016 at 1:16 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> Hi All,
>
> The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed; it
> is
> a source-only release (no binary artifacts). We kindly request that the
> IPMC now vote on the release.
>
> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/f9321c1ce45c4f696639ecac2eac6a
> cdcfbff6a669281941c9c06742@%3Cdev.pirk.apache.org%3E
>
> The artifacts can be downloaded here: https://repository.apache.org/
> content/
> repositories/orgapachepirk-1002
>
> The artifacts have been signed with key 1FD8849B found in the KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/pirk/KEYS
>
> All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'.
> You can view the release notes here: https://issues.apache.
> org/jira/secure/ReleaseNote.jspa?projectId=12320320&version=12338109
>
> Please vote accordingly:
>
> [ ] +1, accept as the official Apache Pirk 0.1.0-incubating release
> [ ] -1, do not accept as the official Apache Pirk 0.1.0-incubating release
> because...
>
> The vote will run for at least 72 hours.
>
> Thanks!
>
> Ellison Anne
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Thanks Justin. I have just updated the ASF Export Classification page
> to add product name "Apache Pirk" under the Apache Incubator project.
>
> We will co-ordinate the sending of the notice to US Govt., and updating
> the readme via Pirk's dev list.
Thanks for that.
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Tim Ellison <t....@gmail.com>.
On 25/08/16 00:48, Justin Mclean wrote:
> -1 binding, willing to change my vote if encryption code issue
> clarified.
>
>> The artifacts can be downloaded here:
>> https://repository.apache.org/content/
>> repositories/orgapachepirk-1002
>
> Please place the artefacts in the correct place [1] That that
> releases MUST be placed in the list area and that maven is considered
> a secondary channel.
>
> I checked: - name included incubating - signature and hashes good -
> DISCLAIMER exists - LICENSE and NOTICE good - No unexpected binary
> files in release - Can compile from source
>
> I see that the release looks to contains encryption source code [2]
> (Paillier) [5], if so has this process been followed? [3] I can't
> see Prik listed here [4].
Thanks Justin. I have just updated the ASF Export Classification page
to add product name "Apache Pirk" under the Apache Incubator project.
We will co-ordinate the sending of the notice to US Govt., and updating
the readme via Pirk's dev list.
> Just out of interest why the \u201cwideskies\u201d in the class path name?
s/class path name/package name/
Wideskies is the name of an algorithm implemented by Pirk. You can see
the details linked from Pirk's website here
http://pirk.incubator.apache.org/papers/
Regards,
Tim
> Thanks, Justin
>
> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/ 2.
> ./src/main/java/org/apache/pirk/encryption/ 3.
> http://www.apache.org/dev/crypto.html 4.
> http://www.apache.org/licenses/exports/ 5.
> https://en.wikipedia.org/wiki/Paillier_cryptosystem
>
>
> ---------------------------------------------------------------------
>
>
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Update ASF ECCN classification page (was: Re: [VOTE] Apache Pirk
0.1.0-incubating Release)
Posted by Tim Ellison <t....@gmail.com>.
I'm on it.
Regards,
Tim
On 25/08/16 03:33, Suneel Marthi wrote:
> On Wed, Aug 24, 2016 at 9:09 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Aug 24, 2016 at 8:26 PM, Ellison Anne Williams <
>> eawilliamspirk@gmail.com> wrote:
>>
>>> Yes, as per http://www.apache.org/dev/crypto.html --
>>>
>>> The code falls under ECCN 5D002, so we are good there.
>>>
>>> We need to:
>>>
>>> (1) Notify the USG via the sending the specified email
>>>
>>> (2) Add a README containing the crypto -- Do we have to go through the
>>> entire voting process again internally since we are adding a file to the
>>> source release?
>>>
>>
>> I am afraid we do have to rollback and push new set of artifacts. But
>> hopefully we don't have to wait for 72 hrs for all to Vote on a README
>> file.
>>
>> It may not have been needed if we had used https://dist.apache.org/
>> repos/dist/dev/incubator/pirk/ - it would then be an svn checkout and svn
>> commit.
>>
>>
>>>
>>> (3) Edit the export list to add Pirk here
>>> http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access
>>> to
>>> edit the page? I don't think that I do as it says that anyone with
>>> 'site-dev
>>> karma' can edit and, as far as I know, I don't have site-dev karma.
>>>
>>
>> I have access and karma to this, if u can tell me what to add - I can do
>> it now.
>>
>
> It turns out that I don't have karma to edit this file.
>
>>
>>
>>>
>>>
>>> On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
>>> wrote:
>>>
>>>> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
>>>> eawilliamspirk@gmail.com> wrote:
>>>>
>>>>> Got it - will take care of it tonight/in the morning and report back
>>> to
>>>>> general@incubator
>>>>>
>>>>> I'd better notify the USG of the crypto - lol :)
>>>>>
>>>>
>>>> That's the part that had me laughing, all of this source code came out
>>> of
>>>> USG and we are being told to check with USG again.
>>>>
>>>> At the very least we may need to add Pirk to the list of exports - (4),
>>> for
>>>> Justin to reverse his -1
>>>>
>>>>
>>>>> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
>>> suneel.marthi@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Fyi folks
>>>>>>
>>>>>>
>>>>>> ---------- Forwarded message ----------
>>>>>> From: Justin Mclean <ju...@classsoftware.com>
>>>>>> Date: Wed, Aug 24, 2016 at 7:48 PM
>>>>>> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
>>>>>> To: general@incubator.apache.org
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> -1 binding, willing to change my vote if encryption code issue
>>>> clarified.
>>>>>>
>>>>>>> The artifacts can be downloaded here:
>>> https://repository.apache.org/
>>>>>> content/
>>>>>>> repositories/orgapachepirk-1002
>>>>>>
>>>>>> Please place the artefacts in the correct place [1] That that
>>> releases
>>>>> MUST
>>>>>> be placed in the list area and that maven is considered a secondary
>>>>>> channel.
>>>>>>
>>>>>> I checked:
>>>>>> - name included incubating
>>>>>> - signature and hashes good
>>>>>> - DISCLAIMER exists
>>>>>> - LICENSE and NOTICE good
>>>>>> - No unexpected binary files in release
>>>>>> - Can compile from source
>>>>>>
>>>>>> I see that the release looks to contains encryption source code [2]
>>>>>> (Paillier) [5], if so has this process been followed? [3] I can't
>>> see
>>>>> Prik
>>>>>> listed here [4].
>>>>>>
>>>>>> Just out of interest why the \u201cwideskies\u201d in the class path name?
>>>>>>
>>>>>> Thanks,
>>>>>> Justin
>>>>>>
>>>>>> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
>>>>>> 2. ./src/main/java/org/apache/pirk/encryption/
>>>>>> 3. http://www.apache.org/dev/crypto.html
>>>>>> 4. http://www.apache.org/licenses/exports/
>>>>>> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------
>>> ---------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Suneel Marthi <su...@gmail.com>.
On Wed, Aug 24, 2016 at 9:09 PM, Suneel Marthi <su...@gmail.com>
wrote:
>
>
> On Wed, Aug 24, 2016 at 8:26 PM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
>
>> Yes, as per http://www.apache.org/dev/crypto.html --
>>
>> The code falls under ECCN 5D002, so we are good there.
>>
>> We need to:
>>
>> (1) Notify the USG via the sending the specified email
>>
>> (2) Add a README containing the crypto -- Do we have to go through the
>> entire voting process again internally since we are adding a file to the
>> source release?
>>
>
> I am afraid we do have to rollback and push new set of artifacts. But
> hopefully we don't have to wait for 72 hrs for all to Vote on a README
> file.
>
> It may not have been needed if we had used https://dist.apache.org/
> repos/dist/dev/incubator/pirk/ - it would then be an svn checkout and svn
> commit.
>
>
>>
>> (3) Edit the export list to add Pirk here
>> http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access
>> to
>> edit the page? I don't think that I do as it says that anyone with
>> 'site-dev
>> karma' can edit and, as far as I know, I don't have site-dev karma.
>>
>
> I have access and karma to this, if u can tell me what to add - I can do
> it now.
>
It turns out that I don't have karma to edit this file.
>
>
>>
>>
>> On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
>> wrote:
>>
>> > On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
>> > eawilliamspirk@gmail.com> wrote:
>> >
>> > > Got it - will take care of it tonight/in the morning and report back
>> to
>> > > general@incubator
>> > >
>> > > I'd better notify the USG of the crypto - lol :)
>> > >
>> >
>> > That's the part that had me laughing, all of this source code came out
>> of
>> > USG and we are being told to check with USG again.
>> >
>> > At the very least we may need to add Pirk to the list of exports - (4),
>> for
>> > Justin to reverse his -1
>> >
>> >
>> > > On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
>> suneel.marthi@gmail.com>
>> > > wrote:
>> > >
>> > > > Fyi folks
>> > > >
>> > > >
>> > > > ---------- Forwarded message ----------
>> > > > From: Justin Mclean <ju...@classsoftware.com>
>> > > > Date: Wed, Aug 24, 2016 at 7:48 PM
>> > > > Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
>> > > > To: general@incubator.apache.org
>> > > >
>> > > >
>> > > > Hi,
>> > > >
>> > > > -1 binding, willing to change my vote if encryption code issue
>> > clarified.
>> > > >
>> > > > > The artifacts can be downloaded here:
>> https://repository.apache.org/
>> > > > content/
>> > > > > repositories/orgapachepirk-1002
>> > > >
>> > > > Please place the artefacts in the correct place [1] That that
>> releases
>> > > MUST
>> > > > be placed in the list area and that maven is considered a secondary
>> > > > channel.
>> > > >
>> > > > I checked:
>> > > > - name included incubating
>> > > > - signature and hashes good
>> > > > - DISCLAIMER exists
>> > > > - LICENSE and NOTICE good
>> > > > - No unexpected binary files in release
>> > > > - Can compile from source
>> > > >
>> > > > I see that the release looks to contains encryption source code [2]
>> > > > (Paillier) [5], if so has this process been followed? [3] I can't
>> see
>> > > Prik
>> > > > listed here [4].
>> > > >
>> > > > Just out of interest why the “wideskies” in the class path name?
>> > > >
>> > > > Thanks,
>> > > > Justin
>> > > >
>> > > > 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
>> > > > 2. ./src/main/java/org/apache/pirk/encryption/
>> > > > 3. http://www.apache.org/dev/crypto.html
>> > > > 4. http://www.apache.org/licenses/exports/
>> > > > 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
>> > > >
>> > > >
>> > > > ------------------------------------------------------------
>> ---------
>> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > > > For additional commands, e-mail: general-help@incubator.apache.org
>> > > >
>> > >
>> >
>>
>
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Suneel Marthi <su...@gmail.com>.
On Wed, Aug 24, 2016 at 8:26 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> Yes, as per http://www.apache.org/dev/crypto.html --
>
> The code falls under ECCN 5D002, so we are good there.
>
> We need to:
>
> (1) Notify the USG via the sending the specified email
>
> (2) Add a README containing the crypto -- Do we have to go through the
> entire voting process again internally since we are adding a file to the
> source release?
>
I am afraid we do have to rollback and push new set of artifacts. But
hopefully we don't have to wait for 72 hrs for all to Vote on a README
file.
It may not have been needed if we had used https://dist.apache.org/repos/
dist/dev/incubator/pirk/ - it would then be an svn checkout and svn commit.
>
> (3) Edit the export list to add Pirk here
> http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access to
> edit the page? I don't think that I do as it says that anyone with
> 'site-dev
> karma' can edit and, as far as I know, I don't have site-dev karma.
>
I have access and karma to this, if u can tell me what to add - I can do it
now.
>
>
> On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
> > eawilliamspirk@gmail.com> wrote:
> >
> > > Got it - will take care of it tonight/in the morning and report back to
> > > general@incubator
> > >
> > > I'd better notify the USG of the crypto - lol :)
> > >
> >
> > That's the part that had me laughing, all of this source code came out of
> > USG and we are being told to check with USG again.
> >
> > At the very least we may need to add Pirk to the list of exports - (4),
> for
> > Justin to reverse his -1
> >
> >
> > > On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
> suneel.marthi@gmail.com>
> > > wrote:
> > >
> > > > Fyi folks
> > > >
> > > >
> > > > ---------- Forwarded message ----------
> > > > From: Justin Mclean <ju...@classsoftware.com>
> > > > Date: Wed, Aug 24, 2016 at 7:48 PM
> > > > Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> > > > To: general@incubator.apache.org
> > > >
> > > >
> > > > Hi,
> > > >
> > > > -1 binding, willing to change my vote if encryption code issue
> > clarified.
> > > >
> > > > > The artifacts can be downloaded here:
> https://repository.apache.org/
> > > > content/
> > > > > repositories/orgapachepirk-1002
> > > >
> > > > Please place the artefacts in the correct place [1] That that
> releases
> > > MUST
> > > > be placed in the list area and that maven is considered a secondary
> > > > channel.
> > > >
> > > > I checked:
> > > > - name included incubating
> > > > - signature and hashes good
> > > > - DISCLAIMER exists
> > > > - LICENSE and NOTICE good
> > > > - No unexpected binary files in release
> > > > - Can compile from source
> > > >
> > > > I see that the release looks to contains encryption source code [2]
> > > > (Paillier) [5], if so has this process been followed? [3] I can't
> see
> > > Prik
> > > > listed here [4].
> > > >
> > > > Just out of interest why the “wideskies” in the class path name?
> > > >
> > > > Thanks,
> > > > Justin
> > > >
> > > > 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> > > > 2. ./src/main/java/org/apache/pirk/encryption/
> > > > 3. http://www.apache.org/dev/crypto.html
> > > > 4. http://www.apache.org/licenses/exports/
> > > > 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
> > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > >
> >
>
Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk
0.1.0-incubating Release)
Posted by Ellison Anne Williams <ea...@gmail.com>.
Hi Guys,
Thanks so much for jumping on this - you beat me to it this morning! I will
cancel the IMPC vote, re-spin and push the artifacts, and start over again.
Ellison Anne
On Thu, Aug 25, 2016 at 7:52 AM, Suneel Marthi <sm...@apache.org> wrote:
> On Thu, Aug 25, 2016 at 7:51 AM, Suneel Marthi <sm...@apache.org> wrote:
>
> > Thanks Tim.
> >
> > Next Steps to move forward with the Release (for the Release Manager):
> >
> > 1. Merge PR#80 and PR#79 to codebase.
> >
> > 2. Respond to general@ that we'll be pushing new artifacts with updated
> > ReadMe.
> >
> > 3. Drop the existing Staging artifacts from Nexus
> >
> > 4. Rollback the present Release.
> >
> > 5. Create a new Release Candidate
> >
> > Since its only a ReadMe change, I don't think we need to go thru Voting
> > time and it should suffice to pass the Release once we have the minimum
> > required 3 +1s.
> >
>
> meant to say "I don't we need to go thru a 72 hr Voting time"
>
> >
> > For the Release Manager: please read my comments in PR#70 and modify the
> > local settings.xml accordingly. It would be a good idea to go thru a
> DryRun
> > locally first.
> >
> >
> >
> > On Thu, Aug 25, 2016 at 7:28 AM, Tim Ellison <t....@gmail.com>
> > wrote:
> >
> >> On 25/08/16 01:26, Ellison Anne Williams wrote:
> >> > Yes, as per http://www.apache.org/dev/crypto.html --
> >> >
> >> > The code falls under ECCN 5D002, so we are good there.
> >> >
> >> > We need to:
> >> >
> >> > (1) Notify the USG via the sending the specified email
> >>
> >> Done. I cc:'d the dev list, but it may be stuck in moderation.
> >>
> >> > (2) Add a README containing the crypto -- Do we have to go through the
> >> > entire voting process again internally since we are adding a file to
> the
> >> > source release?
> >>
> >> See PR#80. Yep, I'm afraid we will have to re-spin the build :-(
> >>
> >> Apologies for not thinking of export classification earlier, it is
> >> something I have done a few times before too. Please add a line to the
> >> Release Guide to consider whether there needs an update the export page.
> >>
> >> > (3) Edit the export list to add Pirk here
> >> > http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has
> >> access to
> >> > edit the page? I don't think that I do as it says that anyone with
> >> 'site-dev
> >> > karma' can edit and, as far as I know, I don't have site-dev karma.
> >>
> >> Done, see http://www.apache.org/licenses/exports/
> >>
> >> Regards,
> >> Tim
> >>
> >> > On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <
> suneel.marthi@gmail.com
> >> >
> >> > wrote:
> >> >
> >> >> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
> >> >> eawilliamspirk@gmail.com> wrote:
> >> >>
> >> >>> Got it - will take care of it tonight/in the morning and report back
> >> to
> >> >>> general@incubator
> >> >>>
> >> >>> I'd better notify the USG of the crypto - lol :)
> >> >>>
> >> >>
> >> >> That's the part that had me laughing, all of this source code came
> out
> >> of
> >> >> USG and we are being told to check with USG again.
> >> >>
> >> >> At the very least we may need to add Pirk to the list of exports -
> >> (4), for
> >> >> Justin to reverse his -1
> >> >>
> >> >>
> >> >>> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
> >> suneel.marthi@gmail.com>
> >> >>> wrote:
> >> >>>
> >> >>>> Fyi folks
> >> >>>>
> >> >>>>
> >> >>>> ---------- Forwarded message ----------
> >> >>>> From: Justin Mclean <ju...@classsoftware.com>
> >> >>>> Date: Wed, Aug 24, 2016 at 7:48 PM
> >> >>>> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> >> >>>> To: general@incubator.apache.org
> >> >>>>
> >> >>>>
> >> >>>> Hi,
> >> >>>>
> >> >>>> -1 binding, willing to change my vote if encryption code issue
> >> >> clarified.
> >> >>>>
> >> >>>>> The artifacts can be downloaded here:
> >> https://repository.apache.org/
> >> >>>> content/
> >> >>>>> repositories/orgapachepirk-1002
> >> >>>>
> >> >>>> Please place the artefacts in the correct place [1] That that
> >> releases
> >> >>> MUST
> >> >>>> be placed in the list area and that maven is considered a secondary
> >> >>>> channel.
> >> >>>>
> >> >>>> I checked:
> >> >>>> - name included incubating
> >> >>>> - signature and hashes good
> >> >>>> - DISCLAIMER exists
> >> >>>> - LICENSE and NOTICE good
> >> >>>> - No unexpected binary files in release
> >> >>>> - Can compile from source
> >> >>>>
> >> >>>> I see that the release looks to contains encryption source code [2]
> >> >>>> (Paillier) [5], if so has this process been followed? [3] I can't
> >> see
> >> >>> Prik
> >> >>>> listed here [4].
> >> >>>>
> >> >>>> Just out of interest why the “wideskies” in the class path name?
> >> >>>>
> >> >>>> Thanks,
> >> >>>> Justin
> >> >>>>
> >> >>>> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> >> >>>> 2. ./src/main/java/org/apache/pirk/encryption/
> >> >>>> 3. http://www.apache.org/dev/crypto.html
> >> >>>> 4. http://www.apache.org/licenses/exports/
> >> >>>> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
> >> >>>>
> >> >>>>
> >> >>>> ------------------------------------------------------------
> >> ---------
> >> >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> >>>> For additional commands, e-mail: general-help@incubator.apache.org
> >> >>>>
> >> >>>
> >> >>
> >> >
> >>
> >
> >
>
Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk
0.1.0-incubating Release)
Posted by Suneel Marthi <sm...@apache.org>.
On Thu, Aug 25, 2016 at 7:51 AM, Suneel Marthi <sm...@apache.org> wrote:
> Thanks Tim.
>
> Next Steps to move forward with the Release (for the Release Manager):
>
> 1. Merge PR#80 and PR#79 to codebase.
>
> 2. Respond to general@ that we'll be pushing new artifacts with updated
> ReadMe.
>
> 3. Drop the existing Staging artifacts from Nexus
>
> 4. Rollback the present Release.
>
> 5. Create a new Release Candidate
>
> Since its only a ReadMe change, I don't think we need to go thru Voting
> time and it should suffice to pass the Release once we have the minimum
> required 3 +1s.
>
meant to say "I don't we need to go thru a 72 hr Voting time"
>
> For the Release Manager: please read my comments in PR#70 and modify the
> local settings.xml accordingly. It would be a good idea to go thru a DryRun
> locally first.
>
>
>
> On Thu, Aug 25, 2016 at 7:28 AM, Tim Ellison <t....@gmail.com>
> wrote:
>
>> On 25/08/16 01:26, Ellison Anne Williams wrote:
>> > Yes, as per http://www.apache.org/dev/crypto.html --
>> >
>> > The code falls under ECCN 5D002, so we are good there.
>> >
>> > We need to:
>> >
>> > (1) Notify the USG via the sending the specified email
>>
>> Done. I cc:'d the dev list, but it may be stuck in moderation.
>>
>> > (2) Add a README containing the crypto -- Do we have to go through the
>> > entire voting process again internally since we are adding a file to the
>> > source release?
>>
>> See PR#80. Yep, I'm afraid we will have to re-spin the build :-(
>>
>> Apologies for not thinking of export classification earlier, it is
>> something I have done a few times before too. Please add a line to the
>> Release Guide to consider whether there needs an update the export page.
>>
>> > (3) Edit the export list to add Pirk here
>> > http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has
>> access to
>> > edit the page? I don't think that I do as it says that anyone with
>> 'site-dev
>> > karma' can edit and, as far as I know, I don't have site-dev karma.
>>
>> Done, see http://www.apache.org/licenses/exports/
>>
>> Regards,
>> Tim
>>
>> > On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <suneel.marthi@gmail.com
>> >
>> > wrote:
>> >
>> >> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
>> >> eawilliamspirk@gmail.com> wrote:
>> >>
>> >>> Got it - will take care of it tonight/in the morning and report back
>> to
>> >>> general@incubator
>> >>>
>> >>> I'd better notify the USG of the crypto - lol :)
>> >>>
>> >>
>> >> That's the part that had me laughing, all of this source code came out
>> of
>> >> USG and we are being told to check with USG again.
>> >>
>> >> At the very least we may need to add Pirk to the list of exports -
>> (4), for
>> >> Justin to reverse his -1
>> >>
>> >>
>> >>> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
>> suneel.marthi@gmail.com>
>> >>> wrote:
>> >>>
>> >>>> Fyi folks
>> >>>>
>> >>>>
>> >>>> ---------- Forwarded message ----------
>> >>>> From: Justin Mclean <ju...@classsoftware.com>
>> >>>> Date: Wed, Aug 24, 2016 at 7:48 PM
>> >>>> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
>> >>>> To: general@incubator.apache.org
>> >>>>
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> -1 binding, willing to change my vote if encryption code issue
>> >> clarified.
>> >>>>
>> >>>>> The artifacts can be downloaded here:
>> https://repository.apache.org/
>> >>>> content/
>> >>>>> repositories/orgapachepirk-1002
>> >>>>
>> >>>> Please place the artefacts in the correct place [1] That that
>> releases
>> >>> MUST
>> >>>> be placed in the list area and that maven is considered a secondary
>> >>>> channel.
>> >>>>
>> >>>> I checked:
>> >>>> - name included incubating
>> >>>> - signature and hashes good
>> >>>> - DISCLAIMER exists
>> >>>> - LICENSE and NOTICE good
>> >>>> - No unexpected binary files in release
>> >>>> - Can compile from source
>> >>>>
>> >>>> I see that the release looks to contains encryption source code [2]
>> >>>> (Paillier) [5], if so has this process been followed? [3] I can't
>> see
>> >>> Prik
>> >>>> listed here [4].
>> >>>>
>> >>>> Just out of interest why the “wideskies” in the class path name?
>> >>>>
>> >>>> Thanks,
>> >>>> Justin
>> >>>>
>> >>>> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
>> >>>> 2. ./src/main/java/org/apache/pirk/encryption/
>> >>>> 3. http://www.apache.org/dev/crypto.html
>> >>>> 4. http://www.apache.org/licenses/exports/
>> >>>> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------
>> ---------
>> >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>>> For additional commands, e-mail: general-help@incubator.apache.org
>> >>>>
>> >>>
>> >>
>> >
>>
>
>
Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk
0.1.0-incubating Release)
Posted by Suneel Marthi <sm...@apache.org>.
Thanks Tim.
Next Steps to move forward with the Release (for the Release Manager):
1. Merge PR#80 and PR#79 to codebase.
2. Respond to general@ that we'll be pushing new artifacts with updated
ReadMe.
3. Drop the existing Staging artifacts from Nexus
4. Rollback the present Release.
5. Create a new Release Candidate
Since its only a ReadMe change, I don't think we need to go thru Voting
time and it should suffice to pass the Release once we have the minimum
required 3 +1s.
For the Release Manager: please read my comments in PR#70 and modify the
local settings.xml accordingly. It would be a good idea to go thru a DryRun
locally first.
On Thu, Aug 25, 2016 at 7:28 AM, Tim Ellison <t....@gmail.com> wrote:
> On 25/08/16 01:26, Ellison Anne Williams wrote:
> > Yes, as per http://www.apache.org/dev/crypto.html --
> >
> > The code falls under ECCN 5D002, so we are good there.
> >
> > We need to:
> >
> > (1) Notify the USG via the sending the specified email
>
> Done. I cc:'d the dev list, but it may be stuck in moderation.
>
> > (2) Add a README containing the crypto -- Do we have to go through the
> > entire voting process again internally since we are adding a file to the
> > source release?
>
> See PR#80. Yep, I'm afraid we will have to re-spin the build :-(
>
> Apologies for not thinking of export classification earlier, it is
> something I have done a few times before too. Please add a line to the
> Release Guide to consider whether there needs an update the export page.
>
> > (3) Edit the export list to add Pirk here
> > http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access
> to
> > edit the page? I don't think that I do as it says that anyone with
> 'site-dev
> > karma' can edit and, as far as I know, I don't have site-dev karma.
>
> Done, see http://www.apache.org/licenses/exports/
>
> Regards,
> Tim
>
> > On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> >> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
> >> eawilliamspirk@gmail.com> wrote:
> >>
> >>> Got it - will take care of it tonight/in the morning and report back to
> >>> general@incubator
> >>>
> >>> I'd better notify the USG of the crypto - lol :)
> >>>
> >>
> >> That's the part that had me laughing, all of this source code came out
> of
> >> USG and we are being told to check with USG again.
> >>
> >> At the very least we may need to add Pirk to the list of exports - (4),
> for
> >> Justin to reverse his -1
> >>
> >>
> >>> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <
> suneel.marthi@gmail.com>
> >>> wrote:
> >>>
> >>>> Fyi folks
> >>>>
> >>>>
> >>>> ---------- Forwarded message ----------
> >>>> From: Justin Mclean <ju...@classsoftware.com>
> >>>> Date: Wed, Aug 24, 2016 at 7:48 PM
> >>>> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> >>>> To: general@incubator.apache.org
> >>>>
> >>>>
> >>>> Hi,
> >>>>
> >>>> -1 binding, willing to change my vote if encryption code issue
> >> clarified.
> >>>>
> >>>>> The artifacts can be downloaded here: https://repository.apache.org/
> >>>> content/
> >>>>> repositories/orgapachepirk-1002
> >>>>
> >>>> Please place the artefacts in the correct place [1] That that releases
> >>> MUST
> >>>> be placed in the list area and that maven is considered a secondary
> >>>> channel.
> >>>>
> >>>> I checked:
> >>>> - name included incubating
> >>>> - signature and hashes good
> >>>> - DISCLAIMER exists
> >>>> - LICENSE and NOTICE good
> >>>> - No unexpected binary files in release
> >>>> - Can compile from source
> >>>>
> >>>> I see that the release looks to contains encryption source code [2]
> >>>> (Paillier) [5], if so has this process been followed? [3] I can't see
> >>> Prik
> >>>> listed here [4].
> >>>>
> >>>> Just out of interest why the “wideskies” in the class path name?
> >>>>
> >>>> Thanks,
> >>>> Justin
> >>>>
> >>>> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> >>>> 2. ./src/main/java/org/apache/pirk/encryption/
> >>>> 3. http://www.apache.org/dev/crypto.html
> >>>> 4. http://www.apache.org/licenses/exports/
> >>>> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>>
> >>>
> >>
> >
>
Pirk export classification tasks (was: Re: [VOTE] Apache Pirk
0.1.0-incubating Release)
Posted by Tim Ellison <t....@gmail.com>.
On 25/08/16 01:26, Ellison Anne Williams wrote:
> Yes, as per http://www.apache.org/dev/crypto.html --
>
> The code falls under ECCN 5D002, so we are good there.
>
> We need to:
>
> (1) Notify the USG via the sending the specified email
Done. I cc:'d the dev list, but it may be stuck in moderation.
> (2) Add a README containing the crypto -- Do we have to go through the
> entire voting process again internally since we are adding a file to the
> source release?
See PR#80. Yep, I'm afraid we will have to re-spin the build :-(
Apologies for not thinking of export classification earlier, it is
something I have done a few times before too. Please add a line to the
Release Guide to consider whether there needs an update the export page.
> (3) Edit the export list to add Pirk here
> http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access to
> edit the page? I don't think that I do as it says that anyone with 'site-dev
> karma' can edit and, as far as I know, I don't have site-dev karma.
Done, see http://www.apache.org/licenses/exports/
Regards,
Tim
> On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
>> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
>> eawilliamspirk@gmail.com> wrote:
>>
>>> Got it - will take care of it tonight/in the morning and report back to
>>> general@incubator
>>>
>>> I'd better notify the USG of the crypto - lol :)
>>>
>>
>> That's the part that had me laughing, all of this source code came out of
>> USG and we are being told to check with USG again.
>>
>> At the very least we may need to add Pirk to the list of exports - (4), for
>> Justin to reverse his -1
>>
>>
>>> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <su...@gmail.com>
>>> wrote:
>>>
>>>> Fyi folks
>>>>
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Justin Mclean <ju...@classsoftware.com>
>>>> Date: Wed, Aug 24, 2016 at 7:48 PM
>>>> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
>>>> To: general@incubator.apache.org
>>>>
>>>>
>>>> Hi,
>>>>
>>>> -1 binding, willing to change my vote if encryption code issue
>> clarified.
>>>>
>>>>> The artifacts can be downloaded here: https://repository.apache.org/
>>>> content/
>>>>> repositories/orgapachepirk-1002
>>>>
>>>> Please place the artefacts in the correct place [1] That that releases
>>> MUST
>>>> be placed in the list area and that maven is considered a secondary
>>>> channel.
>>>>
>>>> I checked:
>>>> - name included incubating
>>>> - signature and hashes good
>>>> - DISCLAIMER exists
>>>> - LICENSE and NOTICE good
>>>> - No unexpected binary files in release
>>>> - Can compile from source
>>>>
>>>> I see that the release looks to contains encryption source code [2]
>>>> (Paillier) [5], if so has this process been followed? [3] I can't see
>>> Prik
>>>> listed here [4].
>>>>
>>>> Just out of interest why the \u201cwideskies\u201d in the class path name?
>>>>
>>>> Thanks,
>>>> Justin
>>>>
>>>> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
>>>> 2. ./src/main/java/org/apache/pirk/encryption/
>>>> 3. http://www.apache.org/dev/crypto.html
>>>> 4. http://www.apache.org/licenses/exports/
>>>> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Ellison Anne Williams <ea...@gmail.com>.
Yes, as per http://www.apache.org/dev/crypto.html --
The code falls under ECCN 5D002, so we are good there.
We need to:
(1) Notify the USG via the sending the specified email
(2) Add a README containing the crypto -- Do we have to go through the
entire voting process again internally since we are adding a file to the
source release?
(3) Edit the export list to add Pirk here
http://www.apache.org/licenses/exports/ -- Who (of our PPMC) has access to
edit the page? I don't think that I do as it says that anyone with 'site-dev
karma' can edit and, as far as I know, I don't have site-dev karma.
On Wed, Aug 24, 2016 at 8:15 PM, Suneel Marthi <su...@gmail.com>
wrote:
> On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
>
> > Got it - will take care of it tonight/in the morning and report back to
> > general@incubator
> >
> > I'd better notify the USG of the crypto - lol :)
> >
>
> That's the part that had me laughing, all of this source code came out of
> USG and we are being told to check with USG again.
>
> At the very least we may need to add Pirk to the list of exports - (4), for
> Justin to reverse his -1
>
>
> > On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <su...@gmail.com>
> > wrote:
> >
> > > Fyi folks
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Justin Mclean <ju...@classsoftware.com>
> > > Date: Wed, Aug 24, 2016 at 7:48 PM
> > > Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> > > To: general@incubator.apache.org
> > >
> > >
> > > Hi,
> > >
> > > -1 binding, willing to change my vote if encryption code issue
> clarified.
> > >
> > > > The artifacts can be downloaded here: https://repository.apache.org/
> > > content/
> > > > repositories/orgapachepirk-1002
> > >
> > > Please place the artefacts in the correct place [1] That that releases
> > MUST
> > > be placed in the list area and that maven is considered a secondary
> > > channel.
> > >
> > > I checked:
> > > - name included incubating
> > > - signature and hashes good
> > > - DISCLAIMER exists
> > > - LICENSE and NOTICE good
> > > - No unexpected binary files in release
> > > - Can compile from source
> > >
> > > I see that the release looks to contains encryption source code [2]
> > > (Paillier) [5], if so has this process been followed? [3] I can't see
> > Prik
> > > listed here [4].
> > >
> > > Just out of interest why the “wideskies” in the class path name?
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> > > 2. ./src/main/java/org/apache/pirk/encryption/
> > > 3. http://www.apache.org/dev/crypto.html
> > > 4. http://www.apache.org/licenses/exports/
> > > 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Suneel Marthi <su...@gmail.com>.
On Wed, Aug 24, 2016 at 8:13 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:
> Got it - will take care of it tonight/in the morning and report back to
> general@incubator
>
> I'd better notify the USG of the crypto - lol :)
>
That's the part that had me laughing, all of this source code came out of
USG and we are being told to check with USG again.
At the very least we may need to add Pirk to the list of exports - (4), for
Justin to reverse his -1
> On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <su...@gmail.com>
> wrote:
>
> > Fyi folks
> >
> >
> > ---------- Forwarded message ----------
> > From: Justin Mclean <ju...@classsoftware.com>
> > Date: Wed, Aug 24, 2016 at 7:48 PM
> > Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> > To: general@incubator.apache.org
> >
> >
> > Hi,
> >
> > -1 binding, willing to change my vote if encryption code issue clarified.
> >
> > > The artifacts can be downloaded here: https://repository.apache.org/
> > content/
> > > repositories/orgapachepirk-1002
> >
> > Please place the artefacts in the correct place [1] That that releases
> MUST
> > be placed in the list area and that maven is considered a secondary
> > channel.
> >
> > I checked:
> > - name included incubating
> > - signature and hashes good
> > - DISCLAIMER exists
> > - LICENSE and NOTICE good
> > - No unexpected binary files in release
> > - Can compile from source
> >
> > I see that the release looks to contains encryption source code [2]
> > (Paillier) [5], if so has this process been followed? [3] I can't see
> Prik
> > listed here [4].
> >
> > Just out of interest why the “wideskies” in the class path name?
> >
> > Thanks,
> > Justin
> >
> > 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> > 2. ./src/main/java/org/apache/pirk/encryption/
> > 3. http://www.apache.org/dev/crypto.html
> > 4. http://www.apache.org/licenses/exports/
> > 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Ellison Anne Williams <ea...@gmail.com>.
Got it - will take care of it tonight/in the morning and report back to
general@incubator
I'd better notify the USG of the crypto - lol :)
On Wed, Aug 24, 2016 at 8:00 PM, Suneel Marthi <su...@gmail.com>
wrote:
> Fyi folks
>
>
> ---------- Forwarded message ----------
> From: Justin Mclean <ju...@classsoftware.com>
> Date: Wed, Aug 24, 2016 at 7:48 PM
> Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
> To: general@incubator.apache.org
>
>
> Hi,
>
> -1 binding, willing to change my vote if encryption code issue clarified.
>
> > The artifacts can be downloaded here: https://repository.apache.org/
> content/
> > repositories/orgapachepirk-1002
>
> Please place the artefacts in the correct place [1] That that releases MUST
> be placed in the list area and that maven is considered a secondary
> channel.
>
> I checked:
> - name included incubating
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - No unexpected binary files in release
> - Can compile from source
>
> I see that the release looks to contains encryption source code [2]
> (Paillier) [5], if so has this process been followed? [3] I can't see Prik
> listed here [4].
>
> Just out of interest why the “wideskies” in the class path name?
>
> Thanks,
> Justin
>
> 1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
> 2. ./src/main/java/org/apache/pirk/encryption/
> 3. http://www.apache.org/dev/crypto.html
> 4. http://www.apache.org/licenses/exports/
> 5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Fwd: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Suneel Marthi <su...@gmail.com>.
Fyi folks
---------- Forwarded message ----------
From: Justin Mclean <ju...@classsoftware.com>
Date: Wed, Aug 24, 2016 at 7:48 PM
Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release
To: general@incubator.apache.org
Hi,
-1 binding, willing to change my vote if encryption code issue clarified.
> The artifacts can be downloaded here: https://repository.apache.org/
content/
> repositories/orgapachepirk-1002
Please place the artefacts in the correct place [1] That that releases MUST
be placed in the list area and that maven is considered a secondary channel.
I checked:
- name included incubating
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files in release
- Can compile from source
I see that the release looks to contains encryption source code [2]
(Paillier) [5], if so has this process been followed? [3] I can't see Prik
listed here [4].
Just out of interest why the “wideskies” in the class path name?
Thanks,
Justin
1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
2. ./src/main/java/org/apache/pirk/encryption/
3. http://www.apache.org/dev/crypto.html
4. http://www.apache.org/licenses/exports/
5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
-1 binding, willing to change my vote if encryption code issue clarified.
> The artifacts can be downloaded here: https://repository.apache.org/content/
> repositories/orgapachepirk-1002
Please place the artefacts in the correct place [1] That that releases MUST be placed in the list area and that maven is considered a secondary channel.
I checked:
- name included incubating
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files in release
- Can compile from source
I see that the release looks to contains encryption source code [2] (Paillier) [5], if so has this process been followed? [3] I can't see Prik listed here [4].
Just out of interest why the “wideskies” in the class path name?
Thanks,
Justin
1. https://dist.apache.org/repos/dist/dev/incubator/pirk/
2. ./src/main/java/org/apache/pirk/encryption/
3. http://www.apache.org/dev/crypto.html
4. http://www.apache.org/licenses/exports/
5. https://en.wikipedia.org/wiki/Paillier_cryptosystem
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (binding):
Checked:
- signatures are good
- version contains incubating
- LICENSE, NOTICE and DISCLAIMER exists and correct
- No binaries in the source distribution
- Can compile from the source distribution
- All sources contain the ASF header
Regards
JB
On 08/24/2016 07:16 PM, Ellison Anne Williams wrote:
> Hi All,
>
> The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed; it is
> a source-only release (no binary artifacts). We kindly request that the
> IPMC now vote on the release.
>
> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/f9321c1ce45c4f696639ecac2eac6acdcfbff6a669281941c9c06742@%3Cdev.pirk.apache.org%3E
>
> The artifacts can be downloaded here: https://repository.apache.org/content/
> repositories/orgapachepirk-1002
>
> The artifacts have been signed with key 1FD8849B found in the KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/pirk/KEYS
>
> All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'.
> You can view the release notes here: https://issues.apache.
> org/jira/secure/ReleaseNote.jspa?projectId=12320320&version=12338109
>
> Please vote accordingly:
>
> [ ] +1, accept as the official Apache Pirk 0.1.0-incubating release
> [ ] -1, do not accept as the official Apache Pirk 0.1.0-incubating release
> because...
>
> The vote will run for at least 72 hours.
>
> Thanks!
>
> Ellison Anne
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Fwd: [VOTE] Apache Pirk 0.1.0-incubating Release
Posted by Ellison Anne Williams <ea...@gmail.com>.
Email sent to general@incubator to call the vote. Please follow the vote
thread there. Thanks!
---------- Forwarded message ----------
From: Ellison Anne Williams <ea...@gmail.com>
Date: Wed, Aug 24, 2016 at 1:16 PM
Subject: [VOTE] Apache Pirk 0.1.0-incubating Release
To: general@incubator.apache.org
Hi All,
The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed; it is
a source-only release (no binary artifacts). We kindly request that the
IPMC now vote on the release.
The PPMC vote thread is located here: https://lists.apache.org/thread.html/
f9321c1ce45c4f696639ecac2eac6acdcfbff6a669281941c9c06742@%
3Cdev.pirk.apache.org%3E
The artifacts can be downloaded here: https://repository.apach
e.org/content/repositories/orgapachepirk-1002
The artifacts have been signed with key 1FD8849B found in the KEYS file:
https://dist.apache.org/repos/dist/dev/incubator/pirk/KEYS
All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'.
You can view the release notes here: https://issues.apache.or
g/jira/secure/ReleaseNote.jspa?projectId=12320320&version=12338109
Please vote accordingly:
[ ] +1, accept as the official Apache Pirk 0.1.0-incubating release
[ ] -1, do not accept as the official Apache Pirk 0.1.0-incubating release
because...
The vote will run for at least 72 hours.
Thanks!
Ellison Anne