Preserving The Sunlight On Github13 Oct 2016
I'm following along as the Sunlight Foundation winds down their operations and gathering any lessons along the way, that can help us open data and transparency folks can learn from as we do our work. I wrote earlier that we should be learning from the Sunlight Foundation situation and that we are making sure we bake transparency into our projects and wanted to continue to extract wisdom we can reuse as they turn out the lights.
The Sunlight Foundation shared that they are working with the Internet Archive and Github to preserve their projects, and that they are "trying to ensure the open source community can understand and use our projects in the future" by:
- adding documentation
- standardizing licenses
- scrubbing sensitive info
This is the benefits of being transparent and open by default is that you tend to do all of this in real-time. If you are in the business of opening up data, making it accessible with open APIs, you should be using Github, documenting, and telling the story as you go along. Then you do not have to do it all when you are walking away--everything is open by default.
This is why I work out in the open on Github each day, it allows people to take my tools like the CSV Converter, and the API Stack, and put them to work, even as I'm still evolving them. When I step away from a project, it can continue to live on with all the code, definitions, schema, data, licensing, and the story behind in a nice forkable package--no extra work necessary.
Anyways, just a couple of nuggets to consider as we are working on open data and API project across the space.