As a Knight-Mozilla fellow, I wanted to do some type of research during my fellowship that could benefit the news community. During my 10-month fellowship in Berlin in 2016, I spent about eight months researching, collecting data and interviewing reporters, editors, managers, and directors about their on-boarding and off-boarding processes.
This week, eleven contributors gathered with us in Washington, D.C. to work on a new resource—a playbook for open-sourcing newsroom code. Together we hoped to tackle a question that’s come up again and again: how to help more newsrooms produce open-source projects, so that everyone can spend more time on great journalism instead of re-creating common tools, tech, and datasets from scratch.
Three SRCCON participants share notes and learnings from this year’s conference in Portland.
Source is in Portland this week for SRCCON 2016. Here’s how you can follow along with us.
Don’t let a debrief go to waste. The SF Chronicle’s Michael Grant explains how to dig deeper, solve longstanding communication problems, and support the development and implementation of new ideas.
Vox’s director of editorial products on how to set up the processes you need to run healthy projects and a jubilant team.
Good docs help people use your work, but they have other benefits too. They encourage community contributions. They save you from your past self when you’re revisiting your own code six months from now. And they help you think: much like talking to a rubber duck helps you find bugs, carefully documenting your work for users helps you see it from a different perspective and design better code.
Yesterday morning, the ProPublica apps team released a series of documents outlining their coding philosophy, app design and development practices, data validation techniques, and more. We spoke with Scott Klein about how his team’s processes evolved and how they made the time to document it all.
News startups in and around Georgia helped improve search in Newscoop content management system using Solr.