Category Archives: free culture

Open Data Day Google+ Hang Out

Open Data Day 2014 is Coming Feb 22 – Time to Join the Fun!

So, with much help from various community members (who reminded me that we need to get this rolling – looking at you Heather Leson), I pleased to say we are starting to gear up for Open Data Day 2014 on February 22nd, 2014.

From its humble beginnings of a conversation between a few friends who were interested in promoting and playing with open data, last year Open Data Day had locally organized events take place in over 100 cities around the world. Check out this video of open data day in Kathmandu last year.

Why makes Open Data Day work? Mostly you. It is a global excuse for people in communities like yours to come together and organize an event that meets their needs. Whether that is a hackathon, a showcase and fair, lectures, workshops for local NGOs and businesses, training on data, or meetings with local politicians – people are free to organize around whatever they think their community needs. You can read more about how Open Data Day works on our website.

Want to join in on the fun? I thought you’d never ask. Listed below are some different ways you can help make Open Data Day 2014 a success in your community!

A) How can I let EVERYONE know about open data day

I love the enthusiasm. Here’s a tweet you can send:

#OpenData Day is community powered in a timezone near you. http://opendataday.org/ #ODD2014

Yes, our hashtag is #ODD2014. Cause we are odd. And cause we love open data.

B) I’d like to participate!

Great! If you are interested in participating in check out the Open Data Day wiki. We’ve just unlocked the pages so cities haven’t been added yet but feel free to add your city to the list, and put down your name as interested in participating. You can even check to see who organized the event last year to see if they are interested in doing it again.

C) Forget about participating, I want to coordinate an Open Data Day event in my city.

Whoa! Very exciting! Here’s a short checklist of what to do:

If you didn’t organize one last year, check to see if anyone in your city did. It would be good to connect with them first.
Read the Open Data Day website. Basically, pick up on our vibe: we want Open Data Day to work for everyone, from novices who know little about data to experts like Kaggle participants and uber geeks like Bruce Schneier. These events have always been welcoming and encouraging – it is part of the design challenge.
Okay, now add your city to the list, let people know where it will be taking place (or that you are working on securing space), let them know a rough agenda, what to expect, and how they can contribute.
Add yourself to the 2014 Open Data Day map. (Hint: Wikipedia lists Lat/Long in the information side bar for each cities wiki page: “Coordinates: 43°42′N 79°24′W”)
Join the Open Data Day mailing list. Organizers tend to share best practices and tips here. It’s not serious, really just a help and support group.
Check out resources like this and this about how to organize a successful event.
Start spreading the news!

D) I want to help more! How can Open Data Day work more smoothly everywhere?

Okay, for the truly hardcore you right, we need help. Open Data day has grown. This means we’ve outgrown a whole bunch of our infrastructure… like our webpage! Everyone involved in this is a volunteer so… we have some extra heavy lifting we need help with. This includes:

a. Website template update: The current Open Data Day template was generously donated by Mark Dunkley (thank you!!!). We’d love to have it scale a little better and refresh the content. You can see the code on github here. Email me if you are interested. Skills required: css, design

b. Translation: Can you help translate the ODD site into your language? You can submit the requests on github or send a document to heather.leson at okfn dot org with the content. She’ll do the github stuff if that’s beyond you.

c. Map: Leaflet and layers helpers wanted! We’d like a map geek to help correct geolocation and keep the 2014 map fresh with accurate geo for all the locations. Github repo is here and the event list is here.

What’s next?

I’m really looking forward to this year… I’ve lots more thoughts I’ll be sharing shortly.

Plus, I can’t wait to hear from you!

Access to Information, Technology and Open Data – Keynote for the Commissioners

Mission Driven Orgs: Don’t Alienate Alumni, Leverage Them (I’m looking at you, Mozilla)

29 Replies

While written for Mozilla, this piece really applies to any mission-driven organization. In addition, if you are media, please don’t claim this is written by Mozilla. I’m a contributor, and Mozilla is at its best when it encourages debate and discussion. This post says nothing about Mozilla official policy and I’m sure there Mozillians who will agree and disagree with me.

