see below... ------------------------------------------------------- Ing. Simone Giannecchini GeoSolutions S.A.S. Founder - Software Engineer Via Carignoni 51 55041 Camaiore (LU) Italy
phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://simboss.blogspot.com/ http://www.linkedin.com/in/simonegiannecchini ------------------------------------------------------- On Wed, Nov 25, 2009 at 10:21 AM, Ben Caradoc-Davies <[email protected]> wrote: > On 24/11/09 19:19, Andrea Aime wrote: >> If we do proper rotation we'll >> end up being one of the two figures once every 5-10 months >> depending on the release frequency. >> If a PSC member cannot bear to donate the project maintenance >> 2-4 days every 10 months he probably has no business >> sitting in the PSC to start with. At least imho. > > I am concerned that requiring PSC members to perform releases excludes > non-developers and intermittent developers from PSC membership, even > though they might have a major contribution to make to in the standards, > usability, or documentation spaces. I am sure there are those whose > contribution to the PSC I would value, but whom I would not like making > a release. I think GSIP 43 as it stands does not require PSC members to > volunteer, and I support this position. The PSC is about governance, not > engineering work. > > Furthermore, there are competent (or at least willing) release engineers > who might not be on the PSC who should not be excluded. > Good point, I share your view Ben expecially from a company standpoint. I might want to have other people besides me and/or alessioto help with the release, like daniele or emanuele but not being PSC would prevent them from giving their contribution to the release. So I am +1 about releasing the constraint on who can actually make a release. > Should we instead have a release roster, so the position rotates? This > need not be formed from PSC members. A written roster would give advance > warning to those expected to make a release, and give confidence to > those that usually end up doing the donkey work that they will not have > to do it *every* time. Such a roster would also expand the base of those > with experience making a release. We could also have a testing roster. I > am not sure about the roadmap. > > If there is a release roster, I volunteer to be on it, as long as it is > not just me. :-) This is a good idea as well, at least as long as the rules to enter/leave the roster are clear and the permission to enter is upon PSC voting. What do the others think? Ciao, Simone. > > -- > Ben Caradoc-Davies <[email protected]> > Software Engineer, CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre > 26 Dick Perry Ave, Kensington WA 6151, Australia > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
