This is in about 90 minutes in #wikimedia-office .
-Sumana
---------- Forwarded message ----------
From: Sumana Harihareswara <sumanah(a)wikimedia.org>
Date: Tue, Mar 4, 2014 at 7:48 PM
Subject: RFC review tomorrow on TitleValue and passwords
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Tomorrow, Chris Steipp will talk about the threat model for passwords
https://www.mediawiki.org/wiki/Requests_for_comment/Passwords , and Daniel
Kinzler will discuss the new TitleValue patch
https://gerrit.wikimedia.org/r/106517 and updated RfC
https://www.mediawiki.org/wiki/Requests_for_comment/TitleValue . If we have
time, we'll talk about the inline diff proposal, but I fear we might have
to push that to another time.
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-05
I'm sorry for the last-minute time decision (90% my fault, 10% timezones).
Please of course feel free to leave comments on the RFCs before and after
the meeting as well!
These meetings move around so we can sometimes accommodate Europe,
Australia, or various bits of North America, depending on who needs to be
in the meeting. This time the meeting's at 2100 UTC on Wed 5 March:
http://www.worldtimebuddy.com/?qm=1&lid=5391959,5128581,2950159,2147714&h=5…
San Francisco: 1pm-2pm, Wed. March 5th
Berlin: 10pm-11pm, Wed. 5 March
Sydney: 8am-9am, Thurs. 6 March
As usual, it's in IRC, in #wikimedia-office on Freenode.
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
This may be extremely ambitious, but I'm keen to kick off development
around the creation of a map namespace during the Zurich hackathon.
The goal would be to setup an editable map namespace that could be
used for a variety of things, one of which would be adding a map view
to the Special:Nearby page provided via the mobile site. The goal is a
proof of concept not necessarily anything production ready (but that
would be great if we could get to that point!)
Please let me know if you would also be interested on hacking such a
thing - https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Geo_Namespace
- or if doing so would be a terrible idea (but if you have to go down
that route please provide constructive reasoning on what would be a
less terrible idea)
Excited to hack on cool things in Zurich!
Hi All,
I plan to work on the project to implement VERP ( Variable Envelope
Return Path ) functionality to MediaWiki Email system. The project is
originally a manifest of bug
46440<https://bugzilla.wikimedia.org/show_bug.cgi?id=46640>.
Where the developers came with the idea of implementing it this summer, as
the entire infrastructure of mail is being rebuilt. I found the project
interesting as I had done a few Networking courses in my 10th class, out of
my interest and VERP could cut down a lot of resource wastage. The
implementation, includes a MW development side, to create a new API to
implement VERP and a System-Ops component - to route VERP bounces to a
script and call the new API.
Jeff Green is mentoring from the Sys-Ops side and Kunal Mehta
(legoktm) from the MW development side. We have already started by building
up the development environment, with two VBoxes, one acting as the
MediaWiki server and another to act as a router, routing all mails in the
channel to valid/invalid cases so that bounces can be observed. We are
planing to move it to labs, once its up.
I had been part of the MediaWiki community since August 2013, and
it's the community to which I could do my first Open Source Contribution. I
would be more than delighted to do a GSoC with the same community.
Currently, I am doing my second year in Computer Science Engineering at
Amrita Vishwa Vidhyapeetham, Kerala, India.
My Proposal:-
https://www.mediawiki.org/wiki/User:01tonythomas/mediawiki_VERP
UserPage :- https://www.mediawiki.org/wiki/User:01tonythomas
Gerrit Changes: Gerrit owner:
01tonythomas<https://gerrit.wikimedia.org/r/#/q/owner:%2201tonythomas+%253C01tonythomas%…>
Please go through my proposal, and comment in where all I need to
improve.
Tony Thomas <http://tttwrites.in>
FOSS@Amrita <http://foss.amrita.ac.in>
*"where there is a wifi,there is a way"*
Hey all,
I recently had a new repository created; and I wanted to create some jobs
for it.
I dutifully created and had merged:
https://gerrit.wikimedia.org/r/#/c/115968/https://gerrit.wikimedia.org/r/#/c/115967/
Hashar told me I then needed to follow the instructions on [1] to push the
jobs to jenkins. Running the script myself was only pain; it kept erroring
out while trying to create the job. Marktraceur managed to create the jobs
after much "kicking down the door" aka running the script multiple times.
It appears that the problem is that
https://integration.mediawiki.org/ci/createItem?name=mwext-FundraisingChart…
to
https://integration.mediawiki.org/?...
So that's a problem? We're still not sure why Mark was able to create the
jobs with perseverance though.
Another problem that I'm seeing is in responsibilities -- supposedly only
jenkins admins (wmf developers) can submit jobs (and then only when it
works). And then, only people with root on galium can apply the Zuul
configs. To me this is clearly not something the average developer is
supposed to be doing.
Would it make sense to have QChris / ^demon create the standard jobs when
they create the repository?
[1]
https://www.mediawiki.org/wiki/Continuous_integration/Tutorials/Adding_a_Me…
~Matt Walker
Wikimedia Foundation
Fundraising Technology Team
*Hi*
*How do I build a python bot/script with JavaScript for the frontend
(ideally as Wikisouorce gadget <https://www.mediawiki.org/wiki/Gadget>).*
*Project is for gsoc2014. So it should be something which can be live on
wikisource gadgets.*
*Thanks*
*---*
*Rohit Dua*
*8ohit.dua*
Hello All,
As should come as no surprise given the number of advance warnings sent
over the past couple months, the time for migration of the tool labs
project from pmtpa to eqiad is at hand!
[This email applies to tools on the Tool Labs /only/; if you have
projects in labs, then you want to refer to the instructions given by
Andrew Bogott in his previous email.]
For roughly the following two weeks maintainers are encouraged to
migrate their tools to the new eqiad datacenter by themselves. At the
end of that "free" migration period, we will migrate the remaining tools
automatically but keep them disabled until the maintainers have the
opportunity to look them over.
You can find status and notes about the Tool Labs migration at:
https://wikitech.wikimedia.org/wiki/Tool_Labs/Migration_to_eqiad
== Migrating Tools ==
Scripts have been provided to ease the transition. From your *user*
account on tools-login.wmflabs.org, you can do:
$ migrate-tool <toolname>
This will prepare your tool for migration, and schedule the data copy.
More details are provided on-screen. Do this for every tool for which
you are the maintainer. (If there is more than one maintainer, any one
of them can perform the migration).
This will also stop any jobs, webservice or cron entries.
Once the copy is complete (you can check the status of the copy by
issuing the migrate-tool command again) you can issue the following
command from tools-login-eqiad.wmflabs.org:
$ finish-migration <toolname>
this will do the eqiad end of the migration. Please be aware that it
may take some time before the copy is started, as they are queued.
Please also note that, to preserve space and bandwidth, log files are
not copied over (that includes files ending in .out, .err and .log). If
you absolutely need to copy them over, then you can compress them first
with gzip.
*** IMPORTANT ***
Migrating tools with those scripts carefully preserves all data IF IT IS
ONLY ATTEMPTED ONCE. If you run into troubles or issues, please contact
me, and we'll fix you up. They will not allow you to try again if
something went wrong unless you work hard at it. Don't.
== Migrating Users ==
You can migrate the contents of your home in pretty much the same way:
$ migrate-user
This will schedule a copy of your home directory to eqiad. There is no
second half of the script to run once it is complete.
== Advanced Users ==
If there are details you want to handle manually, you can 'ssh eqiad'
from either tools-login or tools-dev (that includes being able to scp).
== In case of panic ==
Do not break glass; come on freenode IRC to the #wikimedia-labs channel
and help can be found. :-)
-- Marc