Wiki Patterns

Patterns for successful wiki use

User Tools

Site Tools

Trace:
one_wiki_space_per_group

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
one_wiki_space_per_group [2018/11/14 21:14] – external edit 127.0.0.1one_wiki_space_per_group [2018/11/28 14:03] (current) – Struct data changed splitbrain
Line 1: Line 1:
-===== One Wiki space per Group ===== +====== One Wiki space per Group ======
- +
-==== What is it? ====+
  
 In a large organisation, different teams want to share knowledge and collaborate on different topics. Some teams are more open to sharing and collaboration than others. A natural approach might be to give each project or group a distinct wiki. In a large organisation, different teams want to share knowledge and collaborate on different topics. Some teams are more open to sharing and collaboration than others. A natural approach might be to give each project or group a distinct wiki.
  
-==== Advantages (as an Adoption Pattern) ====+===== Advantages (as an Adoption Pattern) =====
  
   * Easier page naming in the context of your knowledge area and fewer problems with naming clashes   * Easier page naming in the context of your knowledge area and fewer problems with naming clashes
Line 14: Line 12:
 Page naming is a tricky problem in large cross-organisation wikis. If one Wiki is used for all projects, page naming conflicts might occur. For example, two projects meet on the same day and want to create meeting minutes with the same title. The problem can be tackled by putting together (collaboratively) a set of page naming conventions, and by enforcing these with regular wiki gardening. With separate spaces, you save a lot of this the hassle. Page names only need to make sense within smaller focussed project teams. Page naming is a tricky problem in large cross-organisation wikis. If one Wiki is used for all projects, page naming conflicts might occur. For example, two projects meet on the same day and want to create meeting minutes with the same title. The problem can be tackled by putting together (collaboratively) a set of page naming conventions, and by enforcing these with regular wiki gardening. With separate spaces, you save a lot of this the hassle. Page names only need to make sense within smaller focussed project teams.
  
-==== Disadvantages (as an Adoption Anti-Pattern) ====+===== Disadvantages (as an Adoption Anti-Pattern) =====
  
 As mentioned above, this pattern //feels// like a sensible approach to aid organisation of the wiki, and so it is natural that people would go for a separation of wiki spaces. But is it a mistake? There are a couple of pretty big disadvantages, which lead some people to conclude that this in fact an anti-pattern! As mentioned above, this pattern //feels// like a sensible approach to aid organisation of the wiki, and so it is natural that people would go for a separation of wiki spaces. But is it a mistake? There are a couple of pretty big disadvantages, which lead some people to conclude that this in fact an anti-pattern!
Line 30: Line 28:
 Wiki gardeners tend to be more wiki-savvy than most, so hopefully they will find the centralised recent changes (if you provide one). However wiki gardeners may only become wiki gardeners by slowly developing a 'recent changes' addiction. Wiki gardeners tend to be more wiki-savvy than most, so hopefully they will find the centralised recent changes (if you provide one). However wiki gardeners may only become wiki gardeners by slowly developing a 'recent changes' addiction.
  
-==== Implementation of separate wiki spaces: Separate wiki installations or a Separate spaces on a single installation ====+===== Implementation of separate wiki spaces: Separate wiki installations or a Separate spaces on a single installation =====
  
 A simplistic way of achieving this is to install entirely separate wikis for different groups/teams. A simplistic way of achieving this is to install entirely separate wikis for different groups/teams.
Line 44: Line 42:
   * users may have the option of viewing a centralised 'recent changes' display (see wiki edits occurring across the whole organisation).   * users may have the option of viewing a centralised 'recent changes' display (see wiki edits occurring across the whole organisation).
  
-{{:/images/icons/emoticons/information.gif?16x16}} The advantages above, garnered by hosting the //individual team spaces// on a //single installtion// , help alleviate the disadvantages of the wiki pattern of having individual spaces for each team.+The advantages above, garnered by hosting the //individual team spaces// on a //single installtion// , help alleviate the disadvantages of the wiki pattern of having individual spaces for each team.
  
-{{:/images/icons/emoticons/information.gif?16x16}} Where separate wiki installations are created, it may also be possible to configure easy interlinking (e.g. MediaWiki's interwiki feature) while centralised recent changes could be presented using an RSS aggregation.+Where separate wiki installations are created, it may also be possible to configure easy interlinking (e.g. MediaWiki's interwiki feature) while centralised recent changes could be presented using an RSS aggregation.
  
-==== Related Patterns ====+===== Related Patterns =====
  
   * This is **related to** [[Naming+Conventions|Naming Conventions]]   * This is **related to** [[Naming+Conventions|Naming Conventions]]
Line 57: Line 55:
   * See also [[Permission+Patterns+Overview|Permission Patterns Overview]]   * See also [[Permission+Patterns+Overview|Permission Patterns Overview]]
  
-==== Further Reading ====+===== Further Reading =====
  
-  * This contribution was initially taken from Using Wikis to Manage Use Cases: Experience and Outlook, page 113 of  [[http://www.se.uni-hannover.de/big_picture/LSOplusRE-Proceedings-web-v1.0.pdf|Proceedings of Workshop on Learning Software Organizations and Requirements Engineering]] +  * This contribution was initially taken from Using Wikis to Manage Use Cases: Experience and Outlook, page 113 of  [[http://www.se.uni-hannover.de/events/LSOplusRE/LSOplusRE-Proceedings-web-v1.0.pdf|Proceedings of Workshop on Learning Software Organizations and Requirements Engineering]] 
  
  
  
 ---- struct data ---- ---- struct data ----
 +classification.type  : Pattern
 +classification.focus : Adoption
 ---- ----
  
one_wiki_space_per_group.1542230050.txt.gz · Last modified: by 127.0.0.1