[Gnumed-devel] request for input on wiki newbie guide and more

[J Busser]

I am reworking the wiki

People who recently (tried to) install gnumed
- please advise what information could have been made clearer, and 
presented earlier
- also advise what you *have* found that was helpful, and the order 
in which you would recommend it be read

I have renamed the wiki's "User Support" to "Getting Started"

Within this area I am less sure it works to have "for end user" and 
"for Administrators". My idea of information grouping would be for:

1. computer-inexpert doctors, who want to determine if gnumed *could* 
work for them

2. moderately-skilled people who, though may know little to nothing 
about python or postgres, want to install gnumed (either for 
themselves, or on behalf of doctors) to further assess it. Obviously 
these people will want installation instructions along with 
information to help them understand common problems, including 
configuration.

They should be given information about the difficulty with the gnumed 
client connecting to a local postgres server, on which I am not 
clear. Is it only a problem when trying to serve postgres from the 
same machine that is being used as a client?  Is it a limitation of 
the debian installer, or other installer code, or a problem with the 
python module that tries to connect to a server? What knowledge or 
skills are needed to get around this problem on a local level (while 
awaiting an installer-wide "fix")?

I am not sure how much more to put under this section because it 
would overlap with the next. But it may not be enough to just say "do 
this to install gnumed". It is probably better to offer a little 
more, to help them understand how gnumed is "built", but how much 
more?

3. people who want to understand gnumed well enough to help develop 
it would benefit from (??)

- whitepapers (are they still accurate?) (are they a good starting point?)
- pointers to
- - the API and db schema
- - GUI principles
- - clarification of Horstspace vs Richardspace vs what Syan is developing
- - coding guidelines
- recognition of factors (like people's limited free time) that are 
seriously constraining the project
- whether and how groups who want to get a portion working can be 
successful without having to fork
- something about where the project is heading e.g. whether it is 
likely to be able to use drugref, any other convergence that is being 
planned or a least foreseen

comments/additions/changes to the above appreciated.