ONA Issues — The Meta-Story: How Wired Published Its GitHub...

ONA Issues

var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-6125049-7']); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); There are any number of pressing media issues in the digital age -- we're sure you can come up with a handful without breaking a sweat. ONA Issues is your platform to define them, share them, explore them and get a better fix on how they impact the work you do. Here we'll look to you for your perspectives and conversations and help jump-start discussions by posting insightful reporting, commentary and analysis from anywhere and everywhere. We're here to listen and learn. Join us.

The Meta-Story: How Wired Published Its GitHub Story on GitHub | Wired.com

“When we uploaded the story to GitHub, we published it under a Creative Commons license, and this allowed GitHub’s 1.3 million users to do what they do best: download their own version of the article — called a fork in GitHub parlance — mess around with it, and then offer the changes back to us via the website.

Read how the experiment went on Wired.

Image: GitHub

See onaissues's whole Tumblr