[Incubator] Helping out with code/license reviews
manuel.grizonnet at cnes.fr
Fri Feb 27 06:51:48 PST 2015
Hi Landon, Johan,
just to let you know that there are ongoing development in OTB trunk
that will impact (marginally) this code review.
- We're moving the code architecture to a more modularized OTB. Most of
third parties will be handle as modules and will be used as external
dependencies and we'll minimize the number of internal libraries (no
more internal versions of openjpeg, libsvm, ossim, itk)
- In parallel to the modularization we'll clean up the list of external
dependencies not used anymore (edison, libkml...)
More info on this modularization:
There are still work to do on the modularization side but we hope to
release a new OTB 5.0 in the Spring. I Think that it will help and
facilitate to complete the work done by Johan for the OTB code review.
Note also that my employer CNES (french space agency), funded an audit
by BlackDuck for OTB about code provenance. It was more than 4 years ago
but I'll see if I could provide it to you Landon.
Regarding copyrights, we planned also to introduce also this year a
Contributor License Agreement for OTB, more info here:
Forget to add that we've got a new website with credit to OSGeo which
specify also that we've started the incubation process.
So lots of news on the OTB side but news which are going in the right
direction I think for our OSGeo incubation process.
PS: CC to otb-developers mailing list
Le 24/02/2015 08:09, Johan Van de Wauw a écrit :
> It will be a lot of work for OTB -> it is large, and contains many
> dependant libraries. We may have to limit the scope, eg check that the
> ossim directory is identical to the version of upstream and skip
> reviewing that in detail.
> I actually had a look at much of the code last year, and I documented
> some of the licenses at that point:
> It is not finished, more a draft which worked for me.
> On Mon, Feb 23, 2015 at 10:09 PM, Landon Blake
> <sunburned.surveyor at gmail.com> wrote:
>> I'm getting ready to do the Code Provenance Review for the OTB Project.
>> Would you be willing to help with that?
>> Please let me know, and I'll work with the OTB team to get something set-up
>> for you.
>> On Tue, Sep 30, 2014 at 3:41 PM, Jody Garnett <jody.garnett at gmail.com>
>>> Thanks Johan, any tool recommendations would be great.
>>> Jody Garnett
>>> On Tue, Sep 30, 2014 at 2:24 PM, Johan Van de Wauw
>>> <johan.vandewauw at gmail.com> wrote:
>>>> Hello everyone,
>>>> During recent discussions on the discussion mailing list and others I
>>>> noticed that incubation could use some help.
>>>> I have gained some experience in checking licenses when packaging for
>>>> debian (I have removed files from saga (eg ) and libharu when
>>>> packaging. Checking code for licenses became part of my second nature
>>>> (eg ).
>>>> So if there are any projects in incubation which could use some help,
>>>> I'm available to help.
>>>> It may also be worth pointing out that debian has some pretty nifty
>>>> tools such as licensecheck (in package devscripts) and some lintian
>>>> checks (when you create a package) that tend to help finding offenders
>>>> without browsing all source (which still has to be done).
>>>> Incubator mailing list
>>>> Incubator at lists.osgeo.org
>>> Incubator mailing list
>>> Incubator at lists.osgeo.org
> Incubator mailing list
> Incubator at lists.osgeo.org
More information about the Incubator