-------- Messaggio originale --------
Oggetto: [Mediawiki-i18n] account creation change, and changes
Data: Wed, 21 Nov 2012 16:37:17 -0800
Mittente: S Page <spage(a)wikimedia.org>
Hi there. The Editor Engagement Experiments team wants to improve the
account creation user experience[1].
One simple change is after someone successfully creates an account,
instead of showing 'Login successful', make the page show 'Welcome,
NewUser'. We filed a bug[2] and the change is mostly-merged (thanks
Nikerabbit and IAlex) and should roll out with 1.21wmf5 over the next
two weeks.
This means the existing welcomecreation message splits into new
welcomeuser and welcomecreation-msg messages. If a wiki has
customized its MediaWiki:welcomecreation message then that will
probably need adjustment.
I thought about removing or replacing welcomecreation but the
extensions ApiSignup and SpecialUserSignup (unused by WMF) and
./tests/parser/preprocess/ all refer to it. Do developers usually
introduce a new message then obsolete the old one, or cut over in one
commit?
For your information, the E3 team has more substantial changes to user
login, account creation, and onboarding (welcoming users after account
creation) in development. I'll keep i18n people informed; I hope this
is the right list for the changes. I figure any communication is
better than throwing code onto 863 wikis and letting people figure it
out :-)
[1] https://www.mediawiki.org/wiki/Editor_engagement_experiments#Projects
[2] https://bugzilla.wikimedia.org/show_bug.cgi?id=42215
--
=S Page software engineer on E3
_______________________________________________
Mediawiki-i18n mailing list
Mediawiki-i18n(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
Hi, I thought I had sent this email to this list, but it doesn't show
up in the archives. Re-sending just in case.
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Thu, Nov 15, 2012 at 12:28 PM
Subject: Apply for the FOSS Outreach Program for Women internships
To: wikitech-l(a)lists.wikimedia.org
Hi, the FOSS Outreach Program for Women internships has started!
The blog post:
http://blog.wikimedia.org/2012/11/15/apply-for-the-foss-outreach-program-fo…
The program:
https://live.gnome.org/OutreachProgramForWomen
The Wikimedia specific information:
https://www.mediawiki.org/wiki/Outreach_Program_for_Women
If you are following Wikimedia in Identica, Twitter, G+ or Facebook,
you likes and shares are welcome. Please help out reaching out to
women in tech out there!
--
Quim
--
Quim Gil
Technical Contributor Coordinator
Wikimedia Foundation
For your information. You are invited / encouraged to take this
survey. Thank you!
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Mon, Nov 19, 2012 at 9:40 AM
Subject: Please take this survey about new contributors
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Hi, if you joined the MediaWiki / Wikimedia tech community in 2010 or
later please consider taking this survey:
Newcomer experience and contributor behavior in FOSS communities
https://limesurvey.sim.vuw.ac.nz/index.php?sid=65151&lang=en
The survey is open for sporadic contributors or full time Wikimedia
employees, developers or any other profile. Anybody is welcome to
leave their feedback as long as you have started contributing to this
community in the past 3 years.
11 mature and well established open source projects are taking part in
this survey: Debian, FreeBSD, GNOME, Gentoo, KDE, Mozilla, NetBSD,
OpenSUSE, Python, Ubuntu and Wikimedia. Some of them started some days
ago and have more than hundred responses by now. The data of this
survey is anonymous and will be released under a ‘share-alike’ Open
Data Commons Open Database License (ODbL).
Some background:
>From Kevin Carillo, the researcher:
http://kevincarillo.org/survey-invitation/
>From OpenHatch, a non-profit working on the bridge between free
software projects and new contributors:
https://openhatch.org/blog/2012/a-research-project-to-understand-what-does-…
PLEA
If you, like me, became a bit tired of survey requests like this
please consider filling this one anyway. It focuses in a specific area
where we don't have much data. As fresh technical contributor
coordinator at the WMF I'm looking forward to the results of this
research and the lessons it will bring.
Thank you. :)
--
Quim Gil
Technical Contributor Coordinator
Wikimedia Foundation
Hello,
I would expect those things that are needed to inform my communities on what is going on with updates and so.
Also when complete projectbranches like Wikivoyage and Wikidata are launched or so.
I need to be able to tell the users of the projects what is going to be changed, it would be nice if reasons are given for better understanding, and what they can do to solve it if problems continue.
Greetings - Romaine
> Date: Sat, 10 Nov 2012 14:15:55 +0100
> From: J?r?mie Roquet <arkanosis(a)gmail.com>
> To: "Coordination of technology deployments across
> languages/projects"
> <wikitech-ambassadors(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-ambassadors] What would you like on
> this list?
> Message-ID:
> <CAFOazAP0AJN=q_n7+U1+7m-eXgxe8gy+C36TzObk46PPhcM5yg(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> 100?% agree with previous answers :-)
>
> To sum it up in a few words:
> - new features (including features available on request)
> - future features (and demos)
> - breaking changes (and workarounds)
> - technical discussions go to wikitech-l, not here
>
> Best regards,
>
> --
> J?r?mie
Great opportunity for ambassadors to get involved.
-------- Original Message --------
Subject: Re: [Wikimedia-l] Wikivoyage project launch/migration update
Date: Sun, 11 Nov 2012 11:29:08 +0530
From: Erik Moeller <erik(a)wikimedia.org>
Reply-To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
So, if you've not been following along on wikivoyage-l (
https://lists.wikimedia.org/mailman/listinfo/wikivoyage-l ), you
should know that Wikivoyage is now hosted on WMF servers. :) We're
currently in "beta", as there's still lots of smaller and larger
issues to work through, including transferring images to Commons or
local wikis as appropriate. But now's a great time to get involved if
you want to help fix things. These are the languages that are live
now:
httsp://en.wikivoyage.org/https://de.wikivoyage.org/https://ru.wikivoyage.org/https://nl.wikivoyage.org/https://it.wikivoyage.org/https://sv.wikivoyage.org/
But, any other language code should gracefully redict you to Wikimedia
Incubator, where you can easily get started to prove viability of a
new language. :-)
Like I said: Lots of things are still wonky. If you notice something
you can't fix, please report it on Bugzilla and add it as a blocker
for the tracking bug here:
https://bugzilla.wikimedia.org/show_bug.cgi?id=41184
While we're not done yet, I'd like to take this chance to thank
everyone who's been part of the process so far:
* the existing communities for being awesome in supporting this
migration :-)
* Wikivoyage e.V. and especially Hans (for being our main tech contact
managing the DB transfers), Stefan (for handling all the
organizational fun), and Roland (for technical support and review).
* the WMF technical launch team: Chris Steipp, Daniel Zahn, Matthias
Mullie, Sam Reed + everyone who chipped in with help and support.
* the WMF legal and community advocacy team: Geoff Brigham, Kelly Kay,
Philippe Beaudette, and everyone else who helped.
* anyone else I've forgotten to name :-)
All the best,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
_______________________________________________
Wikimedia-l mailing list
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Hey all,
Just a reminder that jQuery will (after almost 4 years of deprecation!) drop
$.browser [1] in jQuery 1.9.
Please check your scripts and make sure you are are no longer using "$.browser"
(or "jQuery.browser"). After jQuery 1.9 is released, from the next MediaWiki
deployment after that $.browser will be undefined and old code trying to access
a property of it will throw a TypeError for accessing a property of undefined.
Don't be alarmed, this has been a long time coming. It's been almost 4 years,
and by the time this is deployed it will probably have been 4 years.
For those who just realised their script is still using it, or if you read this
later to fix someone else's script that just broke (hello future, did the world
end in 2012?), I'll briefly describe two migration paths you can take from
here:
== Feature detection
In most (if not all) cases of people using $.browser it is because they want
different behaviour for browsers that don't support a certain something. Please
take a minute to look at the code and find out what it is you are special-casing
for that apparently doesn't work in a certain browser.
Research on the internet and look for a way to detect this properly (examples
below). Browser detection (instead of feature detection) is not reliable, nor is
it very effective. For example, Internet Explorer has changed a lot since IE6.
Blindly doing A for IE and B for non-IE isn't very useful anymore as most (if
not all) of the new features will work fine in IE8, IE9 or IE10.
The opposite is also true. If you do something cool for Chrome, you're missing
other WebKit-based browsers that should get the same awesomeness (Safari,
Chromium, iPhone/iPod/iPad, possibly Android, Flock, etc.) these all share the
exact same engine that backs Chrome). And what if Firefox and IE also start to
support this new awesome feature?
There are many ways to do feature detection. jQuery comes with various detectors
built-in in the object "jQuery.support"[2]. This contains for example "support.ajax",
"support.opacity" and many more[2]. You can also easily make your
own feature detector:
* var supportPlaceholder = 'placeholder ' in document.createElement('input');
* var supportJSON = !!window.JSON;
etc.
If you need any help with feature detection, I'd recommend asking in one
of the following channels on irc.freenode.net:
* ##javascript (recommended)
* #jquery
* #wikimedia-dev
== jQuery.client [3]
If you can't figure out how to detect what you really want to switch for, there
is an elaborate plugin in MediaWiki that does the same thing that jQuery.browser
used to do (and more). This can be used as an alternative migration path. To
give an impression:
> jQuery.browser
< {
chrome: true,
version: "22.0.1229.94",
webkit: true
}
> $.client.profile();
< {
name: "chrome",
layout: "webkit",
layoutVersion: 537,
platform: "mac",
version: "22.0.1229.94",
versionBase: "22",
versionNumber: 22
}
For example:
if ( $.browser.chrome ) {}
Would become:
++ dependency: jquery.client
var profile = $.client.profile();
if ( profile.name === 'chrome ) {}
But:
if ( $.browser.msie ) {
// IE doesn't support opacity
el.style.filter = 'alpha(opacity=50)';
} else { .. }
Should become:
if ( $.support.opacity ) {
el.style.filter = 'alpha(opacity=50)';
} else { .. }
Or better yet, since this is supported by jQuery core for a while now, like
this:
$(el).css('opacity', 0.5);
Which will do the right thing for newer browsers and old IE respectively.
-- Krinkle
[1] http://api.jquery.com/jQuery.browser/
[2] http://api.jquery.com/jQuery.support/
[3] https://www.mediawiki.org/wiki/RL/DM#jQuery.client
-------- Messaggio originale --------
Oggetto: [Wikimedia-l] Info action
Data: Mon, 22 Oct 2012 17:41:21 -0400
Hi.
This is just a heads-up that you'll start seeing a "Page information" link
in the sidebar (under "Toolbox") in the coming days on Wikimedia wikis. It
is deployed now to a few wikis already. This "Page information" link leads
to a newly reimplemented info action:
https://en.wikipedia.org/w/index.php?title=Main_Page&action=info
Many, many years ago, the info action was added to MediaWiki, but due to
performance issues, it was quickly disabled by default and was mostly
forgotten about. This year, with the wonderful help of Madman, Krenair, and
others, we have reimplemented the info action to provide an information
dashboard of sorts about a particular page title to users.
This dashboard includes a variety of metadata about the page, including the
page's protection status, length, default categorization sort key, internal
page ID, templates used on the page, and more. The content is somewhat
dynamic: for some pages it will omit certain irrelevant fields and for some
users (such as administrators), certain additional fields (such as the
number of page watchers) will be displayed. This will slowly allow for the
deprecation of outside tools that currently provide information of this
nature.
The hope is that this action will evolve over time to become a valuable
resource for users. If you can think of data points that are missing from
the current action's output or have other ideas to improve the info action
(it desperately needs a little design love), please feel free to e-mail this
list or file a bug at <https://bugzilla.wikimedia.org/>.
MZMcBride
_______________________________________________
Wikimedia-l mailing list
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l