Hahaaa! Still remember the early days of VVVV where it opened with a splash image of movie raings for ALL AGES.. how can I forget :))

Glad you brought that up, because it might need some explaining to not seem unreasonable.

intolight is a small studio and cannot approach open source in a similar way as, say intel (with opencv) or google (with go), etc. Besides our past references of our work, the only thing that will provide food into our mouths is our know-how, and hence our code. Many other studios probably agree, because a lot of brilliant vvvv patches never see the light of this website, just to protect this know-how from "being abused by other companies".

However, in good vvvv spirit we want to share this knowledge with the community of vvvv and the Domies all over the world. But this does not mean that we are cool if someone else is earning money with our work and we go hungry all the while.

So the default license is open to about everything related to Free Sharing, but it requires you to

• not earn money with it
• mention "intolight" as a base for your work
• give the same license to all published derivates of the software

I agree that this seems like a show stopper for some use cases (especially commercial ones), but mind you, this is only the default license. If you think, that your use case cannot be done within these boundaries, then simply contact the copyright holder at license (at) intolight.de and tell us about your project.

Don't worry, we will not stop you making money with the help of these patches, but we want either a slice of it or some in-kind appreciation. For a contribution to the kit we might offer you a non-transferable commercial license, for a flattr-donation you might not be required to mention us in your work, etc.

Also we want to reimburse people that have contributed with their work (vux, unc) from any revenue we generate by applying this license model.

So yeah, the default license is made for all that want to learn, teach, research, entertain or make art just for the fun of it. If your endevour is beyond that scope, simply email us and tell us about idea. We don't bite and it is our declared goal to help both the fulldome and vvvv ecosystems to prosper and flourish.

Thanks for the questions, it helps me to relate. Licensing is a touchy subject, and we should consider a different thread for discussing broader implications.

But to your questions:
I have the notion that CreativeCommons ShareAlike does not force you to publish your instrument, it only wants you to use the same CC again if you choose to give your instrument to anybody else or make a copy to someone else's system. SA pinches here: You can only give it away to all, not to just one.

What I gather from your feedback is the need for a different license for content. Maybe I can exempt the Content-Folder and open that up for anything-goes, as defined in its folder, or default to

Would that be acceptable?

And as I said before, for all the the grey areas with money or secrecy involved, just head over to license (at) intolight.de to negotiate fair terms beyond this license

mmh, not sure. the core of the dome pipeline is a cubemap texture (aka Full Sphere), and emeshe works with plain 2d textures to do its deferred shader magic. it might be possible to rewrite the shaders to use cubemaps instead, and keep using the material definitions and all the rest of emeshe.