From: Jeff King <peff@peff.net>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Thomas Gummerer <t.gummerer@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Elijah Newren <newren@gmail.com>,
Derrick Stolee <stolee@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
"gitster@pobox.com" <gitster@pobox.com>,
Garima Singh <garimasigit@gmail.com>
Subject: Re: [DISCUSSION] Growing the Git community
Date: Thu, 14 Nov 2019 01:06:50 -0500 [thread overview]
Message-ID: <20191114060650.GC10643@sigill.intra.peff.net> (raw)
In-Reply-To: <20191114023100.GD22855@google.com>
On Wed, Nov 13, 2019 at 06:31:00PM -0800, Emily Shaffer wrote:
> Christian's suggestion of a Google Group list was good enough for me.
> For now, the permission settings are as follows:
>
> - Group visibility: Anyone. (So it can be easier to discover and
> advertise.)
> - View topics: Group members only. (Maybe we want to open this up so
> it's easier for non-member Git contributors to take a look at what's
> going on.... but maybe if they're interested they can just join the
> group :) )
I think it makes sense to stay closed for now. One of the reasons to
have a separate group is to make it less daunting to post to. Having a
public archive may work against that.
> - Post: Group members only. (My thinking is that once you're asking for
> someone's time and effort to help mentor you, you can volunteer the
> time and effort needed to push the join button and optionally filter
> your inbox ;) )
It also cuts down on spam (I moderate the git-security google group, and
the spam-blocking is far from perfect).
It is annoying if things get cross-posted to git@vger (whoever replies
with the cc intact will get an annoying "you can't post here" bounce).
But I'd try it this way for a while and see.
> - Join group: Anyone. (Let's make the barrier to entry low.)
Makes sense. I just joined.
-Peff
next prev parent reply other threads:[~2019-11-14 6:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 16:30 [DISCUSSION] Growing the Git community 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
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 [this message]
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=20191114060650.GC10643@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=garimasigit@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
--cc=t.gummerer@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).