Incubator project set up tasks

Welcome to the Apache Pirk (incubating) developers' mailing list! This initial mail is mostly to test that the infrastructure has been set up correctly that allows the development community to exchange information and ideas. The current status of tasks establishing the project's infrastructure is

Re: Incubator project set up tasks

On 28/06/16 13:32, Ellison Anne Williams wrote: > Thanks for sending the dev mailing list welcome! That was more of a test that the list had been set up correctly, and apparently it is working. > Yes, it would be great if you could proceed with the name search > procedures. Started, the JIRA iss

Re: Podling Report Reminder - July 2016

I appreciate that folks are likely on holiday at the moment, and that this first report is going to be light given that Apache Pirk is still getting started; but it will be good to see the committers start to build a report format on the wiki in time for the Incubator PMC to review it and submit to

Re: Podling Report Reminder - July 2016

On 05/07/16 14:17, Ellison Anne Williams wrote: > Thanks Josh! I hit 'Save Changes' on the wiki updates right before your > email came through... If you see anything that needs to be changed in the > report (especially as this is the first one that I have written), please > feel free to change/upda

Re: Incubator project set up tasks

On 12/07/16 00:53, Ellison Anne Williams wrote: > Realized that I could create my own JIRA account (duh), did so, and created > a JIRA ticket with the initial Pirk code (zip file) and SGA attached. > > https://issues.apache.org/jira/browse/PIRK-1 Hurray! Well done for getting to this important m

Re: Github Mirror

I was able to clone the code from Github, and compile it! I know folks are busy getting the project set-up, just wanted to check that (i) all the unit tests you expected to be there are committed (there are not many), and (ii) that you expect the tests to pass (they don't for me). Regards, Tim O

Re: Github Mirror

mail.com> wrote: >>>> >>>>> Hi Tim, >>>>> >>>>> It's building fine for us here and the unit tests are passing (a >> couple >>>> of >>>>> us just tried a fresh pull and build) . There are 23 unit tests and a &

Simple pull request

I've submitted PIRK-2 with a simple pull request as a way to test the development process. It's not urgent, so any committer can feel free to play with how you would test it, modify it, accept/reject it etc. It is a real fix though, so I would like to see it accepted eventually :-) Regards, Tim

Re: Simple pull request

On 14/07/16 14:49, Suneel Marthi wrote: > Cool. How do we go about merging github PRs from both committers and > contributors? > > This is how we do it today on Apache Mahout - > http://mahout.apache.org/developers/github.html > > If there r better ways of doing it, would appreciate some pointers

Re: PIRK-7 -- JMH license issues

