[mapserver-dev] RFC 7.2 voting implications

[Daniel Morissette]

Same here: a regular vote on the RFC should be fine, and getting all 
committers to reconfirm their agreement can't hurt. That may be a good 
way to retire a few who are no longer active (i.e. if they do not 
confirm their agreement to RFC 7.2 then we put their commit rights on 
hold and mark them as retired in the commiters file)

On 12-10-05 9:26 AM, Lime, Steve D (DNR) wrote:
> I'd say no and yes (for non-voting committers). It's probably a good thing to validate the list of committers annually anyway.
>
> Steve
>
> ________________________________________
> From: mapserver-dev-bounces at lists.osgeo.org [mapserver-dev-bounces at lists.osgeo.org] on behalf of thomas bonfort [thomas.bonfort at gmail.com]
> Sent: Friday, October 05, 2012 6:57 AM
> To: MapServer Dev Mailing List
> Subject: [mapserver-dev] RFC 7.2 voting implications
>
> As 7.2 somewhat changes our bylaws, what would be our requirements for
> this vote:
>
> - should we require all PSC members to have voted. My understanding of
> RFC23 leads me to believe that no, but since this is modifying a
> previously voted motion are the rules different?
> - if/once adopted, should we require present committers to accept the
> new version?
>
> regards,
> thomas
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>


-- 
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000