[Board] quick project status check and response to budget inquiry

[Angelos Tzotsos]

Hi Jody,

Sorry I did not find time to communicate this, but I have been reaching 
out to project officers asking for action/reports.
Regarding the projects I represent, we are about to report back.

Cheers,
Angelos

On 1/20/19 3:07 AM, Jody Garnett wrote:
> Quick thanks to Angelos for the initial emails to the project list.
>
> Going to try and reach out to officers individually (using officers list
> <https://www.osgeo.org/about/board/> and contacts
> <https://wiki.osgeo.org/wiki/Contacts> wiki as required so sometimes two
> names are listed):
>
> - deegree:  Markus Schneider or Jens Fitzke
> - FDO + MapGuide Open Source: Jackie Ng
> - geomajas: Pieter De Graef
> - GeoMOOSE: Bob and Brian
> - GeoNetwork: Jeroen
> - GeoNode: Jeffrey
> - GEOS: Sandro
> - Mapbender: Astrid and Olaf (project needs a new officer)
> - MapFish: Eric Lemoine
> - MapServer: Steve Lime
> - Marble: Torsten
> - OpenLayers: Bart and Tim
> - OSSIM: Mark and Garrett
> - PostGIS: Paul (there was an entry in the code-sprint section that can
> probably be moved)
> - pycsw: Angelos <-- did not reply to his own email :)
> - OSGeoLive: Angelos <-- still not replying to his own email
>
> For the projects that appear inactive I included an invitation to scale
> back to OSGeo community program.
>
> Thanks to all the projects that have responded, and a tip of the hat to
> gvSIG (we have been using your budget as an example).
> --
> Jody Garnett
>
>
> On Sat, 19 Jan 2019 at 14:31, Jody Garnett <jody.garnett at gmail.com> wrote:
>
>> Going to share this here as one of our responsibility is to check-in with
>> projects.
>>
>> Here are notes from todo activity
>> <https://git.osgeo.org/gitea/osgeo/todo/issues/29> contacting projects
>>
>>
>>     - deegree: active codebase, no response
>>     - FDO: active codebase, PSC inactive (consider as *community project?*)
>>     - GDAL/OGR: *responded*
>>     - geomajas: last activity august 2018
>>     - GeoMOOSE: very active, no response
>>     - GeoNetwork: very active, no response
>>     - GeoNode: active, no response
>>     - GEOS: active, no response
>>     - GeoServer: *responded*
>>     - GeoTools: *responded*
>>     - GRASS: activer, no response
>>     - gvSIG: actually responded with a budget!
>>     - Mapbender: active codebase, no response
>>     - MapFish: website and latest release from 2011, consider as *community
>>     project?*)
>>     - MapGuide Open Source: PSC inactive, consider as *community project?*
>>     - MapServer: active codebase, no response
>>     - Marble: active codebase, no response
>>     - OpenLayers: active codebase, no response
>>     - OSSIM: active codebase, no budget response
>>     - PostGIS: activer codebase, no response
>>     - pycsw: active codebase, no response
>>     - QGIS: *responded*
>>     - OSGeoLive: last commit in September, discussion on mailing list but
>>     no response yet
>>
>>
>> Unless anyone has any objects I would like to discuss treating FDO,
>> MapFish, MapGuide Open Source as community projects for the 2019 budget.
>> This allows the us to fund projects like MapGuide Open Source while
>> acknowledging that they no meet as a committee. Should any of these
>> projects step up in activity it should be easy for them to go through
>> incubation as their procedures are already in place.
>>
>> We may also wish to speak with the QGIS PSC about QGIS Server being listed
>> as a community project. This would allow us a way to thread the needle
>> between QGIS being graduated and the QGIS team adding and additional
>> project which is not yet part of OSGeo.
>> --
>> Jody Garnett
>>
>
> _______________________________________________
> Board mailing list
> Board at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board


-- 
Angelos Tzotsos, PhD
Charter Member
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20190120/6c2579c6/attachment.htm>