git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Eric Wong <e@80x24.org>
Cc: Emily Shaffer <emilyshaffer@google.com>, git@vger.kernel.org
Subject: Re: Announcing git-mentoring@googlegroups.com
Date: Mon, 25 Nov 2019 09:23:51 -0500	[thread overview]
Message-ID: <20191125142351.GE494@sigill.intra.peff.net> (raw)
In-Reply-To: <20191123001749.GA12923@dcvr>

On Sat, Nov 23, 2019 at 12:17:49AM +0000, Eric Wong wrote:

> > 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.

I think it's trying to find a tradeoff, though. The point isn't to guard
sensitive information. It's to have a less intimidating forum for people
to converse in. Even though anybody from the public _could_ join and
read them, keeping them out of most web searches may be more
comfortable. Likewise, members of the group _could_ exfiltrate all of
the posts and show them publicly. But in practice that's unlikely.

Note that I'm guessing at what others would find more comfortable or
less intimidating. Obviously I'm quite happy to speak my mind all over
public mailing lists. ;) But the point is to give a forum for people who
aren't. I think this setup matches the mentoring list in other orgs.
E.g. Outreachy itself, though there I think you have to actually be an
intern to see the posts. We could moderate membership to the mentor list
but it seems like a hassle for little gain.

-Peff

      reply	other threads:[~2019-11-25 14:23 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
2019-11-25 14:23       ` Jeff King [this message]

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=20191125142351.GE494@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=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).