Apologies for crossposting
The Analytics Team is planning to deploy "tab as field delimiter" to
replace the current space as fielddelimiter on the varnish/squid/nginx
servers. We would like to do this on February 1st. The reason for this
change is that we need to have a consistent number of fields in each
webrequest log line. Right now, some fields contain spaces and that require
a lot of post-processing cleanup and slows down the generation of reports.
What is affected and maintained by Analytics
* udp-filter already has support for the tab character
* webstatscollector: we compiled a new version of filter to add support for
the tab character
* wikistats: we will fix the scripts on an ongoing basis.
* udp2log: we have a patch ready for inserting sequence numbers separated
In particular, I would like to have feedback to three questions:
1) Are there important reasons not to use tab as field delimiter?
2) Are there important pieces of logging that expect a space instead of a
tab and that need to be fixed and that I did not mention in this email?
3) Is February 1st a good date to deploy this change? (Assuming that all
preps are finished)
According to  and , Firefox 22 (release June 25, 2013) will change
authorized only if there is already a cookie set on the third-party
This would break most of the automatic login on sister projects on
Wikimedia websites, since the page just after the log in will no more set
cookies of sister projects, and you will have to manually log in to each
domain (of level wikipedia.org, not of level de.wikipedia.org) -- I tested
with Firefox 16.
What could be done to mitigate this effect? According to  Safari
already have this policy; is there some workaround already in place for
Safari users? I don’t see other solutions than displaying some warning to
This is your weekly preview of higher-risk or general "you should be
aware of" items for the slew of deployments coming in the near term.
== During the week of March 18th: ==
* AFTv5 is continuing their rollout of new features and schema changes
* E2 and E3 are switching their deploy windows on Thursday
* LIGHTNING DEPLOYMENT WINDOWS!
== What? What are Lightning deployment windows? ==
Simply, they are short windows, every weekday (except Friday) where
small, quick, and safe* deployments can occur without going through the
trouble of schedule a full deployment window. It is only 30 minutes
long, and the idea is that more than one deploy could happen in the
window (with coordination), so, emphasis on the QUICK. This shouldn't
involve scap'ing anything.
"safe" is a hard word to really pin down in the world of deployments,
but the guideline on the wiki is good:
If other developers express concern, avoid the temptation to reassure
them that everything will be fine. Take it as a sign that you may be
underestimating the complexity of your deployment in your eagerness.
One goal of these is to reduce the randomness of small non-critical
deployments during the day. If you have something that is quick to
deploy but you don't want to wait until your next regularly scheduled
deployment window, wait until this Lightning Deploy window.
The process for using them is outlined more clearly on the wiki page;
please do take a look.
If you have any questions, don't hesitate to ask.
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| [[User:Greg G (WMF)]] A18D 1138 8E47 FAC8 1C7D |
Thanks for your assistance. I'm checking out the pages you listed. If
possible, I also would like to know something about your security
regulations and rules applying to the internal, like what the staff is
forbidden to do in order to ensure the security of information systems?
What software or hardware Wikimedia uses to protect the database?
I'm very pleased that you help my asks.
> On 03/16/2013 02:02 PM, 徐中强 wrote:
> > Hello,
> > I'm a undergraduate in China. I would like to learn about some detailed
> > information about your organization's information security methods and
> > regulations, because I want to use Wikimedia as an example and introduce
> > its security regulations on my Information security lecture.
> > If it is available, would you please give me some description on what
> > information security regulations and methods your organization applies,
> > terms of software, hardware, network, data storage and personnel?
> > Thank you very much :)
> Hi there! Thanks for your email.
> https://www.mediawiki.org/wiki/Security and
> https://www.mediawiki.org/wiki/Security_for_developers will probably
> give you a lot of information. You can also attend a security training
> on Wednesday remotely via IRC -- but only if you read and view
> prerequisite materials. More information at
> http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067630.html .
> Hope this helps!
> Sumana Harihareswara
> Engineering Community Manager
> Wikimedia Foundation
Sent from my Gmail
Sent from my Gmail
Awesome news! Go team Mobile!
On Mon, Mar 18, 2013 at 1:59 PM, Rachel Farrand <rfarrand(a)wikimedia.org>wrote:
> Welcome Adam and Yuri! Looking forward to working with both of you. :)
> On Mon, Mar 18, 2013 at 10:48 AM, Erik Moeller <erik(a)wikimedia.org> wrote:
>> On Mon, Mar 18, 2013 at 10:29 AM, Tomasz Finc <tfinc(a)wikimedia.org>
>> > I'm pleased to announce that the mobile department has two new staff
>> > members. Yuri Astrakhan & Adam Baso join as sr. software developers on
>> > the mobile partner team.
>> Welcome on board, guys. Really looking forward to the next steps with
>> WP Zero. :-)
>> Erik Möller
>> VP of Engineering and Product Development, Wikimedia Foundation
>> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>> Wmfall mailing list
> Wmfall mailing list