On 17/07/16 16:57, Ellison Anne Williams wrote: > Suneel -- Thanks for creating the JIRA issue and pointing out the licensing > problems. I see that JMH is under the GNU GPL2 ( > http://openjdk.java.net/legal/) which is not compatible with the Apache > license (http://www.apache.org/legal/resolved.

Re: Establish Coding Standards for Apache Pirk

On 17/07/16 18:29, Joe Witt wrote: > I would recommend at this stage to consider Java 8 as the basis. In > NiFi our upcoming major release establishes java 8 as the baseline. I > believe the community went that route because: > > - It contains language features that are beneficial and that > dev

Re: RTC/CTR Discussion

On 17/07/16 19:31, Suneel Marthi wrote: > +1 to RTC, this is what's presently done on Flink, Mahout and few other > projects I had seen. > > Its usually a committer reviewing the patch, providing feedback, and > finally committing it. > Whether a pull request gets a +1 from another committer or no

Re: PR merge process

On 17/07/16 17:34, Suneel Marthi wrote: > 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

Some code structure thoughts

Breaking out the discussion started by Suneel, I see opportunities for a bit of judicious refactoring of the codebase. I'm no expert on Beam etc., so I'm going to keep out of that decision, simply to say I agree that it is probably a bad idea to create submodules too early. At the moment I'm simp

Evolving the simple example

I'm trying to write the simplest of examples using Pirk, so I can understand what is happening, and I'm stumbling a bit in some of the assumptions and side effects ... I have a simple data schema https://paste.apache.org/TcxK describing my data file https://paste.apache.org/8QDH

Re: RTC/CTR Discussion

On 19/07/16 22:27, Ellison Anne Williams wrote: > It seems that we could give RTC a shot, with one reviewer posting a +1 (or > equivalent) comment on a pull request before it is accepted, and switch > back to CTR if RTC became too burdensome. Who is a "reviewer"? I assume another commiter? > It

Re: Some code structure thoughts

On 18/07/16 19:29, Ellison Anne Williams wrote: > Good points. > > Yes, there are currently no examples included in the codebase (other than > in a roundabout kind of way via the tests, which doesn't count) and the > website doesn't have a step-by-step walkthrough of how to get up and > running fr

Re: incubator-pirk git commit: configuring google analytics

On 21/07/16 00:38, eawilli...@apache.org wrote: > Repository: incubator-pirk > Updated Branches: > refs/heads/gh-pages 22fa4e21f -> 838e508df > > > configuring google analytics > This raises the question about who should have access to the accounts held outside the ASF that are associated wit

Re: PIRK-7 -- JMH license issues

gt; now >>>> vying to provide native runners that can support Beam. This kind'a >> makes >>>> Beam an abstraction over every other streaming framework. >>>> >>>> As an application developer, I would write my jobs against the Beam API >&g

Re: Evolving the simple example

On 20/07/16 23:02, Ellison Anne Williams wrote: > At the risk of making things too nested (and hence difficult to read), I > will answer inline below. Inlining responses is the only sane way to go ;-) See below > On Tue, Jul 19, 2016 at 6:22 AM, Tim Ellison wrote: > >> I

Re: Build failed in Jenkins: pirk #8

On 21/07/16 03:56, Apache Jenkins Server wrote: > See > > Changes: > > [eawilliams] [trivial] -- Enhancements to build XML and Paillier class - > closes > > [eawilliams] [none] -- Replace multi if-else with switch stmts - closes > > --

Re: RTC/CTR Discussion

On 22/07/16 05:50, Andy LoPresto wrote: > One of the nice effects of RTC is that the community gets an > opportunity to gently enforce code convention and prevent rapid build > up of technical debt. Something else I've witnessed is that as the > community grows, non-committers feel more comfortable

Serialization and storage changes

I picked up PIRK-19, about the schema storage format -- but then got a bit distracted :-) I've ended up pulling out the code that deals with serialization and storage in the Querier, Query, and Response classes. As we discussed on another thread, these types shouldn't really be responsible for st

JIRA key names in summary

There are a number of Pirk JIRA issues that have the JIRA Key repeated in summary line. It looks like that was done deliberately and I am just wondering why? e.g. PIRK-15is called "PIRK15 - Add User Documentation to the Pirk Website" Seems redundant, no? Regards, Tim

Re: PIRK Components on JIRA

On 22/07/16 06:36, Andy LoPresto wrote: > Component leads are useful if you want to make sure that someone > (relevant) from the core team sees every issue as it gets reported > (as long as it is assigned to something) and then triages it. If your > core team is not necessarily divided by focus tha

Re: Minimum Maven version

My understanding is that the change to Java 8 was because earlier versions are now end of life, and Pirk's dependencies are moving to Java 8. What is the driver to move up to a later Maven version? I guess as a principle, specifying the lowest possible version of the project's dependencies in the

Re: Minimum Maven version

On 22 July 2016 at 22:13, Joe Witt wrote: > Within NiFi we went with the "oldest version of Maven we could fairly > easily support" approach. I really wish we had not. > > As a new project you have one shot to set some of the fundamentals > down right such as the JVM you're tied to or the Maven

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

