Tag: reportingon

by Ryan Sholin

In 2008, I was awarded a Knight News Challenge grant to build ReportingOn, a back channel for beat reporters to share ideas, information, and sources. The goal of the project was to provide journalists of all stripes with a place to talk about content — not craft, or process, or skillset. I taught myself enough […] more »

by Ryan Sholin

Since ReportingOn launched with a new Question & Answer format in July 2009, a few new entries in what I’ll call the Q&A 2.0 space have popped up and grown their base of users. Here’s a look at three Q&A 2.0 applications with wide appeal. Aardvark Aardvark allows users to ask questions via instant message, […] more »

by Ryan Sholin

Those of you who have been keeping score surely noticed that I’ve saddled the iteration of ReportingOn that launched late on July 1 with a “2.0” label when I talk about it. Many of you might remember what the backchannel for beat reporters looked like before the clock struck “late” on July 1: Home_logged_in_400 That’s […] more »

by Ryan Sholin

ReportingOn 2.0 is live and ready for your questions. And answers. It’s still the backchannel for your beat, but it’s an absolute re-imagining of the network. For those of you who haven’t been keeping score, ReportingOn is a project funded by the Knight News Challenge, and it’s a place for journalists of all stripes to […] more »

by Ryan Sholin

Here’s an eight-minute tour of ReportingOn 2.0, as it stood on our development server on Tuesday June 17, 2009. I’m extremely psyched to report that we’re on track for a July 1 launch of the second phase of this Knight News Challenge funded project. As a quick refresher, ReportingOn 1.0 launched back in October 2008, […] more »

by Ryan Sholin

It’s been a busy few weeks for ReportingOn, with development of Phase 2 continuing behind the scenes, and a lot of public conversation about the network’s start and continuation as I’ve traveled to San Jose and Philadelphia in recent days. In San Jose, I gave a short talk on ReportingOn as part of my requirements […] more »

by Ryan Sholin

When I last wrote here to report on ReportingOn progress, I talked about the work I was doing with my development and design team to define the terms of the RO pitch. A dozen or so whiteboards later, the Lion Burger team is actively putting together mockups and the beginnings of the database for what […] more »

by Ryan Sholin

[I’m going back to the proverbial drawing board for ReportingOn, working with the development and design team at Lion Burger to build the next iteration of the backchannel for your beat from scratch, more or less. Here’s some of what we’re talking about in front of the whiteboard…] I’ve been pitching ReportingOn using the same […] more »

by Ryan Sholin

DIY development, design, community management, and marketing isn’t for me (this year). This is an update about what’s going on with ReportingOn, which is to say, there’s not much going on with ReportingOn. For now. My Knight News Challenge-funded project to connect journalists on the same topical beat with their peers launched on October 1. […] more »

by Ryan Sholin

I thought about ReportingOn for more than a year before the public beta launched on October 1; I turned the idea over in my head, scrawled back-of-a-napkin sketches, and built several HTML prototypes before I ever got close to building something with dynamic code. While I was going through that process of refining the idea […] more »