community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Some clarification needed for Apache Extra projects - Apache Extra in specific
Date Fri, 28 Sep 2012 19:44:59 GMT
On Fri, Sep 28, 2012 at 4:13 AM, Ross Gardler
<> wrote:
> On 28 September 2012 02:41, Rob Weir <> wrote:
> ...
>> Specific example.  OpenOffice podling has signed up for a security
>> mailing list where we receive security-related bug reports from
>> LibreOffice, an open source project that is LGPL/MPL, not ALv2.  We do
>> this by subscribing our security list directly to theirs.  Is this
>> against policy?   This seems directly analogous to a project receiving
>> bug reports from a non ALv2 Apache Extras project.
> This is completely different. LibreOffice is a separate project with a
> separate infrastructure and community. The subscription of an ASF list
> to a LibreOffice list is nothing more than a communication link
> between two distinct entities. The proposal here is to not create a
> separate project with a separate management structure but to simply
> host incompatible code externally and manage it from within an ASF
> PMC.

Exactly my point.  To the question put earlier:

 "whether mailing list connections and other conveniences would create
unacceptable confusion
about the distinction between 'things the PMC does' and 'things some
PMC members happen to do elsewhere.'"

IMHO, the mailing list connections are not the issue.  The issue is
the relationship between the Apache Extras project and the Apache
projects.  If the relationship is improper, from a control and
dependency perspective, then that is the problem.  The mailing list
use connection does not create the problem.  And I suspect that
avoiding the mailing list connections would change nothing fundamental
if there were a control and dependency issue.



> Ross
> --
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective

View raw message