That temporary list still exists. I granted Quim admin rights.

In T162967#3306532, @srishakatux wrote:

In T162967#3306528, @bd808 wrote:

If the bundle names were squashed down to 8.3 filenames they would be something horrible like MEDIAW~1.BUN and MEDIAW~2.BUN

Yup, that's how they were.

Notes: https://etherpad.wikimedia.org/p/hack17strategy

Wrapping the list of images in a begin/end pair of templates solves the issue of multiple slugs, see: https://ca.wikipedia.org/w/index.php?title=Usuari:Ad_Huikeshoven/proves&veaction=edit.

Thank you @matmarex. I implemented in my namespace on nl.wp and it works! See the article: https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/wmhack17?veaction=edit and the begin and end templates: https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/wmhack17_start https://nl.wikipedia.org/wiki/Gebruiker:Ad_Huikeshoven/wmhack17_einde.

Please use the webinterface on mobile devices, including Android. discourse.wmflabs.org displays nicely in a webbrowser on a mobile device. The Discourse Android app is outdated and does not originate from the developers of Discourse.

Presentation: https://commons.wikimedia.org/wiki/File:Wikimania_2016_Hackathon_Learning_Lua.pdf

@daniel please see T100508#2014479 for a clear user story, simple UI and UX idea without the expiry issue you are worried about.

Regarding your question: I did a vagrant up before enabling flow.
On my Windows desktop it works now, and also on my Ubuntu laptop.

(i had done a git pull before my last message)
after

vagrant ssh
sudo apt-get install libpcre3 libpcre3-dev
exit

I get a message about the downgrade you mention
and then varnish does provision

The https://gerrit.wikimedia.org/r/#/c/282911/ patch linked from T132337 doesnot solve the above reprted problem. Please reopen, I get exactly the same error after applying the patch.

Hi Bryan, could you have a look into this please?

On another machine, a laptop, with a fresh install of Ubuntu, I replicated the error with enabling Varnish:

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libpcre3-dev' returned 100: Reading package lists...

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install libpcre3-dev' returned 100: Reading package lists...

I tried

vagrant ssh
sudo apt-get install libpcre3 libpcre3-dev

and tried to provision again, which results in

==> default: Notice: /Stage[main]/Varnish/Exec[build_xkey]/returns: /tmp/build-xkey.sh: line 6: ./autogen.sh: No such file or directory

@Ottomata thanks for looking it to this. I have good news. The good news is that my machine is now provisioned with eventlogging without errors. I solved by vagrant destroy deleting the instal path ~/Vagrant and start over with $ git clone --recursive https://gerrit.wikimedia.org/r/mediawiki/vagrant . Previously I used the .iso image from https://mediawiki-vagrant-image.wmflabs.org/mediawiki-vagrant/ . My guess is there something not good in the .iso image, at least when used at a Windows host @bd808. Question for @Jdforrester-WMF if my solutions works for you?

@Ottomata Here is what I get on a pristine VM. First before pulling your change, and then after pulling your change. Indeed, it didn't affect this problem.

Today I got a related error after enabling flow:

==> default: Error: Could not find command '/vagrant/srv/eventlogging/virtualenv/bin/pip'

Reach out to small wikis about this. Have a conversation at Wikimania for example. Please involve stewards and / or small wiki monitoring team.

In MediaWiki-Vagrant there is a role Flow which depends on the role centralauth. After enabling Flow (and provisioning and waiting for an hour) you'll end up with a farm consisting of

• dev.wiki.local.wmftest.net
• login.wiki.local.wmftest.net
• centralauthtest.wiki.local.wmftest.net
• fr.wiki.local.wmftest.net
• frwiktionary.wiki.local.wmftest.net
• he.wiki.local.wmftest.net
• zhwikivoyage.wiki.local.wmftest.net

For existing registered users on your localhost (dev.wiki.local.wmftest.net) you have to manage your global account in preferences. If you don't you get an error page at login.wiki.local.wmftest.net after log in and you have to go manually to dev.wiki.local.wmftest.net to find your wiki where you are logged in. (I haven't found a way to add additional wikis in this setup.)
Looks to me there is something like a wikifarm role now.

Yesterday I installed MediaWiki-Vagrant from https://mediawiki-vagrant-image.wmflabs.org/wiki/Main_Page and enabled and provisioned Flow. The "No wiki found" error page for a nonexistent *.wiki.local.wmftest.net gives a list of available wikis in the farm. On top is devwiki, which links to http://dev.wiki.local.wmftest.net:8080/ and not to an IP address. Looks like resolved to me.

After enabling Flow I ended up with a small wiki farm. After enabling role interwiki I could manage interwiki links at the page special:interwiki. That might help in the wikidata role as well.

I've got mediawiki-vagrant up and running including visualeditor role. However with enabling flow provision says ""error: pkg.m4 missing, please install pkg-config". How to surpass this hurdle? Where and how should I install pkg-config (I tried manually several places without success).

The "official" and the "we" in the quote of the Mailman 3 Release note is something written from the perspective of the Mailman developer / release team.

@RobLa-WMF , thanks for the kind words. The status of Discourse is a pilot a test and generates feedback about what people like and what people don't like. There are some strong preferences to receive updates or notifications by mail about discussions and to be able not only to reply by mail to a discussion thread but also to be able to create a new thread. Some people have been asking for synchronization of mailing lists and Discourse. As, if and when that materializes Discourse can or will coexist alongside Mailman mailing lists, just like gmane coexists alongside Mailman. Discourse provides an alternative web interface and some extras. GNU Mailman 3.0 also provides a web interface. After an updrade to Mailman 3 there might be a reduced level of interest in moving to Discourse.

In T124690#2025074, @Steko wrote:

Re: Multi lingual interface. Discourse has an internationalised interface, admins can choose the default language but users are able to change to their language of choice from the preferences dialog.

Any test mailman list will do which behaves technically the same as for example wikimedia-l.

My story: As a user when I visit my wachtlist I would want to be able to filter the pages for which changes are displayed on date the page was added to my watchlist.

My story: As a user when I visit my wachtlist I would want to be able to filter the pages for which changes are displayed on date the page was added to my watchlist.

As a user I do not want to set limited timeframe to keep an article on my watchlist. Behind the user story is a *valid* user request.

In T124690#2007048, @Samwilson wrote:

https://discourse.wmflabs.org/ is currently down: 502 Bad Gateway

Thanks for looking into this. I understand it is several days of work no matter which option is chosen. To get this feature some funding or sponsoring is necessary or someone higher up in the hierarchy to allocate resources c.q. prioritize this task amidst the plethora of other tasks. I flag this for later.

Hi @Tgr. Thanks for your analysis. The first option you mention is probably the way to go now. I have asked for a sample Oauth plugin at https://meta.discourse.org/t/does-anyone-have-an-oauth-plugin-sample/38779.

In T125107#1979024, @Steko wrote:

Ideally discourse.wmflabs.org should be working with Wikimedia single-signon (SSO) credentials, apart from the specific problem listed here. Detailed instructions are here and I don't think it should be difficult. This way users could sign in with their Wikimedia credentials. What do you think?

As an admin at https://discourse.wmflabs.org/ I just upgraded the Discourse installation. Discourse has two kinds of sysops "admin" and "moderator". I haven't found out yet if someone with "moderator" rights can upgrade the installation or not. This is something to be aware of that an "admin" can at the browser interface of Discourse with a single mouse click start an upgrade.

In T124829#1967438, @yuvipanda wrote:

There's automatic SSL for things using labs proxies - the latter URL works for me?

On Windows laptop both with Firefox and with Chrome created a new editor and didn't see the big preference dialog. This isn't a mac or ff exclusive issue.

In T31923#1959888, @Qgil wrote:

Related: even if we said that Discourse is not a Q&A system, maybe it is worth noticing that as a result of a discussion in wikimedia-l, now there is a Discourse test instance in https://discourse.wmflabs.org/

I like the part "nobody apart from the project contributors should be forced to use Phabricator. " (A lot of people find in hard to navigate Phabricator, including me).

As a documentation starter:

• This phab: ticket has been announced by Quim Gil on wikimedia-l
• That post links to WMF product development process

moved to graph: as suggestief by Yurik. Thanks for the improvements

Pie charts can now be added with functionality provided by extension:graph

On en.wp I added a https://en.wikipedia.org/wiki/Template:PieChart}template for piecharts, including documentation and template data. @Yurik, the parameters width, height and outerradius have been merged to a single parameter radius.

The template calls has been added to a page in a VE enabled namespace: sandbox. In VisualEditing mode the chart isn't displayed, there is a puzzle piece and another icon (image not available or something). Clicking the edit button on the puzzle piece allows for easy editing of the fields and the data - thought it is now in the above shown JSON form.

Thanks for your comment @Yurik.
So that is a great idea to create a template. I templatified the original pie chart. On the talk page I inserted the pie chart as a template call: {{Gebruiker:Ad Huikeshoven/Taartgrafiek|heigth=125|width=125|innerradius=10|values=[

  {"x": "perziken","y": 100},
  {"x": "pruimen","y": 32},
  {"x": "bessen","y": 80},
  {"x": "aardbeien","y": 46},
  {"x": "bananen","y": 41}
] |outerradius=125|title="Fruits"}}.

Yurik is right. The Extension:Graph can add a piechart. You can see an example here. [1]

nl.wp doesn't recognize xx-XX languages codes like nl-NL, the language templates accept only two letter codes (sometimes three letter codes)