[Pywps-dev] OSGeo incubation update
Tom Kralidis
tomkralidis at gmail.com
Sat Sep 10 13:39:44 PDT 2016
Thanks very much Luís. FYI I've started the provenance page setup at [1]. Upon
some clarification/guidance from the OSGeo Incubation Committee [2],
I'll send an update to the list on provenance way forward.
Thanks
..Tom
[1] https://github.com/geopython/pywps/wiki/ProjectProvenanceReview
[2] http://lists.osgeo.org/pipermail/incubator/2016-September/003152.html
On Thu, Sep 1, 2016 at 3:57 PM, Luís de Sousa
<luis.de.sousa at protonmail.ch> wrote:
> Hi there Tom, if I can help in any way with the code provenance please let
> me know. Cheers,
>
> Luís
>
>
> -------- Original Message --------
> Subject: [Pywps-dev] OSGeo incubation update
> Local Time: September 1, 2016 2:28 PM
> UTC Time: September 1, 2016 12:28 PM
> From: tomkralidis at gmail.com
> To: pywps-dev at lists.osgeo.org <pywps-dev at lists.osgeo.org>
>
> Hi all: great to see so much action around PyWPS in the
> last weeks -- great work all!
>
> I'd like to provide an update on our OSGeo incubation [1] path
> and way forward. We've made great strides:
>
> - including inclusion into OSGeo-Live, which will yield significant benefits
> over time especially as we move to PyWPS 4.0
> - we have a PSC and an RFC framework
> - we are moving towards OGC compliance with http://demo.pywps.org as a
> deployed instance; this will also put us in a great position to make PyWPS
> an official OGC Reference Implementation
>
> A full list of OSGeo incubation related progress is available at [2].
>
> Having said this, I think we are close to proposing PyWPS becoming an OSGeo
> project with remaining tasks in [3], namely:
>
> - code provenance review [4], we need a scan of all Python files to
> ensure (using 3.2.5)
> - project graduation checklist; I've started a draft in [5] which needs
> input and polishing off
> - contributor and license agreements [6]; we've done a good job
> at capturing most CLAs here. I think this is good enough for moving
> ahead at this point
> - clarify contributors: once we discuss/decide copyright transfer (or not)
> we can call this done
>
> Once the above items are in good order I'd like to propose PyWPS
> for graduation. The meat of the work here is the code provenance. IMHO
> I think a 1 hour sprint on IRC can help move this item into completion.
>
> Comments/thoughts/suggestions?
>
> Thanks
>
> ..Tom
>
> [1] https://github.com/geopython/pywps/wiki/OSGeoIncubation
> [2]
> https://github.com/geopython/pywps/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3A%22OSGeo%20Incubation%22%20
> [3]
> https://github.com/geopython/pywps/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22OSGeo%20Incubation%22%20
> [4] https://github.com/geopython/pywps/issues/130
> [5] https://github.com/geopython/pywps/wiki/ProjectGraduationChecklist
> [6] https://github.com/geopython/pywps/issues/124
> [7] https://github.com/geopython/pywps/issues/84
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pywps-dev
>
>
More information about the pywps-dev
mailing list