<div dir="ltr"><div dir="ltr"><div dir="ltr">Hello Cameron:<div><br></div><div>This is a case where as a "showcase" OSGeo Project you are going to be held to a very high standard (in part because OSGeo live is often the first experience some project teams will have of working with a team that treats intellectual property seriously). Even for those of us who scoff at the idea of intellectual property - we still take communication and assent seriously as part of treating each other (and especially potential contributors) with respect.</div><div><br></div><div>My personal take - by all means keep asking for email, even if it has very little legal weight - the personal commitment behind sending that email ... is literally the outreach osgeo strives for as an organization.</div><div><br></div><div>Formally you can ask the OSGeo Board for access to legal services, the foundation has contacts and budget to support your project in this way.</div><div><br></div><div>I also note that some projects and organizations adopt an relaxed guideline for contributions that fix spelling mistakes or make some other "obvious" contribution:</div><div>- <a href="https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md">https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md</a> (see small vs large)</div><div>- <a href="https://carto.com/contributions/#obvious-fix">https://carto.com/contributions/#obvious-fix</a> (see obvious fix rule)</div><div><br></div><div>I find the carto one the most complete, but just seeing how complete they had to get makes me wonder about the effort involved. Still it is your community, perhaps some effort like this to enable drive-by contributions may be a good trade?</div><div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div></div></div></div></div></div><br><br><div class="gmail_quote"><div dir="ltr">On Mon, 24 Sep 2018 at 03:26, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><p>OSGeo Incubation committee,</p>
<p>At the OSGeoLive project, we have been debating how we
address contributor agreements.</p>
<p>It is coming to a head because we have made it easier to
contribute translations and docs (which could be as simple as
fixing a spelling mistake).</p>
<p>To date, we have been specifically asking software developers to send an email to our public email list saying something like:</p>
<p>"I want to contribute XXX to OSGeoLive. I acknowledge that my contributions will be in line with OSGeoLive's Open licenses ..."</p>
<p>We have conflicting opinions on the legal value gained by such statements, versus the overhead involved. <br>
</p>
<p>We'd be interested to hear thoughts on whether such legal protections
are still warranted in today's open source and business environment.</p>
<p>Cheers, <br>
</p>
<p>Cameron Shorter, one of the OSGeoLive committee members.<br>
</p>
<br>
<div class="gmail-m_8071141795342477999gmail-moz-cite-prefix">On 18/09/2018 12:25 AM, Nicolas
Roelandt wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Hi Cameron, all,
<div><br>
</div>
<div>Thanks for your concerns.</div>
<div><br>
</div>
<div>I agree with you we should acknowledge and
thank our contributors. <br>
</div>
</div>
<div>I checked (quickly, but as any new contributor)
some OSGeo projects which some of our members are
involved in (MapBender, MapServer, PyWPS, GeoServer)
so they can correct me if I'm wrong.</div>
<div>Not all of them required to send a mail for
licensing agreement. I noticed the case of GeoServer
where small and bigger contributions are treated
differently. [1]</div>
<div>Maybe we can copy that and only ask a mail for
big contributions.</div>
<div><br>
</div>
<div>I think the prominent statement should be in our
translation page of course, but more importantly in
a CONTRIBUTING.md file in the root folder of our
repositories like many other projects. [1][2][3][4]<br>
</div>
<div dir="ltr">
<div>I produce a basic one so we can start to work
on it, see PR #433 [5]<br>
</div>
<div><br>
</div>
<div>And in that file, propose to people to add
themselves into contributors.csv, and explain that
a mail address will be appreciated.</div>
<div>We should say that, by default, by any kind of
contribution (code PR, documentation improvement,
translations) you agree with our licensing terms
and that your OK that we will use it for
OSGeoLive.<br>
</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Nicolas<br>
</div>
<div><br>
</div>
<div>[1] <a href="https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md" target="_blank">https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md</a></div>
<div>[2] <a href="https://github.com/mapserver/mapserver/blob/branch-7-2/CONTRIBUTING.md" target="_blank">https://github.com/mapserver/mapserver/blob/branch-7-2/CONTRIBUTING.md</a></div>
<div>[3] <a href="https://github.com/mapbender/mapbender-starter/blob/release/3.0.6/CONTRIBUTING.md" target="_blank">https://github.com/mapbender/mapbender-starter/blob/release/3.0.6/CONTRIBUTING.md</a></div>
<div>[4] <a href="https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst" target="_blank">https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst</a></div>
<div>[5] <a href="https://github.com/OSGeo/OSGeoLive-doc/pull/433" target="_blank">https://github.com/OSGeo/OSGeoLive-doc/pull/433</a></div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Le ven. 14 sept. 2018 à 23:04, Cameron Shorter
<<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Nicholas,</p>
<p><br>
There are a number of points here:<br>
<br>
1. One of the OSGeo incubation criteria is that we ensure
that all contributions to OSGeo are available via our Open
Licenses. We achieve that by ensuring that every person
who contributes to OSGeo writes a public statement saying
they agree with our open license, as per:<br>
<br>
<a class="gmail-m_8071141795342477999gmail-m_-4656127677139227341m_3826277416979285945m_-5509287762926719876moz-txt-link-freetext" href="https://trac.osgeo.org/osgeolive/wiki/Source_code" target="_blank">https://trac.osgeo.org/osgeolive/wiki/Source_code</a><br>
</p>
<p>If we are to comply with our OSGeo Incubation
obligations, then we will need to extend this to
Translations.<br>
<br>
How can we ensure that anyone contributing to Transifex is
ok with our open license? Can we get them to send the same
email before we give them access? (I think we are ok if
people use an alias or git id instead of their real name.
One of our contributors is called wildintellect, and I
don't know what his/her real name is).</p>
<p>The importance of ensuring license compliance is because
lack of license compliance can become a barrier to entry
for corporations who are scared of being sued if they use
Open Source.</p>
<p>2. If someone contributes to our project, it is the right
thing for us to acknowledge them.</p>
<p>3. A good measure of OSGeoLive's success is to quote the
number of people who have contributed. Ie, it is good for
us to track number of contributors.<br>
<br>
So I suggest:<br>
* Update to note that to contribute, we will be expecting
to have your permission if we are to use your
translations. You can see email conversation last time we
were retrospectively chasing down agreements from people
for their Open Source contributions here: <a class="gmail-m_8071141795342477999gmail-m_-4656127677139227341m_3826277416979285945m_-5509287762926719876moz-txt-link-freetext" href="https://lists.osgeo.org/pipermail/osgeolive/2011-July/thread.html" target="_blank">https://lists.osgeo.org/pipermail/osgeolive/2011-July/thread.html</a>
. In particular: <a class="gmail-m_8071141795342477999gmail-m_-4656127677139227341m_3826277416979285945m_-5509287762926719876moz-txt-link-freetext" href="https://lists.osgeo.org/pipermail/osgeolive/2011-July/003686.html" target="_blank">https://lists.osgeo.org/pipermail/osgeolive/2011-July/003686.html</a></p>
<p>* We could be creative in the way that we confirm
commitment to Open licenses.</p>
<p>** Maybe insert a prominent statement in our translation
page (ideally next to the [submit] button) saying "by
submitting are are agreeing to make your content available
via our open license policy" and link to our open policy
page.</p>
<p>** Request people add their name to our list of
contributors page (not sure how we do that, but we can
work out details later)</p>
<p>Cheers, Cameron<br>
</p>
<br>
<div class="gmail-m_8071141795342477999gmail-m_-4656127677139227341m_3826277416979285945m_-5509287762926719876moz-cite-prefix">On
15/9/18 3:25 am, Vicky Vergara wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:arial,helvetica,sans-serif">Thanks
for moving the discussion to the OSGeoLive mailing
list.</div>
<div style="font-family:arial,helvetica,sans-serif">Regards<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Sep 14, 2018 at 12:33 AM Nicolas
Roelandt <<a href="mailto:roelandtn.pro@gmail.com" target="_blank">roelandtn.pro@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>I asked for a review of an announcement [1]
for our contributors and translators regarding
the new European General Data Protection
Regulation (GDPR) [2].</div>
<div><br>
</div>
<div>It was not straightforward as I thought and
it became a debate.</div>
<div><br>
</div>
<div>My mistake was not to publish the link to
the draft here, as I wanted to avoid mails
here about "Fix that, add this, ..."<br clear="all">
<div><br>
</div>
<div>I was wrong, so please next time, tell me
to bring it to the public mailing list.</div>
<div><br>
</div>
<div>The debate is not settled and was already
bring it there. We just released 12.0 so I
think we can discuss it now and have clear
policies.</div>
<div><br>
</div>
Best, </div>
<div><br>
</div>
<div>Nicolas</div>
<br>
[1] <a href="https://mensuel.framapad.org/p/osgeolive_contributor_consent_message" target="_blank">https://mensuel.framapad.org/p/osgeolive_contributor_consent_message</a><br>
</div>
<div dir="ltr">[2] <a href="https://ec.europa.eu/info/law/law-topic/data-protection_en" target="_blank">https://ec.europa.eu/info/law/law-topic/data-protection_en</a></div>
</div>
</div>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/osgeolive</a></blockquote></div></blockquote></div></blockquote></div></blockquote></div>-- <br><div dir="ltr" class="gmail-m_8071141795342477999gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div><span style="font-size:12.8px">Cameron Shorter</span><br></div><div>Technology Demystifier</div><div>Open Technologies and Geospatial Consultant</div><div><br></div><div>M +61 (0) 419 142 254</div><div><br></div></div><div><br><br></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a></blockquote></div></div></div></div></div>