Just a reminder, these posts are not legal advice. This site is the personal blog of Mark Radcliffe and the opinions expressed are those of Mark Radcliffe and not those of his clients, DLA Piper or the clients of DLA Piper.

About Me:

Mark Radcliffe

I have been practicing law in Silicon Valley for over thirty years assisting startups and global companies develop and market innovative products and services. I have participated in multiple business cyles in Silicon Valley from hardware to software to internet to cloud. My projects have included developing the dual licensing business model for open source startup, developing the original domain dispute resolution policy for NSI and assisting Sun in open sourcing the Solaris operating system. Recently, I served on the US Japan Innovation and Entrepreneurship Council (one of ten members) to develop a plan to encourage the innovation in Japan and the United States. I have been working with the same attorneys since 1986 although we have merged with other law firms several times. I am now a partner at DLA Piper, a (relatively) new global law firm formed in 2005 from the merger of three law firms. The firm now has 4200 lawyers in 31 countries and 77 cities. My experience in corporate securities (particularly venture capital) and intellectual property enables me to assist companies structure the financing and intellectual property strategy for developing ane exploiting a new product or service. I and my team work with fifty startups at one time as well as Global Fortune 100. I have been fortunate enough to work with companies in software, cloud computing, semiconductor, health care IT and Web 2.0.

The recent announcement about the “Openstack” product from Rackspace emphasizes the increasing importance of the cloud to the open source industry.

For the last year, I have seen an increasing number of open source issues relating to cloud computing (for a general review of cloud contracts, see my presentation as part of a panel for PLI Many of these legal issues are new; it reminds me of the legal situation in 2004 when many fundamental legal issues in open source licenses, such as the scope of the GPL and the remedies for breach of an open source license, were unsettled.  The use of open source software in the cloud raises new and difficult legal issues such as when is use in the cloud a “distribution” (which triggers obligations to make source code available in the GPL family of licenses) and what is an “aggregate” in the cloud. We had a very lively discussion about these issues at the Stanford Law School E-Commerce conference (most of these questions deal with the GPL family of licenses so the use of the Apache license by OpenStack project will avoid some of these questions). 

The obligation to provide source code under GPLv2 is based on the “distribution” of object code of the GPL Licensed Code.  The term distribution does not have a simple or obvious meaning; “distribution is defined in Section 106(3) of the Copyright Act of 1976 (“1976 Act”) as the right “to distribute copies or phonorecords of the copyrighted work to the public by sale or other transfer of ownership, or by rental, lease, or lending.” The term “public” is not separately defined in the 1976 Act but is defined by reference to “publication”.  Publication is defined as follows:  “Publication is the distribution of copies or phonorecords of a work to the public by sale or other transfer of ownership, or by rental, lease, or lending.  The offering to distribute copies or phonorecords to a group of persons for purposes of further distribution, public performance, or public display, constitutes publication.  A public performance or display of a work does not of itself constitute publication.”  Publication is a complicated concept which derives from the Copyright Act of 1909 (“1909 Act”).  Under the 1909 Act, publication without copyright notice had very significant legal consequences: it could result in the loss of all rights under the 1909 Act, placing the work in the public domain.   

Ironically, cloud computing requires us to reach back to the “limited publication” doctrine from the 1909 Act to find legal guidance for how to interpret the scope of the distribution right.  The doctrine of limited publication was created by the courts under the 1909 Act in order to avoid the forfeiture of rights under the 1909 Act through inadvertent transfer of a copy of the work without the required copyright notice.  White v. Kimmel is the seminal case for the doctrine and defines a “limited distribution” as a distribution that “communicates the contents of a [manuscript] to a definitely selected group and for a limited purpose without the right of diffusion, distribution or sale.”  White v. Kimmel, 193 F.2d 744, 746 (9th Cir. 1952).  The doctrine of limited publication continues to be viable under the 1976 Act, but it has become much less important because the use of copyright notice is now optional and the failure to include it no longer puts the work into the public domain.  The House Report of the 1976 Act defines distribution to the public as “it refers to persons under no explicit or implicit restriction with respect to disclosure of its contents.”  Cloud computing may bring new life to the “limited publication” doctrine and open source lawyers may be reading a lot of 1909 Act cases (get ready, there are more than 50 of them that are relevant and thanks to our summer associate Eduardo Blanco from Northwestern University School of Law that helped me sort through them).


  1. [...] the rest of this great post here Comments (0)    Posted in Attorney Lawyer Legal   [...]

    Pingback by Attorney, Lawyer, and Legal Information — July 30, 2010 @ 5:54 pm

  2. [...] Law & Life: Silicon Valley » Open Source in the Cloud: New Legal Questions [...]

    Pingback by Evidence Under the Rules: Text, Cases and Problems Books | The Books Stores — July 31, 2010 @ 3:44 am

RSS feed for comments on this post. TrackBack URL

Sorry, the comment form is closed at this time.