codeforamerica Vallejo_waffle issues

codeforamerica / Vallejo_waffle

This is where we post our project tasks

1 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

INFO: Get city feedback on our messaging for INFO question solicitation materials

#117 nikzei opened 9 years ago
0
Follow up with PD and Joanna re: their ideas about speaker/story to represent the City

#116 nikzei opened 9 years ago
0
INFO: look into using google search widget (particularly for search in the site) - seems like search will be an important part of this project

#115 nikzei opened 9 years ago
0
Make meeting summary of CSS testing notes

#114 jazmynlatimer closed 9 years ago
0
Put feedback into Issues from CSS testing

#113 jazmynlatimer opened 9 years ago
0
Schedule a meeting with Loveless

#112 jazmynlatimer closed 9 years ago
0
discuss as team how/when to follow up with Richmond PD

#111 andrewschneider opened 9 years ago
0
Follow up with Bret Goldstein

#110 jazmynlatimer opened 9 years ago
0
mailchimp 7/27

#109 andrewschneider closed 9 years ago
0
Add questions from summit into Info Bank spreadsheet

#108 jazmynlatimer closed 9 years ago
0
Create interactive mockups for Admin section of CSS tool

#107 jazmynlatimer opened 9 years ago
0
Push edits to midyear report from google doc to web version

#106 jazmynlatimer closed 9 years ago
0
Survey to solicit questions for Info Bank

#105 jazmynlatimer opened 9 years ago
0
prototype "wand" like tool in typeform that would filter which dept css intake problems go to

#104 nikzei opened 9 years ago
1
arrange session with Solano County Legal Services folks (through Jill Sowards) to get their recs for info bank questions that people seem to need answers for

#103 nikzei closed 9 years ago
0
reach out to Corp. Garcia about 7/11 event and setting up way to work together; Kenny said that he's the one in charge now

#102 nikzei closed 9 years ago
0
list of languages, tools used for our builds - for future sustainability guidance

#101 nikzei opened 9 years ago
0
Info Bank: user reads answer (template for all answers)

#100 jazmynlatimer closed 9 years ago
0
RETRO: Discuss what the minimum goal we want each tool to accomplish?

#99 jazmynlatimer opened 9 years ago
0
RETRO: start talking about summit roles and goals

#98 jazmynlatimer opened 9 years ago
0
RETRO: Check in mid-July about prototypes

#97 jazmynlatimer opened 9 years ago
0
RETRO: for biweekly meetings in Vallejo, split up

#96 jazmynlatimer opened 9 years ago
0
RETRO: reach out to Richmond PD after midyear report is finished

#95 jazmynlatimer opened 9 years ago
0
RETRO: make private github repo for prototype updates and discussions

#94 jazmynlatimer closed 9 years ago
1
RETRO: assign people to mailchimp responsibility biweekly

#93 jazmynlatimer closed 9 years ago
1
RETRO: update codeforvallejo.org design

#92 jazmynlatimer opened 9 years ago
0
RETRO: start a google doc of people we need to follow up with

#91 jazmynlatimer opened 9 years ago
1
RETRO: research how people search for answers in info bank tool

#90 jazmynlatimer opened 9 years ago
0
research foreclosure,blight, zombie properties, how neighbors have organized elsewhere? Whether the attorney general is involved in these types of things and if maybe our tool might connect neighbors with the AG's office?

#89 nikzei closed 9 years ago
1
email Claudia: re (1) whether foreclosed/zombie properties or a big problem, (2) whether the process of moving them toward abatement is different from doing so with those not yet foreclosed, and (3) whether there is a resource where neighbors can learn about how to deal with these types of properties without hiring an attorney

#88 nikzei closed 9 years ago
0
Contact Tina for details and time slots for July 11th NW event

#87 jazmynlatimer closed 9 years ago
0
First mockups of Info Bank: user sees results of possible answers

#86 jazmynlatimer closed 9 years ago
0
First mockups of Info Bank: user asks question

#85 jazmynlatimer closed 9 years ago
0
Create interaction task flow for CSS Intake

#84 jazmynlatimer closed 9 years ago
0
quick check in re: website feedback from Code Osmosis - decide next steps

#83 nikzei closed 9 years ago
1
PROTOTYPES: mock ups for Beta (prioritized over user testing)

#82 nikzei closed 9 years ago
0
MID-YEAR REPORT: prepping our respective sections - 6/4 first draft meeting

#81 nikzei closed 9 years ago
0
INFO: thinking about how we frame our intention of balancing out the services we highlight (accountability, transparency)

#80 nikzei opened 9 years ago
1
INFO: create list of use cases

#79 nikzei closed 9 years ago
1
INFO: plans and partners for survey distribution

#78 nikzei closed 9 years ago
0
INFO: survey (paper distribution) - want do residents want to know?

#77 nikzei opened 9 years ago
0
INFO: identify who we'll rely on to promote it (if use case specific, start identifying strategies)

#76 nikzei opened 9 years ago
0
INFO: Storyboard examples of use cases (all will slack examples - J will draw)

#75 andrewschneider closed 9 years ago
0
DISPATCH MAP: mvp - show vehicles on a map

#74 andrewschneider opened 9 years ago
0
RTM: compile list of potential analyses

#73 andrewschneider opened 9 years ago
0
RTM: background research

#72 andrewschneider opened 9 years ago
0
DISPATCH MAP: talk w Greg, understand what deployment will entail

#71 nikzei closed 9 years ago
0
CSS INTAKE: talk to reporters about process

#70 nikzei opened 9 years ago
0
CSS INTAKE: follow up w Tina: what elements of info does she need?

#69 nikzei closed 9 years ago
0
CSS INTAKE: cityvoice research (functionality, use, sttengths, weaknesses, etc)

#68 nikzei opened 9 years ago
0