MediaWiki modifications

    From Consumerium development wiki R&D Wiki
    Revision as of 03:31, 7 February 2004 by 142.177.75.90 (talk) (spelling, a few notes - similar page needed for all the other wiki code - mediawiki is very far behind some of them, e.g. tikiwiki which does most of this now)

    This page is for discussing and defining the modifications/patches that we need to make to the MediaWiki software to enable running Content Wiki and Opinion Wiki. A similar page exists for each other wiki code option.

    MediaWiki-namespace

    This is a new feature in MediaWiki. It is a namespace for storing and accessing large number of short items quickly. All [[MediaWiki:]] entries are stored in RAM and can be modified on the fly by sysops. MediaWiki-namespace items have the possibility to use variable-subsitution which is really useful for displaying campaign stats in Opinion Wiki articles among other things.

    For further information on this: m:Meta-Wikimedia:MediaWiki namespace

    Added namespaces

    For Content Wiki to be managed well we need to have at least the following namespaces:

    • Product
    • ProductGroup - what is this?
    • Company
    • faction and tendency (describing one's own biases/assumptions)

    For the Opinion Wiki we need at least the following namespaces:

    • Group
    • VirtualGroup - what is this?
    • Campaign

    Article signing

    The software has to be extended to enable organisations and individuals to sign any version of any article in the Content Wiki with GnuPG or other keys. This is essential to maintain the integrity of the recorded information. Some people may want to see the live wiki, understanding the possible hazards in it, but most will likely want some level of assurance from authorative parties on the correctness of the information


    Content autogeneration

    We need to have a module for generating and identifying information coming from the Consumerium Vault, wherein information is verified by staff. Also reacting to editing of autogenrated content (if made possible) has to be dealt with.


    Article creation restrictions

    For Opinion Wiki we need to restrict the creation of Group-articles to only those entities that are registered in and verified by the Vault


    Privelege management

    For Opinion Wiki we need totally new code to manage the addition, modification and removal of usergroups who can be granted arbitrary priveleges (at present there is only 'developer', 'sysop' and 'blocked IP' status) ---

    Editing restrictions

    For the Opinion Wiki we need to manage restriction of editing of certain articles and subarticles to certain users belonging to designed usergroups OR alternatively require their editorial approval before an edit is visible.


    Middleware connection with Opinion Wiki edits

    Edits to the Opinion Wiki have to be screened by middleware software to update the composite view of the wiki eg. changes in votes or scores