Heya folks :)
We've created https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
to keep all the development discussions around Wikidata in one public
place. Feel free to subscribe if you are interested.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community
Reading [1], I'm wondering if we couldn't have a wiki version of this
page that could be updated along the road. For example the text talk
about MySQL and but doesn't talk about the MariaDB migration. By the way
the two The Architecture of Open Source Applications books may find
there place on
On Mon, May 6, 2013 at 5:00 AM, reporter repor...@kaulen.wikimedia.orgwrote:
MediaWiki Bugzilla Report for April 29, 2013 - May 06, 2013
Fresh charts[1] are available.
Željko
--
1: https://www.mediawiki.org/wiki/Bugzilla_Weekly_Report
___
Wikitech-l
Hi,
A discussion has started on-wiki about a global watchlist, and other
related improvements to the watchlist feature.
A few people have started to organize the various bug reports about
watchlists, but there is still much to do before we have a clear
prioritized vision of what the watchlist
Hi,
On Mon, May 6, 2013 at 2:28 PM, Mathieu Stumpf
psychosl...@culture-libre.org wrote:
Reading [1], I'm wondering if we couldn't have a wiki version of this page
that could be updated along the road. For example the text talk about MySQL
and but doesn't talk about the MariaDB migration.
[1]
Hi,
It seems to me that there are 15-20 distinct GSoC projects with interested
mentors, depending on how you count it. Here's the list I compiled:
Core MediaWiki:
- Automatic category redirects
- MediaWiki API 2.0
General extensions:
- Book structures
- Inline commenting
- MediaWiki-Moodle
Le 2013-05-06 15:34, Guillaume Paumier a écrit :
Hi,
On Mon, May 6, 2013 at 2:28 PM, Mathieu Stumpf
psychosl...@culture-libre.org wrote:
Reading [1], I'm wondering if we couldn't have a wiki version of
this page
that could be updated along the road. For example the text talk
about MySQL
and
Hi,
On Sun, Mar 10, 2013 at 2:11 AM, Rob Lanphier ro...@wikimedia.org wrote:
Short version: This mail is fishing for feedback on proposed work on
Gerrit-Bugzilla integration to replace code review tags.
I was wondering: has a decision been made regarding this? I'm resuming
work on (notably)
Only to honor the subject and initial motivation of this thread:
Recently we started drafting an actual Starter Kit, as Mathieu requested:
https://www.mediawiki.org/wiki/Project:New_contributors/Starter_kit
Edits and questions in the discussion page are welcome. In fact with a
bit of focus
On 05/06/2013 05:41 AM, Guillaume Paumier wrote:
A few people have started to organize the various bug reports about
watchlists, but there is still much to do before we have a clear
prioritized vision of what the watchlist feature should become.
fwiw I had already suggested a Bug Day focusing
FYI
-- Forwarded message --
From: Erik Moeller e...@wikimedia.org
Date: Mon, May 6, 2013 at 9:44 AM
Subject: Jared Zimmerman joins Wikimedia Foundation as Director of UX
To: wikimediaannounc...@lists.wikimedia.org
Hi folks,
It’s my great pleasure to announce that today, Jared
Le lundi 06 mai 2013 à 09:14 -0700, Quim Gil a écrit :
Only to honor the subject and initial motivation of this thread:
Recently we started drafting an actual Starter Kit, as Mathieu requested:
https://www.mediawiki.org/wiki/Project:New_contributors/Starter_kit
Edits and questions in the
On 2013-05-06 1:31 PM, Quim Gil q...@wikimedia.org wrote:
On 05/06/2013 05:41 AM, Guillaume Paumier wrote:
A few people have started to organize the various bug reports about
watchlists, but there is still much to do before we have a clear
prioritized vision of what the watchlist feature
What happened to last years gsoc project in this area? Are there people
working on getting it merged?
Patchsets for watchlist are waiting for review for too long.
The GSOC project: https://gerrit.wikimedia.org/r/#/c/16419/
other patchsets waiting for review:
Hi, long email but only for GSoC mentors and curious minds alike.
WARNING: GSoC common sense requires absolute confidentiality about
discussions or resolutions of candidates. You can't share any
confidential information, no matter how evident it looks to you or how
well you get along with a
Hello all,
Let's move our MediaWiki deploy cycle to weekly instead of 2-week.
This will also reduce the number of standing deployment windows
throughout the week by having those projects/teams simply ride the
MediaWiki train.
== Current situation ==
Right now, a new version of MediaWiki is
Extrapolating from our experience from two-week deploy cycles and what
bugs we find at each stage, would moving to a one-week deploy cycle
substantially increase the number of users exposed to really bad bugs?
For instance, if we're currently finding and fixing about 2 deployment
blocker bugs per
On Mon, 06 May 2013 21:04:39 +0200, Greg Grossmeier g...@wikimedia.org wrote:
It takes up to 2 weeks for new features/bug fixes to be rolled out to
the various Wikimedia wikis.
Four weeks, actually, if your change gets merged just after a branching point.
(2 weeks until next branching +
On Mon, May 6, 2013 at 3:04 PM, Greg Grossmeier g...@wikimedia.org wrote:
Let's move our MediaWiki deploy cycle to weekly instead of 2-week.
This will also reduce the number of standing deployment windows
throughout the week by having those projects/teams simply ride the
MediaWiki train.
\o/
Le 06/05/13 21:04, Greg Grossmeier a écrit :
Let's move our MediaWiki deploy cycle to weekly instead of 2-week.
As long as we tend to the hour, I am fine :-]
Weekly deploy is a bit of a challenge since we will have less time to
figure out a solution for any blocking bug, but overall I think it
On Mon, May 6, 2013 at 12:20 PM, Sumana Harihareswara
suma...@wikimedia.org wrote:
Extrapolating from our experience from two-week deploy cycles and what
bugs we find at each stage, would moving to a one-week deploy cycle
substantially increase the number of users exposed to really bad bugs?
quote name=Brad Jorsch date=2013-05-06 time=15:32:19 -0400
One other plan that was discussed in February, if I recall, was
something like this:
week0, Thursday: Deploy wmf1 to test and mw.org
week1, Monday: Deploy wmf1 to first-round wikis
week1, Thursday: Deploy wmf1 to remaining wikis
On Mon, May 6, 2013 at 12:52 PM, Greg Grossmeier g...@wikimedia.org wrote:
Yep, Robla's creating that sample calendar now.
My reasoning for removing that initial separation that may be faulty:
We're running automated and non-automated tests against betalabs, and
that has started producing
On Mon, May 6, 2013 at 3:52 PM, Greg Grossmeier g...@wikimedia.org wrote:
I'm pretty sure this email will have a mid-air collision with Robla and
his writeup of the proposal you outlined, Brad.
I think Robla was the one who suggested it in February, actually. I
was just repeating it here.
quote name=Brad Jorsch date=2013-05-06 time=16:15:33 -0400
On Mon, May 6, 2013 at 3:52 PM, Greg Grossmeier g...@wikimedia.org wrote:
I'm pretty sure this email will have a mid-air collision with Robla and
his writeup of the proposal you outlined, Brad.
I think Robla was the one who
Hi Siebrand, moving your feedback about process to the list.
On 05/06/2013 01:12 PM, Siebrand Mazeland (WMF) wrote:
Here is my ranking
(snip, thank you!)
I would like to provide some feedback, too: The whole process of GSoC
was very confusing to me. Students communicated on melange,
Brian Wolff bawolff at gmail.com writes:
On 2013-05-06 1:31 PM, Quim Gil qgil at wikimedia.org wrote:
On 05/06/2013 05:41 AM, Guillaume Paumier wrote:
A few people have started to organize the various bug reports about
watchlists, but there is still much to do before we have a clear
tl;dr
New OpenID extension version 3.30 20130505
https://www.mediawiki.org/wiki/Extension:OpenID
A new version 3.30 20130505 has been published today.
It's a security fix and fixes some CSRF and XSS vulnerabilities.
The new version is strongly recommended.
Has been tested and works with latest
On 05/06/2013 05:26 PM, Aaron Pramana wrote:
Brian Wolff bawolff at gmail.com writes:
On 2013-05-06 1:31 PM, Quim Gil qgil at wikimedia.org wrote:
On 05/06/2013 05:41 AM, Guillaume Paumier wrote:
A few people have started to organize the various bug reports about
watchlists, but there is
+1
Such a rule would seem rather misguided...
-bawolff
On 2013-05-06 6:58 PM, Sumana Harihareswara suma...@wikimedia.org wrote:
On 05/06/2013 05:26 PM, Aaron Pramana wrote:
Brian Wolff bawolff at gmail.com writes:
On 2013-05-06 1:31 PM, Quim Gil qgil at wikimedia.org wrote:
On
We figured it out. Aaron had been reading a rule wrong, and I've written
Google to ask them to clarify it in the future to prevent future
misreadings. :(
So we can get back to the thread topic - watchlist improvements!
-Sumana
On 05/06/2013 06:33 PM, Brian Wolff wrote:
+1
Such a rule would
On May 3, 2013, at 9:33 PM, Anomie wrote:
On Fri, May 3, 2013 at 1:02 PM, Krinkle wrote:
First of all, I think a lot of our commit subjects are poorly written,
even for a commit message. Having said that, a good commit subject is
also a good release note (that is, if the change itself is
Greg Grossmeier wrote:
== What are the drawbacks of two-weeks? ==
These are mostly known by everyone so I'll just simply state the most
obvious one :-)
It takes up to 2 weeks for new features/bug fixes to be rolled out to
the various Wikimedia wikis.
This is not a bad thing, though. Two
On Mon, May 6, 2013 at 7:20 PM, MZMcBride z...@mzmcbride.com wrote:
The reason I ask about a distinction is that there have been a lot of
changes to Wikimedia wikis lately and likely more to come, as the
Wikimedia Foundation has gotten larger and has more dedicated tech
resources. Overall,
Hello,
The Wikimedia Language Engineering team [1] invites everyone to join
the team’s monthly office hour on May 8, 2013 (Wednesday) at 1700
UTC/1000 PDT on #wikimedia-office. During this session we would be
talking about some our recent activities and updates from the ongoing
projects. Event
No negative experiences at all Erik. The only real problems we've run into
are people complaining they weren't aware of editing features that we
pushed to mobile that users were not aware of due to not using mobile. I
reckon this would be less of an issue in desktop.
I would ___ love ___ to see a
36 matches
Mail list logo
