Apache Logo
The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Bloodhound

15 Mar 2017 [Gary Martin / Mark]

Report was filed, but display is awaiting the approval of the Board minutes.

21 Dec 2016 [Gary Martin / Chris]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

The threat of moving the project to the attic is ongoing but further
progress has been acheived in the form of promoting a GSoC student to be
a full committer on the project.

Releases
========

There have been no releases over the last three months. The last release
was towards the end of 2014:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last changes
in December 2016:

Resignations:
 * Mat Booth (12th December 2016)

Additions:
 * Dammina Sahabandu (13th December 2016)

The last new committers were added in May 2014.

Community & Development
=======================

The relatively small numbers of PMC members who are able to contribute
necessary skills for the continuation of the project remains a concern
although it has been mitigated by the addition of Dammina to the PMC.
Dammina was already one of the most active contributors and so it is
hoped that his addition will help drive the project forward.

It was also sad to see the resignation of Mat Booth from the PMC but he
had not considered himself to be one of the active contributors for a
long time. His advice will of course be missed.

The details for these PMC changes will be updated shortly.

There has been a modest increase in the number of emails to the dev list
over the previous quarter. Much of this was driven by Dammina with
discussions of what might go into a new release, updates to Trac and new
ideas around potential changes to the standard icon provider for the
project. In addition there were some queries from users indicating a
few problems with installation documentation and multi-product use cases
that we could better support.

Activity on the user list is negligible.

21 Sep 2016 [Gary Martin / Shane]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

The threat of moving the project to the attic is ongoing but some progress
has been made after an emailed plea for more contributors sent to the dev
email list. A summary of the discussion is provided below.

Releases
========

There have been no releases over the last three months. The last release
was towards the end of 2014:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last additions
in January 2014.

The last new committers were added in May 2014.

Community & Development
=======================

As discussed in the last report there are currently not considered to be
enough PMC members with the necessary skills to continue the project.
Since then an email was sent to the dev list as encouraged by the board
and after this there have been 27 emails to the list that discuss interest
in the project or otherwise represent some attempt to make progress. Of
these there are some responses from GSoC students who might be able to
make a quick transition to be on the PMC.

Areas of progress include restoring the main issue tracker to working
order after it became non-responsive and one potential contributor is
looking at updating the version of Trac upon which Bloodhound is based.

With these discussions ongoing it is probably prudent to take some further
time to encourage the new potential committers to translate interest in
involvement into contributions.

15 Jun 2016

Terminate the Apache Bloodhound Project

 WHEREAS, the Project Management Committee of the Apache Bloodhound
 project has chosen by vote to recommend moving the project to the
 Attic; and

 WHEREAS, the Board of Directors deems it no longer in the best
 interest of the Foundation to continue the Apache Bloodhound project
 due to inactivity;

 NOW, THEREFORE, BE IT RESOLVED, that the Apache Bloodhound project
 is hereby terminated; and be it further

 RESOLVED, that the Attic PMC be and hereby is tasked with oversight
 over the software developed by the Apache Bloodhound Project; and be
 it further

 RESOLVED, that the office of "Vice President, Apache Bloodhound" is
 hereby terminated; and be it further

 RESOLVED, that the Apache Bloodhound PMC is hereby terminated.

 Special Order 7D, Terminate the Apache Bloodhound Project, was
 tabled.

15 Jun 2016 [Gary Martin / Jim]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

The board should be aware that the Bloodhound PMC has voted on moving the
project to the attic as discussed below.

Releases
========

There have been no releases over the last three months. The last release
was towards the end of 2014:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last additions
in January 2014.

The last new committers were added in May 2014.

Community & Development
=======================

As discussed in the last report, due to there not being enough active PMC
members with the necessary skills to keep the project going, there has
been discussion of moving the project to the Attic. As such a vote has been
undertaken to make an official decision on this, which was passed with the
following results:

+1: (7) brane, chambej, gjm, matevz, mbooth, rjollos, saintgermain
0: (0)
-1: (0)

A link to the summary email for this is here: https://s.apache.org/qqj0

The resolution to terminate the Apache Bloodhound project has therefore
been added as item D of the Special Orders section of the board agenda for
this month.

20 Apr 2016 [Gary Martin / Chris]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

The board should be aware that the Bloodhound PMC is discussing moving
the project to the attic as discussed below.

Releases
========

There have been no releases over the last three months. The last release
was in fact towards the end of last year:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last additions
in January 2014.

The last new committers were added in May 2014.

Community & Development
=======================

Committer activity has remained stubbornly low with very little activity
on the development mailing list.

The continued lack of activity led the PMC to discuss whether there are
enough active members of the PMC who have the time, interest and necessary
skills to keep the project going. At this point, only one member of the
PMC has stated that they would be prepared to continue. Three others have
indicated that they are in favour of moving to the attic.

An alternative suggestion for further development to continue by moving
away from Trac as the basis for the project was raised. This was suggested
to be a radical departure from the work of Bloodhound that, if there was
interest in that direction, it could be done outside of the ASF.

Discussion having died down on the above topic, there will shortly be a
formal vote on the motion to move to the attic which will take place on
the private mailing list.

16 Mar 2016 [Gary Martin / Shane]

No report was submitted.

@Shane: pursue a report for Bloodhound

20 Jan 2016 [Gary Martin / Shane]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

There are no issues requiring board attention at the current time.

Releases
========

There have been no releases over the last three months. The last release
was in fact towards the end of last year:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last additions
in January 2014.

The last new committers were added in May 2014.

Community & Development
=======================

Committer activity is extremely low, as evidence from email lists show.
For this to be addressed, we need a concerted effort to get committers
talking on the dev list again to see who has time to help progress the
project and build enthusiasm for continuing.

Recent developments do include a prospective GSoC student enquiring as
to whether we would be a suitable project which is fantastic. It is not
clear whether we would be suitable for such a scheme this year but the
project chair has indicated that he would make time to mentor a student if
it were deemed appropriate. In particular this should require a backup
mentor from the PMC to ensure any student project is given appropriate
attention. A decision on this from the PMC is required in a short time to
avoid prejudicing the enquiring student's chances of finding another
project.

16 Dec 2015 [Gary Martin / Jim]

No report was submitted.

21 Oct 2015 [Gary Martin / Brett]

Project Description
===================

Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing

Issues
======

There are no issues requiring board attention at the current time.

Releases
========

There have been no releases over the last three months. The last release
was in fact towards the end of last year:

 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project with the last additions
in January 2014.

The last new committers were added in May 2014.

Community & Development
=======================

Committer activity remains stubbornly low. Email discussions related to
tickets deemed necessary for the next release continued along with some
discussions of plans for future developments. This resulted in two of
our GSoC students responding indicating an interest in helping out.

Such GSoC students in the short term might be considered the best source
for new additions to the PMC. The current low activity should be thought
of as counter-productive to encouraging the GSoC students' interest and
more generally is a barrier to interest from new developers.

There are currently 7 remaining active tickets that are incomplete and
marked to be in the next release.

Email discussions in general are still decreasing in volume though the
user list does appear to get reasonably timely responses to queries.

We have also experienced some periods of downtime on the main bloodhound
issue tracker which managed to go un-noticed for a few days. This would
have been quicker to spot with heavier use from the developer community
but also points at the need to improve our site monitoring.

16 Sep 2015 [Gary Martin / Shane]

No report was submitted.

@Shane: pursue a report for Bloodhound

15 Jul 2015 [Gary Martin / Rich]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues requiring board attention at the current time.

Releases
========
There has no release over the last three months. The last releases
were:

 * apache-bloodhound-0.6 (16th July 2013)
 * apache-bloodhound-0.7 (23rd August 2013)
 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project.
 * PMC members:
   * Last additions were in January 2014.
   * No further changes since last report.

The last new committers were added in May 2014 for the GSoC scheme.

Community & Development
=======================

Committer activity has remained low and so progress towards the next release
remains slow. Recent emails to the Bloodhound dev list have looked to discuss
the tickets sheduled in the current milestone and tickets are in progress.

As previously reported, the INFRA ticket for the broken read-only nfs mount
of the svn repository remains incomplete, leaving Bloodhound's repository
browser out of commission.

As in other areas, progress towards upgrading the main Bloodhound issue
tracker to the newest version has also been slow. As part of this effort,
problems with the stability of the two demo sites were looked into. One of
the demos has subsequently been disabled.

The user email list activity has dropped back considerably as the effect of
the previous release properly passed by.

17 Jun 2015 [Gary Martin / Rich]

No report was submitted.

22 Apr 2015 [Gary Martin / Rich]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues requiring board attention at the current time.

