RE: [Schematics-development] blueDonkey / Motorola Extensions

[Anton v. S. <an...@ap...>]

MJ Ray wrote:

> I think we will also need explicit copyright assignments or
> permissions for all non-trivial contributions if we ever hope to
> publish it as a book. Sadly, it seems logins must be required and
> also some way to trace authorship of any block.

Gordon Weakliem wrote:

> It looks like the PyCookbook figured this out after the fact:
>
> "...we wanted the recipes to be usable under any circumstances
> where Python could be used.  In other words, we wanted to ensure
> completely unfettered use... Unfortunately, the Python license
> cannot really be used to refer to anything other than Python
> itself.  As a compromise, we chose to use the modified Berkely
> license... We contacted each of the recipe authors and confirmed
> that they agreed to publish these recipes under said license."
>
> Seems like it would be better to get that out of the way up
> front, i.e. the registration process and probably part of the
> page template as well (by submitting, author agrees to following
> license <link>).

I agree.  In case anyone missed it, bluedonkey has a notice on their home
page:

"Important Note to all Contributors: All information contributed to any of
the blueDonkey.org TWiki pages becomes the property of the site's owner(s).
Should a book be accepted for publication in hard copy, contributors who
have signed their contributions will be acknowledged (please indicate in
your TWiki profile if you do not wish to be listed). blueDonkey.org's
owner(s) will be listed as editors for the book. Contributors should note
that there will be no other remuneration for their contributions here."

BTW, something like this might raise the question in some contributors'
minds of whether the "owners" could end up profiting financially from
contributions (as unlikely as that might seem), which is something we might
want to address.

> I think that registration is a very small
> obstacle and probably necessary to achieve something near press
> quality.  If someone can't be bothered to register, then they
> probably can't be bothered to put even minimal editing effort in
> either.  It's one thing to contribute code, but some level of
> exposition is required to get the point across, discuss tradeoffs, etc.

Again, I agree.

Anton