RFC voting system

[naderman]

I've just been browsing through the 3.2 RFCs and realised that it's starting to become somewhat difficult to track them. There are 81 now in very different stages. I think we need to come up with some system of voting on RFCs to be able to at least reject some that we don't plan on implementing. To do so, we need to formalise some voting rules: Who can vote? How many votes by whom are required to make a decision? How long is the voting phase?

Apart from that technical questions arise: Do we want to start using some different system, can we somehow incorporate this voting system into area51? Do we just want to vote through +1/-1 posts? Other ideas?

We could potentially create a new page that lists all the RFCs from area51 on http://www.phpbb.com and allows users to vote on them while comments would still be made on area51. This would simultaneously allow us to use the votes system for priorities. Would this help get more community participation/opinions?

[nextgen]

In my opinion I do not think that opening another site just to help you vote if 100% of the community in only 5% phpbb.com pay attention to this development.

[Vinny]

To do so, we need to formalise some voting rules: Who can vote? How many votes by whom are required to make a decision? How long is the voting phase?

Something about number of posts or registration date or votes of the team would have more strength.

Apart from that technical questions arise: Do we want to start using some different system, can we somehow incorporate this voting system into area51? Do we just want to vote through +1/-1 posts? Other ideas?

A new page to browse through of RCF to vote. I liked it.


Yet, I think that if implemented the voting system, the votes of the dev team should be able to approve/deny any RFC.

[Oleg]

The way I understand the RFCs are accepted is if there is consensus among the development team that they should be accepted. So voting (or any activity in an RFC, really) mostly serves to expedite the process of the development team looking at said RFC and deciding if it should be implemented.

I've just been browsing through the 3.2 RFCs and realised that it's starting to become somewhat difficult to track them.

How about 1) topic title prefix indicating current status (possibly expand from the current accepted/rejected/pending), and 2) an up-to-date status summary in the first post (X developers for/Y developers against/Z community votes/any unresolved issues)?

We could potentially create a new page that lists all the RFCs from area51 on http://www.phpbb.com and allows users to vote on them while comments would still be made on area51. This would simultaneously allow us to use the votes system for priorities. Would this help get more community participation/opinions?

If you care for positive votes only, this can already be done in tickets, so we'd just need to link to the tickets.

We also have http://wiki.phpbb.com/PhpBB3.1/RFC which is not receiving a whole lot of love.

[ecwpa]

Maybe a mod for this board specificaly. Lets call it "Simple poll".

Every first post can be "Liked" (optional dislike option), then at the top of the topic it'll show how many people like the idea and if you want to make the data more clear, separate the bars per group.

Something like this:

25 Users like this idea, 3 phpBB developers like this idea.

If the dislike option is enabled then you can have an extra graphic with like/dislike ratio ala Youtube.

30% of users like it |####|-----------------------|
17% of phpBB developers like it |##|----------------------|


Now, I'm thinking that can be done with the regular polls, right?

[MichaelC]

Something similar to the Wordpress's ideas centre?

[rxu]

Well, JIRA allows to vote for the tickets, so if RFC is a ticket, you can vote. Then you can filter RFC tickets to track votes.

[keith10456]

... We could potentially create a new page that lists all the RFCs from area51 on http://www.phpbb.com and allows users to vote on them while comments would still be made on area51. This would simultaneously allow us to use the votes system for priorities. Would this help get more community participation/opinions?

I really like this... Receiving and evaluating input from the community is always a good idea.

[MartinTruckenbrodt]

Hello,
so many missing core features are realized with MODs for Olympus. At this time for me it seems like the MODs are ignored for the feature discussion here. I think there is a connection needed to the Olympus MOD DB.
I'm a long-time MOD author. And all of my recent MODs are validated MODs. Some of them are very large MODs. And only Multiple Newsletters Add On is not adding missing core features. I spent a lot of time in programming the MODs. And MOD validation team spent a lot time in validation. So my opinion is that it should be possible to have a finished feature discussion without having a finished RFC. Then you get a Go from the dev team for the feature to start programming the RFC.

BTW: The poll thing is a very good idea!
BTW: For MODs there is a rating system. Maybe these results should been used, too.

Bye Martin