[20:33:14] srishakatux: do we have somewhere I can point Outreach/GSoC folks asking about multiple people on the same project? [21:18:47] some gsoc FAQ? [21:19:08] you can't have several people doing the *same* project [21:19:37] they may be similar, or each a part of a greater thing (and still, that's problematic) [21:19:40] but doing the same… [21:19:54] well, maybe if you really wanted duplication :\ [21:27:05] Hi [21:38:29] c [21:38:50] Dereckson: HI :) [21:56:35] ragesoss: Platonides: I think https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project is the best place if you're looking for a general guide. But the answer to the question about multiple people on same project is "No" and that's answered on the respective websites for those programs (GSoC/Outreachy). [21:57:09] See https://developers.google.com/open-source/gsoc/faq#can_a_group_submit_a_proposal_together_to_work_on_a_single_project [21:57:16] Niharika: cool, thanks. I knew the answer was 'no' for the particular case, but wasn't sure about it more broadly. [21:57:54] :) [21:58:07] Hi [21:58:11] and was just wondering if there was a quick place I could link people to that had more detail than I had about it. [21:58:39] Yeah, just ask them to read up the gsoc/outreachy website in more detail next time. [21:58:48] So few students bother to. :/ [21:59:15] while you are discussing gsoc lets add my gsoc question as well. I'm struggling a bit with comming up with good microtask [21:59:16] s [22:00:04] https://phabricator.wikimedia.org/T138464 most micro tasks for other projects are bug fixes within an existing code base [22:00:09] I think part of the dynamic is that they are trying to feel out which projects alread have people planning to apply, and they are sometimes interacting with the other people in the same thread, and they're in the awkward position of threatening competition for someone else. [22:01:14] but as this project is a bit stand alone. I'm doubting between letting the student do some work on functions which will surely be needed later on/laying the ground work and doing something in an existing python based tool [22:02:53] basvb_ what about something like sketching the UI for a microtask? [22:03:46] yep, although I'm mostly interested in their back-end skills, but that's a good one to add into the mix [22:03:58] or setting up a super simple UI as a tool, using the necessary language, without any of the implementation yet. [22:04:05] also had a small flask one in mind [22:04:52] but more general letting them work on other tools feels a bit odd as a way to let them convey their interest/capabilities for this project [22:06:35] yeah. tricky.