From: Jeff King <email@example.com> To: Pratyush Yadav <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Git in Outreachy December 2019? Date: Mon, 9 Sep 2019 13:00:03 -0400 [thread overview] Message-ID: <20190909170002.GA30399@sigill.intra.peff.net> (raw) In-Reply-To: <firstname.lastname@example.org> On Sun, Sep 08, 2019 at 08:26:10PM +0530, Pratyush Yadav wrote: > I'd like to put out a proposal regarding first contributions and micro > projects. > > I have a small list of small isolated features and bug fixes that > _I think_ git-gui would benefit with. And other people using it can > probably add their pet peeves and issues as well. My question is, are > these something new contributors should try to work on as an > introduction to the community? Since most of these features and fixes > are small and isolated, they should be pretty easy to work on. And I > think people generally find UI apps a little easier to work on. > > But I'll play the devil's advocate on my proposal and point out some > problems/flaws: > - Git-gui is written in Tcl, and git in C (and other languages too, but > not Tcl). That means while people do get a feel of the community and > general workflow, they don't necessarily get a feel of the actual git > internal codebase. > - Since I don't see a git-gui related project worth being into the > Outreachy program, it essentially means they will likely not work on > anything related to their project. > - Git-gui is essentially a wrapper on top of git, so people won't get > exposure to the git internals. > > I'd like to hear your and the rest of the community's thoughts about > this proposal, and whether it will be a good idea or not. Right, I came up with similar devil's advocate arguments. :) I'm not totally opposed, because part of the point of these microprojects just getting people familiar with interacting with the community and submitting a patch. They're not always in the same area the intern intends to work, just because there's not always a trivial problem to be solved there. So we do look at it mostly as a "can you do this basic test" test, and not necessarily as a prelude to the project. But it would be nice if it were at least in the same _language_ that the ultimate project will be done in. Because we're evaluating the applicant's ability to write code in that language, too. So I dunno. I am on the fence. -Peff
next prev parent reply other threads:[~2019-09-09 17:00 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 [this message] 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 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=20190909170002.GA30399@sigill.intra.peff.net \ --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).