Thanks - yes agree on all points.
-Tony
> On Feb 11, 2017, at 5:07 PM, Justin Mclean <[email protected]> wrote:
>
> Hi,
>
>> However, if someone has developed a performer, on their own would it not be
>> possible for them to contribute that to the project so that it can be
>> further developed and evolve within the Apache framework?
>
> Outside contributions like that are possible. In order to import them into
> your repo (and make them part of a release) the author(s) of the code would
> need to submit a software grant [2], an IP check on the code would be needed
> and the authors need to sign ICLAs. [2]
>
>> Of course anyone could develop a performer and make it open source on their
>> own and share it with others outside the Apache framework.
>
> Yep that also 100% fine.
>
>> Justin what would the Apache Way be? Would it be that anyone wanting to
>> contribute some pre-existing component proposes that on the distribution
>> list and a vote is taken on a per component basis?
>
> Probably no need for a vote but up to the PPMC. One of the things to be
> careful of is if the people involved are willing to continue to support the
> code at Apache.
>
>> Or would it be better to have the components exist outside the Apache
>> framework - perhaps using a standard Apache 2.0 license?
>
> This is also an option, and while we would prefer an Apache license, any
> license is possible (including a commercial one).
>
> Thanks,
> Justin
>
> 1. http://apache.org/foundation/how-it-works/legal.html#incoming-code
> 2. https://www.apache.org/licenses/icla.txt