On 23/07/16 03:54, smarthi wrote: > Github user smarthi commented on the issue: > > https://github.com/apache/incubator-pirk/pull/19 > > This is good to merge now. It enforces Java 8 and Maven 3.3.9 as also RAT > checks for license headers. Looks like there are still some vestiges of

Re: Authenticating serialized data for safety and peace of mind

Ah the trust model discussion, that wasn't parked for long ;-) On 23/07/16 04:43, Jacob Wilder wrote: > Given that deserialization attacks are a ripe attack surface > it's a > good idea to make it possible to authenticate serializ

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

On 23/07/16 23:03, Suneel Marthi wrote: > yeah, wasn't sure if we wanted to retain some Java 7 compatibility. > > Maybe retain as 1.7 still. What do you mean? Upgrade and enforce Java 8, but only use Java 7 features? Regards, Tim > On Sat, Jul 23, 2016 at 6:00 PM, T

Re: [GitHub] incubator-pirk issue #20: PIRK-11: Switch to SLF4J with Log4j2 bindings

On 23/07/16 15:53, ellisonanne wrote: > Github user ellisonanne commented on the issue: > > https://github.com/apache/incubator-pirk/pull/20 > > +1 > > Phew! That's a lot of files... :) I agree. I just had to merge them into PR#18 ;-) Regards, Tim

Re: Authenticating serialized data for safety and peace of mind

On 23/07/16 21:40, Jacob Wilder wrote: > Andy, I had considered using symmetric signatures but I think that while it > is simpler in the pairwise case it would lead to significant complexity if > we reach a point where one responder is servicing queries for multiple > queriers. In that case we woul

Re: Authenticating serialized data for safety and peace of mind

here. I'm still back at the design points at the moment, I guess there are multiple ways to implement a design around the standard formats for signing, key representation, etc. Are you talking about using BouncyCastle OpenPGP APIs? Regards, Tim > — Jacob Wilder > > >> On Jul 2

Re: Authenticating serialized data for safety and peace of mind

validity of its internally generated Query and Response > objects. I think the suggestion is not just message validation, but also establishing sender identity and comparing it against a white-list too, right? (i.e. a simple form of ACL ;-) Regards, Tim > On Sun, Jul 24, 2016 at 9:40 AM, Tim El

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

the caution? > Hence, I wasn't sure if we wanted to change to 1.8. > > thoughts? I'm for changing it to target Java 8. Regards, Tim > On Sat, Jul 23, 2016 at 6:49 PM, Tim Ellison wrote: > >> On 23/07/16 23:03, Suneel Marthi wrote: >>> yeah, wasn't s

DataSchema schemaName case sensitivity

I'm in the throws of hacking on DataSchema and notice that some parts of the Pirk code maintain case for the schema name, and others map it to lowercase. Any objection to me making Pirk case-preserving and case-sensitive to the data schema name throughout, i.e. fakeDataSchema != fakedataschema? I

Re: RTC/CTR Discussion

> Ellison Anne Williams wrote: >>> >>>> I don't see point in having to get a +1 from another committer for >> fixing >>>> trivial items such as merge conflicts, build breaks, etc. I also would >>>> through trivial updates to the website like fixi

Re: DataSchema schemaName case sensitivity

On 25/07/16 13:40, Ellison Anne Williams wrote: > Sounds good - go for it :) Cool, will do. Thanks Ellison Anne. Regards, Tim > On Mon, Jul 25, 2016 at 8:35 AM, Tim Ellison wrote: > >> I'm in the throws of hacking on DataSchema and notice that some parts of >> t

Re: Trust Model for Pirk

On 24/07/16 17:35, Ellison Anne Williams wrote: > There has been a lot of good discussion lately about signing Pirk objects, > validating, etc in another thread. I would like for us to step back and > consider the trust model for Pirk. > > Pirk is an application that runs within a user's system to

Multiple filters in a query

