[openFATE 306624] voting mechanism for membership approval on users.o.o
Feature added by: Hendrik Vogelsang (hennevogel) Feature #306624, revision 1 Title: voting mechanism for membership approval on users.o.o Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To be better able to vote on membership approvals the openSUSE board is looking for some ruby hacker willing to implement a voting mechanism in users.opensuse.org. users.o.o is a ruby on rails application. Pepple that want to become openSUSE members fill out an application form in users.o.o. This is then evaluated by the openSUSE board. Each application is voted upon. What is missing in users.o.o is the possiblity to vote on those applications. This would need a couple of things: Each application needs a state attribute with the following content: * New * To be Accepted * Accepted * To be Rejected * Rejected Also the respective listings in the interface are needed. And for each board member an voting field. (+1,0,-1) coupled with a free text field. -- openSUSE Feature: https://features.opensuse.org/306624
Feature changed by: Hendrik Vogelsang (hennevogel) Feature #306624, revision 5 Title: voting mechanism for membership approval on users.o.o - Hackweek IV: Unconfirmed + Hackweek IV: New Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To be better able to vote on membership approvals the openSUSE board is looking for some ruby hacker willing to implement a voting mechanism in users.opensuse.org. users.o.o is a ruby on rails application. Pepple that want to become openSUSE members fill out an application form in users.o.o. This is then evaluated by the openSUSE board. Each application is voted upon. What is missing in users.o.o is the possiblity to vote on those applications. This would need a couple of things: Each application needs a state attribute with the following content: * New * To be Accepted * Accepted * To be Rejected * Rejected Also the respective listings in the interface are needed. And for each board member an voting field. (+1,0,-1) coupled with a free text field. -- openSUSE Feature: https://features.opensuse.org/306624
Feature changed by: Michael Löffler (michl19) Feature #306624, revision 6 Title: voting mechanism for membership approval on users.o.o - Hackweek IV: New + Hackweek IV: Evaluation Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To be better able to vote on membership approvals the openSUSE board is looking for some ruby hacker willing to implement a voting mechanism in users.opensuse.org. users.o.o is a ruby on rails application. Pepple that want to become openSUSE members fill out an application form in users.o.o. This is then evaluated by the openSUSE board. Each application is voted upon. What is missing in users.o.o is the possiblity to vote on those applications. This would need a couple of things: Each application needs a state attribute with the following content: * New * To be Accepted * Accepted * To be Rejected * Rejected Also the respective listings in the interface are needed. And for each board member an voting field. (+1,0,-1) coupled with a free text field. -- openSUSE Feature: https://features.opensuse.org/306624
Feature changed by: Hendrik Vogelsang (hennevogel) Feature #306624, revision 8 Title: voting mechanism for membership approval on users.o.o - Hackweek IV: Evaluation by project manager + Hackweek IV: Done Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Engineering Manager: Klaas Freitag (kfreitag) Partner organization: openSUSE.org Description: To be better able to vote on membership approvals the openSUSE board is looking for some ruby hacker willing to implement a voting mechanism in users.opensuse.org. users.o.o is a ruby on rails application. Pepple that want to become openSUSE members fill out an application form in users.o.o. This is then evaluated by the openSUSE board. Each application is voted upon. What is missing in users.o.o is the possiblity to vote on those applications. This would need a couple of things: Each application needs a state attribute with the following content: * New * To be Accepted * Accepted * To be Rejected * Rejected Also the respective listings in the interface are needed. And for each board member an voting field. (+1,0,-1) coupled with a free text field. -- openSUSE Feature: https://features.opensuse.org/306624
participants (1)
-
fate_noreply＠suse.de