=== Ursinha-bbl is now known as Ursinha === ian_brasil_ is now known as ian_brasil === jjohansen is now known as jj-afk === head_v is now known as head_victim === Ursinha is now known as Ursinha-afk === bazhang_ is now known as bazhang === jj-afk is now known as jjohansen === jussi01_ is now known as jussi [09:03] Oh a netsplit! === jjohansen is now known as jj-afk === hyperair is now known as Guest68417 === bilalakhtar_ is now known as bilalakhtar [12:50] mpt: what do you think about http://www.foopics.com/showfull/c7e1ce704b9de523e51ec5d4a3569003 [12:52] thorwil: do you know http://picasaweb.google.com/100804433705878937883/Mockups# – what about them? [12:54] JanCBorchardt: yes, i know them. associates the transport controls more with the track, less with the player. smaller targets, further away from the menu icon [12:56] thorwil, it reduces the number of visible columns, which is good. The playback control layout is consistent with Rhythmbox and VLC, but inconsistent with Banshee, Totem, Decibel, and Exaile. [12:56] JanCBorchardt: my actual thoughts are http://thorwil.wordpress.com/2010/08/06/ayatana-sound-menu-2/ but here i tried to change only was has chances of being accepted [12:57] mpt: it follows that the control layout is inconsistent between those you listed ... [12:57] JanCBorchardt, ah, I was trying to find those mockups yesterday [12:57] thorwil, yes :-) [12:57] thorwil: ah right, now I remember reading your post [12:57] add Listen to the second list [12:57] mpt, me too ;) [12:58] mpt: there's a DIN/ISO-somthing norm about transport control layout [12:58] weehu, it‘s aday :) [12:58] thorwil, seriously? [12:59] JanCBorchardt: hey :) [12:59] mpt: yes. i might be able to dig it up, but then again, in a case like this, making play/pause mots easily accessible beats much everything else, i'd say [12:59] yeah [13:00] which is one reason i placed them above track info [13:00] so what's happening? [13:00] all righty then [13:01] Is anyone else here going to UDS? [13:01] \o [13:01] ah, of course [13:01] i was on the standby-list, so not that of course ;) [13:02] Of course as in, I should have known that [13:02] So there are a few UX-related sessions registered so far [13:02] https://blueprints.launchpad.net/ubuntu/+spec/multimedia-design-n-science-of-colour [13:03] https://blueprints.launchpad.net/ubuntu/+spec/multimedia-design-n-type-in-the-desktop [13:03] https://blueprints.launchpad.net/ubuntu/+spec/other-design-n-research-to-design [13:03] https://blueprints.launchpad.net/ubuntu/+spec/multimedia-design-n-china [13:03] https://blueprints.launchpad.net/ubuntu/+spec/design-n-china-follow-up [13:03] https://blueprints.edge.launchpad.net/ubuntu/+spec/other-design-n-ayatana-update <- that one's about us [13:03] https://blueprints.edge.launchpad.net/ubuntu/+spec/other-design-n-design-in-open-source <- so is that [13:04] https://blueprints.edge.launchpad.net/ubuntu/+spec/other-design-n-feedback [13:04] https://blueprints.edge.launchpad.net/ubuntu/+spec/other-design-n-community <- that one's about us too [13:05] Probably there are more coming [13:05] cool [13:06] Oops. Andchat didn't tell me anyone was talking in here. Sorry I'm late. [13:06] hi godbyk [13:06] broken link: https://blueprints.launchpad.net/ubuntu/+spec/multimedia-design-n-china [13:06] hey, mpt [13:06] thorwil: https://blueprints.edge.launchpad.net/ubuntu/+spec/design-n-china [13:06] mpt: thanks! [13:06] I think aday might like to call for help with the HIG now :-) [13:07] yep [13:07] what about remote participation? I will not be in Florida === wers-brb is now known as wers [13:07] help!!! [13:07] lol [13:08] before that - i want to ask - which of those sessions are most relevant for gnomey folks? [13:08] JanCBorchardt, there will almost certainly be streaming audio and IRC for each room. I don't see any details on that at the moment, but subscribe to if you haven't already [13:09] in particular - is the fonts session particularly related to the ubuntu font, or is it more generic than that? [13:09] mpt, cool. thanks [13:09] aday, probably the design-n-community and design-in-open-source ones [13:09] I won't be at UDS (I'm a poor grad student and wasn't sponsored), but hope to attend some of the sessions remotely again. [13:09] aday, the font one is about using different fonts and styles in different places, so it may affect GTK. [13:09] mpt: thanks [13:10] i'll maybe send a mail round to advertise those [13:10] andreasn: ping ;) [13:11] so, about the hig - we're trying to get the hig effort back up and running again [13:11] godbyk: same here ;) [13:11] i'm organising a meeting of the interested parties to plan what needs to be done [13:11] JanCBorchardt, sorry, busy requesting a fdo account :) [13:12] so if anybody is interested in that, let me know when you're available [13:12] i'm hoping to try and decide on the format and priority content at that meeting [13:12] andreasn: Ayatana meeting now, just so you know :) [13:12] aday: what meeting are you organizing? [13:12] godbyk, for the GNOME HIG [13:12] godbyk: human interface guidelines 3.0 [13:12] yes, I know, trying to do 10 things at the same time :) [13:13] sorry for that [13:13] Ah, gotcha. Yeah, I'd love to attend if I can. [13:13] sorry, i should have given more background - we're re-writing the HIG :) [13:13] aday: I've looked at the pattern library that was started. I like the idea. [13:13] JanCBorchardt, was it something specific you wanted to ask me? [13:14] andreasn: no [13:14] godbyk: cool. comments and feedback are welcome [13:14] anyway, I'm with you in both soul and flesh now :) [13:15] we're going to need help with writing and editing, so if anybody wants to have a go at writing a pattern that would be great [13:16] and let's figure out how we're going to do it [13:16] wers: yes, that's the first step [13:16] which we'll hopefully be sorting out soon [13:17] i'll be updating the gnome usability list - so watch that space if you're interested [13:17] godbyk: remote participation for UDS: http://uds.ubuntu.com/participate/remote/ [13:17] what has been the format for the HIG so far? docbook? [13:18] thanks, JanCBorchardt [13:18] thorwil: depends what you mean by format... but yes, i think it's docbook [13:18] we still need to decide on format, so any comments there would be good [13:19] yepyep [13:19] so that's one action item [13:20] everyone think of what the format should be [13:20] possibilities include: wiki, CMS, mallard... [13:20] let's report back next week or maybe on the HIG meeting [13:20] wers: good idea [13:21] btw, did everyone here get their ayatana-ux membership expiration date extended? [13:21] ok [13:21] I extended everyone's this morning [13:21] except people who are leaving anyway [13:21] I'm not sure if I got the extension [13:21] mpt: ah, cool. just checking. [13:23] next week, let's have a secretary to write down the minutes then send the minutes to the list and/or post on the wiki [13:23] * thorwil is reminded of the supermarket where they would take the meat out of the packaging, turn it around to make it look fresh again, repackage and relable. regarding expiration date [13:23] it's time to be efficient [13:23] if only i had enough time to be efficient :) [13:23] I can be the first secretary. let's take turns [13:23] wers: that's easy enough. though lately, nothing much has been happening at many of the meetings. it's easy to read the 3-4 line exchanges in the logs. :) [13:24] godbyk, let's fix that by having a clearly defined agenda [13:24] wers: also a good idea. [13:25] and set the agenda ahead of time [13:25] let's see now what next week's agenda will be. I found one. it's to report back our thoughts on the HIG [13:26] is there anything we should do in preparation for UDS? [13:26] Adding ideas to the whiteboards of those blueprints would be useful, I think [13:27] wers: did you catch mpt's agenda item? [13:27] godbyk, nope. what was it? [13:27] Adding ideas to the whiteboards of those blueprints would be useful, I think [13:28] ok [13:28] That wasn't an agenda item, I was just answering godbyk's question [13:28] ooh. ok [13:28] does anyone of you not have access to the ayatana-ux repo on gitorious yet? [13:28] godbyk, did you ever get time to write up a user testing template? [13:28] script template, I mean [13:28] mpt: A user testing template? [13:29] We talked about doing that a couple of months back. [13:29] oh boy. [13:29] I'm going to guess 'no', then. :-) [13:29] ok [13:29] Is it something you'd like to do? [13:29] Sure. What kind of user testing? [13:30] (Most of the scripty stuff I have to deal with is related to bureaucratic IRB things like informed consent.) [13:30] The sort where you ask someone to try doing something in Ubuntu, and sit and watch them without saying anything [13:30] (try doing something specific, I mean) [13:30] Right. [13:31] So you want some boilerplate 'we're testing the software, not you..' intro type stuff? [13:32] yes [13:32] exactly [13:32] Gotcha. Yeah, I can whip up some of that. [13:32] Thank you. [13:32] godbyk: dunno whether this is useful: http://live.gnome.org/Pongo/Tutorial [13:32] i wrote it a while ago... it's not particularly complete [13:33] Then maybe next week we can discuss how to get people running tests of their own. [13:33] aday: cool. [13:33] (Canonical's Charline Poirier is busily running a user test of Unity right now.) [13:33] mpt: Yeah, it'd be great if we could get people running some of their own tests. [13:33] For a lot of usability testing, you don't need huge sample sizes, etc. [13:34] ok [13:34] Anything else? [13:36] nothing's coming to mind. [13:37] ok, thanks everyone [13:37] thanks, mpt! [13:38] see you next week :) [13:39] tried to write minutes for today. we can use this as a template https://wiki.ubuntu.com/Ayatana-UX/Minutes/20101014 [13:40] thorwil, is yours, or is it from someone else? [13:40] mpt: mine [13:41] ok, I'm linking to it from the spec [13:41] I know I missed a lot for today's minutes. feel free to edit the page [13:41] mpt: cool. i will not other bringing it up on the list, then [13:41] bother, even [13:42] godbyk: mpt: letting people run their own tests is great. Any way I could help? [13:42] It'd be useful to get some feedback from developers on the idea. [13:42] What questions do they have about usability testing that we can answer? [13:43] What information/resources do they need to be able to run their own tests? [13:43] like what questions to they have, what problems do _they_ see for them (like decisions) [13:43] excellent idea [13:43] In general, how can we help them? [13:44] Just writing some generic intro text and tossing it out there won't do much. [13:44] The developers would be the users of this process, so research them like any other user research [13:44] towards a software life-cycle model with integrated globally distributed testing ^^ [13:45] yep, intro text is not the important thing, besides it is already there [13:45] You could also explore the general impressions that developers have about usability testing. What do they think of it? Are they interested in learning how to do it? [13:45] aday's pongo testing wiki page is pretty good, really. === nakkel is now known as Nakkel [13:46] godbyk: when you say "what info do they need to be able to run their own tests?" do you mean developers? [13:46] JanCBorchardt: yes. [13:46] godbyk: I would definitely _not_ advise having developers test their own apps [13:47] they need to be educated about UX and design stuff, but they should not do the tests [13:47] It is crucial for testing that you are not biased. [13:48] testing should definitely be organized by us, as I see it. [13:49] I agree about the bias and -- while it's certainly not optimal -- I think that almost any usability testing is better than none at all. [13:49] inner circle user/contributors of projects might be in a good position to do testing [13:49] being not immersed in implementation, but having a good link to developers [13:50] enough enthusiasm and good knowledge of the project [13:50] for the most part, you just have to try to keep your mouth shut, not grab the mouse away from the user, and try to avoid strangling them. :) [13:51] being slightly masochistic helps, too. [13:51] isn't the really hard part drawing conclusions, getting to solutions, anyway? [13:53] For really fine-tuned detail stuff, it's more difficult to analyze the results. But for the big problems.. well, they'll be apparent after you've seen a few people trying to use your software and stumbling in the same places. === ian_brasil_ is now known as ian_brasil === ian_brasil_ is now known as ian_brasil === Ursinha-afk is now known as Ursinha === ian_brasil_ is now known as ian_brasil === mohi1 is now known as Mohan_chml === xfaf is now known as zul [15:35] godbyk, thorwil: sorry I am answering late – just be sure I read and agree with your replies. :) === jorge is now known as jcastro === james_w` is now known as james_w === MichealH is now known as MichealH-Test === MichealH-Test is now known as MichealH === jj-afk is now known as jjohansen === Andre_Go` is now known as Andre_Gondim === cjohnston_ is now known as cjohnston === xfaf is now known as zul === JanC_ is now known as JanC === MichealH is now known as lassemon === lassemon is now known as MichealH === maco2 is now known as maco === oubiwann is now known as oubiwann-away === oubiwann-away is now known as oubiwann