The Opportunity

Mozilla is an amazing organization. With a smaller staff, and aided by a community of supporters, it not only competes with the Goliaths of Silicon Valley but uses its leverage whenever possible to fight for users’ rights. This makes it simultaneously a world leading engineering firm and, for most who work there, a mission driven organization.

That was on full display this weekend at the Mozilla Summit, taking place concurrently in Brussels, Toronto and Santa Clara. Sadly, so was something else. A number of former Mozillians, many of whom have been critical to the organization and community were not participating. They either weren’t invited, or did not feel welcome. At times, it’s not hard to see why:

Again this is not an official Mozilla response. And that is part of the problem. There has never been much of an official or coordinated approach to dealing with former staff and community members. And it is a terrible, terrible lost opportunity – one that hinders Mozilla from advancing its mission in multiple ways.

The main reason is this: The values we Mozillians care about may be codified in the Mozilla Manifesto, but they don’t reside there. Nor do they reside in a browser, or even in an organization. They reside in us. Mozilla is about creating power by foster a community of people who believe in and advocate for an open web.

Critically, the more of us there are, the stronger we are. The more likely we will influence others. The more likely we will achieve our mission.

And power is precisely what many of our alumni have in spades. Given Mozilla’s success, its brand, and its global presence, Mozilla’s contributors (both staff and volunteers) are sought-after – from startups to the most influential companies on the web. This means there are Mozillians influencing decisions – often at the most senior levels – at companies that Mozilla wants to influence. Even if these Mozillians only injected 5% of what Mozilla stands for into their day-to-day lives, the web would still be a better place.

So it begs the question: What should Mozilla’s alumni strategy be? Presently, from what I have seen, Mozilla has no such strategy. Often, by accident or neglect, alumni are left feeling guilty about their choice. We let them – and sometimes prompt them to – cut their connections not just with Mozilla but (more importantly) with the personal connection they felt to the mission. This at a moment when they could be some of the most important contributors to our mission. To say nothing about continuing to contribute their expertise to coding, marketing or any number of other skills they may have.

As a community, we need to accept that as amazing as Mozilla (or any non-profit) is, most people will not spend their entire career there nor volunteer forever. Projects end. Challenges get old. New opportunities present themselves. And yes, people burn out on mission – which no longer means they don’t believe in it – they are just burned out. So let’s not alienate these people, let’s support them. They could be a killer advantage one of our most important advantages. (I mean, even McKinsey keeps an alumni group, and that is just so they can sell to them… we can offer so much more meaning than that. And they can offer us so much more than that).

How I would do it

At this point, I think it is too late to start a group and hope people will come. I could be wrong, but I suspect many feel – to varying degrees – alienated. We (Mozilla) will probably have to do more than just reach out a hand.

I would find three of the most respected, most senior Mozillians who have moved on and I’d reach out privately and personally. I’d invite them to lunch individually. And I’d apologize for not staying more connected with them. Maybe it is their fault, maybe it is ours. I don’t care. It’s in our interests to fix this, so let’s look inside ourselves and apologize for our contribution as a way to start down the path.

I’d then ask them if them if they would be willing to help oversee an alumni group. If they would reach out to their networks and, with us, bring these Mozillians back into the fold.

There is ample opportunity for such a group. They could be hosted once a year and be shown what Mozilla is up to and what it means for the companies they work for. They could open doors to C-suite offices. They could mentor emerging leaders in our community and they could ask for our advice as they build new products that will impact how people use the web. In short, they could be contributors.

Let’s get smart about cultivating our allies – even those embedded in organizations with don’t completely agree with. Let’s start thinking about how we tap into and help keep alive the values that made them Mozillians in the first place, and find ways to help them be effective in promoting them.

New Zealand: The World’s Lab for Progressive Tech Legislation?

6 Replies

Cross posted with TechPresident.

One of the nice advantage of having a large world with lots of diverse states is the range of experiments it offers us. Countries (or regions within them) can try out ideas, and if they work, others can copy them!

