Bloodhound status (Was: Shepherd assignments, December 2012, first pass)

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Tue, Dec 4, 2012 at 2:20 AM, Benson Margulies <bi...@gmail.com> wrote:
> Jukka Zitting: Bloodhound

The report looks pretty good - they've added a few new committers and
cut some releases after their previous report. The report, like the
previous one, notes community diversity as the top issue, but with the
new committers in place and looking at the nicely growing commit and
list activity it seems to me as if the project is already on a good
track towards graduation.

In fact based on my brief review I don't see any notable reasons to
vote against graduation should a vote come up tomorrow, so I've
categorized the project as ready to graduate as soon as they feel
they're up to it. Mentors, please correct if needed.

The report was so far signed off by just one mentor (though I assume
Greg will review it latest when it hits board@) and there was some
delay earlier in getting their release reviewed, but apart from that
it looks like the mentors are doing a great job helping the project.

PS. It would be interesting to see a summary of how the relationship
with the Trac project played out in practice. I remember this being a
source of quite a bit of concern when Bloodhound was being proposed,
but it looks like everything has worked out fairly well. This might be
a useful example to keep in mind when similar cases come up in the
future.

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: Bloodhound status (Was: Shepherd assignments, December 2012, first pass)

[Branko Čibej <br...@apache.org>]

On 12.12.2012 03:22, Kalle Korhonen wrote:
> Also - there's a fairly new startup in San Francisco area going by the same
> name Bloodhound (see http://bloodhound.com/). I'm not associated with them,
> just happened to hear about them. It's obviously not in the same business
> but given how Apache projects have traditionally been rather cautious with
> branding and trademark conflicts, name change is perhaps something the
> project may want to consider.

This is actually ridiculous, both the name and the logo look like a
ripoff. I'm sure that site wasn't up even a few months ago; I certainly
did a bit of searching around for the use of "bloodhound" an found only
a range of blood testing medical equipment.

-- Brane


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: Bloodhound status (Was: Shepherd assignments, December 2012, first pass)

[Kalle Korhonen <ka...@gmail.com>]

Also - there's a fairly new startup in San Francisco area going by the same
name Bloodhound (see http://bloodhound.com/). I'm not associated with them,
just happened to hear about them. It's obviously not in the same business
but given how Apache projects have traditionally been rather cautious with
branding and trademark conflicts, name change is perhaps something the
project may want to consider.

Kalle


On Tue, Dec 11, 2012 at 2:21 PM, Jukka Zitting <ju...@gmail.com>wrote:

> ything has worked out fairly well. This might be
> a useful example to keep in mind when similar cases come up
>

Re: Bloodhound status (Was: Shepherd assignments, December 2012, first pass)

[Branko Čibej <br...@apache.org>]

On 11.12.2012 23:21, Jukka Zitting wrote:
> Hi,
>
> On Tue, Dec 4, 2012 at 2:20 AM, Benson Margulies <bi...@gmail.com> wrote:
>> Jukka Zitting: Bloodhound
> The report looks pretty good - they've added a few new committers and
> cut some releases after their previous report. The report, like the
> previous one, notes community diversity as the top issue, but with the
> new committers in place and looking at the nicely growing commit and
> list activity it seems to me as if the project is already on a good
> track towards graduation.

New committers are not the same as community diversity, unfortunately.
The overwhelming majority of contributors to the project are sponsored,
in one way or another, by a single commercial entity. As things
currently stand, if that entity looses interest, the project dies.

The intent is that, with announcements about frequent releases going to
(amongst other places) trac-hacks, interest will eventually bring new
blood to the project.

> In fact based on my brief review I don't see any notable reasons to
> vote against graduation should a vote come up tomorrow, so I've
> categorized the project as ready to graduate as soon as they feel
> they're up to it. Mentors, please correct if needed.

I agree, apart from the community diversity issue.

> PS. It would be interesting to see a summary of how the relationship
> with the Trac project played out in practice. I remember this being a
> source of quite a bit of concern when Bloodhound was being proposed,
> but it looks like everything has worked out fairly well. This might be
> a useful example to keep in mind when similar cases come up in the
> future.

I'm not actively involved in liaison with Trac, but I do know that the
Bloodhound community is being very careful about not stepping on any
toes, and stressing that BH is an enhancement of Trac, not a fork. For
now, I don't detect any friction between the two projects.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org