Releases
========
There has no release over the last three months. The last releases
were:

 * apache-bloodhound-0.6 (16th July 2013)
 * apache-bloodhound-0.7 (23rd August 2013)
 * apache-bloodhound-0.8 (11th December 2014)

PMC/Committer Changes
=====================

There are currently 15 PMC members on the project.
 * New PMC members:
   * Last additions were in January 2014
 * Resigning PMC members:
   * Hyrum K Wright resigned on 16th February 2015

The last new committers were added in May 2014 for the GSoC scheme.

Community & Development
=======================

Committer activity has remained low over this quarter though there have been
efforts from committers to get unstable automated builds working and we have
also been taking time to update the issue tracker to the latest version of
Bloodhound. This in particular has brought one of our original PMC members
into a position to increase his involvement in the project.

There have been a few long running INFRA tickets for work related to
Bloodhound that remain open. In particular access to a read-only nfs mount
of the bloodhound svn repository continues to be missing. However, no
attempt has been made to press for progress on this issue from the PMC.

In contrast INFRA were able to provide site monitoring for the main issue
tracker and demo sites in a reasonable time. This gives us good confidence
in the stability of the main issue tracker but appear to show that our demo
servers are struggling under their load.

Although we have been involved with GSoC for the previous two years, we did
not organise ourselves to continue for this year. It was also suggested that
we should put more effort into the integration of previous work before
considering taking on further students.

The user email list has increased in response to our release in December.
Discussions on the dev mailing list have also increased in comparison to
the previous quarter.

18 Mar 2015 [Gary Martin / Chris]

No report was submitted.

17 Dec 2014 [Gary Martin / Chris]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======
It is worth the board noting that there have been concerns raised about
the rate of development and the inability to create a release. While
there has since been a release, this is discussed below.

Releases
========
There has been one release over the last three months. The last releases
were:

 * apache-bloodhound-0.6 (16th July 2013)
 * apache-bloodhound-0.7 (23rd August 2013)
 * apache-bloodhound-0.8 (11th December 2014)

Community & Development
=======================
No new committee members have been added this quarter. The last new
committee members to be added joined in January 2014. The last new
committers were added in May 2014 for the GSoC scheme.

Concerns have been raised on the private list about the rate of
development to the extent of a suggestion of moving the project to the
attic. This has not resulted in any great response but the reasons for
this are not clear. However, one outcome from this suggestion was that
a release was finally created and the vote passed smoothly.

It was also good to see demonstrations of continued interest from some
of the GSoC students.

It is clear that the rate of development has to increase again. Given
the recent progress, the situation will hopefully become clearer over
the next three to six months.

17 Sep 2014 [Gary Martin / Jim]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======
There are no issues that we believe currently require the board's attention.

Releases
========
There have been no releases over the last three months. The last releases
were:

 * apache-bloodhound-0.6 (16th July 2013)
 * apache-bloodhound-0.7 (23rd August 2013)

Community & Development
=======================
No new committee members have been added this quarter. The last new
committee members to be added joined in January 2013.

As mentioned in the previous report, Apache Bloodhound was involved in GSoC
for a second year, and we were able to accept three students with three
PMC members able to take on the duties of mentorship. In contrast with the
previous year where we only had one successful student, this year all of our
students were able to complete their projects successfully.

Following on from GSoC, we are beginning to look at the possible path of the
students to graduate to the PMC. Up until now we have not made any judgement
on whether the work towards GSoC is enough to warrant an automatic promotion
to the PMC.

Work towards a new release is ongoing. Currently there are no issues that
have been identified as blocking and so a candidate release is likely to be
ready for the community to vote on within a week.

In June and July we experienced some issues with the project's VMs which
appeared to be a result of the distribution upgrades that were required on
6th June. After requests to improve the puppet manifests to avoid excess
work on the main VM, the situation looks to have been resolved. However,
problems are sometimes reported with one of the two demos running on the
second VM.

18 Jun 2014 [Gary Martin / Greg]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======
There are no issues that we believe currently require the board's attention.

Releases
========
There have been no releases over the last three months. The last releases
were:

 * apache-bloodhound-0.6 (16th July 2013)
 * apache-bloodhound-0.7 (23rd August 2013)

Community & Development
=======================
No new committee members have been added this quarter. The last new
committee members to be added joined in January 2013. Unfortunately, Gavin
McDonald chose to leave the committee this month citing a lack of time for
involvment. Gavin will of course be welcomed back to the committee should
he find time again.

