From: Gregory Brown Date: 2007-07-16T01:53:25+09:00 Subject: Re: graphing/charting application On 7/15/07, Chad Perrin wrote: > > I'm sure that Geoffry would appreciate documentation patches. > > Sure . . . just as soon as I figure out how to use the library. With the > information that's provided, I could probably sort out how to create > simplest-case line graphs, but beyond that I'd have to put real time into > it -- time I might prefer to spend on Scruffy, which it appears has > better documentation. This might sound rude, but I don't intend it to be offensive. What makes you think maintainers of weakly documented projects care whether or not *you* use their software? It really irks me when people whine about lack of documentation for projects. Yes, it sucks, yes it makes it harder for general adoption of projects, but that burden isn't necessarily on the original developer's shoulders. Free software is a gift. It's also a collaborative effort. If I release an undocumented library and people who are skillful enough and have sufficient time to read the source can make use of it, great. If someone wants to help document the software to show appreciation for my work and learn in the process, as well as provide a resource for others, even better. What people forget to consider or refuse to consider is that adding features to software or fixing bugs benefits the developers directly. Writing documentation *might* benefit them, but often the folks who write these things are very busy and are already working on other important things, so documentation doesn't get written. It's fine to say "I don't have the time to learn this undocumented lib" and move on to another one, but criticizing projects for not being documented is a baseless argument. You're asking why volunteers don't volunteer more of their time to make *your* life easier, instead of helping things along or at least *shutting up* when you're not happy. I apologize for a mini-rant here, but users who think project maintainers owe them something really suck.