[fusion-dev] Fusion RFC 2 - Bootstrap Fusion PSC

[Paul Spencer]

Ok, we've had some time to think about this.  I've had a couple of  
minor comments on some parts which I have integrated:

* clarified that anyone may propose changes and request a vote on a  
change, not just PSC members (but only PSC member votes count)

* added a statement indicating that proposals may require an RFC at  
the discretion of the PSC, with RFCs being required for changes to the  
PSC itself and for major changes to the code (changing public API,  
technically risky work, changes with wide scope etc)

Since neither change was significant, I don't think that we need to  
wait any longer to vote on this.

I will send a separate email to fusion-users and fusion-dev requesting  
a vote.

Cheers

Paul

On 14-May-08, at 5:28 PM, Paul Spencer wrote:

> I would like to open up RFC 2 [http://trac.osgeo.org/fusion/wiki/FusionRfc2 
> ] for comment and general community feedback.
>
> In summary, we would like to create a governing body for the Fusion  
> project made up of key stakeholders and other community members that  
> makes decisions on behalf of the community operating under the  
> guidelines described here:
>
> http://trac.osgeo.org/fusion/wiki/ProjectSteeringCommitteeGuidelines
>
> The initial membership of the committee is small and limited to key  
> technical stakeholders.  As the community grows, the PSC will bring  
> on active members of the community as formal members to ensure broad  
> representation.  Although voting on issues is limited to PSC  
> members, all discussions will be public on the fusion developer's  
> list and anyone may (and is encouraged to) comment on any issues  
> through the fusion developers list.
>
> I propose to leave this RFC open for discussion for one week (until  
> May 21) at which time we will adopt it if there is no serious  
> dissent from the community.  During that time, any comments on the  
> PSC Guidelines will be accepted and integrated into the formal  
> guidelines if it makes sense to the initial committee members - i.e.  
> I will add the changes if no proposed member objects to proposed  
> changes.  Any substantial change in the nature of the guidelines  
> will be open for general discussion and may postpone the adoption  
> date to provide sufficient time for community feedback.
>
> Thanks for your involvement ...
>
> Paul
> __________________________________________
>
>   Paul Spencer
>   Chief Technology Officer
>   DM Solutions Group Inc
>   http://www.dmsolutions.ca/
>
> _______________________________________________
> fusion-dev mailing list
> fusion-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-dev


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://www.dmsolutions.ca/