Re: Simple pull request

> On Thu, Jul 14, 2016 at 3:03 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > I think we can take those instructions from Mahout and tailor them for > > Pirk. > > > > (As Mahout PMC u have our permission to do that - kidding :) ) > > > > Ho

Upgrade ElasticSearch version

Please update the ElasticSearch version to 2.3.4 in the next commit or PR. Thanks.

Re: [GitHub] incubator-pirk issue #19: PIRK-10: Upgrade and Enforce Java 8

yeah, wasn't sure if we wanted to retain some Java 7 compatibility. Maybe retain as 1.7 still. On Sat, Jul 23, 2016 at 6:00 PM, Tim Ellison wrote: > On 23/07/16 03:54, smarthi wrote: > > Github user smarthi commented on the issue: > > > >

Re: Minimum Maven version

how do i access that? On Fri, Jul 22, 2016 at 10:05 PM, Joe Witt <joe.w...@gmail.com> wrote: > Did you look in /home/travis/build/apache/incubator-pirk/target/rat.txt? > > The RAT reports are generally pretty good I have found. > > On Fri, Jul 22, 2016 at 10:04 PM, Sune

Re: Minimum Maven version

/rat.txt -> [Help 1] On Fri, Jul 22, 2016 at 6:07 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > ... I am also gonna disable Jdk 7 jobs on travis as part of this change. > > OK with @here ? > > > On Fri, Jul 22, 2016 at 6:01 PM, Suneel Marthi <suneel.mar...@gma

Re: Minimum Maven version

... I am also gonna disable Jdk 7 jobs on travis as part of this change. OK with @here ? On Fri, Jul 22, 2016 at 6:01 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > Let's go with Option 1, i can modify .travis.yml to account for Maven 3.3x > > On Fri, Jul 22, 2016

Re: Minimum Maven version

We r good now, I disabled the rat check to get past the build failure, i guess we don't need that for travis, do we? On Fri, Jul 22, 2016 at 6:19 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > Getting a travis build error for RAT, any ideas ? I am not seeing this > locally

Re: Minimum Maven version

some of the checks as people put in PRs. > > I'm happy to help do licensing/header hunting soon. > > Thanks > Joe > > On Fri, Jul 22, 2016 at 6:53 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > We r good now, I disabled the rat check to get past the build fai

Re: Minimum Maven version

master/pom.xml#L257-L268 > > That will address the XML parsing issue I believe and should also > address the travis.yml header issue. > > Thanks > Joe > > On Fri, Jul 22, 2016 at 10:06 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > how do i access that? >

Re: Interest in extending to Cascading?

There was a talk at Apachecon NA, May 2016, Vancouver by Ken Krugler about Cascading + Flink. Flink does provide a Cascading extension but its not part of Apache Flink and is a side project from Data artisans - https://github.com/dataArtisans/cascading-flink But as u said there are no

Re: PIR reading list

On Tue, Aug 9, 2016 at 6:02 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi Tim, > > Disclaimer: As a pure mathematician by training, I'm bent towards the > theoretic mathematical explanations of PIR. :) > > PIR has 'historically' (it's only 20 yrs or so old) been a theoretic >

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

en automatically? Ugh. > > On Sat, Aug 13, 2016 at 8:30 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > > Seems like we are missing the signature .asc files and Nexus has failed > to > > push the artifacts to staging. > > > > We need to rollback the

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

ew vote email thread and declare this > one null or keep this one going? > > On Sat, Aug 13, 2016 at 4:33 PM, Suneel Marthi <smar...@apache.org> wrote: > > > ... and in https://dist.apache.org/repos/dist/dev/incubator/pirk/ > > > > On Sat, Aug 13, 2016 at 4:23 PM,

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

at 8:22 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > In Nexus, > > 1. Select 'orgapachepirk-1000' in staging repositories. > 2. Click on 'Close' button on top -> will prompt u for a message -> fill > in 'Blah blah' > 3. Nexus then puts the artifacts to a st

Re: FindBugs in Eclipse

On Fri, Aug 12, 2016 at 11:23 AM, Tim Ellison <t.p.elli...@gmail.com> wrote: > On 12/08/16 16:15, Suneel Marthi wrote: > > Most Apache committers I have known (most of Databricks, Hadoop vendors, > > Data Artisans and others) are all IntelliJ users and IntelliJ has > excel

Re: FindBugs in Eclipse