For example, in the world of drug policy, Portugal effectively decriminalized virtually all drugs. The result has been dramatic. And much of it positive. Some of the changes include a decline in both HIV diagnoses amongst drug users by 17% and drug use among adolescents (13-15 yrs). For those interested you can read more about this in a fantastic report by the Cato Institute written by Glenn Greenwald back in 2009 before he started exposing the unconstitutional and dangerous activities of the NSA. Now some 15 years later there have been increasing demands to decriminalize and even legalize drugs, especially in Latin America. But even the United States is changing, with both the states of Washington and Colorado opting to legalize marijuana. The lessons of Portugal have helped make the case, not by penetrating the public’s imagination per se, but by showing policy elites that decriminalization not only works but it saves lives and saves money. Little Portugal may one day be remembered for changing the world.

I wonder if we might see a similar paper written about New Zealand ten years from now about technology policy. It may be that a number of Kiwis will counter the arguments in this post by exposing all the reasons why I’m wrong (which I’d welcome!) but at a glance, New Zealand would probably be the place I’d send a public servant or politician wanting to know more about how to do technology policy right.

So why is that?

First, for those who missed it, this summer New Zealand banned software patents. This is a stunning and entirely sensible accomplishment. Software patents, and the legal morass and drag on innovation they create, are an enormous problem. The idea that Amazon can patent “1-click” (e.g. the idea that you pre-store someone’s credit card information so they can buy an item with a single click) is, well, a joke. This is a grand innovation that should be protected for years?

And yet, I can’t think of single other OECD member country that is likely to pass similar legislation. This means that it will be up to New Zealand to show that the software world will survive just fine without patents and the economy will not suddenly explode into flames. I also struggle to think of an OECD country where one of the most significant industry groups – the Institute of IT Professionals appeared – would not only both support such a measure but help push its passage:

The nearly unanimous passage of the Bill was also greeted by Institute of IT Professionals (IITP) chief executive Paul Matthews, who congratulated [Commerce Minister] Foss for listening to the IT industry and ensuring that software patents were excluded.

Did I mention that the bill passed almost unanimously?

Second, New Zealanders are further up the learning curve around the dangerous willingness their government – and foreign governments – have for illegally surveilling them online.

The arrest of Kim Dotcom over MegaUpload has sparked some investigations into how closely the country’s police and intelligence services follow the law. (For an excellent timeline of the Kim Dotcom saga, check out this link). This is because Kim Dotcom was illegally spied on by New Zealand’s intelligence services and police force, at the behest of the United States, which is now seeking to extradite him. The arrest and subsequent fall out has piqued public interest and lead to investigations including the Kitteridge report (PDF) which revealed that “as many as 88 individuals have been unlawfully spied on” by the country’s Government Communications Security Bureau.

I wonder if the Snowden documents and subsequent furor probably surprised New Zealanders less than many of their counterparts in other countries since it was less a bombshell than another data point on a trend line.

I don’t want to overplay the impact of the Kim Dotcom scandal. It has not, as far as I can tell, lead to a complete overhaul of the rules that govern intelligence gathering and online security. That said, I suspect, it has created a political climate that amy be more (healthily) distrustful of government intelligence services and the intelligence services of the United States. As a result, it is likely that politicians have been more sensitive to this matter for a year or two longer than elsewhere and that public servants are more accustomed at policies through the lens of its impact on rights and privacy of citizens than in many other countries.

Finally, (and this is somewhat related to the first point) New Zealand has, from what I can tell, a remarkably strong open source community. I’m not sure why this is the case, but suspect that people like Nat Torkington – and open source and open data advocate in New Zealand – and others like him play a role in it. More interestingly, this community has had influence across the political spectrum. The centre left labour party deserves much of the credit for the patent reform while the centre-right New Zealand National Party has embraced both open data. The country was among the first to embrace open source as a viable option when procuring software and in 2003 the government developed an official open source policy to help clear the path for greater use of open source software. This contrasts sharply with my experience in Canada where, as late as 2008, open source was still seen by many government officials as a dangerous (some might say cancerous?) option that needed to be banned and/or killed.

