[09:36] <noseasasi> buenos dias
[09:36] <jsgotangco> salut
[09:36] <noseasasi> pregunta sobre el ubuntu
[09:37] <noseasasi> salut
[09:37] <jsgotangco> no habla espanol
[09:37] <jsgotangco> hehe
[09:38] <noseasasi> ok
[09:38] <noseasasi> i am very bad enghish but i do
[09:38] <jsgotangco> lets try then :D
[09:39] <noseasasi> my xmms and beep player no play nothing
[09:39] <jsgotangco> hoary or warty?
[09:39] <noseasasi> i try others but is the same
[09:39] <noseasasi> warty
[09:39] <jsgotangco> hmmm
[09:40] <jsgotangco> tried alsamixer?
[09:40] <noseasasi> in the foros there are others whit the same trouble 
[09:40] <noseasasi> no i dont try
[09:40] <noseasasi> one moment...
[09:43] <noseasasi> one moment
[09:44] <noseasasi> no play.
[09:44] <noseasasi> the xmms is block
[09:45] <jsgotangco> i really dont know whats wrong at the moment
[09:45] <carlos> noseasasi: I think it's better if you ask at #ubuntu or #ubuntu-es
[09:45] <noseasasi> thanks i try others thinks
[09:45] <noseasasi> bye
[09:46] <carlos> noseasasi: but I think the problem is with esd sound daemon
[09:46] <noseasasi> gracias carlos ahura mismo
[09:46] <jsgotangco> carlos: he's in warty
[09:47] <carlos> noseasasi: you need to select the esd plugin output in xmms
[09:47] <noseasasi> thaks
[09:47] <carlos> noseasasi: de nada ;-)
[03:08] <Burgundavia> any body here?
[03:08] <Kinnison> Nup, we're all asleep
[03:08] <Burgundavia> any malone people here?
[03:08] <Kinnison> You want bradb and he's not here right now
[03:09] <Kinnison> or bjornt
[03:10] <Burgundavia> hmm
[03:19] <Burgundavia> hey bradb, just the man I was looking for
[03:19] <bradb> Burgundavia: hi
[03:20] <Burgundavia> I have some ideas/thoughts regarding malone
[03:20] <Burgundavia> is now a good time to hear them?
[03:21] <bradb> Burgundavia: sure
[03:22] <Burgundavia> alright then
[03:22] <Burgundavia> User Prefs
[03:22] <Burgundavia> -Email Prefs
[03:22] <Burgundavia> --Merge the validate with upper section, as I would expect all my emails to be listed, with a check box column listing them as validated.
[03:38] <bradb> Burgundavia: sorry dude. was reading email and came back to the IRC window to see that our internet connection had flaked at the router. :/
[03:38] <Burgundavia> np
[03:38] <Burgundavia> User Prefs
[03:38] <Burgundavia> -Email Prefs
[03:38] <Burgundavia> --Merge the validate with upper section, as I would expect all my emails to be listed, with a check box column listing them as validated.
[03:46] <bradb> Burgundavia: ok, so are you familiar with FOAF?
[03:46] <bradb> Burgundavia: FOAF, i.e. Friend of a Friend, i.e. the part of Launchpad you see under /people.
[03:47] <Burgundavia> a little
[03:47] <bradb> Burgundavia: If you're suggesting a Malone improvement, it's probably something that you're seeing under /malone.
[03:47] <Burgundavia> I remember hearing a little at mataro
[03:47] <Burgundavia> ok
[03:47] <Burgundavia> then I do have stuff for that to
[03:47] <bradb> Burgundavia: If you're suggesting an improvement about how to better interact with your personal prefs, accounts, etc. that's a FOAF thing.
[03:47] <Burgundavia> ok
[03:47] <bradb> our FOAF guy is salgado, who doesn't appear to be around atm.
[03:48] <Burgundavia> I will note that
[03:48] <Burgundavia> for malone
[03:48] <bradb> Burgundavia: ok, so for the Malone-specific stuff, I'd be interested to hear about how you think it can be improved.
[03:48] <Burgundavia> main malone screen
[03:48] <Burgundavia> -text jammed together when view of ff 1.0.1
[03:48] <Burgundavia> -seperation between product and package?
[03:48] <Burgundavia> -you have lots of screen realestate, use it
[03:48] <Burgundavia> respond to 1 & 2 and then I will discuss 3
[03:49] <bradb> can you give me a URL for #1? i'm not sure what you're referring to, exactly.
[03:49] <Burgundavia> https://launchpad.ubuntu.com/malone
[03:49] <Burgundavia> should I show you a screenshot
[03:50] <Burgundavia> yes I am running Ubuntu Hoary
[03:51] <bradb> oh, yes, I'm aware of that main screen ugliness. it was very recently introduced. ;) we've got some hardcore UI hacking happening in .ch at the moment though, so expect that to improve in the next week or two, i would guess.
[03:52] <bradb> for #2, what's your question, exactly?
[03:52] <Burgundavia> ok
[03:52] <Burgundavia> not really clear in my mind what exactly a product is
[03:53] <bradb> Burgundavia: a product is the source code as it exists outside of any given distribution.
[03:53] <Burgundavia> ah
[03:53] <Burgundavia> there is no mention of source code in there
[03:54] <Burgundavia> I guess that finishes the main screen
[03:54] <bradb> Burgundavia: e.g. Mozilla Firefox.
[03:54] <Burgundavia> ok
[03:54] <bradb> Burgundavia: It's the "upstream" to the source package in a distribution.
[03:54] <Burgundavia> I see now
[03:54] <bradb> it's the place where most of the bugs actually get /fixed/ :)
[03:54] <Burgundavia> hmm
[03:54] <Burgundavia> I wonder how that could be made clearer?
[03:55] <Burgundavia> I guess the other issue is
[03:55] <bradb> Burgundavia: the word "product" is sort of confusing, especially because we sometimes use "upstream" and sometimes use "product", and it's still not entirely clear which one is the best term.
[03:55] <Burgundavia> are you planning on have seperate "main" pages
[03:56] <Burgundavia> product is nice because upstream doesn't have much traction outside the dev community
[03:56] <Burgundavia> however, the confusion in the same community over product vs package is also bad
[03:56] <Burgundavia> same == not devs
[03:58] <bradb> ok, so first, separate "main" pages...for...?
[03:58] <bradb> every "context" has its bug tracker.
[03:58] <Burgundavia> for seperate use cases
[03:58] <Burgundavia> developer, end user, etc.
[03:59] <bradb> oh, not sure yet. i think it's expected that the UI will grow into something that looks a bit different depending on how you interact with the system though (so, you'd have different options to select if you're a sourcepackage maintainer v.s. an end-user v.s. a distro release manager, etc.)
[04:00] <Burgundavia> ok
[04:01] <Burgundavia> as the current does everything, doesn't really work
[04:01] <Burgundavia> but if there is ui love happening, sounds good
[04:01] <Burgundavia> onwards then
[04:01] <Burgundavia> is there work happening on the bug screen ui?
[04:03] <bradb> Burgundavia: always. :)
[04:03] <Burgundavia> ok
[04:04] <Burgundavia> my thoughts
[04:04] <Burgundavia> type ahead for distro, ala the current bugzilla
[04:04] <bradb> Burgundavia: where?
[04:04] <Burgundavia> possibly with the current stable as the top one
[04:04] <Burgundavia> sorry, enter new bugs screen
[04:05] <Burgundavia> which would elminate the ugly popup
[04:05] <bradb> Burgundavia: https://launchpad.ubuntu.com/malone/distros/ubuntu would be the page on which you'd file distro bugs (i.e. /malone/distros/<distroname>)
[04:05] <Burgundavia> ok
[04:06] <Burgundavia> is the other bug screen going away entirely then?
[04:06] <bradb> but yes, we're aware of the less-than-ideal issue of using a popup to select one item from a list of dozens, hundreds, or even thousands of options. we brought in a guy from the Mozilla project to help address that (for more than just selecting distros)
[04:06] <Burgundavia> you probably can get away with that
[04:06] <bradb> yeah, the filing a bug screen that makes you type the distro will probably disappear shortly
[04:06] <Burgundavia> link to already reported bugs on that page currently goes to main screen
[04:06] <Burgundavia> on Ubuntu page too
[04:07] <Burgundavia> blue sky about that: type ahead for summary, ala firefox with box beneath showing possibly related bugs
[04:08] <bradb> Burgundavia: Interesting. We've spec'd a UI for showing you possibly related bugs, but not using Google Suggest style widgets (yet.)
[04:09] <Burgundavia> dhtml+js is very very cool
[04:12] <Burgundavia> my todo list is broken if you have nothing assigned to you
[04:13] <Burgundavia> just shows all bugs
[04:15] <bradb> urgh, yeah, the searching and those quick search links has broken in some of the bug filing screens. I'll sort that out in due course (i think there's already a bug filed for one of those problems, but if you can't find a bug filed for something that you find broken in Malone, bug reports are the best way to ensure that I don't forget to fix something. :)
[04:15] <bradb> s/bug filing screens/bug listing screens/
[04:15] <Burgundavia> another crazy idea
[04:15] <Burgundavia> sub todo lists for bugs
[04:15] <Burgundavia> some bugs have several things that need to be done
[04:15] <Burgundavia> so create a subtodo list
[04:15] <Burgundavia> thus if the bug was go to work
[04:16] <Burgundavia> subtodo list 1 would be: get out of bed
[04:16] <Burgundavia> etc.
[04:17] <Burgundavia> Kinnison: what do you think of my idee?
[04:18] <Burgundavia> hmm
[04:18] <Kinnison> why not just file bugs for the subtasks and make the primary bug depend on them -- or else have a proper todo/task manager which can relate several tasks to the same bug
[04:18] <Burgundavia> hey that works too
[04:18] <Burgundavia> but what if people file (foo is broken)
[04:19] <Burgundavia> when it requires bar, baz, and bat to be fixed?
[04:19] <Burgundavia> and each is a lengthy task?
[04:21] <bradb> Burgundavia: we're planning on building a todo app, which is the thing that will manage bug dependencies, i believe.
[04:21] <Burgundavia> bradb: hey, cool
[04:21] <Burgundavia> that about exhausts my imm. thoughts
[04:21] <Burgundavia> I am certain I will have more less than wonderful ideas soon
[04:22] <bradb> Burgundavia: the good news is, we're on it. pretty much everything you've said we've already either spec'd out (but not yet scheduled for implementation) or can at least see on the horizon, and have already done some thinking about.
[04:22] <Burgundavia> great
[04:22] <Burgundavia> isn't being behind the ball great?
[04:23] <bradb> :)
[04:24] <daf> Burgundavia, the .desktop file fascist :)
[04:24] <Burgundavia> daf: noticed that did you?
[04:24] <Burgundavia> daf: That is my todo list
[04:24] <daf> :)
[04:25] <Kinnison> Burgundavia: we get told for every new malone bug
[04:25] <Burgundavia> I have now filed exactly one half the bugs in ubuntu
[04:25] <Burgundavia> Kinnison: by what means? ircbot?
[04:25] <daf> going to need to give dilys full multi-channel support soon
[04:26] <Kinnison> Burgundavia: yeah
[04:26] <Kinnison> daf: yeppers
[04:26] <Burgundavia> in #canonical
[04:26] <Burgundavia> ?
[04:26] <Kinnison> naah, in a launchpad channel
[04:26] <daf> the sekrit one
[04:26] <Burgundavia> ah
[04:26] <Kinnison> s00pah s3kr1t
[04:27] <Burgundavia> now if only I can get rights to assign them
[04:27] <Kinnison> hey salgado
[04:27] <Burgundavia> salgado: you do FOAF stuff right?
[04:28] <salgado> Burgundavia, yeah, I do
[04:28] <Burgundavia> I had a though regarding the email pref stuff
[04:29] <Burgundavia> merge the validation stuff into the main section listing emails
[04:29] <Burgundavia> and make certain that all emails on record are listed
[04:32] <salgado> Burgundavia, I don't understand exactly what you want to do. 
[04:32] <salgado> would you mind mailing it to me?
[04:32] <Burgundavia> sure
[04:32] <salgado> I'm in the middle of moving all office stuff to a new building
[04:32] <Burgundavia> I will email you an edited screenshot as well
[04:32] <salgado> have *lots* of stuff to fix here and will not be available on irc
[04:32] <salgado> Burgundavia, that would be really good. thank you
[04:33] <Burgundavia> np
[04:37] <dreamcatcher> in case nobody noticed, roseta seems unusable right now *wink*
[04:38] <daf> we know, we have a fix, and we're hoping it will be deployed tomorrow
[04:39] <dreamcatcher> kewl, tks
[05:16] <Burgundavia> I am in the launchpad database twice
[05:16] <Kinnison> Me too
[05:16] <Burgundavia> hmm
[05:16] <Kinnison> When the people merging stuff is done we can fix it
[05:17] <Burgundavia> in addition, when I try and edit the task status of a bug, I get a system error
[05:17] <Burgundavia> bradb: ping
[05:20] <bradb> Burgundavia: hi
[05:21] <Burgundavia> bradb: attempting to update the severity of the bugs produces a system error
[05:21] <bradb> Burgundavia: ok, can you report a bug for that please? i'll forget otherwise.
[05:21] <Burgundavia> ok
[05:22] <Burgundavia> and another thought about ui's
[05:22] <bradb> https://launchpad.ubuntu.com/malone/products/malone
[05:22] <Burgundavia> clicking to get the task is, IMHO, not very discoverable
[05:23] <bradb> Burgundavia: yeah, we're trying to think of a better way to handle that row clicking, how to go directly to the task vs. the main bug page, if those might even become one page, etc.
[05:24] <Burgundavia> bradb: it took me about 5 minutes to clicking to figure that one out
[05:24] <Burgundavia> because clicking else where in the same row takes you some where completely different
[05:25] <Burgundavia> the highlighting shoudl only be for the package when you go there, and the task when you go there
[05:25] <bradb> oh, you mean on the bug main page you're clicking
[05:25] <Burgundavia> yes
[05:25] <bradb> (URLs help keep this stuff clear)
[05:25] <Burgundavia> yes
[05:26] <Burgundavia> https://launchpad.ubuntu.com/malone/bugs/259
[05:26] <Burgundavia> the buttons at the top (bugs, translations, bounties) - those are launchpad bugs?
[05:28] <bradb> Burgundavia: that's some UI design reworking. i think that when those links work correctly, they'll take you to the respective views of whatever thing you're looking at (the translations in Ubuntu, the bugs in Ubuntu, the bounties in Ubuntu, etc.)
[05:29] <Burgundavia> bradb: yah, cause they are borked right now
[05:30] <Burgundavia> bradb: what does status accepted mean?
[05:43] <bradb> Burgundavia: the opposite of rejected.
[05:43] <Burgundavia> bradb: where should new bugs stay at accepted or new?
[05:43] <Burgundavia> does accepted mean they are a bug?
[05:43] <bradb> new bugs are New.
[05:44] <Burgundavia> ok
[05:44] <Burgundavia> and once they are verified to be a bug, then they are accepted?
[05:45] <bradb> yeah. to be honest, we don't have enough statuses yet (IMHO) to accurately describe the state of a bug task, so it's a bit ambiguous, atm.
[05:45] <Burgundavia> ok
[05:45] <Burgundavia> I remember the discussions at Mataro about that
[05:45] <bradb> e.g. "rejected" can mean, wontfix (for which we have a priority instead), notabug, maybe worksforme, etc.
[05:46] <Burgundavia> I am now about to make a dumb statement
[05:46] <Burgundavia> why do you have priority and severity?
[05:46] <Burgundavia> is low severity item not high priority?
[05:47] <bradb> priority describes how important it is to fix this bug
[05:47] <bradb> severity describes how big of an impact the bug has on the users affected by it
[05:48] <Burgundavia> hmm
[05:48] <Burgundavia> I guess so
[05:49] <Burgundavia> like I said, I was about to say something stupid
[05:49] <bradb> Burgundavia: think about it. they is a different set of criteria to decide how important it is to fix a bug, vs. describing the impact that a bug has on the users affected by it.
[05:50] <Burgundavia> ya