On 10/12/2011 01:18 AM, K. Peachey wrote: Correct. We have no interest in this bug getting fixed. The matter doesn't exist anymore. It is a non-topic. This is the difference from last time this happened. Thanks for understanding. -- Lars Aronsson (lars(a)aronsson.se) Aronsson Datateknik - http://aronsson.se

Before everyone else jumps on Lars here, I'm going to try and make a bit of sense of this situation as I see it (puts on his Sumanah hat). It's primarily a misunderstanding. a) Lars may not be a native english speaker, and is here representing his community's decisions, please do not read too much into his tone. b) The Swedish community clearly did not fully understand that experimental status of LQT, that it is not deemed ready for production use. A review of events as they seem to me: #1 So during the 1.17 upgrade LQT brroke for the Swedish community, they filed bugs and went "it happens" thinking this was fully tested production mw.org supported extension. #2 Then it broke in 1.18 again and they went (and I'm extrapolating here) "ugh, this isn't a one time thing, there are big problems here we don't want to babysit this extension when so many of our users are unhappy every time it breaks, leaving us with non-working talk pages." #3 So they talked it over and decided to go back to regular talk pages. #4 They let us know through mw.org mailing list that they weren't about to use what they view as such a poorly supported extension. Since I love analogies, they feel like they went to the store and bought a game (Rage for the PC), brought it home and it was buggy as hell, they submitted reports about the problems. Then after the next patch it was still buggy. This time they went back to the store and got a refund, they didn't take the time to file meticulous bug reports (that is non-trivial to do for regular users and admins imo). They really don't care anymore about whatever bugs it may have, they've moved on. Of course the misunderstanding here is that LQT is production ready and would operate more-or-less bugfree (in terms of show stoppers and major problems). This just isn't the case. So it's unfortunate that the Swedish community has been operating under this assumption, but they clearly made the right decision for their users if they need something stable right now and aren't ready to deal with big problems right now during upgrades. Lars I hope this clears thing up for you, and you can go back to your community with a bit of enthusiasm restored, we care about LQT, it's getting better, and maybe one day we'll have a "production" ready version that you can try out again and re-evaluate with your users. But that day is not today. status of extensions and who they appropriate for. - Finlay On Tue, Oct 11, 2011 at 8:01 PM, John Du Hart <compwhizii(a)gmail.com> wrote:

The discussion is at http://sv.wikisource.org/wiki/Wikisource:M%C3%B6tesplatsen#1.18-buggar and the talk page http://sv.wikisource.org/wiki/Wikisourcediskussion:M%C3%B6tesplatsen#1.18 I successfully created a LQ thread on my sv.ws talk page. :/ http://sv.wikisource.org/wiki/Anv%C3%A4ndardiskussion:John_Vandenberg -- John Vandenberg

It still seems to be functional on en.wikinews also. Maybe it's configuration specific for se.ws? -Jon On Tue, Oct 11, 2011 at 21:35, Gerard Meijssen <gerard.meijssen(a)gmail.com>wrote;wrote: -- Jon [[User:ShakataGaNai]] / KJ6FNQ http://snowulf.com/ http://ipv6wiki.net/

On Wed, Oct 12, 2011 at 3:08 PM, Niklas Laxström <niklas.laxstrom(a)gmail.com>wrote;wrote: Last time I checked, work on LQT was postponed in favor of MoodBar. With all due respect to new trends of editor retention, isn't the old discussion system one of main things that scares noobs off? -- Best regards, Max Semenik ([[User:MaxSem]])

LQT's got exactly as many developers attached to it as it ever has had: one (part-time). Andrew has continued his work on the backend rewrite, and if you report bugs, he'll fix them. But I completely understand that projects may wish to disable or not adopt LQT given the glacial pace of development. That's consistent with the prioritization in http://strategy.wikimedia.org/wiki/Product_Whitepaper -- we just simply don't have the resources to give it the amount of love that it'll need right now. And while I agree it's tremendously important to replace talk pages (I wrote the original LQT proposal in 2004 for that reason, and shepherded the initial development), it's also tremendously difficult to do right -- not quite Visual Editor scale of complexity, but close. So unless we end up partnering on this e.g. with Wikia or a chapter, it'll likely not pick up again until mid-2012. But until then, we at least owe it to the project and the community to keep it maintained so the codebase doesn't rot and users who have chosen to use it aren't completely frustrated. So please do report bugs and major UI/UX issues, and perhaps we can organize a LQT bug triage soon. -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate