Last modified: 2012-07-04 16:16:41 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 T39778, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37778 - Enable LiquidThreads on fi.wikimedia.org
Enable LiquidThreads on fi.wikimedia.org
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Dereckson
: shell
Depends on:
Blocks: 19699
  Show dependency treegraph
 
Reported: 2012-06-21 13:17 UTC by Niklas Laxström
Modified: 2012-07-04 16:16 UTC (History)
5 users (show)

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


Attachments

Description Niklas Laxström 2012-06-21 13:17:15 UTC
It is better than nothing.
Comment 1 Dereckson 2012-06-21 13:22:52 UTC
I'm inclined to support this request: if LiquidThreads are considered buggy and not ready for deployment on the Wikimedia projects, chapters should be given a broader power of appreciation.

Niklas knows the LiquidThreads issues and so ask it knowingly.
Comment 2 Dereckson 2012-06-21 13:38:37 UTC
Code review: Gerrit change #12366

wernda is willing to take care of any LQT installation, so I'm adding him in cc.
Comment 3 Dereckson 2012-06-21 13:39:00 UTC
[adding 'shell' keyword]
Comment 4 Sam Reed (reedy) 2012-06-21 20:11:39 UTC
All other requests were closed as LATER because of lqt being known buggy..
Comment 5 Dereckson 2012-06-21 21:48:20 UTC
(In reply to comment #4)
> All other requests were closed as LATER because of lqt being known buggy..

As I indicated in comment 1, all other requests were from regular WMF projects. This request have came from a Wikimedia chapter. I'm confident we can be more flexible on what we deliver to those wikis, as long as they know what they are doing and it doesn't have a negative impact on our infrastructure.
Comment 6 Sam Reed (reedy) 2012-06-21 23:29:46 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > All other requests were closed as LATER because of lqt being known buggy..
> 
> As I indicated in comment 1, all other requests were from regular WMF projects.
> This request have came from a Wikimedia chapter. I'm confident we can be more
> flexible on what we deliver to those wikis, as long as they know what they are
> doing and it doesn't have a negative impact on our infrastructure.

No they weren't. Of the "not dones":

Wikimedia Brazil https://bugzilla.wikimedia.org/show_bug.cgi?id=25609

Meta https://bugzilla.wikimedia.org/show_bug.cgi?id=33635
Comment 7 Dereckson 2012-06-22 06:26:39 UTC
Niklas, could you give a rationale better developed than "It is better than nothing." explaining why you would like the extension?
Comment 8 Niklas Laxström 2012-06-22 11:30:08 UTC
Because we want most recent discussions on the top and manual archiving of topics is just waste of time. Plain watchlists are not enough when one can use Lqt to track conversations and as a TODO list.
Comment 9 Nemo 2012-06-22 12:20:30 UTC
Chapters' wiki are hosted by the WMF but are "owned" by the chapters, much like for instance the board owns boardwiki: they don't need better rationales and such. Nobody can throw an unsupported software on a wiki community, but chapters (which are represented by their boards) can do so to themselves, as long as they don't damage anyone else (and I don't see how they could).
(br.wikimedia is probably not a good example because the unchapter didn't have a board and they didn't even seem to be aware of the issues.)
Comment 10 Nemo 2012-07-04 16:09:48 UTC
Done.

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


Navigation
Links