[07:28:55] hi i want to start working. please give me the direction [07:30:07] rahul: That's vague. What do you want to work on? [07:32:27] i couldn't find documentation of any project?? [09:06:37] Read the channel topic, for future reference. [17:02:45] Questions & Answers IRC hour for new Google Code-in 2017 Wikimedia mentors in this channel starting in one hour. [17:58:11] Hello ! [18:00:00] Hi everybody! [18:00:04] Starting now here: IRC hour for new Google Code-in 2017 Wikimedia mentors (Questions & Answers) [18:00:12] I'm going to wait about 2 or 3 more minutes if someone's late [18:00:18] hi framawiki :) [18:02:08] So... for the next hour in this IRC channel, we'll have a "Questions & Answers" session for Google Code-in 2017 Wikimedia mentors [18:02:21] We already had such a session 73 hours ago but in a "Google Hangout" video call, and this IRC hour is another option. [18:02:32] And In general, we also collect "Feedback and Lessons learned" for Wikimedia's participation in GCI in https://phabricator.wikimedia.org/T181738 and you are free to add comments. [18:02:47] What I always say is: We had more than 300 GCI tasks fixed last year, so we definitely need more tasks in the next six weeks, especially for the holidays around the end of this calendar year. Please spread the word and add more tasks. :) [18:03:15] I don't want to repeat everything again that's already written on https://www.mediawiki.org/wiki/Google_Code-in/Mentors (which also links to the "Mentor responsibilities" defined by Google) and in the email that GCI mentors received last Tuesday. [18:03:41] That's all from my side. Whatever questions or comments you have: Please ask them. I'm here for the next 55 minutes. :) [18:04:13] Please feel free to ask questions about Google Code-in and/or add your comments [18:04:48] Hello [18:05:10] hi [18:05:27] so I'll repost these two lines: [18:05:31] I don't want to repeat everything again that's already written on https://www.mediawiki.org/wiki/Google_Code-in/Mentors (which also links to the "Mentor responsibilities" defined by Google) and in the email that GCI mentors received last Tuesday. [18:05:35] Hiya [18:05:40] Whatever questions or comments you have: Please ask them. We're here for the next 55 minutes. :) [18:05:48] o/ [18:06:12] just an idea: It would be interesting to make a commons category for all files created during the event [18:06:15] hello everyone! :) [18:06:20] Yo srish! [18:06:32] Yo Andre! [18:06:58] framawiki, hmm... "interesting" yes, but also another step to perform for tasks that include "upload something to Commons" :) [18:07:51] andre__: Can we inform students about their progress? [18:08:10] rlot, in which way? per task you better should, as a mentor :D [18:08:12] Rlot what do you mean? [18:08:35] There's students list tab in GCI dashboard [18:08:36] but as there is no "leaderboard" or ranking, I think it is intentional to not say "You have XY tasks resolved and you are in the Xth place" [18:08:53] Oh, ok [18:09:03] Hah, I've never looked at that tab. True :D [18:09:21] it's an interesting question. I'm not entirely sure [18:09:42] afaik GCI had public leaderboard on pre 2015 editions [18:09:50] Melange? [18:10:10] yes [18:10:14] Maybe ask that on the general gci-mentors@ mailing list? I could also if you are not subscribed [18:10:37] yeah, but 2016 had a better software (no more "melange"), plus I think Google said they are more after quality than quantity of students' work [18:12:06] More...comments? Questions? Feedback? Criticism? Hugs? :) [18:12:39] andre__: if what happened with Albert221 yesterday with confusing tasks happens again how should it be handled [18:12:57] Yay, no more melange. I remember how terrible that was from when i was in gsoc [18:13:09] Fyi, i've built a leaderboard app that lists only github activity, so it isnt leaking anything [18:13:16] Can I become a mentor later on if I havent signed up yet? [18:13:21] bawolff: yes [18:14:09] ok, might do that in a couple of days [18:15:00] bawolff, if you'd already like to receive an invitation email, pass your preferred email address in a private /msg :) [18:15:09] http://community.coala.io [18:16:00] https://github.com/coala/community [18:17:02] jayvdb: You'e both coala and wikimedia mentor? [18:17:45] Would be easy to adjust to support Phab., but it isnt perfect as it misses tasks that arnt not a 'assigned' task [18:17:54] Org admin for both [18:18:57] jayvdb: Isn't coala part of fossasia? [18:19:21] I saw coala tasks as fossasia org last year [18:19:45] It is intentional that it only shows assign chucks of work, as it only showing what students could determine by a bit of stalking [18:20:09] Last year we were part of fossasia [18:22:15] We've also built https://coala.github.io/gci-leaders/ ;-) [18:28:05] More...comments? Questions? Feedback? Criticism? Hugs? [18:32:06] There is also https://github.com/i5o/gcileaderboard , which could be run on the toolserver, which is a complete leaderboard [18:33:47] jayvdb: install it on tools can be a gci task :) [18:35:48] the data can only be fetched by a mentor (for ^ tool) or org admin for my tool [18:36:13] nice. [18:36:32] Here is a good vein for new gci tasks https://phabricator.wikimedia.org/T107037 [18:37:07] someone needs to mentor them :P [18:37:24] framawiki: , are there any blockers remaining on that task ? [18:38:30] same with https://phabricator.wikimedia.org/T177810 and others [18:39:08] it looks like it has been done by a few senior devs, so most wrinkles should have been sorted out, and it is now very reproducible. [18:40:28] I'm not quite up to speed on the mw interface, so if a better dev can look on it :) [18:45:15] framawiki: which task are you referring to? [18:45:29] oh, convert the world to ooui [18:54:20] Last call for any comments or questions! :) [18:57:01] andre__: my question wasnt anawered [18:57:04] Answered* [18:57:57] Zppix, oh sorry! [18:58:25] Well, there is no general answer to that. Of course tasks should be as clearly phrased as possible, and of course any mentors should know very well what they mentor. [18:59:07] there will always be a small number of tasks that won't work out perfectly well. For example when a student cannot reproduce and realizes that the task is already fixed :D [18:59:13] andre__: I mentored task that required student to recreate this issue] [18:59:30] ...but I expect mentors to be experts in their field, help, and be generous. [18:59:31] And student reported that this issue does not occur [18:59:53] I looked into it, and I can confirm it [19:00:00] then the student did good work by trying to reproduce the issue and the student deserves credits for their task if they already claimed it :) [19:00:27] However there's no change in this extension codebase since creation of this ticket [19:00:36] its impossible that it fixed itself [19:00:37] Heisenbugs exist :D [19:00:47] https://en.wikipedia.org/wiki/Heisenbug [19:01:20] Hmm, accepted this GCI task, will handle it if this issue will still occur [19:01:36] Sounds good. Thanks :) [19:01:58] Alright... time is up! [19:01:58] (Of course anyone is free to continue discussions here, but I will need to slowly sneak out of here) [19:02:02] Thanks a lot everybody! [19:02:24] If mentors have any questions, feel free to contact the org admins - see https://www.mediawiki.org/wiki/Google_Code-in/Mentors for contact info [19:02:28] Thanks & cheers!