Re: [orion-dev] User Experience Call

[Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>]

I like the classification. Your email made me think of this list, which includes a few more:

1 - new users/kick the tires
- be inviting/pretty, welcoming/guiding.
- make it easy to create some content, edit, try it out
2 - non-Orion developers using JS or some other language.
- language tooling
- site deployment flexibility
3 - Orion contributors who want to submit features/fixes to Orion
- git workflows that make it easy to clone and merge/keep up with mainstream
- accepting contributions workflow so that it's easy for committers to take the work in
4 - Orion committers
- git workflows that make it easy to work in topic branches, merge, etc
- self hosted sites
5 - Orion integrators
- localhost scenarios
- code consumption/decoupling our services
- tons of examples

Perhaps #3 and #4 could be collapsed, but the git workflows are certainly different for each.
John did some work about a year ago on a persona list [1] (where user #4 was named Boris, user #2 might be Nathan)...
One thing that might be useful as we prioritize UX issues is to always track which user (whether named or not) we are doing the work for. If we focus on a particular set of workflows that apply mostly to one kind of user, it should be intentional...

[1] http://wiki.eclipse.org/Orion/Use_Cases

Boris Bokowski ---05/01/2012 07:57:30 AM---+1 to what John said. I would recommend you look at two classes of users for which the UX can be

From: Boris Bokowski <bokowski@xxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 05/01/2012 07:57 AM
Subject: Re: [orion-dev] User Experience Call
Sent by: orion-dev-bounces@xxxxxxxxxxx

---

+1 to what John said.

I would recommend you look at two classes of users for which the UX can be improved:

1. Regular users who get an account on orionhub.org to kick the tires. John's last sentence ('Generally...') sums up nicely what needs to be improved.

2. Potential adopters of (pieces of?) the technology who do a local install of Orion and need an easy way to set it up, and configure it with projects they are working on (hence point 0 from John).

I would have liked to join the call but have to get back onto my feet first. :-)

Will you be posting notes?

Boris

On Apr 28, 2012 4:35 PM, "John J Barton" <johnjbarton@xxxxxxxxxxxxxxx> wrote:

On Fri, Apr 27, 2012 at 3:43 PM, John J Barton <johnjbarton@xxxxxxxxxxxxxxx> wrote:
On Fri, Apr 27, 2012 at 1:41 PM, Simon Kaegi <Simon_Kaegi@xxxxxxxxxx> wrote:
> Hi all,
>
> I'd like to hold a call next Tuesday at 12pm Eastern time (e.g. same time of
> day as our regular Thursday call) to discuss user experience as well as
> ideas around theming. For an initial meeting Susan suggested bringing "a
> list of the 10 things that bug you the most as a user"

My list in case it might inspire discussion:

0. Confusion. Constantly decoding URLs with ids instead of project names.
 

1. Waiting. eg git repositories page.
2. Scrolling. eg git repositories page or plugins page
3. Flashing. Many pages do large repaints for small actions.
4. Overwriting. Accidentally edit a file in two tabs, you lose.
5. Cursing. Search then click the breadcrumb to go to a directory. It
searches instead.
6. Debugging. well, no debugging of course.
7. Pondering. Did it work? Why FAILED? Oh, I need to look over there
to see the message.

Generally I like to see the UI be more compact, with smaller icons and
less redundant text, update in-place rather than by-page, provide
messages at the point of interaction, and be more workflow focused and
therefore less uniform.

jjb

>  and I think that's
> fine for a first call. Please feel free to ping additional ideas on the
> list. User experience is incredibly important and depending on the need this
> call might be made a regular bi-weekly chance to discuss.
>
> I unfortunately do not have an Eclipse bridge number at the moment but am
> getting help from the Foundation to set things up. I will send an update
> either before the call or failing that we can use my personal bridge.
>
> -Simon
>
>
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orion-dev
>


_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev