Hi Christian, *,

[...]
The work Per is doing is not for the developers we already have it is
probably more for new ones.

Probably that's another part of the problem I have. This makes it
sound like there wouldn't be any documenation for new builders at all.
That's just not the case.

There's additional value in what Per was doing: removing obsolete instruction concerning CVS etc. Note: I was unable to find a good page about SVN just two months ago in OOo wiki, and I've seen that most of the build instructions were really outdated as they didn't point to real sources. If you think that having instruction which is completely off the mark is OK, then you probably don't understand the point of having documentation.

Note: documentation is just what it is, it documents the current processes. It cannot simplify them. Maybe OOo should move to more standard build tools: this comes up in conversation quite a lot, and maybe standard autoconfigure tools would work. But migrating to a complete new set of build tools is a major project for many people, and probably not worth the effort.

Idiots will of course stay idiots and will ask stupid questions. But there is one thing you do in such a case: you create a FAQ and put the link to the FAQ instead of answering all that stupid questions.

Regards
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to