Matthias Müller-Prove <Matthias.Mueller-Prove sun.com> writes:
> A useful summary for your example above would be:
"Correcting links to
> [[User Interface Guidrline]]"
> Less than 50 characters. The wiki diff page uses more
than 900
> characters for the same message.
>
Hi Matthias,
well, I guess we're on the same page, actually - your text
would make
a nice summary line when pressing the save button in the
wiki. Those
summaries then appear besides the time and user entries on
the history:
http://wiki.services.openoffice.org/mwiki/index.php
?title=Build_up_a_Vibrant_User_Experience_Community&acti
on=history
> I argue for some more effort on the side of the author
to save a
> significant amount of time on the reader's side.
>
Agreed, generally. Only that it is superfluous and redundant
in this
case, to manually enter those revision tracking stuff in the
main
text. As Eike said, just provide a sensible commit summary,
when
saving substantial work in the wiki. That's exactly for what
it's
meant for. Wikipedia articles are also maintained like this,
and
they usually also contain no code.
Cheers,
-- Thorsten
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe specs.openoffice.org
For additional commands, e-mail: dev-help specs.openoffice.org
|