From: Christian Couder <email@example.com> To: Emily Shaffer <firstname.lastname@example.org>, Johannes Schindelin <Johannes.Schindelin@gmx.de> Cc: Jeff King <email@example.com>, Jonathan Tan <firstname.lastname@example.org>, git <email@example.com> Subject: Re: Git in Outreachy December 2019? Date: Tue, 17 Sep 2019 17:10:43 +0200 [thread overview] Message-ID: <CAP8UFD38S_nV2NmjeadZ0J5ftJgBwghOZ+BNHZaNQ72nZmLtNA@mail.gmail.com> (raw) In-Reply-To: <nycvar.QRO.firstname.lastname@example.org> Hi Emily and Dscho, On Tue, Sep 17, 2019 at 1:28 PM Johannes Schindelin <Johannes.Schindelin@gmx.de> 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.
next prev parent reply other threads:[~2019-09-17 15:10 UTC|newest] Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-27 5:17 Jeff King 2019-08-31 7:58 ` Christian Couder 2019-08-31 19:44 ` Olga Telezhnaya 2019-09-04 19:41 ` Jeff King 2019-09-05 7:24 ` Christian Couder 2019-09-05 19:39 ` Emily Shaffer 2019-09-06 11:55 ` Carlo Arenas 2019-09-07 6:39 ` Jeff King 2019-09-07 10:13 ` Carlo Arenas 2019-09-07 6:36 ` Jeff King 2019-09-08 14:56 ` Pratyush Yadav 2019-09-09 17:00 ` Jeff King 2019-09-23 18:07 ` SZEDER Gábor 2019-09-26 9:47 ` SZEDER Gábor 2019-09-26 19:32 ` Johannes Schindelin 2019-09-26 21:54 ` SZEDER Gábor 2019-09-26 11:42 ` Johannes Schindelin 2019-09-13 20:03 ` Jonathan Tan 2019-09-13 20:51 ` Jeff King 2019-09-16 18:42 ` Emily Shaffer 2019-09-16 21:33 ` Eric Wong 2019-09-16 21:44 ` SZEDER Gábor 2019-09-16 23:13 ` Jonathan Nieder 2019-09-17 0:59 ` Jeff King 2019-09-17 11:23 ` Johannes Schindelin 2019-09-17 12:02 ` SZEDER Gábor 2019-09-23 12:47 ` Johannes Schindelin 2019-09-23 16:58 ` SZEDER Gábor 2019-09-26 11:04 ` Johannes Schindelin 2019-09-26 13:28 ` SZEDER Gábor 2019-09-26 19:39 ` Johannes Schindelin 2019-09-26 21:44 ` SZEDER Gábor 2019-09-27 22:18 ` Jeff King 2019-10-09 17:25 ` SZEDER Gábor 2019-10-11 6:34 ` Jeff King 2019-09-23 18:19 ` Jeff King 2019-09-24 14:30 ` Johannes Schindelin 2019-09-17 15:10 ` Christian Couder [this message] 2019-09-23 12:50 ` Johannes Schindelin 2019-09-23 19:30 ` Jeff King 2019-09-23 18:07 ` Jeff King 2019-09-24 14:25 ` Johannes Schindelin 2019-09-24 15:33 ` Jeff King 2019-09-28 3:56 ` Junio C Hamano 2019-09-24 0:55 ` Eric Wong 2019-09-26 12:45 ` Johannes Schindelin 2019-09-30 8:55 ` Eric Wong 2019-09-28 4:01 ` Junio C Hamano 2019-09-20 17:04 ` Jonathan Tan 2019-09-21 1:47 ` Emily Shaffer 2019-09-23 14:23 ` Christian Couder 2019-09-23 19:40 ` Jeff King 2019-09-23 22:29 ` Philip Oakley 2019-10-22 21:16 ` Emily Shaffer 2019-09-23 11:49 ` Christian Couder 2019-09-23 17:58 ` Jonathan Tan 2019-09-23 19:27 ` Jeff King 2019-09-23 20:48 ` Jonathan Tan 2019-09-23 19:15 ` Jeff King 2019-09-23 20:38 ` Jonathan Tan 2019-09-23 21:28 ` Jeff King 2019-09-24 17:07 ` Jonathan Tan 2019-09-26 7:09 ` Jeff King
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAP8UFD38S_nV2NmjeadZ0J5ftJgBwghOZ+BNHZaNQ72nZmLtNA@mail.gmail.com \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Git in Outreachy December 2019?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).