Most Apache committers I have known (most of Databricks, Hadoop vendors, Data Artisans and others) are all IntelliJ users and IntelliJ has excellent code inspection (much much better than Eclipse). I personally never had a need for findbugs. On Fri, Aug 12, 2016 at 11:06 AM, Tim Ellison

Re: Release Preparations

I am pushing in one last change in next 20 mins, this is to enable the code coverage badge on github. On Fri, Aug 12, 2016 at 12:05 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > I'm about to tag all of our completed/closed JIRA issues to-date with Fix > Version = 0.1.0 in

Re: Mentor Question -- Release and Pom File

. On Sat, Aug 13, 2016 at 8:57 AM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > You should use -Psigned_release. > > Once u r past release:prepare and release:perform and u need to rollback. > > -- run mvn -Psigned_release release:rollback > mvn -Psign

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

I am thinking we could have one Vote that runs for 72 hrs, approving the candidate release branch would also mean testing and validating the artifacts. correct? On Sat, Aug 13, 2016 at 8:49 AM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi All, > > After some hiccups last night

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

s, but it seemed to make sense to me to > use a double internal vote until we are comfortable with releasing and work > out some of the kinks. Either way, I think that we should cut release > branches and generate release artifacts from there. > > Thoughts? > > > > On

Re: Mentor Question -- Release and Pom File

rm no foul. > > On Sat, Aug 13, 2016 at 9:13 AM, Suneel Marthi <smar...@apache.org> wrote: > > Oh yes, that's the reason why my settings didn't work. Should we add the > > parent POM and delete ? > > > > > > @Joe, any idea how to purge > > https://re

Re: Mentor Question -- Release and Pom File

eatedwilversionofmypassword=} > > > > > On Sat, Aug 13, 2016 at 9:22 AM, Suneel Marthi <smar...@apache.org> wrote: > > I had the real apache repo URL in POM as opposed to the staging URL. So > > that completely bypassed staging. > > > > If I am und

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

... and in https://dist.apache.org/repos/dist/dev/incubator/pirk/ On Sat, Aug 13, 2016 at 4:23 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > The KEYS file has been pushed to https://dist.apache.org/repos/ > dist/release/incubator/pirk/ > > On Sat, Aug 13, 2016 at 4:08 P

Re: [VOTE] Pirk's First Release - 0.1.0 - Branch Vote

:-) I was gonna suggest :- 1. push the artifacts to staging on Nexus at https://repository.apache. org/service/local/staging/deploy/maven2 2. call for a Vote on the staged artifacts 3. Once Vote passes, 'Release' the artifacts in Nexus and that would transfer them to

Re: Release Preparations

wrote: > No problem - I will most likely cut the branch late afternoon - let's say, > after 3 PM EST. > > On Fri, Aug 12, 2016 at 12:07 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > > I am pushing in one last change in next 20 mins, this is to enable the

Re: Build failed in Jenkins: pirk #8

I have seen this happen occasionally on other projects too, in large part its caused by multiple builds from different projects queued up on a server and forking multiple jvms to execute unit tests and integration tests and crashing. I bet it would work now if u trigger a manual build. For a

PR merge process

I am seeing that the original author of a PR is being wiped out while committing the PRs to the codebase. The 'git commit' command to retain the original author as contributor is: git commit --author -a -m "PIRK- description closes apache/pirk#ZZ" This way the original author would show

Re: Beam Integration

Beam is a project from Google and its been used internally at Google for a while and was recently donated to Apache by Google. I have limited experience working with it, and presently prototyping it at work for a project. You may want to check out the below links.

Re: Establish Coding Standards for Apache Pirk

e only one). But more importantly this is > > something which is quite personal in terms of developer productivity > > and I think there is value in the community avoiding having a > > preferred IDE. > > > > Thanks > > Joe > > > > On Sun, Jul 17,

Re: Planning for first Apache Pirk Release

good time to move forward with the > release. > > > On Fri, Aug 5, 2016 at 9:25 AM, Suneel Marthi <smar...@apache.org> wrote: > > > Hi All, > > > > Given the activity and traction on the project over the last few weeks, > > shall we start planning for the firs

Re: Travis Builds Not Starting for PRs

I did notice that too. Not sure what's going on, I can poke around tomorrow and see what's up with it. On Fri, Aug 5, 2016 at 7:35 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > I've noticed that the Travis builds on the last few PRs have not started - >

Re: Mentors - Release Process?

