Users are very confused and worried any time a new version of wiki software
is launched and tested, and some major or minor bug comes invariably out.
A clear message using central sitenotice, with links to doc pages listing
the changes at different levels of detail and to their talk pages to
On Thu, Dec 5, 2013 at 8:28 PM, Alex Brollo alex.bro...@gmail.com wrote:
Users are very confused and worried any time a new version of wiki software
is launched and tested, and some major or minor bug comes invariably out.
A clear message using central sitenotice, with links to doc pages
Hi,
What about subscribing to this list instead? I think that users who
want to see updates, should use relevant information channels, rather
than forcing everyone to see notices they may not be interested in.
On Thu, Dec 5, 2013 at 11:28 AM, Alex Brollo alex.bro...@gmail.com wrote:
Users are
I disagree with Alex, usually people don't give a damn about new
deployments. Just geeks and technical people (poeple who work on templates,
bots, etc.) care about these stuff
Best
On Thu, Dec 5, 2013 at 2:04 PM, Petr Bena benap...@gmail.com wrote:
Hi,
What about subscribing to this list
I disagree that sitenotices are stupid or disruptive. It's a good way
to inform users about really important stuff, which unfortunatelly is
sometimes misused for something irrelevant. However this way everyone
can be informed when needed and that's good. Using this for update
information is, of
On 05.12.2013. 11:37, Petr Bena wrote:
I disagree that sitenotices are stupid or disruptive. It's a good way
to inform users about really important stuff, which unfortunatelly is
sometimes misused for something irrelevant. However this way everyone
can be informed when needed and that's good.
On Thu, 2013-12-05 at 11:28 +0100, Alex Brollo wrote:
Users are very confused and worried any time a new version of wiki software
is launched and tested, and some major or minor bug comes invariably out.
So a constant Be confused and worried, every Thursday! site notice on
Wikipedias (Tuesday
Sitenotice would be an exaggeration. Google and Facebook and millions of
other sites update their software, probably even more frequently than we
do, and without any big notifications to all users every week.
People who consider themselves capable of testing new features should just
sign up to
I am not very happy about this but we came to the case
where it might be useful to explicitly uninstall some
hook(s) for out unit tests.
You might want to checkout MediaWikiTestCase::uninstallHook
https://gerrit.wikimedia.org/r/#/c/99349/
I am not happy about blurring differences between unit
Le 05/12/13 11:28, Alex Brollo a écrit :
Users are very confused and worried any time a new version of wiki software
is launched and tested, and some major or minor bug comes invariably out.
A clear message using central sitenotice, with links to doc pages listing
the changes at different
Le 05/12/13 15:59, Antoine Musso a écrit :
There is a GetHumanTimestamp() that let you override the method
behaviour which is used by the cldr extension.
Was referring to GetHumanTimestamp *hook*. Sorry.
--
Antoine hashar Musso
___
Wikitech-l
Yes, I needed to turn off visual editor because it was altering the
section header 'edit' text which was causing parser tests to fail. I
fixed it like this: https://gerrit.wikimedia.org/r/84436
--scott
___
Wikitech-l mailing list
The sites are updated weekly, sometimes with additional deployments inbetween
the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you subscribe to https://meta.wikimedia.org/wiki/Tech/News , which is
an also weekly newsletter summarising new features and important fixed bugs
On 5 December 2013 13:08, Bartosz Dziewoński matma@gmail.com wrote:
The sites are updated weekly, sometimes with additional deployments
inbetween the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you subscribe to https://meta.wikimedia.org/wiki/Tech/News ,
which is
quote name=Risker date=2013-12-05 time=13:55:42 -0500
On 5 December 2013 13:08, Bartosz Dziewoński matma@gmail.com wrote:
The sites are updated weekly, sometimes with additional deployments
inbetween the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you
The sites are updated weekly, sometimes with additional deployments
inbetween the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you subscribe to https://meta.wikimedia.org/wiki/Tech/News ,
I suggest that MediaWiki uses Twitter to announce new MediaWiki versions
like -
On 12/05/2013 10:08 AM, Bartosz Dziewoński wrote:
I suggest you subscribe to https://meta.wikimedia.org/wiki/Tech/News
, which is an also weekly newsletter summarising new features and
important fixed bugs every week, as well as providing links to the
detailed change logs.
Tech News, yeah!
I
This morning Faidon has deployed a
patchhttps://gerrit.wikimedia.org/r/#/c/99394/1/templates/varnish/mobile-frontend.inc.vcl.erbto
redirect wap.and mobile. subdomains (see also this
patch https://gerrit.wikimedia.org/r/#/c/98058 for the apache side
handling), but later due to some cencerns the
From the apps team: We don't use either of those, so don't worry about
the apps when killing them :)
--
Yuvi Panda T
http://yuvi.in/blog
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Thu, Dec 5, 2013 at 1:23 PM, Yuri Astrakhan yastrak...@wikimedia.orgwrote:
This morning Faidon has deployed a
patch
https://gerrit.wikimedia.org/r/#/c/99394/1/templates/varnish/mobile-frontend.inc.vcl.erb
to
redirect wap.and mobile. subdomains (see also this
patch
On 12/5/13, Risker risker...@gmail.com wrote:
On 5 December 2013 13:08, Bartosz Dziewoński matma@gmail.com wrote:
The sites are updated weekly, sometimes with additional deployments
inbetween the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you subscribe to
Le Thu, 05 Dec 2013 19:08:15 +0100, Bartosz Dziewoński
matma@gmail.com a écrit:
The sites are updated weekly, sometimes with additional deployments
inbetween the scheduled ones. Constant sitenotice would be a bad idea.
I suggest you subscribe to https://meta.wikimedia.org/wiki/Tech/News
How about getting this stuff included in the Signpost? I think that's a
good medium for it.
There used to be a Technology report but I've not seen it for a while...
Dan
On 5 December 2013 10:28, Alex Brollo alex.bro...@gmail.com wrote:
Users are very confused and worried any time a new
On Thu, Dec 5, 2013 at 5:00 PM, Dan Garry dga...@wikimedia.org wrote:
How about getting this stuff included in the Signpost? I think that's a
good medium for it.
There used to be a Technology report but I've not seen it for a while...
Dan
BRION, they called it.
On 12/05/2013 01:22 PM, Brian Wolff wrote:
On 12/5/13, Risker risker...@gmail.com wrote:
Some streamlining of communication processes, and giving consideration to a
quick and straightforward process to reach information that can be done
directly from any WMF wiki, would be a really significant
On Thu, 05 Dec 2013 23:00:04 +0100, Dan Garry dga...@wikimedia.org wrote:
How about getting this stuff included in the Signpost? I think that's a
good medium for it.
Signpost is English-specific, Wikipedia-specific and English-Wikipedia-specific.
--
Matma Rex
On 5 December 2013 23:36, Bartosz Dziewoński matma@gmail.com wrote:
On Thu, 05 Dec 2013 23:00:04 +0100, Dan Garry dga...@wikimedia.org
wrote:
How about getting this stuff included in the Signpost? I think that's a
good medium for it.
Signpost is English-specific, Wikipedia-specific
VE is a BAD idea, its full of holes and bugs
On Tue, Dec 3, 2013 at 4:32 PM, David Gerard dger...@gmail.com wrote:
On 3 December 2013 21:26, Mark A. Hershberger m...@everybody.org wrote:
We've put together RC3 for 1.22.0. Please test the tarball and report
any bugs you find on Bugzilla:
On Tue, Dec 3, 2013 at 4:39 PM, John phoenixoverr...@gmail.com wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does not
make the software itself a bad idea.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Bad idea [to package/install],…
Is what I believe beta was saying Tyler.
On Friday, December 6, 2013, Tyler Romeo wrote:
On Tue, Dec 3, 2013 at 4:39 PM, John phoenixoverr...@gmail.comjavascript:;
wrote:
VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just
Correct, I see how my words can be taken several ways. Right now VE is a
very unstable, bug filled, obnoxious elephant. Given enough time, testing,
and maturity it as a lot of promise.
Right now its like trying to use a rocket like
Hoi,
Let us be honest indeed. The others are not heard when they scream and
shout in their little corner of the world..
Thanks,
Gerard
On 5 December 2013 23:41, Happy Melon happy.melon.w...@gmail.com wrote:
On 5 December 2013 23:36, Bartosz Dziewoński matma@gmail.com wrote:
On Thu,
Hi,
On Thu, Dec 5, 2013 at 10:22 PM, Brian Wolff bawo...@gmail.com wrote:
As it stands we don't really summarize changes very well, which is a
prerequisite for telling people about changes. Occasionally changes
make it to Tech/news, but that seems sporadic.
snip
I think the best way
33 matches
Mail list logo
