[05:25:17] Could https://codein.withgoogle.com/dashboard/tasks/5116835657678848/ be published pls [05:25:28] generic pywikibot task ;-) [05:26:05] see https://phabricator.wikimedia.org/T60941#2827394 [09:59:08] will do... [10:07:22] maybe we need an unpublished column on the GCI workboard ? [10:08:19] Do we have a generic "fix a bug " task that can be used to allow follow-on tasks for participants ? e.g. https://codein.withgoogle.com/tasks/5692963376070656/ "FOSSASIA: Do a mini-project, solve an issue, add a feature, fix a bug, improve design, add tests" [10:11:46] jayvdb, we could have an unpublished column if it helps to solve some problem. (as it also adds more workload to keep stuff in sync) [10:11:59] I don't know which exact problem it solves though :) [10:12:30] No, we don't have a generic 'fix a bug' task (and I'd love to have time to see what the other projects do, especially Fossasia is great). [10:12:47] Should we? :) I'd be very open to try, but our mentor structure is a bit different I think [10:14:37] I am also a FOSSASIA mentor, so I see more of how they do it. some aspects are terrible , but others are good. generic bugs are good. slack chat rooms are good. [10:15:27] they are drowning in crappy submissions because their beginner tasks are inviting people with no chance of ever being a technical contributor [10:17:50] andre__: : could you also publish https://codein.withgoogle.com/tasks/5187941458509824/ pls [10:20:16] ah, interesting! I'd love to know more about that [10:20:34] Published! Thanks for the ping! [10:33:36] I've created a generic Pywikibot "enhancement" task at https://codein.withgoogle.com/dashboard/tasks/4719662784839680/ [10:35:12] We have a good Python coder who has just finished a task, so I want to keep giving them tasks they can do ;-) [10:35:48] IIRC, a student cant do the same task twice. So the generic task can only be used once; then I need to write a custom task for them..? [10:39:08] jayvdb: yeah, unfortunately. That's why we had "Make X translatable part 15" tasks and such last year. Highly recommended to add numbering, makes it easier to differentiate [10:39:16] should I publish https://codein.withgoogle.com/dashboard/tasks/4719662784839680/ ? [11:29:38] Yes please [11:31:16] On the FOSSASIA coala sub-org we are using codes for all tasks, e.g CI1, CI2, CI3, followed by the long description [11:35:23] published! thanks [12:53:22] very much appreciated [13:19:12] naah, other way round - I highly appreciate your GCI tasks! :) [16:42:46] andre__: around :) [16:42:51] Looking forward at the GCI meeting. The recent hack on Deutsche Telekom has cut down my internet speed so slow that I dont even know how my participation would go [16:42:53] I have a quick question for you! [16:43:03] srishakatux, shoot! [16:43:09] yay! Tony :D [16:43:31] tonythomas: at least Google is not completely down in your area. happened to me last week. [16:43:52] andre__: god. looks like its the end of the world closing on us. [16:44:05] that to create a completely new task for GCI, does it need to be on Phabricator already? [16:44:06] * andre__ gets some popcorn [16:44:07] andre__: btw. Today I posted the black money to India. Hope the customs wont mind it. [16:44:18] srishakatux: it's not a must, no [16:44:27] srishakatux: our rules are pretty blurry when it comes to this [16:44:35] and if you create on on GCI site, do you then need to create it on Phab? [16:44:43] or even then no [16:44:45] srishakatux: the advantage of having the task on Phab though is that if noone picks it up in GCI, noone will know that this task exists [16:45:00] srishakatux, and hence it won't be available as an #easy tasks to any new contributors outside of GCI [16:45:12] okay! got it. [16:45:13] srishakatux: you don't have to. but it's very welcome. [16:45:32] srishakatux, it's that tradeoff between a closed platform like GCI and additional time+work to dup it on Phab basically [16:45:36] just letting you two :) that we dont have much people coming in :D [16:45:59] and also even if some are, I am speculating that they are mostly from WMF [16:46:14] okay [16:46:36] tonythomas: where did you get all that black money from :D [16:48:19] tonythomas: Good good! We'll be rich if this works out :P [16:53:30] * andre__ reboots [17:54:22] srishakatux: Thank you! That was good! [17:54:43] srishakatux: (and I hope I wasn't too dominant) [17:55:23] hehe :) no no andre__ you were awesome :) [17:55:33] I wouldn't have been able to answer any of that :D [17:55:35] True. it went great :) [17:55:59] thank you tonythomas for joining and bringing your awesome ideas as always :D [17:56:07] srishakatux: btw, the one thing about black money - you dont speak about where it came from :P (For the record, it was sent by someone with the name andre__ ) [17:56:22] srishakatux: heh. I would always want a #wikimedia-gci [17:56:33] srishakatux, I'm just trying to pass all my knowledge to you so you will run that next year :P [17:57:08] andre__: it won't be that easy :D you have been doing it for years and are a pro :D I will take double the years to learn that :D [17:57:19] (I'm half-serious. GCI is pretty... exhausting, after 4yrs. I'm still going to be around of course!) [17:57:41] srishakatux: haha, you've been doing great so far, way better than me, when it comes to recruiting mentors for example [17:57:55] hehe.. that is easy :P [17:59:58] srishakatux: just another note for gci admins: we always have to have 50 tasks open and available. so that's also a thing to keep an eye on when publishing new tasks, and trying to find new tasks. [18:00:24] (it's been sometimes making me a bit nervous in the past when we went close to those 50, without having many unpublished tasks in the backlog) [18:00:55] ahha, I see. [18:03:34] I am thinking of creating one new task about wikispeech logo today, that Quim mentioned :D [18:04:45] andre: unless you think it does not make sense :P [18:05:15] srishakatux: that would be lovely. That email is still on to-do in my inbox. If you describe requirements a bit (like "you've used an SVG editor before" or such) and expected file format etc, and "we collect proposals so don't be disappointed if your proposal is not the one that is chosen in the end", that could be a fun task [18:05:34] maybe you could also contact the original proposer and tell them about the code-in idea, but they might not know what GCI is [18:06:24] okay great! I will do that, will hopefully learn how it is actually done :) [18:06:41] and this doesn't need to be on Phabricator, straight on GCI? [18:07:03] I'd say so in this specific case, yes [18:07:09] There's a deadline [18:07:21] and this is on-wiki stuff that feels a bit out of scope for Phab IMHO [18:07:55] can't parse what you just said [18:08:05] so you are saying that I should create a task on Phabricator? [18:08:40] nope [18:08:45] go straight to GCI [18:08:57] LOL :D [18:08:58] okay [18:08:59] logos are on-wiki things. which makes it feel like out of scope for Phabricator [18:09:14] ahha, got it got it now! [18:09:30] will do it today! and loop you in it. [18:19:28] ...and I guess you can resolve T150636 [18:19:28] T150636: Organize/ prepare content for an informational google hangout session for new Google Code-In mentors on Thu 2016-12-01 17:00UTC - https://phabricator.wikimedia.org/T150636 [18:19:35] Congrats! [18:23:48] https://codein.withgoogle.com/dashboard/task-instances/4880241149345792/ - andre__ ; he bit the hook . again, thanks [18:24:11] hah. will publish in a min. thanks! [18:24:32] (this is the one you published a while ago) [18:25:06] ahaha. well, in that case: nice nice to see things are working as expected! :D [18:25:35] * andre__ still needs to start learning those 16 digit GCI numbers by heart. It already works for Phabricator, partially. [18:27:29] haha