git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: "Michal Suchánek" <msuchanek@suse.de>
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 13:41:59 -0700	[thread overview]
Message-ID: <CAJoAoZnKebM4m3AXW6+RBY7dBsQhAcReqd61VtXHNjcnPBeemQ@mail.gmail.com> (raw)
In-Reply-To: <20220316201058.GI163591@kunlun.suse.cz>

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
normal mailing list in your inbox. Anyway, as I mentioned in
https://lore.kernel.org/git/CAJoAoZn91dyFEdMKUj_XU8CjUbh5EtdqjTR3CaAe%3DBhii7dt3Q%40mail.gmail.com,
the list mostly serves as a roster, not as a place for discussion.

 - Emily

  reply	other threads:[~2022-03-16 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 21:04 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 [this message]
2022-03-16 21:34     ` Michal Suchánek
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

  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=CAJoAoZnKebM4m3AXW6+RBY7dBsQhAcReqd61VtXHNjcnPBeemQ@mail.gmail.com \
    --to=emilyshaffer@google.com \
    --cc=amerrick@google.com \
    --cc=git@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --subject='Re: Let'\''s have a user experience workshop' \
    /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

Code repositories for project(s) associated with this 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).