On Tue, 31 May 2011 21:32:31 +0200 Hans-Peter Diettrich <[email protected]> wrote:
> Mattias Gaertner schrieb: > > > The writers don't earn much money. Writing a book is a lot of work and > > you have to sell a lot of books, before it pays out. > > True, in detail for all technical writing :-( > > > OTOH having a book helps the project and therefore the coders. > > How does it help, and exactly whome? It helps when telling people about the project. You can say: ... and there is a book about it. This makes a difference. Sometimes a big one. And in this particular case: Many writers of the Lazarus books are in the FPC and/or Lazarus development teams. So there is no real distinction between writers and coders here. > Good documentation encourages the *use* of the project, but how should > this help the project coders? There are less boring questions. > It would increase the acceptance of a project a lot, when somebody wrote > a book *before* the coding starts, and then the project is made usable > in the outlined way. Writing books about all those nasty problems, that > arise from the installation, configuration and use of FPC/Lazarus, on > the various supported platforms, IMO doesn't make much sense, because > they will be outdated within weeks :-( I doubt that. For example each time the debian package maintainers apply more of the debian policies, there are new problems/questions coming to us. They simply ignore our outlined way. The windows installer is not perfect too. Mattias -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
