Re: [VOTE] Hide 'issues' tab in the Camel-Extra Google Project site

[Hadrian Zbarcea <hz...@gmail.com>]

Henryk, it's a legal issue and an important one. It is not arbitrary 
that ASF projects cannot use xGPL. And believe it or not, the vast 
majority of companies I interacted with do care if it's permissive 
licenses or like BSD or MIT or ALv2 or something much more restrictive 
like GPL or other licenses. It depends actually on a lot of factors.

Actually one of your responsibilities now as a Camel committer is to 
inform yourself on the nuances of oss licensing and ideally educate your 
customers as well. There are plenty here who could help.

You've got a valid point on the perception we create by hosting doc like 
camel-hibernate on the apache site. I suspect that will be removed soon. 
It should. Before that though, we should clarify what its new home 
should be.

One more thing, the ASF infra is very accommodating. They will help us 
with whatever we need... as long as it makes sense. Hosting services for 
camel-extra does not.

Cheers,
Hadrian


On 09/29/2012 04:22 PM, Henryk Konsek wrote:
>> I assume that the outcome of the discussion at [1] will be we cannot use
>> the Apache mailing list for mail notifications from Apache Extra / Camel
>> Extra.
>> I'm not sure what the outcome will be for the documentation, we already
>> have in the Apache Confluence WIKI for Camel Extra components. May be we
>> have to move it to Camel Extra. But we will wait for the final decision...
>
>  From my point of view, Camel Extra needs to be settled somewhere. At
> Apache or not at Apache.
>
> My pain about the Camel Extra is that it is not equally maintained as
> regular Camel. I endorse Camel to my clients and then I need to
> explain them why Hibernate or Db4o components are not released with
> the latest Camel. All clients/companies I worked for (including the
> one I currently work for) don't care if they use Apache or LGPL
> licensed jars. They don't get the ASF projects policies - they just
> want to use the Camel to integrate their stuff. From their point of
> view listing Hibernate component as the Camel documentation page [1]
> and then not releasing it's latest version with new version of regular
> Camel means that something is wrong with the release cycle the Camel
> itself.
>
> For me (and other Camel Extra users) the most important thing is to be
> sure that Extra releases are as reliable as Standard Camel releases.
> And are in sync with them.
>
> If ASF policy tells that Camel Extra stuff is not welcome at Apache
> infrastructure, we will use some other infrastructure. If Extra
> notifications or Jira tickets are problem for Apache infra guys -
> let's screw it and focus on the Camel Extra development itself.
>
> Have a nice weekend :) .
>
> [1] camel.apache.org/hibernate.html
>