Quim,
I like your line of thought here.
The Newsletter extension could be useful in all kind of ways, and I
was glad to see that it's apparently still in active development.
It would be helpful for me to have proposals shown in the newsletter
divided by approximate time horizon (next week, next
Greetings,
Here is another weekly update on the work of the Discovery department. If
you have questions, please ask!
== Highlights ==
* Published Maps Terms of Use [0]
== Discussions ==
=== Search ===
* The time needed to restart our elasticsearch clusters is improving [1]
* Fixed a rare edge ca
Very happy to see the progress as well as the team work on the statement of
purpose and look forward to the next steps. Thank you also to the guidance
and facilitation by Arthur.
On Fri, Dec 16, 2016 at 4:13 PM, Grace Gellerman
wrote:
> +1 to Anna's :)
>
> Good job everyone!
>
> On Fri, Dec 16,
+1 to Anna's :)
Good job everyone!
On Fri, Dec 16, 2016 at 8:10 AM, Anna Stillwell
wrote:
> :)
>
> On Thu, Dec 15, 2016 at 3:09 AM, Pau Giner wrote:
>
>> Hi all,
>>
>> Some months ago we started to define a statement of purpose for design at
>> Wikimedia. We shared our initial iteration and go
*Cross posting on purpose, no excuses made.*
Hi,
At Wikimedia Sverige we have been working on an extension called
Wikispeech. It will be a text-to-speech solution which aim to make the
information on Wikipedia more accessible for people that have limited
abilities to read.
This is Wikimedia Sver
I strongly support "native" Wikipedia lists using Wikidata queries, and by
that I mean proper SPARQL, not Lua hacks.
Listeria is used "in production", e.g. on Welsh (about 17.000 lists in
articles, see https://tools.wmflabs.org/listeria/botstatus.php), but it was
always intended as a proof of conc
img_auth.php is used in some private Wikimedia wikis, so you might be
able to get WMF people to review your changes. It also means that they
will be scrutinized more closely before they're merged.
--
Bartosz Dziewoński
___
Wikitech-l mailing list
Wik
Hi all!
At the ArchCom office hour (aka RFC IRC meeting) on December 14, we discussed
Legoktm's proposal for a deprecation policy for PHP code [1]. This would
supersede the current guideline [2], allowing deprecated code to be removed
after a couple of releases, even if it may still used by some e
Hello everyone,
The draft goals for the Technology and Product teams at the Wikimedia
Foundation have been posted on MediaWiki for FY2016-17, Q3 (January–March) [1]
Goals for this quarter will become final the beginning of January. The Product
and Technology teams regularly post draft goals a
Hello!
Recently I've worked on some MediaWiki setups with enabled "img_auth.php".
During that work I've noticed a few things that I think can be improved, to
make an extension developer's life easier.
I know that this feature is mostly used by private/intranet wikis, so there are
only limited r
On Fri, Dec 16, 2016 at 2:16 PM, Quim Gil wrote:
> Imagine the same approach for new projects/features, security reviews, new
> betas, release plans... This is a good way to scale communications without
> drowning central spaces like Tech News, wikitech-ambassadors or your
> nearest Village Pump.
On Fri, Dec 16, 2016 at 12:51 AM, Pine W wrote:
> The issue which I am attempting to address is not a UI change itself
> (good or bad) but rather communication about proposed and upcoming UI
> changes.
Communication of proposals and changes is a problem indeed. Not just for
UX, the problem is c
On Fri, 16 Dec 2016, at 04:18 PM, Gergo Tisza wrote:
> * write a detailed list of everything you intend to do in March
> * in that month, avoid doing anything that you did not think to put on
> that list
> I think you will gain some insights about the cost of trying to organize
> things far ahead i
On Thu, Dec 15, 2016 at 3:51 PM, Pine W wrote:
> My proposal would be that proposed UI changes which affect large
> proportions of the user base should be announced 3 months in advance.
>
So here is a fun experiment:
* choose an activity you do a lot (say, editing Wikipedia pages)
* write a deta
14 matches
Mail list logo