Hi,
On Fri, Dec 6, 2013 at 8:53 AM, Guillaume Paumier
gpaum...@wikimedia.org wrote:
I think the Tech news page makes it simple enough to get involved and
contribute: https://meta.wikimedia.org/wiki/Tech/News#contribute ; We
also have a reasonably-stable schedule, so now we just need more
On 12/06/2013 08:51 PM, Daniel Friesen wrote:
And the MediaWiki development community is separate from Wikimedia and
consists of more than just people developing features intended for the
Wiki[pm]edia community.
I do not believe it should be the responsibility of volunteer MediaWiki
community
K. Peachey wrote:
People that are interested in the version will more than likely already
know about [[Special:Version]], if they want the added onscreen [clutter]
presence they could whip up a gadget or something to pull it from the API.
Any wiki wanting to use a site notice to display version
On Sat, Dec 7, 2013 at 5:19 AM, K. Peachey p858sn...@gmail.com wrote:
People that are interested in the version will more than likely already
know about [[Special:Version]], if they want the added onscreen [clutter]
presence they could whip up a gadget or something to pull it from the API.
On Dec 6, 2013 1:12 PM, Gerard Meijssen gerard.meijs...@gmail.com wrote:
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
How true. Alex asked because of a major upgrade problem on Wikisource which
2013/12/6 Guillaume Paumier gpaum...@wikimedia.org
I think the Tech news page makes it simple enough to get involved and
contribute: https://meta.wikimedia.org/wiki/Tech/News#contribute ; We
also have a reasonably-stable schedule, so now we just need more
people to give a hand. I'm actually
On Fri, Dec 6, 2013 at 9:31 AM, Amir E. Aharoni
amir.ahar...@mail.huji.ac.il wrote:
* How to get developers not to forget to write that.
Quim, Guillaume - ideas on how to improve it?
There's already a reminder at the top of
https://wikitech.wikimedia.org/wiki/Deployments , and Greg does a
On Fri, Dec 6, 2013 at 9:30 AM, John Vandenberg jay...@gmail.com wrote:
How true. Alex asked because of a major upgrade problem on Wikisource which
interrupted almost everyone. See wikisource-l for details.
I think there are times when a community would like a mass notice of some
sort, and
On Fri, 06 Dec 2013 09:31:09 +0100, Amir E. Aharoni
amir.ahar...@mail.huji.ac.il wrote:
Well actually, this reminds of the perennial who should update the
RELEASE-NOTES discussion. It's hard to update it all the time in Gerrit,
because it creates a lot of conflicts, so people don't do it and
On Fri, 06 Dec 2013 08:53:36 +0100, Guillaume Paumier gpaum...@wikimedia.org
wrote:
Developers would be ideally-placed to help identify noteworthy changes
that will affect Wikimedia users, but most find that activity about as
interesting as writing documentation, which says something :)
On 2013-12-06 12:31 AM, Amir E. Aharoni wrote:
The RELEASE-NOTES file should be useful for people who install MediaWiki on
their servers. It isn't so useful for Wikipedia readers and editors. The
Tech News should do the job of RELEASE-NOTES for Wikipedia readers and
editors, and it's easy to
There could be a small-sized version number somewhere on screen. Those who
are interested in would learn where it is and could watch it, while others
won't be disturbed.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
People that are interested in the version will more than likely already
know about [[Special:Version]], if they want the added onscreen [clutter]
presence they could whip up a gadget or something to pull it from the API.
On Sat, Dec 7, 2013 at 4:53 PM, Bináris wikipo...@gmail.com wrote:
There
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
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
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
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
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
36 matches
Mail list logo
