From: Philip Oakley <philipoakley@iee.email>
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 21:50:55 +0000 [thread overview]
Message-ID: <9bc6368d-cb14-8bd7-f58d-08087258311b@iee.email> (raw)
In-Reply-To: <CAJoAoZn91dyFEdMKUj_XU8CjUbh5EtdqjTR3CaAe=Bhii7dt3Q@mail.gmail.com>
Hi Emily,
On 16/03/2022 17:48, Emily Shaffer wrote:
> On Wed, Mar 16, 2022 at 10:38 AM Philip Oakley <philipoakley@iee.email> wrote:
>
>>> Interested?
>>> * Join the git UX Google group (https://groups.google.com/g/git-ux) 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).
Could you at least add a post to the group (doesn't need to be sent out)
to that effect, so that the UX of those that register is informative?
> 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.
I'd be reasonably happy with that. An initial event would help clarify
expectations.
> Hopefully that rationale clears up
> why you're unable to post or see anything there. :)
>
> - Emily
next prev parent reply other threads:[~2022-03-16 21:50 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 [this message]
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:
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=9bc6368d-cb14-8bd7-f58d-08087258311b@iee.email \
--to=philipoakley@iee.email \
--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).