Skip to content

Meeting notes

Jump to bottom
Trey Gordner edited this page Sep 23, 2019 · 5 revisions

190430

  • Determine points of contact, regular workflow and project tools
    • Points of contact: Stephen for design/dev, Trey for PM, when in doubt CC both
    • On Fairvote side: Scott advisory, Emily and Owen leading (cc both)
    • Workflow: meetings every 1-2 weeks, email in between as needed.
    • Project tools: using Github as code repository, wiki (including meeting notes), and project management tool.
    • New idea: Landing page, Nationbuilder/ActionNetwork list for updates --> rankit.vote redirect to splash page w/ email signup for updates, email [email protected] to support dev, "continue to beta site"
      • Who has DNS access to rankit.vote? Emily does.
      • Stephen to build landing page, work with Emily on DNS and email form
    1. Do you already have a Firebase account? No Firebase account
    2. The code is open source, do they wish to have the process open source as well? This matters for the Github repo. A public repo is a public repo. Decision: process is private, code will be public at end
  • Identify 5 current/past users of RankIt to interview about their poll creation/voting needs
    • VoterChoice MA, RepresentUs, RCVRC
    • Combo of state and national leads
    • Emily to ask Drew Penrose if he can see who uses the old app the most (has view access to Firebase), set up
    • Emily to collect list of emails requesting bug fixes/features, send invites to be involved in new version
      • Emily willing to send FairVote swag to interviewees. Great motivator!
  • Identify the FairVote team's focus group to meet with about their admin/analytics needs
    • Chris Hughes w/ RCVRC, Erica Frasier (Research Analyst), Owen, Emily (Marketing), ? Customer Support, Scott (Gen. Dev.)
    • No current process on customer support. Trey/Scott's recommendation: create [email protected], forward to Emily for now.
    • Next step: Determine focus group, schedule ballot design and admin/analytics conversation
  • Outline what we need from FairVote to begin writing functional specifications
    • Note: Specifications in this case = Agile user stories. These will also be the App Requirements listed in the contract.
    • Question from Scott: what happens to stories that fall outside of the first version? Trey: will also keep track of these in a backlog in Github.
    • Trey and Stephen to review old app, begin creating user stories/sketches.
    • Stephen: basically 3 parts to app--Voting experience, poll review/educational features, administrative features (including poll creation).

190510

  • Decision: should we create a splash page with email capture or leave the beta active? Unfortunately, we can't do both.
    • Emily to give Stephen DNS access, code to embed beta signup form, video of past poll
    • Stephen to take down application, put up form
  • Strategy discussion: should this app be fun and informal (eg. create your own poll to ranking ice cream) or formal and political (eg. simulating local elections)?
  • Tension between excite and educate: Which wins? Or are we attempting "edutainment"?
  • Design discussion: what kind of ballot style(s) should be supported?
    • DEC: whatever looks best on mobile, preference for interactivity over fidelity to paper
  • Interview procedure and next step (Emily to thank, let them know Trey will contact them soon)
  • Emily: want to give national partners some early access--how to do this?
    • Preview of interactive
    • Owen and Emily to share examples of single-winner and multi-winner results graphics that succeed, and others that fail
  • Decision-making: whose input is binding and whose is optional?
    • Advisory group (i.e. Stakeholders): Louis, Scott, Erica (Research/Analytics), Drew (Policy), Chris (Design), Eric Ashman (sp?)
    • Beta testers - non-binding advice as users
    • Emily is business lead, has final say
    • Trey to send TY note to beta testers and timeline for this month

190830

  • Timeline and process for internal (staff + advisor) testing
    • Ready to go to internal testers Tuesday
    • Especially concerned about technical accuracy
    • Trey to draft email to internal testers, send on 9/3
  • Timeline and process for beta testing
    • Drip email: sign in and create your own poll, take a poll, read the results
    • 1st email on 9/9, reminder on 9/13, end on or before 9/20. Bug fixes, final testing through 10/4, ready to launch 10/7.
    • Does it make sense to include anyone else?
  • Point of contact while Emily and Owen are OOO
  • Version 1.1?
    • Collect feature requests during beta testing, write up as backlog for potential future contract
    • Timeline: After Stephen's kid (December), Before June to take advantage of the 2020 media cycle

190430

  • Support for IE: DEC will not support (Stephen -- browser sniffing w/ warning?)
  • Utah system of multi-winner --> No decision, Emily & Katie to discuss w/ Sangita, reply by Monday
    • Rob: "we were hoping RankIt could be part of the educational effort in Utah"
    • "cities in Utah (including two this November) use the winner-take-all form of RCV"
  • How do tie breaks work?
    • coin toss -- does this need explaining?,
    • possible that no one gets over the threshold
  • Stephen, what else do you need from this group?
    • Embedding bug: "iframe converter" needed for FairVote website, Emily to try again and send code
  • Emily and Owen to review language for multi-winner elections
  • Sending to beta testers --> TUESDAY
Clone this wiki locally