[Marketing] contract review, need to approve and sign .. now?

[Jody Garnett]

It was a subtle difference - they were clear we own all work produced
during the project.

The clarification is needed for prior IP they bring to the party. One of
the reasons to go with a company that does this for a living is they bring
IP and experience to the party.

I just want to double check that their IP (even if we have an unlimited
license) does not end up anywhere in the themes produced; since we intend
to share them with our sub-brands: geoforall.org, live.osgeo.org, etc...

The specific conflict is live.osgeo.org which is an LGPL project on GitHub:
https://github.com/OSGeo/OSGeoLive-doc

(Cameron can I ask you to stick a LICENSE.txt file on that github :P )

--
Jody Garnett

On 24 March 2017 at 12:04, Jeffrey Johnson <ortelius at gmail.com> wrote:

> This definitely needs to be clarified. OSGeo will *own* all work
> products generated under this project and it alone has the authority
> to set the license under which they are distributed. I believe we
> should use the appropriate cc licenses, but this is our decision as an
> organization, not the vendors.
>
> On Thu, Mar 23, 2017 at 11:42 PM, Jody Garnett <jody.garnett at gmail.com>
> wrote:
> > In case it was not obvious this is my hesitation:
> >
> >> - [ ] work prior/seperate to this project --> osgeo gets an unlimited
> >> license (we need to make sure they understand that the graphical look
> will
> >> end up in open source projects and we cannot have a license conflict)
> >
> >
> > We do intend to take generated design and use it across our product line
> for
> > projects such as OSGeo Live (which are distributed under an open source
> > license).
> >
> > _______________________________________________
> > Marketing mailing list
> > Marketing at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/marketing
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/marketing/attachments/20170324/1b505620/attachment.html>