From: Derrick Stolee <stolee@gmail.com> To: Jeff King <peff@peff.net> Cc: "git@vger.kernel.org" <git@vger.kernel.org>, Emily Shaffer <emilyshaffer@google.com>, Jonathan Nieder <jrnieder@gmail.com>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, "gitster@pobox.com" <gitster@pobox.com>, garimasigit@gmail.com Subject: Re: [DISCUSSION] Growing the Git community Date: Thu, 19 Sep 2019 22:17:57 -0400 Message-ID: <d13a8d01-065b-bfff-d279-c57cd0c0f7c9@gmail.com> (raw) In-Reply-To: <20190919221615.GA25636@sigill.intra.peff.net> On 9/19/2019 6:16 PM, Jeff King wrote: > On Thu, Sep 19, 2019 at 12:30:13PM -0400, Derrick Stolee wrote: >> >> 5. Advertise that Git wants new contributors >> > This point is the one I'm least on board with. Not because I'm not > thrilled to have new contributors, but that to some degree I think the > open source system relies heavily on intrinsic motivations like > scratching your own itch. I'm worried that advertising "hey, we need > people to work on stuff!" then brings in people who are well-meaning but > don't necessarily care much about Git in particular. And it becomes an > administrative headache to try to figure out things for them to do, or > get them acclimated to the community. Your concerns are valid. > I.e., I think we want to grow the community a bit more organically, > which should be more sustainable in the long run.> > So I think any advertising would be more about making it clear that _if_ > you have an idea, we're very interested in welcoming newcomers. And that > to me falls under a lot of the points already made above: making the > process more clear and more inviting to people who are already thinking > about contributing. I guess I was vague about this. It's not "we need more people to work on our (non-existent) backlog" but instead "if you have an interest in contributing your (existing) ideas to Git, we welcome you with open arms!" Thanks, -Stolee
next prev parent reply other threads:[~2019-09-20 2:18 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-19 16:30 Derrick Stolee 2019-09-19 17:34 ` Denton Liu 2019-09-19 20:43 ` Emily Shaffer 2019-09-19 22:26 ` Jeff King 2019-09-20 17:48 ` Junio C Hamano 2019-09-20 15:22 ` Garima Singh 2019-09-20 17:51 ` Junio C Hamano 2019-09-19 18:44 ` Klaus Sembritzki 2019-09-19 19:12 ` Klaus Sembritzki 2019-09-19 20:20 ` Klaus Sembritzki 2019-09-20 5:04 ` Klaus Sembritzki 2019-09-20 5:41 ` Klaus Sembritzki 2019-09-20 6:54 ` Klaus Sembritzki 2019-09-20 7:43 ` Klaus Sembritzki 2019-09-20 10:25 ` Klaus Sembritzki 2019-09-19 21:40 ` Mike Hommey 2019-09-23 21:28 ` Johannes Schindelin 2019-10-01 15:03 ` Jakub Narebski 2019-09-19 22:16 ` Jeff King 2019-09-20 2:17 ` Derrick Stolee [this message] 2019-09-20 2:23 ` Jeff King 2019-09-19 22:21 ` Elijah Newren 2019-09-25 13:36 ` Pierre Tardy 2019-09-25 14:02 ` Derrick Stolee 2019-10-04 12:39 ` Jakub Narebski 2019-09-25 14:14 ` Philip Oakley 2019-10-04 10:48 ` Jakub Narebski 2019-11-12 18:45 ` Emily Shaffer 2019-11-12 20:01 ` Johannes Schindelin 2019-11-13 6:45 ` Christian Couder 2019-11-13 15:06 ` Thomas Gummerer 2019-11-14 2:31 ` Emily Shaffer 2019-11-14 6:06 ` Jeff King 2019-11-15 4:48 ` Junio C Hamano 2019-11-14 6:08 ` Pratyush Yadav 2019-11-14 10:01 ` Thomas Gummerer 2019-09-20 10:48 ` Philip Oakley 2019-09-20 14:36 ` brian m. carlson 2019-09-20 15:16 ` Randall S. Becker 2019-10-04 14:27 ` Jakub Narebski 2019-09-20 15:20 ` Garima Singh 2019-09-20 17:43 ` Junio C Hamano 2019-09-20 18:52 ` Junio C Hamano 2019-09-23 12:36 ` Derrick Stolee 2019-09-23 21:46 ` Johannes Schindelin
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=d13a8d01-065b-bfff-d279-c57cd0c0f7c9@gmail.com \ --to=stolee@gmail.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=emilyshaffer@google.com \ --cc=garimasigit@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=jrnieder@gmail.com \ --cc=peff@peff.net \ --subject='Re: [DISCUSSION] Growing the Git community' \ /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
git@vger.kernel.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ git@vger.kernel.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git