From: "Michal Suchánek" <email@example.com>
To: Alice Merrick <firstname.lastname@example.org>
Subject: Re: Let's have a user experience workshop
Date: Wed, 16 Mar 2022 21:10:58 +0100 [thread overview]
Message-ID: <20220316201058.GI163591@kunlun.suse.cz> (raw)
On Tue, Mar 15, 2022 at 02:04:09PM -0700, Alice Merrick wrote:
> Hello Git,
> I’m doing a 20% project with the Git Core team at Google. I've been
> encouraged by Emily Shaffer and Jonathan Nieder to reach out to the
> Git community to help incorporate UX practices into the Git
> development cycle. My goal is to 1) gauge interest in improving Git's
> user experience and 2) recruit interested folks in organizing or
> attending a workshop where you can learn more about what UX is and
> discuss ways to bake UX into the process of making changes to Git to
> improve the experience for all users.
> Some additional context about me: I am a UX (user experience)
> professional at Google. I have experience applying UX and
> accessibility practices to developer tools for searching,
> reviewing, debugging code, etc. For the past couple years I’ve worked
> with the Golang project on their websites and helped set project
> priorities by collecting community feedback through their annual
> developer survey.
> * Join the git UX Google group (https://groups.google.com/g/git-ux) if you
> are interested in participating in an event.
> * 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?
next prev parent reply other threads:[~2022-03-16 20:11 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 [this message]
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
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: 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 \
* 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).