Home opinion-and-analysis Open Sauce Canonical copyright assignment policy 'same as others'

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Canonical chief executive Mark Shuttleworth has called for an uniform copyright assignment policy for contributors to free and open source software projects.


He told iTWire that while many companies and institutions used such assignment to include contributions in projects of which they were the primary copyright owner and contributor, "they all use divergent contracts, and it would be good to standardise and harmonise those".

Shuttleworth was reacting to queries raised in connection with an article in the Linux Weekly News where editor Jon Corbet had expressed reservations about the Canonical policy. Corbet mentioned that he had asked Canonical some queries but received no answers over the course of a couple of days.

(It must be noted here that Canonical took less than three-and-half hours to provide a detailed response to iTWire's queries; the delay in publishing this article is solely because this writer was on holiday.)

Elaborating on his point, Shuttleworth said, "for example, Intel required copyright assignment for contributions to Clutter and other projects. Novell to Moblin. Red Hat has a number of contributors' agreements too. There's a long list of those agreements; a few of them are poisonous but they are the rare exception.

"The guidance at Canonical is that we encourage our employees to sign copyright assignment agreements for the projects they participate in (as far as I know we've done so for MySQL, Zope, FSF, Novell, Red Hat, Intel and others) in order to facilitate the upstreaming of their work. There are variations on the language used. Canonical's was highlighted in a recent LWN article, but I think the article created the very mistaken impression that Canonical's agreement is materially different from any of the others I've mentioned."

WEBINAR 26/27th May

Thinking of deploying Business Intelligence (BI)? So are your competitors.

And the most important, fundamental, tool for delivering your BI information to your users? Dashboards.

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect

 

 

 

 

Join the iTWire Community and be part of the latest news, invites to exclusive events, whitepapers and educational materials and oppertunities.
Why do I want to receive this daily update?
  • The latest features from iTWire
  • Free whitepaper downloads
  • Industry opportunities