All this is to say that in both the public (e.g. civil society and the private sector) and within government there is greater expertise around thinking about open source solutions and so an ability to ask different questions about intellectual property and definitions of the public good. While I recognize that this exists in many countries now, it has existed longer in New Zealand than in most, which suggests that it enjoys greater acceptance in senior ranks and there is greater experience in thinking about and engaging these perspectives.

I share all this for two reasons:

First, I would keep my eye on New Zealand. This is clearly a place where something is happening in a way that may not be possible in other OECD countries. The small size of its economy (and so relative lack of importance to the major proprietary software vendors) combined with a sufficient policy agreement both among the public and elites enables the country to overcome both internal and external lobbying and pressure that would likely sink similar initiatives elsewhere. And while New Zealand’s influence may be limited, don’t underestimate the power of example. Portugal also has limited influence, but its example has helped show the world that the US -ed narrative on the “war on drugs” can be countered. In many ways this is often how it has to happen. Innovation, particularly in policy, often comes from the margins.

Second, if a policy maker, public servant or politician comes to me and asks me who to talk to around digital policy, I increasingly find myself looking at New Zealand as the place that is the most compelling. I have similar advice for PhD students. Indeed, if what I’m arguing is true, we need research to describe, better than I have, the conditions that lead to this outcome as well as the impact these policies are having on the economy, government and society. Sadly, I have no names to give to those I suggest this idea to, but I figure they’ll find someone in the government to talk to, since, as a bonus to all this, I’ve always found New Zealanders to be exceedingly friendly.

So keep an eye on New Zealand, it could be the place where some of the most progressive technology policies first get experimented with. It would be a shame if no one noticed.

(Again If some New Zealanders want to tell me I’m wrong, please do. Obviously, you know your country better than I do).

Beyond Property Rights: Thinking About Moral Definitions of Openness

2 Replies

“The more you move to the right the more radical you are. Because everywhere on the left you actually have to educate people about the law, which is currently unfair to the user, before you even introduce them to the alternatives. You aren’t even challenging the injustice in the law! On the right you are operating at a level that is liberated from identity and accountability. You are hacking identity.” – Sunil Abraham

I have a new piece up on TechPresident titled: Beyond Property Rights: Thinking About Moral Definitions of Openness.

This piece, as the really fun map I recreated is based on a conversation with Sunil Abraham (@sunil_abraham), the Executive Director of the Centre for Internet and Society in Bangalore.

If you find this map interesting… check the piece out here.

Open Data Day: Lessons for Hacktivists

Build Community

From the beginning our goal was simple. It wasn’t code, or even opening data per se. It was about community.

We wanted to foster a friendly event where anyone would feel welcome to participate. The team in Ottawa had, in particular, done great work in reaching out an engaging new people in previous hackathons, they’d have a wealth of non-software developers and even full families attend their events. This was as much a hackathon as it was a community event.

So Open Data Day was always meant to serve as a catalyst for community and network creation. Yes, creating, adding to or working on a project was strongly encouraged, but the real output to help open data advocates find and connect with one another, as well as grow the movement by engaging new people. An effective community was always going to be the core ingredient for petitioning a government to make data open, teaching students or policy makers how to use data or have a group of developers launch a project. While we wanted to create cool software, visualizations and analysis, what I wanted even more was to foster local leaders, champions, social glue and community hubs.

And that’s what we got.

One of the strengths of Open Data Day is its incredible decentralized nature. I blog about it to encourage people to organize and help moderate a mailing list, but beyond that everything is done by local volunteers. From a capacity building perspective, it is an incredible event to watch unfold. I’d like to think Open Data Day has played a helpful role in connecting local stakeholders and even knitting them together with regional, national and international peers.

While I believe that a beautiful piece of code can be critical in making policy makers, the public or others see the world in a different light I also think that building community and developing allies who can share that story of that code with leaders and the public at large is, depending on the breadth of your goals, equally important.

What Works for Communities Can Work for Governments

