Change 233066 merged by jenkins-bot:
Use placeholder HTML rather than rendering the board in getParserOutput

https://gerrit.wikimedia.org/r/233066

In T98270#1573756, @gerritbot wrote:

Change 233881 merged by jenkins-bot:
Have Flow depend on BetaFeatures

https://gerrit.wikimedia.org/r/233881

Just curious, does this affect non-Wikimedia wikis using Flow (without having BetaFeatures, which are specific to Wikimedia)?

On each wiki, the "information" link should point to that wiki's version of Project:Flow, and "discussion" to Project_talk:Flow.

We probably want something similar like the auto-installing templates? Otherwise I'm willing to bet we'll forget to create these at some point :)

It would be great to have some screenshots here of the current status (or some instructions on how to trigger the guided tour) in this ticket.

In T98270#1575210, @QuimGil wrote:

Just curious, does this affect non-Wikimedia wikis using Flow (without having BetaFeatures, which are specific to Wikimedia)?

BetaFeatures is not specific to Wikimedia. It is FOSS (GPLv2+), supported in MediaWiki-Vagrant, and anyone can install it.

Also, this should work fine without BetaFeatures (it's an optional flag, and the hooks will either behave fine or not be called if BetaFeatures is not installed).

In T98270#1580358, @matthiasmullie wrote:

On each wiki, the "information" link should point to that wiki's version of Project:Flow, and "discussion" to Project_talk:Flow.

We probably want something similar like the auto-installing templates? Otherwise I'm willing to bet we'll forget to create these at some point :)

Can we instead change the requirement, and link to MediaWiki.org for the information/discussion links? That's what all the ones on English Wikipedia do.

Oh, I see your question is specifically in regards to the "Have Flow depend on BetaFeatures" MediaWiki-Vagrant commit.

MWV is primarily a development environment, and the Flow Beta Feature is now automatically installed and enabled there. However, someone could still override this to turn it off on their MWV wiki.

Change 235003 had a related patch set uploaded (by Matthias Mullie):
Whitelist Flow opt-in on user talkpage as BetaFeature

https://gerrit.wikimedia.org/r/235003

Change 230648 merged by jenkins-bot:
Beta feature Flow on user talk page

https://gerrit.wikimedia.org/r/230648

Change 233868 merged by jenkins-bot:
Activate guided tour from opt in process

https://gerrit.wikimedia.org/r/233868

There are some problems with opting-out.

Straighforward scenario

1. Create a User talk page and enter some text
2. Then enable "Flow on user talk" in Preferences - Beta
3. User talk page is converted to Flow without any problem. The previous page content is archived at User_talk:username/Archive_1
4. Go back to Preferences - Beta and disable "Flow on user talk" . The User_talk page keeps displaying Flow board and all Flow board's functionality is there.
   
   deployment-fluorine /a/mw-log/exception.log consistently displays the following error :

2015-09-07 17:45:44 deployment-mediawiki02 enwiki exception ERROR: [da2719b3] /wiki/Special:Preferences Flow\Exception\FlowException from line 88 of /srv/mediawiki/php-master/extensions/Flow/includes/BoardMover.php: Main discussion workflow for 127519 not found {"exception":"[Exception Flow\\Exception\\FlowException] (/srv/mediawiki/php-master/extensions/Flow/includes/BoardMover.php:88) Main discussion workflow for 127519 not found\n[stacktrace]\n#0 /srv/mediawiki/php-master/extensions/Flow/Hooks.php(1587): Flow\\BoardMover->prepareMove(integer, Title)\n#1 /srv/mediawiki/php-master/includes/Hooks.php(204): FlowHooks::onTitleMove(Title, Title, User)\n#2 /srv/mediawiki/php-master/includes/MovePage.php(231): Hooks::run(string, array)\n#3 /srv/mediawiki/php-master/extensions/Flow/includes/Import/OptInController.php(137): MovePage->move(User, NULL, boolean)\n#4 /srv/mediawiki/php-master/extensions/Flow/includes/Import/OptInController.php(112): Flow\\Import\\OptInController->movePage(Title, Title)\n#5 /srv/mediawiki/php-master/extensions/Flow/includes/Import/OptInUpdate.php(50): Flow\\Import\\OptInController->disable(Title)\n#6 /srv/mediawiki/php-master/includes/deferred/DeferredUpdates.php(119): Flow\\Import\\OptInUpdate->doUpdate()\n#7 /srv/mediawiki/php-master/includes/MediaWiki.php(706): DeferredUpdates::doUpdates(string)\n#8 /srv/mediawiki/php-master/includes/MediaWiki.php(526): MediaWiki->restInPeace(string)\n#9 [internal function]: Closure$MediaWiki::doPostOutputShutdown()\n#10 {main}\n"}

cucumber features/opt_in.feature:30 works locally but exposes the issue mentioned above on beta.

For the opt-in wikis, we need to add <span class='flow-link-to-archive'></span> around the archive link if the template page already exists before T111098: Run FlowCreateTemplates.php on all Flow-enabled wikis in production is run (i.e. the early adopter wikis).

I've done it on three:

• https://fr.wikipedia.org/w/index.php?title=Mod%C3%A8le:Page_de_discussion_wikitexte_convertie_en_Flow&diff=118475825&oldid=118150418
• https://ca.wikipedia.org/w/index.php?title=Plantilla:P%C3%A0gina_de_discussi%C3%B3_en_wikitext_convertida_a_Flow&diff=15739736&oldid=15426368
• https://www.wikidata.org/w/index.php?title=Template:Wikitext_talk_page_converted_to_Flow&diff=249441657&oldid=239869322

