M. Fioretti a écrit : > [snip] On one hand, I know enough these days to > (almost) never create personally the problem we're talking about. On > the other hand, I am not skilled enough to compile such a list, > certainly not as much as Wietse or others here who probably already > have such a list in their mind and/or could write it down in very > little time. > > If I don't create the problem and don't know enough to *implement* the > solution myself and both of these things were already said, why should > you think that *I* could be the one able to *implement* it myself, > only because I'm the one who *suggested* it (***)? >
don't take it personally. it's a common reply that generally means "sure, but it requires volunteers". > It's like if a child saw a big rock blocking the street and, > suggesting to a passing-by body builder that he may easily remove it, > were told by a third person "why don't you move it yourself?" > > (***) again, please note that mine was and remains a *suggestion*, I'm > not demanding that anybody does this now or anything like that. > > Never mind, really, let's move on. > > Marco yes, it's a good suggestion. unfortunately, writing such list requires work. otherwise, the list quality would be bad, and thus worst than not having a list. The "decentralized howto model" is problematic. while you can talk about a printed book, it's hard to talk about (sometimes unversioned) moving targets. a bad howto may become good if the author updates it. a good howto may become bad if the author (or contributors) introduce errors or bad ideas. note that the wiki you mentioned was built to get people to write docs there. but as you can see, not much volunteers... and there's another problem. many users won't find the list anyway. Most people visit the site of their OS or distribution. some will google, but without experience, it's not easy to use the right terms in the search query. others will use "reasonably good" terms, but won't have enough experience to quickly ignore "unuseful" links so as to have the opportunity to visit useful ones... and let's not even speak of people who are in a hurry to get "something running" and won't read docs (they will copy paste lines from here and there). so, yes. good docs are good, and it's good to have as many of them as possible. nobody disagrees on that.
