allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <>
Subject Re: Incubator PMC/Board report for Sep 2012 ([ppmc])
Date Mon, 03 Sep 2012 17:00:24 GMT
If this looks fine, I'll post it to the wiki page for our mentors to sign off.

Allura is forge software for the development of software projects, including
source control systems, issue tracking, discussion, wiki, and other software
project management tools.

Allura has been incubating since June 2012.

A list of the three most important issues to address in the move towards graduation

  1. Move project development to ASF hardware
  2. Grow the community
  3. Verify distribution rights, esp. with regard to dependencies' licenses

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?

  No issues at this time

How has the community developed since the last report?

  We have had several introductions and discussions among developers and users
  on the allura mailing list.  We recieved and merged two patches from a
  contributor (who isn't a committer).  The Bloodhound podling is in a similar
  domain as Allura, so we have had some cross-list emails.

How has the project developed since the last report?

  All active committers have submitted CLAs and have accounts created.  The
  software grant for Allura has been submitted.  On the mailing list, several
  licensing questions have been discussed and resolved how to handle: external
  contributions, handling of a non-essential GPL library, and handling of our
  ForgeHg tool which has a dependency on the GPL'd mercurial library.


On 9/3/12 12:19 PM, Dave Brondsema wrote:
> Rich prepared last month's report; I can work on this months' today.
> Apparently we report monthly for the first few months (I didn't realize
> that until now).
> On 9/3/12 9:22 AM, Marvin wrote:
>> Dear podling,
>> This email was sent by an automated system on behalf of the Apache Incubator PMC.
>> It is an initial reminder to give you plenty of time to prepare your quarterly
>> board report.
>> The board meeting is scheduled for Wed, 19 September 2012, 10:00:00 PST. The report

>> for your podling will form a part of the Incubator PMC report. The Incubator PMC

>> requires your report to be submitted 2 weeks before the board meeting, to allow 
>> sufficient time for review and submission (Wed, Sep 5th).
>> Please submit your report with sufficient time to allow the incubator PMC, and 
>> subsequently board members to review and digest. Again, the very latest you 
>> should submit your report is 2 weeks prior to the board meeting.
>> Thanks,
>> The Apache Incubator PMC
>> Submitting your Report
>> ----------------------
>> Your report should contain the following:
>>  * Your project name
>>  * A brief description of your project, which assumes no knowledge of the project
>>    or necessarily of its field
>>  * A list of the three most important issues to address in the move towards 
>>    graduation.
>>  * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
>>  * How has the community developed since the last report
>>  * How has the project developed since the last report.
>> This should be appended to the Incubator Wiki page at:
>> Note: This manually populated. You may need to wait a little before this page is
>>       created from a template.
>> Mentors
>> -------
>> Mentors should review reports for their project(s) and sign them off on the 
>> Incubator wiki page. Signing off reports shows that you are following the 
>> project - projects that are not signed may raise alarms for the Incubator PMC.
>> Incubator PMC

Dave Brondsema : : personal : programming

View raw message