Yes, many thanks. I made a couple of trivial edits, and signed off on the report. I'll find Greg sometime today and encourage him to review it as well. :)
-Hyrum On Tue, Jun 12, 2012 at 12:58 PM, Joachim Dreimann <[email protected]> wrote: > Thanks Gary. I'm happy with the report, seems to reflect the current status > well. > > - Joe > > On 12 June 2012 11:18, Gary Martin <[email protected]> wrote: > >> Hi everyone, >> >> OK, I have thrown some words together from some notes I had and I have >> updated our section of the report with the following if anyone would like >> to review it: >> >> Bloodhound is an issue tracker derivative of Trac, with the goal of making >> deployment easy, and usage intuitive. >> >> Bloodhound has been incubating since December 2011. >> >> The top three issues that need to be addressed to move toward graduation >> are >> still: >> >> 1. Improving community diversity >> 2. Lowering the barrier to entry and development >> 3. Creating shippable releases and getting user feedback >> >> Over the last three months there has been significant design and >> development >> effort into the project, taking the codebase from being a basic installer >> to >> add a new interface. The front-end design is considered to be complete at >> this >> stage but more work is required to implement this design. Despite this, the >> project remains installable and it has become possible for new developers >> to >> contribute relatively quickly. >> >> No new committers have been added over the last three months but we have >> had >> very welcome patches from new contributors. Activity on the developer >> mailing >> list seems to have reduced which is disappointing. This may be remedied in >> part by encouraging more discussion that currently takes place in the issue >> tracker to take place in the mailing list. >> >> The target of creating an initial release is ongoing. With the conversion >> of >> most of the interface to a new basic design, it is only completion of a >> subset >> of the dashboard design that should be seen as a requirement for an initial >> release. This remains the immediate primary goal of the community. >> >> >> Thanks to everyone for their patience in waiting so long for me to >> complete that! >> >> Cheers, >> Gary >> >> >> >> On 06/12/2012 11:05 AM, Gary Martin wrote: >> >>> Hi, >>> >>> Assuming that nobody else has done it, I am finally able to attempt to do >>> the report. I'll write something up, paste it into the wiki and then repeat >>> that here. I assume that we will be able to continue revising the entry so >>> I will hope for comments on anything I have missed or might be considered >>> misleading. >>> >>> Cheers, >>> Gary >>> >>> >>> On 06/09/2012 12:06 PM, Greg Stein wrote: >>> >>>> I'll write a report later tonight (I'm EST). But if someone gets there >>>> first... cool. >>>> >>>> Cheers, >>>> -g >>>> On Jun 9, 2012 6:18 AM, "Marvin"<[email protected]> 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, 20 June 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, Jun 6th). >>>>> >>>>> 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: >>>>> >>>>> http://wiki.apache.org/**incubator/June2012<http://wiki.apache.org/incubator/June2012> >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>> >> -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
