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
On Sep 26, 2012 10:07 PM, "Christian Müller" <christian.muel...@gmail.com>
wrote:

> 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 to do)
> and what not. I didn't found an answer at [3] or [4]. I want clarification
> about the following question:
>
> - Is it inline with the Apache policy to forward commit notifications from
> Apache Extra projects to the regular Apache project mailing list (INFRA
> managed)?
>
> - Is it inline with the Apache policy to forward issue notifications from
> Apache Extra issue tracker (Google code) to the regular Apache project
> mailing list (INFRA managed)?
>
> - Is it inline with the Apache policy to direct users from Apache Extra to
> raise issues at the regular Apache issue tracker (JIRA)?
>
> - Is it inline with the Apache policy to host content on Apache Confluence
> which covers Apache Extra artifacts  (e.g.
> http://camel.apache.org/hibernate.html)?
>
> [1]
>
> http://camel.465427.n5.nabble.com/Re-Apache-Extras-notifications-was-Disable-GitHub-commenting-httpd-td5719778.html
> [2] http://code.google.com/a/apache-extras.org/p/camel-extra/
> [3]
>
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches
> [4] http://community.apache.org/apache-extras/guidelines.html
>
> Thanks in advance,
> Christian
>
> --
>

Reply via email to