p with the concerned folks on this. > > One general TODO: > >- In order to publish our release artifact to Maven, we need to have >Pirk setup in the Nexus Repository - a ticket to INFRA is required -- >http://www.apache.org/dev/publishing-maven-artifacts.html#sig

Re: For Review -- Draft August Podling Report

+1 from me. Given the activity on the project over the past few weeks, should we start planning for a first Apache release (say mid-August). Suneel On Fri, Jul 29, 2016 at 10:33 AM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi Mentors, > > Can you please review the following

Re: [VOTE] - Pirk 0.1.0 Release

Thanks for the feedback. Tim. See my comments inline below. @Ellison lets rollback the release. On Mon, Aug 15, 2016 at 7:35 AM, Tim Ellison wrote: > On 14/08/16 04:19, Ellison Anne Williams wrote: > > Hi, > > > > This is the vote for release 0.1.0 of Apache Pirk

Re: [VOTE] - Pirk 0.1.0 Release

t; > > So, not done yet... I will rollback once we figure out what's going on (so > that folks can still access the artifacts). > > > > On Mon, Aug 15, 2016 at 8:28 AM, Suneel Marthi <smar...@apache.org> wrote: > > > Thanks for the feedback. Tim. > > > >

Next Steps - Pirk Release

1. Drop the staging artifacts in Nexus 2. Cancel the previous Vote 3. Someone verify the Notice and License files, and bless them 4. Push a new Release Candidate

Re: [GitHub] incubator-pirk pull request #62: [WIP - Do not Merge] Fix code warnings

Agree, they should be merged to master. Please go ahead and do it. On Mon, Aug 15, 2016 at 11:17 AM, Tim Ellison wrote: > Suneel, > > I know you have marked this as WIP, but they look good, why not merge > them now to master so they don't get stale? The release branch

Re: [VOTE] - Pirk 0.1.0 Release

> > > On 16/08/16 13:06, Suneel Marthi wrote: > > > On Tue, Aug 16, 2016 at 7:42 AM, Tim Ellison <t.p.elli...@gmail.com> > > wrote: > > > > > >> On 15/08/16 23:36, Suneel Marthi wrote: > > >>> To test this PR locally , perform a dry-run

