User manual + Help contents

Hi,

there has been lots of talk about from various people why we should have and need a user manual. Yet no action has been taken, except from the Indian team who has made a good document which could be used as a starting point for a “global” manual.

Is there anyone out there that feel like contributing and actually do some work here? Don’t worry to much about formats, sharing etc, we can simply start with a word / odf document and put it in launchpad. I am happy to help out here.

Also, we do have a easy-help solution in place in DHIS 2 which needs to be populated with meaningful and informative help messages. If anyone feel like contributing I will help with the details.

cheers,

Lars

Lars,

I am to meet a technical writer on tuesday to discuss terms of
references for documentation. HMN will pay. Why dont you come? There
are some issues we should sort out, like “FOSS” design, so we can
easily add things ourselves later, and of course some thinking about
how we can keep track of versions in different languages.

Johan

Lars Helge Øverland wrote:

···

https://launchpad.net/~dhis2-devsdhis2-devs@lists.launchpad.nethttps://launchpad.net/~dhis2-devshttps://help.launchpad.net/ListHelp

Hi Johan

Lars,
I am to meet a technical writer on tuesday to discuss terms of references
for documentation. HMN will pay. Why dont you come? There are some issues we
should sort out, like "FOSS" design,

I think we should agree in principle on an appropriate copyright
licence prior to engaging writers - given the need for translation et
al, I would suggest that a creative-commons attribution only licence
would be appropriate.

I guess the other issue you are touching on is "source code" ... what
do you proposes?

Regards
Bob

···

2009/5/1 Johan Ivar Sæbø <johansa@ifi.uio.no>:

so we can easily add things ourselves
later, and of course some thinking about how we can keep track of versions
in different languages.
Johan

Lars Helge Øverland wrote:

Hi,

there has been lots of talk about from various people why we should have and
need a user manual. Yet no action has been taken, except from the Indian
team who has made a good document which could be used as a starting point
for a "global" manual.

Is there anyone out there that feel like contributing and actually do some
work here? Don't worry to much about formats, sharing etc, we can simply
start with a word / odf document and put it in launchpad. I am happy to help
out here.

Also, we do have a easy-help solution in place in DHIS 2 which needs to be
populated with meaningful and informative help messages. If anyone feel like
contributing I will help with the details.

cheers,

Lars

________________________________
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

Bob Jolliffe wrote:


Hi Johan
2009/5/1 Johan Ivar Sæbø :
Lars,
I am to meet a technical writer on tuesday to discuss terms of references
for documentation. HMN will pay. Why dont you come? There are some issues we
should sort out, like "FOSS" design,
I think we should agree in principle on an appropriate copyright
licence prior to engaging writers - given the need for translation et
al, I would suggest that a creative-commons attribution only licence
would be appropriate.

These are the things I would like to discuss, but of which I know very
little. Anyway, though HMN is willing to pay to improve the product
they’re using in Sierra Leone, they don’t want to own the
documentation. So any advice on licence we can put on it, which I guess
will be on the same entity as the software (U. of Oslo), will be
appreciated.

I guess the other issue you are touching on is "source code" ... what
do you proposes?

It must be written on some open platform, and if the output is a pdf
(maybe generated from some wiki-like tool), we should also have the
plain text and be able to do whatever we want with it (change
screenshots, text, etc etc)

Johan

···

johansa@ifi.uio.nohttps://launchpad.net/~dhis2-devsdhis2-devs@lists.launchpad.nethttps://launchpad.net/~dhis2-devshttps://help.launchpad.net/ListHelphttps://launchpad.net/~dhis2-devsdhis2-devs@lists.launchpad.nethttps://launchpad.net/~dhis2-devshttps://help.launchpad.net/ListHelp