Welcome Sean!
On Mon, Jun 24, 2013 at 8:17 AM, Ct Woo ct...@wikimedia.org wrote:
Hi All,
The Technical Operations team is pleased to announce Sean Pringle joined us
today ( 24th June, 2013). Among his duties, Sean will be attending to all
aspects of the database layer including management,
On Mon, Jul 1, 2013 at 2:39 PM, Quim Gil q...@wikimedia.org wrote:
We have a very early version of a community metrics dashboard! See the
details below or jump directly to http://www.mediawiki.org/wiki/**
Community_metrics http://www.mediawiki.org/wiki/Community_metrics
Even if the main
On Fri, Jul 19, 2013 at 11:20 AM, C. Scott Ananian
canan...@wikimedia.orgwrote:
It might also be worth going a wikibase release (on its own schedule or
else scheduled shortly after each MW release), that contains a particular
MW version along with version of the extensions that have been
I attempted to install Wikibase the other day and made a fun discovery.
Installing it properly requires the following (12) extensions:
WikibaseClient
Wikibase DataModel
WikibaseLib
Wikibase Repository
DataValues
DataTypes
ValueParsers
ValueView
ValueValidators
ValueFormatters
Diff
Scribunto
And
On Fri, Jul 19, 2013 at 11:44 AM, Jeroen De Dauw jeroended...@gmail.comwrote:
Hey,
What if you want to use wikibase 1.23 and MyAbominationExtension 1.5 that
requires an incompatible version of DataValues and MyAwesomeExtension 1.0
that requires an incompatible version of ValueView?
If
extensions as core-like libraries: MediaWiki's
fun new landmine for admins (Ryan Lane)
4. Re: Git config trick. (Tyler Romeo)
5. Re: MediaWiki extensions as core-like libraries: MediaWiki's
fun new landmine for admins (Jeroen De Dauw)
6. Re: Git config trick. (Roan Kattouw
On Fri, Jul 19, 2013 at 3:33 PM, Yuvi Panda yuvipa...@gmail.com wrote:
(The bot is temporarily being called lolrrit-wm instead of gerrit-wm
until we get some issues fixed. lolrrit-wm is not a permanent nick for
the bot!)
Hello! The old gerrit-wm was a bunch of python scripts running as
On Sat, Jul 20, 2013 at 4:34 AM, Jeroen De Dauw jeroended...@gmail.comwrote:
Hey,
you're adding in a whole new set of incompatibilities.
How so?
Extensions that use any of these extension libaries now depend on the
version of MediaWiki and the version of the extension. That's a new set of
On Sat, Jul 20, 2013 at 2:08 PM, Ryan Lane rlan...@gmail.com wrote:
In case of the components
created for Wikidata, we have been supporting Composer for a while
now,
which is a great fit to our needs.
We in this situation is Wikidata and not the developer community. In
fact
On Sun, Jul 21, 2013 at 9:41 AM, Jeroen De Dauw jeroended...@gmail.comwrote:
What started this thread was Ryan having problems with installing Wikibase.
And I can see why this would not be all that smooth. The components you
need is probably not the biggest hassle. After all, you just need to
On Mon, Jul 22, 2013 at 6:25 AM, Denny Vrandečić
denny.vrande...@wikimedia.de wrote:
I assume Ryan didn't mean to single out the Wikidata development team.
Other teams have done this as well -- the Translate extension depends on
ULS, CodeEditor depends on WikiEditor, Semantic Result Formats
On Mon, Jul 22, 2013 at 7:17 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Mon, Jul 22, 2013 at 9:35 PM, James Forrester
jforres...@wikimedia.orgwrote:
It would imply that this is a preference that Wikimedia thinks is
appropriate. This would be a lie. For a similar example, see the
On Mon, Jul 22, 2013 at 11:13 PM, anubhav agarwal anubhav...@gmail.comwrote:
I was following this
tutorial
https://www.mediawiki.org/wiki/Writing_an_extension_for_deploymentfor
deploying an extension on MediaWiki. It asked me to create a
labs/git/gerrit account.
When I opened the
On Fri, Jul 26, 2013 at 8:41 AM, Greg Grossmeier g...@wikimedia.org wrote:
Full announcement on the blog:
http://blog.wikimedia.org/2013/07/26/future-third-party-releases-mediawiki/
Today, the Wikimedia Foundation is pleased to announce that we have
contracted with two long-time members of
Seems we had the protocols listed explicitly (to disable SSL2) and
TLS1.1/1.2 weren't available in the past when we were using Ubuntu 10.04.
We've been on 12.04 for a while, but the protocol list wasn't updated. I'm
pushing an updated config now. Thanks for letting us know!
On Mon, Jul 29, 2013
On Mon, Jul 29, 2013 at 11:51 AM, C. Scott Ananian
canan...@wikimedia.orgwrote:
That ssllabs link also shows that wikimedia has RC4 encryption enabled
on SSL connections, which offers no real security. This is apparently
related to the TLS 1.0 -vs- TLS 1.1/1.2 issue:
On Mon, Jul 29, 2013 at 2:03 PM, Thomas Gries m...@tgries.de wrote:
Am 29.07.2013 21:31, schrieb Ryan Lane:
That ssllabs link also shows that wikimedia has RC4 encryption enabled
on SSL connections, which offers no real security. This is apparently
related to the TLS 1.0 -vs- TLS 1.1
On Mon, Jul 29, 2013 at 7:34 PM, C. Scott Ananian canan...@wikimedia.orgwrote:
Au contraire: I think WMF has a responsibility to ensure the safety and
security of its editors, who might be working on topics controversial in
their home regions.
Obviously, which is why our SSL security is
On Wed, Jul 31, 2013 at 1:06 PM, David Gerard dger...@gmail.com wrote:
Oh - if anyone can authoritatively compose a WMF blog post on the
state of the move to SSL (the move to logins and what happened there,
the NSA slide, ongoing issues like browsers in China, etc), that would
probably be a
On Wed, Jul 31, 2013 at 1:39 PM, Paul Selitskas p.selits...@gmail.comwrote:
Can we enable full security mode (as an optional feature) geographically
based on the most concerned governments, if the whole thing isn't going
fast due to lack of resources?
No. That's in fact much, much harder.
On Wednesday, July 31, 2013, Ryan Lane wrote:
On Wed, Jul 31, 2013 at 1:06 PM, David Gerard
dger...@gmail.comjavascript:_e({}, 'cvml', 'dger...@gmail.com');
wrote:
Oh - if anyone can authoritatively compose a WMF blog post on the
state of the move to SSL (the move to logins and what
On Wed, Jul 31, 2013 at 9:28 PM, Anthony wikim...@inbox.org wrote:
On Wed, Jul 31, 2013 at 5:59 PM, George Herbert george.herb...@gmail.com
wrote:
The second is site key security (ensuring the NSA never gets your private
keys).
Who theoretically has access to the private keys (and/or
On Sat, Aug 17, 2013 at 10:13 AM, Tyler Romeo tylerro...@gmail.com wrote:
On Fri, Aug 16, 2013 at 9:59 PM, C. Scott Ananian canan...@wikimedia.org
wrote:
Because the other TLS 1.0 ciphers are *even worse*.
On Sun, Aug 18, 2013 at 5:37 AM, rupert THURNER rupert.thur...@gmail.comwrote:
On Sat, Aug 17, 2013 at 10:48 PM, bawolff bawolff...@gmail.com wrote:
yes ken, you are right, lets stick to the issues at hand:
(1) by when you will finally decide to invest the 10 minutes and
properly trace the
On Mon, Aug 19, 2013 at 6:03 PM, Risker risker...@gmail.com wrote:
On 19 August 2013 20:35, Chad innocentkil...@gmail.com wrote:
On Mon, Aug 19, 2013 at 5:32 PM, Tyler Romeo tylerro...@gmail.com
wrote:
Quick question: will the patch that was just merged regarding removing
the
Stay
On Mon, Aug 19, 2013 at 6:21 PM, Risker risker...@gmail.com wrote:
On 19 August 2013 21:09, Ryan Lane rlan...@gmail.com wrote:
On Mon, Aug 19, 2013 at 6:03 PM, Risker risker...@gmail.com wrote:
On 19 August 2013 20:35, Chad innocentkil...@gmail.com wrote:
On Mon, Aug 19, 2013 at 5
On Tue, Aug 20, 2013 at 8:04 PM, MZMcBride z...@mzmcbride.com wrote:
Erik Moeller wrote:
In general, though, I'd prefer for WMF to move away from what could be
characterized as appeasement and towards actively resisting censorship
and monitoring.
I agree with you and I imagine most
We don't consider etherpad archive-worthy. It's always been considered an
ephemeral service and we're not willing to put any effort into to save data
from it. If you care about data that you've personally hosted in it, please
put it somewhere that's meant to be archived.
We don't have backups for
On Sat, Aug 24, 2013 at 1:49 AM, Federico Leva (Nemo) nemow...@gmail.comwrote:
I already have been archiving my stuff from etherpad on wiki, of course,
and I've never ever used etherpad.wmflabs.org because I knew everything
in Labs can die any time, but this doesn't mean that I don't worry for
On Mon, Aug 26, 2013 at 12:55 PM, Trevor Parscal tpars...@wikimedia.orgwrote:
VisualEditor is MIT licensed. It was originally GPLv2 by default as per my
contract with Wikimedia, but early on we got written permission from all
authors to change it. We did this because we wanted to ensure
On Sun, Aug 25, 2013 at 5:15 PM, Jeroen De Dauw jeroended...@gmail.comwrote:
Hey,
I'm curious what the stance of WMF is on BSD, MIT and MPL licensed code. In
particular, could such code be deployed on WMF servers?
Was this just grenade lobbing? You still haven't clarified your question,
If we switch the URLs to HTTPS we'll have issues with users in China and
Iran and we can't really use geoip targeting for this like we are for
log-in.
On Tue, Sep 3, 2013 at 5:40 AM, billinghurst billinghu...@gmail.com wrote:
Now that we push/force/encourage https:// connections, are we going
On Fri, Sep 6, 2013 at 1:08 PM, C. Scott Ananian canan...@wikimedia.orgwrote:
New revelations on NSA capabilities yesterday in the New York Times: see
https://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html for a
jumping off point.
The bottom line seems to be:
1) don't use RC4
On Tue, Sep 10, 2013 at 10:58 AM, Amir Ladsgroup ladsgr...@gmail.comwrote:
I'm not talking about right now. Right now is okay (consensuses of the
community because of availability of SSL of WMF projects since August
25 in Iran) to enable SSL as default like other countries and I'm
asking to
On Wed, Sep 11, 2013 at 8:45 AM, Magnus Manske
magnusman...@googlemail.comwrote:
There was a recent mail saying that Labs is not considered production
stability. Mainly a disagreement about how many 9s in the 99.9% that
represents.
Indeed. I don't want to get into the debate about this
On Wed, Sep 11, 2013 at 7:50 AM, John phoenixoverr...@gmail.com wrote:
tools.wmflabs.org is supposed to be the replacement for the toolserver
which the wmf is basically forcefully shutting down. I started the
migration several months ago but got fed up with the difficulties and
stopped. In
On Mon, Sep 16, 2013 at 3:12 PM, Gabriel Wicke gwi...@wikimedia.org wrote:
Hi,
while tinkering with a RESTful content API I was reminded of an old pet
peeve of mine: The URLs we use in Wikimedia projects are relatively long
and ugly. I believe that we now have the ability to clean this up if
On Mon, Sep 16, 2013 at 4:41 PM, Gabriel Wicke gwi...@wikimedia.org wrote:
On 09/16/2013 03:25 PM, Ryan Lane wrote:
https://www.mediawiki.org/wiki/Manual:Short_URL#URL_like_-_example.com.2FPage_title
*Warning:* this method may create an unstable URL structure and leave
some
page
?
Maybe this is something that could be delivered via a gadget and
enabled in user preferences?
V/r,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
page load.
V/r,
Ryan Lane
[1]
http://www.mediawiki.org/wiki/Extensions_FAQ#How_do_I_disable_caching_for_pages_using_my_extension.3F
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
.
As for the tests, simple tests seem fairly easy to create, as you can
use Selenium IDE to record actions, then output the script in a few
different languages (I'm assuming we'll use PHP). I think the hardest
part is going to be keeping the tests up to date with the code.
Respectfully,
Ryan Lane
be really nice to have this be compatible.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
the
Wikimedia foundation, and the core developers to be very welcoming of
improvements to the software.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Deki did? Deki is/was a fork of MediaWiki.
http://en.wikipedia.org/wiki/MindTouch_Deki
Confluence is also a fairly heavily used enterprise wiki.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
:).
MediaWiki isn't really designed to be an enterprise wiki, but it works
fairly well as one given enough effort. Installing Semantic MediaWiki
and associated extensions gives it a clear advantage over most
enterprise wikis IMO.
Respectfully,
Ryan Lane
Notice that if you use LDAP for this (which really is a good idea),
you can pull the info into the wiki using the External Data extension:
http://www.mediawiki.org/wiki/Extension:External_Data#.23get_ldap_data_-_retrieve_data_from_LDAP_directory
On Wed, Mar 3, 2010 at 2:51 PM, Danese Cooper
fruitful. Can we please move the
discussion back to planning how this is going to work?
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
.
When selenium launches a browser, it does so using a clean profile. It
launches a fresh browser from a new profile every test it runs. This
shouldn't be an issue.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
group name size increased in the schema (bug 11057) so that
all external groups can be synced properly
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
cached, in a way. When a user is added
to a group via $user-addGroup(), it gets added to the local database.
As far as I know everything is stored locally for users, in some way.
I treat the external database as something to be synced with, not as a
real backing store.
Respectfully,
Ryan Lane
in selenese scripts, not via a browser.
http://grid.tesla.usability.wikimedia.org:/console in a browser
will return the environments currently available for the selenese
scripts. Note that some of those environments aren't currently
functional as I work out bugs.
Respectfully,
Ryan Lane
.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
for lightweight
applications that don't need to do actions on a user's behalf without
direct interaction.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
different things. Both would be nice to
have. The following article gives a good idea of the differences:
http://softwareas.com/oauth-openid-youre-barking-up-the-wrong-tree-if-you-think-theyre-the-same-thing
Respectfully,
Ryan Lane
___
Wikitech-l mailing
we should handle moderation and/or admin
rights, please let me know.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
.
Thanks,
GerardM
Odd, this only happens when creating an account with openid. I'll take
a look at this. Thanks for the feedback.
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
On Sat, May 29, 2010 at 12:27 PM, Ryan Lane rlan...@gmail.com wrote:
On Sat, May 29, 2010 at 8:34 AM, Gerard Meijssen
gerard.meijs...@gmail.com wrote:
Hoi,
I created a profile on the torrent... I used my OpenID profile grin... The
problem is that when I am logged in, I lose the sidebar
something out?
Respectfully,
Ryan Lane
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Mar 13, 2012 at 8:10 AM, John Erling Blad jeb...@gmail.com wrote:
Exporting authentication from Mediawiki by OAuth is probably both
acceptable and interesting, even if OAuth is said to give a rather
weak security. It could be that people are a bit confused about OAuth
vs OpenID.
In
I've ran a script to auto-create user accounts for users who had
enough information in their USERINFO file (user name, svn account
name, email address). If you are one of these lucky few (there were
only 28 that didn't already have accounts), then you can follow these
instructions to log in:
My user account on MediaWiki.org is 'SVG' and my user account on
labsconsole.wikimedia.org is 'Tim Weyer'. Is it because I didn't tell
https://svn.wikimedia.org/svnroot/mediawiki/USERINFO/cervidae my username?
In general, it's a great working script.
So, I was given a CSV and was asked to
[I know this isn't the first time USERINFO as a source for git
migration has come up but I don't remember the past discussion; sorry
if I'm covering old ground]
We could just change hashar's script to use labs-name (new key) as
Wiki username (with a fallback to name if there's no labs-name)
On Mon, Mar 19, 2012 at 6:24 PM, Brion Vibber br...@pobox.com wrote:
As some may know, we've restricted videos on Wikimedia sites to the
freely-licensed Ogg Theora codec for some years, with some intention to
support other non-patent-encumbered formats like WebM.
One of our partners in
We already started working on a new virtual cluster known as labs
(wmflabs.org) which purpose is to allow people develop stuff and later
move it to some production, some time ago. I believe it would be nice
to have exactly same environment (probably we could just extend
wmflabs for that)
version? The stable version would be
better if it was more restricted.
On Tue, Mar 27, 2012 at 5:36 AM, Ryan Lane rlan...@gmail.com wrote:
We already started working on a new virtual cluster known as labs
(wmflabs.org) which purpose is to allow people develop stuff and later
move it to some
It already supports sending to multiple channels. I can't go into
details right now, but I'll follow up on this later with more info.
On Wed, Mar 28, 2012 at 6:06 AM, Antoine Musso hashar+...@free.fr wrote:
Le 27/03/12 21:10, Max Semenik a écrit :
I think these notifications should be sent to
Part of the gerrit slowness is that the web server is in eqiad and its
database is in pmtpa. We noticed some slowness of the interface when
moving the gerrit service to a new server. That said, the new server
handles the load much better, so overall it was worth the extra
latency.
We need to
TL;DR: we have no plans for anonymous HTTPS by default, but will
eventually default to HTTPS for logged-in users.
1. It would require an ssl terminator on every frontend cache. The ssl
terminators eat memory, which is also what the frontend caches do.
2. HTTPS dramatically increases latency,
On Mon, Apr 2, 2012 at 12:33 PM, Tim Starling tstarl...@wikimedia.org wrote:
On 02/04/12 06:14, Ryan Lane wrote:
TL;DR: we have no plans for anonymous HTTPS by default, but will
eventually default to HTTPS for logged-in users.
1. It would require an ssl terminator on every frontend cache
On Mon, Apr 2, 2012 at 4:20 PM, Petr Bena benap...@gmail.com wrote:
That's not what I wanted to say, I wanted to say https may cause
troubles with caching, In fact some caching servers have problems
with https since the header is encrypted as well, so they usually just
forward the encrypted
On Mon, Apr 2, 2012 at 6:34 PM, Tei oscar.vi...@gmail.com wrote:
Perhaps have a black list of countries that are know to break the
privacy of communications, then make https default for logued users in
these countries.
This may help because:
- It only affect a subgroup of users (the ones
Indeed. Detecting a potential MITM is useless if you can't determine if
it's real or not. For instance the switch from RapidSSL to DigiCert
certificate was quite suspicious.
I don't know how to best publicise it, though. I suppose we would list
them somewhere like
Now there're users reporting in village pump that
http://bits.wikimedia.org/ is blocked in China Mainland. Users
visiting http://zh.wikipedia.org/ see unstyled pages without scripts
while https://zh.wikipedia.org/ works fine.
Tell them to use https then? Have them petition their Government
We really need to start surveying real statistics on what programming
languages community members know.
I've seen this assertion waved around again and again, but don't see where
it originates from, besides the very unreliable fact that we just don't talk
much about ruby around here.
I for
We've already gone down the Ruby road once. I think a lot of the
people involved with that would say it was a bad call, especially ops.
Ruby at scale can certainly be a lulz engine, especially for those on the
sidelines. This project doesn't seem to place any software demands on the
Ryan, I only ran into it recently. But look over bundler:
http://gembundler.com/rationale.html
If another situation where something needs gems without existing apt
packages comes up it may be a helpful thing to have in your toolkit of
solutions.
Two useful things that bundler seems to
On Sat, Apr 7, 2012 at 12:28 AM, Federico Leva (Nemo)
nemow...@gmail.com wrote:
Now that 1.19 deploy has been completed, it seems a good idea to discuss
about our test wikis.
I see the following problems:
* No inventory of test wikis exist. There are many and they don't follow any
pattern or
Great to have you with us. I'm excited for us to get some awesome work
done in Labs!
On Mon, Apr 9, 2012 at 9:47 AM, Ct Woo ct...@wikimedia.org wrote:
Happy Monday.
Please join me to welcome our latest member (contractor) to the Operations
Engineering team, Faidon Liambotis. Faidon hails
Antoine's welcome to speak his mind freely, like anyone; there's no
party line. I agree with him that we're unlikely to invest any
significant effort in this unless it gains substantial traction and
starts to look like a real alternative. But I don't think Daniel was
asking for that -- he
On Fri, Apr 13, 2012 at 9:27 AM, Platonides platoni...@gmail.com wrote:
On 28/03/12 12:17, Antoine Musso wrote:
Le 28/03/12 04:37, Ryan Lane a écrit :
It already supports sending to multiple channels. I can't go into
details right now, but I'll follow up on this later with more info
Why not just use a queue? We use the job queue for this right now for
nearly the same purpose. The job queue isn't amazing, but it works.
Maybe someone should replace this with a better system while they are
at it?
On Mon, Apr 23, 2012 at 5:45 AM, Daniel Kinzler dan...@brightbyte.de wrote:
Hi
Well, make sure to participate in the development of the system then!
On Fri, Apr 27, 2012 at 3:12 PM, Daniel Friesen
li...@nadir-seen-fire.com wrote:
I still have the same stance on the topic as before:
http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/59502
I really
sorry to drop in, just a question:
why haven't you ever thought about implementing Extension:OpenID ?
Well, this discussion is on OAuth. They do different things.
- Ryan
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
See change: https://gerrit.wikimedia.org/r/#/c/6883/
Faidon and I have been lamenting some security concerns on labsconsole
and decided that two factor authentication could help. We quickly
threw together an extension for HMAC based One Time Passwords (HOTP).
If you've used two factor
I don't think you'll ever find a finished bug-/issue-tracking solution that
caters just as well for newbies and developers. The main reason is (of
course?) that most issue tracking software is written for developers, by
developers with little or no experience or thought as to what makes a good
I heard that there was a plan to merge these wikis to one central wiki
for technical documentation for various projects on wikimedia, what is
the current status of that? Are we going to merge it to labsconsole,
or to wikitech? There are some services atm running on labs and
documentation is
On Mon, Jun 4, 2012 at 2:06 PM, Petr Bena benap...@gmail.com wrote:
I'd be happy to help, however wikitech is restricted wiki, so I guess
I can't really help there, anyway I think it would be best if current
wikitech was kept for historical purposes, and in case we forgot to
move something you
On Mon, Jun 4, 2012 at 2:15 PM, Petr Bena benap...@gmail.com wrote:
Ok, if there is any stuff that can be done on wikitech like
categorization of pages etc I could help with that, but otherwise I
have no idea how I could be useful on that wiki, I have barely any
knowledge of production. What
On Wed, Jun 6, 2012 at 4:09 AM, Lars Aronsson l...@aronsson.se wrote:
On 2012-06-06 00:19, Diederik van Liere wrote:
A workflow where engineers have to bug a Gerrit admin to do something is a
broken workflow:
As something of an outsider/newcomer, I hear two very different
stories. The
I'm not sure if it makes sense to have the Labs/OpenStack/Nova management
interface on this same new wikitech wiki though. This means that all the
community projects running inside labs will/might use this same wiki to
document
their internal structure - which can (and should be) a lot of
Namespaces are usually a pain in the ass. Sj's post on the subject:
https://meta.wikimedia.org/w/index.php?title=Talk:Wikimedia.orgdiff=365735
6oldid=3657294#Separating_the_wheat_from_the_chaff.
From his post: ... but that would address many of the reasons that people
fragment what are
I have never said that moving to IPv6 is a bad idea. What I am
complaining about is the dismissive attitude taken toward the volunteers
that are stuck cleaning up the mess when Engineering decides to do
something, apparently on the spur of the moment, without telling anyone
outside their
The problem was never IPv6. The problem was always about the unspoken
expectation that everyone else would just drop everything else they have
going on to patch up all the stuff that got broken as a result of this
sudden change. I get that this was an exciting step for the engineers who
got
Are the breakages on the site really that massive? We've been getting
little to no reports of breakages.
From what I understand, most of these breakages are in tools and scripts
developed and operated by volunteer developers, not WMF developers. The
big one is Huggle, which on enwp is used
On Tue, Jun 19, 2012 at 3:39 AM, Chris Peterson cpeter...@mozilla.com wrote:
hi, I'm a developer at Mozilla and I have a patch [1] that would switch
Firefox's Wikipedia search box from HTTP to HTTPS.
Who would be an appropriate technical contact at Wikimedia that I can
coordinate with? Is
On Wed, Jun 20, 2012 at 8:39 AM, Martijn Hoekstra
martijnhoeks...@gmail.com wrote:
Great, we've been needing something like this! Do you have a ballpark
figure when you expect the data loss issues to be under control, and maybe
have something for beta testing?
Op 20 jun. 2012 02:33 schreef
It's fixed in:
https://gerrit.wikimedia.org/r/12363
and:
https://gerrit.wikimedia.org/r/12361
Just needs review.
- Ryan
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
The important thing to do is to make the bots channel +m, so only
the bots can talk. Otherwise, development discussion will follow to
the new channel and this is a bad thing.
+1. Splitting devs way from support means support questions go
unanswered by devs. As long as we aren't splitting
I'm especially interested in tasks where there's a lot of work to do --
that way, people can be given lots of hands-on things to do that can
provide practice to help people be more comfortable with tools like git
and gerrit, or more comfortable with the MediaWiki hooks, or where the
task
101 - 200 of 436 matches
Mail list logo
