Last modified: 2013-12-15 02:08:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58506, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56506 - enable Flow extension on test2 and a handful of mediawiki.org pages
enable Flow extension on test2 and a handful of mediawiki.org pages
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Sean Pringle
:
Depends on: 58012 57270 57279 58351
Blocks: 31235
  Show dependency treegraph
 
Reported: 2013-11-02 03:12 UTC by spage
Modified: 2013-12-15 02:08 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description spage 2013-11-02 03:12:29 UTC
The Flow extension for user-to-user communication is running on ee-flow.wmflabs.org and on the beta cluster, but interested users don't stick around for dialog, and the lack of SUL is a barrier. So the Flow team would like to get early feedback and testing from users on a production wiki.  Only one or two Talk:Flow_Portal/Xx pages on mediawiki.org will have Flow enabled.

We will submit the config change and continue conversations with Ops and security.
Comment 1 MZMcBride 2013-11-02 21:10:23 UTC
Any reason not to enable Flow on the phase 0 wikis (testwiki, test2wiki, mediawikiwiki)?
Comment 2 Gerrit Notification Bot 2013-11-07 06:32:30 UTC
Change 94106 had a related patch set uploaded by Spage:
Enable Flow discussions on a few test wiki pages

https://gerrit.wikimedia.org/r/94106
Comment 3 Wikifram@gmail.com (Account disabled) 2013-12-03 15:14:44 UTC
Any reason to do this when known major bugs like the lack of all history are not solved? I understand the need for more feedback, but the history (contributions, view history, watchlist, recent changes) needs to be correct, complete, and usable before rolling this out any further.
Comment 4 spage 2013-12-03 19:30:01 UTC
(In reply to comment #3)
> Any reason to do this when known major bugs like the lack of all history are
> not solved?

Yes there are. We want to test the technical aspect of having a cross-wiki DB on an external cluster, which is hard to simulate on labs instances. Also not having single user-login is a disincentive for a lot of would-be testers (thanks for participating despite that). Terminology is confusing, I wouldn't consider this a roll-out or a release.
Comment 5 Wikifram@gmail.com (Account disabled) 2013-12-03 21:12:00 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Any reason to do this when known major bugs like the lack of all history are
> > not solved?
> 
> Yes there are. We want to test the technical aspect of having a cross-wiki DB
> on an external cluster, which is hard to simulate on labs instances. Also not
> having single user-login is a disincentive for a lot of would-be testers
> (thanks for participating despite that). Terminology is confusing, I wouldn't
> consider this a roll-out or a release.

Fair enough. I'll complain a lot harder if you would try the same at enwiki (where deployments were planned as well, but seem to be postponed for the moment, I hope).
Comment 6 MZMcBride 2013-12-03 21:14:29 UTC
(In reply to comment #4)
> Yes there are. We want to test the technical aspect of having a cross-wiki DB
> on an external cluster, which is hard to simulate on labs instances.

Then we need a better testing infrastructure. Please file appropriate bugs where gaps currently exist.

> Terminology is confusing, I wouldn't consider this a roll-out or a release.

Terminology is confusing when people intentionally subvert natural meanings of standard words. This bug is most certainly about a (limited) roll-out/release.
Comment 7 MZMcBride 2013-12-05 04:57:33 UTC
Now scheduled for Tuesday, December 10, 2013.
Comment 8 spage 2013-12-11 01:32:32 UTC
We need a DBA to CREATE DATABASE flowdb on extension1 cluster.  I filed RT ticket 6486, https://rt.wikimedia.org/SelfService/Display.html?id=6486

This and remaining deployment steps are in https://www.mediawiki.org/wiki/Flow_Portal/2013-12_Devployment#Deploy_steps
Comment 9 Gerrit Notification Bot 2013-12-11 22:54:41 UTC
Change 94106 merged by jenkins-bot:
Enable Flow on a few wikis (but no pages)

https://gerrit.wikimedia.org/r/94106
Comment 10 spage 2013-12-12 07:50:49 UTC
mediawiki.org Talk:Flow went live at 2013-12-11 15:24 PST!  Thanks everyone.
Comment 11 MZMcBride 2013-12-15 02:08:43 UTC
https://gerrit.wikimedia.org/r/100911

---
Enable Flow on a few pages

On testwiki, test2wiki, and mw.org, enable Flow for
'Talk:Flow QA', 'Talk:Sandbox' (and 'Talk:Flow' on mw.org)
---

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links