zondag 13 februari 2011

Reach, Participation, Quality & Innovation

Preparing for an upcoming strategy weekend for the Dutch local chapter I revisited the strategy project. What can be done to achieve goals with respect to reach, participation, quality and innovation in the Netherlands, I wondered. Wikipedia and other projects are run on Mediawiki. Critical software that itself is one of the projects of the Wikimedia Foundation.

The Mediawiki software provides for a global content management system. Marketeers of commercial software houses prefer the tag Enterprise Content Management for their products. Would Mediawiki ever qualify as an universal content management system, not just a global content management system?

I happened to visit http://svn.mediawiki.org/viewvc/mediawiki/trunk/phase3/includes/parser/Parser.php?revision=81894&view=markup today, just to notice that core development of Mediawiki software happens in a 'svn' or Subversion repository, and not in wiki pages. Our carpenters, stonemasons, plumbers, pipefitters and other construction workers, including architect and civil engineers happen to not really live in the house they're building ;)

Next weekend the strategist probably will settle on a vision to keep our feet on earth with delivering global content on a platform for global content management. The movement as a whole has ambitious goals, but they don't include any universality claims. Or did I just identify an opportunity to be included in the SWOT analysis?

2 opmerkingen:

  1. I don't get this. We (mediawiki developers, and ops folk) use MediaWiki for all of our documentation, for our code review, for extension management, and soon for managing virtual machines for our test/dev network.

    For source control we use something specifically written for the job. A wiki is not suited for this job.

    BeantwoordenVerwijderen
  2. Depends on what link you view: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/81894 is a more mediawiki-esque view of that commit. svn has many features that make it more attractive for software development. For example you wouldn't want ~~~~ be replaced when coding. Similarly trying to write an encyclopedia in svn would be a pain.

    BeantwoordenVerwijderen