Hi Christian,
Christian Lohmaier skrev:
Hi Per, *,
On Wed, Jul 15, 2009 at 11:09 AM, Per
Eriksson<pereriks...@openoffice.org> wrote:
Having a building guide would simplify and make it easier for new developers
to find articles and getting to the right pages faster by providing the
navigation as in the developer guide.
I beg to differ. You don't need a guide. The people who try to build
OOo and fail are those who don't bother to read instructions. Even a
step-by-step instruction explicitly written to match their system
wouldn't help in that case. But that's another story.
I have another view there, which is why founded this initiative.
http://wiki.services.openoffice.org/wiki/Development/Simplifying_entry_for_new_developers
It is based on my own experience when I first started to get interested
in OpenOffice.org.
If a developer cannot find the building information it is probably
because there they can't find the information, or that there are too
many documents, including documents with wrong information. New
documents are written because they cannot edit the CVS documents etc.
Of course this initiative includes:
- Updating links to the new content
- Provide redirects
- Promoting this guide on all the places where content is currently placed.
This work would be done by sorting, consolidating and editing the various
wiki pages into a guide with a structure.
I dislike the idea to have a huge guide.
Actually after this work is done, the content will be much smaller than
what we have today, it will provide better navigation etc. Plus please
see above.
What I have identified is that we have an enormous amount of documents
on too many places.
In this work various negative comments about building OpenOffice.org being
impossible in the articles will be replaced by constructive tips for the
developer.
It never was complicated to build OOo on linux. Since aqua version is
default, it is no longer complicated to build OOo on Mac OSX. The only
problematic systems are Windows and other ports.
What I am referring to is actually problems in the current documents,
where building is referred to as:
Complicated
Impossible
Ooo-build is much easier
These are all things that will be removed in this initiative.
The problem only arises because people are too lazy to read, always
know better, don't even use the OOo build system / ignore warnings
issued by configure / don't try a default build but in a "I do fancy
tricks with the buildsystem stuff" way.
No. The problem is that we have:
- Documents for building the software everywhere
- Tutorials which complete eacher instead of being one document
- Hard to as a new developer get a good overview of the process.
/../
I will only accept to question my own designs of my pages. I will never
question the new developer.
We need them too much.
Per
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
