--- Comment #13 from Rob Kam <> ---
(In reply to comment #12)
> As for how to do this, doesn't someone just need to bundle an XML export of
> the templates they want, and then import them into the wiki?
> (In reply to comment #5)
> > Broadly, decentralization seems like a pretty bad idea. For images, we
> > implemented InstantCommons, allowing one site to be a central repository of
> > images, preventing needless and costly duplication. We did this in an
> > abstract
> > way, allowing sites to easily use Wikimedia Commons, but also set up or
> > customize other central repositories to use. I don't see why we wouldn't do
> > the
> > same for global bits and pieces.
> +1 to this.

For a less than guru Mediawiki non-WMF admin. When finding out that templates
are an essential part of setting up a wiki. They have to figure out which wiki
to use as a source and then which templates. When the XML gets imported into
the destination wiki, they've also got red links to missing sub-templates,
details that apply specifically to the source wiki, (e.g. the name and logo of
that source wiki) and maybe other features like style sheets that still need
fixing. Afterwards how do they keep the templates up to date with changes and
bug fixes. Every time the install is upgraded the process needs repeating. 

Their ought to be a simpler and efficient way to do this. Installing and
maintaining extensions is mostly a neat and simple process. A central
repository for this sounds like a good idea. I don't know enough about
to be able suggest a possible right way this could be gone about.

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

Reply via email to