On Thu, 2009-04-16 at 12:31 +0200, Murray Cumming wrote:
> On Tue, 2009-03-31 at 17:43 +0200, Murray Cumming wrote:
> > Yeah, I would normally avoid any boring legal discussion, but I do think
> > it's a fundamental part of copyright law that you can't go to court and
> > defend a copyright if you are not the copyright holder. That concept has
> > some fancy latin name and it's lawyer 101. And a license is meaningless
> > without copyright.
> 
> I haven't seen anything that changes my mind about this. I want my code
> to be under my chosen open source license, not under public domain.
> 
> Therefore, I'll move the clutter-tutorial to GNOME's git repository and
> use GNOME's bugzilla, instead of bugzilla.openedhand.com which now asks
> patch submitters to approve that copyright waiver.

I think there has been some form of misunderstanding here; the copyright
waiver is only needed for the Clutter libraries, not - for instance -
for the tutorial.

the attachment flag on Bugzilla is entirely optional in nature;
otherwise we'd have a disclaimer saying you are waiving your copyright
when attaching a patch to Clutter core by pressing 'Submit'.

for external documentation and bindings hosted on clutter-project.org
that we don't control (e.g. the clutter-sharp bindings) we cannot ask
for a copyright waiver simply because we don't have the copyright on
thme -- the copyright of the tutorial is (C) Openismus, not (C) Intel
Corporation.

also if you don't want to waive your copyright *when contributing to
Clutter* then you can contact us and we'll start the loop with the Intel
lawyers for other copyright handling options. that's also what I wrote
in the original email.

> The openedhand developers have not made any real effort to review the
> clutter tutorial anyway, despite my efforts to make it an official part
> of clutter rather than something outside of clutter/openedhand.

I actually read the tutorial, and apart from the general "2.5D/3D" issue
that was reported, the general feeling was that the tutorial just needed
some more examples and review from third party developers. I speak for
myself, but I cannot write a decent tutorial because: a) I know how
Clutter internals work, and b) if I have to write some documentation I
prefer having it inside the API reference.

ciao,
 Emmanuele.

-- 
Emmanuele Bassi, Senior Engineer        | [email protected]
Intel Open Source Technology Center     | http://oss.intel.com

-- 
To unsubscribe send a mail to [email protected]

Reply via email to