list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <>
To: Emily Shaffer <>
Cc: Alice Merrick <>,
	Git List <>, David Aguilar <>
Subject: Re: Let's have a user experience workshop
Date: Sun, 15 May 2022 09:17:53 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

(bcc-ing workshop attendees again)

Emily Shaffer wrote:
> On Mon, May 9, 2022 at 8:35 PM Jonathan Nieder <> wrote:

>> 1. Continuing the conversation
>> I and some others (e.g. David, cc-ed) ended the workshop wanting to
>> discuss a little more --- when deciding (1) what to work on and (2)
>> settling on a design for that work, what has worked well for us in the
>> past?  What didn't work?  What research methods have we tried?  What
>> would we like to try?  We mentioned wanting to continue that
>> discussion on-list, so trying that now. :)
> For all 4 of the above - I wonder whether it really makes sense to try
> and organize those things asynchronously. If I'm being honest, what
> I'd much prefer would be a monthly-or-so working group meeting with
> other folks interested in performing research, making recommendations,
> learning how to improve Git's UX, etc. I'd absolutely make time to
> attend such a thing, and I believe it would be the easiest way to
> organize research and concert our efforts. Would other folks be
> interested in showing up, too?

Interesting!  I'd also enjoy a meet-up, but e.g. for "3. Testing ideas
with users" I would find it worrisome if getting user input would
require reviews on a given patch stalling out until the next monthly
meeting.  (Reviews are already slower than they should be as it is!)
I don't know that that's what you meant to suggest; I'm just aiming to
understand what you mean about the "all 4" above.

> I'd envision it as something between a working group and a book club -
> we could learn different aspects of UX design and research, and apply
> them in various ways. It might be nice to have Alice along for at
> least the first couple of sessions to answer questions and help us
> learn in a bit more targeted direction than we got at the workshop.

Sounds nice to me.  If others turn out to be also interested, then
what would be the next step for making that happen?


  reply	other threads:[~2022-05-15 16:18 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
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 [this message]
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).