Almost immediately upon launch of Open Data Day, government officials began showing up at the hackathons. Some came unofficially, others officially, and in some places, the hackathons were invited to take place at city hall. Because we set a venue Open Data Day created a predictable publicized space where governments that were curious, reluctant, eager or cautious could come and engage at a speed that worked for them.

When you build a safe place for a broader community – if your event has more of the feel of a public consultation or community meet-up than a gathering of subversive technologists – you can create space for governments. More importantly, the one thing that characterizes most open data hackathons I’ve witnessed or investigated,is that the participants share a desire to make their community better. That is something most government officials can easily wrap their heads around.

Thus, in a way that I don’t think anyone planned, Open Data Day events have become a place where governments want to understand more of what is possible, learn about the community that is interested in data and wrestle with how open data can change the way they work. What began with a few pioneering cities three years ago has evolved where now places like the Victoria Palace in Romania (the seat of government) and the White House in Washington DC are hosting Open Data Day events.

This type of engagement creates new opportunities, and new challenges, but that is exactly the type of progress many movements would like to see.

Plant a Flag

Setting a date and having people around the world step up and embrace had another interesting impact. It created a deadline not just for community organizers who were organizing their local open data day event, but also for governments that want to engage these communities.

Indeed in the past it has been amazing to see how many governments now see Open Data Day as a deadline for launching open data portals or releasing additional data sets. This is a fantastic outcome as it creates subtle pressure on governments to act.

This year was no exception. I heard of governments around the world releasing data sets in anticipation of Open Data Day. In particular there was a flurry of activity from European governments and agencies. Indeed the European Union chose to launch its open data portal in time for Open Data Day. But there was also much activity across the continent. This included that launch of data portals for the Building Performance Institute Europe, the Italian Senate, the city of Venice , the city ofTrento, the region of Puglia in the south of Italy, and the province of Bolzano. But the practice has become widespread. I was particularly happy to see a city a few kilometers from my home town do the same: the City of Victoria, BC launched its Open Data portal for the day.

These announcements show the amplifying effect of getting organized across geographies. The advocacy work of a group in one country helps reinforce a message that benefits advocates in other countries. This is pretty basic stuff — political advocacy 101 if you will — but it is a reminder of why congregating around a single date, and meeting in person still have value for those who are unpersuaded.

Ultimately Open Data Day is important because it serves the needs of local advocates and activists wherever they are. That means keeping the event coherent so that it can continue to be a global event that people understand, yet flexible so that it can satisfy local needs and desires. For example, the event in Manila focused on poverty while in Washington DC it focused on building community and capacity. These types of events are not, in of themselves, going to completely solve a problem, but I do believe that they are part of a broader political effort that activates a community, engages government and creates pressure for change.

Open Data Day 2013 in Vancouver

2 Replies

Better late than never, I’m going to do a few posts this week recapping a number of ideas and thoughts from Open Data Day 2013. As is most appropriate, I’m going to start the week with a recap of Vancouver – the Open Data Day event I attended and helped organize along with my friend Luke Closs and the very helpful and supportive staff at the City of Vancouver – in particular Linda Low and Kevin Bowers. I’ve got further thoughts about the day in general, its impact and some other ideas I’ll share in subsequent posts.

Vancouver! 2013!

What made Open Data Day in Vancouver great for me was that we had a range of things happen that really balanced time between “creating” (e.g. hacking) and engagement. As a result I’m diving this blog post into three parts: setting the scene, engagement and outcomes as well as sharing some lessons and best practices. My hope is that the post will make for fun reading for regular readers, but the lessons will prove helpful to future open data day organizers and/or plain old hackathon organizers.

Setting the scene

Despite competing with a somewhat rare sunny day in Vancouver at this time of year we had over 80 participants show up at City Hall, who graciously agreed to host the room. Backgrounds varied – we had environmentalists, college and university students, GIS types, open street mappers, journalists, statisticians among others. In addition, the city’s administration made a big commitment to be on hand. Over 20 staff were present, including one of the Deputy City Managers and a councillor – Andrea Reimer – who has been most active and supportive on the Open Data file. In addition we had a surprise guest – Federal Minister Tony Clement, who is the minister responsible for Open Data with the national government.

