January 20, 2014

Leadership/Planning Group mission and organization

• The group provides support to the brigade captains in strategic planning, public communication and event planning and is a place for ongoing development of new leadership for Code for Asheville.
• The group is 100% open: meetings are open to anyone, notes from meetings are posted publicly on the wiki, and the agenda for each upcoming meeting will be brainstormed in the Open Asheville Google group.
• Meetings will be biweekly until March, then monthly. The next meeting is 5:30-7:00pm February 3, 2014 at the French Broad Chocolate Lounge upstairs.
• Meetings will have a chairperson to keep things moving efficiently. This is not a permanent role - for now, the chair for each meeting will be designated at the previous one. Jason Mann will chair the February 3 meeting.
• Meeting agenda and notes - Eric Jackson will prepare a summary of each meeting and post it, together with raw notes, on the wiki. He will also kick off the agenda discussion for the next meeting in the Google group, but it will be the next chairperson's role to support that discussion and develop the final agenda.
• Regarding apps developed with CfA support, our organizational role is to support efforts by individuals and businesses - CfA should not "own" any apps. In cases where we do spearhead a development effort, everything we do should be open-source under a commercial-friendly license like the MIT license to encourage individuals and businesses to take them and run with them.

City open data policy update

• The city is open to a dialogue on an open data policy through the offices of the city manager and the city PR representative before passing a reviewed policy on to the Council. CfA is to kick this off by providing a sample policy.
• The next Hack Night will include hacking on a sample policy (Heather Seltzer and Scott Barnwell to lead this).

Code for Asheville communications

• Public communication about what CfA is, what it does needs to be much improved. We need a clear statement of our mission and good material on this and all our activities on the website and in social media.
• Heather Seltzer will kick off discussion to work out a mission statement and begin action on improving communications.

February 22 Code Across Event

• The event will be a smaller Hackathon designed to get some interesting projects started and to initiate conversations. A key 2014 goal will be to ensure that we follow through in supporting these projects and continuing the conversations after the hackathon ends.
• We will prepare several ideas for people to work on (a trash pickup app, a budget app, and a food delivery app were discussed as possibles). Scott B. will find out what information people are requesting to see if we are missing a high-potential app. We need to have candidates by the next Hack Night.
• Dave Michelson will reach out to Mojo Coworking regarding space for the event and will recruit programmers to work on any apps we want to prepare for in advance.
• Dave will also get a city representative to join us.
• We still need to get an elected official and ideas still needed for other people to invite (neighborhood group reps, non-profits, etc.).

Next Hack Night

• In general, Hack Nights will have multiple projects available to work on. Brigade captains will post a list of these in advance
• The next Hack Night (1/28/2014) will include: (1) collecting data, setting up for 2/22 Code Across event; (2) hacking on a sample Open Data Policy and talking points for the city; (3) website and communication hacking.

Raw Notes

Notes from Leadership Committee Jan 20, 2013

Attendees

Dave Michaelson Jason Mann Eric Jackson Daniel Holt Heather Seltzer

Agenda:

Policy Update from Scott via Jason -City is open to look at policy samples and dialogue on the details per the city PR representative and head of IT. Meetings with the city manager in the work. Our task is to formulate sample policy for so pertinent departments can review.

Discussion leads to being sure the policy is written ‘timeless’ to match changing technology. For example ‘read-able data’ not PDFs

Action Item: Next Hack Night will include developing sample policy to present to city (Scott and Heather)

2. Communications for CFA -Need for Mission Statement (bullet points) -Unified online message via Facebook and Website -Will recruit social media manager organically

Action item: Heather to create a worksheet for group to decide on Mission Statement

3. How does the Leadership/Organizing Group work? Meetings are from 5-7 bi-weekly till monthly meetings in March

There will be a Meeting Chair that will keep Agenda in focus during meetings

Assigned Roles: Eric will get meeting notes on Wiki post meeting Eric will start online agenda brainstorm and share on Google Groups before next meeting Jason will be the next Meeting Chair till either rotation or assigned roles are decided

4. Feb 22nd Event -Dave to reach out to Craig at Mojo for space -Smaller Hackathon to start projects -Put several ideas out for groups to work on -Trash App -Budget App -Food Delivery ? -Name it and put it on Social Media. Dave to get a city representative, Need an elected official. What non-profits can we reach out to?

Action Items: Scott to see what people are requesting data for to see if we are missing an idea Dave to reach out to Craig for Space Dave to recruit programmers for both smaller Apps

5.Next Hack Night Agenda to be sent out to group: -Hackers collect data for Feb 22 -Policy to finish up sample policy and talking points -Website ideas???

Action Items: Have several projects going at once at Hack Nights based on current goals. Send Agenda to whole CFA.

6. Follow-Up/Maintenance of Apps -MIT Open Policy? -Not worry while we create and discuss best fits for App after creation -Be careful not to align ourselves too closely with apps that may reflect badly either because of disuse or controversy.