[TYPO3-hci] Extension Manager - Usability

[Sudara Williams]

My thoughts:

It would be a mistake to treat Usability as a separate 'project' from Core or any other project - it needs to be integrated into every project and become a part of the process of development.

If there is a usability issue/enhancement with TER, it should be listed as a problem with TER, because it IS a problem with TER. 

Keeping the usability ideas and the enhancements separate would lead to more of the same problem - poor usability. Designing and Usability testing needs to become a way of life in the current dev cycle, and not something to think about after the fact or separately.

I like the wiki idea - it is already there, lets fill it up.

It seems like we really need:

 a) for small stuff: patches to various projects and submit them to the correct bugtracker
 b) for big stuff and future development: there is no way around working with the willing developers on making their features more usable and sexy

We need to have the usability conversations WITH the developers. We should have the conversations there, post the notes there, talk about the different options there, invite them to participate, and asking for feedback for what is possible. 

There is nothing to fear - if you do not program, post up your PSD, or describe the interaction you desire.

We need to work hand in hand with the folks who are committing changes daily. Eventually, after 'proving' oneself to the Core team (via patches), it would be useful to have a Usability freak who is trusted with commit rights to make this process smoother and even more ideally, be a part of feature planning.

my thoughts!

greetings from Innsbruck!
Sudara


-----Original Message-----
From: typo3-team-hci-bounces at lists.netfielders.de on behalf of Andreas Balzer
Sent: Tue 4/10/2007 7:00 PM
To: typo3-team-hci at lists.netfielders.de
Subject: Re: [TYPO3-hci] Extension Manager - Usability
 
Benjamin Mack schrieb:
> Hey Andreas,
> 
> Andreas Balzer wrote:
>> right. What do you think about, if we ask for a project in bugtracker, 
>> which would be optimal for planning all that stuff..
> 
> I would rather do this:
> * Create a new wiki page "Usability Tasks", where we compile the 
> existing ideas into topics with real tasks and subtasks, so we can 
> figure out a way, what can be done for 4.2 or for 5.0.
> * Small usabiltiy no-brainers (as on the wiki page) are often connected 
> to the bugtracker, we could search for them and get them fixed.
> 
> As the progress of the HCI-group is very little right now (at least 
> that's my impression), we should use this new Usability Task wiki page 
> as a list to see what is actually going on in terms of coding and 
> realization right now. I have heard of the new topapps etc. proposals 
> and we have so many good ideas in our hands but what's the status of 
> them being really finished?
> 
I would use a bug tracker project for this (and I have requested one), 
as it is ideal to keep track about multiple tasks (bugs) with multiple 
persons (reporters) and it also offers a discussion plattform (notes). 
But... As the T3 wiki is conected to the bugtracker, we can use the bug 
reports and fill a wiki page with those things. So lets use a 
combination of both :)

Andreas
_______________________________________________
TYPO3-team-hci mailing list
TYPO3-team-hci at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5062 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-hci/attachments/20070411/9bc78878/attachment.bin