| 1 |
On 04/21/2010 08:36 PM, Jorge Manuel B. S. Vicetto wrote: |
| 2 |
> Even though it might be desirable to be able to vote on single points of |
| 3 |
> the discussion, a governance policy document can't be just a sum of |
| 4 |
> points. Therefore, if we opt to have a vote for individual points, I |
| 5 |
> propose in the end we chose someone to write a coherent document based |
| 6 |
> on those points and to submit the final document to a global vote. |
| 7 |
|
| 8 |
Agreed. |
| 9 |
|
| 10 |
Any reason we couldn't just use a forum vote for this purpose? The |
| 11 |
drafting aspects of this don't need to be binding since the final vote |
| 12 |
will be. |
| 13 |
|
| 14 |
Also - a forum might be more inviting to the non-dev community, which I |
| 15 |
think is a good thing. However, since devs will ultimately approve the |
| 16 |
final document, we might consider having some kind of a dry-run vote on |
| 17 |
the individual points that is restricted to devs, so that we can avoid |
| 18 |
having the final draft vetoed and having to guess why. |
| 19 |
|
| 20 |
So, in a nutshell: |
| 21 |
1. Forum votes open to anybody with a forum account. This can be |
| 22 |
iterative if the comments are useful. |
| 23 |
2. Propose best ideas from forum to a dev-only vote to confirm. This |
| 24 |
can be iterative until all ideas seem acceptable. |
| 25 |
3. Assemble final draft, do an RFC to clean it up, and then put it out |
| 26 |
for a formal vote per the usual process. |
| 27 |
|
| 28 |
This gives the entire community a big say in the final document - |
| 29 |
basically the community is proposing the elements of the first draft, |
| 30 |
and then it only changes if devs can't accept something in it. |
| 31 |
|
| 32 |
Rich |
Archives