1:20 a.m.
#20: Candidate and Community Q/A feature
--------------------------+-------------------------------------------------
Reporter: jspaleta | Owner: nigelj
Type: enhancement | Status: assigned
Priority: major | Milestone: Release 0.2.0
Component: General | Version: trunk
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Changes (by nigelj):
* status: new => assigned
* version: 0.1.0 => trunk
* milestone: Release 0.1.5 => Release 0.2.0
Old description:
Purpose: To generate a slate of community questions to ask each
candidate in an election to help people do a side by side comparison of
candidates's thoughts on important Fedora project issues as seen by the
voting community.
This involves 4 things
1)A way for community to write in questions for candidates
2)A way for community to vote for questions previously submitted by a
certain deadline
3)A way for each candidate to answer "top" questions, by a certain
deadline
4)Displaying all candidate answers to all "top" questions together side
by side in context with the question. No commenting or revisioning beyond
the deadline
Notes:
I am told that lmacken is working on a community idea storm like app
which should be able to do
1) and 2)
3) is essentially setting some arbitrary limit to the number of questions
candidates will be expected to ask, as part of the election announcement.
You may want to supplement the community vote process with a small group
selection step to weed out a highly inappropriate question.
Once the slate of questions are selected the app would need to provide a
space for each candidate to answer each of those selected questions.
Such a space should be limited to a finite number of words per question,
to discourage people like me from writing overly detailed responses.
4) just makes it fair. If an issue or answer is hotly contested a
candidate-candidate debate can be done in a mailinglist or the
blogosphere.
New description:
Purpose: To generate a slate of community questions to ask each candidate
in an election to help people do a side by side comparison of candidates's
thoughts on important Fedora project issues as seen by the voting
community.
This involves 4 things
1. A way for community to write in questions for candidates
2. A way for community to vote for questions previously submitted by a
certain deadline
3. A way for each candidate to answer "top" questions, by a certain
deadline
4. Displaying all candidate answers to all "top" questions together side
by side in context with the question. No commenting or revisioning beyond
the deadline
Notes:
I am told that lmacken is working on a community idea storm like app which
should be able to do
1) and 2)
3) is essentially setting some arbitrary limit to the number of questions
candidates will be expected to ask, as part of the election announcement.
You may want to supplement the community vote process with a small group
selection step to weed out a highly inappropriate question.
Once the slate of questions are selected the app would need to provide a
space for each candidate to answer each of those selected questions. Such
a space should be limited to a finite number of words per question, to
discourage people like me from writing overly detailed responses.
4) just makes it fair. If an issue or answer is hotly contested a
candidate-candidate debate can be done in a mailinglist or the
blogosphere.
Comment:
To be honest, this is something that I wished to add from the start, but
didn't have time, I just added Ticket #23 as something else that I'm
planning on adding (nomination in-app).
The way I see this as working is as follows:
User goes to a.f.o/voting and notices Upcoming Elections: ABSTRACo
December 2008, they click and are given a list of current nominations and
a prompt to "Login for more options", when they log in, if they are in a
group that can vote in the election, they can either "Ask a question" or
"Nominate someone" (including themselves).
They choose "Ask a Question" and is prompted to either choose a candidate
or "All Candidates" and they can enter a question, say "Will you offer
users free ice creams for a year?", notification goes out to the nominee,
or all the nominees.
The nominee(s) login and notice "You have a question to answer ..." so
they click on the link and are presented with a list of questions, they
select the one they want, and some options appear, "Reject Question",
"Refer to co-ordinator(s) for rejection", "Answer". In the case of
"Reject question" it'll be counted as a statistic of non-answered
questions, if it's refered, then the co-ordinator (either someone from the
body of the group that is holding the election, or someone in the
elections group) can review the question and choose to either "Reject it"
or "Bounce it back" (with reasons).
Questions for all would be approved by the co-ordinators before the fact
in case of spam, and new candidates after the question would be presented
with the question as well.
At all stages questions would be made visible (to avoid duplicates etc).
With the end view something like:
----
Foo Bar
I want to be part of ABSTRACo because I think it'd be cool.
Questions:
Answered (2):
Q. Will you give us Ice Creams? (baz)
A. If your all good little boys
Q. Will you let us include our pet fish in the distribution? (moa)
A. No it wouldn't be fair
Not Answered (3):
Q. What's 1+1? (...)
The candidate declined to answer this question.
Q. How do I install yum? (...)
This question was rejected by the election co-ordinator because:
Inappropriate
Q. What are your policies? (...)
The candidate did not answer this question before the election started.
----
Thoughts?
--
Ticket URL: <https://fedorahosted.org/elections/ticket/20#comment:1>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections