pirk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Ellison <t.p.elli...@gmail.com>
Subject Re: Draft for Review - October Podling Report
Date Fri, 07 Oct 2016 13:29:21 GMT
On 07/10/16 12:59, Ellison Anne Williams wrote:
> Good points. From a mentor perspective, what would you consider to be
> diverse enough community involvement for the project to be self-sustaining?

The goal is to ensure that if one or two existing people / companies
decide (for whatever reason) that they no longer want to participate in
Pirk, the community will be able to continue.

Now we don't need to get into a debate about how likely that loss is for
Pirk, but as a general rule the guidance is that having three distinct
'entities' as regular committers would be a minimum.

Of course, the more the better.

Take a look here for a good overview


> On Fri, Oct 7, 2016 at 4:56 AM, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> On 05/10/16 13:50, Ellison Anne Williams wrote:
>>> It appears that podling reports have been moved to quarterly instead of
>>> monthly - looks like we don't have to submit a report until December.
>>> http://incubator.apache.org/report-groups.txt
>>> (Thanks to Suneel for the info!)
>> Sure, though I still think it is worth us reflecting on progress more
>> frequently.  I have no fear of the code (IP) cleanliness, procedures, or
>> personalities involved in Pirk.  I do worry a bit about whether Pirk
>> will be self-sustaining in terms of diverse community involvement.
>> It is still early days, and there has been good progress on developer
>> and user documentation and guidance.  Hopefully we can continue in that
>> vein, and the project will continue to see the benefits.
>> Regards,
>> Tim
>>> On Wed, Oct 5, 2016 at 4:14 AM, Tim Ellison <t.p.ellison@gmail.com>
>> wrote:
>>>> On 01/10/16 01:14, Ellison Anne Williams wrote:
>>>>> Hi Guys,
>>>>> Please find the draft podling report for October below -- please let
>>>>> know if you have any comments/suggestions/questions. I will post it to
>>>> the
>>>>> incubator wiki when everyone is happy with it.
>>>>> Thanks!
>>>>> Ellison Anne
>>>> FYI the layout got messed up on my client, so I hit return a few times
>>>> to reformat the text below...
>>>>> PirkPirk is a framework for scalable Private Information Retrieval
>>>>> (PIR).
>>>>> Pirk has been incubating since 2016-06-17. The initial code for
>>>>> Pirk was granted on 2016-07-11.
>>>>> Three most important issues to address in the move towards graduation:
>>>>> 1. Grow the community to establish diversity of background 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 code base.
>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>>>>> be aware of?
>>>>> None.
>>>>> How has the community developed since the last report?
>>>>> We have attracted a couple of new contributors since the last report.
>>>>> The mailing list activity, pull requests, and page views to the Apache
>>>>> Pirk website (via Google Analytics) have also increased since the last
>>>>> report.
>>>>> How has the project developed since the last report?
>>>>> The project is in the process of completing it's second release,
>>>>> 0.2.0-incubating. The project has also undertaken a refactor of some
>>>>> the packages and drivers and added additional user/developer
>>>>> documentation on the website.
>>>>> Date of last release:
>>>>> August 29, 2016
>>>>> When were the last committers or PMC members elected?
>>>>> Pirk elected two new committers (Tim Ellison and Suneel Marthi, both
>>>>> mentors) on August 18, 2016.
>>>> +1 from me.
>>>> I think we are well on the the way to achieving goal two, the repeatable
>>>> release process/schedule, and as you have written, it is now a case of
>>>> focusing on user and developer community to ensure the project is
>>>> sustainable in the long run.
>>>> Regards,
>>>> Tim

View raw message