![](https://seccdn.libravatar.org/avatar/0295f9d5d76379b5da73427b67acd395.jpg?s=120&d=mm&r=g)
Feature changed by: Karl Cheng (qantas94heavy) Feature #311117, revision 11 Title: Team activity vote. - Hackweek VI: Unconfirmed + Hackweek VI: Done Priority Requester: Neutral Requested by: Yifan Jiang (yfjiang) Partner organization: openSUSE.org Description: We intend to implement a web-based application to allow people managing a customizable polling system, as well as showing convenient statistics of the voting results in both web page and download-able odf format. We call the tool 'Snoek'. Use Case: Shuang wants to organize a team building and bring people for dinner after that. She logs into Snoek and create a new team building activity with proper summary like 'Team building in August 2011'. Except for the basic description of the activity, in the activity creation page, she also needs to create a deadline for the activity. After that, polls needed to be defined for the activity: Pool 1 - Which game do you want to play in team building? option 1. option 2. option 3. Poll 2 - Where do you want to go have dinner after team building? option 1. option 2. option 3. Poll 3 - Which food do you prefer to have in the dinner? option 1. option 2. option 3. Then Shuang submit the activity and send mail to related people to ask them vote before deadline. After deadline Shuang revisited the activity page she created, and the tool will show her the number of people voting stats, which could be the basis of choice for team building and dinner. She can finally export the data into odf format. Business case (Partner benefit): openSUSE.org: Some times, we need statistics of internal preference of choice to, for example, where do we want to go team building? what size of t-shirt do people want in hackweek? which restaurant do we want to go dinner? These kind of stats can be only done manually at the moment, which could be painful and the questionnaires are usually not re- usable. We target to bring convenience typically described in the user case description section. Discussion: #1: Cornelius Schumacher (cschum) (2011-01-23 21:17:17) What framework are you going to use to implement this tool? #2: Daniel Collingridge (dcollingridge) (2011-01-24 18:21:56) Sounds interesting. I would also like to know what framework/language is being used. #3: yfjiang Jiang (yfjiang) (2011-01-25 02:33:57) (reply to #2) Sorry for the late reply, I didn't notice the only button below comments is 'Preview comment' :) We are going to use Django 1.2.4 and pure python 2.6. #4: yfjiang Jiang (yfjiang) (2011-01-25 02:36:50) Sorry for the late reply, I didn't notice the only button below comments is 'Preview comment' :) We are going to use Django 1.2.4 and pure python 2.6. #5: yfjiang Jiang (yfjiang) (2011-02-11 11:11:23) Hackweek 6 phase is closing. Here is the code where we are: git clone http://147.2.207.136/repo/snoek.git/ (http://147.2.207.136 /repo/snoek.git/) Please see README and TODO for more details. [Internal Demo] http://147.2.207.135:8080/ Finally may I wish you happy hacking and we appreciate your contribution :) -- openSUSE Feature: https://features.opensuse.org/311117