provides a minimum functionality of what people expect these days. It is very much like the MediaWiki
interface, for better or worse.
Description and Documentation
merely update the Foswiki distribution's MANIFEST file
and add the following line:
during the development of 1.1, the HistoryPlugin could
be further enhanced; those enhancements should be handled in subsequent RequestProposals
and task items.
-- Contributors: WillNorris
- 27 Apr 2009
It would be better to bring this functionality into the RDiff code, instead of duplicating things and increasing the codebase we have to maintain.
It also seems to me to be important to analyse the actual benefits of the code and to consider what we can do better (as the core has full access to things)
- 28 Apr 2009
Same comment as I have on CompareRevisionsAddOn
As long as I do not see some commitment to start implementing this in core, we should put this extension in 1.1.
We can always remove it again when the feature is in core.
- 29 Apr 2009
Make them default plugins, I installed them on our system around a week ago and this seems to be standard functionality. There wasn't anything additional I had to install as the stuff for dependencies was already available on my installation.
- 01 Jul 2009
Please do ship HistoryPlugin
as part of the standard distribution.
- 02 Jul 2009
As an additional note - as the current maintainer of HistoryPlugin
I give my permission to change the change policy to FollowReleaseProcess
. This is required for all extensions that become default extensions to protect both our users and the original authors.
Sven, again, given the condition and promise that we merge the feature of HistoryPlugin
into core in 2.0 - are you OK to lift your concern? That would save the community a vote
- 22 Jul 2009
done, and commited to trunk
presumably Will will be doing some docco work, and adding unit tests.
- 27 Jul 2009