Our event was fairly loosely organized. We had a general agenda but didn’t over script anything. While Luke and I are comfortable with relatively flexible agenda for the day, we knew the unstructured nature of the event was a departure for some from the city and were grateful that they trusted us both with the format and with the fast, loose and informal way we sought to run the day.

Here are some high level lessons:

When Possible host it Somewhere Meaningful. City Hall is always nice. Many attendees will have never engaged with local government before, this creates a space for them to learn and care about municipal government. It also reaffirms the broader culture changing and social/change oriented goals of an open data hackathon. Besides, who isn’t welcome at City Hall? It sets a great tone about who can come – which is pretty much anyone.
Give the Politicians Some Room. Don’t be afraid to celebrate politicians and leaders who have championed the cause. Hackathons are about experimenting, not talking, so Andrea’s five minute talk at the beginning was the right mix of sincere engagement, enthusiasm and length.
Don’t Only Attract Software Developers. Vancouver’s event was in part a success because of the diversity of participants. As you’ll see below, there are stories that emerged because we tried hard to engage non-software developers as well.
Transit. This may sound obvious but… if you want to attract lots of people make it convenient to get to. We right off the subway line – City Hall is pretty central.
RSVP. We did one thing wrong and one thing right. On the wrong side, we should have allowed more people to register recognizing that not everyone would show. We’d turned people away and ended up having room for them because of the no shows. On the right side, we blasted our list to see if anyone wasn’t going to come at the last minute and, got some responses, which allowed us to re-allocate those seats.

Engagement: Open Dataing

The one thing both Luke and I were committed to doing was getting participants and city staff to talk to one another. Building off an idea Luke witnessed in Ottawa we did 45 minutes of Open “Dataing.” During this period city staff from about eight different departments, as well as Minister Clement, staked out a part of the room. We then had people cluster – in groups of about 5-7 – around a department whose data or mission was of interest to them. They then had 10 minutes to learn about what data was available, ask questions about data they’d like, projects they were thinking of working on, or learn more about the operations of the city. In essence, they got to have a 10 minute speed date on data with a city official.

After 10 minutes blew a whistle and people went and clustered around a new official and did it all over again. It was a blast.

Key Lessons:

Open Dataing is about getting everyone engaged. Helping public servants see what citizens are interested in and how they can see technology working for them, it’s also about getting participants to learn about what is available, what’s possible, and what are some of the real constraints faced by city staff
I wish we’d had signs for the various departments being represented, would have made it easier for people to find and gravitate towards the issues that mattered most to them.
This type of activity is great early on, it’s a way to get people talking and sharing ideas. In addition, we did the whole thing standing, that way no one could get too comfortable and it ensure that things kept flowing.

Outcomes

After the dating, we did a brief run through of projects people wanted to work on and basically stepped back and hacked. So what got worked on? There were other projects that were worked on, but here are the ones that saw presentations at the end of the day. There are some real gems.

Bike Parking App

The Bike Rack app came out of some challenges about data gathering that Councillor Reimer shared with me. I suggested the project and a team of students from UBC’s Magic Lab turned it into something real.

The city recently released a data set of the locations of all city owned bike racks. However, the city has little data about if these locations are useful. So the app that got hacked is very simple. When you arrive at your destination on bike you load it up and it searches for the nearest bike rack. For the user, this can be helpful. However, the app would also track that lat/long of where the search was conducted. This would let city planners know where people are when looking for bike rack so they would start to have some data about underserved locations. Very helpful. In addition, the app could have a crowdsourced function for marking the location of private bike racks (managed by businesses) as well as an option to lat/long where and when your bike was stolen. All this data could be used to help promote cycling, as well as help the city serve cyclists more effectively.

Homelessness Dashboard

My friend Luke connected a Raspberry Pi device to one of the giant TVs in the room where we were working to share the work he had done to create a dashboard based on the city’s rental standards database. Luke’s work even got featured on the Atlantic’s website.

