Making an Open Source Project Press-Friendly
blackbearnh writes "Corporations know that part of launching a successful project is projecting the right image to the media. But a lot of open source projects seem to treat the press as an annoyance, if they think about it at all. For a reporter, even finding someone on a project who's willing to talk about it can be a challenge. Esther Schindler over at IT World has a summary of a roundtable discussion that was held at OSCON with pointers about how open source projects can be more reporter-accessible. 'Recognize that we are on deadline, which for most news journalists means posting the article within a couple of hours and for feature authors within a couple of days. If we ask for input, or a quote, or anything to which your project spokesperson (you do have one? yes? please say yes) might want to respond, it generally does mean, "Drop everything and answer us now." If the journalist doesn't give you a deadline ("I need to know by 2pm"), it's okay to ask how long you can take to reach the right developer in Poland, but err on the side of "emergency response." It's unreasonable, I know, but so are our deadlines.'"
Simply put, FOSS developers usually fall into one of two categories: hackers coding in their spare time and those who work on FOSS projects as part of their job. Those in the former category likely have day jobs, and are already short on time. They do this as a hobby, and if their spare time is spent coding, they don't necessarily have spare time to devote to commenting for reporters. The latter category is contributing code as part of their job. They likely don't have the authority to comment on the record regarding their work, or they have to get permission from the marketing trolls to do so. Either way, if you're getting a response, it's not likely to be quick.
The lesson here is plan ahead. As soon as you know you're going to be working on a story, start asking for comments. If you wait until the last second, you're likely to not get a reply. Yes, reporters can get short deadlines, but you can't expect volunteers contributing their spare time to jump at your say-so, and you have to allow time to get the corporate wheels rolling in the latter case.
The summarizer says:
But a lot of open source projects seem to treat the press as an annoyance...
And the press-person says:
'...it generally does mean, "Drop everything and answer us now." If the journalist doesn't give you a deadline ("I need to know by 2pm"), it's okay to ask how long you can take to reach the right developer in Poland, but err on the side of "emergency response." It's unreasonable, I know, but so are our deadlines.'
Wow, I can't imagine why volunteer developers consider the press an annoyance. Maybe the press should cut back on the 30-second deadline and take some time to actually get facts, instead of getting something out the door now, even if it isn't right. I think that journalists with this attitude are probably in the wrong business -- you should be doing research and finding the story, not demanding that a non-storyteller drops what they're doing to give you the story on a silver platter. Software only appears to move quickly...in reality, businesses are slow to adopt new software these days. Taking the time to do thorough research on an open source project will not kill the press, just like waiting a few weeks for a story on a software project will not kill the software project.
Me, I would prefer to read the right story than the first story. I wish that the press' job to make sure that the right story is the first story...but that shall continue to be my wish.
The Right Reverend K. Reid Wightman,