[04:27:36] okay weird, I just got a notification that a student claimed one of my tasks. yay :D [04:30:56] [[Tech]]; Username Violation; /* Those browsers (Mozilla, Google Chrome, and Internet Explorer) issuing message "Can not load page" when I trying to open Wikipedia */; https://meta.wikimedia.org/w/index.php?diff=15038866&oldid=15034268&rcid=7111968 [07:27:03] legoktm: oh nice, either the software reads your mind or other people had the same request and it was implemented quite quickly :) (I didn't see it on the mailing list yesterday though) [07:46:43] Funny, FOSSASIA "Find a bug in open-event-webapp" is a beginner task. Apparently they think there are many bugs. :) [07:48:26] Am I supposed to publish my own tasks? (How do I do that?) I just created https://codein.withgoogle.com/dashboard/tasks/5200329926770688/preview/ [07:51:10] Nemo_bis: ^? [07:51:52] legoktm: as far as I get it, an admin has to approve them (but I should really try to find out and document this) [07:51:57] legoktm, I've published it now. Thanks! [07:52:57] ok, thanks :) in the future should I ping you or does the website notify you about new tasks? [07:53:08] Yes, so it was last year too. [07:53:38] legoktm: it's ok to ping, or maybe just add a note [READY] to the task title so that I know it's not a draft? [07:54:25] ok, I can do that [07:54:49] that might be a good idea in general [07:59:07] It seems Confluence is not good for spam https://issues.openmrs.org/browse/GCI-71 [08:00:00] I doubt this is a beginner task, it's too hard even for me (and the mentor himself :p) https://codein.withgoogle.com/tasks/5186866982682624/ [08:00:53] Hmm LatexToMediaWiki https://codein.withgoogle.com/tasks/5204874035724288/ [08:01:52] I think we already cover all of this http://blogs.fsfe.org/myriam/2011/10/20/when-is-a-bug-report-useful/ [08:03:53] This also too hard imho https://codein.withgoogle.com/tasks/6276926998052864/ in my school and university billboards spaces is so precious that even finding one spot is a via crucis [08:09:20] Could asciinema be used to record a mediawiki-vagrant installation, or is it limited to one shell? https://codein.withgoogle.com/tasks/5893121204289536/ [08:09:53] Impressive how nicely the GCI website works on mobile. Melange was a horror story. [08:10:59] Nemo_bis: it probably could be. as long as its not realtime waiting for core to clone :P [08:11:56] Maybe we can speed up the recording for the time it's getting cloned. [08:13:17] Niharika: but the website is much slower for me than melange, I keep waiting [08:13:32] legoktm: good point... I think it's best to ask a (meaningful) screenshot [08:19:48] https://www.mediawiki.org/wiki/Talk:Google_Code-in_2015#Ideas_for_beginner_tasks [08:27:30] Oh, a task for adding links to doc.wikimedia.org counterparts to the the Manual pages on Mediawiki would be good. And possibly updating the list of functions and variables for it. [08:28:16] I'll file one. [08:43:56] Nemo_bis: Do I need to have a phabricator ticket for a task I create on the GCI website? [08:47:00] Niharika: not mandatory [08:47:36] But then you should at least have a project namespace page or something to track the thing [08:47:46] Otherwise users will have no idea what is going on [08:49:40] Nemo_bis: I'll create the ticket. Is there an existing one for updating the Manual pages for core classes? [08:49:51] I wonder if it should be split up. [08:53:37] Niharika: you'll need to make a list where the action is needed and allow participants to strike the items they did [08:54:00] https://www.mediawiki.org/wiki/Template:MW_file could be made smarter, class1 should probably be implied by the class name [08:54:33] Alternatively, you could add a tracking category for the template calls which don't specify any classN parameter. Or do you also want new pages to be created? [08:57:14] I don't see the need for new pages because doc.wikimedia.org provides the same information. But I would like to improve the existing ones at least. [09:04:39] Why did the section links after section editing recently break? [09:05:02] Once upon a time, after editing https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/Reports/2015-November&action=edit§ion=7 , I would be redirected to https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Reports/2015-November#Usage_data_2 (with _2) [09:05:26] Niharika: then a category will probably suffice [11:21:35] "LDAP Exception: Unable to start TLS connection when connecting to LDAP." on https://phabricator.wikimedia.org/auth/login/ldap:self/ , expected? [11:35:05] Nemo_bis: uhm, no. LDAP was changed IIRC so this is worth a task with steps to repro [11:40:11] andre__: prtksxna wants to sign up for GCI as a mentor. [11:43:13] andre__ Niharika: Commented on the tasks and appended to https://www.mediawiki.org/wiki/Google_Code-in_2015#Contacting_Wikimedia_mentors [11:46:27] prtksxna: yay, awesome! Could you drop your preferred email address in a private /msg so I can send you a registration invitation email? [11:46:55] andre__: Done. Thanks! [11:48:27] prtksxna: Invitation email sent. Thank you! And please let us know how we can help / if something is unclear! [11:52:31] andre__: Registering now [11:57:14] Hah another old friend at https://codein.withgoogle.com/dashboard/task-instances/6243809545420800 [11:58:07] Yes, nice nice [17:08:11] qchris: any chance you could take a speedy look at https://www.mediawiki.org/wiki/Git/New_repositories/Requests ? :) [17:09:31] Gimme 30mins. [17:09:44] epic! [17:37:20] addshore: The description mentions the 'analytics/limn/wikidata/data' repo. But that does not exist. However, 'analytics/limn-wikidata-data' exists (difference is the trailing two slashes, which are dashes here) [17:37:22] Does that mean that (to match naming) instead of the requested 'analytics/limn/wikidata/data/vendor' you actually want 'analytics/limn-wikidata-data/vendor' ? [17:40:03] ann qchris there is a / where there should be a - [17:40:23] infact, a few! analytics/limn-wikidata-data [17:40:34] Exactly. [17:40:39] That's why I am asking :-) [17:40:51] So you want 'analytics/limn-wikidata-data/vendor' right? [17:40:56] fixed the request! [17:40:57] yes! [17:41:20] That's because I actually copied the name from github where all /s are -s ;) [17:41:30] :-) [17:41:34] Done [17:41:48] Amazing, many thanks! [17:41:50] yw. [17:42:44] Since you mention github ... note that it might take a bit until the repo replicates to github. [17:54:45] Thats fine :) I dont actually use github really, it's just nicer to look at sometimes ;0 [18:51:31] I wonder if we should tell GCI students to get an (unaffiliated) cloak... is this still the process? https://chebe.dreamwidth.org/71388.html [18:51:46] I saw so many such cloaks that I thought there was some form by now [19:32:33] Nemo_bis: what essential benefit does having a cloak confer? [19:35:10] your IP is masked [19:35:50] Nemo_bis: according to https://freenode.net/faq.shtml#cloaks yes [19:36:30] "Lastly, note that a cloak does not guarantee that your IP address remains hidden. " [19:36:35] That FAQ item is a bit vague, surely on purpose [19:37:05] ori: yes but still better than plastering all over the channels every time you join or leave [19:37:35] there is a form for cloaks [19:37:49] sure, but that has to be weighed against the cost, which in this case is an additional hurdle for contributors [19:37:53] for unaffiliated cloaks? [19:38:06] ori: hence I was asking whether it still is a manual process :) [19:38:08] unaffiliated cloaks can be requested on #freenode [19:38:10] iirc [19:38:23] https://meta.wikimedia.org/wiki/IRC/Cloaks#Purposes_of_a_cloak [19:39:01] ori: *New* contributors at that. [19:45:17] yeah, I wouldn't recommend we recommend it for GCI [21:40:31] robla: https://phabricator.wikimedia.org/T119162#1861071 [21:41:59] RoanKattouw_away: ^ [21:58:51] coming up in a minute or so: https://phabricator.wikimedia.org/E107 [23:13:16] qgil: we're planning on making next week's RFC meeting our agenda bashing session: https://phabricator.wikimedia.org/E121 [23:14:06] central task on the agenda will be https://phabricator.wikimedia.org/T116024 , which I've edited to point to a couple of the other important Phab tasks [23:42:26] hi robla , sorry, I have been jumping from meeting to meeting, and now actually I'm at the security tech talk. [23:42:30] But ok, sounds good. [23:42:45] firm deadline for next week sounds good [23:42:51] meanwhile we can fine tune [23:46:56] qgil: I'm thinking we should reserve one slot per area in the big room, and let that be the backbone of the schedule [23:48:00] One slot for each area every day? [23:48:38] well, that is a detail, but in general that might a way to structure the schedule, yes [23:50:51] Robertson 1 is the big room: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016/2016-01-04 [23:52:11] we have 7 open slots there, under the currently published schedule (4 on the first day, 3 on the second day. Theoretically, rfarrand may turn that into 8) [23:53:38] True. :) So yes. [23:53:40] in the event of 8, we potentially have the opportunity to give each area an anchor, plus bias the selection of the following meeting to be in the same area [23:54:12] that works great for 4->8. It doesn't work as well for 5->8 (or 7) which is what we have [23:54:25] so, here's my proposal [23:55:36] Monday, 10am, we do Content Format. Monday: 11:30am, we do Content API [23:56:03] those are the two that gwicke was proposing to merge in the ArchCom meeting, but are also already very big areas [23:57:13] we then have one other area in the afternoon, and then split the other two on Tuesday (one before lunch, one after) [23:58:22] that's the basics of my thinking, and I think that's what I'm going to start drafting into the schedule. qgil: does that work for you? [23:59:13] It is a good backbone indeed, robla [23:59:31] from there, building the rest of the pre-schedule will be simpler