DemocracyLab Project Portfolio Onboarding Survey (votorola at zelea.com)

Michael Allan mike at zelea.com
Tue Apr 2 18:20:55 EDT 2013


Hi Mark,

Thanks for sharing the draft survey.  For anyone who has trouble with
the scrubbed HTML attachment, I've pasted a text version below.

One suggestion I have is to add to each survey question an explanation
of the information sought.  Just a short explanation, little more than
a tooltip.

Another suggestion is to allow for on-fly changes to the survey
design.  Probably you already thought of this.  Basically it means
allowing for the addition of new survey questions.  Maybe also
indicating in the views that are compiled from the results (tables and
what not) the questions that were left unanswered.  Then new questions
would advertise their presence and the answers would eventually
trickle in, updating the views.  The aim ofc is to allow the design to
adapt instead of being set up-front.

Please CC Mark for replies, as he's not subscribed.  Again, the text
is below.

Mike


DemocracyLab Project Portfolio Onboarding Survey
------------------------------------------------

I. Project Basics

   a. Purpose and Summary of App (Text)

   b. Functional Status

      i. Active Community (Y/N, Link)

      ii. Beta Demo (Y/N, Link)

      iii. Development Timeline/Priorities (Text)

   c. Documentation of Engagement Results (Y/N, Link)

II. Identity

   a. Identity Description (Y/N, Text)

   b. Login Mechanisms

      i. Email/Username and Password (Y/N)

      ii. OAuth Login (Y/N)

         1. Facebook

         2. Google

         3. Twitter

         4. LinkedIn

         5. OpenID (is this OAuth or something different?)

   c. Demographic Information

      i. Demographic Info Required (Y/N)

      ii. Demographic Info Optional (Y/N)

      iii. Description of Uses of Demographic Info (Text)

   d. Public Persona

      i. User Profile (Y/N)

      ii. Anonymous (Y/N)

      iii. Pseudonames (Y/N)

      iv. Real Names (Y/N)

      v. Authenticated Identity (Y/N)

   e. Reputation Systems

      i. Enabled (Y/N)

      ii. Description of Uses of Reputation Systems (Text)

III. Community

   a. Community Description (Y/N, Text)

   b. Open Communities (Y/N)

   c. Restricted Communities (Y/N)

      i. Membership approved by moderator (Y/N)

      ii. Membership list preloaded (Y/N)

IV. Communication

   a. Communication Description (Y/N, Text)

   b. Intra-site Communications

      i. Forums

         1. Commenting System (Y/N)

         2. Threaded Discussions (Y/N)

         3. Comment Rating System (Y/N)

         4. Comment Tagging System (Y/N)

         5. Comment Filtering System (Y/N

      ii. Messaging

         1. Private messages to other users (Y/N)

         2. Private messages to groups (Y/N)

   c. External Communications

      i. Mailing List (Y/N)

      ii. Integration with Social Media (Y/N)

      iii. SMS (Y/N)

V. Issue Framing and Exploration

   a. Issue Framing Description (Y/N, Text)

   b. Moderator Controlled (Y/N)

   c. Community Generated (Y/N)

      i. Vetting Process (Y/N)

      ii. Collaborative Drafting Mechanism (Y/N)

VI. Dialogue and Deliberation

   a. Dialogue and Deliberation Description (Text)

   b. Survey Capabilities (Y/N)

   c. Data Representation (Y/N)

   d. Consensus Mechanisms (Y/N)

   e. Conflict Mapping Mechanisms (Y/N)

   f. Time Limited (Y/N)

VII. Decision Making

   a. Decision Making Description (Y/N, Text)

   b. Voting Capabilities (Y/N)

      i. Iterative Voting (Y/N)

      ii. Delegated Voting (Y/N)

      iii. Time Limited (Y/N)

   c. Adoption by Authority (Y/N)

      i. Binding Decision Based on Online Outcome (Y/N)

      ii. Authority Agrees to Consider Online Outcomes (Y/N)

      iii. Online Process Disconnected from Real-world Authority (Y/N)

VIII. Collaborative Action

   a. Collaborative Action Description (Y/N, Text)

   b. Project Management (Y/N)

   c. Asynchronous Collaboration (Y/N)

      i. Volunteer Pledges (Y/N)

      ii. Resource Pledges (Y/N)

   d. Synchronous Events (Y/N)

IX. Technology Architecture

   a. Technology Architecture Description (Text)

   b. Software License

      i. Open Source (Y/N)

         1. License (Link)

         2. Source Code (Link)

      ii. API (Y/N)

   c. Details of Technology Utilized (Text)


Mark Frischmuth (Google Drive) said:
> Attached: DemocracyLab Project Portfolio Onboarding Survey.html
> Sent using Google Docs http://docs.google.com/
> 
> Hi Votorola team,
> 
> I've attached a draft outline of the "Project Onboarding Survey" we're  
> working on for civic tech applications that choose to participate in the  
> collaborative workspace we're developing at DemocracyLab.  Any  
> comments/suggestions you have are welcome.
> 
> Best regards,
> Mark
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.zelea.com/list/votorola/attachments/20130402/655c0886/attachment.html>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.zelea.com/list/votorola/attachments/20130402/655c0886/attachment-0001.html>



More information about the Votorola mailing list