<div dir="ltr"><div dir="ltr">Hey Alex,<div>I've just been sitting in on the osgeolive fortnightly meeting. opendatacube was getting discussed.</div><div><a href="http://irclogs.geoapt.com/osgeolive/%23osgeolive.2020-09-01.log">http://irclogs.geoapt.com/osgeolive/%23osgeolive.2020-09-01.log</a></div><div>Projects which are to be included on the next OSGeoLive release are getting worked out now. It would be great to see opendatacube included.</div><div><br></div><div><table style="color:rgb(0,0,0);font-family:Tinos;font-size:16px"><tbody><tr><td valign="top">19:59:38</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">darkblue_b:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">opendatacube AU is enthusiastic last week</td></tr><tr><td valign="top">19:59:41</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">kalxas:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">motion to include them in the next version</td></tr><tr><td valign="top">20:00:01</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">kalxas:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">darkblue_b, yes I have reached out to them months ago to become Community Project<br></td></tr></tbody></table></div></div><div><table style="color:rgb(0,0,0);font-family:Tinos;font-size:16px"><tbody><tr><td valign="top">20:05:21</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">cameronshorter:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">I can vouch for the people behind Datacube. Alex is very active in the Australian OSGeo community. And the project comes out of combined government/university and has great roots.</td></tr><tr><td valign="top">20:05:23</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">darkblue_b:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">phma we can chat about this</td></tr><tr><td valign="top">20:05:33</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">kalxas:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">phma, we can help in chat outside the meeting</td></tr><tr><td valign="top">20:05:34</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">phma:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">ok</td></tr><tr><td valign="top">20:05:50</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">kalxas:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">cameronshorter, push them to apply :)</td></tr></tbody></table></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 16 May 2020 at 07:29, Alex Leith <<a href="mailto:alexgleith@gmail.com">alexgleith@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hey Jody and others<div><br></div><div>I work at Geoscience Australia, and Kirill is on my team. Most of the contributions to the ODC Core codebase are from GA, though there some minor contributions from external individuals and some significant work from CSIRO.</div><div><br></div><div>We talked about the code headers and the team in GA feel confident that there is no significant code in there that is not original to the ODC, which is one of the reasons for auditing and adding headers, as I understand it.</div><div><br></div><div>I think we'll write some script that goes and adds Even's suggested addition into all the appreciate files. I'll report back when we've merged that in, which will be soonish!</div><div><br></div><div>Thanks again for your support here.</div><div><br></div><div>Cheers,</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 15 May 2020 at 21:48, Angelos Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>Big +1 to have opendatacube onboard.<br>
<br>
On 5/15/20 9:02 AM, Jody Garnett wrote:<br>
</div>
<blockquote type="cite">
<pre>I went back to check the website (<a href="https://www.opendatacube.org" target="_blank">https://www.opendatacube.org</a>) to see who
is actually distributing opendatacube. This really is a great example of
open source being used as the glue to bind a partner ship of a wide range
of organizations. In this case I assume the players (Geoscience Australia,
NASA, CSIRO, USGS,Catapult,Analytical Mechanics Associates) are putting in
work, which is distributed by a public repository (
<a href="https://github.com/opendatacube" target="_blank">https://github.com/opendatacube</a>).
1. Checking the history of a random file
<a href="https://github.com/opendatacube/datacube-core/commits/develop/datacube/model/__init__.py" target="_blank"><https://github.com/opendatacube/datacube-core/commits/develop/datacube/model/__init__.py></a>
shows
it was created by Kirill888 <a href="https://github.com/Kirill888" target="_blank"><https://github.com/Kirill888></a> from Canberra
Australia.
2. That is a unique name so I have a good chance of finding him on LinkedIn
krill-kouzoubov <a href="https://www.linkedin.com/in/kirill-kouzoubov/" target="_blank"><https://www.linkedin.com/in/kirill-kouzoubov/></a>
3. LinkedIn shows his employer is Geoscience Australia
4. If I assume he is operating as an employee, and not as an individual,
GeoScience Australia the legal entity distributing at least part of
<a href="http://opendatacube.org" target="_blank">opendatacube.org</a> as open source.
I think if I find another file we could find a different organization; this
really is a shared work.
Notes:
- The kind of research I just did above is a bother, one of the things we
are addressing here is getting that detail out of the way so that any
potential user or contributor the the project can tell who they are working
with (and evaluate risk accordingly).
- This kind of thing where multiple organizations are distributing a shared
work are exactly where an open source foundation like OSGeo thrive. In some
cases groups find it easier to use a CLA to donate the code to OSGeo which
operates as neutral party to distribute the code. OSGeo is willing to do
so, but asks that the project set up a committee (usually with
representation from the different partners) to manage things.
I am really impressed with opendatacube, if you are happy using Even
Rouault's approach you should run with it. The other questions you can save
for later in your open source journey.
--
Jody Garnett
On Thu, 7 May 2020 at 15:23, Jody Garnett <a href="mailto:jody.garnett@gmail.com" target="_blank"><jody.garnett@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>Still that is the subject under discussion:
- confirmation that this is open source, and which license?
- are we sure it is open source?
- really? Who wrote this - and did they (or their employer) understand it
was being released as open source
Copyright is a slightly different topic, it is a great tool for enforcing
the open source license :)
For a community project we ask folks spot check their headers (which
catches many of the above questions). For incubation was ask projects dig
into the history a bit and confirm the providence of the code (where it
came from).
--
Jody Garnett
On Thu, 7 May 2020 at 14:28, Alex Leith <a href="mailto:alexgleith@gmail.com" target="_blank"><alexgleith@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>person or organisation responsible
</pre>
</blockquote>
<pre>Responsible for distribution of the file?
If that's it, I guess I need to go digging for some further examples.
Because as I said earlier, we don't have a formal ODC organisation. I could
check into whether Geoscience Australia could be that org, but I'm not sure
that it should.
And I really hope you're not talking responsible for holding copyright,
because that's a far more complex issue!
On Thu, 7 May 2020 at 23:21, Jody Garnett <a href="mailto:jody.garnett@gmail.com" target="_blank"><jody.garnett@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>This discussion, and your projects decision on how to open source, is
why we have this check list.
It is minimal, the part that is weak is noting the person or
organization responsible. Headers with such information can help when doing
a providence review (where the code came from), but git history even better
:)
So back at you - what is appropriate for your project? And do you find
any odd files when checking your headers? Most projects do...
On Wed, May 6, 2020 at 6:53 PM Alex Leith <a href="mailto:alexgleith@gmail.com" target="_blank"><alexgleith@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>Thanks Even, that looks like a really simple solution!
Does anyone see any issues with Even's proposed approach?
On Thu, 7 May 2020 at 09:22, Even Rouault <a href="mailto:even.rouault@spatialys.com" target="_blank"><even.rouault@spatialys.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre>On jeudi 7 mai 2020 09:09:01 CEST Alex Leith wrote:
</pre>
<blockquote type="cite">
<pre>Hey Jody
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre></pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>Thanks for the advice.
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre></pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>We had a look at the Apache license documentation and it says:
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>Each original source document (code and documentation, but not the
</pre>
</blockquote>
</blockquote>
<pre>LICENSE
</pre>
<blockquote type="cite">
<pre></pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>and NOTICE files) *should* include a short license header
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre><a href="https://infra.apache.org/apply-license.html#new" target="_blank">https://infra.apache.org/apply-license.html#new</a>
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre></pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>Does the OSGeo Project process require the license to be in headers,
</pre>
</blockquote>
<pre>or
</pre>
<blockquote type="cite">
<pre>simply encourage?
</pre>
</blockquote>
<pre>Not speaking on behalf of OSGeo, but I'd suggest using the the
one-line variant offered by the SPDX initiative, which is adopted by the
Linux Kernel project among others, and has the advantage of conveying
explicit non-ambiguous licensing in a short way, and to be easily analyzed
by automated tools (compliance checking). Just put the following at the
beginning of files (way of commenting to be adopted with the one offered by
the programming language)
// SPDX-License-Identifier: Apache-2.0
See <a href="https://spdx.org/ids-how" target="_blank">https://spdx.org/ids-how</a>
--
Spatialys - Geospatial professional services
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
</pre>
</blockquote>
<pre>--
Alex Leith
m: 0419189050
</pre>
</blockquote>
<pre>--
--
Jody Garnett
</pre>
</blockquote>
<pre>--
Alex Leith
m: 0419189050
</pre>
</blockquote>
<pre></pre>
</blockquote>
<pre></pre>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Incubator mailing list
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a></pre>
</blockquote>
<br>
<br>
<pre cols="72">--
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
<a href="http://users.ntua.gr/tzotsos" target="_blank">http://users.ntua.gr/tzotsos</a></pre>
</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><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div>Alex Leith<br></div>m: 0419189050</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><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><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>Technical Writer, Google</div></div><div><br><br></div></div></div></div></div></div></div></div></div></div></div></div>