Bloodhound attracted a number of GSoC student applications, a number of
which were considered high enough quality to expect success. We were able
to accept three projects and, as in previous mentoring schemes, we have
voted to allow the students committer access.

Development effort has slowed of late and it is disappointing that we have
not been able to create a release in the last few months. This should be
rectified fairly shortly.

19 Mar 2014 [Gary Martin / Greg]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues that we believe currently require the board's attention.

Releases
========

There have been no releases over the last three months. The last releases
were:

* apache-bloodhound-0.6 (16th July 2013)
* apache-bloodhound-0.7 (23rd August 2013)

Preparation of a new release is expected within around a week.

Community & Development
=======================

Two new committee members have been added this quarter:

* SaintGermain (1st January 2014)
* Antony Semonella (9th January 2014)

Bloodhound is once again looking to become involved with GSoC this year and
the community has prepared a number of sample projects for students interest.
This has already seen six students discussing projects on the dev mailing
list who all seem to have been engaged with promptly in order to hold their
interest. We have three PMC members who have put themselves forward for
mentorship. This has also being used as an informal opportunity for those
mentors to discuss GSoC with local students which may benefit projects beyond
Bloodhound with potential students.

Development effort has increased again after a slow January but the mailing
list traffic has remained healthy with new contributors appearing fairly
regularly. This activity has obviously been boosted significantly by the GSoC
related discussions.

18 Dec 2013 [Gary Martin / Brett]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues that we believe currently require the board's attention.

Releases
========

There have been no releases over the last three months. The last releases
were:

* apache-bloodhound-0.6 (16th July 2013)
* apache-bloodhound-0.7 (23rd August 2013)

Community & Development
=======================

No new committee members have been added this quarter. The last addition to
the committee was on 10th April 2013.

The involvement of Bloodhound with the GSoC and ASF-ICFOSS mentoring schemes
is now complete. The GSoC student who passed the mid term review went on to
complete a successful project. There has not been much further contact from
this student after project completion at this point and so a possible invite
to join the PMC has not yet been considered. Unfortunately, the ASF-ICFOSS
student did not complete the process successfully. As in the case of the
GSoC students, we have left this student with commit access which will allow
the project to be completed if the student desires.

Over the last few months there has been an increase in contributions from
some new developers which may result in new committee members to announce in
the next report.

18 Sep 2013 [Gary Martin / Doug]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues that we believe currently require the board's attention.

Releases
========

There have been two releases over the last three months. The last releases
were:

* apache-bloodhound-0.6 (16th July 2013)
* apache-bloodhound-0.7 (23rd August 2013)

Community & Development
=======================

No new committee members have been added this quarter. The last addition to
the committee was on 10th April 2013.

Bloodhound continues to be involved with GSoC with one of the three projects
passing the mid term review. As mentioned in the June 2013 report to the
board, all the students were granted access to the Bloodhound repositories.
Although it is disappointing to see two of the projects fail, the committee
has left the associated students with committer access and have encouraged
these students to continue if they wish. This is not expected to have any
impact on their ability to join the committee in the future.

Bloodhound is also involved in the ASF-ICFOSS mentoring scheme where we have
one student. As for the GSoC scheme, we have granted this student commit
access.

19 Jun 2013 [Gary Martin / Chris]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues that we believe currently require the board's attention.

Releases
========

There have been no releases this month. The last releases were:

* apache-bloodhound-0.5.2-incubating (1st April 2013)
* apache-bloodhound-0.5.3 (15th April 2013)

A 0.6 Release is considered to be imminent but at the time of writing, there
are blocking issues.

Community & Development
=======================

No new committee members have been added this month. The last addition to
the committee was on 10th April 2013.

Bloodhound continues to be involved with GSoC and three projects have been
accepted. We anticipate granting all three GSoC project students access to
the bloodhound repositories, at least for the duration of their projects,
with the hope that they will remain involved in Bloodhound beyond the end of
these projects.

15 May 2013 [Gary Martin / Brett]

Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing.

Issues
======

There are no issues that we believe currently require the board's attention.

Releases
========

There have been no releases this month. The last releases were:

* apache-bloodhound-0.5.2-incubating (1st April 2013)
* apache-bloodhound-0.5.3 (15th April 2013)

A discussion about the next releases has recently begun.

Community & Development
=======================

No new committee members have been added this month. The last addition to
the committee was on 10th April 2013.

Bloodhound has submitted projects for GSoC and has put a good amount of
effort into encouraging prospective students to get involved and interact on
the mailing list. We appear to have four valid proposals from students.

