From: Emily Shaffer <email@example.com> To: Jeff King <firstname.lastname@example.org> Cc: Jonathan Tan <email@example.com>, firstname.lastname@example.org Subject: Re: Git in Outreachy December 2019? Date: Mon, 16 Sep 2019 11:42:08 -0700 [thread overview] Message-ID: <20190916184208.GB17913@google.com> (raw) In-Reply-To: <20190913205148.GA8799@sigill.intra.peff.net> On Fri, Sep 13, 2019 at 04:51:49PM -0400, Jeff King wrote: > On Fri, Sep 13, 2019 at 01:03:17PM -0700, Jonathan Tan wrote: > > > > Do we have interested mentors for the next round of Outreachy? > > > > > > The deadline for Git to apply to the program is September 5th. The > > > deadline for mentors to have submitted project descriptions is September > > > 24th. Intern applications would start on October 1st. > > > > > > If there are mentors who want to participate, I can handle the project > > > application and can start asking around for funding. > > > > I probably should have replied earlier, but if Git has applied to the > > program, feel free to include me as a mentor. > > Great! See my followup here: > > https://public-inbox.org/git/20190904194114.GA31398@sigill.intra.peff.net/ > > Prospective mentors need to sign up on that site, and should propose a > project they'd be willing to mentor. > > > There was a discussion about mentors/co-mentors possibly working in a > > part of a codebase that they are not familiar with  - firstly, I > > think that's possible and even likely for most of us. :-) If any > > question arises, maybe it would be sufficient for the mentors to just > > help formulate the question (or pose the question themselves) to the > > mailing list. If "[Outreachy]" appears in the subject, I'll make it a > > higher priority for myself to answer those. > > I do think it's OK for mentors to not be intimately familiar with the > part of the code that is being touched, as long as the project is simple > enough that they can pick up the technical details easily as-needed. A > lot of what mentors will help mentees with is the overall process (both > Git-specific parts, but also more general development issues). But I > think the proposed projects do need to be feasible. > > I'm happy to discuss possible projects if anybody has an idea but isn't > sure how to develop it into a proposal. Hi Peff, 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. 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 For the longer projects, we came up with a few more: - find places where we can pass in the_repository as arg instead of using global the_repository - convert sh/pl commands to C, including: - git-submodules.sh - git-bisect.sh - rebase --preserve-merges - add -i (We were afraid this might be too boring, though.) - reduce/eliminate use of fetch_if_missing global - create a better difftool/mergetool for format of choice (this one ends up existing outside of the Git codebase, but still may be pretty adjacent and big impact) - training wheels/intro/tutorial mode? (We thought it may be useful to make available a very basic "I just want to make a single PR and not learn graph theory" mode, toggled by config switch) - "did you mean?" for common use cases, e.g. commit with a dirty working tree and no staged files - either offer a hint or offer a prompt to continue ("Stage changed files and commit? [Y/n]") - new `git partial-clone` command to interactively set a filter, configure other partial clone settings - add progress bars in various situations - add a TUI to deal more easily with the mailing list. Jonathan Tan has a strong idea of what this TUI would do... This one would also end up external but adjacent to the Git codebase. - try and make progress towards running many tests from a single test file in parallel - maybe this is too big, I'm not sure if we know how many of our tests are order-dependent within a file for now... 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. - Emily
next prev parent reply other threads:[~2019-09-16 18:42 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 [this message] 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 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=20190916184208.GB17913@google.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).