gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] Re: GNUmed manual


From: Gour
Subject: [Gnumed-devel] Re: GNUmed manual
Date: Tue, 09 Sep 2008 17:10:31 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

>>>>> "Karsten" == Karsten Hilbert <address@hidden> writes:

Karsten> It sucked because it was a lot more effort to change something
Karsten> and the need to install a toolchain actually put off would-be
Karsten> contributors (again, *those* can and should be Jane Random
Karsten> Useress). The toolchain may not even be available for, say,
Karsten> Windows.

Karsten, do you speak just like that or do you base your statements on
some facts?

Which toolchain is required to write reStructuredText?

It's just plain lightweight markup and can be written from Vim,
Emacs...down to Window's Notepad.

So, nothing to put off any contributor.

Karsten> No quick changing something online inbetween patients at 3am
Karsten> night shift in response to a good idea in a posting on the
Karsten> list.

Huh, why you can't just open your editor and save the note which can be
later pushed/committed to the trunk?

Karsten> - see the wiki as a means of collecting "rough" manual pages -
Karsten> writes the actual manual based on those pages - regularly
Karsten> publishes that "final" manual, say, twice weekly

If we want to have nicely-looking manual, wiki is not the way.

Why should the manual be updated twice weekly?

Do you have two regular releases per week?

Karsten> If one has to use locally installed tools to contribute to the
Karsten> manual then I won't be able to contribute to it meaningfully
Karsten> anymore. If that's fine with you because you volunteer to do it
Karsten> - no problem :-)

You do not need any tools to contribute to the manual and it would be
nice to take a look at some of the URLs I'm posting here before giving
statements which do not hold water ;)

Besides that, this is a good case for DVCS where one can easily pull
latest code/docs from the trunk, contribute to the docs even while being
offline and then commit back.

My humble feeling is that replying to every proposal for a change in the
current workflow (which seems the be like engraved in the rock) by
suggesting: no problem if you'll do it, won't inspire many contributors
in the future.

At least, it would be fair to provide real arguments against it....


Sincerely,
Gour


-- 

Gour  | Zagreb, Croatia  | GPG key: C6E7162D
----------------------------------------------------------------

Attachment: pgpJi65n7UQj4.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]