Reasons for open-sourcing production code / license
MartinB
the FMX conference. One speaker (can't recall the name, he was in some
way related to http://opensourcevfx.org/) had a few good points about
why it makes sense for a studio to release it's code as open-source.
Amongst others was the idea that code has a chance to be maintained
and bugfixed continuously.
A similar introduction would probably make a lot of sense in this
forum, too, in order to motivate others to contribute?
Along those lines: I haven't read the suggested license details, but I
would like to propose considering other license models for this
repository, too. In particular, the Creative Commons license model
seems to be very reasonable and flexible (http://creativecommons.org/
choose/).
I personally am happy to share my code but currently use a license
that I call "quote ware", which requires larger productions to inform
me they use it and to allow me to cite them on this. Not everybody
complies but I find it very gratifying (and useful) to get this kind
of feedback.
Opinions?
-- MartinB
instinct-vfx
to explain opensource to descision makers to let them opensource
code. Examples of studios that do and why they do etc.
On May 27, 1:26 pm, MartinB <mbr3...@googlemail.com> wrote:
> I recently attended a panel about open-source in the VFX industry at
> the FMX conference. One speaker (can't recall the name, he was in some
Christopher Diggins
On Fri, May 27, 2011 at 7:26 AM, MartinB <mbr...@googlemail.com> wrote:
> I recently attended a panel about open-source in the VFX industry at
> the FMX conference. One speaker (can't recall the name, he was in some
> way related to http://opensourcevfx.org/) had a few good points about
> why it makes sense for a studio to release it's code as open-source.
> Amongst others was the idea that code has a chance to be maintained
> and bugfixed continuously.
>
> A similar introduction would probably make a lot of sense in this
> forum, too, in order to motivate others to contribute?
This is a good idea. I will try to write something on the Wiki when I
have time.
> Along those lines: I haven't read the suggested license details, but I
> would like to propose considering other license models for this
> repository, too.
We selected the New BSD License after careful consideration of the
different license options made available to us through Google code
hosting. By using the Google code hosting service we have to choose
one license of a small subset of OSI approved licenses
(http://code.google.com/p/support/wiki/FAQ). I feel strongly that the
New BSD License is an excellent choice.
> In particular, the Creative Commons license model
> seems to be very reasonable and flexible (http://creativecommons.org/
> choose/).
Creative commons is not recommended for use with Software (see
http://wiki.creativecommons.org/Frequently_Asked_Questions#Can_I_use_a_Creative_Commons_license_for_software.3F)
> I personally am happy to share my code but currently use a license
> that I call "quote ware", which requires larger productions to inform
> me they use it and to allow me to cite them on this. Not everybody
> complies but I find it very gratifying (and useful) to get this kind
> of feedback.
We can't modify a license (it would no longer be OSI approved, nor
approved by Google code hosting) but I think it would be a good idea
to encourage users of source code found on the community to credit the
authors. As you say it is gratifying to receive feedback and
acknowledgement that people are using your code. Would that be an
acceptable compromise?
Christopher
> Opinions?
>
> -- MartinB
Christopher Diggins
<insti...@googlemail.com> wrote:
> Definitley! Ideally such an introduction would also assist developers
> to explain opensource to descision makers to let them opensource
> code. Examples of studios that do and why they do etc.
I've written a short blurb on the Wiki:
http://code.google.com/p/3ds-max-dev/wiki/WhyYouShouldOpenSource
Cheers,
Christopher