Hi Andrea, I am not to worried about us nominating anyone for the committee that is a purely policy based. We can however tighten up that page (and should since it still mentions attending weekly IRC meetings as a requirement).
Should we make a GSIP to tighten up this page? Thanks for providing a list of examples - it was important to me (especially when looking for candidates) to emphasis that advocacy and community involvement are key - one does not have to be part of the core development group. Jody On Fri, Nov 27, 2009 at 7:35 PM, Andrea Aime <[email protected]> wrote: > Jody Garnett ha scritto: >> >> The responsibilities are listed here: >> - http://geoserver.org/display/GEOSDOC/0+Project+Steering+Committee >> - >> http://geoserver.org/display/GEOS/GSIP+1+-+Project+Steering+Committee+formation > > Imho the document is missing something crucial. > > It should state that a PSC needs to have a strong involvement in the > GeoServer community, active on the devel list, and should be doing > _something_ besides making policies. > It can be development, answering user questions, making documentation, > actively evangelizing the project, making releases, representing an > actively working group, anything that proves the person has a continued > commitment to the project. > > I don't know about others, but the idea of a PSC member as a pure policy > maker is dead wrong to me. > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
