[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] wiki changes
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] wiki changes |
Date: |
Mon, 08 Sep 2008 19:39:14 +0200 |
Jim,
thanks for the improved wiki.
> People must remember that GNUmed is an open source project.
>
> The proper 'culture' in open-source communities is that the end-user,
> upon experiencing some problem, would take a look at an FAQ database
> (under development), consult a project knowledge-base (under
> development), look in existing bug-reports (location to be
> stabilized), and only then reporting a bug.
>
> A "bug" should at least appear to be something other than a trace
> which the program presently automatically reports to bug tracker, as
> a result of issues which may not be bugs but the simple result of
> improper program configuration by the user.
>
> A bug, once it is reported, can be 'subscribed-to' and, upon it
> becoming fixed, the interested person can automatically receive bug
> report concerning any fix that has been committed.
>
> If you plan to use GNUmed in an actual production system, it is
> incumbent on you to ensure that you have adequate local help, i.e.
> that you can be self-sufficient for your needs. The GNUmed
> development team cannot be relied on for such things. Ideally,
> whoever would be supporting you locally would make helpful
> contributions to how GNUmed could be improved.
>
> In the meantime, if you have followed the User manual and the FAQs
> and Known Issues pages do not answer your problem, consult the
> Developer list archive and if your answer is not there, email the
> Developer list (subscription required).
While the above is entirely true it seems to me to put a little bit
too much pressure on reporters. I am not sure how to express it properly.
Karsten
--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196