From: Eric Wong <e@80x24.org>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org
Subject: Re: Announcing git-mentoring@googlegroups.com
Date: Sat, 23 Nov 2019 00:17:49 +0000 [thread overview]
Message-ID: <20191123001749.GA12923@dcvr> (raw)
In-Reply-To: <20191122231921.GB101478@google.com>
Emily Shaffer <emilyshaffer@google.com> wrote:
> On Fri, Nov 22, 2019 at 08:31:27PM +0000, Eric Wong wrote:
> > Emily Shaffer <emilyshaffer@google.com> wrote:
> > > The community expectations for the mailing list are the same as those
> > > for the main Git list, but posts are only visible to members (anyone can
> > > join) in order to create a more private space for beginner questions.
> >
> > It would be better to promote anonymous or pseudonymous posts
> > if beginners aren't comfortable...
> >
> > > For now, posting is limited to members only (again, anyone can join) -
> > > but if we find a high incidence of needing to forward messages to and
> > > from the main list, we can change that permission as needed.
> >
> > ...because anybody can expose the archives, anyways. And right now,
> > messages aren't visible to generic search engines, either; so fewer
> > people can get helped...
>
> Hm, this is a little circular, right? Part of the rationale for keeping
> viewing limited was "that way it's not visible to generic search
> engines".
Sorry if I wasn't clear. My points were:
1) limiting visibility harmful to helpfulness
2) trusting "members" to keep potentially embarrasing posts
away from the public eye is unrealistic. Let posters
maintain anonymity or pseudonymity for themselves.
next prev parent reply other threads:[~2019-11-23 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 19:47 Announcing git-mentoring@googlegroups.com Emily Shaffer
2019-11-22 20:31 ` Eric Wong
2019-11-22 23:19 ` Emily Shaffer
2019-11-23 0:17 ` Eric Wong [this message]
2019-11-25 14:23 ` 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=20191123001749.GA12923@dcvr \
--to=e@80x24.org \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
/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).