[Incubator] The Open Data Cube as a OSGeo Community Project
Alex Leith
alexgleith at gmail.com
Mon Feb 22 13:54:16 PST 2021
Hey Folks
This has been lingering for too long, so I'll just kick it a bit.
Our headers are currently:
> # This file is part of the Open Data Cube, see https://opendatacube.org
for more information
> #
> # Copyright (c) 2015-2020 ODC Contributors
> # SPDX-License-Identifier: Apache-2.0
The Copyright section is causing the inability for us to move forward, as I
understand it.
So, question. In the short term, if we removed the line about Copyright,
would be be able to proceed with coming on board as a community project?
Or are there other issues in addition?
Cheers,
On Fri, 13 Nov 2020 at 12:08, Bruce Bannerman <
bruce.bannerman.osgeo at gmail.com> wrote:
> Hi Alex,
>
> You may wish to take some legal advice on the wording of the IP assignment
> in the header.
>
> I expect that your project will have problems with such a blanket IP
> assignment.
>
> IP usually needs to be assigned to a legal entity.
>
> This will probably need some type of IP rights assignment by individual
> contributors.
>
> I expect that this will take some time to resolve, assuming that your
> project understands all of its contributors.
>
> Sorting out IP is typically a critical task that is done during the
> incubation process.
>
> Kind regards,
>
> Bruce
>
>
>
>
> On 12 Nov 2020, at 11:19, Alex Leith <alexgleith at gmail.com> wrote:
>
> Hey there Incubation List
>
> It's taken a bit of time to think through and negotiate, but our
> `datacube-core` repo now has complete license headers on all Python files.
>
> Example:
> https://github.com/opendatacube/datacube-core/blob/develop/datacube/api/core.py
> <https://github.com/opendatacube/datacube-core/blob/develop/datacube/api/core.py>
>
> The chosen header:
> # This file is part of the Open Data Cube, see https://opendatacube.org for
> more information
> #
> # Copyright (c) 2015-2020 ODC Contributors
> # SPDX-License-Identifier: Apache-2.0
>
> And we'll work through some other key repositories to add headers too.
>
> So, back to the list:
>
> 1.
>
> Be geospatial
> - Confirm by checking README or project description
> 1. Not explicit in the project README
> <https://github.com/opendatacube/datacube-core>. Very clear on
> the project webpage <https://www.opendatacube.org/>.
> - Project page on the osgeo website
> 1. https://www.osgeo.org/projects/open-data-cube/
> - We ask projects have some user documentation, for example an
> OSGeo Live quickstart
> 1. The ODC has extensive documentation
> <https://datacube-core.readthedocs.io/en/latest/>, which could
> always be better, but exist and are good. We have a backlog item to add the
> ODC to OSGeo Live project, which will include some simple documentation and
> an example implementation.
> 2. Have a free license or an open source license.
> - The license must be OSI approved
> 1. Apache 2.0 licensed
> <https://github.com/opendatacube/datacube-core/blob/develop/LICENSE>
> - We ask that the project team check the file headers and double
> check the license has been appropriately applied
> 1. File headers have been implemented on all Python files in the
> `datacube-core` project
> 3. Welcome participation and new contributors.
> - We look for a clear contribution policy
> 1. We have a CONTRIBUTORS.md
> <https://github.com/opendatacube/datacube-core/blob/develop/CONTRIBUTING.md>
> file
> - We ask that the project demonstrate collaboration, perhaps
> with a history of bug report or pull request.
> 1. We have a long history of contributions and code review on a
> number of repositories, including the core
> <https://github.com/opendatacube/datacube-core/pulls?q=is%3Apr>
> and the ows <https://github.com/opendatacube/datacube-ows>
> engine.
> - Projects are required to have a code of conduct
> 1. We have a code of conduct
> <https://github.com/opendatacube/datacube-core/blob/develop/code-of-conduct.md>
> .
>
>
> I think we tick all the boxes, so I'm submitting this as our application
> for the Open Data Cube to be recognised as an OSGeo Community Project.
>
> Kind regards,
>
> Alex Leith
>
>
>
> On Wed, 23 Sep 2020 at 09:22, Alex Leith <alexgleith at gmail.com> wrote:
>
>> Hey Folks
>>
>> Finally making some progress here.
>>
>> I'm using this tool, which works well:
>> https://github.com/johann-petrak/licenseheaders
>>
>> And I'm planning to use this text. Any issues with my proposed wording?
>>
>> #
>> # Copyright (c) 2015-2020 ODC Contributors
>> #
>> # This file is part of the Open Data Cube
>> # See https://opendatacube.org for more information
>> #
>> # SPDX-License-Identifier: Apache-2.0
>> #
>>
>> On Tue, 8 Sep 2020 at 17:20, Jody Garnett <jody.garnett at gmail.com> wrote:
>>
>>> Yeah this kind of thing can be quick (many projects keep track of code
>>> from day one) or take years (for geoserver we eventually sat down with a
>>> code sprint and git history).
>>>
>>> Here is a script I made, that produced a CSV file, that I then open up
>>> in a spreadsheet:
>>>
>>> #!/bin/bash
>>> for file in `git ls-files -x src/*`
>>> do
>>> HASH=`git log --diff-filter=A --format="%H" -- $file | tail -n 1`
>>> AUTHOR=`git show -s --format="%aN" --date=short $HASH --`
>>> CREATED=`git show -s --format="%cd" --date=short $HASH --`
>>> MODIFIED=`git log --format="%cd" --date=short -n 1 -- $file`
>>> printf "%s,%s,%s,%s,%s\n" $file "$AUTHOR" "${CREATED:0:4}"
>>> "${MODIFIED:0:4}" $HASH
>>> done
>>>
>>> Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=442206
>>>
>>> Keep in mind some of the fun of this exercise is to double check where
>>> your code actually came from and confirm you have permission to distribute
>>> it as open source. While a script can provide a running start, it is your
>>> confidence in what you have done as a team that we are really going for
>>> here :)
>>>
>>> Also note that code providence audits like this are performed when
>>> evaluating software projects for use. Performing this check yourself lowers
>>> the bar for organizations wishing to use your software.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Thu, 3 Sep 2020 at 16:56, Alex Leith <alexgleith at gmail.com> wrote:
>>>
>>>> Thanks Markus!
>>>>
>>>> I'll have a read of it, but I haven't got much experience running perl
>>>> and we are probably better off whipping up something custom.
>>>>
>>>> Always nice to see the history!
>>>>
>>>> On Fri, 4 Sep 2020 at 05:08, Markus Neteler <neteler at osgeo.org> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I searched around for a while,
>>>>>
>>>>> found
>>>>> https://wiki.osgeo.org/wiki/GRASS_Incubation_Progress
>>>>> --> https://wiki.osgeo.org/wiki/GRASS_Provenance_Review
>>>>>
>>>>> with the hint
>>>>> "Kudos to Schuyler Erle for writing the PERL script which quite helped
>>>>> (tools/copywrite.pl). The expansion of CVS names was done by reading
>>>>> in contributors.csv."
>>>>>
>>>>> and voilà:
>>>>> https://github.com/OSGeo/grass/blob/master/tools/copywrite.pl
>>>>>
>>>>> (originally added on April 27, 2006:
>>>>>
>>>>> https://github.com/OSGeo/grass-legacy/blob/develbranch_6/tools/copywrite.pl
>>>>> )
>>>>>
>>>>> Dunno if it helps in your case but nothing is lost ;-)
>>>>>
>>>>> Markus
>>>>>
>>>>> On Thu, Sep 3, 2020 at 12:38 AM Alex Leith <alexgleith at gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > I've been procrastinating on this for a long time... I will get to
>>>>> it, but if there is an existing script, that would help!
>>>>> >
>>>>> > On Thu, 3 Sep 2020 at 02:02, Markus Neteler <neteler at osgeo.org>
>>>>> wrote:
>>>>> >>
>>>>> >> Hi Alex,
>>>>> >>
>>>>> >> On Wed, Sep 2, 2020 at 12:55 AM Alex Leith <alexgleith at gmail.com>
>>>>> wrote:
>>>>> >> >
>>>>> >> > Oh nice!
>>>>> >> >
>>>>> >> > I'm working on ODC as an OSGeo project... I just need to find a
>>>>> day to add headers to all our Python files to progress to the next stage.
>>>>> >>
>>>>> >> I did much of this job back then for GRASS GIS (in 2006 or so): we
>>>>> >> used a script to generate and inject draft headers with author names
>>>>> >> extracted from the repo log.
>>>>> >> Don't know if I can still find this tool but others here may have
>>>>> done
>>>>> >> something similar.
>>>>> >>
>>>>> >> Cheers,
>>>>> >> Markus
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Alex Leith
>>>>> > m: 0419189050
>>>>>
>>>>> --
>>>>> Markus Neteler, PhD
>>>>> https://www.mundialis.de - free data with free software
>>>>> https://grass.osgeo.org
>>>>> https://courses.neteler.org/blog
>>>>>
>>>>
>>>>
>>>> --
>>>> Alex Leith
>>>> m: 0419189050
>>>> _______________________________________________
>>>> Incubator mailing list
>>>> Incubator at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/incubator
>>>
>>>
>>
>> --
>> Alex Leith
>> m: 0419189050
>>
>
>
> --
> Alex Leith
> m: 0419189050
> _______________________________________________
> Incubator mailing list
> Incubator at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/incubator
>
>
>
--
Alex Leith
m: 0419189050
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20210223/a9b32fd2/attachment-0001.html>
More information about the Incubator
mailing list