list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <>
To: Alice Merrick <>,
Subject: Re: Let's have a user experience workshop
Date: Wed, 16 Mar 2022 17:36:23 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Alice,

On 15/03/2022 21:04, 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[1] 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[2].
> 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 am interested in the UX from the perspective of Human Error and how we
form our mental models of the task at hand (e.g. see historic
discussions about the 'staging area').

Git does have rather a lot of non physical concepts to grasp, and now
that it's way beyond being just an SCM for the Linux kernel, the user
base has become rather diverse.

I'm a retired systems engineer who worked in defence electro-optics in
the UK. I am mainly on Windows.

> * 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)
> [1]
> [2]

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

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