COmanage Developers List

[Benn Oshrin <>]

This would be fine for the dev call, or the dev list. (In general, 
always post to the list, not individuals. I've added comanage-dev as a 
cc here.)

The general convention for Cake is that Cake code goes in lib/ and your 
app's code goes in app/. Occasionally, it is useful to copy a default 
Cake file from lib to app and override it.

Cake is licensed under MIT, while I2 work is done under Apache2. MIT is 
compatible with (ie: can be incorporated into) Apache2 work.

So a file that is Apache2 licensed is our work. (I think the coding 
guidelines say what boilerplate needs to go in each file.) MIT licensed 
files in lib are Cake work. MIT licensed files in app are Cake files 
we've changed.

On 5/18/12 9:48 AM, Steve McGrath wrote:
> Hey Benno,
>
> I'm not sure whether this is a question I should be asking you or if
> it should wait for the developer call, but I'm curious how much of the
> Registry DB configuration code was written by COmanage and how much
> came directly from Cake.  A lot of the files in the Registry directory
> have the MIT license at the top and it's not clear which ones have
> been modified and which ones are just the framework.
>
> Also, are there any rules about the licenses?  I see that some files
> have the MIT license at the top, while others have the Apache license
> and a "University Corporation for Advanced Internet Development, Inc."
> there.
>
> Thanks,
>
> Steve