[00:21:55] Reedy: Three things open that I can see, in order of importance: [00:23:17] 1. adding the actual "which challenge I'm on" to the "I've submitted my challenge and am now being returned to this page" page. [00:23:44] i.e. chosen Challenge Title and Challenge text. [00:24:01] 2. Adding wiki links to the Challenge text field, so we can link to more details about each challenge [00:25:37] Those are the two big ones. And then some other stuff that's just annoyance (like replacing "signupstart" with actual copy.) [17:06:13] You are currently on the Challenge 1 challenge [17:06:18] lol [17:06:26] BAD cut and paste. [17:07:31] Reedy: ref ^^^ that. That's the "challenge name" field, and it now shows up on the post-accepted challenge page. Can we also get the "challenge description" on that page as well? Because that's how we want to link to further details about the challenge. [17:13:46] gregdek, how do you want the block of text/the addition of the description formatting? [17:14:03] Next line "$1 challenge description: $2" or something? [17:14:10] $1 being the challenge name, $2 being the description [17:15:55] Hm. [17:16:11] Then do you want the short description, or the challenge text? [17:16:20] The challenge text, definitely. [17:16:49] '''Current challenge: $1''' -- $2 [17:16:58] Let's try that. [17:20:26] An additional message, rather than altering the other one I added, rihgt? [17:21:36] Yep. [17:52:01] anybody familiar with this code challenge thing? [17:52:06] seems i'm being roped into a meeting about it [17:52:44] brion: yep, I can tell you all about it. [17:52:57] https://www.mediawiki.org/wiki/Weekend_of_Code <- 'messaging draft area' says it was october 15 [17:53:03] i assume that's not accurate :) [17:53:11] brion: heh, yes, outdated. :) [17:53:34] The updated timeframe will run between whenever we can launch it (my hope; Thursday) and November 8th -ish. [17:53:50] There's an instance of it running on test.wikipedia.org now. [17:54:09] JeroenDeDauw wrote most of it, Reedy is also working on cleaning it up for launch. [17:54:18] If you go to: [17:54:35] i'd probably recommend doing a code challenge without special software, so we have a better idea what's required. but i assume y'all have talked about that previously [17:54:56] Yeah, we're trying to keep the requirements as light as possible. [17:54:57] http://test.wikipedia.org/wiki/Special:ContestWelcome/October_2011_Coding_Challenge [17:54:58] brion, too late? ;) [17:55:02] LOL :) [17:55:07] gregdek, updates are out on test now [17:55:14] hey, first i've heard of any of this beyond vague mentions [17:55:19] Erik's chief concern was having a good flow that collects user data and possible CVs. [17:55:37] brion: my fault, I think, for not communicating enough and transparently enough. [17:55:38] creepy :) [17:57:02] Reedy: thanks, checking it out now. [17:57:35] Reedy: brion: I can has sysop on test, so I can access the stuff for contest and future extensions myself? [17:58:40] Reedy: closer. The only thing now is figuring out how to make the link in the pop-up for the challenge to actually go somewhere, which I suspect is css weirdness. [17:59:04] gregdek, create the target page? [17:59:28] Oh, will that do it? One sec. [17:59:33] yeah [17:59:39] redlink means none existent ;) [17:59:47] JeroenDeDauw, have you ever logged in on test? I don't seen an account [18:00:16] Reedy: https://test.wikipedia.org/wiki/User:Jeroen_De_Dauw [18:00:22] oh, spaces [18:00:36] I'm getting to the point where I need glasses to read captchas. Sigh. [18:00:39] you've already got sysop [18:00:47] Huh [18:00:54] roan did it 1st sept [18:01:07] wtf [18:01:14] I got a permission error a minute ago [18:01:19] But now it works [18:01:31] Oh well [18:01:32] i put you in the contest groups [18:02:26] Reedy: page now exists, but link still doesn't go to a new page or create a new tab. I'm on FF 7.0.1. Will check on Chrome. [18:02:27] Reedy: right - forgot that these rights are not automatically granted to sysops [18:02:33] gregdek, https://www.mediawiki.org/wiki/Weekend_of_Code#Participant_flow_example doesn't show any steps between picking the challenge and completing it [18:02:50] is the intention for challenges to be 100% stand-alone projects with no peer interaction? [18:03:10] or is there an implied 'try stuff out, ask for help, get mentoring' stage [18:03:30] brion: the intention is to provide some resources to help people get up to speed a bit. [18:03:32] Reedy: in that case, can you make me bureaucrat? [18:03:49] So figuring out which of those resources will be best, per challenge, will be part of today's meeting. [18:04:12] *nod* [18:04:23] (In fact, we're finalizing which challenges we're picking today.) [18:04:59] If people want to collaborate, that's fine, but because it's a contest, we must stipulate rules -- and rules basically say "one winner". [18:07:26] hm [18:07:37] in open source, we're all winners ;) [18:08:37] *JeroenDeDauw throws rocks at svn conflict [18:13:41] Reedy: same behavior on Chrome. I can show you if you like. [18:13:57] I can show you it working fine for me... [18:14:05] Reedy: err - looks like I can still not make myself upload wizard campaign editor - can you not edit your own rights as bureaucrat?? [18:15:13] Well, whatever, don't need it when bureaucrat anyway [18:15:13] yeah you can [18:15:18] i granted you all the other rights [18:16:25] Reedy: I do not have the "Upload Wizard campaign editor" right, and it's under "Groups you cannot change". Is this something wrong in Upload Wizard then? [18:16:34] Oh [18:16:39] I didn't realise you were after Uw rights [18:16:55] But yes [18:16:57] That's a bug [18:17:00] the group name is far too long [18:17:14] Upload Wizard campaign editor = 29 chars [18:17:29] ug_group varbinary(16) NOT NULL default '' [18:19:18] LOL [18:19:42] Reedy: ok, fun way to find a bug [18:19:51] Had the same issue with contest yesterday [18:19:56] I can't believe no one complained about that [18:20:02] and translate not so long ago [18:20:10] If the right was added to a group it'd be fine [18:20:11] Yeah, I didn not know about the 16 char restriction [18:20:53] heh [18:21:00] low-level group names are kinda sorta meant to be keys [18:21:05] hence they're localizable :) [18:21:11] and those names can be long :DD [18:21:40] Reedy: can you fix this for Upload Wizard? Then I know how to do it correctly later on [18:21:47] Then why have the 16 char limit? [18:21:48] bah i'm gonna spend all day upgrading machines. good thing i brought my home laptop which is alreadyt updated [18:22:22] We should possibly increase the length [18:22:41] JeroenDeDauw, need to find something <= 16 chars [18:22:54] "UW campaign editors" is still 20 [18:23:11] Increasing the length sounds better [18:23:19] Any idea why we have this restriction ATM? [18:23:26] It's bugs waiting to happen [18:24:17] It's "easy" enough to fix the schema [18:24:21] but doesn't help us in the short term [18:24:52] UW camp editors [18:24:55] seems a little meap [18:24:58] *mean [18:45:19] gregdek, http://www.mediawiki.org/wiki/Special:Code/MediaWiki/100252 [18:46:16] not live yet [18:47:00] Oh, ok. Yeah, that looks like the problem, doesn't it? [18:48:40] i've tested it locally and it seems to fix [18:48:46] so will merge it out in a few [19:20:26] gregdek, hi. Friendly reminder: please let me know if/when you need communications support for the Weekend of Code (e.g. reviewing a blog post, sending tweets, etc.), and if possible not the day before you need it :) [19:22:51] guillom: my apologies -- I will loop you in asap. Long meeting this afternoon to nail down many details, and much of the fallout I can run by you. [19:23:11] ok [20:47:53] Reedy: when is contect planned to be deployed on mw.org? [20:48:01] *contest [20:48:01] now ish [20:48:06] lol [20:48:16] will it be the rev that was on test or trunk? [20:49:16] Reedy: poke [20:50:39] Need to check with Erik [20:59:45] Reedy: '''Current challenge: $1''' -- $2 [20:59:52] Not sure I agree with that message [20:59:58] The user cannot change it [21:00:03] It was gregdeks suggestion [21:00:03] So 'current' is odd [21:00:14] I don't think so [21:00:14] gregdek: ? [21:00:16] Current makes sense [21:00:40] "current" implies the possibility of change, which is not there [21:02:35] JeroenDeDauw, Reedy: We're going to be rewriting that whole block of text, it looks like. [21:02:46] Usefu [21:02:47] l [21:03:01] JeroenDeDauw, Reedy: will get you copy as soon as we have it. [21:04:59] Hallo. Is anybody familiar with something like Etherpad, but for source code? We are looking for something like it for the Localization team. [21:06:04] Nope [21:06:09] use etherpad? ;) [21:20:43] aharoni: neilk is the guy you need to talk with for etherpad source code deep dives [21:22:24] Reedy, Etherpad is nice for documents, but not amazing for source code. Usable, but not perfect. [21:30:36] Reedy, JeroenDeDauw: 2 quick tweaks for the MyContests page, and maybe 1 painful one. [21:30:57] Easy tweak #1: change "I am interested in volunteer opportunities" to "I am interested in receiving email about volunteer opportunities". [21:31:38] thats just a source message update [21:31:43] Easy tweak #2: change "I am interested in working for the Wikimedia Foundation" to "I am interested in being contacted about working for the Wikimedia Foundation." [21:31:50] same [21:31:56] ok. [21:32:39] And actually -- I'm not sure that we need the other change. Lemme test something and get back to you. [21:32:46] Reedy: you doing that or me? [21:33:25] Reedy: is this on production, btw? [21:33:36] And are we making changes in production or on test? [21:34:12] Just change the source code and then push it out [21:34:16] it'll be changed everywhere [21:34:47] OK, great. And is it testable on prod at this point? [21:35:33] yes, other than you not having the user groups granted [21:35:34] but i can fix that [21:35:58] That would be great. :) [21:36:21] Since at this point, I think we want to just make data changes in prod. [21:56:52] JeroenDeDauw, Reedy: one last big piece. Right now, we are not allowing users to change once they've selected. Can we allow people to change their contest radio button at any time? [21:57:04] Is this a small change or a big change? [21:58:11] Seemingly the functionality is there to change nearly everything else [21:58:17] Not sure why it wasn't added before... [21:58:30] Good Q. [21:58:38] So let's change that if we can. ;) [21:58:46] And if there's some reason we can't, lemme know asap. [22:03:52] gregdek: their contest radio button? [22:04:00] gregdek: do you mean their challenge? [22:05:40] JeroenDeDauw: Yes. [22:05:43] The challenge they've selected. [22:06:00] It still needs to be a radio button, i.e. one challenge only -- [22:06:01] gregdek: you want them to be able to change this?! [22:06:29] I originally had that on this page, but then removed it after someone told me we did not want that IIRC [22:06:39] The concern is that if a challenger gets deep into the muck with a challenge, i.e. "oh, we didn't understand what we were getting into", that we want them to change back. [22:06:56] Right [22:07:00] JeroenDeDauw: apologies for the change. Especially if I was the one who told you to make it that way in the first place... :/ [22:07:12] The radio list just showed the challenge names though [22:07:17] Is it difficult to change back? I sincerely hope the answer is no. :) [22:07:30] That is extremely easy to add back in [22:07:40] But if you want a more fancy GUI, it's harder [22:07:43] That should be sufficient, with the additional text of the "currently selected challenge" as well. [22:07:52] No, no more fancy GUI. [22:08:06] Just radio buttons, and the add'l text for "currently selected challenge" that is already present. [22:08:21] Well, then users will just see the challenge names, without any way to get to their descriptions [22:10:29] gregdek: ^ [22:46:41] JeroenDeDauw: that should be fine. There will be references to the general descriptions elsewhere too. [23:03:32] gregdek: done [23:04:54] gregdek: where you able to check out the extension on test wiki yet? [23:07:12] Looking, one sec. [23:26:20] JeroenDeDauw: we're applying your patch now. [23:27:37] gregdek: ok [23:44:10] gregdek: still looking for challenge ideas btw? [23:45:04] JeroenDeDauw: I think we're done. :) [23:45:12] ok, cool [23:45:21] What's your idea, though? We really should be seeding for the next challenge.