Dear Wikivoyagers,
the Wikivoyage sites currently have string functions for templates
enabled. This adds the {{#len:}}, {{#pos:}}, {{#rpos:}}, {{#rsub:}},
{{#count:}}, {{#replace:}}, {{#explode:}}, and {{#urldecode:}} parser
functions to MediaWiki markup. These string functions can't be
supported on Wikimedia Foundation sites, and templates using them will
break after the migration.
Wikimedia Foundation is currently implementing Lua as a scripting
language for templates which should offer a better approach in the
long run. You can read more about this here:
https://www.mediawiki.org/wiki/Lua_scripting
Your help would be appreciated eliminating any existing dependencies
on these functions. Wikipedians may also be able to help with
conversion to templates not dependent on those functions, and it's
worth looking on en.wikipedia.org for templates with the same name or
purpose.
Thanks,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
I would suggest that everybody be reappointed on a 1 year temporary
adminship basis and then we convert everything to permanent then. To my
mind, this offers several advantages:
*in a transition, people are bound to move on, this means those who
decide that the new project is not for them will simply be removed
automatically by the conversion process in a year
*at the beginning, every project (I'm talking about the smaller
non-english ones) has plenty of activity, but it fairly often dies down
way before than a year, and the project is left with a high number of
admins that were initially approved, shutting out Global sysops and
misdirecting new users to inactive admins
*it would make all admins, no matter when or why or how they gained the
tools elected by the new wikivoyage community directly, as in most of
our wikimedia wikis
*the new project will likely have a community that's a "merger" of the
wikivoyage community, wikitravel community and wikimedia community plus
some new folks, and I imagine some re-imagining of guidelines, processes
and whatnot would take place, it only makes sense that admins be
re-appointed for otherwise the project would lack management, but it
also might end up generating collisions, and difficulty to integrate;
temporary appointment would mean that the community would simply be able
to run for a year with the admins, then in a year's time they could
evaluate how things are going and confirm that everything's going okey.
My main points honestly are the likelyhood of a long list of admins that
then decide they don't like the new project and become inactive and
making all admins directly elected by the community, which is the usual
practice on our wikis.
Regards,
Snowolf
On 23/10/2012 20:01, Philippe Beaudette wrote:
> Hi everyone,
>
> In the migration process, one of the questions that has come up is the
> initial assignment of the administrator rights. Our current plan is
> to assign administrator rights to anyone who currently has them on the
> legacy Wikivoyage wiki (and I'm certainly open to expanding that to
> include the legacy Wikitravel wiki, I just don't know how many people
> are in that group that aren't already wikivoyage administrators).
>
> I wanted to toss that out as a discussion point here and see what the
> general feeling was about that as an opening position? Am I way off
> base? Is there something else that would work better? My main
> interest here is a lightweight system that will work to get the
> project launched.
>
> pb
> ___________________
> Philippe Beaudette
> Director, Community Advocacy
> Wikimedia Foundation, Inc.
>
> 415-839-6885, x 6643
>
> philippe(a)wikimedia.org
> <mailto:philippe@wikimedia.org>
Hi everyone,
In the migration process, one of the questions that has come up is the
initial assignment of the administrator rights. Our current plan is to
assign administrator rights to anyone who currently has them on the legacy
Wikivoyage wiki (and I'm certainly open to expanding that to include the
legacy Wikitravel wiki, I just don't know how many people are in that group
that aren't already wikivoyage administrators).
I wanted to toss that out as a discussion point here and see what the
general feeling was about that as an opening position? Am I way off base?
Is there something else that would work better? My main interest here is
a lightweight system that will work to get the project launched.
pb
___________________
Philippe Beaudette
Director, Community Advocacy
Wikimedia Foundation, Inc.
415-839-6885, x 6643
philippe(a)wikimedia.org
The account transfer mail sent out today covers general, shared, de,
it, wts, en, fr, nl, ru and sv. What's the status of the remaining
languages like fi and ja? Is there any reason not to just copy
everything other?
Cheers,
-jani
Hello,
What is the planning for merging accounts from Wikivoyage, Wikitravel
and Wikimedia?
Should something be done before the migration?
Regards,
Yann
First post!
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Tue, Oct 16, 2012 at 11:47 AM
Subject: Wikivoyage project launch/migration update
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Hi folks,
a quick update on the launch of a travel project under the WMF
umbrella, and the import of the existing Wikivoyage site.
* The name of the new site will be wikivoyage.org, per community vote.
Language domains will live at (foo).wikivoyage.org.
* A mailing list has been set up at
https://lists.wikimedia.org/mailman/listinfo/wikivoyage-l
* We're not planning to import "Wikivoyage Shared" (which is a media
repository similar to Commons) and are encouraging the community to
help with transferring appropriately licensed files to Wikimedia
Commons.
* The Wikivoyage Association is currently finalizing details of a
domain name transfer with WMF. They have also recently secured
wikivoyage.com.
* The technical launch team at WMF consists of Chris Steipp, Daniel
Zahn, Sam Reed, Matthias Mullie, and myself. Everyone is encouraged to
help. Technical updates will be posted to
https://www.mediawiki.org/wiki/Wikivoyage_migration and related pages.
We're using #wikimedia-wikivoyage on irc.freenode.net to coordinate,
so feel free to join us there any time and use it for other related
issues.
* We've received a tarball of extensions running on the Wikivoyage
sites, have imported them into Wikimedia's Git repo, and are currently
reviewing them and making changes where needed to ensure they're ready
for WMF. See https://www.mediawiki.org/wiki/Wikivoyage_migration/Extensions
for a list of extensions if you want to help (and feel free to comment
on the priorities suggested by the Wikivoyage folks)
We may not be able to deploy all extensions; we're using the two week
time-box for the launch as the main forcing function.
* The hairiest part is to properly migrate user accounts. We can only
migrate with users' permission, so Wikivoyage will kick off an opt-in
process shortly to ask users to consent to transferring their private
account data. On the WMF side, we have to reconcile account names with
existing ones and require renames if necessary.
We'll set up an initially private test instance in Labs and iterate
over it with a (possibly reduced) content import, to ensure that all
the tricky legal bits (e.g. attribution) are handled correctly. Then
we'll set up the production cluster wikis.
* Our goal is to go live by the end of this month. That might slip
depending on the domain name transfer and unexpected technical hurdles
or emergencies on the WMF side. We will aim to minimize downtime for
current users, and to ensure that the old sites can be available in
read-only mode for a little while longer to make it possible to
compare site behavior.
Let me know if you have any questions about the process. :-)
All best,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
