This isn’t just about holding the event. We have to develop a framework that allows technology activists to donate their code to the Public Good App House. To that end, we are meeting with creative commons to get an appropriate license which is one way that we can explicitly identify donation. We also need to describe how this donation will work in the field.We believe that challenges are a tool that can create urgency. We’ve used in the past to incent people to surface their work and to help provide funding so that that work can move forward. We have some open questions about using challenges in this model:Is money the best incentive? Research would indicate that paying volunteers depresses volunteerism. So, in this model, we want to do things that contribute to the reputations and connections of volunteers. This might include: creating badges that allow participants to identify themselves as contributors, ensuring that credit to the original development team persists in all versions of the apps, partnering with an organization like LinkedIn to create some recognitions that can so up on that site, partnering with corporations to provide access to a community of experts to showcase the developed appsHow done do we need an app to be to take it on?Can the original engineers serve as some kind of advisory committee?
Safe Night is done with seed funding from Microsoft but with support from other corporations and foundations as well – Vodafone Americas Foundation, Blue Shield of California Foundation. In addition, we are continuing to do fund development.The project as an advisory group that includes community members. We are currently in the process of finalizing development.We are also selecting the pilot group and getting them the necessary information to bring them on to the project.Finally, as we’ve talked about this with broader community members, we’ve identified two other places for development:Human traffickingParoleesWe are also going to fund the quick development of some small apps for the domestic violence, and adjacent communities – the first will be a panic button that works as a web part in sharepoint.
This is still very nascent but we know that it’s something that we are hearing and we would like to begin exploring so that we can understand what is necessary for this to work.
The wiki is a repository. But we need a way that people can vote up a particular problem as one that has more urgency around it. We also need to make sure that these problem identifications stay open enough to have a robust set of possible solutions. This isn’t a place, necessarily, for one-to-one development of solutions.Building out from adjacent communities. Providing feedback to those communities when apps are developed and adopted.Donating code is a discrete act that we can ask people to do. But how do we judge that code and then finish it? It seems like takes a community of engineers who would be willing to provide feedback in certain areas. I think there are some open source governance models that could apply here (imagine in different technical areas we have a board who votes on whether a set of code will be committed, so to speak, to the public good app house; which begs the question of what we do with the rest of the code).We are building these initial processes in ways that will help us define that.
How can we create anenvironment in which NGOs caninform the development of apps? And benefit from them?
We are going to define a repeatablemethodology to organize input from thesector.
We will use that information to get appsfrom three main places.1. Technology activists.2. Community-identified and funded development.3. Corporate donations.
1. Technology activists.• Partner with Random Hacks of Kindness, Code for America, Campus Party and other event organizers.• Hold our own hackathons • In partnership with a corporation • In partnership with an NGO• Use challenges to incent development in certain categories.
2. Community-identified and fundeddevelopment.
3. Corporate donations• License apps that have been created for social good.• Development of community-identified products.• Provide input from the field to CSR efforts.
There are two big areas to tackle withregard to scale.• Broad-based NGO input.• Engineering oversight and quality control.
We also need to closely monitorsustainability.• Distribution in the TechSoup Global marketplace.• Cost of maintaining and enhancing a variety of code.• Cost of managing community donations and input.• Define adoption as more than a download.