Crime mapping – lots of quality questions

One great project involved no software at all. We had some real data crunchers in attendance and they started diving into the Vancouver Police Department’s data with a critical eye. I wish the VPD could have been there since their conclusions were not pretty. The truth is, the Vancouver Police department makes very little data open, and what it does make, is not very good. What was great to see were some very experienced statisticians explain why. I hope to be able to share the deck they created.

Air quality egg

A few weeks prior to Open Data Day I shared that I’d be launching a project – with the help of the Centre for Digital Media – around measuring air quality in Vancouver. Well, the air quality egg we’d ordered arrived and our team started exploring what it would, and might not, allow us to do. The results were very exciting. Open Data Day basically gave us time to determine that the technical hurdles we were worried about are surmountable – so we will be moving forward.

Over the coming months we’ll be crafting a website that uses Air Quality Eggs to measure the air quality in various neighborhoods in Vancouver. We have a number of other community partners that are hoping on board. By Clean Air Day we’d love to have 50-100 air quality eggs scattered across various neighborhoods in greater Vancouver. If you are interested in sponsoring one (they are about $150) please contact me.

Youth Oriented events RSS feed

One intrepid participant, also not a developer, got the city to agree to create and share an RSS feed of youth oriented events. This was important to them as they were concerned with youth issues – so a great example of a community organizer getting a data resource from the city. Next steps – trying to get other organizations with youth organized events to agree to share their program data in a similar data schema. What a great project.

Provincial Crowdsourced Road Kills and Poaching Maps

I was very excited to have to participants from the David Suzuki Foundation at the hackathon. They worked on creating some maps that would allow people to crowdsource map road kills, and instances of poaching, across the province of British Columbia. I love that they had a chance to explore the technical side of this problem, particularly as they may be well placed to resolve the community building side that would be essential to making a project like this a success.

Neighbourhood quality Heat Maps

Another team took various data sets from the Vancouver Open Data portal to generate heat maps of data quality (proximity to certain services and other variables). This prompted a robust conversation about the methodologies used to assess quality as well as how to account for services vs. population density. Exactly the types of conversations we want to foster!

Figuring our how to translate all of the data.vancouver.ca datasets

Another participant Jim DeLaHunt – put in some infrastructure that would make it easier to translate Vancouver’s open data into multiple languages in order to make it more accessible. He spent the day trying to identify what data in which data sets was structured versus unstructured human readable text. And… much to his credit he created a wiki page, the Vancouver Open Data language census to update people on his work so far.

Live Bus Data Mapped

Another team played with the local transit authority’s real time bus data location API. It was pretty cool to see the dots moving across a google map in real time.

Their goals were mostly just to experiment, play and learn, but I know that apps like this have been sold into coffee shops in Boston, where they let customers know how far away the next bus.

Open Street Map

A Open Street Mapper participant spent the data getting address data merged with OSM.

Key Lessons:

Don’t try to over manage the event – give people space and time to create
Even if the energy feels low after a long day – definitely share out what people worked on, even if they didn’t finish what they wanted. There is lots to be learned from what others are doing and many new ideas get generated. It was also great for city staff to see what is possible
Get people to share github repos and other links while on site. Too many of the above projects lack links!

Thank you again for everyone who made Open Data Day in Vancouver a success! Looking forward to next year!

Community Managers: Expectations, Experience and Culture Matter

3 Replies

Here’s an awesome link to grind home my point from my OSCON keynote on Community Management, particularly the part where I spoke about the importance of managing wait times – the period between when a volunteer/contributor takes and action and when they get feedback on that action.

In my talk I referenced code review wait times. For non-developers, in open source projects, a volunteer (contributor) will often write a patch which they must be reviewed by someone who oversees the project before it gets incorporated into the software’s code base. This is akin to a quality assurance process – say, like if you are baking brownies for the church charity event, the organizer probably wants to see the brownies first, just to make sure they aren’t a disaster. The period between which you write the patch (or make the brownies) and when the project manager reviews them and say they are ok/not ok, that’s the wait time.

