[00:12:39] cary: What? [00:13:06] Marybelle, you seem to have infinite rights here [00:13:14] Nope. [00:13:15] op some staff members, like guillom. [00:13:18] This channel is _. [00:15:27] You need Roan. [00:15:32] And you really ought to move the channel. [00:17:42] -ChanServ- Entry Nickname/Host Flags [00:17:42] -ChanServ- ----- ---------------------- ----- [00:17:42] -ChanServ- 1 MZMcBride +votsriRfAF [modified 1 year, 6 weeks, 4 days, 16:06:24 ago] [00:17:42] -ChanServ- 2 RoanKattouw +votsriRfAF [modified 33 weeks, 6 days, 01:11:42 ago] [00:17:42] -ChanServ- ----- ---------------------- ----- [00:17:46] -ChanServ- End of #wikimedia-usability FLAGS listing. [00:18:03] I don't know what _. means [00:18:07] the redirect should be reversed [00:18:10] oh [00:18:12] got it. [00:18:18] It's _. [00:18:21] not -. [00:18:24] right [00:18:29] it's a bad name. [00:18:37] actually, it should be #wikimedia-ux [00:18:45] guillom, so make it :) [00:18:56] just did [00:19:00] You go girl. [00:19:02] http://commons.wikimedia.org/wiki/Commons:Deletion_requests/File:Male_Ejaculation.JPG#File:Male_Ejaculation.JPG [00:19:17] *guillom guesses this is NSFW [00:19:27] cary: You need to clean up Commons. [00:19:38] Marybelle, you need to clean up your bedroom. [00:19:50] You first. [00:20:03] NO U [00:23:35] http://commons.wikimedia.org/wiki/Commons:Deletion_requests/File:Human_male_penis_with_pre-ejaculate.jpg [00:23:40] Commons really is a disgrace. [00:29:15] do I even need to look? [00:29:55] god, that almost made me vomit [00:32:42] And according to Infrogmation, calling images like that "disturbing" isn't a valid reason for deletion. [00:32:56] Commoners have the common sense skills God gave a pistachio nut. [00:32:58] Just saying. [00:34:02] we're having a fun discussion on the admins channel about the goatse image. [00:34:02] WHERE DID GUILLOM GO? [00:34:11] Did it get deleted? [00:34:16] I deleted that last one [00:34:19] I commented on the other one. [00:34:25] Cool. Thanks. [00:34:32] TwoWings "voting" keep is not a rational reason to keep. [00:34:32] http://en.wikipedia.org/wiki/Wikipedia:Files_for_deletion/2010_March_29#File:Goatse.fr_homepage.png is still open? [00:34:37] He wants Commons full of porn. [00:34:50] I'm trying to vandalize the topic of #wikimedia-ux and it's locked. [00:34:56] I need guillom. [00:35:13] I sent him a memo. [01:04:13] wasn't this the day of the great release? :P [01:47:19] hello people [01:48:01] hello TrevorParscal [01:48:15] hi trevor - my sympathies on the stomach unpleasantness [01:48:37] parutron and i are looking at the simplified search on prtotype [01:48:39] thanks - i'm hoping to be done with this pronto.... [01:48:53] howie and I had a discussion for a way to change the behavior [01:49:02] i havn't gotten around to protyping it [01:49:27] oh cool - what's the change? [01:49:39] but it would essentially be that the text in the search box doesn't change when you scroll through the suggestions, and the bottom "containg..." would always show what you typed [01:50:08] and then we could make that "containing..." reachable by the keyboard [01:50:10] why don't we defer the simplified search from tonight's deployment? [01:50:16] and we could wrap the up and down keys [01:50:27] fair enough [01:50:27] great - for me that's the interaction we'd have to get to to be able to deploy [01:50:33] keyboard access to the "contains" [01:50:58] parutron: yeah, I think, as per our conversation, we've just been looking for a nice solution - the one we had was never really that good [01:51:02] but we are dang close [01:51:08] and those changes are failry simple [01:51:25] fairly simple when you're NOT dealing with food poisoning..... [01:51:31] i will hack the prototype of while I'm traveling [01:51:35] indeed [01:51:47] that sounds great to me! [01:51:48] it's better to be conservative tonight [01:51:56] for sure [01:52:07] we need to be learning ops lessons tonight, not UI ones [01:52:10] that way we can also have some time for feedback on the prototype [01:52:11] so let's continue discussion/iteration on search [01:52:20] sounds good to me [01:52:27] which i'd feel uncomortable about too [01:52:40] I think it also aligns with our desire to never release features we know are flawed [01:53:25] if we don't know - sometime deploying can answer those doubts, but if we completly understand something is wrong, deploying it is just being mean to the users [01:54:39] we just haven't had enough time to evaluate the new features we are bundling into the default [01:55:01] aurora just typed QA on my keyboard [01:55:05] but i take TrevorParscal and parutron are on the same page for the left nav? [01:55:05] she's trying to tell us something [01:55:16] haha [01:55:18] we like it [01:55:34] she will be the youngest coder ever [01:55:44] yes, she will [01:56:07] trevor i just noticed that donate + help are back in the "interaction" section, even though in an ideal world, we'd want them in the top "always visible" section. am assuming this is something we'll have to deal with per wiki as that is how it is managed. [01:56:09] is that correct? [01:56:45] yes [01:57:18] it's a matter of changing MediaWiki:Sidebar [01:57:22] on every wiki [01:57:26] great. [01:57:36] cool. with that (and without any official approval or authority over you) i insist you relax and get well! [01:57:45] k [01:57:50] thnx [01:57:54] :) [01:58:15] i will be checking in online at the time of the switch. mostly out of team love! [01:58:26] you know nimish is out sick too :( [01:58:32] we look forward to it [01:58:45] maybe we will do a group skype call... [01:58:49] we are ready! [01:59:01] sitenotice got lots of translation in one hour [01:59:02] hooray.... [01:59:15] next time we should deploy at happy hour! [01:59:50] good idea [02:00:06] but that's 3am in europe [02:00:26] ops people revolt against parutron [02:00:32] :) [02:00:52] parul was curious about the site notice [02:00:54] here it is [02:00:56] http://commons.wikimedia.org/wiki/MediaWiki_talk:Sitenotice#Interface_change [02:01:34] when is enwiki slated to switch? [02:02:47] TrevorParscal: rest up [02:03:07] k-thx-bye [02:04:15] Prodego: shooting towards end of the month [02:04:39] *Prodego nods [05:23:26] so, we have some people here... [05:23:50] we're just waiting for our netherlands peeps to wake up... [05:26:07] hey TrevorParscal [05:26:18] howdy [05:26:25] roan should be online in 5-10 min [05:29:06] it's cold in the office [05:29:12] i'm going to make a cup of tea [05:31:13] brb as well [05:32:10] hi [05:32:41] howdy [05:32:45] what time is it over there? [05:32:48] mid-day? [05:32:51] 1532 [05:33:11] so, 7:32pm for us ignorant americans [05:33:26] er... [05:33:34] 3:32pm? [05:33:42] i can haz military time lessons [05:33:49] 3:33 [05:33:49] pm [05:34:12] how's it going? [05:34:26] it's okay, I have an enormous todo list for the week [05:35:45] which will be fun [05:36:16] i'm back [05:36:20] hi werdna [05:37:46] hello nkomura [05:38:01] you poor people, doing deployments at 11pm :p [05:38:14] it's all right [05:38:30] we keep roan up beyond midnight all the time you know [05:38:32] hello RoanKattouw [05:38:37] it is our turn ;) [05:38:43] nkomura: yes, but he's youthful and would probably be up that late anyway ;) [05:38:43] speaking of RoanKattouw, here he is [05:38:54] true [05:39:06] it is so beyond my bed time [05:39:17] *yawn* [05:40:30] good morning RoanKattouw [05:41:28] RoanKattouw: do you see mark in other IRC channels? [05:42:46] RoanKattouw: sup? [05:43:19] nkomura: I know I'm not officially involved, but if something breaks and you need another pair of hands, I'm desperate for distraction from this physics :) [05:43:32] hehe [05:43:37] Don't worry werdna we'll call you in [05:43:39] werdna: thank you [05:43:48] Yeah mark seems to be around [05:44:01] But his status is away [05:44:08] We told him 8 though [05:44:29] So lemme prep the PrefSwitch deployment now while Mark's presumably still getting up [05:44:36] http://wiki.wikked.net/wiki/Wikimedia_statistics/Daily [05:44:49] looks like we're right on target for deploying off peak [05:45:02] TrevorParscal and RoanKattouw: let's scope out today's deployment [05:45:18] Yes [05:45:26] ok [05:45:27] I read something about not deploying SimpleSearch in the logs [05:45:27] so we'll update the beta and make the switch for commons [05:45:45] right [05:45:47] RoanKattouw: yeah, we're going to push that out with en [05:45:53] we have more to work on there [05:46:10] left nav is in [05:46:35] the new tool bar w/ nowiki and redirect is in [05:46:57] dialogs for IE7/8 are in [05:48:14] vector might be in - i'm thinking it's redy [05:48:17] :) [05:48:22] :D [05:48:30] *TrevorParscal gets snarky late at night [05:48:35] :D [05:48:52] *tomaszf watches from rafters [05:48:59] hey tomaszf, what's up? [05:49:34] TrevorParscal: OK so I'm just gonna update wmf-deployment to trunk state then [05:49:43] been playing with the ipad tonight .. had to put it down as all that focus on a small device was getting to me [05:49:51] tomaszf: thoughts? [05:49:51] *tomaszf decided to drop in and see how you guys were doing [05:50:26] RoanKattouw: yes [05:50:31] tomaszf: we're fine so far [05:50:42] Mostly because we didn't do anything yet [05:50:43] but let's talk after we make some changes to the cluster :) [05:50:58] The most exciting thing happening right now is me running svn merge on my machine :) [05:51:14] overall positive for the first couple of hours. the safari browsing experience is really nice. really fast and smooth. if only i could keep pandora, adium and something else in the background i'd think about getting the 2nd rev with camera [05:51:24] hehe .. that just means the fun stuff is coming up :) [05:51:31] mark is dropping in tonight right? [05:51:48] Yes [05:52:07] tomaszf: iPhone OS 4 preview is on thursday [05:52:49] nice .. i hadn't seen news on the yet .. at least official news [05:53:37] battery life on this thing is really nice so far .. its been going solid since 10AM .. 8+ hrs of use [05:53:37] whttp://www.cnet.com.au/apple-to-introduce-iphone-os-4-0-thursday-339302223.htm [05:54:31] I'll move to staff channel to let the usability folks do some work [05:54:37] :) [05:55:24] not like we're doing anything much yet [05:55:36] mark - oh mark, where are you? [05:56:31] mornings are tough for him [05:56:47] *TrevorParscal understands [05:56:56] this morning kicked my butt [05:57:53] mark is here! [05:58:01] where? [05:58:03] yay [05:58:10] in sysadmin channel [05:58:14] Quick, can anyone reproduce https://bugzilla.wikimedia.org/show_bug.cgi?id=23060 ? [05:58:15] mark is punctual! [05:58:20] Calcey filed this bug at 10:56 [06:00:31] *nkomura is reviewing the bug [06:00:40] side effect of our clever cursor save/restore stuff? [06:00:42] hmm [06:02:16] i don't have access to IE tonight [06:02:31] *werdna does if you really can't find it anywhere else [06:02:39] hi there [06:02:53] hi mark [06:02:56] mark: You've been purging 1:10 all night? [06:03:00] yes [06:03:07] and we can increase that if needed [06:03:10] good morning [06:03:16] morning :) [06:03:36] OK [06:03:36] owch [06:03:45] dude, it's pretty bad [06:03:49] the good thing about commons is that most people don't browse it, but just land on specific image pages [06:03:57] i think we will be retaining IE8 blacklisting [06:04:03] So first, I'll need to run scap to deploy some software changes [06:04:09] yes [06:04:19] TrevorParscal: IE8 usage < IE7 usage so let's do that [06:04:27] IE7 is working fine [06:04:40] TrevorParscal: Could you change that in trunk for me? [06:04:43] yeah, I think our test pages were too short to check for this [06:04:45] sure [06:05:23] what should I blacklist though, it's broken with the heading thing [06:05:30] this is worse than it was before [06:05:32] TrevorParscal: is it possible just to blacklist headings for IE8? [06:05:43] would require hacking [06:06:39] Oh right blegh [06:07:13] it actually does a scroll up/down for any toolbar stuff [06:07:32] [06:07:33] the way we are resolving the issues with the dialogs has cause issues for everything else [06:07:39] this is a bit of a regression [06:07:42] I wonder why that is [06:07:47] oh no [06:08:03] Actually, how the heck does that happen [06:08:11] I thought Adam fixed this by just moving dialog.close() calls [06:08:12] do you have IE? [06:09:15] basically, we need to blacklist IE for the whole WikiEditor until we sort this out [06:09:35] IE8 [06:09:40] IE7 is working [06:09:48] nice, WMF promotes alternate browsers ;) [06:09:51] correct [06:09:57] TrevorParscal: Think http://www.mediawiki.org/wiki/Special:Code/MediaWiki/64439 might be guilty? [06:10:04] *TrevorParscal looks [06:10:34] mark: qq [06:11:01] did you want to apply the change in thumbnail to commons as well? [06:11:13] I think shotgun debugging is probably the superior approach here because we made relatively few changes to the textSelection code [06:12:50] TrevorParscal: Why don't you try reverting a few revs locally to see if any of them is to blame? [06:13:07] i'm already doing that [06:13:08] nearly done [06:13:22] Suspicious revs IMO being the r64439/41 couple and r64400 [06:19:22] TrevorParscal: No, there's no suspicious revs below r64399 that I can see [06:19:49] Could you try to like go down to r64129 and go up from there [06:21:29] for sure [06:21:36] TrevorParscal: Ooh, sprites! [06:21:57] yeah, nice huh? [06:22:05] adam rocked that pretty hard [06:22:15] No I mean [06:22:19] What if they're guilty? [06:22:21] r64326 [06:23:19] hmm [06:23:43] TrevorParscal: Suggestion: [06:23:47] + .click( function() { return false; } ) [06:23:54] Maybe that needs e.preventDefault(); for IE? [06:24:00] yeah [06:24:05] it totally does [06:24:12] (in the sprite code, if ( 'offset' in tool ) block in wikiEditor.toolbar.js ) [06:24:30] *RoanKattouw apologizes to mark on behalf of the entire team for this mess-up [06:24:40] no problem :) [06:24:47] i fixed that up at some point though [06:24:55] I'm writing code as we speak myself ;) [06:25:40] to improve the handling of the squid purging [06:27:17] allthoguth line 322 in toolbar.js is redundant and possibly causing issues [06:27:23] the handlers get added below [06:27:36] h I see [06:28:53] TrevorParscal: I'm pretty sure that's the culprit [06:29:02] just committed a fix [06:29:05] testing some stuff [06:29:09] Because that handler fires first and due to it returning false, the other handlers don't get called [06:29:11] Did that fix it? [06:32:13] no - it's still all over the place [06:32:23] Bleh [06:32:33] mind you, I'm in bad shape to be fixing complex bugs right now [06:32:41] What happens if you go back to r64325 altogether? [06:33:02] same behavior - I went to r64324 too [06:33:11] for good measure :) [06:33:29] Oh come on [06:33:31] https://bugzilla.wikimedia.org/show_bug.cgi?id=23061 [06:33:43] Calcey's timing is horrible today [06:34:01] ha ha [06:34:09] It has to be afternoon in Sri Lanka already, surely they could've started testing earlier than 5 minutes before scheduled deployment? [06:34:17] so - we can push out the code, with IE8 blacklisted for the editing tools [06:34:27] Yes [06:34:29] then solve these issues in the next week or so, then push that out [06:34:29] *grumble* [06:34:38] we can have a hack-a-thon in berlin for this stuff [06:34:41] OK so we blacklist IE8 for wikiEditor whole [06:34:43] if it's not solved by then [06:34:47] yes [06:34:54] nkomura: where do you stand on this? [06:35:09] for IE8 users, they will get the skin and sidebar, but not the editing tools, we can patch it later [06:35:52] she fell asleep at her keyboard I think [06:36:58] i'm here [06:37:07] i was reviewing bugs [06:37:39] so IE8 users get the old toolbar in our sparkling new UI? [06:38:36] i agree that it is not time for heavy debugging right now [06:39:47] and we should take this opportunity to get the ops issue (deploying the skin) out of the way [06:40:10] yup [06:40:46] 8.9% of our users will not get the new toolbar for a week or so - I can live with that personally [06:41:54] OK so let's roll [06:42:05] I'm gonna scap the software changes now [06:42:56] RoanKattouw: is the db ready for prefswitch? [06:43:16] Not yet [06:43:27] But I'll push out the software first, then enable PrefSwitch [06:44:03] right, you have to push the software, then run update.php, then turn on prefswitch [06:44:08] so users will not see vector as default yet after you push out the software right? [06:44:12] or db errors will occur [06:44:17] k [06:44:21] Yes [06:44:27] I won't literally be running update.php [06:44:35] when do you you do the default config switch? [06:44:35] understood [06:44:36] But I'll be creating the new table manually [06:44:59] After we confirm the whole thing is working properly [06:45:00] after the software is updated, and the db table is created [06:45:05] and that [06:45:09] got it [06:45:09] he he [06:45:23] just wanted to make sure that we don't have a window that users cannot opt-out [06:45:39] *nkomura goes back to reviewing bugs [06:50:02] OK new software is live, sans PrefSwitch, please test [06:50:17] Most importantly, confirm IE8 is indeed blocked [06:50:26] k [06:50:37] bhagya is online [06:50:47] i will ask her to test IE8 is blacklisted [06:51:26] yes [06:51:31] it's blocked and IE7 is working [06:51:42] Good [06:52:31] good morning/evening [06:52:35] however, the icons aren't showing up [06:52:38] the sprited ones [06:52:44] can you make sure they are deployed? [06:53:01] http://img87.imageshack.us/img87/5370/picture1tk.png [06:54:07] i think the blacklisting is too strong ;) [06:55:15] Bleh forgot to svn ad [06:55:34] "i like my ie support like I like my coffee, black and non-existent" [06:56:25] Fixed now [06:57:14] hooray [06:58:14] pretty icons are back! [06:58:31] :) [06:58:34] coffee is good [06:58:36] *mark makes some more [06:59:18] RoanKattouw: status when convenient [06:59:29] Just created PrefSwitch table on Commons [06:59:33] Now preparing to turn it on there [07:05:23] bhagya says no toolbar is appearing in IE8 in production [07:05:35] OK the config for PrefSwitch should be set up now [07:05:38] can IE8 get the old toolbar please? [07:06:51] my testing showed the old toolbar [07:07:02] Locally or on production? [07:07:12] There might be weird JS interference and stuff [07:07:35] crap [07:07:42] yeah, production is showing othewise [07:07:55] we need to sort that before we change the config [07:07:58] hmm [07:08:39] Does this happen on commons specifically? [07:09:20] i think it's a js thing [07:09:34] Yeah that's why I asked [07:09:39] bhagya is validating using en.wp [07:09:43] If it's like enwiki local JS messing up, we don't have to worry about that just yet [07:09:48] so i suspect it is global [07:09:49] Ask here to switch to commons.wm [07:10:30] dude, there's a billion js files [07:10:50] Yeah [07:11:39] she is verifying with commons [07:11:53] happening on en [07:11:57] en-wp [07:12:03] yeah [07:12:04] so, what's the difference here... [07:13:35] dude - i'm getting pretty tired ... :( [07:13:52] bhagya confirmed no toolbar both in en.wp and commons [07:14:42] brb [07:14:52] I managed to reproduce without IE [07:15:07] By setting an early breakpoint and setting $.browser.name = 'msie'; on the console [07:15:33] you guys gracefully degrade for RTL in IE7 [07:15:45] Ugh [07:15:48] can we do similar downgrade? [07:15:50] Same old same old [07:16:04] if ( toolbar supported ) remove old toolbar [07:16:11] We need to block IE8 on the toolbar explicitly [07:16:37] sounds good to me ;) [07:17:20] Oh wait there's another way [07:18:12] i just committed something [07:18:17] please include it in your patch [07:21:21] Yay my fix works [07:21:24] Deploying both [07:21:30] nice [07:21:41] my capability of writing good code is very low right now [07:21:48] I'm glad we are sticking to simple fixes here [07:22:04] *nkomura is ready to test [07:23:58] *TrevorParscal is ready to take sleeping pills and wake up on wednesday evening for his flight to dublin [07:24:35] TrevorParscal: we are getting close to switch, you can do it! [07:24:42] :) [07:24:48] RoanKattouw: is the fix live? [07:24:57] Yes [07:25:36] yep [07:25:38] works [07:26:22] Cool [07:26:30] I am ready to briefly enable PrefSwitch on Commons for testing [07:27:39] k [07:27:46] can we stage it on test breifly? [07:27:54] briefly? [07:28:14] Sure [07:28:46] TrevorParscal: you're going wednesday? how exciting! [07:29:10] yeah, I will be in Ireland at like 5pm thursday [07:30:24] That late? [07:30:42] Oh wait, timezones [07:31:10] OK PrefSwitch is enabled on test [07:31:31] haha instant i18n fail [07:31:44] Personal tools * <prefswitch-link> [07:31:46] yeah [07:32:05] bhagya also confirmed the old toolbar in en.wp and commons using IE8 [07:35:20] are we waiting for an update for test? [07:36:21] Test is now running PrefSwitch [07:36:27] I'm working on fixing the i18n [07:36:27] looks good [07:36:31] i18n working [07:36:50] Good timing dude [07:37:00] You hit it a second after I synced the messages [07:37:20] :) [07:38:08] looks good to me too [07:38:21] *sigh* bad Trevor [07:38:21] let's roll :) [07:38:32] Oh wait [07:38:34] nm [07:38:41] what did I do? [07:38:41] I thought you'd been careless with tokens and stuff but it's OK [07:38:51] Wasn't gonna be a big deal anyway [07:38:56] Yeah so we're all set here [07:38:58] me, careless with tokens? never! [07:39:06] k [07:39:12] lets do it then [07:39:38] mark: So I'm gonna do this: [07:40:13] * Tweak the meaning of $wmgUsabilityEnforce in CommonSettings.php a little bit so it changes the default for usebetatoolbar-cgd in addition usebetatoolbar [07:40:22] * Enable $wmgUsabilityEnforce on Commons [07:40:30] * Set $wgDefaultSkin='vector'; on Commons [07:40:42] * Enable $wmgUsePrefSwitch on Commons [07:40:53] $wmgUsabilityPrefSwitch [07:41:03] * Disable $wmgUsabilityOptIn on Commons (end) [07:41:08] ok [07:41:17] and once you synced all that, I will empty the purge cache on locke [07:41:19] Sticking it all in one wmf-config rev [07:41:33] sounds good [07:42:52] Committed r629 in wmf-config [07:43:06] Am I clear to sync? [07:43:14] you are [07:43:17] punch it! [07:44:06] yeah! [07:44:14] logmsgbot> !log catrope synchronized php-1.5/wmf-config/InitialiseSettings.php 'Enable Vector, toolbar by default on Commons' [07:44:21] All done [07:44:46] "View, View source, View history" hmmm [07:44:51] we need to think about that [07:44:55] but this is great [07:45:04] Yeah the Commons folks changed Read to View apparently [07:45:05] requests going up already? [07:45:10] oh are we getting out of the peak? [07:45:11] http://wiki.wikked.net/wiki/Wikimedia_statistics/Daily [07:45:21] did we clear the cache? [07:45:31] nkomura: Yes, Europe's waking up [07:45:44] new interface for commons is up! [07:45:45] yay [07:45:46] It's now 9:45 in NL and 8:45 in the UK [07:46:39] mark: I'm done, ball's in your court ;) [07:47:07] *TrevorParscal has a laundry list of things to poke at now [07:47:21] so, should I stay up a bit longer, or just get some sleep? [07:47:40] RoanKattouw: I cleared the purge cache yes [07:47:49] so every commons url that is now requested, gets a subsequent purge [07:47:55] Awesome [07:47:59] and another one after 15 mins [07:48:03] if anyone needs me urgently, just call me, my number is on the contact list on the staff wiki [07:48:07] TrevorParscal: Like what (re: laundry list)? [07:48:10] good night trevor ;) [07:48:12] Dude get some sleep [07:48:41] the tabs collapsing is nice, but we need to figure out a way to make them already collapsed on load, rather than show them all and then take 5 seconds to collapse them down [07:48:48] anyways [07:48:48] ok [07:48:52] i'm going to bed guys [07:49:04] thank you everyone for helping make this work [07:49:13] actually [07:49:16] ? [07:49:17] the skin switching isn't so bad [07:49:19] you barely notice it ;) [07:49:22] ah [07:49:32] thought you were going to tell me I had to stay up [07:49:34] haha no [07:49:36] go to bed :) [07:49:37] well done [07:49:39] :) [07:49:40] k [07:49:41] cya [07:49:41] go away TrevorParscal [07:49:42] thanks TrevorParscal [07:49:48] take good care [07:49:58] KTHXBYE [07:50:03] Yeah I'm surprised, I'm not seeing anything on Ganglia [07:50:24] perhaps commons is too small ;( [07:50:29] are we swimming nicely mark? [07:50:32] Very much possible [07:50:34] very nicely [07:50:46] it has 6.5 million articles [07:50:51] Got any idea of the purge rate of your script [07:50:59] and gets 50% more pv than nl.wp [07:51:15] Yeah it's the second largest wiki by number of articles, but those articles are probably read less [07:52:00] 282k pv /hr isn't that small [07:52:31] vs 194 pv/hr for nl.wp [07:53:23] nice, I'm visiting random links [07:53:25] sometimes I get monobook [07:53:34] when I load again a few seconds after, it's vector [07:53:44] interesting [07:53:47] gonna try it out [07:55:25] i get 100% vector browsing random files [07:55:31] hehe [07:55:36] make sure you have no cookie set [07:55:40] or you will be hitting the apaches every time [07:55:50] ah [07:55:52] in firefox, you may need to remove all cookies for 'commons.wikimedia.org' [07:55:57] let me clear that [07:56:13] also, random files is 100% apaches [07:56:15] mark: so the thumbnail size change you wanted to apply, that is for wikipedias only right [07:56:16] ? [07:56:17] so don't do that, just click on links [07:56:23] hmm also commons I guess [07:56:32] I'll sync that change in a bit so it appears as part of the UX changes ;-) [07:56:47] k [08:00:22] RoanKattouw: 123 purges per second right now [08:03:58] :O nkomura can you reproduce https://bugzilla.wikimedia.org/show_bug.cgi?id=23052 ? [08:04:32] *nkomura is looking [08:05:26] It's the same jumping bug, but on Firefox 3.5 [08:08:35] i can reproduce it [08:08:51] so it is not too bad as the cursor position remains in tact [08:09:06] Rigth [08:09:09] but the editing screen scrolls up [08:09:26] let's keep it as high priority bug [08:17:23] thumbnail size change is live [08:17:59] i've got monobook for the first time after many tries [08:18:17] not so bad is it :) [08:18:26] no [08:18:37] I think we should simply go this route for the bigger wikis too [08:18:46] much less risk for our infrastructure, and less work too [08:18:47] now i'm getting it more often after clearing cookies [08:19:48] what do you mean by this route? [08:19:58] using purging instead of an instant switchover [08:20:22] we have been thinking of a few ways to pull it off, but it requires drastic changes to our infrastructure, and is pretty risky [08:21:15] i see [08:21:32] I put some ideas on the Usability page on wikitech [08:21:49] co-existing the old/new ui until cache is purged is not bad [08:21:53] no [08:21:56] and we can improve it somewhat [08:22:01] right now we're using a simple method [08:22:12] for next time, we could actually purge the content of the cache, instead of whatever is requested right now [08:22:16] so then it would be even better [08:22:30] What exactly do you mean? [08:22:32] and the UIs are not so drastically different that you really notice it [08:22:42] RoanKattouw: right now we just purge pages that are being visited [08:22:52] next time we could try to get a dump of the cache right before switchover [08:22:59] and then purge the cage as fast as we can [08:23:01] cache [08:23:06] Right [08:23:22] So instead of purging each page after it's visited, you'd simply do for all pages in cache: pureg [08:23:27] indeed [08:23:39] I didn't have time to write the scripts for that for today [08:23:45] but we may get to it for the big migration [08:24:36] If we do that I think we should try to sort them by popularity a bit [08:24:42] indeed [08:24:47] we can use the LRU time [08:24:50] squid knows this [08:25:16] Cool [08:27:22] well that went smooth [08:27:25] well done everyone :) [08:31:52] thank you for the brilliant purge idea mark and being stand by during the sw updates [08:32:09] RoanKattouw: thank you for the deployment as always [08:32:14] Sure [08:32:30] i have a blog announcement ready, but would like jay to have a look before publishing it [08:32:39] so it will go out tomorrow morning our time [08:32:40] I'll be busy with other things probably but I'll have Adam poke at the jumping bugs, [08:32:49] i updated the tweet tho [08:32:58] (he's probably the one that caused them in the first place, so he's probably much better qualified to fix them) [08:33:00] Cool [08:33:08] thanks everyone [08:33:09] You should go to sleep too [08:33:12] ;) [08:33:14] good night naoko :) [08:33:16] yeah [08:33:20] good night [08:33:23] Night [12:02:39] Nice work on the skin change [12:50:22] Hi, can I find documentation somwhere on how to insert button into the new toolbar ? Someone said yesterday his script didn't work. I told him the problem as on his side as it was working fine in my vector. But it appeaes I manually disabled the "new edit toolbar" and "new insert dialog" a while ago. So I was till in the old toolbarl [12:51:21] but now that Commons has switched my setting got reset to enable those two beta featured. I undid that since I still have no solution for that script. [12:51:30] I kinda presume this is a solved issue, right ? [12:52:07] http://usability.wikimedia.org/wiki/Toolbar_customization [12:52:32] Still a bit WIP [12:52:51] But anyone with some JS knowledge should be able to find their way from there [12:55:25] Hm.. [12:56:58] RoanKattouw: So in comparision to the old toolbar I'd add button to section-main/group-insert, right ? [12:57:52] Depends on where you want the button to appear [12:58:25] Well, up front next to the others, where is used to be [12:58:31] it* [12:59:12] In the upper part of the toolbar? [12:59:27] As opposed to inside the Advanced or other sections? [13:00:33] Well I dont use any of the Advanced/Special/Help sections ; I'd like by buttons next to " B I (link) (image) (sign) " [13:00:46] Yeah I think that's main/format [13:00:48] Ah [13:00:50] main/insert [13:00:55] The first section is main/format I think [13:01:26] OK. I'll see if I can make a function that will do all that that is backwards compatible with mwCustomEditButtons[mwCustomEditButtons.length] method. Gimme a few minutes [13:02:12] ie. AddButtonToMainInsertBar(id, fileurl,title,insertbefore,insertafter,sampetext){ // }} [13:02:32] Did you know about mwCustomEditButtons.push(foo); as an alternative to mwCustomEditButtons[mwCustomEditButtons.length] = foo; ? [13:02:35] Or am I reïnveting the wheel if I do that ? [13:02:54] yes I do, but I used the .length method as a copy from something else. Push is better indeed. [13:03:01] Not really, we don't currently have such a function [13:03:10] OK. You will by the end of today :) [13:03:19] And of course said function is trivial [13:04:08] I'll find out when writing the function if I find calling it is not much less then using the script directly. It's new for me, so I'll find out [13:04:23] It's probably gonna be shorter, yes [13:04:23] Hopefully I will conclude that doing it directlyt with the sample code you linked to is DRY [13:07:19] I'm pretty sure it is [13:08:45] yes, but if the function becomes too specific it's useless. And I think when I add more optoins I'll be about the same as using wikiEditor( 'addToToolbar', { [13:08:53] which itself is actually a good function and not a raw-thing [13:09:00] right ? [13:10:15] Well it's more or less raw [13:10:42] But it supports a wider range of options than made apparent in the examples [13:11:00] yeah, I'm starting to see some of it in the source code [13:11:02] You could of course put an addToToolbar call on one or two lines [13:11:22] addToToolbar() exists ? [13:11:40] No [13:11:42] ok [13:11:49] I mean the .wikiEditor( 'addToToolbar' call [13:12:34] So, you think another function will become part of the vector-core to add buttons ? Or is this good enough ? I havent' decided for myself, but if waiting a week saves me work now, I'm fine with that [13:12:51] Probably not [13:13:47] ok [13:20:53] RoanKattouw: It is correct that the buttons do no longer have a way of selecting them with CSS and/or jQuery by id or unique class ? [13:21:14] like mwCustomEditButtons[x].imageId was [13:22:51] Because some scripts of mine, and possibly others add click-functions to the buttons by Id, and add for example an automatic edit-summary aswell when the button is clicked (ie. a button to add {{category redirect|<>}} sets wpSummary.val("Category redirected") etc. [13:23:20] Krinkle: check out refToolbar 2.0 for an example [13:23:38] Krinkle: http://en.wikipedia.org/wiki/User:Mr.Z-man/refToolbar_2.0 [13:23:54] Hm [13:24:24] You're right, the buttons don't have IDs [13:24:24] thedj: eh.. can you be more specific ? [13:24:48] That's a very good feature to add, lemme file it in Bugzilla [13:25:04] RoanKattouw: I might have an idea to simplyfy it [13:25:13] example: 'tools': { [13:25:13] 'smile': { [13:25:14] label: [13:25:23] use 'smile' as part of the id [13:25:35] Yeah that's probably what we'll do [13:25:42] okay [13:26:01] since those are lowercase and unique afaik [13:26:17] Tho an override optoin might be handy, or not. I'll leave that up to you folks [13:27:46] Krinkle: if you want to change the new toolbar, then User:Mr.Z-man/refToolbar 2.0.js is a nice example. [13:27:53] examples are usually easier than documentation :D [13:28:35] I'll take a look, but the documentation helped me I got it working [13:28:54] I'm writing the function anway since I'm too lazy right now rewriting the scripts - I might at somepoint, or not. [13:28:59] anyway* [13:29:49] *thedj gets back to work [13:30:37] RoanKattouw: Something else I noticed. when periMsg is used (and thuss sample text inserted when clicked without selection) - it automatcly selects everything once inserted. [13:30:55] but it selects everything, including the open and close tags (pre, post) [13:31:00] shouldn't it just select periMsg ? [13:39:12] I think it should, yes [13:39:39] WFM with italic button [13:40:33] RoanKattouw: You're right, and it does xD [13:41:35] I had periMsg: "test", pre: "{\{test|", post: "}\}\n" [13:41:46] when I clicked it I got {{test|[test]}} [13:41:54] with [test] selected. Where did [ and ] came from ? [13:50:22] RoanKattouw: Here's a function I wrote just now, works fine on first sight: http://commons.wikimedia.org/wiki/User:Krinkle/insertVectorButtons.js [13:51:56] Krinkle: periMsg has to be a message key. For literal text use peri [13:52:09] Thx [13:52:39] Where does periMsg look for the key ? Directltly into the MediaWiki namespace or a subpage of somthing ? [13:52:45] ie MediaWIki:Test ? [13:53:12] Yes, the MediaWiki namespace [13:53:39] OK. But not MediaWiki:Toolbar-Test or anything, direct link to the namespace. [13:53:53] OK. Thx. I fixed "peri". Looks better now, ready for use in my scripts [13:53:53] No no prefix [13:54:02] k [14:15:40] RoanKattouw: Do you know which fires first ? $j(function() or addOnloadhook ? [14:15:59] I think addOnloadHook fires first [14:16:20] if you could take a short look at http://commons.wikimedia.org/wiki/User:Krinkle/vector.js under // === Extra buttons in toolbar === [14:16:31] I get kCustomMainInsertButton undefined as error Hm. [14:16:47] probably because if fired before it was defined. [14:20:35] Ok. I removed the $j(function() from the insertVectorButtons.js file - it only declares the function there no need to wait for dom ready [14:21:04] Thx for help RoanKattouw - cya later. oh, and before I go. could you link me to the bugzilla ticket so I 'll know when it's in ? [15:09:31] Krinkle: https://bugzilla.wikimedia.org/show_bug.cgi?id=23065 [15:16:23] Good morning adam_miller [15:16:32] Our Commons rollout tonight went pretty smooth [15:16:32] morning RoanKattouw [15:16:39] last night? [15:16:46] Although we did disable wikiEditor for IE8 entirely because of some bugs [15:16:55] Yeah, last night around 3 am ET [15:17:16] what were the bugs? [15:17:20] There's some weird scrolling bugs happening in IE and my suspicion is they're caused by your modifications to the textSelection plugin [15:17:24] Lemme look up the bug number [15:17:26] s [15:18:20] https://bugzilla.wikimedia.org/show_bug.cgi?id=23052 [15:18:41] This is in FF 3.5.8, the editor scrolls up when clicking the indent button [15:18:55] me? break something? while fooling with code I don't fully understand? impossible. [15:19:17] https://bugzilla.wikimedia.org/show_bug.cgi?id=23060 --> IE8 jumps on heading insert, Trevor discovered it's really all toolbar buttons [15:19:34] so i should be able those locally, right? [15:19:36] So our big testing culprit was our texts probably weren't large enough for the textarea to have a scrollbar [15:19:38] Yes [15:19:47] Won't work on the cluster because we blocked IE8 there [15:20:06] Oh and you'll have to revert the blocking rev locally of course, lemme grab the rev number for you [15:20:25] !rev 64648 [15:20:25] --elephant-- I don't know anything about "rev". [15:20:30] ... [15:20:46] !rev is http://www.mediawiki.org/wiki/Special:Code/MediaWiki/`e1 [15:20:46] --elephant-- You don't have permission to do that. [15:20:49] :O [15:21:07] OK whatever, http://www.mediawiki.org/wiki/Special:Code/MediaWiki/64648 [15:23:44] *RoanKattouw beats elephant into submission [15:23:47] !rev 64648 [15:23:47] --elephant-- http://www.mediawiki.org/wiki/Special:Code/MediaWiki/64648 [15:23:52] !bug 23060 [15:23:52] --elephant-- https://bugzilla.wikimedia.org/show_bug.cgi?id=23060 [15:24:41] adam_miller: So just to give you the list, we're talking about bugs 23052, 23060, 23061, 23062 for the scrolling issues [15:25:10] And there's bug 23064 (CSS fail in IE7) [15:25:11] RoanKattouw: remind me how I use svn up to filter out a revision? [15:25:23] svn merge -c -64648 . . [15:26:04] thanks [15:40:55] I would love for the sections and groups to have ids also [15:41:20] morning folks (or evening, depending on your time zone) [15:41:50] Good afternoon [15:45:11] how are things? [15:46:50] Well the switchover went quite well [15:46:54] As did the thumb size change [15:52:14] good [15:52:27] I was around long enoough to see that the thumb change had zero impact on load [15:52:31] which was to be expected [16:00:43] http://usability.wikimedia.org/wiki/Talk:Beta_Feedback_Survey he's rude, but the man got a point [16:01:02] <{c|busy}> jpg [16:01:08] <{c|busy}> who is using jpg? [16:01:20] <{c|busy}> >.< [16:02:20] guillom: What the heck is he talking about? [16:02:34] RoanKattouw, howie's tables [16:02:39] <{c|busy}> *coug* http://usability.wikimedia.org/wiki/File:Beta_retention_1dec09.jpg *cough* [16:02:39] Oh [16:03:05] ah [16:03:08] Yeah I thought that was ridiculous as well [16:03:36] <{c|busy}> hey, what's going on with #wikimedia-ux ? [16:03:47] I think everyone agrees that it's a good thing our statistician doesn't make usability decisions [16:03:57] That the guy probably didn't realize [16:03:59] <{c|busy}> RoanKattouw, we need to move everyone to that channel. This one is really invalid. :) [16:04:14] Ugh are we getting that again [16:04:22] I created the channel, ut I didn't do anything else until a decision was made [16:04:36] Let's at least discuss it with Naoko [16:04:48] And if we do move, this chan could redirect like #wikipedia-usability does [16:04:58] Ah, did [16:05:12] <{c|busy}> Yes, well this is the one with the wrong name. [16:05:20] Or let's just stay here and not care about the name [16:05:38] <{c|busy}> Well, no, then we can't change the topic. [16:05:46] ? [16:05:46] <{c|busy}> unless you're here. [16:05:52] Right [16:06:00] I can request that ChanServ join this channel I think [16:06:07] ye you can [16:06:10] *yes [16:06:17] <{c|busy}> it doesn't make the name less wrong :) [16:06:35] For the record, that actually was the topic some time ago [16:06:43] <{c|busy}> something which requires simplicity itself to correct. [16:20:48] {c|busy}: the joint picture experts group was in our channel? [16:21:03] <{c|busy}> TrevorParscal, lolwut? [16:21:17] who - you asked who is USING jpg [16:21:20] sorry [16:21:25] I'm still a bit out of it [16:21:31] <{c|busy}> Oh, we know who did it :) [16:23:53] ok [16:23:56] I'm heading in [16:51:30] TrevorParscal: Could you identify to services please? Then I can add you to the list of chanops [16:52:07] Same goes for adam_miller and nimish_g [16:53:30] RoanKattouw: how do you do that? [16:53:49] /msg NickServ identify username password [16:53:55] Provided you have a user/pass for NickServ [16:53:56] RoanKattouw: i'm already identified [16:53:59] I always am [16:54:22] Ha [16:54:26] Indeed you are [16:55:05] apparently he's not... I don't have a username/pass on nickserv [16:55:26] nimish_g: /msg NickServ register yourpassword you@email.com [16:55:45] Trevor and Adam turned out to be identified after all, so I added them to the chanops list [16:55:58] They can now op themselves with /msg ChanServ op #wikipedia_usability [16:56:14] hi - do we have a meeting in 5 minutes? [16:57:21] nimish_g: hi [16:58:36] ok, I registered with nickserv and identified, says I'm not authorized [16:58:40] hannes-_-: hey [16:59:01] meeting or no meeting? [16:59:21] nimish_g: Did it send you a confirmation e-mail? [16:59:37] yep, and I confirmed with it [16:59:45] hi hannes_away [16:59:48] And did you identify with /msg NickServ identify nimish_g yourpassword ? [17:00:53] yep [17:01:44] meeting [17:01:46] Hm [17:01:50] RoanKattouw: so, there was a tech working group meeting we were going to - but it's moved now [17:01:56] so, could you call in? [17:02:01] I have already called in [17:02:01] adam_miller: you as well - if possible [17:02:10] To the bridge number that is [17:02:11] you're called in right now? [17:02:14] yES [17:02:20] Do I need to call an extension instead? [17:02:25] using the bridge again today? [17:02:35] adam_miller: Do you have your VOIP "act together"? [17:02:41] i think so [17:02:45] That'd be cool [17:02:48] i have a thing setup, but i havent tested it yet [17:03:02] TrevorParscal: Can you conference us in then? [17:03:07] I'm 677, Adam what's your ext? [17:03:09] adam_miller: does that mean you have an extension? [17:03:21] i've had one [17:03:28] but i have software setup to use it now [17:03:39] nimish_g: You can now op yourself as well [17:03:50] give me two seconds, i need to clean up lunch quick [17:04:29] yes [17:04:47] adam, roan, call into the 2001 extension [17:05:34] OK [17:05:58] It hung up on me :( [17:06:29] TrevorParscal_: what's the full number for that? [17:06:35] Oh nm [17:06:40] Mic was disconnected [17:07:31] ok [17:07:38] now we need to try 2002 i guess [17:08:31] TrevorParscal: what's the full number? [17:08:43] 2002 internally [17:08:49] TrevorParscal: thats a tech-meeting only? so u dont need me? [17:08:51] (415) 839 6885 x2002 [17:09:13] sure [17:09:15] please call in [17:09:19] hannes-_-: :) [17:09:22] whoa, that's easy [17:09:33] ok [17:09:53] thanks hannes-_- we're gonna talk about some quick high level feedback from the study and i'd like you to be here [17:09:59] i'll give you the signal when you can sign off [17:10:35] can I call the regular number? [17:10:49] this RoanKattouw: (415) 839 6885 x2002 doesn work [17:13:07] adam_miller: did you get your voip stuff from rob? [17:13:12] yes [17:14:21] which number top call nimish_g_ ?? [17:14:44] Internally, 2002 [17:14:48] do you have an extension in the voip system? [17:14:51] If you have a WMF VOIP thing [17:15:15] yes [17:15:36] Then log into the WMF phone system and dial 2002 [17:15:40] Who just joined? [17:15:43] me [17:15:51] but u cant hear me can u? [17:15:58] nope. are you talking? [17:16:03] have you spoken yet? [17:16:04] no :P [17:16:13] haha...well then we don't know =P [17:16:20] yes, Is said "can you hear me?" [17:16:21] :) [17:16:29] we can't [17:18:49] you still can t hear me? [17:18:52] :( [17:19:30] HOLY CRAP [17:19:32] What's that noise [17:19:33] did someone flush their phone down the toilet [17:19:42] Whoever that is please mute or hang up [17:19:47] it's a horror film [17:19:48] the VOIP is trying to suck our souls out through our ears [17:19:55] ha ha [17:20:11] Ugh [17:20:33] Could you guys hold the meeting? [17:20:36] I can't hear a thing [17:20:50] All I hear is static and Parul's voice is in the background [17:21:21] who's phone is doing that? [17:21:28] can everyone hang up and call back in? [17:21:28] Not mine, I'm muted :D [17:21:29] doing what? [17:21:33] All that noise [17:21:40] i'm on mute [17:21:40] creating a horrible static [17:21:44] I dont hear noise [17:21:50] I can hear u talking [17:21:52] Could you hang up? [17:22:01] done [17:22:03] ahhhhhh [17:22:08] OK it was definitely you [17:22:10] so much better [17:22:14] hannes-_-: Were you playing a video game? [17:22:15] :( [17:22:18] no [17:22:25] ofcoarse not [17:22:33] I dont even have games on my machine [17:22:33] Oh that's what it sounded like... [17:22:42] I could hear that [17:22:45] could not [17:22:58] I ll try to call back in [17:23:06] if it happens again say something [17:23:25] it happened again [17:23:37] everyone on mute now? [17:23:38] sorry [17:23:44] what voip software are you using hannes-_- ? [17:23:51] Express talk [17:23:54] is the same as roan? [17:23:58] no [17:24:01] he is on ubuntu [17:24:10] ohhh of course [17:24:11] I use Twinkle [17:24:12] I cannot use his software [17:24:25] twinkle doesnt work for windows [17:26:08] ok, so I ll not try to call back in [17:54:25] <{c|busy}> Thus far, the Commons community hasn't resulted [17:55:07] There were some comments on the take me back survey [17:55:24] Some people couldn't find the watch button [17:59:39] hannes-_-: we're gonna talk about scheduling/ops/release stuff [17:59:56] so feel free to check out [18:00:09] get back to your other things (i.e. jules!) [18:00:42] oh wait [18:00:46] quickly discussing logo. [18:01:48] ok done ;) [18:22:07] nkomura: I added you to the access list so you can now make yourself a chanop with /msg NickServ op #wikipedia_usability [18:22:18] Trevor, Nimish, Adam and myself already have this ability [18:22:38] except guillom and myself are the ones with the technical skills. [18:22:50] we'll have to feed them commands. [18:22:56] heh [18:23:00] bah [18:23:03] I'll just give you access too [18:23:04] bah indeed. [18:23:13] the wikipedia usability initative is coming to an end anyway ;à) [18:23:14] ;) [18:23:14] don't bother [18:23:21] guillom is also a usability guy and giving cary access seems defensible :) [18:23:21] we don't care. [18:23:43] RoanKattouw, answered your e-mail about the Gallery tab [18:24:02] *guillom goes grab lunch [18:39:02] TrevorParscal: Your Google Doc seems to be missing rows [18:40:10] maybe [18:40:17] feel free to re-import [18:40:20] It's got 25 rows, the CSV has 33 lines [18:40:30] the csv wasn't properly escaped too [18:40:38] many of the comments required merging [18:40:57] Oh [18:41:02] It was just regexed up [18:41:09] understood [18:41:10] Oh of course [18:41:15] it's just to give the gits [18:41:16] The comments contained commas, dug [18:41:18] *gist [18:41:18] *duh [18:41:36] the comments are in multi-lingual [18:41:39] most of the people commenting seem irrational - but there are some reasonable people in there [18:42:09] 25 or 33 entries for the past twelve hours seem low [18:42:48] I filtered entries not containing comments [18:43:05] Let me count how many people have actually switched to Monobook [18:47:02] \ [18:47:18] \msg NickServ op #wikipedia-usability [18:47:28] I'm obviously doing this wrong [18:48:09] nimish_g: the comments from Commons are coming in multiple languages [18:48:38] it will be great if your translation integration can detect the language of comments [18:50:01] nimish_g: Forward slash [18:50:17] nkomura: We can translate quite a few ourselves though [18:52:02] nkomura: 267 people currently have skin=monobook set on Commons [18:54:05] RoanKattouw: did we set people who had "Default" skin to be vector? [18:54:11] (on commons) [18:54:32] Yes [18:55:16] do we know how many unique users we have for Commons? [18:55:34] 3. The rest are sockpuppets. [18:55:45] lol [18:56:01] 1096745 user accounts [18:56:32] including SUL? [18:56:38] nimish_g, http://usability.wikimedia.org/wiki/Multimedia:Initial_survey [18:56:52] Yes [18:57:12] Most of those are probably SUL accounts, they get created the second you visit an image description page on Commons [18:57:18] Most Wikipedians have done that some time [18:58:19] *nkomura goes to look active Commons users [18:58:35] these are the 3 Commons users Cary is talking about: http://commons.wikimedia.org/wiki/File:Wikimania_2007_Commons_puzzle_piece.jpg [18:58:43] :) [18:58:52] :) [19:00:28] questions to cary and guillom, did you opt out? [19:00:30] ;) [19:00:53] that's a very nice photo [19:00:55] opt out? [19:01:04] I have had Beta on for a while. [19:01:13] I opted in when Beta was first released. I opted out a few times during the past few days to check if things were working as well in Monobook & Vector [19:01:23] I have not opted out. [19:01:50] how's the experience now that Vector is the default interface? [19:01:57] I have opted in and out repeatedly on commons but only to get to the pages of text for translations (it's currently on)... I did not leave feedback, so as not to clutter up anything [19:02:30] hmm no mostly on prototype, I guess, so maybe it wouldn't have been picked up [19:03:22] commons have 2500 active users and 800 very active users according to ErikZ's stats [19:03:46] I wonder which I am [19:05:19] do you contribute more than 25 times or more to Commons in a week? [19:05:41] active users 5 times or more in a week [19:06:11] the former is "Very active" authors according to the definition of the stats [19:13:00] hmm [19:13:07] I think I would presently be "active" [19:16:22] hannes needs to let up on the small "A" business... [19:16:36] it's getting annoying. [19:51:59] nkomura: thanks to our multilingual team, we have most of the prefswitch comments translated [19:52:08] =) [19:52:31] really? [19:52:34] russian too? [19:52:40] That was Google [19:52:48] ya, I put those into google [19:53:01] But I translated German and French (would like them checked, esp. French), Tom presumably did Polish and Nimish took a stab at Spanish [19:53:04] but we could ask anya...admittedly though most of the comments aren't terribly useful [19:53:17] RoanKattouw: your german seemed right [19:53:19] "new opportunities" probably better translates to "new features" [19:53:32] line 24 [19:53:41] but I don't know [19:53:47] maybe anya can tell us [19:53:54] it looks cyrillic [19:54:18] It's definitely Cyrillic [19:54:27] Which is why I marked it as "ru?" [19:54:31] right [19:54:43] ya it's def russian [19:54:44] mostly, these people are just whining [19:55:08] The comment about the $1 regex thing: I thought that worked [19:55:28] Provided you parenthesize or use $0 for the entire match (not sure the latter is supported) [20:18:56] My computer is too slow for the Vector skin. [20:19:07] it's not the first time I hear that [20:21:07] that's not good. [20:25:21] IE users on 6 year old crap, they are out there. [20:26:10] héhé [20:26:13] well [20:26:27] the performance improves significantly after the second time tho [20:26:34] I have an old laptop with firefox, and vector is slow on it too [20:27:37] but then again, everything is slow on my old laptop :) [20:27:39] Vector or the toolbar? [20:27:44] I'd expect the latter to be the culprit [20:27:55] don't remember, really, I don't use it much any more [20:27:56] I have to look into jQuery 1.4 migration again so we can speed stuff up [20:28:00] (the laptop, not vector) [20:35:19] RoanKattouw: how's it going? [20:35:32] jquery 1.4 migration... sounds fun [20:35:35] Yeah [20:35:44] The bugs our plugins are causing with 1.4 are less fun [20:35:53] I'll have to find time to sort those out [20:36:29] More generally, I've been busy with school lately and only been paying the utmost necessary attention to usability [20:38:28] 1.4.2 has about 3x performance increase over 1.3.2 [20:38:34] it's well worth the pain [20:40:01] Yes [20:40:13] Especially for improving toolbar performance, where DOM manip is pretty much the bottleneck [20:46:21] HEY TrevorParscal and RoanKattouw [20:46:31] howdy! [20:46:40] did you get my email about SimpleSearch [20:46:47] there are two .focus() calls i'd like to remove from the textSelection plugin to fix the IE8/7 jumping shit [20:47:19] awesomeness [20:47:23] can you think of any reason we'd need them there? line 23 and 90 [20:47:52] Looking [20:48:16] adam_miller: Keep in mind document.selection doesn't do what you expect when the textarea isn't focuesd [20:48:37] Instead of manipulating/querying the textarea it'll grab info about whatever else is focused and contains text, e.g. the document [20:50:17] well focusing on it is causing the scroll to jump [20:50:49] we could write another function that stores the current scroll position, focuses and then resets the scroll position if we need to keep those focus() calls in there [20:52:23] Well on insert you want to scroll to the cursor position anyway [20:53:13] scroll the textarea, but not the main document [20:54:08] Right [21:09:51] I've added a click event to one of the self added toolbar buttons ($j('#wpTextbox1').wikiEditor('addToToolbar', etc.) - and add an event using: $j("#wikiEditor-ui-toolbar img[rel=mybuttonname]").live('click', function(){ [21:10:09] but it doesn't get fired. I presume Vector returns false after it has done it's code insertion ? [21:10:49] Yes [21:10:50] is that true ? and if so why ? If for a reason that is still present, is there a way around it ? [21:10:57] Because of [21:10:57] :) [21:11:10] Oh, that makes sense [21:11:15] Hm.. [21:11:38] Why a ? [21:12:33] with css span[a]:hover { cursor: pointer} works aswell, and solves having to return true, and making it hard for scripts to add events to it ;0 [21:13:41] or if the attributes should validate, ; with css span.button{} [21:13:48] spans and divs have problems with focus loss on IE [21:14:30] OK. I didn't knew that. - Do you know another way have a click handler on it ? [21:15:54] or maybe override the return false, add the click() and then return false in the local script. [21:17:44] I'm not totally sure we need return false now that we have e.preventDefault() though [21:17:49] So we might just be able to ditch it [21:18:47] That'd be nice [21:23:05] Krinkle: why not just use the toolbar API? [21:23:16] for the action [21:23:30] He wants to tack onto the action for existing buttons (right?) [21:23:41] not quite [21:23:48] TrevorParscal: But does the toolbar API allow arbitrary actions? [21:23:48] he said self added [21:23:53] yes [21:24:00] to buttons I add with the script RoanKattouw told be about earlier today [21:24:33] but if $j('#wpTextbox1').wikiEditor('addToToolbar', also has a callback option within section.group.tools [21:24:39] ..then it's solved. [21:25:02] there are different action types, replace, encapsulate, callback and dialog [21:25:20] I use encapsulate button, since that's the primary functoin (to insert code in the textarea) [21:25:31] but I also like to add a callback to it to fill in an wpSummary [21:25:51] hmm [21:25:54] interesting idea [21:26:07] we could add an extra callback parameter [21:26:17] to be executed along with the action no matter what the type [21:26:22] right [21:26:36] but, to be honest, the encapsulate selection thing is so simple [21:26:43] you should just use the callback action [21:27:27] Any docs about actions other then encapsulate ? [21:27:32] I only got this: http://usability.wikimedia.org/wiki/Toolbar_customization [21:27:41] $( '#wpTextbox1' ).textSelection( 'encapsulateSelection', { ... } ) [21:28:04] Krinkle: we are supposed to spend April documenting, but now it looks more like may [21:28:17] No problem. I can do much with very little. [21:28:23] but I'm happy to help you in the mean time [21:28:34] or even after that point for that matter [21:28:45] TrevorParscal: In that case, it'd be great if you could take a look a the two scrips in question [21:28:48] only a few lines. [21:29:07] http://commons.wikimedia.org/wiki/User:Krinkle/insertVectorButtons2.js <= script to simplify adding buttons (dont repeat yourself; DRY) [21:29:08] sure [21:29:19] http://commons.wikimedia.org/wiki/User:Krinkle/vector.js <= scroll down, here I add the butotns [21:29:20] buttons* [21:29:33] i see it [21:29:43] so, rather than action type encapsulate [21:29:51] use action type 'callback' [21:30:13] does the rest work the same way with action type callback ? (ie. label, optoins, pre, post etc.) [21:30:22] then use that { pre, peri, post } object as the { ... } parameter in $( '#wpTextbox1' ).textSelection( 'encapsulateSelection', { ... } ) [21:30:30] inside the callback function [21:30:51] the function goes in a 'execute' parameter [21:30:57] Hm... could you give an example of an existing callback-button ? (or write a fake one) [21:31:01] yes [21:33:31] http://pastebin.com/edDYm7kB [21:33:57] Oh, that looks nice [21:34:14] I'll see what I can do [21:35:13] :) enjoy [21:37:13] RoanKattouw: after playing around a bit, i found some cases where removing those focus() calls causes the text to be instered in the top of the document instead of the textarea [21:38:16] i tried storing the scroll position and resetting it after a focus() call, but that just makes the jump even more annoying because it jumps twice [21:38:33] *TrevorParscal_ hates IE8 [21:39:07] why didn't you guys disable IE7? it looks like it's behaving the same way [21:39:23] um - it was working for me last night [21:39:36] i was using IE8 in IE7 mode [21:39:39] what are you using? [21:39:51] same deal [21:41:51] TrevorParscal: i did get your simplesearch email [21:41:55] i might just move on to that [21:42:25] adam_miller: it will be less stressful i think [21:52:09] TrevorParscal: Alright, it works :) [21:52:21] http://commons.wikimedia.org/wiki/User:Krinkle/insertVectorButtons3.js and http://commons.wikimedia.org/wiki/User:Krinkle/vector.js (// Welcome) [21:53:20] Krinkle: cool [21:53:48] I'll suspicious, but maybe without the function(){ } around it. [21:57:57] ok. it needs it - np. [21:58:38] OK. I officially have everything switched to vector and works too - with no compromises. [21:58:57] Especially the presence of jQuery is a blessing TrevorParscal [22:00:35] :) [22:01:00] Krinkle: thanks for working to get your stuff to work with vector! [22:01:25] Yeah, likewise [22:52:59] RoanRoanRoan [22:53:15] Anyone in here knowledgeable about user skin subpages? [22:53:31] I heard a rumor that User:Example/common.css will be implemented soon. True? [22:56:47] THIS CHANNEL IS SO USEFUL. [22:56:51] *Marybelle goes to browse SVN. [23:14:45] Marybelle: correct [23:15:11] Marybelle: mediawiki 1.16 is being prepared atm. common.js will be in 1.17 [23:17:17] Ah, okay. [23:17:48] thedj: I was going to note it here, but I have no idea when the site will be updated: http://meta.wikimedia.org/wiki/Vector#How_do_I_make_the_links_at_the_top_of_the_page_lowercase.3F [23:17:54] So I felt it safest to just mention /vector.css. [23:18:07] You also wouldn't really want to fuck with the links in other skins, I suppose. [23:19:28] Marybelle: all skins that have lowercase force so with CSS, so yes, that is the appropriate method. [23:27:22] is there a reason vector has such poor contrast? [23:30:03] I'm asking because I've finally looked at the skin on some other monitors and am seeing details I was not able to pick out before [23:32:26] the light gray background always seemed looks like a white, and the gradients are non-existant [23:53:32] Romaine: Boe ! [23:53:34] :D [23:59:01] :p [23:59:32] is there a scheme of when which project will get vector as new skin? (planning) [23:59:59] yes.