Re: Source JAR vs. Convenience binary JAR license files (was: Re: [GitHub] incubator-pirk pull request #65: [PIRK-53] - Fix LICENSE and NOTICE Files fo...)

On Wed, Aug 17, 2016 at 10:38 AM, Tim Ellison wrote: > On 17/08/16 11:40, ellisonanne wrote: > > Github user ellisonanne commented on a diff in the pull request: > > > > https://github.com/apache/incubator-pirk/pull/65# > discussion_r75099656 > > > > --- Diff:

Re: New Pirk Committers - Tim Ellison and Suneel Marthi

Thanks for the honor, glad to be part of this project. On Thu, Aug 18, 2016 at 4:58 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > As per the vote on private, I would like to extend a welcome to our newest > Pirk committers - Tim Ellison and Suneel

Re: Source JAR vs. Convenience binary JAR license files

iscuss the submodule breakout > > > > On Sat, Aug 20, 2016 at 1:13 PM, Suneel Marthi <suneel.mar...@gmail.com> > > wrote: > > > >> For this release, lets add the README as has been suggested. > >> > >> > >> --- > >&

Re: Source JAR vs. Convenience binary JAR license files

NF/LICENSE /META-INF/bin-license-notice/NOTICE-bin - should be in /META-INF/NOTICE easy fix 3. Why do we have META-INF/bin-license-notice instead of just META-INF ? I'll address (1). On Fri, Aug 19, 2016 at 10:53 AM, Suneel Marthi <smar...@apache.org> wrote: > > > On Fri, Aug

Re: Source JAR vs. Convenience binary JAR license files

On Fri, Aug 19, 2016 at 11:13 AM, Tim Ellison <t.p.elli...@gmail.com> wrote: > On 19/08/16 15:53, Suneel Marthi wrote: > > On Fri, Aug 19, 2016 at 10:13 AM, Tim Ellison <t.p.elli...@gmail.com> > wrote: > > >> I'd appreciate other mentors' close

Re: Source JAR vs. Convenience binary JAR license files

On Fri, Aug 19, 2016 at 10:13 AM, Tim Ellison wrote: > On 19/08/16 14:52, Ellison Anne Williams wrote: > > Can you please take a look at PR 65 (PIRK-53) and let me know if we are > > ready to go with L for our first release? > > I feel like I'm being the bad cop :-( > >

Re: Source JAR vs. Convenience binary JAR license files

omment that I sent a few minutes ago. > > Thanks! > > > On Fri, Aug 19, 2016 at 11:16 AM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > > On Fri, Aug 19, 2016 at 11:13 AM, Tim Ellison <t.p.elli...@gmail.com> > > wrote: > > > > > On 19/0

Re: [VOTE] - Pirk 0.1.0 Release

To test this PR locally , perform a dry-run of mvn -Psigned_release release:prepare Verify target/apache-pirk-0.1.0-incubating-sources.jar and target/apache-pirk-0.1.0-incubating.jar On Mon, Aug 15, 2016 at 6:29 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > I fixed issue

Re: [VOTE] - Pirk 0.1.0 Release

I concur. On Mon, Aug 15, 2016 at 8:37 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > With Suneel's pom updates to remove the offending openjdk files from > apache-pirk-0.1.0-incubating-sources.jar, the only remaining issue is the > jboss-logging license issue. > > This appears

Re: Source JAR vs. Convenience binary JAR license files

+1 On Sat, Aug 20, 2016 at 12:40 PM, Tim Ellison wrote: > On 20 August 2016 at 17:04, Ellison Anne Williams < > eawilliamsp...@gmail.com> > wrote: > > > Yes, if that's acceptable, then I can go that route. > > > > I can allow the artifacts to be generated and pushed to

Fwd: Apache PIO v0.10.0 release

If you aren't including such files in every jar fix the build so it happens as required. You can avoid dealing with binary artifact requirements by producing only source artifacts for releases. > On Aug 20, 2016, at 11:24 AM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > > This

Re: [VOTE] - Pirk 0.1.0 Release

Yes Josh, source-release.zip I assume is the "official release artifact" and that's the one I had verified. We need to get our packaging correct following this release and split the project up to be more modular; that way its easier to manage the final release artifacts with the appropriate

Re: Draft Podling Report

ground and expertise. 2. Establish a formal > >>> release > >>> >> process and schedule, allowing for dependable release > >>> cycles in > >>> a > >>> >> manner consistent with the Apache development process. > >>> 3. Add > >>> to > >>> >> and improve the Pirk user documentation and examples both on > >>> the > >>> >> website and in the codebaseAny issues that the Incubator PMC > >>> (IPMC) > >>> or > >>> >> ASF Board wish/need to beaware of? Yes. The Pirk community > >>> >> participation and growth has stalled over the last few months. > >>> >> Recently, there has been discussion on the mailing list about > >>> retiring > >>> >> Pirk (putting it in the attic) for right now.How has the > >>> community > >>> >> developed since the last report? The Pirk community has not > >>> developed > >>> >> since the last report - there have been no new contributors or > >>> >> committers added.How has the project developed since the last > >>> report? > >>> >> The Pirk project has stalled - the existing community has > >>> not been > >>> >> active nor has the community grown.Date of last release: > >>> October 9, > >>> >> 2016When were the last committers or PMC members elected? > Pirk > >>> >> elected two new committers (Tim Ellison and Suneel Marthi, > both > >>> >> mentors) on August 18, 2016. > >>> >> > >>> >> > >>> > >>> > >>> > >>> > >> >

Re: Wiki permissions?

could u add me to pirk confluence wiki - smarthi ? On Tue, Aug 23, 2016 at 11:57 AM, Josh Elser wrote: > Thanks, Joe. > > Poking around. I have no idea how to do anything on confluence :) > > Joe Witt wrote: > >> added Elser and Tim as admins. Cannot figure out Ellison's

Re: [VOTE] Apache Pirk 0.1.0-incubating Release

g, 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.mar...@gmail.co

Fwd: [VOTE] Apache Pirk 0.1.0-incubating Release

Fyi folks -- Forwarded message -- From: Justin Mclean Date: Wed, Aug 24, 2016 at 7:48 PM Subject: Re: [VOTE] Apache Pirk 0.1.0-incubating Release To: gene...@incubator.apache.org Hi, -1 binding, willing to change my vote if encryption code issue

Re: [VOTE] Apache Pirk 0.1.0-incubating Release

