Open Stack

Colin, I guess where I'm getting a little confused is that normally 
copyright is meant to keep other people from using the content in ways 
in which you don't want them to use it.  However, by contributing their 
material to a CC or Apache-licensed guide, Aptira knows (or should know) 
that their content becomes available to anyone to use in any way they 
want to use it, though attribution must be carried through, and the 
license must be passed along.

Is Aptira under the impression that that is not the case, that they 
maintain the copyright and can stop other people/companies from using 
that material?

----  Nick

On 1/14/2014 5:28 PM, Colin McNamara wrote:
> Rich, let me take another real world use case.
>
> First, let me reiterate. Stating copyright is for the protection of the
> individual developer as well as the corporations contributing. It
> elevates visibility of how owns copyright.
>
> *Real world use case - Aptira and Training-Guides*
>
> Sean and I started a project within Docs a while back. This goals of
> this project is to provide Open Source training materials to the
> community. To achieve these goal we used a mix of content included
> within OpenStack documentation. About halfway through the effort, one of
> the guides that we used for a large amount of content got refactored,
> forcing us to pivot.
>
> Aptira had been participating significantly at that point, and had
> *contributed their own training programs to the effort. *That corporate
> contribution of significant content was key to training-guides moving
> forward. Without a clear a and concise copyright I don’t think it would
> have been possible.
>
> Either way, I feel like we are debating a philosophy point vs the legal
> question that was posed earlier. The action that comes out of this
> discussion is both guidance from the foundations legal council and the
> opportunity for someone to submit a talk exploring these items.
>
> Regards,
>
> Colin
>
> *Colin McNamara*
> People | Process | Technology
> --------------------------------------------
> *Mobile*: 858-208-8105
> *Twitter:*@colinmcnamara <http://www.twitter.com/colinmcnamara>
> *Linkedin*:www.
> <http://www.linkedin.com/colinmcnamara>linkedin.com/in/colinmcnamara
> <http://www.linkedin.com/colinmcnamara>
> *Blog*:www.colinmcnamara.com <http://www.colinmcnamara.com/>
> *Email*:colin at 2cups.com <mailto://colin@2cups.com>
>
>
>
>
>
>
>
> On Jan 14, 2014, at 1:04 PM, Rich Bowen <rbowen at redhat.com
> <mailto:rbowen at redhat.com>> wrote:
>
>> Well, as I said earlier, I believe that the spirit of the Apache
>> license is that you ALWAYS say yes, to any request to reuse, remix,
>> repurpose, re-whatever your documentation content.
>>
>> If we believe that the Apache license expresses our wishes about our
>> project, and if we understand what the license says, then we have no
>> reason ever to say no when someone asks to quote from, paraphrase, or
>> copy our docs wholesale.
>>
>> Or our source code, for that matter.
>>
>> On 01/14/2014 02:54 PM, Nermina Miller wrote:
>>> Hence my questions :) How DO you deal with such requests?
>>>
>>> On Jan 14, 2014, at 2:47 PM, Rich Bowen <rbowen at redhat.com
>>> <mailto:rbowen at redhat.com>> wrote:
>>>
>>>>
>>>> On 01/14/2014 02:41 PM, Nermina Miller wrote:
>>>>> When I worked on manuals for an international association, I used
>>>>> to check the copyright policy of each company whose material we
>>>>> used for support. They varied. In some cases, you could paraphrase,
>>>>> in some only quote. They also had specific notes you were required
>>>>> to use whether in text, footnote, or reference list. So, there are
>>>>> some specifics that are important to state for those who want to
>>>>> write tutorials, blog posts, and larger bodies of work.
>>>>
>>>> Absolutely, but I presume that none of those products were Open
>>>> Source. That changes the game.
>>>>
>>>> We're not a software company. We're an Open Source project.
>>>>
>>>> --
>>>> Rich Bowen -rbowen at redhat.com
>>>> OpenStack Community Liaison
>>>> http://openstack.redhat.com/
>>>> _______________________________________________
>>>> Openstack-docs mailing list
>>>> Openstack-docs at lists.openstack.org
>>>> <mailto:Openstack-docs at lists.openstack.org>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>
>> --
>> Rich Bowen -rbowen at redhat.com
>> OpenStack Community Liaison
>> http://openstack.redhat.com/
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> <mailto:Openstack-docs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>