In addition to the interesting discussions resulting from GSoC, the dev
mailing list has been very active covering a good range of topics. And we
appear to be remaining responsive to questions. Post graduation interest
appears to be ongoing with some more voices appearing on the dev list. We
have also seen bloodhound specific questions appearing on the external
trac-user mailing list. Although it is good to see interest anywhere, we
have attempted to encourage this kind of discussion to move to bloodhound
lists.

A conversation regarding a potential 1.0 release has also begun as we have
recently made very good progress on the initial aims of the project.

17 Apr 2013 [Gary Martin / Jim]

What is Bloodhound?
=========================
Apache Bloodhound is a software development collaboration tool, including issue
tracking, wiki and repository browsing.

Issues
=========================
There are no issues that need the board's attention.

Releases
=========================
There have been two releases this month:

* apache-bloodhound-0.5.2-incubating (1st April 2013)
* apache-bloodhound-0.5.3 (15th April 2013)

Community & Development
=========================
Bloodhound graduated to TLP based on a resolution passed by the board at the
meeting of 20th March 2013. Common tasks for migration to TLP have been
completed by INFRA. Updates to websites to conform to Apache standards are
ongoing.

In addition to the new committee members added at the point of graduation, one
further committee member was voted in on 10th April 2013.

Bloodhound has also submitted projects for GSoC.

20 Mar 2013

Establish the Apache Bloodhound Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to a software development collaboration
 tool, including issue tracking, wiki and repository browsing.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Bloodhound Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Bloodhound Project be and hereby is
 responsible for the creation and maintenance of software
 related to a software development collaboration tool, including
 issue tracking, wiki and repository browsing; and be it further

 RESOLVED, that the office of "Vice President, Apache Bloodhound"
 be and hereby is created, the person holding such office to serve
 at the direction of the Board of Directors as the chair of the
 Apache Bloodhound Project, and to have primary responsibility
 for management of the projects within the scope of responsibility
 of the Apache Bloodhound Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Bloodhound Project:

   * Mat Booth <mbooth@apache.org>
   * Matevž Bradač <matevz@apache.org>
   * John Chambers <chambej@apache.org>
   * Branko Čibej <brane@apache.org>
   * Joachim Dreimann <jdreimann@apache.org>
   * Andrej Golcov <andrej@apache.org>
   * Peter Koželj <peter@apache.org>
   * Gary Martin <gjm@apache.org>
   * Gavin McDonald <gmcdonald@apache.org>
   * Ryan Ollos <rjollos@apache.org>
   * Mark Poole <mpoole@apache.org>
   * Greg Stein <gstein@apache.org>
   * Hyrum K. Wright <hwright@apache.org>
   * Jure Žitnik <jure@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary Martin
 be appointed to the office of Vice President, Apache Bloodhound,
 to serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache Bloodhound PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Bloodhound Project; and be it further

 RESOLVED, that the Apache Bloodhound Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Bloodhound podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Bloodhound podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

 Special Order 7B, Establish the Apache Bloodhound Project, was
 approved by Unanimous Vote of the directors present.

20 Mar 2013

Bloodhound is a software development collaboration tool,
including issue tracking, wiki and repository browsing.

Bloodhound has been incubating since 2011-12-23.

The most important issue the Bloodhound community needs to address
is diversifying the community, but we believe this is no longer
any impediment to graduation.

We're hoping to graduate soon, before the next report. While
growing our community further continues to be important, we
have seen more outside interest recently. This addresses the
only barrier to graduation raised after the December2012 report.
We have further prepared by completing the PODLINGNAMESEARCH,
and just recently completed the community vote on graduation
readiness.

