Mechtilde wrote:
Hello,
Chris has named simon and me explicit. So I think it is a good moment to
tell something about my ideas to do it
Simon can also complete it.
First some Information. I have looked for documents about Base or parts
of it since nearly three years. It was not easy to find anything
especially for the upcomming version 2.
In Spring 2007 I have the idea to collect all (= what I know andwhat I
can find) documents (as links) in thewiki. So many people are able to
complete it. I summer I began to write it down on my local computer.
At the time of the OOoCon Chris ask, if we want to work on doing more
documentation for Base. This was the point that I published my raw text
to the wiki.
thank you for that - i am sure that drew rather do not need coordination
but a lot of people does and you two make a good job, please continue in
that direction :)
In the following I answer point to point
Drew Jensen schrieb:
Christoph Lukasiak wrote:
Tim wrote:
Drew,
I set up a wiki for the sbdc driver at
http://wiki.services.openoffice.org/wiki/Base/connectivity/PostgreSQL
It is linked from the Base wiki page - Connecting to Non-embedded
Databases.
I have been using this driver since it came out without any problems.
really confusing :( - if i use only the wiki 'ui' i would rather not
find this pages
1. database vs. base -> there should be only one main place for such
info (base was also confusing in my past experience: the 'base' of
what?) or it should be really good linked
I understand you don't like the name, but Base not database is the name
of the module. When people add things about Writer should they use a
root of word processor?
I saw this Problem and I saw that this page (Base) contains general
information about the modul OpenOffice.org Base. So I look for another
name of a page. I found the empty page "Database". So I took them.
We can discuss if it is better to change the content between Base and
database or another possibilities.
if the single people do not want to change, please find a solution for
better crosslinking
2. connectivity ist also suboptimal - i would await that f.e. postgre
connectivity docu is stored or linked from the 'postgre' wiki page .
This is a good idea. Can someone do it, who read more in the postresql wiki.
this site already exists .. even if the content is a little poor :(
maybe we should link every document containing postgres info into this
page - what do you think, drew?
Why would that be more appropriate, or for that matter why only have it
on one site and not both. Someone who starts by getting postgres and
goes to that wiki looking for information on a front end package; finds
information about something called OpenOffice.org Base. Someone who
starts with OpenOffice.org Base and wants to look for other RDBMS as
backends finds information about something called PostgreSQL. Seems like
a good way to cover both contingencies.
One idea I have we can have an general text on Base and there a link to
database (or howwe named the side) where the person can find more
information.
cool
.. but as drew has already mentioned, we now have two database docu
coordinator for such kind of confusions :)
http://wiki.services.openoffice.org/wiki/Database_Docu_Coordinator
please support them
Regarding this - well supporting is one thing but to be honest I do have
a problem with the idea of the roles as 'gatekeepers'. It is completely
against the whole idea of a wiki. It fits well in the world of a
corporate intranet, but that isn't what we are building here is it?
For me (and I think also for Simon) it is not the role to do it but the
extract the daily work. I'm looking very often if I find somthing in the
internet about the OpenOffice.org Base modul to develop an own
application. And so I get the idea to put these things together and
available for others.
you cannot agree with everyone: if you make nothing it is bad - if you
make anything you 'became a dictator' .. if you make it in one way you
find a person who do not like this, if you make it how he like it, you
find another person, who do not like that .. oo is free, we are part of
oo and we are free to organize us to improve the whole project; if
anybody do not like it, he can keep on working in other way .. if you do
anything on oo you will find always anyone who hates it, so should we
stop to work? i do not think so, but in opposite to that, i think that
who does a lot of good work for the community, have the right to decide
over it (that is also open source and wiki tradition ;)
p.s. this is no statement against drew's statement (drew: please do not
misunderstand me .. i am sure we want exactly the same thing, but call
it with other names)
Everybody can help to collect it.
I noticed that today on another mailing list Louis Suarez-Potts talked
about the wiki 'growing organically' as if that where a bad thing. I
don't understand this apparent tendency to hierarchy and control
structures. What is the fear - that people will put things in willy
nilly places. Well what if they do. Someone asks them to move it, or
goes in and adds missing category links and if all else fails - go in
and move it directly.
We also can discuss about the sructure of these informations. But I also
think it is not good if anybody change the structure without informing
someone.
yes,
.. and i am sure, if the people recognize a structure, they will be glad
to follow it
This first of all because this side should also be linked in the
Online-help.
We must decide about changing the text or content and the structure of a
side (e.g using link with name anker in the help)
sure
For one thing, the problem right now isn't that we are being over run by
folks making too many entries, it is getting people involved in posting
anything IMO.
My main idea is to collect as much as possible of information about Base
on one public place.
yes,
i think nobody who wants to use the database docu has anything against
it to find it in short time
Regards
Mechtilde
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