There was a code comment in the query schema class that stated: "Could easily add the ability for multiple filters (filter list capability) instead of just one." I don't think that is necessary, as it is easy for a user to write a "aggregated filter" that will combine calling multiple filter step

Defining schema code comments (was: Re: [GitHub] incubator-pirk pull request #26: [PIRK-19] Make DataSchema/QuerySchema Agnos...)

On 27/07/16 03:17, ellisonanne wrote: > As a very small (kind of nitty) style item, I would much rather have > setter methods for QuerySchema to set the `elementName` and > `filterNamesSet` rather than setting these fields via > > ``` querySchema.getElementNames().addAll(elementNames); > querySc

Re: Defining schema code comments

On 27/07/16 11:33, Ellison Anne Williams wrote: > Yes, I do agree that schemas are immutable once created - I can't think of > a good/plausible reason why we would need to change a schema once it's > created... > > The incremental composition that you added is very clean -- along those > lines, t

Re: [PIRK-20] Switching to Use Enum for DataTypes | Seeking input

On 27/07/16 16:04, Jacob Wilder wrote: > Hello everyone, > I've tried a few things while working on this but would appreciate some > suggestions on how to move forward. Or perhaps decide not to. > > I've pushed a very limited version of this up here: > https://github.com/jacobwil/incubator-pirk/co

Re: Jenkins build became unstable: pirk » Apache Pirk (incubating) Project #13

On 29/07/16 03:55, Apache Jenkins Server wrote: > See Travis liked this commit ok, but Jenkins failed with: java.io.IOException: No such file or directory at java.io.UnixFileSystem.createFileExclusively(Native Method)

Re: For Review -- Draft August Podling Report

On 29/07/16 15:33, Ellison Anne Williams wrote: > Hi Mentors, > > Can you please review the following draft Pirk podling report? I will post > it on the incubator report wiki once everyone is happy with it. > > Thanks! > > Ellison Anne > > ** > > Pirk > > Pirk is a framework for scala

Re: For Review -- Draft August Podling Report

On 29 July 2016 at 19:17, Ellison Anne Williams wrote: > Tim had submitted a JIRA request for the Pirk podling name search on > 6.28.16: > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-108 > > However, it is still unassigned and thus unresolved/open. What do we need > to do in order t

[OT] vacation time

FYI I'm heading off on annual vacation in the next day or so, and if my family have anything to do with it, I won't be at the keyboard for about 10 days. Assuming the podling report doesn't change significantly, please add my approval as it is transferred to the incubator wiki. Have fun. I'm sur

Re: [GitHub] incubator-pirk issue #44: [PIRK-42]: Fix DataSchema getTextName NullPointerE...

Geez, that's embarrassing. Sorry folks I introduced that bug then disappeared. The fix looks correct, but as I wrote a while ago, we should look to remove Java serialization from Pirk to avoid any number of potential issues. I will raise a JIRA issue to do this, and expect to schedule it for aft

Re: ApacheCon Europe 2016

On 03/08/16 20:36, Ellison Anne Williams wrote: > Hi Suneel, > > I just (yesterday) submitted a proposal for Hadoop Summit Tokyo in October. > Here is the information: > > * > > Title: Scalable Private Information Retrieval — Introducing Apache Pirk > (incubating) > > Abstract: Querying inf

Re: [GitHub] incubator-pirk pull request #48: [Pirk 38]: Update Javadocs for Schema Loade...

Thanks for this Walter. It's good to see the developer docs get some love too. In my defense, I will write full javadocs documentation for Pirk's APIs (i.e. public and protected types/methods), but tend to write comments for private and package level access types/methods that are designed to be r

Re: Mentors - Release Process?

On 06/08/16 21:06, Ellison Anne Williams wrote: > It appears that we reached consensus regarding proceeding with a release. I > would like to get our first release out over the next couple of weeks. Yep, it will be a good practice to release early and often. I don't see any fundamental release bl

PIR reading list

Could folks recommend some reading material to help me become more familiar with the principles behind Pirk's PIR? Many of the publications I have found on-line are academic reviews (information theoretic vs. computational PIR, trading off communication and processing complexity, etc), or deep mat

QueryInfo.queryNum (was: Re: [GitHub] incubator-pirk pull request #43: PIRK-29)

On 02/08/16 21:23, ellisonanne wrote: > Github user ellisonanne commented on a diff in the pull request: > > https://github.com/apache/incubator-pirk/pull/43#discussion_r73229948 > > --- Diff: > src/main/java/org/apache/pirk/querier/wideskies/QuerierDriverCLI.java > --- @@ -55,7 +58,7 @@ public s

Re: QueryInfo.queryNum

On 10/08/16 15:34, Ellison Anne Williams wrote: > First, there are some wacko comments that I made in that pull request that > I tried to delete but don't appear to have quite cleared (in my haste, I > started making comments before going through all of the changes - turns out > I was looking at th

KeyedHash#hash(String, int, String)

Why does org.apache.pirk.utils.KeyedHash#hash(String key, int bitSize, String input) have int fullHash = Math.abs(concat.hashCode()); What is the value of performing the "Math.abs" in computing this hash? p.s. I now realize I'm entering the toddler phase of Pirk development, where I wander a

Fwd: [jira] [Resolved] (PODLINGNAMESEARCH-108) Establish whether "Apache Pirk" is a suitable name

Key: PODLINGNAMESEARCH-108 > URL: > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-108 > Project: Podling Suitable Names Search > Issue Type: Suitable Name Search >Reporter: Tim Ellison > > A suitable name search is requir

Re: [jira] [Resolved] (PODLINGNAMESEARCH-108) Establish whether "Apache Pirk" is a suitable name

On 10/08/16 19:23, Ellison Anne Williams wrote: > w00t! :) > > The tapir (taPIR - yes, we are complete dorks) was our initial contribution > to a Pirk mascot. I'm sure that he can be voted off of the island, if > desired. ;) lol - I missed that reference. I say she can stay (provided the image w

Project logo (was: Re: [jira] [Resolved] (PODLINGNAMESEARCH-108) Establish whether "Apache Pirk" is a suitable name)

n be voted off of the island, if > desired. ;) > > On Wed, Aug 10, 2016 at 1:51 PM, Tim Ellison wrote: > >> Yay! Time to print the T-shirts ;-) >> >> BTW I neglected to mention that the project logo is great. >> (and what's with the Tapir on the homepage?) &

Re: FindBugs in Eclipse

On 12/08/16 14:16, Ellison Anne Williams wrote: > For Eclipse users, there is a Findbugs Eclipse plugin that is super easy to > use. You can find it here: > > https://marketplace.eclipse.org/content/findbugs-eclipse-plugin Yep, I agree. Though I hear rumours that not everybody is an Eclipse user

Re: KeyedHash#hash(String, int, String)

Anyone got thoughts on this? On 10/08/16 17:23, Tim Ellison wrote: > Why does > org.apache.pirk.utils.KeyedHash#hash(String key, int bitSize, String > input) > > have > int fullHash = Math.abs(concat.hashCode()); > > What is the value of performing the "Mat

Re: FindBugs in Eclipse

rds, Tim > On Fri, Aug 12, 2016 at 11:06 AM, Tim Ellison wrote: > >> On 12/08/16 14:16, Ellison Anne Williams wrote: >>> For Eclipse users, there is a Findbugs Eclipse plugin that is super easy >> to >>> use. You can find it here: >>> >>> https

Re: Release Preparations

Keep working it. We could delay the release, but IMO releases should be frequent enough that missing one is not a big deal, and there is no point in delivering function that is not ready yet. Regards, Tim On 12 August 2016 at 22:31, Suneel Marthi wrote: > I have a PR for the Coveralls code cov

Re: [VOTE] - Pirk 0.1.0 Release

On 14/08/16 04:19, Ellison Anne Williams wrote: > Hi, > > This is the vote for release 0.1.0 of Apache Pirk (incubating). > > The vote will be going for at least 72 hours and will be closed on Wednesday > , > August 16, 2016. > > The artifacts can be downloaded here: https://repository.apache. >

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

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 0.1.0 would be unaffected. Regards, Tim On 14/08/16 18:57, smarthi wrote: > GitHub user smarthi opened a pull request: > > https://github.com/apache

Re: KeyedHash#hash(String, int, String)

lue). You are just as likely to get a hash collision by 'folding' the hash value range using abs() as you are taking the lower bits and ignoring the sign bit, aren't you? Regards, Tim > On Fri, Aug 12, 2016 at 11:06 AM, Tim Ellison wrote: > >> Anyone got thoughts on

Re: [VOTE] - Pirk 0.1.0 Release

> that folks can still access the artifacts). Yep, and still work from the 0.1.0 branch so that the development can progress while the release is being tweaked. Regards, Tim > On Mon, Aug 15, 2016 at 8:28 AM, Suneel Marthi wrote: > >> Thanks for the feedback. Tim. >> >>

Data partitioner questions

A couple of questions about the data partitioners... (1) Why do they split into, and reconstruct from, BigIntegers? The types always get decomposed into primitives, and therefore the parts are always BigInteger values of bytes [1], and they are used as intValues [2] when using the exponent tabl

Re: [VOTE] - Pirk 0.1.0 Release

On 14/08/16 04:19, Ellison Anne Williams wrote: > All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'. > You can view them here: https://issues.apache.org/jira/browse/PIRK-47?jql= > project%20%3D%20PIRK%20AND%20fixVersion%20%3D0.1.0 BTW (just so you don't inadvertently send t

Re: KeyedHash#hash(String, int, String)

rything passed. We can remove it, if > desired. Ok, I'll include it in an incoming PR. Removing the abs() now makes it symmetrical with the message digest implementation -- which makes me happy :-) Regards, Tim > On Mon, Aug 15, 2016 at 11:18 AM, Tim Ellison wrote: > >> On

Re: Data partitioner questions

On 15/08/16 20:32, Ellison Anne Williams wrote: > Answers inline below > > On Mon, Aug 15, 2016 at 12:33 PM, Tim Ellison wrote: > >> A couple of questions about the data partitioners... >> >> (1) Why do they split into, and reconstruct from, BigIntegers? >>

Re: [VOTE] - Pirk 0.1.0 Release

ms that we can stand on the Apache Licensing rules and follow >> Spark's lead and include similar language in our NOTICE file. >> >> Can we make the same argument about the org.openjdk.jmh.infra.generated.* >> files in the apache-pirk-0.1.0-incubating-sources.jar? If so

Re: [VOTE] - Pirk 0.1.0 Release

>> parent POM. >> >> For 6, the test material u r seeing is from src/test not from test/. We >> should consider moving those to test/ for the next release, otherwise I >> don't think its a blocker for this release. >> >> Will be pushing a PR soon. >&g

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 wrote: > >> On 15/08/16 23:36, Suneel Marthi wrote: >>> To test this PR locally , perform a dry-run of mvn -Psigned_release >>> release:prepare >>> >>> Verify

Re: [VOTE] - Pirk 0.1.0 Release

; On Tue, Aug 16, 2016 at 9:01 AM, Ellison Anne Williams < >>> eawilliamsp...@gmail.com> wrote: >>> >>>> Hmmm... I didn't see them last night - will double check >>>> >>>> On Tue, Aug 16, 2016 at 8:43 AM, Tim Ellison >>>> wrote

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 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: LICENSE --- > @@ -199,4 +199,64 @@ > distributed under the License is distributed

Re: Source JAR vs. Convenience binary JAR license files

that many projects are not following it -- so something is wrong. http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled http://www.apache.org/dev/licensing-howto.html#binary Regards, Tim > On Wed, Aug 17, 2016 at 10:55 AM, Suneel Marthi > wrote: > >> On Wed, Aug 17,

Re: Source JAR vs. Convenience binary JAR license files

e interpreting it correctly. > > > > On Wed, Aug 17, 2016 at 10:55 AM, Suneel Marthi > wrote: > >> On Wed, Aug 17, 2016 at 10:38 AM, Tim Ellison >> wrote: >> >>> On 17/08/16 11:40, ellisonanne wrote: >>>> Github user ellisonanne

Re: Source JAR vs. Convenience binary JAR license files

nded-resources/META-INF >> https://github.com/apache/hbase/tree/master/hbase- >> thrift/src/main/appended-resources/META-INF >> >> This is for jars; it's also easy to adjust L&N for assemblies (tars and >> zips) because you're explicitly listing files to i

Re: Source JAR vs. Convenience binary JAR license files

gt; src/main/appended-resources/META-INF/LICENSE and >>>> src/main/appended-resources/META-INF/NOTICE that will be appended to >> the >>>> default. See https://issues.apache.org/jira/browse/ACCUMULO-3990 and >>> these >>>> examples: >>>> &g

Re: New Pirk Committers - Tim Ellison and Suneel Marthi

On 18/08/16 21:58, Ellison Anne Williams wrote: > As per the vote on private, I would like to extend a welcome to our newest > Pirk committers - Tim Ellison and Suneel Marthi. Thanks! To celebrate I will spend the remainder of the day setting up my distributed test environment (cough,

Re: [GitHub] incubator-pirk issue #65: [PIRK-53] [WIP] - Fix LICENSE and NOTICE Files for...

On 18/08/16 18:53, smarthi wrote: > Github user smarthi commented on the issue: > > https://github.com/apache/incubator-pirk/pull/65 > > +1 to merge, given that most of the feedback has been addressed now. Really? I have not done a thorough review, but a quick build of remotes/ellison

Re: Distributed Tests Before Accepting PR

On 18/08/16 17:12, Ellison Anne Williams wrote: > 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 > accepting a PR that touches anything affecting the tests). Mea culpa. My usual working practice is

Re: [GitHub] incubator-pirk issue #65: [PIRK-53] [WIP] - Fix LICENSE and NOTICE Files for...

requirements. > > On Fri, Aug 19, 2016 at 6:54 AM, Tim Ellison wrote: > >> On 18/08/16 18:53, smarthi wrote: >>> Github user smarthi commented on the issue: >>> >>> https://github.com/apache/incubator-pirk/pull/65 >>> >>> +1 t

Re: Source JAR vs. Convenience binary JAR license files

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&N for our first release? I feel like I'm being the bad cop :-( I'm trying to put myself into the shoes of somebody picking up one of these artefacts, and

Re: Distributed Tests Before Accepting PR

6 at 9:09 AM, Darin Johnson > wrote: > >> I've built full integration tests with hadoop-minicluster before. They're >> a pain to setup but aren't bad to maintain once done and could be >> integrated into travis-ci. >> >> On Fri, Aug 19, 2016 at

Re: Source JAR vs. Convenience binary JAR license files

On 19/08/16 15:53, Suneel Marthi wrote: > On Fri, Aug 19, 2016 at 10:13 AM, Tim Ellison wrote: >> I'd appreciate other mentors' close review of these built artefacts too. >> >> Seems that the main project source release looks good, but the >> convenience J

Re: Source JAR vs. Convenience binary JAR license files

in hand with the submodule refactor and > proceed with the release. If you have any suggestions on cleaning that > doesn't involve a submodule refactor, I happy to implement them. > > > On Fri, Aug 19, 2016 at 10:53 AM, Suneel Marthi wrote: > >> On Fri, Aug 19, 2016 at 10:

Re: Source JAR vs. Convenience binary JAR license files

On 20 August 2016 at 04:52, Ellison Anne Williams wrote: > After spending a bit of time taking a look at the submodule breakout, I > would rather wait and break the project out into submodules in a more > deliberate manner (not as a first pass just for the binary artifacts). > > As submodules see

Re: Source JAR vs. Convenience binary JAR license files

e a "documented step" until the scripts handle it all. ... or even produce the JAR, then - delete the exe-jar's sig/hash - rearrange the L&N files - re-sign/hash Provided it is a repeatable process for the binaries, I think that would be ok. WDYT? Regards, Tim > On Sat

Re: Source JAR vs. Convenience binary JAR license files

an. To avoid any confusion you may want to consider creating a brief readme file in the META-INF to explain that the L&N files in there only relate to the exe-jar. Regards, Tim > On Sat, Aug 20, 2016 at 11:51 AM, Tim Ellison > wrote: > > > On 20 August 2016 at 16:23, Ellis

Re: [VOTE] - Pirk 0.1.0 Release

On 21/08/16 17:32, Ellison Anne Williams wrote: > This is the vote for release 0.1.0 of Apache Pirk (incubating); it is a > source-only release (no binary artifacts). Please can you clarify what is being proposed for release? Is it all the artefacts at the URL given below? The reason I'm asking

Re: [VOTE] - Pirk 0.1.0 Release

I'm +1 to release https://repository.apache.org/content/repositories/orgapachepirk-1002/org/apache/pirk/apache-pirk/0.1.0-incubating/apache-pirk-0.1.0-incubating-source-release.zip sha1: 1175b40e99e28b8f5cb609a2c0ff65896786f89d My checks worked out ok too. Regards, Tim On 21/08/16 17:32, Ellis

Wiki permissions?

Who has admin rights to the PIRK wiki space [1]? Please could I (tellison) have write access to create a page? [1] https://cwiki.apache.org/confluence/display/PIRK Thanks, Tim

Re: Distributed Tests Before Accepting PR

_developers#testing Thanks, Tim > On Fri, Aug 19, 2016 at 9:09 AM, Darin Johnson > wrote: > >> I've built full integration tests with hadoop-minicluster before. They're >> a pain to setup but aren't bad to maintain once done and could be >> integrated

Re: Wiki permissions?

Seems that Joe was defined as the initial admin, so we'll need him to add more folks. https://issues.apache.org/jira/browse/INFRA-12132 Regards, Tim On 23/08/16 14:16, Ellison Anne Williams wrote: > I don't have permissions... > > On Tue, Aug 23, 2016 at 9:13 AM, Tim Elliso

Re: Wiki permissions?

now we have the following people with all permissions: Billie Rinaldi (billie) Billie Rinaldi (billie.rinaldi) Ellison Anne Williams (eawilliams) Josh Elser (elserj) Joseph Witt (joewitt) Suneel Marthi (smarthi) Tim Ellison (tellison) Regards, Tim

Update ASF ECCN classification page (was: Re: [VOTE] Apache Pirk 0.1.0-incubating Release)

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 > 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 -- >>> >>> T

TSU NOTIFICATION - Encryption

SUBMISSION TYPE: TSU SUBMITTED BY: Tim Ellison SUBMITTED FOR:The Apache Software Foundation POINT OF CONTACT: Secretary, The Apache Software Foundation FAX: +1-919-573-9199 MANUFACTURER(S): The Apache Software Foundation PRODUCT NAME/MODEL

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

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 modera

Re: Distributed Tests Before Accepting PR

o be > set for the various distributed tests. Thanks for pointing this out! > > As time allows, I can add primers for AWS and GCP (specifically). Thanks. It is important that we do distributed testing, so any pointers would be appreciated. Regards, Tim > On Tue, Aug 23, 2016 at 9:19 AM, Ti

  1   2   >