VoteWrap Wiki:Community Portal

Discussions

• Jonathan Glass - Thor Prohaska

• Thor Prohaska - Ronald Evans

Modification of the VoteWrap Method

Any modifications to the VoteWrap Method will be done using the VoteWrap Method itself.

If you want to propose modifications or enhancements to the core VoteWrap method then all you have to do is register yourself and then mark up the changes in the appropriate place s in this wiki.

Any registered users that behave in a way that is not is the spirit of the VoteWrap Method will have their access to this wiki removed.

Proposed Enhancements to the VoteWrap Method

• Voter verification by peer reference.

• Use actual instead of rounded Importance & Urgency values to determine Consensus Level.

• Identification using Semantic Web technology of identical VoteWrapped issues that have arisen independently. And then aggregating the individual issues into a single VoteWrapped instance.
  • Separate Issues Scenario
    • 1,000 individual instances of an issue exist.
    • Each issue on average requires:
      • $1,000 and 10 person days to resolve.
      • In total requiring $1,000,000 and 10,000 person days.
  • Merged Semantic VoteWrap Scenario
    • Assumptions.
      • 1: After analysis of all 1,000 instances it is determined that 70% of the issue is identical with complete agreement ( Vote YES ). 20% is similar ( Vote UNDECIDED ). And, 10% is in disagreement ( Vote NO ).
      • 2: UNDECIDED portion will take 10 person days to resolve.
      • 3: NO portion will take 30 person days to resolve.
      • 4: 10 times more people can work on the issue so it can be completed in 5 days.
    • 1 individual instance of the issue.
    • Takes in total 50 Person days and $5,000
  • The VoteWrapped scenario will take:
    • 1/2% of the $$$
    • 1/2% of the person days.
    • 50% quicker to complete.

Implementation Ideas

The GUI

It is envisaged that all the implementations of the VoteWrap Method into a collaborative space will have a GUI interaction along these lines.

• Highlight the text or graphic to be VoteWrapped.
• Right click on the highlighted elements to display the pop-up menu.
• Select the VoteWrap option.
• The VoteWrap data entry screen appears.
• After entering voting and configuration data the results are displayed.
• When the view is switched back to the VoteWrapped element then its summarised state is displayed directly in the element. E.g. the text will be the various vote colours of No (Red), Undecideds (Oranges) and Yes (Green).

MediaWiki

• Implement the method into MediaWiki.

Semantic MediaWiki

• Once the basic MediaWiki extensions have been created above then extend the method into Semantic MediaWiki.

Google Apps Engine

• The App Engine seems like a good environment to implement the VoteWrap Method.

CGI Script

CGI Script to implement the method onto the web server.

Browser plug-in

Browser plug-in to implement the method directly into the browser. Obviously FireFox or similar open source would be the best place to start.

Strong encryption

Security will be of ultra importance. How to implement needs investigation.

Distributed Database

For the maximum uptake of VoteWrap it must NOT be under centralised control. In fact it must be structured in a way that makes it as close to impossible as is practical to be controlled centrally. If it isn't then I wouldn't use it for anything important or sensitive if it was. I want each voter to control their own data and to only have it aggregated in a central location. If the central instance is destroyed accidentally or deliberately then in can be reconstituted from all the distributed instances.

How to best do this is a work in progress.