One could see PageMaintainer as a pattern in the sense of the PatternTheory. This wouldn’t change the facts, but it would lead the describing thoughts, because a pattern description has a routine structure. One would also ask: “what is the problem, that is solved. What is the context, what are related patterns, the pros and the cons.”. In the end you have something that is made, as a part of culture, that can be applied in situations where this seems to fit.
– HelmutLeitner
Pattern Form
- Pattern Name: PageMaintainer
- Context: Collectively evolving texts, especially in wikis.
- Problem: When collectively writing texts, there is an insecurity, what the various contributors may do. The worst case is that nobody feels responsible for the outcome and nobody feels entitled to refactor the page. Another common situation is to leave this to the founder, but he may not be able to cope with the work load, considering a larger system.
- Solution: The responsibility for a page is transferred to a PageMaintainer, either formally or informally. He adds structure to the article and the discussion and cares for an active process. Now there is a clear social situation. The work load is distributed.
- Possible problems: If the maintainer doesn’t care, the process may get stuck.
- Related patterns: WikiMaintainer?, WikiRefactoring?, PageMode?, ArticleMode?, MaintainerMode.
- Examples: this page, EthicsDiscussion, PatternTheory
This is a start to show the big picture, it’s not complete (maybe 70%). If someone does this in a pattern book it may involve lots of comments and example stories and develop into a 1-2 page mini-chapter.
See also