On Wed, Aug 24, 2016 at 9:09 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > > > On Wed, Aug 24, 2016 at 8:26 PM, Ellison Anne Williams < > eawilliamsp...@gmail.com> wrote: > >> Yes, as per http://www.apache.org/dev/crypto.html -- >> >> Th

Re: [VOTE] Apache Pirk 0.1.0-incubating Release

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,

Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

On Thu, Aug 25, 2016 at 7:51 AM, Suneel Marthi <smar...@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 w

Re: Pirk export classification tasks (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

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.mar...

Re: Out of Pocket

Same here, I'll be out this week and in Berlin next week. On Tue, Sep 6, 2016 at 3:39 PM, Ellison Anne Williams wrote: > Hi Guys, > > Forgot to mention that I would be mostly out of pocket starting last > Thursday through the end of this week. I will be checking email >

Re: Website Updates - Please Review

Never mind, i see that this has been taken care of.. sorry!! On Tue, Aug 30, 2016 at 11:57 AM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > There's one step we missed and is still pending in the Release process - > creating a 0.1.0 tag in github and checking in the 0.1.0 artif

Re: For Mentors - Correct [ANNOUNCE] Distro?

yes, it should also be sent to annou...@apache.org On Tue, Aug 30, 2016 at 11:34 AM, Ellison Anne Williams < eawilli...@apache.org> wrote: > Hi Mentors, > > It seems clear that the [ANNOUNCE] email should be sent to our dev list and > the general@incubator list. Does it also need to be send to >

Re: Website Updates - Please Review

There's one step we missed and is still pending in the Release process - creating a 0.1.0 tag in github and checking in the 0.1.0 artifacts against this tag. @ellisonAnne ^^^ On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams < eawilli...@apache.org> wrote: > Hi, > > Given that it's

Re: Website Updates - Please Review

On Tue, Aug 30, 2016 at 12:05 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > > > On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams < > eawilli...@apache.org> wrote: > >> Hi, >> >> Given that it's generally a mess to put website updates thro

Re: Website Updates - Please Review

ally used 'mvn -Psigned_release release:rollback' to to roll > back the release -- I used the alternate steps that you gave here: > https://lists.apache.org/thread.html/c8acce2a20e8e2671d85fd8504bb2c > 7c52ebb5159b955ec762754bc7@%3Cdev.pirk.apache.org%3E > > > > On Tue, Aug 30, 2

Re: Website Updates - Please Review

On Tue, Aug 30, 2016 at 11:50 AM, Ellison Anne Williams < eawilli...@apache.org> wrote: > Hi, > > Given that it's generally a mess to put website updates through the PR > system (due to the large number of auxiliary files changed - in the > hundreds...), I have made several updates to the Apache

Re: Completing Apache Pirk 0.1.0-incubating Release

I am finalizing the release now !! On Mon, Aug 29, 2016 at 7:58 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > Should I go ahead and finish the release? > > Sent from my iPhone > > > On Aug 29, 2016, at 7:05 PM, Ellison Anne Williams < > eawilliamsp...@gma

Re: Completing Apache Pirk 0.1.0-incubating Release

oe.w...@gmail.com> wrote: > > > Congrats all! > > > > On Aug 29, 2016 5:04 PM, "Suneel Marthi" <suneel.mar...@gmail.com> > wrote: > > > > > I am finalizing the release now !! > > > > > > On Mon, Aug 29, 2016 at 7:58 PM, Suneel Mar

Re: Completing Apache Pirk 0.1.0-incubating Release

; documentation that I have been keeping throughout the release process. > > Will send out the email now. > > On Mon, Aug 29, 2016 at 8:26 PM, Suneel Marthi <suneel.mar...@gmail.com> > wrote: > > > Its done, there's only 2 steps to finalize the Release from where we lef

Is it ok to use Java 8 lambdas in Pirk ?

not sure how it would behave on Storm, MapReduce that don't support lambdas yet

Re: Draft for Review - Apache Pirk September Podling Report

the project may well be > desirable, > > but I don't really see it as a graduation issue. > > > > Growing the user and development community is definitely a key goal for > > Pirk graduation. Personally, I'd move that further up the list. We can > > discuss ideas

Re: Next short term goal?

Once I am back home from Berlin next week, I was looking at working on Responder-Flink, Flink's awesome Streaming capabilities (its not mini-batch like the other hyped ones) makes Flink the perfect distributed engine to implement the Wideskies algorithm. It would help for Pirk-noobs like me and

Re: Next Release

Would u like me to do it? I would rather someone else did it though, I can jump in if none show up. On Thu, Sep 29, 2016 at 5:16 PM, Ellison Anne Williams < eawilli...@apache.org> wrote: > Is any other committer volunteering to serve as release manager for our > release tomorrow/Friday? If I

Re: [GitHub] incubator-pirk pull request #93: WIP-Pirk 63-DO NOT MERGE

Refactor is definitely a first priority. Is there a design/proposal draft that we could comment on about how to go about refactoring the code. I have been trying to keep up with the emails but definitely would have missed some. On Mon, Sep 19, 2016 at 6:57 PM, Ellison Anne Williams <

Re: [GitHub] incubator-pirk pull request #93: WIP-Pirk 63-DO NOT MERGE

(??? :-) ) https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65870673 On Mon, Sep 19, 2016 at 11:07 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > A shared Google doc would be more convenient than a bunch of Jiras. Its > easier to comment and add notes that way. > > >