The project now has two online demo instances running of
Apache Bloodhound, one of which shows the current state of the
trunk branch [ http://bh-demo1.apache.org ] and providing
a first implementation of the new search functionality,
responsive layout and multi-product architecture that has
been developed. Together these represent the main strands of
what Apache Bloodhound set out to achieve. Unfortunately,
we do not yet have the ability to make use of the repository
browser, which was something that was brought up in the
previous report.

We added two new committers to the project in January, and
a fourth incubation release. We have also seen more interest
in the project from a number of channels including irc and
the dev mailing list which we are, as ever, hoping to convert
into growth of the developer community and continue to improve
upon diversity.

Signed-off-by:
Hyrum Wright: [ ](bloodhound)
Greg Stein: [ ](bloodhound)
Branko Čibej: [x](bloodhound)

P.S.: The Incubator vote to graduate Bloodhound passed on 2013-03-13.
 A resolution to establish the Apache Bloodhound TLP has been
 submitted to the Board.


Shepherd notes:

19 Dec 2012

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:

 1. Improve community diversity
 2. Growth of user community
 3. Lowering the barrier to entry and development

Since the last report, Bloodhound has successfully created two more releases.
The problems highlighted in the September report, regarding the use of an
external site for the download of some of the dependencies, have been largely
solved by working with their maintainers to ensure that their packages are
available through a standard location (pypi).

Releases themselves are beginning to become a little more routine although the
time between the initiation of the vote for release of 0.2.0 and the
subsequent announcement of the result was of concern. In contrast the 0.3.0
release was significantly smoother.

Three new committers have been added to the project and they have driven
considerable conversation on the mailing lists in a relatively short time. The
barriers to contributing have been reduced significantly and we plan to
continue to work on this area. In addition to the identification of tickets
that are suitable for newcomers we now have documentation of aspects of ticket
management and the workflow that we use. Proposals for larger enhancements are
also documented on the wiki in such a way that they reflect the decisions made
on the project dev mailing list, reducing the work associated with digging
through the mailing list.

From the infrastructure side the project has two open requests. One of these
requests was opened in July, requesting a means for the Bloodhound source
browser to have effective access to a local copy of the svn repository.
Alternatives have been suggested but there is no obvious resolution to this
issue at this point.

Signed-off-by: brane, jukka

19 Sep 2012

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:

 1. Improve community diversity
 2. Lowering the barrier to entry and development
 3. Establish a frequent release cycle

Since our last report Bloodhound has had its first release, version 0.1.0-RC1.
This was promptly followed by one external website hosting resources required
during the installation to go offline. At the time of writing this is
unresolved, although a temporary fix has been identified and suggestions for a
more permanent fix have been made.

Our project issue tracking system has now also been upgraded to this first
release of Bloodhound. Predictably the number of issues raised since has risen
significantly since as it exposed many minor shortcomings not obvious
when not used daily.

Conversations have also started on how to highlight issues that potential new
contributors would find engaging and manageable in complexity. This is mainly
to address point 2 of the issues listed above.

Signed-off-by: gstein, jukka

20 Jun 2012

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
adding 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, and should
help community diversity by increasing the exposure of the project.

Signed off by mentor: hwright, gstein
Shepherd: Dave Fisher

21 Mar 2012

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 current three most important issues toward graduation remain unchanged
from last month, and are:

 1. Improving community diversity
 2. Lowering the barrier to entry and development
 3. Creating shippable releases and getting user feedback

The last month saw the addition of one committer, Joachim Dreimann, as well
as increased technical discussion on the mailing lists, particularly around
the areas of user interface, multi-project support and rudimentary
installation capabilities. In addition, the first commits of code that
should form part of the distribution have been achieved, providing the
basis for multi-project support and a very basic installer script.

The primary goals of the community remain getting something potential
developers can play with into the repository, and creating a release to
get some widespread exposure to the project.

Signed off by mentor: hwright, gstein

15 Feb 2012

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 current three most important issues toward graduation are:

 1. Improving community diversity
 2. Lowering the barrier to entry and development
 3. Creating shippable releases and getting user feedback

We missed the report last month, largely due to inattention.  There were
a number of discussions about the relationship between Bloodhound and Trac
in early January, but those appear to have been resolved to the satisfaction
of both sets of developers and the Incubator PMC.

Since incubation some effort has gone into setting up some of our ASF
infrastructure, most notably a VM to host an instance of Trac to use for
project and issue planning.  This instance will hopefully be migrated to
Bloodhound soon, as we hope to be self-hosting.  We also have set up:

 - Mailing lists
 - Commit access for all the initial committers
 - Placeholder pages for the main website and Trac/Bloodhound front pages

The community is going through a learning process about how the ASF
functions, and how to be inclusive of the external community.  Although
most of the current developers are colocated, the mailing lists have
started to see increased activity, as the existing community learns to
work in a more open manner.  A couple of additional people have expressed
interest in participating, and are actively posting to the mailing list.
A number of mockup designs have started to flow into the repository.

The primary goals of the community include getting something potential
developers can play with into the repository, and creating a release to
get some widespread exposure to the project.

Signed off by mentor: gstein, hwright