Le 08/11/13 04:21, Mark A. Hershberger a écrit :
The main thing I've done is a bit of reordering and collection:
* New features
* Breaking changes (collected in a single section)
* Configuration changes
* Bug fixes
* API changes
* Language updates
* Misc changes
I would put the
Le 07/11/13 18:27, C. Scott Ananian a écrit :
It seems to me that having a gerrit (or other) page somewhere which lists
exactly what is currently deployed where (and when the next scheduled
deploy is) is a prerequisite for all of the more aggressive let's mix up
the set of wikis in early
That is a statement, not an explanation.
John
On Thu, Nov 7, 2013 at 4:05 PM, Jon Robson jdlrob...@gmail.com wrote:
From personal experience don't touch cache manifests with a barge pole...
Bear in mind the majority of browsers provide at least 5mb of local storage
and we are talking about
That is a statement, not an explanation.
Please provide a valid explanation why you want to do this.
John
On Thu, Nov 7, 2013 at 9:35 AM, Daniel Friesen
dan...@nadir-seen-fire.com wrote:
Cache manifests are extremely inflexible. The HTTP caching we already
have is more flexible than cache
I'm not interested in writing an entire explanation for you on how cache
manifests work and their faults when you could simply do a web search
for one of the many existing tutorials.
The issues with using cache manifests to try and do this should be
perfectly understandable once someone
Hi,
would anyone experienced (like hashar) be interested in setup of
jekins on wikimedia labs so that we can get a unit test environment
available to all devs for any projects, written in languages like:
* C
* C++
* Python
* PHP
+ other frequently used languages
I think it would be useful for
I noticed there is integration project, but what its status is, I don't know
On Fri, Nov 8, 2013 at 11:21 AM, Petr Bena benap...@gmail.com wrote:
Hi,
would anyone experienced (like hashar) be interested in setup of
jekins on wikimedia labs so that we can get a unit test environment
available
Hi, I am a volunteer contributor requiring sponsorship, but I don't appear
to have received an email regarding it... Please could you look into this?
Thanks
Alex Monk
On Thu, Oct 31, 2013 at 6:39 PM, Quim Gil q...@wikimedia.org wrote:
Hi,
Hey,
What about using TravisCI or any of the many alternatives? I'm not sure
what the benefit would be of setting up and maintaining something like that
yourself.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
TBH I have no idea which sw for this is best, whatever that is working
I am fine with... I thought people are using jenkins for MW, so there
are likely more people who have experience witht hat
On Fri, Nov 8, 2013 at 1:14 PM, Jeroen De Dauw jeroended...@gmail.com wrote:
Hey,
What about using
Le 08/11/13 10:33, Daniel Friesen a écrit :
I'm not interested in writing an entire explanation for you on how cache
manifests work and their faults when you could simply do a web search
for one of the many existing tutorials.
If you could explain to the newbie there like me what a cache
On Fri, Nov 8, 2013 at 9:45 AM, Antoine Musso hashar+...@free.fr wrote:
So what is a cache manifest? :D
tl;dr - Cache manifests are made for offline web apps, and Wikipedia is not
an offline web app.
Cache manifests are a new HTML5 feature that is specifically made for
single page (or, at the
Le 08/11/13 11:24, Petr Bena a écrit :
I noticed there is integration project, but what its status is, I don't know
That is a play ground area. Merely intended to test out new features
for later inclusion in production.
--
Antoine hashar Musso
Le 08/11/13 11:21, Petr Bena a écrit :
would anyone experienced (like hashar) be interested in setup of
jekins on wikimedia labs so that we can get a unit test environment
available to all devs for any projects, written in languages like:
* C
* C++
* Python
* PHP
If the project is hosted
On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote:
In order to get somewhere with this discussion, it would be useful to
know the current practice of other free software projects, using
Bugzilla or not. As a newcomer, can I assign bugs to myself in GNOME,
KDE, Ubuntu, Debian... etc?
In case
On Fri, Nov 8, 2013 at 6:52 AM, Andre Klapper aklap...@wikimedia.orgwrote:
On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote:
In order to get somewhere with this discussion, it would be useful to
know the current practice of other free software projects, using
Bugzilla or not. As a
Again, as far as I'm concerned, we're solving a non-problem. Yes, in
theory it would be nice if everyone easily got all permissions to
everything. But bugzilla is not set up with the antivandal features needed
to make that work. Instead, we should aim to make it possible for
newcomers to easily
Yes, I made a simple unit test suite for huggle, which uses internal
QT unit test system, basically what I need to do is
* periodically pull the latest version of source code from master branch
* build the test suite (if build is failed submit this information)
* execute test suite (qt unit test
to explain how QT unit testing works a bit more, it's basically
another QT project that includes the source code from master branch
and produces a binary file (called tst_testmain) which can be executed
with various parameters and executes the unit tests defined in its
source code, for example:
On Fri, Nov 8, 2013 at 12:38 AM, Erik Moeller e...@wikimedia.org wrote:
What might have some degree of traction, based on the
discussion, is to have some blessed delegation coming from the
original triumvirate of architects.
+1
I'd personally like to see this kept flexible, so that it's
.. 3) it is a nightmare
http://alistapart.com/article/application-cache-is-a-douchebag is a good
read to anyone who is curious to the why.
On 8 Nov 2013 07:06, Tyler Romeo tylerro...@gmail.com wrote:
On Fri, Nov 8, 2013 at 9:45 AM, Antoine Musso hashar+...@free.fr wrote:
So what is a cache
On Thu, Nov 7, 2013 at 10:38 PM, Erik Moeller e...@wikimedia.org wrote:
2) We don't award Architect as a job title beyond the original
triumvirate, but we _do_ introduce a Senior Software Engineer II (same
band as the Architect band), and would define some criteria for that,
among which proven
On Fri, Nov 8, 2013 at 11:33 AM, Jon Robson jdlrob...@gmail.com wrote:
.. 3) it is a nightmare
http://alistapart.com/article/application-cache-is-a-douchebag is a good
read to anyone who is curious to the why.
I wouldn't go so far to say it is a nightmare. The article you linked
blows things
I've used cache manifests for offline applications. It works reasonably
well in that situation. So I wouldn't dismiss it entirely for all purposes.
But it's not the right solution here.
--scott
___
Wikitech-l mailing list
On Fri, Nov 8, 2013 at 9:00 AM, Bryan Davis bd...@wikimedia.org wrote:
I think that picking the title Senior Software Engineer II may be
underselling the value of this highest tier to the outside world. In
my recent job search I saw a bit of the tech ladder side of the org
chart for several
On 11/08/2013 03:55 AM, Alex Monk wrote:
Hi, I am a volunteer contributor requiring sponsorship, but I don't appear
to have received an email regarding it... Please could you look into this?
Sorry, this is only a consequence of an extremely busy week. We hope to
send the email with details to
There was a report of external issues reaching en.wikipedia.org - nginx
timeouts - about 1 hour ago, also reported resolved.
Forwarding in from outages-l as I haven't seen any internal discussion...
-george
-- Forwarded message --
From: Marco Davids (SIDN) marco.dav...@sidn.nl
Yes, there was downtime. Things should be back up now.
-Chad
On Fri, Nov 8, 2013 at 11:43 AM, George Herbert george.herb...@gmail.comwrote:
There was a report of external issues reaching en.wikipedia.org - nginx
timeouts - about 1 hour ago, also reported resolved.
Forwarding in from
This worked beautifully.
Thanks Daniel Friesen,
--Shawn
From: wikitech-l-boun...@lists.wikimedia.org
[wikitech-l-boun...@lists.wikimedia.org] on behalf of Daniel Friesen
[dan...@nadir-seen-fire.com]
Sent: Saturday, November 02, 2013 7:08 PM
To:
On Fri, 8 Nov 2013, at 20:51, Petr Bena wrote:
Hi,
would anyone experienced (like hashar) be interested in setup of
jekins on wikimedia labs so that we can get a unit test environment
available to all devs for any projects, written in languages like:
* C
* C++
* Python
* PHP
+
On Thu, Nov 7, 2013 at 9:06 AM, C. Scott Ananian canan...@wikimedia.orgwrote:
I'm a little puzzled here: this whole discussion is because new owners want
to have the bug actually assigned to them, instead of just commenting, I'm
working on this in the bug?
Let's look at the github model --
On Fri, Nov 8, 2013 at 2:09 PM, Steven Walling steven.wall...@gmail.comwrote:
On Thu, Nov 7, 2013 at 9:06 AM, C. Scott Ananian canan...@wikimedia.org
wrote:
I'm a little puzzled here: this whole discussion is because new owners
want
to have the bug actually assigned to them, instead of
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Maybe Dan Garry could chime in here as well.
___
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling steven.wall...@gmail.comwrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Maybe Dan
On Fri, Nov 8, 2013 at 2:31 PM, Chad innocentkil...@gmail.com wrote:
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling
steven.wall...@gmail.comwrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes
Hello there,
Here's what's coming up in the world of Wikimedia project deployments.
As always, the full known schedule is available on Wikitech:
https://wikitech.wikimedia.org/wiki/Deployments
Next week:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_November_11
== Throughout the week
Petr
I'll try to setup Travis tests to run on every github commit on Monday. :)
That seems like the best solution as the repo is on github!
Also this way you'll be able to see the status of the tests for all
branches and pull requests etc :-)
Addshore
On 8 Nov 2013 17:22, Petr Bena
I forgot one important note about next Thursday's MediaWiki deploy.
It'll include:
* MassMessage [6] rollout to all wikis
Happy days of no longer using a bot for sending newsletters!
[6] https://www.mediawiki.org/wiki/Extension:MassMessage
Greg
quote name=Greg Grossmeier date=2013-11-08
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling steven.wall...@gmail.com wrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Yes.
Rob
On 11/08/2013 11:09 PM, Steven Walling wrote:
I would be okay just turning off assignment.
I don't support turning off assignment. A large number of MediaWiki
projects use only Bugzilla (which is also the only open source tracker
the WMF uses). Even for stuff WMF engineers work on, there
On 11/06/2013 04:54 PM, Chad wrote:
How about we make editbugs self-granting? That is, if you've got editbugs
you can give it to others (like we did with Coder a few years ago). It works
pretty well, scales infinitely, and tends to protect itself against abuse.
I agree with the others that the
41 matches
Mail list logo