Re: [GitHub] incubator-pirk pull request #93: WIP-Pirk 63-DO NOT MERGE

k > pirk-benchmark > pirk-distributed-test > > Once we add other responder implementations, we can add them as submodules > - i.e. for Flink, we would have pirk-flink; for Beam, pirk-beam, etc. > > We could break 'pirk-core' down further... > > On Mon, Sep 19, 2016 at 5

Re: [jira] [Commented] (PIRK-13) Switch from json-simple to Jackson

We can just stick with Simple JSON then, I agree that the move to Jackson is more involved and impacts large swaths of the codebase. Given this I'll go ahead and modify the JsonSerializer to use Simple JSON and we have one less license to deal with ☺ On Wed, Aug 17, 2016 at 9:52 PM, Walter

Re: [jira] [Commented] (PIRK-13) Switch from json-simple to Jackson

Simple JSON seems to not handle generics well enuf. I guess we need to take a stab at this code and gradually move to Jackson and defer this Jira to a later release. If it makes it easier to use Gson over Jackson, then let's go for it. On Thu, Aug 18, 2016 at 12:33 AM, Suneel Marthi <s

Re: Distributed Tests Before Accepting PR

Apologies for this. Reverting now. On Thu, Aug 18, 2016 at 12:12 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi Guys, > > As a friendly public service announcement - please make sure that you run > the distributed test suite before you accept a PR (or at least, before >

Re: [jira] [Commented] (PIRK-13) Switch from json-simple to Jackson

e > simplest approach philosophically or with regards to dependencies (mostly > licenses) it would be using the appropriate tool for each job. > > — > Jacob WIlder > > On Thu, Aug 18, 2016 at 1:01 AM, Suneel Marthi <smar...@apache.org> wrote: > > > Simple JSON seems t

Re: [jira] [Commented] (PIRK-13) Switch from json-simple to Jackson

I guess we could resolve this JIRA as 'Will not Fix' . On Thu, Aug 18, 2016 at 12:28 PM, Suneel Marthi <suneel.mar...@gmail.com> wrote: > That's how we have it now. Let's keep that way then. > > On Thu, Aug 18, 2016 at 12:24 PM, Jacob Wilder < > jacobwilder.openso

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

I think we shuld close the vote once we hit a quorum of 3 +1 (binding) votes. On Thu, Aug 25, 2016 at 12:23 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > This is the vote for release 0.1.0 of Apache Pirk (incubating); it is a > source-only release (no binary artifacts).

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

+1 binding 1. Verified the ReadMe for Export controls 2. Verified Hashs and Sigs 3. RAT check passes 4. Clean build from Source and all tests pass On Thu, Aug 25, 2016 at 12:23 PM, Ellison Anne Williams < eawilliamsp...@gmail.com> wrote: > Hi, > > This is the vote for release 0.1.0 of Apache

Re: Storm Implementation of Pirk

+1 to go with log4j2 - 2.1 as a temporary solution. +1 to merge this PR On Fri, Aug 26, 2016 at 2:09 PM, Chris Harris wrote: > Hi All, > > I am taking the WIP tag off of the Storm implementation for Pirk. It > passes all tests and provides accurate results when

Re: Mentors Question - IPMC Vote

+1 u can Close the Vote now. On Mon, Aug 29, 2016 at 11:50 AM, Billie Rinaldi wrote: > I think you can go ahead and call it. :-) > > On Mon, Aug 29, 2016 at 8:41 AM, Ellison Anne Williams < > eawilliamsp...@gmail.com> wrote: > > > Hi Guys, > > > > It has been 72 hours since