If @Mooeypoo does https://he.wikipedia.org/wiki/%D7%AA%D7%91%D7%A0%D7%99%D7%AA:%D7%93%D7%A3_%D7%A7%D7%95%D7%93_%D7%95%D7%99%D7%A7%D7%99_%D7%9E%D7%95%D7%9E%D7%A8_%D7%9C%D7%96%D7%A8%D7%99%D7%9E%D7%94 , she'll probably be less likely to mess up the syntax.

I think those are the only four in this round.

Text for email notification

Title: New discussion system on User talk:Name

Whether a "User talk" in Title, Button text can be with GENDER ?

Change 237614 had a related patch set uploaded (by Matthias Mullie):
Add GENDER support for opt-in Echo messages

https://gerrit.wikimedia.org/r/237614

Just pushed a new commit to add more GENDER support for Echo notifications.

Opt-out issues can be ignored here - we already have a separate ticket for that: T111830: Fix toggling Flow to false in BetaFeatures (opt-out)

Change 237614 merged by jenkins-bot:
Add GENDER support for opt-in Echo messages

https://gerrit.wikimedia.org/r/237614

Checked in betalabs for enabling 'Flow on user talk' option by

• a new user with previously non-existing User talk page
• a user that has some content on User talk page - the page is properly archived and the link is placed in the page's Board description

Moving to Product Review since opt-out feature is split from this ticket as T111830: Fix toggling Flow to false in BetaFeatures (opt-out).

This looks good ! Waiting on these:

T111830: Fix toggling Flow to false in BetaFeatures (opt-out)
T112784: Link to archived wikitext page isn't added when opting in for 2nd time

MediaWiki:Flow-notification-link-text-enabled-on-talkpage Here need $1 too for gender to user

In T98270#1674017, @Sunpriat wrote:

MediaWiki:Flow-notification-link-text-enabled-on-talkpage Here need $1 too for gender to user

Filed as T113784: GENDER support for Flow-notification-link-text-enabled-on-talkpage.

Change 235003 abandoned by Matthias Mullie:
Whitelist Flow opt-in on user talkpage as BetaFeature

https://gerrit.wikimedia.org/r/235003

I wonder how many bots and user scripts that attempt to leave messages on users' talk pages will be broken by this?

A typical workflow for such a bot/script might be:

1. Test if the page contains the message already (or contains some other message, such as enwiki's progressive warning templates), to avoid flooding.
   1. This might be done by looking at section headers, comments included in the warning, [[https://en.wikipedia.org/w/api.php?modules=query+links|prop=links]], etc.
   2. Some may specifically state how to remove whatever it is the bot looks for (e.g. "remove the comment" or "remove or retitle this section") to enable further bot-messages on the topic.
2. Check if the page's wikitext contains something like "{{bots|optout=NotificationType}}" to allow individual users to opt out of bot notifications of a particular type.
3. Add a new section to the talk page with the content of the message.

How can the above be correctly accomplished on a Flowified talk page? I could probably figure out #3 on my own, but the other steps seem difficult. An announcement should be sent to the mediawiki-api mailing list with such instructions.

In T98270#1684610, @Anomie wrote:

I wonder how many bots and user scripts that attempt to leave messages on users' talk pages will be broken by this?

We've been working and communicating about it for a while. Pywikibot and MessagePoster (in core) provide the main support needed.

A typical workflow for such a bot/script might be:

1. Test if the page contains the message already (or contains some other message, such as enwiki's progressive warning templates), to avoid flooding.
   1. This might be done by looking at section headers, comments included in the warning, [[https://en.wikipedia.org/w/api.php?modules=query+links|prop=links]], etc.

prop=links will work. However, Flow is based on an endless list of topics, each of which is there own page. So to use that method it would need to loop through a set of recent enough topics (e.g. 25) then combine them into a prop=links request, e.g. https://www.mediawiki.org/w/api.php?action=query&titles=Topic:Sojpiv245cuiw67c|Topic:Sojs3simnwvh96fk&prop=links . pywikibot has support for looping through topics.

1. Check if the page's wikitext contains something like "{{bots|optout=NotificationType}}" to allow individual users to opt out of bot notifications of a particular type.

This can be done with view-header, but I don't think pywikibot has support for that yet (but it can be done directly).

Is there a version of prop=links that includes templatelinks (or better yet, a way to *just* check what templates PageX transcludes)

1. Add a new section to the talk page with the content of the message.

Pywikibot supports this now. See https://www.mediawiki.org/wiki/Manual:Pywikibot/Flow . On-wiki scripts can use MessagePoster to create topics without needing to know whether it's wikitext or Flow.

How can the above be correctly accomplished on a Flowified talk page? I could probably figure out #3 on my own, but the other steps seem difficult. An announcement should be sent to the mediawiki-api mailing list with such instructions.

Done.

In T98270#1686822, @Mattflaschen wrote:

1. Check if the page's wikitext contains something like "{{bots|optout=NotificationType}}" to allow individual users to opt out of bot notifications of a particular type.

This can be done with view-header, but I don't think pywikibot has support for that yet (but it can be done directly).

Is there a version of prop=links that includes templatelinks (or better yet, a way to *just* check what templates PageX transcludes)

prop=remplates, but that won't actually work for enwiki's "{{bots|optout=NotificationType}}" since the bot needs to check the content of the "optout" parameter. And the usual semantics are that it has to be directly on the page, transclusion doesn't count.

An announcement should be sent to the mediawiki-api mailing list with such instructions.

Done.

I should have said mediawiki-api-announce. I'll forward it.

Thanks!

All Blocked- by issues and other outstanding issues are fixed.