Hi list,<br><br>I made some changes in the wiki:<br><ul><li>Created a RFC wiki page: <a href="http://pgrouting.postlbs.org/wiki/RFC">http://pgrouting.postlbs.org/wiki/RFC</a></li><li>Called "PSC guideline" RFC-01: <a href="http://pgrouting.postlbs.org/wiki/RFC/01">http://pgrouting.postlbs.org/wiki/RFC/01</a></li>
<li>Kept only basic information on the previous PSC wiki page: <a href="http://pgrouting.postlbs.org/wiki/PSC">http://pgrouting.postlbs.org/wiki/PSC</a></li></ul>Then I wrote RFC-02 to describe the changes involved with moving to OSGeo infrastructure.<br>
<a href="http://pgrouting.postlbs.org/wiki/RFC/02">http://pgrouting.postlbs.org/wiki/RFC/02</a><br>Feel free to edit the document and add additional information.<br><br>Stephen, I think the RFC's were a good idea. Thank you for that! <br>
I first thought it just makes everything more complicated, but it doesn't.<br>Anyone who has some good proposals, feel free to add some new RFC.<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Also updated on the wiki <a href="http://pgrouting.postlbs.org/wiki/PSC" target="_blank">http://pgrouting.postlbs.org/wiki/PSC</a><br>
There I removed the paragraph about IRC as well. (<a href="http://pgrouting.postlbs.org/wiki/PSC?action=history" target="_blank">http://pgrouting.postlbs.org/wiki/PSC?action=history</a>)<br>
</blockquote>
<br></div>
I will note that in other PSC, proposals are submitted for comment by all, but voting is based on PSC membership. I think it is important to get community input and to keep them informed, but voting is about moving the project forward regardless. We can grow the PSC as needed and as new developers start contributing and making a significant impact. If anyone on the list can veto an action then you run the possibility of getting bogged down. You need leadership not design by committee. My 2 cents anyway. I will support whatever. I also think the PSC needs to listen to the community or they will loose them, but the PSC is in theory more aware of the technical challenges and issues.<div class="im">
<br></div></blockquote><div><br>Yes, this veto thing also came up in a discussion with Venka. As far as I understood if there is a veto by one member and if no solution or compromise can be found, then the majority of a vote of all PSC members is sufficient. Here is the paragraph:<br>
<br><div style="margin-left: 40px;"><i>If a proposal is vetoed, and it cannot be revised to satisfy all
parties, then it can be resubmitted for an override vote in which a
majority of all eligible voters indicating +1 is sufficient to pass it.
Note that this is a majority of all committee members, not just those
who actively vote.
</i><br></div></div></div><br>So as an example if I ask to vote for RFC-02 and only you and Anton vote, but one of you vetoes, then it requires all PSC members to vote. Otherwise it would pass even with two people's vote, right?<br>
<br>For me this procedure sounds not bad. And to keep a kind of "standard" PSC guideline I'm in favour not to change this part. But well, the PSC has to agree? ;-)<br><br>Daniel<br><br>PS: I will keep this RFC-02 for a view days for editing and discussion and if there are no complaints, let's get votes for RFC-01, RFC-02 and a new release. Maybe April 1st. is not the best day for this ;-)<br>
<br>