The thing is, if you never tell people how long they are going to have to wait – expect them to get unhappy. More importantly, if, while their waiting, other contributors come and make negative comments about their contributions, don’t be surprised if they get even more unhappy and become less and less inclined to submit patches (or brownies, or whatever makes your community go round).

In other words while your code base may be important but expectations, experience and culture matter, probably more. I don’t think anyone believes Drupal is the best CMS ever invented, but its community has a pretty good expectations, a great experience and fantastic culture, so I suspect it kicks the ass of many “technically” better CMS’s run by lesser managed communities.

Because hey, if I’ve come to expect that I have to wait an infinite or undetermined amount of time, if the experience I have interacting with others suck and if the culture of the community I’m trying to volunteer with is not positive… Guess what. I’m probably going to stop contributing.

This is not rocket science.

And you can see evidence of people who experience this frustration in places around the net. Edd Dumbill sent me this link via hacker news of a frustrated contributor tired of enduring crappy expectations, experience and culture.

Heres what happens to pull requests in my experience:

you first find something that needs fixing

you write a test to reproduce the problem

you pass the test

you push the code to github and wait

then you keep waiting

then you wait a lot longer (it’s been months now)

then some ivory tower asshole (not part of the core team) sitting in a basement finds a reason to comment in a negative way.

you respond to the comment

more people jump on the negative train and burry your honestly helpful idea in sad faces and unrelated negativity

the pull dies because you just don’t give a fuck any more

If this is what your volunteer community – be it software driven, or for poverty, or a religious org, or whatever – is like, you will bleed volunteers.

This is why I keep saying things like code review dashboards matter. I bet if this user could at least see what the average wait time is for code review he’d have been much, much happier. Even if that wait time were a month… at least he’d have known what to expect. Of course improving the experience and community culture are harder problems to solve… but they clearly would have helped as well.

Most open source projects have the data to set up such a dashboard, it is just a question of if we will.

Okay, I’m late for an appointment, but really wanted to share that link and write something about it.

NB: Apologies if you’ve already seen this. I accidentally publishes this as a page, not a post on August 24th, so it escaped most people’s view.

Beautiful Maps – Open Street Map in Water Colours

3 Replies

You know, really never know what the web is going to throw at you next. The great people over at Stamen Design (if you’ve never heard of Stamen you are really missing out – they are probably the best data visualization company I know) have created a watercolor version of Open Street Maps.

Why?

Because they can.

It’s a wonderful example of how you, with the web, you can build on what others have done. Pictured below my home town of Vancouver – I suggest zooming out a little as the city really comes into focus when you can see more of its geography.

Some Bonus Awesomeness Facts about all this Stamen goodness:

Stamen has a number of Creative Commons licensed map templates that you can use here (and links to GitHub repos)
Stamen housed Code for America in its early days. So they don’t just make cool stuff. The pitch in and help out with cool stuff too.
Former Code for America fellow Michael Evans works there now.

eaves.ca

if writing is a muscle, this is my gym

Category Archives: free culture

Open Data Day Google+ Hang Out

Open Data Day 2014 is Coming Feb 22 – Time to Join the Fun!

A) How can I let EVERYONE know about open data day

B) I’d like to participate!

C) Forget about participating, I want to coordinate an Open Data Day event in my city.

D) I want to help more! How can Open Data Day work more smoothly everywhere?

What’s next?

Access to Information, Technology and Open Data – Keynote for the Commissioners

Mission Driven Orgs: Don’t Alienate Alumni, Leverage Them (I’m looking at you, Mozilla)

The Opportunity

How I would do it

New Zealand: The World’s Lab for Progressive Tech Legislation?

Beyond Property Rights: Thinking About Moral Definitions of Openness

Open Data Day: Lessons for Hacktivists

Build Community

What Works for Communities Can Work for Governments

Plant a Flag

Open Data Day 2013 in Vancouver

Community Managers: Expectations, Experience and Culture Matter

Beautiful Maps – Open Street Map in Water Colours