git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: Alice Merrick <amerrick@google.com>, Git List <git@vger.kernel.org>
Subject: Re: Let's have a user experience workshop
Date: Wed, 16 Mar 2022 22:34:52 +0100	[thread overview]
Message-ID: <20220316213452.GJ163591@kunlun.suse.cz> (raw)
In-Reply-To: <CAJoAoZnKebM4m3AXW6+RBY7dBsQhAcReqd61VtXHNjcnPBeemQ@mail.gmail.com>

On Wed, Mar 16, 2022 at 01:41:59PM -0700, Emily Shaffer wrote:
> On Wed, Mar 16, 2022 at 1:11 PM Michal Suchánek <msuchanek@suse.de> wrote:
> 
> > > * Reply directly to this email if you are interested in organizing the
> > > event to discuss git UX (scheduling the event, sending invites,
> > > communicating with invitees)
> >
> > Can you, please, use a sane mailing list for the discussion?
> >
> > The user experience of Google Groups really bad.
> >
> > Also it seems it is accessible only to people with a google account.
> >
> > Could you use a more inclusive technology?
> 
> Git already uses Google Groups for the security list (e.g. for fixing
> pre-disclosure security issues) and for the mentoring list, and it's
> fine to subscribe to one with a non-Google account; it acts just as a

The link you provided only allows access with a Google account. If there
is one that allows access in other ways it was not provided.

Please try to use open technologies that are accessible to everyone, not
only people affliated with one specific company.

Thanks

Michal

  reply	other threads:[~2022-03-16 21:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 21:04 Let's have a user experience workshop Alice Merrick
2022-03-16 17:36 ` Philip Oakley
2022-03-16 17:48   ` Emily Shaffer
2022-03-16 21:50     ` Philip Oakley
2022-03-16 20:10 ` Michal Suchánek
2022-03-16 20:41   ` Emily Shaffer
2022-03-16 21:34     ` Michal Suchánek [this message]
2022-03-16 22:05     ` Junio C Hamano
2022-05-10  3:35 ` Jonathan Nieder
2022-05-12 22:23   ` Emily Shaffer
2022-05-15 16:17     ` Jonathan Nieder
2022-05-16  7:43       ` Emily Shaffer
2022-05-20 16:17         ` Alice Merrick
2022-05-20 16:22           ` rsbecker

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220316213452.GJ163591@kunlun.suse.cz \
    --to=msuchanek@suse.de \
    --cc=amerrick@google.com \
    --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. 
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 NNTP newsgroup(s).