[mythtv-users] MythFrontend 0.21: What is a watch list?

[match at ece.utah.edu]

On 11 Mar 2008 at 19:15, Brad DerManouelian wrote:

> My point is that if dev spent 1/3 their time writing doc instead of  
> coding and fixing bugs, we'd have only 2/3 of a complete system. Tons  
> of people complained that 0.21 took so long to release. Imagine if  
> they had to wait for dev to catch up on doc as well.

Point taken. 

For the record, while I've been anxiously looking forward to this release, I've 
not complained (not that you're accusing me personally.)
> 
> Also, OpenSource is the only type of software development process I've  
> ever seen where developers were expected to provide end-user  
> documentation.

We (the community at large) assume that the dev is the only person who 
CAN document his work. After all, we were not by your side during the 
creation process, so what do we know about it? (My understanding of the 
subject, I'm not really qualified to speak for "the community", and nobody 
elected me king.)

Whether real or percieved there is a disconnect. Please help me if I'm wrong 
here.

> The software companies I've worked for would fire any  
> developer who tried to give doc to end users without going through a  
> tech writer.

Another good point. But open source is not the "real world". When creating 
software for a company the dev and the tech writer are part of the same 
team, aren't they? Don't they collaborate on the documentation? (I'm asking 
because I don't know.)

On the other hand, a dev working on an open source project doesn't have 
the luxury of an on board tech writer, so there is no option but to write the 
docs himself. (I'm guessing here, since I'm not a developer. Correct me if I 
have it wrong.)
> 
> Please don't point out where I'm clearly wrong and that other  
> companies have dev write doc.

Before we all run over a cliff here, if anything I've written has offended you, 
then I am deeply sorry. It is certainly not my intention. I have nothing but 
gratitude for all the devs, writers, packagers, et all, and I'm mortified to think 
that my comments might have been taken in the wrong light.

> I'm speaking from my personal experience  
> of the admittedly short 8 years working for software companies.

So this is where the rubber meets the road, eh? Tell you what, I would be 
OVERJOYED to lend a hand with the documentation. I'm willing to put my 
money where my mouth is. I'm not a tech writer, but I have a fair command 
of the language.

All I need is some _very pointed_ guidance to do it. I can only write about the 
things I'm aware of, so to all the devs, this is an open invitation. If you want 
ME to help YOU write the documentation for YOUR work, I'm happy to give it 
a shot. (small assignments first, please)

Where to begin? (please don't say wiki)

Marvin