list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <>
To: Philip Oakley <>
Cc: Alice Merrick <>, Git List <>
Subject: Re: Let's have a user experience workshop
Date: Wed, 16 Mar 2022 10:48:57 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Mar 16, 2022 at 10:38 AM Philip Oakley <> wrote:

> > Interested?
> > * Join the git UX Google group ( if you
> > are interested in participating in an event.
> I joined the group, but there are no current entries, and, at present I
> can't post anything.

I can shed a little light here. I set up the list; for now, it's
primarily intended for use as a roster for a future live event
(similar to, but smaller scale than, the diversity/equity/inclusion
workshop we had a couple of years ago). Maybe after the event it will
be useful to open that list up for posting, but if I'm being honest,
I'd personally prefer to keep discussions about Git's UX on git@vger,
where everybody can participate. Hopefully that rationale clears up
why you're unable to post or see anything there. :)

 - Emily

  reply	other threads:[~2022-03-16 17:49 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 [this message]
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
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:

  List information:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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 inbox:

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