This issue has been raised in the Wishlist Survey as: Page status color code not always showing
Another useful feature of Discourse is that it can export whole categories (to json, by the sounds of it). So we could make those dumps available, if desired. (I'm not sure how it handles private topics etc.)
New we just need a new release for addwiki/mediawiki-api for these changes. :-)
Wed, Nov 15
:-) XTools will never be far from our minds (even if we don't use it...).
@zhuyifei1999: ah, oops I'm not sure how I overlooked that :-)
I've not been able to reproduce this locally (but I haven't tried everything yet). I wonder what situations lead to the title of a Parser object not being set?
Anyone got time to review the above patch?
Tue, Nov 14
Here's the summary data of gadgets with wiki count, the number of wikis they're default on, and the total/active user counts: F10785334. The active user count isn't enabled on all wikis, so that's not necessarily right.
So there seem to be able 2244 gadgets (or gadget names, rather, because it looks like they sometimes get renamed when being copied between wikis).
I think it makes sense to keep the tool name in the URL. So we'd have discourse-mediawiki.wmflabs.org and discourse.wmflabs.org to start with, which would (if sucessful) move to discourse.mediawiki.org and discourse.wikimedia.org? @Niharika I think there's too much similarity between discourse and discuss for them to be used for different things.
Mon, Nov 13
Here is the query from that email, and leaving aside the LQT and user/babel templates (not that they don't need to be globalized, but are at least all of a type), the top bunch are:
Good point @Qgil, about not needing to stick to PHP.
Fri, Nov 10
This is not yet complete, but a partially-working demo is now live on the CommTech wiki: https://commtech.wmflabs.org./wiki/Special:Preferences
I think the main drawback with StackOverflow is that we'd be splitting things over a number of different Stack Exchange sites: https://stackoverflow.com/ for programming, https://serverfault.com/ for sysadmining, https://webapps.stackexchange.com/ for MediaWiki administration, https://webmasters.stackexchange.com/ for general website stuff... there are more that would probably be relevant. Of course, some projects have their own stack exchange sites, e.g. https://drupal.stackexchange.com/ and https://wordpress.stackexchange.com/ spring to mind, so perhaps there's an option for https://mediawiki.stackexchange.com/ (I think it was proposed once, but they don't keep old proposals visible, or at least I can't find it).
Thu, Nov 9
I can't reproduce this bug with Easy LST enabled, but I can with the (old) OCR gadget. Does that work for any of you?
Any news on this? Can the webservice be restarted?
Wed, Nov 8
This bug may not be related to CodeMirror after all, but is the result of user script interaction (i.e. it doesn't appear with safemode=1).
Are you proposing to make that move in small steps, or to make the first step, which is enough to get GlobalPreferences to work, and then hope that some unspecified team continues the move at some unspecified time in the future? :)
Tue, Nov 7
Actually, I spoke too soon. :-( It doesn't resize when switching between horizontal and vertical proofreading (i.e. when the edit box is at the left, vs. at the top). I can resize by height in both views, but not by width.
Testing in Firefox, the edit box is correctly on the left and syntax highlighting works:
I think the service and a couple of value objects (PreferenceDescription and PreferenceDescrpition?) are the way to go, but that doing so in one leap is too much. https://gerrit.wikimedia.org/r/389665 is an attempt to move toward this better architecture, but not do it all at once; it is fully backwards compatible.
Some discussion currently happening around the WordPress plugin developers' interface: https://make.wordpress.org/plugins/2017/11/06/concept-a-developer-dashboard/ (just for interest's sake).
Mon, Nov 6
Sat, Nov 4
I really like the Stackexchange sites, and keep an eye on a few of them for MediaWiki questions, and I think that if we're to go for the separate Q&A-style site then we should just use the sites that already exist and have large communities. Sure, they're not Libre, but they're already in use and are working. In fact, even if we go with an in-house site, we will always be needing to respond on Stackexchange as well, because people will continue to ask questions over there.
Fri, Nov 3
Yes, definitely can throw a better error, good idea.
Thu, Nov 2
It sounds like this is not a ia-upload issue after all, but we are working on T175680: Switch to chunked uploading for large DjVus anyway.
Wed, Nov 1
The second point is perhaps the same as this? T174173: User Preference Help Message (help-message) should be lined up with the field
Tue, Oct 31
I've updated https://tools.wmflabs.org/ia-upload/ with the above fix; see what you think.
Is there any danger to blindly removing text from pages that return an error code of 10? i.e. just looping through the whole work, and running djvused -u file.djvu -e "select x; remove-txt; save" on the corrupt pages? You're doing it interactively — is there a something that makes you abort the process sometimes?
Mon, Oct 30
Some recent items that this has happened with:
Sun, Oct 29
Thu, Oct 26
I agree that the filesystem cache is probably fine. Like you say, the biggest reason is the fact that we have multiple servers, but the bulk of the cached data probably isn't used by both of them.
Fri, Oct 20
I've renamed that project, and given it the alias of MediaWiki-extensions-GlobalPreferences. Should work now.
Two good ideas here.
Thu, Oct 19
I ran into this issue with GlobalPreferences, and am working around it by instantiating the service just after redefinition:
Wed, Oct 18
Let's leave it till the following week; I'd prefer to be there. Thanks!
(I replied before seeing bd808's reply.)
My understanding is that composer support came before extension registration, and amongst some extension developers (mostly enterprise-y ones, maybe) was seen as a great way to load an extension without having to add anything to LocalSettings.php. Mostly SMW-related extensions, I think (I was working on a SMW company intranet at the time, developing in-house extensions that all loaded themselves without anything further than an entry in composer.json, and I remember converting some extensions to be like this because it was seen as a good practice). So, it was a feature, not a bug! :-)
Oct 18 2017
Oct 16 2017
Oct 14 2017
Is there a general name for this sort of metadata? I'm thinking that it is basically what is called 'coverage' in archival terms:
Oct 13 2017
Yeah, it is a bit confusing. :-(
Oh, no, sorry: it would be able to be enabled globally, and that would apply to the wikis that haven't hidden it — on those ones, the local default would be used always.
Oct 12 2017
@TerraCodes Good point. You mean with $wgHiddenPrefs? Those preferences will also be hidden on Special:GlobalPreferences on that wiki, but they'll be visible and globalizable on other wikis. Similar to how it'll handle preferences for extensions that aren't installed everywhere.
If you're looking for pre-build (partial) data for validated categorized works from Wikisource, https://tools.wmflabs.org/ws-cat-browser/ produces JSON files e.g. https://tools.wmflabs.org/ws-cat-browser/works.json that could be some slight help.
This is common to all uses of HTMLForm.
Oct 11 2017
Oct 10 2017
Oct 9 2017
Oct 6 2017
See also: T153332: Investigation: Global gadgets