Dear Scott,
Am 11.08.14 um 05:36 schrieb C. Scott Ananian:
What seems like a deadlock may in fact be parsoid timing out while
trying to connect to your local wiki's API end point. We have had
some users report problems of this sort which were caused by their
firewall or access control
2014-08-10 17:00 GMT+03:00 Michał Łazowik mlazo...@me.com:
Wiadomość napisana przez Nicolas Vervelle nverve...@gmail.com w dniu 10 sie
2014, o godz. 15:45:
I hope it's not an other step from WMF to prevent the application of
community decisions when they not agree with it. I fear that they
Hi Kerry,
I agree that this discussion is happening among a small group of
exprerienced people, and research with newbies about their preferred
communication tools would be valuable.
However, I feel that Kiwi offers a friendlier experience than we have now,
is an incremental improvement to the
On 9 August 2014 21:04, Bryan Davis bd...@wikimedia.org wrote:
On Sat, Aug 9, 2014 at 6:52 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Agreed; mobilefrontend and mobilefrintend-tests would probably work
as
a pair, same with cirrus etc. however the list of roles is getting kinda
long
Hoi,
Code review should be a strictly technical process surely. However the
community CANNOT decide on everything. The WMF has one codebase for
MediaWiki and it explicitly defines with long lead times the things it is
working on. It does invite the community to be involved in the process.
However,
On Mon, 11 Aug 2014, at 19:20, Gerard Meijssen wrote:
Hoi,
Code review should be a strictly technical process surely. However the
community CANNOT decide on everything. The WMF has one codebase for
MediaWiki and it explicitly defines with long lead times the things it is
working on. It does
On Mon, 11 Aug 2014, at 15:17, Pine W wrote:
Following up on a conversation on the gendergap email list, I am discussing
with Freenode the possibility of changing the default web client to one
that is friendlier and has a less technical feel, primarily for the benefit
of new users who access
Hoi,
This is simply not true. At Wikimania there were several sessions where the
topic was what will the technical underpinnings be of our software. It was
also discussed to some extend what kind of effect things may have on a
community. When you are in those conversations you realise that many
What could cause this behavior and how should I configure my system to
prevent the deadlocks? If this is a Bug in either MediWiki or the
VisualEditor or Parsoid, how to further investigate and fix it?
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Il 11/08/2014 11:36, svetlana ha scritto:
On Mon, 11 Aug 2014, at 19:20, Gerard Meijssen wrote:
Hoi,
Code review should be a strictly technical process surely. However the
community CANNOT decide on everything. The WMF has one codebase for
MediaWiki and it explicitly defines with long lead
On 11 August 2014 10:56, Ricordisamoa ricordisa...@openmailbox.org wrote:
The same is going to happen for Flow (which I strongly believe is needed,
but is being deployed untimely)
Flow is neither ready nor proposed for wider deployment yet, so I do not
understand your comment.
Other than its
On Aug 11, 2014 12:04 PM, Dan Garry dga...@wikimedia.org wrote:
On 11 August 2014 10:56, Ricordisamoa ricordisa...@openmailbox.org
wrote:
The same is going to happen for Flow (which I strongly believe is
needed,
but is being deployed untimely)
Flow is neither ready nor proposed for
Then there's something wrong somewhere since what is eventually perceived
by active remote community is just a wall of semi-clueless decisionism.
Vito
Inviato con AquaMail per Android
http://www.aqua-mail.com
Il 11 agosto 2014 11:45:56 Gerard Meijssen gerard.meijs...@gmail.com ha
scritto:
On 11 August 2014 10:56, Ricordisamoa ricordisa...@openmailbox.org wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
We are.
SUL finalisation (which is broadly a blocker to much of this work) is
currently
Replace in XML dump was done automatically and I did not want to remove
timestamp from all revisions (even from current ones) because the wiki is
quite large (about 9000 articles). So I made my own tool to touch such
revision timestamps:
On 11 August 2014 11:08, Martijn Hoekstra martijnhoeks...@gmail.com wrote:
I think this is where part of the problem lies. Will discussion on whether
or not to deploy it to a local wiki still be possible when the WMF decides
it is ready for wider deployment, with a possible no for an answer?
Just a way more to contact flow (and others too) development (in addition to
what Dan Garry wrote, which i can totally underline) is to go into IRC
channel(s) [1]. Many developers are online in IRC, so you can ask, talk and
discuss with them. Just as a note.
[1]
On Mon, 11 Aug 2014, at 19:56, Ricordisamoa wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
THANK YOU! you are, alone, worth a whole engineering team
___
Almost every WMF developer attended Wikimania this year, and there was
quite a lot of fruitful discussion and feedback given. Somewhat
surprisingly (to me, it was my first Wikimania) the tone in person was
quite different than what you might expect from email list traffic. Perhaps
that was
Hi,
finally the change got merged. Now help is needed for the initial
deployment to betacluster.
See:
https://bugzilla.wikimedia.org/show_bug.cgi?id=69298
The goal is to check out files from
https://gerrit.wikimedia.org/r/mediawiki/services/mathoid
to the
/srv/deployment/mathoid/mathoid
On
On Mon, 11 Aug 2014, at 21:42, Chris Keating wrote:
I think the most helpful thing would be to not attempt to start wars, and
particularly not on behalf of anyone or against individuals. We are all on
the same side here: trying to make the projects (and the project
interfaces, as a part
Please do not drop the PhpTagsCodeEditor, PhpTagsDebugger and PhpTags
Widgets extensions.
I'm going to do them.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 10 August 2014 00:51, Ricordisamoa ricordisa...@openmailbox.org wrote:
If we're going to store JavaScript gadgets and Lua modules in a central
wiki (this is planned, I suppose), some coding guidelines would be
certainly useful.
We've talked a good deal about adding a global stash of
Le 10/08/2014 10:27, svetlana a écrit :
I feel that having development carried out by employees hinders
programming the same software as a hobby: for instance, they work in
a single language, and don't need localised documentation
We have developers across all continents with a wide range of
Le 10/08/2014 13:23, Legoktm a écrit :
In honor of bug 1's 10th birthday today, take the time to fix some out
of date documentation or write some missing ones :)
https://bugzilla.wikimedia.org/show_bug.cgi?id=1
-- Legoktm
On that subject, if you see unclear/missing documentation and do
On Mon, Aug 11, 2014 at 10:23 AM, James Forrester
jforres...@wikimedia.org wrote:
On 10 August 2014 00:51, Ricordisamoa ricordisa...@openmailbox.org wrote:
If we're going to store JavaScript gadgets and Lua modules in a central
wiki (this is planned, I suppose), some coding guidelines would be
09.08.2014 16:32, addshorew...@gmail.com пишет:
Great news all!
Some talks at Wikimania got me looking at ALL of the extensions on gerrit,
and thus, some things happened!
We now have zuul / jenkins triggers and jobs for unit tests (non voting) on
ALL extensions on gerrit (excluding empty
Il 11/08/2014 12:27, James Forrester ha scritto:
On 11 August 2014 10:56, Ricordisamoa ricordisa...@openmailbox.org wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
We are.
SUL finalisation (which is
Perhaps the easiest place to start with this sort of opt-in ignoring would
be in discussions; thus I filed a request for a Flow feature
https://bugzilla.wikimedia.org/show_bug.cgi?id=69404 : preference to
ignore comments from specific users (killfile). Thank you for the idea,
svetlana.
Sumana
I've thought about this a fair bit and it's actually a non-trivial
problem. Not technically, mind you - technically, it's trivial.
The problem lies with the whole revert/communicate, or warn/communicate
problem. We have no way for administrators/sysops to mark comments in
C. Scott Ananian canan...@wikimedia.org wrote:
Almost every WMF developer attended Wikimania this year, and there was
quite a lot of fruitful discussion and feedback given. Somewhat
surprisingly (to me, it was my first Wikimania) the tone in person was
quite different than what you might
On Mon, Aug 11, 2014 at 12:24 PM, Tim Landscheidt t...@tim-landscheidt.de
wrote:
{{cn}}
More like the attendees were those who could afford to go and/or were given
scholarship.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
So I'd just like to make one point, I think this superprotect right has
proper technical implications and use cases. In other words, while you guys
may disagree with how it is currently being used (e.g., the MediaViewer
drama and whatnot), I think it is a good idea, and I am actually surprised
On Aug 11, 2014 12:51 PM, Tyler Romeo tylerro...@gmail.com wrote:
More like the attendees were those who could afford to go and/or were
given
scholarship.
Some people could afford to go if it were closer or can't take that much
time off but if it happens to be nearby then they can come for a
Someone could also say the coup d'état has been done when too many people
was traveling.
Anyway there are simply different views between many tech guys
entusiasticly trying to push out new features and many people from the
daily community side emphasizing need for partecipation and
On Aug 11, 2014 1:24 PM, Tim Landscheidt t...@tim-landscheidt.de wrote:
C. Scott Ananian canan...@wikimedia.org wrote:
Almost every WMF developer attended Wikimania this year, and there was
quite a lot of fruitful discussion and feedback given. Somewhat
surprisingly (to me, it was my
On Aug 11, 2014 7:58 AM, svetlana svetl...@fastmail.com.au wrote:
On Mon, 11 Aug 2014, at 19:56, Ricordisamoa wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
THANK YOU! you are, alone, worth a whole
Now, having observed that not only user Eloquence (aka Erik Moeller)
himself engaged in the enforcement of superprotect right on de.wp
[1] but soon after a workaround was published a change was deployed
[2, 3] as counter measurement to block any possible interference can
no longer be
Brian Wolff bawo...@gmail.com wrote:
Almost every WMF developer attended Wikimania this year, and there was
quite a lot of fruitful discussion and feedback given. Somewhat
surprisingly (to me, it was my first Wikimania) the tone in person was
quite different than what you might expect
Hi,
[Putting purely the mw dev hat on]
I'm putting a hat on from pure observer point of view as neither a
member of de.wp nor wmf.
So dont complain that mw fixes a bug in how page protection. If you are
I'm not complaining, I'm observing the events that happened around the
introduction of
Looks like the only change here was to the Wikimedia config, not the
MediaWiki software defaults (and thus be subject to a normal release
schedule). Instead, this seems to have been done quickly just for the
purpose of enforcing something against the wishes of the community.
On Mon, Aug 11, 2014
On Sun, Aug 10, 2014 at 3:12 PM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
hopelessI'd really like to hear Jimbo's opinion on the matter/hopeless
A few years ago, Jimbo came by en.wn, and we were trying to explain to him
how our project infrastructure works. Understand, a central part
On 08/11/2014 01:17 AM, Pine W wrote:
Would WMF or the volunteer dev community be willing to implement
this? If so, is filing a
Bugzilla bug the best way to get the wheels of progress to turn?
It could potentially be installed on Wikimedia Labs. There are
instructions at
Is wikitech-l really the best place for this discussion?
-- Lewis Cawte (Lcawte)
On 11 August 2014 18:44, pi zero wn.pi.z...@gmail.com wrote:
On Sun, Aug 10, 2014 at 3:12 PM, Ricordisamoa
ricordisa...@openmailbox.org
wrote:
hopelessI'd really like to hear Jimbo's opinion on the
On Tue, Aug 12, 2014 at 12:18 AM, Brian Wolff bawo...@gmail.com wrote:
Now, having observed that not only user Eloquence (aka Erik Moeller)
himself engaged in the enforcement of superprotect right on de.wp
[1] but soon after a workaround was published a change was deployed
[2, 3] as counter
On Mon, Aug 11, 2014 at 1:56 PM, Lewis Cawte lewisca...@googlemail.com
wrote:
Is wikitech-l really the best place for this discussion?
-- Lewis Cawte (Lcawte)
Perhaps not. I'd actually replied to the message, and didn't even notice
which list it was on.
Pi zero
No, it is not. Unless we are continuing to discuss the technical implications
of this change, I suggest this be moved to wikimedia-l.
Also, can we please stop using Wikipedia templates in this thread (e.g.,
{{cc}}). Not everybody here is a Wikipedia editor and knows what they mean. I’d
prefer
Hey,
What reusable things come out of each Wikimedia Engineering project?
The Wikibase software, developed primarily by Wikimedia Deutchland,
includes a lot of reusable code. Basically the components listed as
library on this page: https://www.mediawiki.org/wiki/Wikibase/Components
This
On 11/08/14 16:54, Tyler Romeo wrote:
There are many legitimate cases (e.g., office actions and copyright-related
issues) where I could see the superprotect level coming in handy. There are
some cases where the WMF simply cannot afford (usually b/c of legal
reasons) to trust the community, even
On Aug 11, 2014 2:34 PM, James HK jamesin.hongkon...@gmail.com wrote:
Hi,
[Putting purely the mw dev hat on]
I'm putting a hat on from pure observer point of view as neither a
member of de.wp nor wmf.
Note: that i consider my mw dev hat to not involve wmf.
So dont complain that mw
Sorry wrong url, i meant https://gerrit.wikimedia.org/r/#/c/153345/ not the
url i wrote.
Anyways, if the original email was complaining about the config change and
not the delete/edit rights change then its much more reasonable. i thus
take back my previous email.
--bawolff
On Aug 11, 2014 3:45
That is one thing we should take into account when clearing them out.
We should look at the date of last commit or the date of creation and if
they were in the last 6 months of so possibly leave them there.
And naturally take a backup of the deleted repos and shove it somewhere?
Addshore
On 11
On Mon, Aug 11, 2014 at 9:01 AM, Brandon Harris bhar...@wikimedia.org wrote:
Ignoring people by actually ignoring people tends to work pretty well.
This depends on your background, your history with them, and why you
are ignoring them. I'm more likely to just leave a discussion than to
Le Mon, 11 Aug 2014 18:55:22 +0100, Matthew Flaschen
mflasc...@wikimedia.org a écrit:
On 08/11/2014 01:17 AM, Pine W wrote:
Would WMF or the volunteer dev community be willing to implement
this? If so, is filing a
Bugzilla bug the best way to get the wheels of progress to turn?
It could
What issues are they causing by being there?
On Tuesday, August 12, 2014, addshorew...@gmail.com wrote:
That is one thing we should take into account when clearing them out.
We should look at the date of last commit or the date of creation and if
they were in the last 6 months of so possibly
Newbies are going to fail hard at IRC. Pretty much all of the questions Seb
poses for a built-in newbie chat still exist with a built-in Freenode
interface, with the addition of a complicated and often difficult (not to
mention culturally... unique) environment. Much better to think along the
On Mon, Aug 11, 2014 at 2:01 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Before this, there was no expectation that a page could be protected
such that sysops could not alter the content of the superprotected
page.
This is false.
Now, the devs/ops have attempted to introduce that
Frances makes a good point, and now I'm thinking about the different
scenarios we're talking about. There are two big ones:
1) A has a policy or editing dispute with B and they just sort of get on
each other's nerves a lot, so they try to avoid seeing each other's edits,
talk page messages, and
On Tue, Aug 12, 2014 at 3:49 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Mon, Aug 11, 2014 at 2:01 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Before this, there was no expectation that a page could be protected
such that sysops could not alter the content of the
Dear Scott
dear All,
Am 11.08.14 um 11:54 schrieb C. Scott Ananian:
What could cause this behavior and how should I configure my system to
prevent the deadlocks? If this is a Bug in either MediWiki or the
VisualEditor or Parsoid, how to further investigate and fix it?
Wikitech-l
Il 11/08/2014 12:27, James Forrester ha scritto:
On 11 August 2014 10:56, Ricordisamoa ricordisa...@openmailbox.org wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
We are.
SUL finalisation (which is
On 8/11/14, 5:11 PM, svetlana wrote:
Why aren't they implementing a global repository for gadgets, modules,
templates which is (IMHO) what the community needs first?
We are.
SUL finalisation (which is broadly a blocker to much of this work) is
currently underway and should help make a lot
On Mon, Aug 11, 2014 at 6:54 PM, John Mark Vandenberg jay...@gmail.com
wrote:
Was this functionality was ever supported by MediaWiki core?
Of course this is supported by MediaWiki core, although I cannot attest as
to whether it was previously implemented on WMF wikis.
*-- *
*Tyler Romeo*
63 matches
Mail list logo