Re: [VOTE] - Pirk 0.1.0 Release (PPMC re-vote)

Nope, that should be fine. On Fri, Aug 26, 2016 at 12:45 AM, Walter Ray-Dulany wrote: > Does it matter that this release candidate is at > https://org/apache/pirk/pirk/ > instead of ...org/apache/pirk/apache-pirk/ like the last candidate > was? > > Walter > > On

Re: Cleaning our Nexus Staging Repo

close the vote (I was going to wait until COB, > > but it has been 72 hrs). > > > > On Wed, Aug 24, 2016 at 10:31 AM, Suneel Marthi <suneel.mar...@gmail.com > > > > wrote: > > > >> You may want to close the Vote summarizing the results, since its been

Re: Cleaning our Nexus Staging Repo

e the vote (I was going to wait until COB, > > but it has been 72 hrs). > > > > On Wed, Aug 24, 2016 at 10:31 AM, Suneel Marthi <suneel.mar...@gmail.com > > > > wrote: > > > >> You may want to close the Vote summarizing the results, since its been > &g

Re: Next Release

I am cool with someone else playing the RM role, lets plan for a release early next week in time for October incubator report. On Sat, Sep 24, 2016 at 8:19 PM, Walter Ray-Dulany wrote: > No objections, and I would defer to the community on numbering (which right > now

Re: Draft for Review - October Podling Report

cond release, 0.2.0-incubating. The > project has also undertaken a refactor of some of the packages and > drivers and added additional user/developer documentation on the > website.Date of last release: August 29, 2016When were the last > committers or PMC members elected? Pirk elected two new committers > (Tim Ellison and Suneel Marthi, both mentors) on August 18, 2016. >

Re: [VOTE]: Apache Pirk 0.2.0-incubating Release

+1 binding 1. Verified Sigs and Hashes 2. Built from source successfully 3. Checked the License and Notice files 4. RAT checks pass On Fri, Sep 30, 2016 at 7:54 PM, Ellison Anne Williams < eawilli...@apache.org> wrote: > Hi Guys, > > This is the vote for the 0.2.0-incubating (source only)

Re: Wiki Write Access

r of > some of the packages and drivers and added additional user/developer > documentation on the website.Date of last release: August 29, 2016When were > the last committers or PMC members elected? Pirk elected two new committers > (Tim Ellison and Suneel Marthi, both mentors) on Au

Re: [VOTE] Retire Apache Pirk (incubating)

I was recently reading this article about using Homomorphic Encryption for encrypted Deep Learning and building safe A.I. - https://iamtrask.github.io/2017/03/17/safe-ai/ and Pirk with Pallier Encryption was the first thing that came to mind; and the high relevance of Pirk as AI becomes more

Re: Draft Podling Report

t;> Add >>> to >>> >> and improve the Pirk user documentation and examples both on the >>> >> website and in the codebaseAny issues that the Incubator PMC >>> (IPMC) >>> or >>> >> ASF Board wish/need to beaware of? Yes. The Pirk community >>> >> participation and growth has stalled over the last few months. >>> >> Recently, there has been discussion on the mailing list about >>> retiring >>> >> Pirk (putting it in the attic) for right now.How has the >>> community >>> >> developed since the last report? The Pirk community has not >>> developed >>> >> since the last report - there have been no new contributors or >>> >> committers added.How has the project developed since the last >>> report? >>> >> The Pirk project has stalled - the existing community has not >>> been >>> >> active nor has the community grown.Date of last release: >>> October 9, >>> >> 2016When were the last committers or PMC members elected? Pirk >>> >> elected two new committers (Tim Ellison and Suneel Marthi, both >>> >> mentors) on August 18, 2016. >>> >> >>> >> >>> >>> >>> >>> >>> >>

Re: Draft Podling Report

o much on > > > their plate to meaningfully contribute to Pirk right now. (of course, I > > am > > > squarely in that space) If/when that changes, we can always revisit > Pirk > > > and perhaps pull it out of retirement. > > > > > > I will go ahead and

Re: Draft Podling Report

retirement. > > > > > > I will go ahead and submit the report as it is due today. > > > > > > On Wed, Mar 1, 2017 at 9:29 AM, Suneel Marthi <smar...@apache.org> > > wrote: > > > > > >> I concur with everything Tim's said below. As