[00:30:26] StevenW, jdlrobson: new VectorBeta code should be on test.wiki now [00:30:33] Looking [00:30:47] please test, and I'll push to Mediawiki.org and test2 if it's good. [00:32:11] looks good to me kaldari [00:32:54] kaldari: we're good to go [00:33:19] (reminder that wmf9 is also on Commons and maybe other wikis too) [00:33:44] kaldari: is your deployment done? [00:40:43] greg-g, note it's not fixed. You may have mistakenly thought it is because we have switched that example page to DynamicPageList in the meantime. [00:40:46] see update on the bug [00:54:28] I'm trying to do a git push to gerrit, but it says my authentication fails. I'm using the same username and password as I do for the gerrit website. Is there something special I need to do when doing git push? [00:54:38] what command? [00:55:16] git push origin wmf/1.23wmf9 [00:55:35] You can't bypass gerrit [00:55:58] HEAD:refs/for/wmf/1.23wmf9 [00:57:04] What command should I use instead? [00:57:51] Reedy: The instuctions at https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Case_1b:_extension_changes say to just do git push origin wmf/1.23wmf9 [00:58:57] should I just do a normal git commit and review? [01:00:13] or should I use the interface in gerrit to create the deployment branch for the extension? [01:01:43] git review will work [01:02:07] For [01:02:08] $ git push origin wmf/1.20wmf1 [01:02:22] That's for the original creation of the deployment branch for the extension [01:08:43] Reedy: Benny showed me the "Cherry Pick To" button, which is very handy :) [01:08:53] heh, it is [01:57:51] greg-g: https://wikitech.wikimedia.org/w/index.php?title=Deployments&diff=94315&oldid=94298 should get merged soon, just FYI [03:16:32] marktraceur: like, no need for an LD? [04:15:50] greg-g: No, I want to LD it tomorrow [04:18:03] marktraceur: cool [08:50:18] Hi, is it possible to purge a page using JavaScript? [12:28:19] Morning [12:28:21] What happend with commons mediawiki template? [12:28:25] now width is fixed [12:28:28] and not to 100% [12:32:39] what is mediawiki template? [12:32:55] Wilfredor: it's a "feature" of the beta function "typography update" [12:32:58] smth like Template:MediaWiki? [12:33:40] Raymond_: ok, let me disable this great "feature" function [12:33:44] Raymond_: thanks [12:34:03] Wilfredor: I have disabled it too and filed a bug already this morning [12:34:47] Raymond_: Nice, here is morning in this moment [12:35:08] Wilfredor: morning in Germany I mean :-) [12:35:18] hm [12:35:21] :D [12:35:23] 13:34 [12:35:45] https://bugzilla.wikimedia.org/59815 [13:11:15] Could someone tell me why this cannot be merged? https://gerrit.wikimedia.org/r/#/c/101820/ [13:12:44] arav93: needs a (manual) rebase [15:19:19] Hi! I came here to ask a lame question. Does Ghostscript support the DjVu format? [17:00:30] Anyone is here? [17:01:10] Guest34: Yes! What's up? [17:01:57] We have all got used to the model of communication of posting on user talk pages and in other venues. That is somewhat similar to sending e-mails on the internet. I was wondering, what the admins and experienced editors think about adding the ability to chat? That would allow interactive communication that could be used in dispute solving, or in collaborative editing for example. The editors could decide at any time if they w [17:02:28] The logs of the chats would be either saved in one place, and links to the logs would be posted on the editors' talk pages; or the logs could be posted on the talk pages, perhaps in collapsed form. [17:02:30] I think that's been discussed numerous times [17:03:07] probably will happen at some point though might also be riots if that happens [17:03:11] It should be implemented as a feature of real-time chat on all wikis. [17:03:12] I have posted it on https://meta.wikimedia.org/wiki/Wikimedia_Forum#On-wiki_chat [17:03:52] What has been the decision so far? [17:04:18] a bit ancient but https://www.mediawiki.org/wiki/Future/Real-time_collaboration [17:05:08] actually english wikipedia's articles for creation has a chat /help thing [17:05:12] obscure [17:05:26] https://en.wikipedia.org/wiki/Wikipedia:Article_wizard [17:06:16] But that is not exactly what I'm talking about, is it? [17:06:46] not totally exactly same [17:07:50] Why does it have to be exactly what you're talking about? [17:08:04] Article Wizard is just uses IRC. [17:08:21] Future is much closer. My question, why it is not on agenda? [17:08:30] i think that's what any chat might use in the backend, imho [17:08:37] Future/Real-time I mean. [17:08:46] Presumably because no one sees it to be as valuable as other projects [17:08:50] but with user interface [17:09:12] i doubt there is consensus and some people will rage [17:09:27] but think it's inevitable and will be tried at some point [17:09:30] YOU WANT US TO BE SOCIABLE!?! [17:09:35] :) [17:10:16] There is an extension that does this real-life communication [17:11:17] Guest34: One of the recent developments on real-time collaborative editing was that we tried using TowTruck for RTC - it also includes text chat *and* voice chat over WebRTC. [17:11:28] cscott is the one to blame [17:11:52] But I think the project is still in infancy - we got it shoehorned into wikitext editing, but not super well, and he started working on VE integration [17:12:13] I'M SORRY. TOGETHERJS. [17:12:23] It's a dumb name but it's the new name [17:13:19] What's http://git.wikimedia.org/summary/?r=mediawiki/extensions/MediaWikiChat.git ? [17:14:08] win 40 [17:14:13] * cscott wakes up when TOGETHERJS is SHOUTED [17:14:22] Grumble grumble [17:14:32] cscott: I don't like the new name, it's not as cool [17:14:37] But also I pinged you. [17:14:38] i agree. [17:14:50] yes, actually i wake up when pinged. even softly. [17:15:07] google also recently released a new real time API. fwiw. [17:15:31] but i don't think it's as serverless as mozilla's, i think you have to use google services to some degree. didn't look at it too closely. [17:16:04] https://developers.google.com/drive/realtime/ [17:16:58] s/serverless/self-hostable/? [17:17:10] ish [17:17:21] Looks like it's based on Drive [17:17:25] (from the URL) [17:17:30] the mozilla apis deliberately use a server which is as simple as possible. plus it's also self-hostable. [17:17:45] the google apis seem to use a more complicated server. which is not self-hostable. [17:18:06] but again, i didn't actually look at them all that closely. [17:18:48] greg-g: Confirmed that my metrics fix is merged and will go out this afternoon [17:21:09] Backporting to both deployed versions (whatever bloody versions they are, I dunno) [17:24:13] It requires download. [17:34:33] Do you mean https://www.mediawiki.org/wiki/Extension:WebChat? [17:34:51] It requires downloading additional software. [17:37:01] May we continue the discussion? Got disconnected. [17:39:34] No it doesn't [17:41:04] Anyway, it is different as real/future, am I right? [17:41:11] from real/future [17:43:54] What would be the venue for future/real-time consensus? [17:53:27] real-time consensus? [18:12:19] greg-g: may I use the LD today? MaxSem fixed a bug in collections that would be nice to get out (it looks scary, but it's mostly because it's a revert of a revert of a scary patch with a fix: https://gerrit.wikimedia.org/r/106293) [18:13:22] mwalker, I already subscribed to LD today for mobile stuffs [18:13:29] can deploy that too:) [18:14:55] that's a bigun [18:16:03] MaxSem: you sure? I don't see you on the calendar :) [18:16:14] that's 1 line changed from what was deployed some time ago:P [18:16:39] MaxSem: "Mobile (Kaldari) - https://gerrit.wikimedia.org/r/#/c/105719/ and https://gerrit.wikimedia.org/r/#/c/105408/" <-- that? [18:16:45] Thursday, January 09 00:00–00:30 (Wed) 16:00–16:30 Greg Lightning deploy time [18:16:46] Two fixes for Multimedia metrics gathering (MarkTraceur) [18:16:46] https://gerrit.wikimedia.org/r/106282 [18:16:46] https://gerrit.wikimedia.org/r/106166 [18:16:46] https://gerrit.wikimedia.org/r/106236 [Max] [18:16:46] that was scheduled for yesterday :) [18:17:11] wth, cache! [18:17:18] (seriously I just reloaded it) [18:17:18] do we need bug reports from IE users ? [18:17:39] waits for April [18:20:41] mutante, what kind of reports? [18:21:12] MaxSem: any by users who have browsers that are so old they dont understand SNI [18:21:35] because of https on a single IP [18:21:40] with multi-services [18:24:42] mutante, per https://www.mediawiki.org/wiki/Browser_support#Browser we're no obliged to support IE below 6 [18:24:56] MaxSem: and i said April because of [18:24:57] !ie [18:24:57] sadness. [18:25:03] oh, that changed:) [18:25:10] !ie6 [18:25:10] IE6 is an awful browser, don't use it [18:25:24] oh, so 6 is also affected? [18:25:30] IE6 – XP – April 8 2014 end of extended support [18:25:35] that is what i meant with April [18:25:59] MaxSem: "exceptions being Windows XP+IE & Android 2.3" [18:26:45] <^d> The main thing is usage. It doesn't matter if MSFT ends support for IE6 if we have real number of people using it :\ [18:27:07] that would mean i need an extra IP just for them :/ [18:27:14] grmbl [18:27:38] mutante, of tell them to FOAD and don't redirect them to secure [18:27:53] MaxSem: i have one workaround... [18:28:00] renumber the order of virtual hosts [18:28:03] to just make bugzilla first [18:28:16] then they can all report bugs, just never use etherpad [18:28:31] this isnt about cluster , but misc web server [18:28:36] with misc. services [18:28:41] does EP even work for them? [18:28:47] dunno:) [18:28:58] there is other stuff, but it has minimal number of users [18:29:10] eh, yea, also no planet for them [18:29:25] but i'm thinking if i make one the first, make it BZ [18:29:40] <^d> So they can complain about how nothing else works :p [18:29:50] yes:) [18:30:51] what's the failure mode for them - their crapbrowsers displaying a security warning? [18:31:20] MaxSem: no, them just always getting the first virtual host Apache loads, and that's it [18:31:26] heh [18:31:28] but if they wanted BZ they might get ar.planet [18:31:30] f.e. [18:31:59] make die-ie-die.wikimedia.org first;) [18:32:08] because it's alphabetically, unless i add symlinks like 000-, 001, etc [18:32:13] :) [18:35:09] "dear IE user, if you're seeing it you suck" [18:37:09] yea, ln -s ../sites-available/000-iesucks [19:51:58] Quick question: What should happen if i query the API using "Action=edit", while having Chunked Transfer Encoding enabled? [19:52:20] and what would happen? [19:52:59] Varnish returns a "503, Service unavailable" error without any further information. [19:54:08] Which has confused the heaven out of me for the past few weeks, since my API calls just kept failing (Chunked encoding wasn't supposed to be set to true though) [19:55:35] Kind of wondering if that is "By Design", or if it should return something a tad more er... informative :) [20:12:13] Reedy: Does the branch-making script now make branches for extensions automatically? If so awesome. [20:17:00] marktraceur: It's been able to do it for ages [20:17:06] Like, since it was written [20:17:44] Oh, but someone enabled it for MMV [20:17:59] I guess I maybe saw that patch breeze by and didn't pay enough attention at the time [20:18:02] Yeah, Aaron defaulted to doing it for nearly all extensions [20:18:05] Woo! [20:19:19] * JD|cloud was going to say that Guest34's idea is patently absurd [23:00:35] ciao [23:00:43] !lista [23:00:47] !list [23:00:47] meta.wikimedia; page; Tech [23:00:47] mediawiki-l and wikitech-l are the primary mailing lists for MediaWiki-related issues. See http://lists.wikimedia.org/ for details. [23:00:48] meta.wikimedia; user; MiszaBot [23:00:57] Hi, Manoval