incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <>
Subject [DISCUSS] [VOTE] Release Apache Bloodhound 0.1.0 (incubating)
Date Tue, 07 Aug 2012 21:16:03 GMT

[branching a discuss thread]

On Tue, Aug 7, 2012 at 10:56 PM, Greg Stein <> wrote:
> As I replied to Marvin, Apache Roller had a hard dependency on
> Hibernate for some of its incubator releases. Allowing that was okay'd
> by the IPMC, VP Legal, and the Board :-)
> My view is that these are not true ASF projects, so *some* wiggle is
> allowable, especially with a plan in hand.

Note that even though podlings aren't full Apache projects yet,
incubating releases *are* official Apache releases, and should
therefore be held to a similar standard. If that standard can't easily
be reached, some podlings (like Subversion when it came in) have opted
to keep cutting non-Apache releases outside the ASF until those issues
have been resolved.

> It's certainly a subjective judgement call. I don't know where to draw
> the line, nor whether we must draw it. One of those "know it when you
> see it" things. And we have the judgement of a large body of people
> here on this list.

Personally I'm fine with things like missing license headers or
partially incomplete license metadata (which sounds like is the case
here), as long as those are just omissions that don't fundamentally
affect our rights (or those of downstream users) to distribute the
releases and as long as there's a commitment to fix such issues in
time for the next release. Such minor issues are fairly common also in
many TLPs (I've filed a number of related bugs), so it's not even a
problem that's limited just to the Incubator.

Larger issues like exceptions to documented licensing policy (like in
the examples brought up here) should always be explicitly cleared with
legal, etc.


Jukka Zitting

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message