[Embedlets-dev] Re: Licenses...

[Andrzej J. T. <an...@ch...>]

Nicola clarifies:

> Not really. Simply substitute "Apache" with the name of the copyright
> holder and the name of the project, and it's usable.
> 
> example: http://www.krysalis.org/license.html

I think this makes a lot of sense......let's use the Apache license boilerplate, 
and just change the terms to refer to our project/copyright holders.  It would 
seen to meet our needs the best, and most seem to like that license.

> But you must start first here and start growing. When there will be a
> community working on code and some initial implementations, it can be
> discussed.

I agree.....it think it's premature to approach Apache at the moment.  Let's wait 
a month or two (I doubt it will be longer than that) and have something more 
substantial to show (eg. Spec v 1.0, interface definitions, and parts of a 
container ref impl).  Then we can revisit the idea of approaching Apache.

> There is some level of politics at Apache.

I think we also need to get just a touch further down the road before we open 
the floodgates and attract the level of attention that Apache partnership would 
bring.  A small tight group is more likely to produce a good Version 1.0 
spec/impl faster than a larger group.  Think of what the embedlets discussions 
were like if we had 100 instead of a half dozen active participants.  We need to 
move fast right now to get the germ sprouted and rolling in the right direction, 
and a small tight team has a chance of pulling that off. Once the directions and 
spec are solid, then it's less likely that larger participation will slow things down 
or change the direction.  

> If you all want, I can ask informally some people there what they would
> think about it. Let's see what others think.

I think it would be better if we had more than just an "idea" before we approach 
Apache, even informally.


Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com