Re: Livido spec - License

>
> Hello all,
>
> After some stormy discussions on the Livido license it is time to compare
> and see what course to take.
>
> Garbriel says:
>     - put the specification document under the CC No Change license
>       because it will protect against subversioning.
>
> Jaromil says:
>     - It must be an open project , with free modification and
> participation
>       by everyone.
>
>
> I agree with Jaromil but would rather apply it only to the SDK and example
> host / plugins.
>
> Having the specification freely modifiable by everyone
> will lead to countless subversioning which leads (eventually) to
> incompatibility between the subversioned specifications.
> The problem at hand here is that backwards compatibility would not
> be able to maintain itself - A sister specification could easily
> wrap all existing Livido plugins but the new plugins conform to
> the sister specification will be incompatible with other hosts.
> I think it is clear to anyone that this leads to chaos.
>
> Basically there are thus 2 choices:
>   1. reserve all rights for modification of the specification document
>     (either by CC license or a (C) All rights reserved)
>
>   2. leave the specificiation document copyleft or in the GNU FDL
>      as a mere research project without any practical value.
>
> Looking at , for example existing open specifications (and also FreeFrame)
> we see in overal that open formats and open specification are carefully
> protected from modifications by external bodies; Usually some official
> body guards the specification and mediates towards new releases of the
> specification. However, Livido has no official body or institute that
> lies down the necessary path for maintaining such a specification.
>
> I call to a vote among Livido developers to choose which course
> to take and would like to ask the List to share their thoughts as what
> they think is the best course to take from a practical point of view.
>
> My vote will surprisingly go to option 1 since a freely changeable
> specification will have no practical value and will thus be meaningless.
>
> Hoping for your replies,
>
>   Niels
>

Naturally, I agree with Niels. The way we keep it open is by opening up
the ticket system, so that anybody can make tickets against the work in
progress, but we (original developers) have the power to close/accept the
ticket recommendations. This would be similar to the ticket system on
sourceforge, where anybody can make bug reports/requests for enhancements,
but only registered developers can close/accept the tickets.

We can also set up maybe a livido-dev mailing list, so that any changes to
tickets are forwarded to the list.

Gabriel.

_______________________________________________
piksel-dev mailing list
piksel-dev <at> bek.no
http://plot.bek.no/mailman/listinfo/piksel-dev
http://www.piksel.org