Summary:
On Thursday July 11th we will be enabling a new centralized login
service to make the login experience for users more streamlined.
More detail:
To address the shortcomings of the current Single User Login (SUL)
system, the Platform team is making significant changes to the way that
CentralAuth logs users into other wikis on login:
* Users will be logged into a new, centralized domain when they login to
any public WMF wiki with a global account. This domain is
login.wikimedia.org
* Global accounts will no longer see the "Login Success" page after
login, instead they will be redirected back the article where they
came from. On the article page, we will transparently attempt to login
the user to all of the sister projects, instead of relying on the
images on the login success page.
* All of the public WMF wikis will use the central wiki to check
anonymous user's logged-in status, and transparently log the user in
if they are centrally logged in.
(Thanks to Chris Steipp for the above language.)
You can see the full rollout plan for this here:
https://www.mediawiki.org/wiki/Auth_systems/SUL2#Rollout_Plan
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hello and welcome to the latest edition of the WMF Engineering Roadmap
update.
This is a larger update than normal as I missed sending this out the
past two weeks (one week being the week of July 4th, and the other this
was deprioritized due to other needs). My apologies.
As always, you can see the full roadmap, with information links, here:
http://www.mediawiki.org/wiki/Roadmap
== Flow ==
* June: started architectual discussions.
* July: have/or will hire for Front End engineers.
* August: work on the API design.
* September: First experimental release of the user-to-uesr discussion
workflow (probably limited to an opt-in group).
* December: Goal date for the full production release of the
user-to-user discussion system.
== Mobile Apps ==
* July: Revised login, iOS multi upload, bug fixes, back to regular
releases, New detail page, earliy campaign work.
== Mobile Web ==
* July: Watchlist thanking/reverting (in beta). Getting started for
mobile in beta.
* August: continued watchlist thanking/reverting. Getting started for
mobile planned to be stable.
== Language ==
* July: ULS deployment to all wikis has been completed. Urgent bugfixes
and performance patches are now being deployed during the weekly
scheduled deployment window.
== Ops ==
* July: Analysis and testing of Ceph lead to probable decision of
staying with Swift.
* September: Migration to eqiad (datacenter in Virginia) from tampa
should be complete.
* December: Creation and setup of the west coast data center should be
complete.
== Platform/MW Core ==
* July: ElasticSearch research (in addition to Solr). Review work of the
GLAM Wiki Toolkit.
* August: Deploy of either Solr or ElasticSearch to test2.wikipedia.org.
Also, a deployment infrastructe sprint will begin.
* September: An Admin Tool sprint begins.
* October: goal date of new search to English Wikipedia. Also, HipHop
deployment tentatively begins.
* November: HipHop deployment tentatively completes.
* December: A very tentative goal date for a centralized code repository
pending other priorities.
== QA ==
* July: more Jenkins job executers for faster full suite runs. Trainings
for test development and failure analysis. Target groups tbd.
* August: Continued improvements of BetaLabs
== Eng Community Team ==
* August: Puppetize Bugzilla. QA training in automated testing for
gadgets.
* September: prep for next OPW round
* October: Community metrics integration
* December: run the application process for the next OPW round
Best,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hello everyone,
It’s with great pleasure that I’m announcing that C. Scott Ananian[1] has joined the Wikimedia Foundation as a Features Engineer.
Before joining us, Scott was Director of New Technologies at One Laptop per Child where he, among other things, worked on Nell, a platform to allow unsupervised learning of early literacy skills on tablets used in places like Ethiopia[2], and the OLPC security mechanism to prevent kids’ laptops from being stolen in transit. In between stints at OLPC, he worked as the Senior Architect at litl, LLC[3]. Clearly he has a thing for highly mobile PCs and applications (don’t tell Tomasz, he already stole Kaldari from Features :-P).
He started volunteering work on the MediaWiki parser project (Parsoid) on February 12th and got his first patch merged on February 15th. He’s had over 150 patches merged since then so it made sense that we should probably hire him ;-)
As you probably guessed with my usual tardiness, his first official day was actually Monday, July 8. He is going to continue his work on the Parsoid team with Gabriel Wicke and Subbu Sastry. He is super-motivated and has been mission-aligned since before Wikipedia existed[4], so I expect you’ll see him range far from our text infrastructure work. When he was at OLPC he liked to say his job was to “build robust and reliable systems to allow kids to discover, share, and learn.”
Scott lives and works in Cambridge, MA[5]. He is a square dancer[6] and theatrical lighting designer. I have it on good word that he’s a demon on MIT Mystery Hunt [7]—not sure if he’s on the same team as our Board Members or not [8], but if not…
Please join me in welcoming C. Scott to the Wikimedia Foundation. :-)
Take care,
Terry
[1]: [[User:Cananian]]
[2]: http://www.dvice.com/archives/2012/10/ethiopian_kids.php
[3]: http://en.wikipedia.org/wiki/Litl
[4]: http://www.salon.com/2000/02/09/linuxdvd/
[5]: tewwy: interested in relocating? :-)
cscott: no, sorry.
cscott: wife, kid, and house like where they are. ;-)
[6]: https://en.wikipedia.org/wiki/Challenge_square_dance ;
https://en.wikipedia.org/wiki/Tech_Squares
[7]: https://en.wikipedia.org/wiki/MIT_Mystery_Hunt
[8]: [[User:Sj]] did, in fact, recruit him to the Codex team in 2009. Codex won in 2011.
terry chay 최태리
Director of Features Engineering
Wikimedia Foundation
“Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.”
p: +1 (415) 839-6885 x6832
m: +1 (408) 480-8902
e: tchay(a)wikimedia.org
i: http://terrychay.com/
w: http://meta.wikimedia.org/wiki/User:Tychay
aim: terrychay
I am using the Vector skin. I have an extension very similar to whatlinkshere. It needs to take the current page as the parameter just like whatlinkshere.
I would like to add it to the toolbox, but actually I do not care where it is in the navigation but the toolbox seems the most logical.
We have done this before with other older skins that had something like this section:
<div id="gumax-special-tools">
I noticed that getToolBox() is within BaseTemplate. Is there a way to add this method to the tool box?
Thanks,
Mary Beebe
Battelle - Charlottesville, VA
Office: 434- 951-2149
**Confidentiality Notice**
This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, any disclosure, dissemination, distribution, copying or other use of this communication or its substance is prohibited. If you have received this communication in error, please return to the sender and delete from your computer system.
I'm writing to report on progress with Mediawiki-Vagrant, and to tell
you a bit about how it could be useful to you. If you've looked at
MediaWiki-Vagrant in the past and thought, 'big deal -- I know how to
configure MediaWiki', this e-mail is for you.
But first, a small snippet to whet your appetite:
# == Class: role::mobilefrontend
# Configures MobileFrontend, the MediaWiki extension which powers
# Wikimedia mobile sites.
class role::mobilefrontend {
include role::mediawiki
include role::eventlogging
mediawiki::extension { 'MobileFrontend':
settings => {
wgMFForceSecureLogin => false,
wgMFLogEvents => true,
}
}
}
MW-V has evolved to become a highly organized and consistent Puppet
code base for describing MediaWiki development environments. Puppet,
you'll recall, is the same configuration management and software
automation tool that TechOps uses to run the cluster. Puppet provides
a domain-specific language for articulating software configuration in
a declarative way. You tell Puppet what resources are configured on
your machine and what relationships inhere among them, and Puppet
takes your description and executes it.
MW-V uses Puppet to automate the configuration of MediaWiki & related
bits of software. But MW-V goes a bit further, too: it exploits the
flexibility of Puppet's syntax and semantics to give MediaWiki
developers a set of affordances for describing their own development
setup. The description takes the concrete form of a Puppet 'role'.
These can be submitted as patches against the MW-V repo and thus
shared with others. The combination of Vagrant / Puppet / VirtualBox
make it quite easy to select and swap machine roles.
Roles can be toggled by adding or removing a line, 'include
role::<name>', from puppet/manifests/site.pp. The current set of roles
are listed here:
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/vagrant.git;a=blob;f=pupp…
They include a VisualEditor role that is powered by a local Parsoid
instance, and roles for Selenium testing, Echo, MobileFrontend,
GettingStarted, and EventLogging.
If you're interested in checking it out:
0. Delete any old instances.
1. Download & install VirtualBox: https://www.virtualbox.org/wiki/Downloads
2. Download & instal Vagrant: http://downloads.vagrantup.com/tags/v1.2.2
3. git clone https://gerrit.wikimedia.org/r/p/mediawiki/vagrant.git
4. Edit puppet/manifests/site.pp and uncomment the role you want to check out.
5. Run 'vagrant up' from the repository's root directory.
Finally: wait! The first run takes an obnoxiously long time (15-20
minutes). Subsequent runs are much faster (~5 seconds if there are no
major configuration changes.)
The documentation on MediaWiki.org is still meager, but it is
concentrated here: http://www.mediawiki.org/wiki/Mediawiki-Vagrant
If you're interested in using MW-V to document and automate your
development setup, get in touch -- I'd be happy to help. I'm 'ori-l'
on IRC, and I'll be at the Amsterdam Hackathon later this month too.
Finally, if you're interested in how this relates to Labs (short
answer: the use-cases are largely complementary), Andrew Bogott and I
have an open submission for a Wikimania talk on this subject:
https://wikimania2013.wikimedia.org/wiki/Submissions/Turnkey_Mediawiki_Test…
We would like to make pages into category pages. If we try to move a page to a category namespace it will not let us. Is there a configuration variable to do that?
Thanks,
Mary
We are running a 100% online version of the browser test automation
workshop with Cucumber we held recently in San Francisco:
Thursday, July 18, 16:00 UTC
Etherpad - IRC - Hangout
More details and time zone conversion:
https://www.mediawiki.org/wiki/Meetings/2013-07-18
If you plan to come, please sign up at the wiki page.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#The_Wikipe…
Jake (User:Ocaasi) needs some help and has written up a spec -- I
include part of it here:
Background: The Wikipedia Adventure (TWA) is an onboarding game--a
guided tour to teach new editors how to contribute to Wikipedia. In the
game players are invited to help out at a hypothetical article (Earth),
and along the way they learn skills while interacting with simulated peers.
Goal: Make TWA players feel like they are actually receiving messages
from other editors, when in fact they are just sending messages to
themselves.
Method: Use the Mediawiki Edit API. Have a button (or a link) on a
Wikipedia subpage of Wikipedia:TWA/ use the API to add target text to a
target page. Because different messages are received at different points
in the game, the ability to customize the target text and target page is
critical.
Implementation: Build a JavaScript userscript stored in the user’s
common.js page. The beta-version of the game will later deliver this
script as a gadget (set in user preferences, turned on by default, and
only active from the Wikipedia:TWA/ subspace).
There's more at the Village Pump page. Anyone have a little time to help?
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi everyone!
It seems that the for-profit company can be as open as the community! I
really like the idea of feature poll of the Blue Spice [1] I wonder: have
anyone tried to run something similar for MediaWiki?
In Semantic MediaWiki we also run polls and surveys from time to time, here
is the one: http://semantic-mediawiki.org/wiki/SMW_users_survey_results
I think that such surveys can have surprising results for the developers
and they are surely nice steps to openness in MediaWiki production process.
[1] http://answers.blue-spice.org/index.php/questions
-----
Yury Katkov, WikiVote
