On Tue, Nov 27, 2012 at 11:23 PM, Tim Landscheidt
t...@tim-landscheidt.de wrote:
[...]
Not to quote from another video about GitHub (where issues
have only title and comment), let's not forget Git: No bug-
tracker at all :-).
Tim
According the http://git-scm.com/community page:
Bug reports
Will Wikivoyage be under SUL? If so, when?
--
Bináris
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Good morning,
I'm glad to announce git-review 1.20 is now available in the FreeBSD port tree.
Installation:
cd /usr/ports/devel/git-review/
make install
Vocabulary:
- a port in FreeBSD is a Makefile cookbook to download, compile when
needed and install an application;
- a package is the
Hello,
On Wed, Nov 28, 2012 at 11:00 AM, Bináris wikipo...@gmail.com wrote:
Will Wikivoyage be under SUL? If so, when?
Wikivoyage is already under SUL.
--
Best Regards,
Sébastien Santoro aka Dereckson
http://www.dereckson.be/
___
Wikitech-l mailing
FYI. I will not be posting release announcements here, but feedback on
the implementation is welcome.
Code is at:
https://gerrit.wikimedia.org/r/gitweb?p=translatewiki.git;a=tree;f=melange
Maybe there is interest in making it more generic and use it to make
other extension bundles too. In that
2012/11/28 Sébastien Santoro dereck...@espace-win.org
Hello,
On Wed, Nov 28, 2012 at 11:00 AM, Bináris wikipo...@gmail.com wrote:
Will Wikivoyage be under SUL? If so, when?
Wikivoyage is already under SUL.
You are right, my fault was to come from .com. It works when using .org
directly.
On Tue, 2012-11-27 at 22:23 +, Tim Landscheidt wrote:
If at the moment the priority field neither necessarily
triggers action nor reflects the actual state of affairs,
why even bother and not just delete/hide it from view? This
would free more time to fix bugs.
I don't see how dropping
On Wed, 2012-11-28 at 00:36 +0100, Krinkle wrote:
I don't think adding more fields/values is the solution. Perhaps use milestone
for immediate?
Currently milestones are used in MediaWiki for tarballs (that we don't
create for MW 1.21), in VisualEditor for deployments (VE-2012-12-34),
and
On Mon, 2012-11-26 at 03:00 +, reporter wrote:
MediaWiki Bugzilla Report for November 19, 2012 - November 26, 2012
Trying to locate the script creating this weekly email, I found
wikimedia/bugzilla/modifications/bugzilla-3.6.2/scripts/bugzilla_report.php
in Gerrit.
We're running Bugzilla
These are prompted by Gerrit review comments, but it seems like a hidden
place to discuss them.
The specific background:
A task I am on uses an external library licensed under the Apache2.0
license. Mediawiki core is shipped under a GPL2 license, so I'm guessing
that is the default licence
On Wed, Nov 28, 2012 at 12:18 PM, Luke Welling lwell...@wikimedia.org wrote:
The questions:
Is my assumption that by default we put everything under GPL2 right?
Are other FS/OSS licences OK to use?
Generally, I think the consensus has been GPLv2 preferred, but any
FLOSS license is probably ok.
On Wed, Nov 28, 2012 at 9:32 AM, Andre Klapper aklap...@wikimedia.org wrote:
On Tue, 2012-11-27 at 22:23 +, Tim Landscheidt wrote:
If at the moment the priority field neither necessarily
triggers action nor reflects the actual state of affairs,
why even bother and not just delete/hide it
It was here
http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/bugzilla-3.4.4/scripts/bugzilla_report.php?view=log
My last correspondence was with one of our former engineers Priyanka who
was going to integrate it back in 2010. Doesn't look like that ever
happened before she left.
--tomasz
On Wed, Nov 28, 2012 at 5:32 AM, Andre Klapper aklap...@wikimedia.org wrote:
Right now I'd like to introduce a clear way to mark issues that should
be handled immediately.
This.
Also
On Wed, Nov 28, 2012 at 9:56 AM, bawolff bawolff...@gmail.com wrote:
An alternative way of looking at
Tomorrow, we have two topics on the agenda for the weekly tech chat / brown bag:
* a mobile QA guest speaker: Pete Hodgson, with Khali Young from
ThoughtWorks, will talk about automated testing (and cross-platform
development strategies). See Pete's blog at: http://blog.thepete.net/
* Sumana is
Krinkle
This is awesome.
In honour of this awesome development I made integrating this with
MobileFrontend my first task [1] on return from vacation:
MobileFrontend now has much cleaner code [2]. Great work! :)
[1] https://gerrit.wikimedia.org/r/#/c/35788/
[2]
On 28/11/12 12:28, Niklas Laxström wrote:
* Running of PHPUnit tests is currently broken
Why?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi,
I am the only one, who see this (in attachment) on the top of WMF's Main
Page (https://wikimediafoundation.org/wiki/Home)?
Best regards,
Samat
attachment: wmf_webpage.png___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
2012/11/28 Samat sama...@gmail.com
Hi,
I am the only one, who see this (in attachment) on the top of WMF's Main
Page (https://wikimediafoundation.org/wiki/Home)?
The same thing is happening in Wikidata, see
https://www.wikidata.org/wiki/Wikidata:Project_chat#Dafuq.3F and the main
page.
--
On Wed, Nov 28, 2012 at 11:31 PM, Bináris wikipo...@gmail.com wrote:
2012/11/28 Samat sama...@gmail.com
Hi,
I am the only one, who see this (in attachment) on the top of WMF's Main
Page (https://wikimediafoundation.org/wiki/Home)?
The same thing is happening in Wikidata, see
On Wed, Nov 28, 2012 at 11:40 PM, Samat sama...@gmail.com wrote:
On Wed, Nov 28, 2012 at 11:31 PM, Bináris wikipo...@gmail.com wrote:
2012/11/28 Samat sama...@gmail.com
Hi,
I am the only one, who see this (in attachment) on the top of WMF's Main
Page
On Nov 28, 2012, at 11:29 PM, Samat sama...@gmail.com wrote:
Hi,
I am the only one, who see this (in attachment) on the top of WMF's Main
Page (https://wikimediafoundation.org/wiki/Home)?
Looks like that one got purged in the mean time. I currently see it on:
Code was updated to use h3 while the (cached) skin CSS still had h5
See
http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2012-November/93.html
Note: code was reverted to wmf4, so the problem will appear now in the
reverse.
We should use an intermediate CSS with rules appliying to
Is there a reason not to use the Yahoo championed approach of embedding a
version number in all static file names so you can set a very long cache
expires time and just add new versions to the CDN when a change is made?
I don't know how often our CSS, branding images, scripts, and other static
On Wed, Nov 28, 2012 at 6:48 PM, Luke Welling lwell...@wikimedia.org wrote:
Is there a reason not to use the Yahoo championed approach of embedding a
version number in all static file names so you can set a very long cache
expires time and just add new versions to the CDN when a change is made?
Hi, thank you for all your feedback. I have moved the draft to
https://www.mediawiki.org/wiki/QA/Strategy
And I have integrated the main point of the discussion here: manual
testing activities work better in some conditions than others, and bug
triaging is needed after them.
I have also
On Wed, Nov 28, 2012 at 12:56 PM, bawolff bawolff...@gmail.com wrote:
What I would really like to see is banning users from touching the
priority field. The field is made rather useless by bug reporters who
feel their pet issue is the most important thing to ever happen - and
suddenly there's
Basics: We rolled out 1.21wmf5 to the non-Wikipedia sites today, after a
brief reversion and re-deployment to fix breakage in how we were
displaying some styling. We are on track to deploy 1.21wmf5 to English
Wikipedia on Monday, December 3 per
https://www.mediawiki.org/wiki/MediaWiki_1.21/Roadmap
On Wed, Nov 28, 2012 at 4:21 PM, Chad innocentkil...@gmail.com wrote:
On Wed, Nov 28, 2012 at 6:48 PM, Luke Welling lwell...@wikimedia.org
wrote:
Is there a reason not to use the Yahoo championed approach of embedding a
version number in all static file names so you can set a very long
FYI, for developers who might be interested.
-- Forwarded message --
From: Steven Walling swall...@wikimedia.org
Date: Wed, Nov 28, 2012 at 8:50 PM
Subject: IRC office hours about account creation and login redesign
To: Wikimedia Mailing List wikimedi...@lists.wikimedia.org
Hi
I know the office hours are probably exactly for this kind of question,
but I have to ask just for the sake of general interest - are these
changes going to be pushed to core, or will they remain in extensions,
for instance simply as a permanent feature of enwp only?
On 28/11/2012 21:51,
On Nov 28, 2012 9:07 PM, Isarra Yos zhoris...@gmail.com wrote:
I know the office hours are probably exactly for this kind of question,
but I have to ask just for the sake of general interest - are these changes
going to be pushed to core, or will they remain in extensions, for instance
simply as
I still experience the problem on Wikidata main page in Monobook skin.
--
Bináris
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 28 November 2012 23:54, Platonides platoni...@gmail.com wrote:
On 28/11/12 12:28, Niklas Laxström wrote:
* Running of PHPUnit tests is currently broken
Why?
Because of https://bugzilla.wikimedia.org/42529
There is also one test failure I don't know to fix. The test is marked
as
34 matches
Mail list logo
