The Apache Software Foundation
The Apache Software Foundation Incubator

Bloodhound Project Incubation Status

This page tracks the project status, incubator-wise. For more general project status, look on the project website.

The Bloodhound project graduated on 2013-03-20


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


  • 2013-03-20 Apache Bloodhound graduates from the Incubator.
  • 2013-03-13 Resolution to establish Apache Bloodhound TLP submitted to the Board.
  • 2013-03-13 Incubator PMC votes for graduation.
  • 2013-03-06 Community votes for graduation.
  • 2013-01-28 Version 0.4 (incubating) released.
  • 2013-01-24 New committer: Matevž Bradač.
  • 2013-01-24 New committer: Andrej Golcov.
  • 2013-01-09 Bloodhound extends commit bit to all ASF committers.
  • 2012-12-04 Version 0.3 (incubating) released.
  • 2012-11-26 New committer: Ryan Ollos.
  • 2012-11-23 New committer: Jure Žitnik.
  • 2012-11-23 New committer: Peter Koželj.
  • 2012-11-15 Version 0.2 (incubating) released.
  • 2012-09-18 New committer: Joachim Dreimann.
  • 2012-09-14 Version 0.1.0 (incubating) released.
  • 2012-02-01 Self-hosting at
  • 2011-12-23 Project enters incubation.

Project info

item type reference link
Website www
Mailing list dev archive
  user archive
  commits archive
Bug tracking
Source code SVN
Mentors hwright Hyrum K. Wright
  gstein Greg Stein
  brane Branko Čibej
PPMC mbooth Mat Booth
  chambej John Chambers
  gjm Gary Martin
  gmcdonald Gavin McDonald
  mpoole Mark Poole
  hwright Hyrum Wright
Committers jdreimann Joachim Dreimann
  jure Jure Žitnik
  peter Peter Koželj
  rjollos Ryan Ollos
  matevz Matevž Bradač
  andrej Andrej Golcov

Incubation status reports

Incubation work items

Project Setup

This is the first phase on incubation, needed to start the project at Apache.

Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the project to be incubated

date item
2013-02-07 Make sure that the requested project name does not already exist and check to be sure that the name is not already trademarked for an existing software product.
N/A If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.
N/A If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
DONE If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.


date item
2012-01-10 Ask infrastructure to create source repository modules and grant the committers karma.
2011-12-28 Ask infrastructure to set up and archive mailing lists.
2012-01-12 Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
2012-01-12 Ask infrastructure to set up self-hosting environment (A VM or Jail).
2012-01-10 Migrate the project to our infrastructure.

Mentor-related responsibility/oversight

date item
2011-12-29 Identify all the Mentors for the incubation, by asking all that can be Mentors.
DONE Subscribe all Mentors on the pmc private and general lists.
2012-01-10 Give all Mentors access to the incubator SVN repository. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file)
2011-12-29 Tell Mentors to track progress in the file 'incubator/content/projects/{}.xml'
date item
N/A Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
N/A Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

date item
DONE Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
DONE Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Establish a list of active committers

date item
DONE Check that all active committers have submitted a contributors agreement.
DONE Ask root for the creation of committers' accounts on

Project specific

Add project specific tasks here.


These action items have to be checked for during the whole incubation process.

These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
  • Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.)
  • Are project decisions being made in public by the committers?
  • Are the decision-making guidelines published and agreed to by all of the committers?

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?

Project Specific

Add project specific tasks here.


Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • If graduating to an existing PMC, has the PMC voted to accept it?
  • If graduating to a new PMC, has the board voted to accept it?

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks?