bobby wrote: > They are separate issues, but there is a common thread running through > both. For example, remembering that "SDCC is a free software", or "feel > free to do better if you can", doesn't provide me with a lot of comfort. > Statements such as these recognize, explain and/or excuse the existence > of the problem, but do nothing to address it, but rather introduce the > final exit, which usually looks something like this: "If you want better > documentation, why don't you write it yourself", which of course is > loaded with all kinds of contradictions. > > 1) It fails to address the problem.
how? it suggests that someone who understands that there's a problem should help solve that problem. > 2) Such requests typically come from _users_, not necessarily developers. who better than a user to help with documentation? after all, it's users that know what questions need to be answered. > 3) They feign an interest in solving the problem, but inspire no one. you're completely overlooking one of the fundamental premises of open source: people work on what it pleases them to work on. if a developer is motivated by zillions of very happy newbie users, then they'll probably work on docs as well as code. if they don't care about anything except making a working program, perhaps mainly for their own use, then they may just work on code. if someone feels that making the program especially easy to _use_ is important, they may just work on docs. these people all do what they do because it scratches an itch. > 4) As a user, my input to the project (such as this offering and > previous ones) is swept under the carpet as a 'gripe' or 'complaint'. your input, i'm sure, is noted. but actions speak much louder than words. have you offered to help improve the docs? have you created patches to modify or improve the help text? i suspect such changes would be warmly received, and might even inspire a developer to notice other areas that need improving. > 5)et al, and etc. > > Am I mistaken or have I observed somewhere that opensource projects > frequently have at least the semblance of an hierarchical management > organization? some do. some don't. have you ever worked in an all-volunteer organization? perhaps a local civic club, or similar unpaid group? you can't _make_ anyone do something. and if someone _wants to do something, it might not be quite what the "organizers" (whoever they may be) want done. but often they'll be willing to let that person go, because, after all, they're the one doing the work. an open source project is essentially a volunteer organization. you can only influence its outcome by helping. criticism, or constant sideline comments, almost never help. paul =--------------------- paul fox, [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
