Jody,

by no response do you mean no response to the budget request? 

GRASS has been preparing the request (I am on PSC) and I asked the PSC to 
submit the request - if it has not come yet, I can submit it - the draft budget 
is here
https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2019#Planned_Expenses

we have a larger than usual item there - we need help to cover the cost of 
GRASS website update,
so we had some discussion about doing some fundraising to help out with that so 
that might have caused the delay. I can put the request on the board budget 
wiki if there are no objections from the rest of GRASS PSC,

Helena



> On Jan 19, 2019, at 5:31 PM, Jody Garnett <[email protected]> wrote:
> 
> Going to share this here as one of our responsibility is to check-in with 
> projects.
> 
> Here are notes from todo activity 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
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/board

Helena Mitasova
Professor at the Department of Marine, 
Earth, and Atmospheric Sciences
Associate director and faculty fellow at the Center for Geospatial Analytics
North Carolina State University
Raleigh, NC 27695-8208
[email protected]

"All electronic mail messages in connection with State business which are sent 
to or received by this account are subject to the NC Public Records Law and may 
be disclosed to third parties.” 

_______________________________________________
grass-psc mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-psc

Reply via email to