Hadrian, thanks for the excellent summary.
Best,
Christian
On Fri, Sep 28, 2012 at 11:45 PM, Hadrian Zbarcea wrote:
> I though Ross was very clear in his explanation, but apparently not...
> **Unfortunately this thread (happens too often
> at the ASF) is digressing into hypothetical, vague and p
I though Ross was very clear in his explanation, but apparently not...
Unfortunately this thread (happens too often
at the ASF) is digressing into hypothetical, vague and philosophical
discussions.
Quoting Ross: "this *is* completely different". As an aside, I
personally don't consider subscr
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
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
I refer back to my original response.
apache-extras is not intended to be a way to route around legal and
community policies here at the ASF. I believe that what you propose
does just that regardless of the license choice and distribution
mechanism. You propose using ASF infrastructure for everyth
On Thu, Sep 27, 2012 at 6:41 PM, Rob Weir wrote:
>
> I think that is just engineering prudence. Take the example of a
> component that you might have a dependency. I see no problem with a
> PMC wanting to be informed about all changes to that component as well
> as all bugs found in that compon
On Thu, Sep 27, 2012 at 7:26 AM, Benson Margulies wrote:
> Perhaps I can help here.
>
> The root of all this, as I understand it, is an optional dependency.
> There is, of course, code that depends on the optional dependency.
> However, no one has mentioned any *source* code that is under an
> inc
...@opendirective.com]
Sent: Thursday, September 27, 2012 13:56
To: Dennis Hamilton; dev@community.apache.org
Subject: RE: Some clarification needed for Apache Extra projects - Apache Extra
in specific
Sent from my tablet
On Sep 27, 2012 9:51 PM, "Dennis E. Hamilton" wrote:
[ ... ]
>
I follow the exchanges with great interest.
To make a few things more clear:
- All Camel extra components are optional and we do not
deliver/release/deploy it with our normal Apache Camel releases (and we do
not plan to do this).
- As package name, we use org.apacheextras.camel.xxx
- As Maven grou
ail.com]
> Sent: Thursday, September 27, 2012 10:24
> To: dev@community.apache.org
> Subject: Re: Some clarification needed for Apache Extra projects - Apache
Extra in specific
>
> [ ... ]
>
> I'd also mention that the Apache Extras projects should not use
&
es on entities defined in an
org.apache-extras.xxx... package.
- Dennis
-Original Message-
From: Luciano Resende [mailto:luckbr1...@gmail.com]
Sent: Thursday, September 27, 2012 10:24
To: dev@community.apache.org
Subject: Re: Some clarification needed for Apache Extra projects - Apache
I'm replying to the original message as this thread seems to be taking
a different direction.
Based on the Apache Extras guidelines snippet below:
Projects hosted on Apache Extras are not considered official Apache
Software Foundation projects and they are also not associated, allied,
or otherwis
On 27.09.2012 13:26, Benson Margulies wrote:
> Perhaps I can help here.
>
> The root of all this, as I understand it, is an optional dependency.
> There is, of course, code that depends on the optional dependency.
> However, no one has mentioned any *source* code that is under an
> incompatible li
On 27.09.2012 12:34, Ross Gardler wrote:
> On 27 September 2012 11:01, "Ulrich Stärk" wrote:
>> On Thu, September 27, 2012 11:24, Ross Gardler wrote:
>>> On 27 September 2012 10:17, "Ulrich Stärk" wrote:
So an additional binary package including e.g. your Hibernate
integration
and
Perhaps I can help here.
The root of all this, as I understand it, is an optional dependency.
There is, of course, code that depends on the optional dependency.
However, no one has mentioned any *source* code that is under an
incompatible license, such as modified sources of an LGPL component.
Th
On 27 September 2012 11:01, "Ulrich Stärk" wrote:
> On Thu, September 27, 2012 11:24, Ross Gardler wrote:
>> On 27 September 2012 10:17, "Ulrich Stärk" wrote:
>>> So an additional binary package including e.g. your Hibernate
>>> integration
>>> and a separate location in SVN/GIT where users can g
On Thu, September 27, 2012 11:24, Ross Gardler wrote:
> On 27 September 2012 10:17, "Ulrich Stärk" wrote:
>> So an additional binary package including e.g. your Hibernate
>> integration
>> and a separate location in SVN/GIT where users can get the sources are
>> OK
>> IMO as long as both are not p
On 27 September 2012 10:17, "Ulrich Stärk" wrote:
> So an additional binary package including e.g. your Hibernate integration
> and a separate location in SVN/GIT where users can get the sources are OK
> IMO as long as both are not part of your official source distribution.
This is not correct. T
I agree with Ross.
In my understanding the whole issue is a non-issue anyway. See [1]. You
are very well allowed to give users instrucions on how to obtain and
install OPTIONAL components to your main product that are dependent on
software with incompatible licenses. You are just not allowed to in
As I see it the end result of the proposed activity is an Apache community
producing GPL code. Extras is not intended to be a way to route around ASF
policies relating to licence choice. It is intended to be a place for
apache related projects.
Others may see it differently.
Sent from my tablet
O
Hello!
A few day ago, I started a thread [1], mainly because we wanted to forward
our Camel Extra [2] commit and issue notifications to our regular Camel
mailing list. We had some issues with this and asked INFRA for help. Now we
realized, there are different understandings what we can do (allowed
21 matches
Mail list logo
