On Thu, Sep 06, 2018 at 11:51:49AM +0200, Christian Couder wrote: > > Thanks. I signed us up as a community (making me the "coordinator" in > > their terminology). I think the procedure is a little different this > > year, and we actually propose projects to mentor through their system. > > Yeah, I think the https://git.github.io/Outreachy-17/ is not actually necessary. I think it still may be helpful for explaining in further detail things like #leftoverbits (though I see you put some of that in your project description). > > So anybody interested in mentoring should go here: > > > > https://www.outreachy.org/communities/cfp/git/ > > > > (and you'll need to create a login if you don't have one from last > > year). You should be able to click through "Submit a Project Proposal", > > after which the fields are pretty self-explanatory. > > I did that for the "Improve `git bisect`" project. As the > "coordinator", you will need to approve that project. Thanks. I approved it, though a few of the descriptions are a little funny. For instance, the text says "we use an issue tracker", which then links to public-inbox. I assume this is because you filled in a field for "issue tracker" and then the system generated the text. I don't know if there's a way go into more detail there. > I think the person who submits a project becomes some kind of primary > mentor for the project. So Dscho, if you want to be such a mentor for > one or both of the other projects on the Outreachy-17 page, please > submit the project(s) otherwise please tell me and I will submit them. > You are free of course to change things in these projects when you > submit them or to submit other completely different projects. Yes, I think the point is make sure the mentors are invested in the individual projects. I imagine a kind of "oh, one of us will probably mentor it" attitude has led to problems in other projects in the past. -Peff
