Hi All,
We would like to discuss the proposal of a new project to the incubator - Pirk.
Pirk is a framework for scalable Private Information Retrieval (PIR).
The proposal is contained below and can also be found on the wiki at
https://wiki.apache.org/incubator/PirkProposal
Looking forward to the discussion -
Thanks!
Ellison Anne
= Pirk Proposal =
== Abstract ==
Pirk is a framework for scalable Private Information Retrieval (PIR).
== Proposal ==
Pirk is a software framework for scalable Private Information Retrieval and is
meant to provide a landing place for robust, scalable, and practical
implementations of PIR algorithms. The initial scalable PIR algorithms of Pirk
were developed at the National Security Agency.
== Background ==
Private Information Retrieval (PIR) is an area of computer science and
mathematics that enables a user/entity to privately and securely obtain
information from a dataset, to which they have been granted access, without
revealing, to the dataset owner or to an observer, any information regarding
the questions asked or the results obtained. Employing homomorphic encryption
techniques, PIR enables datasets to remain resident in their native locations
while giving the ability to query the datasets with sensitive terms.
== Rationale ==
Although PIR has been in existence for over twenty years, it has largely
remained an academic discipline with very little robust or scalable
implementation. Pirk not only provides implementations of novel scalable PIR
algorithms, but it provides a framework into which robust, scalable, and
practical PIR may be developed.
Pirk fits well within the Apache Software Foundation (ASF) family as it depends
on numerous ASF projects and integrates with several others such as Hadoop and
Spark. We also anticipate developing extensions/adaptors for several other ASF
projects such as Kafka, Storm, HBase, and Accumulo in the near future.
== Initial Goals ==
* Ensure all dependencies are compliant with Apache License version 2.0 and
that all code and documentation artifacts have the correct Apache licensing
markings and notice.
* Establish a formal release process and schedule, allowing for dependable
release cycles in a manner consistent with the Apache development process.
* Establish a process which allows different release cycles for the core
framework, extensions/adaptors, and additional algorithms.
* Grow the community to establish diversity of background and expertise.
== Current Status ==
=== Meritocracy ===
We will actively seek help and encourage promotion of influence in the project
through meritocracy. We will discuss the requirements in an open forum. We will
encourage and monitor community participation so that privileges can be
extended to those that contribute.
=== Community ===
Pirk currently has a community of developers within the U.S. government. In
open sourcing Pirk we plan to grow the community to a broader base of
industries and will work to align the interaction of our existing community.
=== Core Developers ===
The initial core developers are employed by the US Government. We will work to
grow the community among a more diverse set of developers and industries.
=== Alignment ===
Pirk was developed with an open source philosophy in mind and the Apache way is
consistent with the approach we have taken to date. Further, Pirk depends on
numerous ASF libraries and projects including Hadoop, Spark, Commons, and
Maven. We also anticipate extensions and dependencies with several more ASF
projects, including Accumulo, Avro, HBase, Storm, Kafka, and others. This
existing alignment with Apache and the desired community makes the Apache
Incubator a good fit for Pirk.
== Known Risks ==
=== Orphaned Products ===
Risk of orphaning is limited though it is important to grow the community. The
project user and developer base is growing and there is already operational use
of Pirk.
=== Inexperience with Open Source ===
The initial committers to Pirk have limited experience with true open source
software development. However, despite the project origins being from closed
source development we have modeled our behavior and community development on
The Apache Way to the greatest extent possible. We are committed to the ideals
of open source software and will eagerly seek out mentors and sponsors who can
help us quickly come up to speed.
=== Homogenous Developers ===
The initial committers of Pirk come from a limited set of entities though we
are committed to recruiting and developing additional committers from a broad
spectrum of industries and backgrounds.
=== Reliance on Salaried Developers ===
We expect Pirk development to continue on salaried time and through volunteer
time. The majority of initial committers are paid by their employers to
contribute to this project. We are committed to developing and recruiting
participation from developers both salar