Raleigh, NC – We have been a little busy since Triangle Open Data Day and are remiss about a recap of the event. Coming soon. In the mean time here are some of your stories:
Raleigh, NC – Photos from Triangle Open Data Day 2015.
Raleigh, NC –
Data Sources from Local Wiki
Cary, NC – The EventBrite page was supposed to start a waitlist once we reached capacity as we always know some people have last minute conflicts etc. Unfortunately, the waitlist function is broken. So please e-mail Ian Henshaw if you want to be put on the waitlist and we will add you manually.
Ian Henshaw –
Durham, NC – We’re proud and excited to announce Caktus Group as a Bronze sponsor of Triangle Open Data Day.
Caktus Group is the nation’s largest specialists in Django, an open source framework. They build custom web, mobile, and SMS applications that address complex business and social needs. They’ve built over 100 solutions that have impacted more than 4 million lives around the world. Caktus’ commitment to open source extends beyond company projects.
Tech Tank Article on Caktus Group: How Libya’s Election Process is Better than the United States’s (Top 10 article on the Tech Tank blog in 2014)
Raleigh, NC – A few of you have been asking about the rules for the hackathon. No rules, just a code of conduct.
The goal of CodeAcross is to activate the Code for America network and inspire residents everywhere to get actively involved in their community.
The theme for CodeAcross 2015 is Principles for 21st Century Government. We encourage events to organize around one or more of the principles.
So bring some skills and learn some new skills, bring some code and write some new code*, bring some friends and meet some new friends, etc.
Lets inspire our municipalities to adopt open data and open source, design websites for their citizen’s needs and embrace technology for improved services.
Principles for 21st Century Government
- Design for people’s needs
- Make it easy for everyone to participate
- Focus on what government can do
- Make data easy to find and use
- Use data to make and improve decisions
- Choose the right technology for the job
- Organize for results
Cary, NC – Triangle Open Data Day Anti-Harassment Policy.
Why do we have an official anti-harassment policy for Triangle Open Data Day events?
- It sets expectations for behavior at the event. Simply having an anti-harassment policy can prevent harassment.
- It encourages people to attend who have had bad experiences at other events.
- It gives event staff/volunteers instructions on how to handle harassment quickly, with the minimum amount of disruption for the event.
- sexual orientation
- gender identity
The above is not an exhaustive list — we do not tolerate harassment of event participants in any form.
Sexual language and imagery is not appropriate for any event venue, including talks. Event participants violating these rules may be expelled from the event, and even banned from future events at the discretion of the event organizers/management.
Harassment includes (but is not limited to):
- offensive verbal comments related to gender, sexual orientation, disability, gender identity, age, race, religion
- the use or display of sexual images in public spaces
- deliberate intimidation
- harassing photography or recording
- sustained disruption of talks or other events
- inappropriate physical contact
- unwelcome sexual attention
Participants asked to stop any harassing behavior are expected to comply immediately.
Exhibiting partners and guest speakers are also subject to the anti-harassment policy. In particular, exhibitors and speakers should not use sexualized images, activities, or other material, or otherwise create a sexualized environment in their slide decks, exhibit material, exhibit staffing, promotional items or demo material.
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact an organizer or event volunteer immediately. Organizers and event volunteers may be identified by t-shirts or special badges/lanyards. Organizers will investigate the issue and take appropriate action. This may include helping participants contact venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event.
- Phone: 919-633-0055
- Law Enforcement:
- Emergency Dial 9-1-1
- Non-Emergency in Durham 919-560-4600 or 919-560-4601
- Non-Emergency in Raleigh 919-996-3335
- Non-Emergency in Chapel Hill 919-968-2760
Though we hope that we never have to invoke this policy, we believe that having this document helps everyone think a little more about how their actions and words affect the whole community, as well as individuals in the community.
License and attribution
This policy is licensed under the Creative Commons Zero license. This policy is based on several other policies, including the GDG Research Triangle Anti-Harassment Policy and the Ohio LinuxFest anti-harassment policy, written by Esther Filderman and Beth Lynn Eicher, and the Con Anti-Harassment Project. Mary Gardiner, Valerie Aurora, Sarah Smith, and Donna Benjamin generalized the policies and added supporting material. Many members of LinuxChix, Geek Feminism and other groups contributed to this work.
Code for Cary has a standing Code of Conduct policy forked from Code for America’s Code of Conduct. Nothing written above should be considered to be in conflict with the Code for Cary Code of Conduct policy
09:30 Jason Hare: The Triangle’s emerging regional data ecosystem
09:40 Jamie Dixon with Ian Henshaw: WCPSS School Scores and Wake County Tax Data
09:50 Robert Campbell with Lori Bush: Cary site plan development map
10:00 Matt Schnars: Homelessness Data for the region
Safety & Justice
10:10 Dylan Young and Andy Shapiro: State-level traffic stop visualization dashboards
10:20 Reid Serozi and Jim Alberque: Visualizing Raleigh’s SeeClickFix information
10:30 Reid Serozi: Bike crash data on new Socrata platform
10:40 Aaron Burns and Sean Rycek (NC State): Bike crash data
10:50 Jamie Dixon with Chris Mathews: Wake County Restaurant Inspection analysis
Photo from Flickr by black rhcp