17 Aug
2009
17 Aug
'09
2:54 p.m.
On Aug 17, 2009, at 2:35 PM, [Ricardo Rodriguez] Your EPEC Network ICT
Team wrote:
Hi all,
Sergiu Dumitriu wrote:
This is about cleaning up.
No system can go on indefinitely by keeping everything online. The
strategy is simple:
- you backup (as we do every day) and remove things that shouldn't be
kept. They're still available on backup should they be needed one day.
As for revisions we'll need a way in the future to be able to maintain
that too since they grow quite large.
I don't agree about absolutely keeping old things online when they're
not needed anymore. If we had done this we would still live with some
mess of xwiki.org as it was back in 2005-2006.
The main point of a wiki is to *NOT* keep stale things by applying
constant refactorings (which is what I suggest) so I definitely don't
agree about using a wiki as an archival system (there are way better
solutions for that) :)
Thanks
-Vincent
Vincent Massol wrote:
I've been supporting here a position where historical archive of any
change in a given document is one of the main reasons to consider a
wiki
as the core of an information system. I would also like to see an
alternative that doesn't imply to delete the seed document even though
it is superseded by a new document. Hi,
As you know I like clean stuff (some could call it an obsession ;)).
While browsing the Design/Idea spaces on dev.xwiki.org I noticed
several pages containing stuff already implemented.
I'd like to propose the following strategy:
* Once a design has been implemented, document it (for example in
the
Modules space on code.xwiki.org)
* When both the new design has been implemented and documented,
delete
the wiki page in the Design space.
Shouldn't we keep those for historical reasons, somewhere outside the
Design space? How about DesignArchive? We could move a page there,
and
add at the end or at the top a conclusion, like "Implemented, see
[the
documentation page]", or "Deprecated, see [alternative design]".
Cheers,
Ricardo