https://bugzilla.wikimedia.org/show_bug.cgi?id=31063
--- Comment #12 from Daniel Friesen <mediawiki-b...@nadir-seen-fire.com> 2011-10-26 09:02:52 UTC --- (In reply to comment #11) > That was a hornet nest, ok... I am almost convinced by the circular loading > argument. Except I have a preference for wikis, that is: put things into a > transparent, editable object repository and harvest from there. Like > Categories > and everything else. There is nothing wrong with having a namespace table, it > could easily be harvested off MediaWiki: - except that would mean hardcoding > the symbolic name for Mediawiki NS. Advantage: changes are tracked, > editability > is free (ultimately extensions should probably register their namespace, but > for a long time this would require user interaction). There's nothing editable at all about formats like MediaWiki:Sidebar. They're horrible hacks with horrible interfaces for what could be a very user friendly special page. And while it's not versioning if we need it we already have a logging system. > I wish the same were true for the interwiki table: store as a transparent, > changeable, version traceable object rather than as database table without > version control and user interface. The present interwiki table, would be a > bad > example of how to manage namespaces. It is not included in import/export. It > remains uneditable for how many years? 1000s of people trying to use mediawiki > have to figure out which of > http://www.mediawiki.org/wiki/Category:Interwiki_extensions they need to > install. How many give up? I am adding bug 31951 to call for moving > Extension:Interwiki to core, and bug 31955 to address the import/export > question for interwiki. I actually have a separate issue with interwiki. IMHO it shouldn't even be necessary to do database changes to change the interwiki table. For a simple wiki with fs access it should be as simple as editing a file. Default interwiki mappings should be done by referring to a core provided file as the default fallback instead of being inserted into the db on install. Wiki farms should be able to have a central interwiki database AND a local interwiki database with overrides, instead of being stuck with either a central one and no overrides or redundant local tables. etc... > I am not a developer, only a mediawiki farm manager and applied user, so I > fully accept your insight into the code structure which I don't have! -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
