[OSGeoLive] [Incubator] The Open Data Cube as a OSGeo Community Project

[Jody Garnett]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20200908/811fa851/attachment.html>