Hi Emily and Dscho, On Tue, Sep 17, 2019 at 1:28 PM Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > On Mon, 16 Sep 2019, Emily Shaffer wrote: > > > Jonathan Tan, Jonathan Nieder, Josh Steadmon and I met on Friday to > > talk about projects and we came up with a trimmed list; not sure what > > more needs to be done to make them into fully-fledged proposals. > > Thank you for doing this! Yeah, great! > > For starter microprojects, we came up with: > > > > - cleanup a test script (although we need to identify particularly > > which ones and what counts as "clean") > > - moving doc from documentation/technical/api-* to comments in the > > appropriate header instead > > - teach a command which currently handles its own argv how to use > > parse-options instead > > - add a user.timezone option which Git can use if present rather than > > checking system local time > > Nice projects, all. There are a couple more ideas on > https://github.com/gitgitgadget/git/issues, they could probably use some > tagging. Thanks! Maybe we should have a page with Outreachy microprojects on https://git.github.io/ I will see if I find the time to create one soon with the above information. > > For the longer projects, we came up with a few more: [...] > > - git-bisect.sh > > That would be my top recommendation, especially given how much effort > Tanushree put in last winter to make this conversion to C so much more > achievable than before. I just added a project in the Outreachy system about it. I would have added the link but Outreachy asks to not share the link publicly. I am willing to co-mentor (or maybe mentor alone if no one else wants to co-mentor) it. Anyone willing to co-mentor can register on the outreachy website. Thanks for the other suggestions by the way. > Converting shell/Perl scripts into built-in C never looks as much fun as > open-ended projects with lots of playing around, but the advantage of > the former is that they can be easily structured, offer a lot of > opportunity for learning, and they are ultimately more rewarding because > the goals are much better defined than many other projects'. I agree. Outreachy also suggest avoiding projects that have to be discussed a lot or are not clear enough. > > - reduce/eliminate use of fetch_if_missing global I like this one! > > It might make sense to only focus on scoping the ones we feel most > > interested in. We came up with a pretty big list because we had some > > other programs in mind, so I suppose it's not necessary to develop all > > of them for this program. I agree as I don't think we will have enough mentors or co-mentors for a big number of projects. Best, Christian.
