If there is LackOfReworking and reworking is considered important, obviously there should be more TechnicalSupportForReworking.
Existing technical support:
- the page history
- to compare with the original
- to revert if reworking goes wrong
- A side-by-side view ability (maybe as a general feature)
- maybe of (1) a page and (2) personal notes
- maybe of (1) the original page and (3) the personal refactoring in progress
- maybe of (1) the original and (2) common notes or refactorings in progress
- Features at a finer granularity than wiki page (sections, paragraphs, signed contributions)
- comments or annotations
Social habits that might be supported technically:
- announce refactoring (who does it, when did it start, ETA)
- original accessable on a separate page or below separator (easy reference to a version of page history)
- Overview of all personal notes of a person
- Identification of the “annotation target” (e.g. by using a fingerprint, current cw PurpleNumber clearly insufficient, inline annotation)
- Performance may be a problem (searching additional information for all “atoms” of a page).
- reaction to changes of the target atom (“comment out of date”)
- wiki becomes even more complicated
- valuable content may be unvisible in personal notes
Implementation - Storage
User-specific views or notes could be stored inline, in subpages or namespaces. Inline storage would not scale, so it can be ruled out. Subpages or namespaces are rather similar, because in either case “some notes” would be stored in a single page.
Implementation - Identification
Implementation - Side-by-side Layout
Helmut: having translation pages and keeping them up-to-date looks like a similar problem having page granularity. AlainDesilet? manages this with his wiki engine beautifully, should be very important for the work of Christophe.
- see also: LackOfGranularity