/srv/irclogs.ubuntu.com/2007/06/01/#ubuntu-meeting.txt

manchickenSure.12:17
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
LureRiddell: ;-)12:17
LureRiddell: and we have agenda full of artwork and usability ;-)12:18
manchickenI'm proposing a very simple, easy to understand program where VERY common issues are listed, and with one click you could solve the problem.12:18
_StefanS_help center thingy..12:18
manchickenNot really that...12:18
mhbmanchicken: I've been thinking about this app, and I'm not sure whether it will be as useful as desired12:18
Luremanchicken: I like the idea to not need console, but I do not think this should be central place for fixes - rather applications should cope with such cases better12:19
mhbI'm with Lure on that one12:19
Lurefor your example: adept should propose to run dpkg-configure12:19
manchickenLure: Sure.12:19
mhband it's hard to guess what problems will be the most common for a release12:19
fdovingmhb, lure, that's fine, applications don't cope, then what do we do?12:19
Hobbseecertainly the adept stuff is12:19
Lureotherwise it looks like we have broken system that needs fixes ;-)12:19
fdovingfix aall applications?12:19
manchickenLure: My biggest concern is that in the short term that is less likely to take hold.12:19
DaSkreechLure: I think that what he wants is for the person to not touch command line12:20
manchickenAnd while we're waiting for these features, users are left being told to hit the command line.12:20
_StefanS_you got all sorts of issues keeping the common issues list updated12:20
Hobbseebut a generic "fix my wifi" is a bit....well, if it's using knetworkmanager - often that requires killing NetworkManager, starting it again, then doing other buggery.  also, you'd need root for that12:20
Luremanchicken: if we can implement fix in menu, we can also add it to application effected, right?12:20
Riddellit wouldn't be hard to change adept to offer that fix(/hack) as an option12:20
manchickenI'm not talking about a permanent fix, or a once and for all fix.12:20
LureRiddell: really? couldn;t notifier do that?12:20
manchickenI'm talking about something that we can put into place where we can have short-term fixes until the real fix is present.12:20
RiddellLure: spose so12:21
DaSkreechmanchicken: do you think this will come across as a We know this is broken we aren't going to fix it here is a band aid ?12:21
Luremanchicken: my concern is that it would look worse than it is12:21
JucatoI suggest that this one fix app would still be able to display terminal output, like what Adept has (can't remember the term for it)12:21
manchickenLure: I think writing a collection of well-presented shell scripts will be easier than making knetworkmanager reload network interfaces and renew DHCP leases.12:21
Luremanchicken: true it would help for user with problem, but people just explore the menu and try to run stuff to try it out12:21
=== ompaul [n=ompaul@freenode/staff/gnewsense.ompaul] has joined #ubuntu-meeting
tomaDaSkreech++12:21
=== ryanakca agrees with DaSkreech
manchickenDaSkreech: I don't think people will see it that way.  Instead I think people will realize that there's something wrong when they are required to go to the command line.12:22
Riddellanother problem is a lot of issues would only come to light after release12:22
manchickenLets face it, if a user has to go to the command-line to fix a problem, that is a failure on our part.12:22
HobbseeDaSkreech: we just did that for the unmount dialog.  *shrug*12:22
manchickenThis is a desktop distribution.12:22
Luremanchicken: I know that some issues are more "common", therefore workarounds are fine12:22
manchickenUsers should be able to do everything without command-line interaction.12:22
DaSkreechmanchicken: I'm behind you for that. But what's the main problem we are trying to solve12:22
Luremanchicken: I just do not want to have central place for them12:22
tomamanchicken: but you can not get an app which prevents that12:22
fdovingmanchicken: if we look at support, it's way easier to do commandline support, than GUI. explaining where to click is a pain. giving a command is easier. i'd prefer an dcop/dbus interface on that one-click-app :)12:22
=== ryanakca agrees that we should rather concentrate on getting things fixed for good, instead of bandaid treatment
manchickenDaSkreech: Getting folks to fix problems without command-line interaction.12:23
DaSkreechryanakca: but we need bandaids12:23
_StefanS_fdoving: I think it would be a good idea, why not expose what is actually run if you need to do some debug/help on it ?12:23
DaSkreechryanakca: how long have we been telling people how to unlock the apt database?12:23
Hobbsee*** can we look at what we can add, and how, as opposed to whether this is a good idea or not?  it seems most people, at least, think it's a good idea ***12:23
yuriyLure: i think when issues are "more common" that's when workarounds are NOT fine. for rare issues, workarounds are fine12:23
ryanakcaDaSkreech: yeah12:23
manchickenDo we have dozens of c++ developers sitting around ready to patch programs for these complicated problems?12:24
Luremanchicken: clicking again in knetworkmanager on interface/wlan does ifdown/ifup, btw12:24
DaSkreechmanchicken: Would something like the Examples folder suffice?12:24
mhbI don't want to discuss it now, but I had an idea based on this one ... a collection of one-time scripts people can use with one click12:24
mhbI even had a mockup somewhere12:24
kwwiimhb: might be a good idea as long as it does not fsck things worse than before12:24
mhbhttp://img177.imageshack.us/my.php?image=oneclickmockupoc3.png12:24
fdovingautomatifix :)12:24
manchickenDaSkreech: My idea initially was to have an icon that sent you to a folder with .desktop entries that launched shell scripts to fix the problems.12:24
Lureyuriy: I agree, but example (dpkg-configure -a) is a common issue, with clear solution12:25
Hobbseefdoving: twitch.12:25
DaSkreechfdoving: ha ha :)12:25
mhbkwwii: not necessarily fixes, little helper scripts12:25
Lureyuriy: and it is not considered bandage12:25
manchickenI don't even want to have to have a separate UI for things.12:25
DaSkreechmanchicken: that could be updated as we added more fixes?12:25
manchickenI'd just like to see konq display icons for clicking.12:25
kwwiithis sounds like something we could add to the help system in a very prominent place12:25
yuriyhow is that not a bandage? dpkg shouldn't randomly fail. and if it does, it should be fixed invisibly to the user12:25
manchickenDaSkreech: Don't see why not.12:25
_StefanS_yuriy: not everything is perfect, you got to admit that12:26
fdovingmanchicken: icons for clicking that opens a konsole and runs scripts with -ex ?12:26
yuriyalso, what "common problems" are we actually talking about other than dpkg-configure -a?12:26
Hobbseei wonder about running dpkg --configure -a whenever adept closes - especailly if it could be detected that it was a crash12:26
DaSkreechyuriy: Fixing network, fixing sudo lockouts, fixing apt issues12:26
Lureyuriy: agree, but this will never happen (dpkg randomly failing) ;-)12:27
manchickenfdoving: Ideally these scripts would do nothing but fix the problem and exit with no command line displaying.12:27
fdovingmanchicken: then i'm 100% against the whole idea.12:27
tomamaybe someone should make a complete list of things which should be fixed by this app12:27
_StefanS_that thing could also be used to re-apply standard kubuntu settings and enable/disable some of the bling automatically12:27
ryanakcaHobbsee: well, KCrash (or whatever the backtrace app is called) knows when it's a crash... maybe implement something that recognizes solely an adept crash and then runs dpkg --configure -a    ?12:27
JucatoI'm against not showing what's going on. at least like Adept's Dpkg view12:27
_StefanS_you should be able to see details if needed12:28
manchickenfdoving: And I'm 100% against us telling users "oh, just enter this one simple command."12:28
manchickenBecause to many users, there is no such thing as one simple command.12:28
DaSkreechtoma: we have a list somewhere12:28
manchickenIt's black, and ugly, and unknown, and scary.12:28
tomamanchicken: windows also refers to cmd now and then12:28
Hobbseeryanakca: sounds sane, manchicken would have to give input12:28
_StefanS_manchicken: I agree12:28
Luremanchicken: the problem is that you will never cover all cases12:28
yuriyryanakca, Hobbsee: i think adept should run dpkg-configure on start up when it's not working. it already gives an error, just needs a button to run the fix.12:29
DaSkreechtoma: almost never12:29
ryanakcahmmm... I guess12:29
Lureyuriy: +1 (or adept_notifier)12:29
DaSkreechtoma: and I know people who feel dirty if they have to do that in windows12:29
tomaDaSkreech: yes they are, look at the knowledgebase answers12:29
_StefanS_toma: you cant really compare, as alot of the "repair" is already available in the windows gui12:30
DaSkreechtoma: it's like someone on Linux from foreveer being told oh you have to edit your registry look for this alien string and find this alien key and switch it12:30
fdovingmanchicken: well.. an option to make it verbose then? - if this is ment as a tool for us to support users, we need something more than 0 or 1, success or fail.12:30
yuriyhow would users access such an app?12:30
LureDaSkreech: yes, but we shoudl add "Troubleshoot" stuff near the failure and not to central place12:30
DaSkreechtoma: it may work but it scares the hell out of you12:30
LureDaSkreech: you want to hide such stuff ;-)12:30
DaSkreechLure: Yeah12:30
tomaDaSkreech: again, i would like to see a complete list of things that you want to fix with that app.12:31
Riddellwell, I see lots of potential problems with it, but of course if someone codes it we can't stop them, and it would be interesting to see the feedback that gets12:31
LureI agree with toma: we first need a list, then we can agree what make sense and what is the best way to address it12:31
DaSkreechtoma: we shoudl have wikied it :(12:31
Riddellmhb's mockup does look interesting12:31
DaSkreechtoma: it's floating on gobby.ubuntu.com12:31
LureI belive that each bandage may need special handling12:31
DaSkreechLure: ++12:31
Riddellyou could even do hot new stuff to update it after release (scary idea)12:31
DaSkreechRiddell: Errm no :)12:31
DaSkreechand I'm a GHNS pimp12:32
fdovingRiddell: very scary, as i guess most scripts will need root access.12:32
_StefanS_fdoving: cant you make a way of undoing changes also ?12:32
_StefanS_fdoving: like a rollback feature12:32
mhbRiddell: yes, something like that ... but I know it's scary12:32
tomai think Riddell means using hot new stuff to add new scripts to the application. Not to scary for me.12:33
mhbRiddell: the scripts would have to be reviewed12:33
Riddellour main focus should be on actually fixing the issues, the adept one does seem entirely fixable even if with a hack in adept rather than outwith it12:33
Riddellmhb: of course12:33
DaSkreechRiddell: as far as I know GHNS currently doens't have versioning12:33
Riddellso code away if you want, but no guarantees it'll ever go on the CD12:33
DaSkreechwhich makes it a terrible choice12:33
fdovingtoma: of those scripts are to be run as root - does hotnewstuff have some kind of md5sum checking thing?12:33
DaSkreechRiddell: Could it be one of those things we ask people to try out of their own will first?12:34
tomafdoving: i believe not anyone can add scripts blindly12:34
=== manchicken_ [n=manchkn@74-134-94-223.dhcp.insightbb.com] has joined #ubuntu-meeting
Riddelllets move on12:34
RiddellSho_: your item12:34
fdovingtoma: i'd like some checksum-verification, really.12:34
DaSkreechSo the consensus is code it and we shall see?12:34
Luremanchicken: can we add a table to your wiki with issue:reason:solution kind of proposal12:34
Sho_Alright12:35
tomafdoving: you can make that ;-)12:35
manchicken_I **HATE** wireless networking.  It is the asscrack of all networking.12:35
manchicken_Lure: Sure.  Not a problem.12:35
fdovingtoma: yep :)12:35
manchicken_Lure: I was gonna make you work on it anyway ;)12:35
_StefanS_manchicken_: you should buy some descent equipment ;)12:35
Sho_The issue at hand is that Kubuntu ships a bunch of default settings and modifications to Konversation which deviate from upstream, and which upstream (that is me and my co-developers) are unhappy with12:35
Luremanchicken: then it will be empty table ;-)12:35
manchicken__StefanS_: For wireless networking there is no such thing.12:35
DaSkreechmanchicken_: I have a cord and some tin cans12:35
_StefanS_manchicken_: I disagree.12:35
fdovingmanchicken_: i liked your konqueror + .desktop idea. simple and very convenient.12:35
LureSho_: examples?12:36
Sho_We've previously been talking to our Kubuntu liason Hobbsee who has agreed to bring those issues up, but as things have stagnated for a while I've decided to become a little more proactive12:36
Riddellwheesht people, listen to Sho_12:36
Sho_Here's some detail on what exactly we have problems with: http://konversation.kde.org/kubuntu-issues.txt12:36
HobbseeSho_: thanks.  uni stuff and crap :(12:36
=== _czessi [n=Czessi@dslb-088-073-023-046.pools.arcor-ip.net] has joined #ubuntu-meeting
Riddellooh system tray shouldn't be on by default? yay!12:36
tomaSho_: the list looks sane to me, we should fix some things.12:36
DaSkreechha ha12:36
DaSkreechFirst thing I thought12:37
Sho_I'm told Riddell hates systray icons, so #1 should be a nobrainer ;)12:37
mhbyes12:37
kwwiilol12:37
Sho_:)12:37
tomaSho_: last one as well12:37
Hobbsee1 & 4 are no brainers12:37
LureSho_: first: I did not agree with some default changes, however I am not sure how can upstream really work with distro about such customization of defaults12:37
Hobbsee3 tonio_ will argue with you over, that the default theme doesnt make implicit sense - but i'm not sure that terms like "voice" etc do either12:38
yuriywhat's wrong with the systray icon? :(12:38
DaSkreechwhy was 3 done?12:38
LureSho_: kubuntu does quite some changes from default kde, but this is imho good as some new ideas can be tested with wider audience12:38
fdovingSho_: good points.12:38
manchicken_Sho_: My concern here would be that these seem like normal things that many distros do to many different programs.12:38
DaSkreechyuriy: Riddel hates any and all System tray icons :)12:38
manchicken_Sho_: So why is it such a big deal?12:38
DaSkreechyuriy: after a while staring at windows I agree12:39
=== yuriy wishes irssi in konsole could have a systray icon
manchicken_Most of these things are just packaging.12:39
DaSkreechSho_: I think that konvi and kopete fall in near the same category12:39
RiddellSho_: the only one I disagree with is tabs on the left are good because you can fit more in.  I have 140 irc windows open, that works as well as it can with a listview on the left but not with tabs along the bottom12:39
Sho_manchicken_: Perhaps we care about Kubuntu more than about other distros for the same reasons you probably think it's a really neat distro? ;-)12:39
fdovingyuriy: you can put konsole in systray. check out kstart :)12:39
DaSkreechSho_: Kopete I think should have a icon tray maybe konvi shoudl as well?12:39
kwwiiRiddell: I agree with that as well, but all bottom-up text based apps should have the same tab placement for usability reasons12:39
Sho_manchicken_: Fact is, Kubuntu is the KDE-centric desktop distro people go for these days, and whatever Konvi Kubuntu ships shapes the public image of Konvi to a great degree12:39
fdovingRiddell: you're a special case :)12:39
Jucatoyuriy: or modify the K Menu entry :)12:39
_StefanS_I like konversation in tray by default12:39
kwwiinew users expect tabs to be in the same place12:40
DaSkreechRiddell: I don't think you are a standard user case12:40
manchicken_Sho_: But my concern is that upstream and distro have always been a bit of a separation of powers.  This seems like there may be a bit of a boundary crossing to me.12:40
kwwiiwe should definitely ask usability peeps about tab placement12:40
Riddellit seems not usual for people to have more than 10 irc windows open12:40
HobbseeI want a decision that "this is how we're running konversation", and that the default settings dont change after that, without consensus from the KC.  This is ridiculous12:40
manchicken_I'm but a lowly geek though.  I'll yield to others, that's just my $0.02.12:40
Lurekwwii: +1 - left side channels are really useful for heavy irc users12:40
Sho_manchicken_: Our stance is that we spend more time thinking about our defaults than distributions and that distributions shouldn't change what we come up with on a whim12:40
Lurekwwii: geeks ;-)12:40
tomaRiddell: can you fix konsole? I have more open then fits in there..12:41
kwwiiLure: exactly :-)12:41
manchicken_Sho_: Why not?12:41
Sho_manchicken_: For example, the tab position change was clearly done on a whim by maintainer preference (I get it, it looks cooler - I wrote it, I like it too), which I don't think is a good enough reason12:41
Lurekwwii: I was fighting against tab placement change, but lost :-(12:41
manchicken_Sho_: Why does it matter to upstream konversation though?12:41
DaSkreechmanchicken_: Kubuntu is high profile12:42
Sho_manchicken_: see [00:41]  <Sho_> manchicken_: Fact is, Kubuntu is the KDE-centric desktop distro people go for these days, and whatever Konvi Kubuntu ships shapes the public image of Konvi to a great degree12:42
kwwiieverone needs a 1024x768 screen to understand why the left tabs waste space as well12:42
RiddellSho_: it's not just the looks, don't you run out of space with bottom tabs?12:42
LureSho_: it is better only for heavy IRC user (like us), but not for typicall kubuntu user that may use it only to get support in #kubuntu (one channel)12:42
DaSkreechHold on. Everyone agrees on point 4 ?12:42
manchicken_Sho_: So does that mean that konvi now gets to dictate how kubuntu packages konvi?12:42
kwwiiRiddell: non-geeks don't have that many channels open12:42
HobbseeDaSkreech: yes12:42
ryanakcapoint 4 is fine by me12:42
RiddellDaSkreech: sure12:42
LureRiddell: you do,m bt not typicall user that wants to get help by Jucato in #kubuntu ;-)12:43
DaSkreechmanchicken_: no he's asking us to look at the default changes12:43
Sho_Riddell: Yes, that's one of the reasons people like the treelist over the tab bar. However I'd argue that new users tend not to open so many views that they run into the problem, and by the time they do, they'll probably be in a position to find the preference themselves.12:43
Riddellmanchicken_: they're asking, not dictating12:43
Jucatoheh :)12:43
kwwiimanchicken_: no, but being the representative kde dist is a very important thing12:43
Riddellkwwii: but non-geeks don't use irc12:43
neversfeldeah12:43
=== neversfelde does
kwwiiRiddell: but they still need things to be usable on first use - geeks love to change things12:43
_StefanS_kwwii: good point !12:43
neversfeldeyeah12:44
mhbRiddell: well, they might start, a lot of (k)ubuntu help points them to IRC12:44
ryanakcaI think #2 can be easily fixed...12:44
manchicken_Yes, but we need to distribute how we think is best to distribute, not how we think upstream would like us to distribute.  If both of these goals align, fantastic.  If they're in conflict, I would say upstream takes the back seat.12:44
tomai would vote for tabs at bottom for the default, but this discussion will be endless... seele?12:44
Hobbseeryanakca: sure it can - but we dont want to change it yet again.12:44
Sho_manchicken_: We're not in a position to dictate, but it'd be swell if we could discuss the issues we have?12:44
Riddellmanchicken_: mind that if we annoy upstream too much we end up not having any software12:45
kwwiimanchicken_: sure, but this is a matter of where the tabs are, not something amazingly hard to prove usability-wise12:45
fdovingi'd say do what the konversation developers have spent hours deciding. what some packager did in 4 minutes doesn't really matter that much.12:45
=== zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
manchicken_Sho_: Sure.  But some of these things seem to be of rather little consequence.  I'm just concerned that konversation--a program that I am now using and have been using for quite some time--may be trying to control downstream distribution a little too much.12:45
kwwiiwe should ask seele and other usability peeps on this (but I know what they are going to say)12:45
mhbmanchicken_: don't forget, "downstream loves them (KDE)"12:45
Jucatomanchicken_: while distros have the right to change defaults and customize, it doesn't mean of course that we do so on a whim. It also doesn't mean that just because we have decided on something that it totally closed for discussion w/ upstream12:45
Sho_manchicken_: Surely you don't find it odd that the developers of software have a stake in how it's going to be presented to the users?12:46
Sho_manchicken_: We're not your wall socket code supply, we make apps12:46
=== ryanakca agrees with the tabs part. It should be the same in all apps: Tree or tabs. And it's (tree) wasted space. If you want a tree, look in preferences.
=== Hobbsee checks if we're adding new stuff here
RiddellI suspect we've run out of new stuff12:47
=== Hobbsee ponders saying "take this to the list, and get seele's input"
mhbyeah12:47
Hobbseetoma: has a point about debian12:47
Jucatoryanakca: but we don't have preferences, we have settings :P12:47
DaSkreechNicklist?12:47
Riddellshould we do a council vote?12:47
ryanakcaDaSkreech: channel list12:47
Jucatoexercise new powers :)12:47
mhbI suggest waiting for the usability folks12:47
mhbto comment on it12:47
DaSkreechryanakca: Right I'm asking on opinion12:47
manchicken_I'm just gonna pull out of this conversation and go AFK for a bit.12:47
DaSkreechShould it be changed?12:47
HobbseeRiddell: fairly sure tonio_ will throw a cow if we do, as he feels strongly on this, and we dont have seele's input either, which i'd prefer to see12:48
mhblike Hobbsee said12:48
Sho_Notably Ellen Reitmayr from the KDE usability team is a participant in Konversation's development process, and an active Konvi user.12:48
ryanakcaRiddell: I'd put it on the ML, and if no concensus by next meeting, then KC can vote12:48
Luremhb: +1 on usability review12:48
Hobbseeand/or el12:48
Sho_Haven't heard any complaints from her about the bottom default so far.12:48
nixternalOK, I am back..sorry for that12:48
kwwiidon't worry, I'll give tonio the love he needs12:48
DaSkreechSho_: wait? the squares one?12:48
ryanakcawb nixternal12:48
LureHobbsee: I think imbrandon was pushing for tree and not Tonio_12:48
HobbseeLure: right12:48
nixternalthat was a quick drive12:48
=== Lure remebers fighting with imbrandon about this ;-)
Hobbseehehe12:48
DaSkreechSho_: Simplistic?12:48
ryanakcalol12:48
jjessemtg still going on?12:49
Riddellok, let's get el to explain the ratonal from a usability view, seele to review and follow that12:49
Hobbseejjesse: yep12:49
Riddelland break the no sys tray thing gently to tonio12:49
kwwiiRiddell: +112:49
Sho_DaSkreech: The default theme is "Simplistic", yeah12:49
fdovingthere is probably not a reason all kde apps have the tabs at top or bottom. :)12:49
=== DaSkreech votes for keeping the current theme
Sho_On what grounds?12:49
LureSho_: bottom tabs is better for sure - near the text reading area and consistent with konsole12:49
DaSkreechIt's impossible to read12:49
=== fernando__ [n=fernando@189.0.214.111] has joined #ubuntu-meeting
Hobbseepeople tend not to grok the different parts of irc anyway, so i dont suspect that the symbols really mean much to the user12:50
Hobbseeapart from the "greyed out means away"12:50
Riddellok, any other business?12:50
kwwiilet's leave this up to those who specialize in this area12:50
Hobbseein which case the point is moot12:50
HobbseeRiddell: yes, toma12:50
LureDaSkreech: I agree that default theme is not good enough, but I vote for kwwii to help konversation gust with new icons12:50
=== ryanakca_ [n=ryan@ubuntu/member/ryanakca] has joined #ubuntu-meeting
Sho_DaSkreech: The nickname list widget has a comprehensive "What's This" help tooltip that uses the active theme to describe the different states, and the theme preview widget in the preferences dialog has description tooltips.12:50
JucatoLure; +1 :D12:50
DaSkreechHobbsee: yeah but I can easily glance at the nicklist and ascertain that some people have powers with squares12:50
DaSkreechI can't do that with simplistic12:50
DaSkreechunless it's explained12:51
HobbseeDaSkreech: true that.  i actually agree with you - that's what i use too12:51
Hobbseebut tonio will absolutely throw a cow over it :)12:51
Riddelltoma has an item?12:51
tomaIn some recent discussions with the debian KDE team it appears that they are not really happy with the coorparation between both parties and I would like to organise a meeting between both to see where we can help eachother. Please -1 if objecting, +1 if you want to attend, 0 if you dont care12:51
Sho_DaSkreech: The nickname list widget has a comprehensive "What's This" help tooltip that uses the active theme to describe the different states, and the theme preview widget in the preferences dialog has description tooltips.12:51
fdoving+112:51
mhb+112:51
DaSkreechSho_: you are assuming that people click on that12:51
HobbseeRiddell: yeah.  the agenda didnt catch up with his brainwaves, though.12:51
Sho_oops, sry12:51
Riddelltoma: actually I hope to plan the real life meeting at debconf12:51
Luretoma: +112:51
kwwii+112:51
Riddellerr, attend, not plan12:52
=== Hobbsee didnt use the what's this help tooltip for a good few years - wouldnt have thought to put that on the contact list
Sho_DaSkreech: Our main concern with the theme Kubuntu chose is that it's graphically poor. If Kubuntu is going to deviate from our default, maybe another option would be to spend some art resources on fixing the theme.12:52
LureSho_: but good icon is always better than tooltip12:52
ryanakca+112:52
Sho_DaSkreech: We're not married to the default, but we'd like for the app not to look like shit.12:52
DaSkreechSho_: I vote for fixing it12:52
tomaRiddell: ok, that's nice, but not many people here will be there I guess12:52
Hobbseewe need to look at sending oru changes back to debian, and oru bugs back - else we just make them furious12:52
Sho_DaSkreech: we're ok with that12:52
LureSho_: exactly - I hope kwwii can help here with some icon proposal12:52
DaSkreechSho_: would you like to contribute what makes it poor?12:52
Jucato+1 for asking kwwii for some awesome looking icons :)12:52
HobbseeDaSkreech: you're volunteering?12:52
mhbSho_: let's keep it family friendly .o)12:53
tomacan we stop the konversation discussion please?12:53
kwwiilooks like I am voluntold to make icons12:53
yuriykubuntu kde packaging is completely separate from debian?12:53
DaSkreechtoma: +112:53
DaSkreechkwwii: lol12:53
Riddellyuriy: no, it's mostly the same12:53
Hobbseeyuriy: no - but it's mainly bugs now12:53
Lurekwwii: just 4 or so (not 20 batteries ;-)12:53
Hobbseewhich we should really send back12:53
nixternaltoma: +1 on the Debian KDE meeting, however physically will be a hard one for me since I am back in school...1 year left then we can all party Kubuntu style :)12:53
yuriyoh i thought Riddell packages the new KDE every time12:53
yuriyor is that just for kubuntu.org?12:54
Hobbseethere's a reportbug-ng too, so you dont have to use email12:54
Hobbseeyuriy: nope.  and nope12:54
Sho_DaSkreech: The colour palette doesn't fit very well into either KDE or Kubuntu defaults, and the serif typography doesn't look particularly fresh.12:54
Hobbseeyuriy: we have to rebuild for kubuntu, and add some of our stuff, but otherwise it's the same12:54
DaSkreechSho_: noted12:54
yuriyoh ok12:54
tomai want a meeting to see where we can help each other and with all people involved, i think thats only possible on irc12:54
DaSkreechSho_: can i request that you put that on the text that we are referencing ?12:54
Sho_Ok, so to sum things up: Disabling the systray icon is a go; removing the C++ patch is a go; theme is going to the artwork people; tab bar ... what?12:54
Riddelltoma: meeting sounds fine, should it be before or after debconf?12:54
mhban irc meeting would be lovely for those that can't attend debconf12:55
DaSkreechSho_: usabilty12:55
tomaRiddell: what do you think?12:55
mhbfrom both sides12:55
DaSkreechSho_: then a decision12:55
=== Zelut [n=christer@ubuntu/member/zelut] has joined #ubuntu-meeting
HobbseeSho_: tab bar to the usability12:55
Hobbseepeople12:55
Sho_DaSkreech: Isn't it kind of redundant to double-check KDE Usability with Kubuntu Usability? ;-)12:55
RiddellSho_: tab bar we ask el for a rationale and seele for feedback and follow them12:55
Sho_hmkay12:55
Luretoma: I think irc meeting is fine and Riddell (+whoever) does f-to-f on debconf12:55
Hobbseemeeting would be good - give me at least a couple of weeks so i can go thru those logs again and become sanely thought out12:55
DaSkreechSho_: sure it is. Swing us what KDE usabilty said :)12:55
tomacan we stop the konversation discussion please?12:56
Sho_DaSkreech: As noted above, El is a participant in our process and so far hasn't complained about the bottom default, anyway12:56
tomaok12:56
HobbseeRiddell: please do impress on them at debconf htat you're interested in making the distros kde both as good as possible, not just trying to add crackful bling12:56
=== yuriy cringed as he anticipated reading "can we stop the konversation conversation please"
tomagood nite all, i'll set it in motion12:56
DaSkreechNite12:56
fdovingnite.12:57
=== nixternal [n=nixterna@ubuntu/member/pdpc.active.nixternal] has joined #ubuntu-meeting
DaSkreechnixxy baby!12:57
mhbanything else?12:57
HobbseeRiddell: afaik, that's not hte case - but it is the perception12:57
RiddellHobbsee: what's not the case?12:57
Sho_DaSkreech: I've added the points about the theme to the txt file12:57
DaSkreechSho_: thanks12:58
HobbseeRiddell: that you're adding crackful bling, and not interested in making kde work the best - just making it the shinyest12:58
Hobbseeid' have to look up the exact quote12:58
Riddellwe only add good bling12:58
Riddellany other business?12:59
Hobbseewell, good bling too.12:59
nixternalno gold wheels with spinners please12:59
HobbseeRiddell: i want a pony, please.12:59
Riddellshould we try and hold regular kubuntu meetings?12:59
jjesseyes01:00
Hobbseeoh yes, that's right01:00
LureRiddell: yes!01:00
mhbsure01:00
LureRiddell: bi-weekly?01:00
Hobbsee* Volunteers for helping to clean up the kubuntu wiki01:00
Hobbseeplease, if there are people who are interested, do so01:00
Hobbseei cleaned up a hwole lot of breezy kubuntu stuff at UDS01:00
JucatoHobbsee: I'll try to see if I could help this weekend on that01:00
yuriykubuntu wiki being wiki.kubuntu.org/Kubuntu?01:00
LureHobbsee: +1 - I like KernelTeam desing01:00
Luredesign even01:00
Hobbseeyuriy: category kubuntu stuff01:00
Hobbseehavent seen that, sorry01:01
Hobbsee* Have monthly meetings, maybe on the first wednesday of each month was the plan01:01
HobbseeRiddell: apparently our kde4 packages start - we probably want to look at working more with debian on this?01:01
Hobbseetha's where we got blasted for a lot01:01
DaSkreechHobbsee: a Mustang?01:02
HobbseeDaSkreech: hm?01:02
RiddellLure: do you think we have enough business for fortnightly?01:02
LureRiddell: we can probably start with monthly as Hobbsee proposed01:03
DaSkreechHobbsee: for your pony01:03
HobbseeDaSkreech: ahh01:03
=== Hobbsee has notes from UDS on this stuff
DaSkreechWhat's the criteria for wiki cleanup?01:03
Riddellhow about first wednesday of each month?01:03
RiddellI remember that was suggested at UDS01:03
HobbseeDaSkreech: "anything that's not needed"01:03
LureRiddell: what time - like tonight?01:04
Hobbseei believe that pending timetable, tha'ts okay01:04
HobbseeLure: yeah01:04
RiddellLure: at a time that suits best for the month?01:04
HobbseeLure: it'd change when daylight savings screws up, though01:04
Hobbseeas in, it's hinged upon my time, so it'll change when au timezones do01:04
Lureor do we have two times (to better fit people like Jucato and then alter?01:04
Riddellso next meeting, 4th of july01:05
HobbseeLure: doesnt really work - we miss the europeans01:05
Hobbseei've tried that01:05
Jucato:)01:05
HobbseeRiddell: tha't sa US holiday, isnt it?01:05
DaSkreechHobbsee: as in out of date?01:05
Riddellyes, means they have no excuse for being at work :)01:05
Hobbseehaha01:05
LureHobbsee: right, as it is during our work hours....01:05
HobbseeLure: exactly01:05
Riddellany volunteer to do minutes from this meeting?01:05
nixternalWednesday for me is busy between after 22:00 UTC01:06
Sho_Hobbsee: (btw, you're going to ping us when the results on the usability review are in?)01:06
=== Zelut [n=christer@ubuntu/member/zelut] has left #ubuntu-meeting []
HobbseeSho_: will CC you on all the relevant mailing list mail, yes.01:06
nixternalargh this ssh is killing me01:06
RiddellSho_: sure, and it's less a review more an opinion, no need to spend hours on it01:06
Riddellnixternal: another day suit better?01:06
Lurenixternal: we can probably do also Tue or Thu01:06
Riddellthursdays tend to have other meetings01:07
Hobbseeactually, screw that01:07
Sho_Hobbsee, Riddell: k, thanks01:07
nixternalRiddell: Monday - Thursday after 22:00 is busy for me for school...anytime before 22:00 is fine01:07
Hobbseemy timetable will change next semester - there's only one more weke of class01:07
Jucatokthxbye? lolcode! :)01:07
LureSho_: and thans for great app!01:07
LureSho_: thanks even01:07
Riddellnixternal: 22:00 local time?01:07
nixternalUTC01:08
Sho_Lure: thanks :)01:08
=== rpereira [n=rpereira@ubuntu/member/rpereira] has joined #ubuntu-meeting
HobbseeRiddell: definetly UTC.  if anyone gives me a timezone in NST or FUTZ, i shoot them.01:09
Jucatohehehe01:09
Riddellok, well lets try wednesdays and pick a time closer to the date01:09
Hobbseegive me a min, i'm fighting estudent01:09
=== bcasanov [n=opera@user-38f165.user.msu.edu] has left #ubuntu-meeting []
Hobbseeooh, saner timetable!01:10
Hobbseeokay, tuesday and wednesday works here, but we may bea ble to push the meeting alter anyway01:10
mhbaww, 22:00 UTC is midnight here :o(01:10
HobbseeRiddell: (up arrow here)01:11
mhbbut it's fine for one or two meetings01:11
Riddellmhb: and he needs it before that time01:11
Riddellstill looking for minutes volunteers :)01:11
mhbRiddell: oh, before that is fine01:11
mhbRiddell: I'll do it01:11
Riddellyay01:11
Riddellmeeting over I think01:12
Hobbseeseems so01:12
Hobbseethanks all for coming01:12
Riddellthanks all01:12
=== chx [n=chx@pdpc/supporter/professional/chx] has left #ubuntu-meeting ["Viva]
Hobbsee1/3 meetings down01:12
Hobbseeand yay, core dev tonight!  maybe01:12
Riddelloh yes, everyone come and support Hobbsee for core dev tomorrow european morning01:12
Hobbsee930 UTC, iirc01:12
Jucatowhat time? (UTC)01:12
=== Jucato computes
Hobbsee7.30pm local01:13
Hobbseenot sure for you01:13
Jucatocool 5:30 pm :)01:13
Jucatoer.. wait01:13
Jucatoshould be 5:30. I'll compute later eheheh01:13
LureHobbsee: good luck with core-dev - you will rock!01:13
mhbHobbsee: good luck01:13
Hobbseethanks :)01:13
JucatoHobbsee: you don't need luck. you have your Long Pointy Stick of Doom TM :)01:14
=== manchicken_ [n=manchkn@74-134-94-223.dhcp.insightbb.com] has left #ubuntu-meeting ["Konversation]
HobbseeJucato: heh01:14
DaSkreechDoooooooooooooooooooooooooooooooooom01:14
=== kwwii heads off for bed soon
=== jjesse [n=jjesse@ppp-69-221-237-3.dsl.klmzmi.ameritech.net] has left #ubuntu-meeting ["Konversation]
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== Jucato [n=jucato@ubuntu/member/Jucato] has left #ubuntu-meeting ["Konversation]
=== ..[topic/#ubuntu-meeting:ubotu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 05 Jun 19:00 UTC: Technical Board | 06 Jun 20:00 UTC: Edubuntu | 07 Jun 20:00 UTC: Ubuntu Development Team | 12 Jun 15:00 UTC: Kernel Team | 13 Jun 12:00 UTC: Edubuntu | 14 Jun 16:00 UTC: Ubuntu Development Team
=== Knightlust [n=Dax@ubuntu/member/knightlust] has left #ubuntu-meeting ["Moodle..."]
=== Sho_ [i=ehs1@kde/hein] has left #ubuntu-meeting ["Stop]
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== ryanakca [n=ryan@ubuntu/member/ryanakca] has left #ubuntu-meeting []
=== Martinp23 [n=Martinp2@wikimedia/Martinp23] has joined #ubuntu-meeting
=== Martinp23 [n=Martinp2@wikimedia/Martinp23] has joined #ubuntu-meeting
=== yuriy [n=yuriy@207-172-67-143.c3-0.frm-ubr3.sbo-frm.ma.cable.rcn.com] has left #ubuntu-meeting []
=== ypsila [n=opera@wrzb-590cf741.pool.einsundeins.de] has left #ubuntu-meeting []
=== illovae_ [n=illovae@unaffiliated/illovae] has joined #ubuntu-meeting
=== merriam_ [n=merriam@85-211-245-180.dyn.gotadsl.co.uk] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== beuno [n=martin@ubuntu/member/beuno] has joined #ubuntu-meeting
=== dregorth [n=Jon@66-190-240-43.dhcp.klmt.or.charter.com] has joined #ubuntu-meeting
=== dregorth [n=Jon@66-190-240-43.dhcp.klmt.or.charter.com] has left #ubuntu-meeting ["Konversation]
=== j_ack [n=jack@p508D901D.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:40:213:2ff:fe05:abdb] has joined #ubuntu-meeting
=== mhb [n=mhb@ubuntu/member/mhb] has left #ubuntu-meeting []
=== Rinchen_ [n=Joey@2001:4830:152d:0:20e:cff:fe74:b250] has joined #ubuntu-meeting
=== nixternal [n=nixterna@ubuntu/member/pdpc.active.nixternal] has joined #ubuntu-meeting
=== mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== freeflying [n=freeflyi@ubuntu/member/freeflying] has joined #ubuntu-meeting
=== wsjunior [n=wsjunior@200.193.226.175] has joined #ubuntu-meeting
=== yharrow_ [n=sysadmin@h-68-164-37-69.nycmny83.dynamic.covad.net] has joined #ubuntu-meeting
=== nixternal_ [n=nixterna@ubuntu/member/pdpc.active.nixternal] has joined #ubuntu-meeting
=== j_ack [n=jack@p508D901D.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Martinp23 [n=Martinp2@wikimedia/Martinp23] has joined #ubuntu-meeting
=== Treenaks [n=martijn@thuis.foodfight.org] has joined #ubuntu-meeting
=== Burgundavia_ [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== j_ack [n=jack@p508D901D.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== czessi_ [n=Czessi@dslb-088-073-025-020.pools.arcor-ip.net] has joined #ubuntu-meeting
=== ompaul [n=ompaul@freenode/staff/gnewsense.ompaul] has joined #ubuntu-meeting
=== Lure [n=lure@external-1.hermes.si] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F761EA.versanet.de] has joined #ubuntu-meeting
=== Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== spiderman_ [n=chatzill@c-67-164-104-223.hsd1.ca.comcast.net] has joined #ubuntu-meeting
spiderman_hi there   im trying to connect MS blue tooth keyboard in ubuntu 7.0.4 and getting error Can't create HID control channel: Connection refused ... can any one tell me what to do09:41
spiderman_?09:41
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== LongPointyStick [n=user@ubuntu/member/hobbsee] has left #ubuntu-meeting []
=== spiderman_ [n=chatzill@c-67-164-104-223.hsd1.ca.comcast.net] has left #ubuntu-meeting []
=== dholbach_ [n=daniel@i59F7423E.versanet.de] has joined #ubuntu-meeting
=== lionel [n=lionel@ip-61.net-82-216-103.rev.numericable.fr] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
=== DarkSun88 [n=Ma@ubuntu/member/darksun88] has joined #ubuntu-meeting
DarkSun88Hi all11:27
=== Jucato [n=jucato@ubuntu/member/Jucato] has joined #ubuntu-meeting
mdzHobbsee: ping?11:36
Hobbseemdz: pong, on release management conference call11:36
Hobbseeas is keybuk11:36
mdzHobbsee: ok, though I have an 1100 meeting11:41
=== neversfelde [n=neversfe@nrbg-4db4408f.pool.einsundeins.de] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
Hobbseemdz: in what TZ?11:53
mdzHobbsee: about 6 minutes from now11:54
Hobbseebugger11:54
mdzis the call finished?11:54
Hobbseealmost11:54
mdzwe scheduled from 0930-1000 UTC for this meeting11:54
Hobbseeright, OK11:54
mdzdid the release call run over, or was there a scheduling error?11:54
Hobbseesoryr - meeting started 45 mins late.11:54
Hobbseeit ran over11:54
=== Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-meeting
Hobbseemdz: it's done now11:55
Hobbseehiya Keybuk11:55
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-meeting
fabbioneHobbsee: trying to become core-dev?11:55
Hobbseefabbione: yes11:55
mdzfabbione: australia-compatible tech board meeting11:56
fabbioneok.. mdz, Keybuk: you have my plus on her work to be core-dev11:56
fabbione(for what it matters)11:56
fabbionei have been eyeballing her work from time to time and it was good11:56
mdzKeybuk: did you hear anything from mjg59?11:56
mdzsabdfl is in the office11:56
fabbionemdz: yeah i could guess that11:56
Hobbseehttps://lists.ubuntu.com/archives/motu-council/2007-May/000124.html was Riddell's input, he found out late11:56
Keybukmdz: it's about 5 hours until he gets up11:57
Hobbseemdz: i'm not sure what you want to do, in the interests of time now.  it's your call.11:57
Riddellthat post doesn't read as enthusiastically as it should have done :)11:57
=== sabdfl [n=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #ubuntu-meeting
sabdflhi all11:57
Hobbseehi sabdfl11:57
sabdflHobbsee: sorry for the delay11:57
Hobbseesabdfl: no problem - our conference call on release management only just ended.11:58
Hobbseewhich Keybuk was on as well11:58
sabdflKeybuk: mdz has another call so it's just you me and mjg59 iirc11:58
sabdflshould we get started?11:59
KeybukHobbsee: how did you find UDS?  did you have a productive week?  any suggestions for how we might improve the format/sessions to make them better?11:59
ograif one MOTU deserves it, its Hobbsee11:59
=== ogra cheers
HobbseeKeybuk: i found it useful, when it wasnt freezing cold.  i had a fairly productive week, getting to know people11:59
sabdflHobbsee: what does -core-dev mean, in your opinion, other than the ability to upload to main/restricted?11:59
=== cyclios [n=cyclios@dsl-083-247-110-137.solcon.nl] has joined #ubuntu-meeting
Hobbseeit's hard for the more community type people to actually get stuff done - it's very coding focussed12:00
Hobbseesabdfl: a responsibility for QA, being able to merge seeds, etc. more so than just MOTU.12:00
HobbseeKeybuk: the sessions seemed better this time, from what i'd heard.  the hotel and such worked really well.12:00
mdzI've delayed my meeting by 30 minutes12:01
HobbseeKeybuk: oh, and getting to know the canonical people were really cool12:01
=== cyclios [n=cyclios@dsl-083-247-110-137.solcon.nl] has joined #ubuntu-meeting
cjwatsonHobbsee: which sessions were you mostly involved in?12:01
Hobbseecjwatson: kubuntu, obviously, irc, forum ambassadors, a bit of planet stuff...12:01
Hobbseeended up sitting on a copule of "canonical" ones, like the developer weather report12:01
cjwatson(I don't think that's particularly Canonical FWIW, though it should probably end up running on a DC machine)12:02
HobbseeKeybuk: actually, that's one thing i'd like to see - an awareness that developer weather report, etc, or some of the more archive-y things you dont actually need to be a canonical employee for - they wont kick you out12:02
Hobbseeit's not, i suspect, but the perception was there12:02
cjwatsonI think, for those sessions that were closed, we were reluctant to overly draw attention to them by pointing out that everything else was open :-)12:03
mdzHobbsee: you mentioned to me that it wasn't apparent to you that it was possible to get involved in certain activities without Canonical, and I've heard indications like that from others as well (for example, people who think that ubuntu-core-dev is only Canonical).  Do you have any thoughts about how we can help to communicate better that this is not the case?12:03
cjwatsonbut it's an interesting point12:03
Hobbseemdz: i think the canonical wiki is a big problem - it's got all htis secret info12:04
Hobbseeof course, the fact that it's secret, and we see bits of secret info coming off it, makes us all wonder how much else we're missing out on12:04
Hobbseewhich makes it hard to actually feel involved in some of the higher stuff.12:04
Hobbseecjwatson: true that.  and i wasnt including the intel stuff in that.12:04
Hobbseemdz: i'm not sure, to be honest.  it's a very big perception on MOTU == community, core-dev == canonical.  it's becoming apparent that there are other non-canonical core devs...12:05
mdzHobbsee: we try to draw that line clearly, and keep Ubuntu activity separate from Canonical activity.  information about business relationships, employees, etc. will always be confidential.  is there something in particular which you feel is misplaced?12:05
Keybukmdz: she spoke about the *Process wiki pages during the call12:05
Hobbseebut as soon as you deal in anything which requires ubuntu-archive powers, or anything special on LP, you're stuffed.12:06
mdzthat was sabdfl's call12:06
Keybukas a community member, it's hard for her to be involved with the milestone or release process, because those checklist/tasklists are on the canonical wiki12:06
Hobbseemdz: it's a bit of working in the dark.  and most people wont do that.12:06
Hobbseeokay, it's a lot of working in the dark, and backtracking, to guess what that info might be.12:06
Hobbseemdz: of course business, employees, etc, will be confidential.  it's hard to say, without actually being able to see what's there, what i'd like to see moved from there to somewhere public of course.  but any of the documentation, like release management, which isnt trouble for compeditors to have shouldnt be a problem, i w ould think12:07
Hobbseei'm not sure if i'im making sense here12:07
Hobbseeblerg.12:08
Hobbsee"if it's not company-secret, then release it"12:08
Hobbseeis the upshot.12:08
mdzthat is in fact pretty much our guideline12:08
Hobbseeand i fail to see how stuff like RM'ing is company secret - if the iso testing is public12:09
mdzwe try to be as transparent as possible12:09
Hobbseethen it's a question of whether your perception matches your actions.12:09
=== DarkSun88 [n=Ma@ubuntu/member/darksun88] has joined #ubuntu-meeting
mdzHobbsee: I agree with you, it should be able to be public12:09
Hobbseeyou'll find, if you spread some of this info around, that people will say 'oh, i'm interested in this', like you did last night - and they wont necessarily be canonical people.12:10
mdzI *think* that sabdfl's concerns had to do with information about the internal network infrastructure, but I'm not going to try to speak for him12:10
Hobbseehe should be here, he should be able to speak for himself.  *g*12:10
sabdflthere will always be some things we want to be uniquely good at, at canonical, that we consider company expertise12:10
Hobbseebut i see your point, yes.  obviously small parts will be confidential12:10
sabdfland those things we keep internal to canonical12:10
Hobbseeyeah12:10
Hobbseeof course12:10
sabdfland there will always be folks wanting to see or participate in that12:11
mdzHobbsee: that particular documentation presumably only came up today during the release call, though the perception certainly predated that.  is there something else about that wiki which troubles you?12:11
sabdflso that point of friction is an inevitability12:11
sabdflsame thing happens when a developer working on cool stuff says "i'll release htis when i'm ready"12:11
Hobbseemdz: the specs being moved to the wiki on the 4th, when UDS started on the 6th, was an absolute nightmare, community wise.12:11
sabdflincreasingly there are also other companies working with ubuntu, and they don't disclose what they do even to canonical12:11
Hobbseethe fact that you were doing it internally, when there was no great logical reason to, when most of the people there didnt work for canonical...is...odd.12:12
Hobbseeat least, i think msot of the people there didnt work for canonical12:12
cjwatsonsabdfl: I'm not sure this is the right place, but I would like to investigate the possibility of documenting the broad outline publicly in order to be able to take advantage of points where we're currently pressed for effort on staff and there are community members want to help, even if many of the specifics are private12:12
mdzHobbsee: it was no better for Canonical; there are no secrets there.  we are always rushed to prepare for UDS after the release, and this was no exception.  I do intend to improve that process this time around12:12
imbrandonright but how do we get rid of the "feeling" that there is a core-dev and canonical-core-dev12:12
sabdflcjwatson: sure, and i do trust your judgement12:12
Hobbseemdz: of course, if you're prepared to open it up, there are probably people who are interested in helping you, who like doing that kind of stuff.12:13
cjwatsonsabdfl: perhaps I can put something together and run it by you?12:13
Hobbseeif you trust them.12:13
mdzHobbsee: it's not as if the UDS schedule was secret until then; it simply didn't exist yet12:13
Mithrandircjwatson: maybe expanding the release checklist to include bits we want to be sane for the milestones too?12:13
sabdflthink of it this way - one of the things canonical brought to the distro world was hard release timing, and that's still a company competence12:13
Hobbseemdz: it somewhat existed.  i know, as i grilled Riddell over what was there.12:13
mdzit required all of the specs to be registered in launchpad, prioritized, etc. before we could generate it12:13
Hobbseesabdfl: of course.  i understand that.12:13
sabdflso, we make a choice to do some of that work ourselves, to preserve the feeling that we're damn damn good at it12:13
Hobbseemdz: wouldnt it have been more helpful if people could have subscribed to all their spects early, so you could have run your autogenerator a bit earlier?12:13
sabdflHobbsee: what do you consider the big challenges on the free software desktop?12:14
Hobbseeooh heck.12:14
Hobbseehmmm....12:14
cjwatsonHobbsee: it was public from at least the 3rd, but we just hadn't had time to go through and register the specs; I think this is a matter of organisation rather than Canonical vs. Ubuntu, though I grant you the point that it would have been helpful to do it earlier12:14
mdzHobbsee: yes, it certainly would12:14
Hobbseecjwatson: bear in mind, i left on the 3rd.  and your third was my 4th.  timezones suck.12:14
Hobbseecjwatson: i understand your point, i'm not trying to grill you on it12:14
mdzbut I agree with Colin, "UDS could be better organized" isn't a Canonical vs. community issue12:15
mdzI've been thinking of writing a document explaining in more detail the relationship between Canonical and Ubuntu12:15
mdzso that it's easier to understand the role that we play and how to interact12:15
Hobbseesabdfl: actually getting it into schools, universites, etc, so people can play with it.12:15
mdzHobbsee: if a community member had volunteered to organize UDS, I would have welcomed them with open arms :-)12:16
sabdflfrom a -core-dev point of view, how can we help that process?12:16
Hobbseesabdfl: a couple of years ago, the only thing i knew about, open-source wise, was firefox.  and then it lead from there.12:16
Hobbseemdz: did you actually say that you would have welcomed input from them?  if the answer is no, then people would have expected that that was a canonical thing, so they couldnt do it.12:16
mdzHobbsee: and I'd like to fix that problem at its root, rather than explicitly saying "yes, you *can* do <most everything>"12:17
Hobbseesabdfl: i'm not sure, to be honest.  hmmm...i suspect edubuntu's going to be your key progress there, for all the new users.12:17
mdzthe assumption shouldn't be that you can't12:17
Hobbseemdz: true.  to us, you're a company, so we only expect to be able to do the things that you make public to us.12:17
Hobbseebecause we wouldnt be able to help out in a normal company like this12:18
Hobbseeyou guys are open, and it's great.  it's still surprising me, tbh.12:18
mdzHobbsee: but Canonical isn't Ubuntu.  Community members hold positions all over, including this very technical board12:18
MithrandirHobbsee: but it's an ubuntu event, not a canonical event, so people should feel empowered to help.12:18
Hobbseemdz: indeed.  perceptions vs reality.12:18
mdzperhaps that's the root12:18
HobbseeMithrandir: sure, but canonical is organising it.12:18
Hobbseemdz: i'm convinced it is.  or at least one of them.12:19
sabdfli'd be happy to have an ubuntu-conf team12:19
sabdflthat's a great idea, actually12:19
Mithrandirso the question is, how can we drag more community people into helping organise it?12:19
mdzCanonical created Ubuntu, but from the very beginning, it was established as a community project12:19
HobbseeMithrandir: by doing as you did in yesterday's meeting12:19
KeybukMithrandir: s/drag/encourage/12:19
mdzwith its own governance and openings for participation all over12:19
Hobbsee"who's interested in doing this?" - especially if you add that you dont ahve to be a canonical employee to do it12:19
mdzCanonical does a lot of the heavy lifting, including most of the things that aren't as much fun as contributing at one's leisure :-)12:20
Hobbseemdz: of course, but we all understand that there's various private stuff involved, and so if it looks private, not to touch it.12:20
MithrandirHobbsee: ok, so we should try to be more explicit about "this is going to happen in six months, if you want to help organise, tell us"?12:20
sabdflthe next summit will be a good opportunity to do better on this front12:20
HobbseeMithrandir: exactly12:20
imbrandoni think just the fact it is a company that started it you *have* to point somethings out explisitly12:20
HobbseeMithrandir: and we need help in ways x, y, z12:20
sabdfland now is a good time to discuss it, since we're just gearing up to arrange it12:20
Hobbseewell, i wont be there.12:20
Hobbseeunfortunately12:21
Hobbseeunless something really big happens and the world explodes.12:21
mdzwhich is why we go to such lengths to make it possible to at least stay informed and participate without attending UDS12:21
Hobbseebut yes12:21
cjwatsonactually, it would be worth having somebody who isn't going to be there on the team to ensure that we think about other people who aren't12:21
cjwatsonalthough I realise that's less of an appealing prospect than helping with a conference you *will* be at12:21
Hobbseemdz: that has improved this time, i think.12:22
cjwatsonHobbsee: at this point, what specific things have you needed to touch but been unable to due to not being in core-dev?12:22
Hobbseemdz: there was more of a perception of "ooh, i wonder what's on today", as opposed to a "oh, paris UDS is on.  so what.  we wont speak to any of those people for the week"12:22
Hobbseecjwatson: kde, mainly.  the seeds i havent looked into, only because i knew it was core dev12:23
mdzHobbsee:  so you stayed in touch with how the community perceived the event, even though you were in attendance?12:23
imbrandonshe touches alot of KDE main with us12:23
mdzthat is challenging12:23
Hobbseecjwatson: i'll probably need it for release management stuff, with the seeds and such.  although ti seems that a lot of permissions are only restricted to -dev now12:24
Hobbseemdz: sure.12:24
Hobbseemdz: i tend to be pretty good at reading people, and i was on irc for a lot of the conference.  particularly when i wasnt in multiple sessions at once.12:24
mdzHobbsee: I didn't even manage to read my email ;-)12:24
Hobbseemdz: yes, but you're mdz.12:25
Hobbseeand one of the conference organisers12:25
Mithrandirmdz: you were everywhere else, though12:25
Hobbseei mean, once the main kubuntu kde4 plan got decided, there wasnt so much kubuntu stuff for me to do12:25
mdzHobbsee: but there are always more things going on12:25
Hobbseeof course12:25
Hobbseei'm not saying i didnt get involved with them - i was more meaning that i didnt have 10 billion sessions in a day to go to12:26
Hobbseewhich i did on teh first day.12:26
Hobbsee3 hours, 4 sessions, iirc, plus the original "welcome" etc ones12:26
mdzwe tried to have some sessions each day for groups which were represented the entire week12:26
Hobbseeit worked well, it really did12:26
mdzKeybuk,cjwatson and I got blisters from shuffling bits of paper12:27
Hobbseeoften we had mornings off, and the community ones were in the latter half of the day12:27
Hobbseeheh12:27
Hobbseeagain, i suspect more people would be happy to help, if they knew you'd accept it12:27
cjwatson( later in the week, it has been proven that people who don't get paid to get up in the morning have a lower rate of doing so ;-) )12:27
mdznext time around, I'd like to do a proper call for topics, have a mailing list for people attending the conference, and generally be more organized about it12:27
Hobbseecjwatson: haha.  true that.12:28
cjwatson(by Friday, I wouldn't have been up for 9 sharp had I not had to be ..)12:28
=== Hobbsee made it every single morning. even if she brougth breakfast down with her!
Hobbsee:P12:28
mdzHobbsee: so you think I should send out a call saying we're looking for volunteers to help organize UDS?12:28
Hobbseemdz: yes.12:28
Hobbseestick it on the mailing list that you're going to create about UDS organisation.12:29
Hobbseethey did that for ubucon.12:29
mdzubuntu-devel-summit12:29
Keybukcjwatson: I would rephrase that as "people who aren't at risk of not being paid" ;)12:29
mdzok, I'm out of time here12:29
HobbseeKeybuk: haha12:30
mdzsabdfl seems to have fallen off the network and only just now reconnected12:30
=== sabdf1 [n=sabdfl@yttrium.canonical.com] has joined #ubuntu-meeting
mdzKeybuk: any further questions for Hobbsee?12:30
sabdf1hi, sorry, network issues12:30
sabdf1from my side, +1 for Hobbsee on -core-dev, with thanks for a wonderful contribution to date and congrats on the speed at which she has made a big impact on an already-big project12:30
Keybukwifi signal is clearly weak in the "West Core" of Millbank12:30
Hobbseesabdf1: you havent suddenly moved to australia, have you?12:30
sabdf1Hobbsee: spiritually, perhaps12:30
imbrandon:)12:30
Hobbseeat least my wifi's not disconnecting every 30 mins again12:30
Keybukmy panel just crashed12:31
MithrandirHobbsee: shh, don't remind it.12:31
Keybuknm-applet seems to have caused it12:31
Keybukfreaky12:31
=== Hobbsee wont curse $isp then
Hobbseeheh12:31
Keybukanyway, unreserved +1 from me#12:31
mdz+1 from me, you've made sustained contributions of excellent quality and are clearly taking an interest in moving the project forward through activities beyond packaging12:31
Hobbseemdz: sabdf1: there are people who will offer you this kind of feedback, i suspect.  i'm one.  but only if you want it, and go asking for it.12:31
mdzHobbsee: congratulations and welcome12:32
Hobbseeseeing as talking to busy people == bad, as it's disrupting them.12:32
Hobbseethankyou :D12:32
mdzKeybuk: will you do the honors in LP and email?12:32
imbrandoncongrats Hobbsee :)12:32
mdzI'm late12:32
Keybukyup12:32
sabdf1Hobbsee: we specialise in being disrupted round here ;-)12:32
mdzthanks12:32
=== mdz [n=mdz@yttrium.canonical.com] has left #ubuntu-meeting ["Ex-Chat"]
sabdf1disruptive, too, i hope!12:32
Hobbseesabdf1: true that.  but you're big and scary, as is mdz.12:32
MithrandirHobbsee: woo, congrats!12:32
imbrandonheh12:33
Hobbseesabdf1: i took a big chance in actually saying "i'm interested in RM" for eg, knowing that i wasnt employed by you.12:33
dholbachcongratulations Hobbsee!12:33
=== dholbach hugs Hobbsee
seb128Hobbsee: congrats ;)12:33
=== Hobbsee hugs dholbach
Hobbseehehe, here are all the lurkers :)12:33
sabdf1Hobbsee: have confidence. you're smart and sane, and make a great contribution, you have a vote and you have credibility12:33
Hobbseesabdf1: :)12:33
Hobbseesabdf1: of course, where to put that feedback to is an interesting question12:33
sabdf1thanks for being part of the project, and it's your project too12:33
Hobbseeand which particular feedback you want, too12:33
Hobbsee:)12:33
shawarmaHobbsee: Congrats!12:34
Hobbseewhich reminds me, i need to whine at the CC :P12:34
sabdf1Hobbsee: i want feedback on the things you care most about, though i hope you understand that i can't always act in the way you might want12:34
sabdf1well done12:34
=== sabdf1 [n=sabdfl@yttrium.canonical.com] has left #ubuntu-meeting []
=== Hobbsee nods
asacHobbsee: congratulations12:35
=== ogra hugs Hobbsee
=== Hobbsee hugs ogra
ografinally12:35
ogra:)12:35
Hobbseehehe12:35
Hobbseei was just going to never go for it again, you know...12:35
Hobbseeonce bitten, twice shy...12:35
ograheh12:35
=== Mithrandir is happy he pushed Hobbsee over the edge, then
MithrandirHobbsee: maybe you didn't, but others wanted you to. :-P12:36
Hobbseehehe12:36
Hobbseeyes....12:36
Hobbseethey'll keep...12:36
=== Hobbsee sharpens the axe...
ograMithrandir, well done :)12:37
=== seb128 [n=seb128@ubuntu/member/seb128] has left #ubuntu-meeting ["Ex-Chat"]
=== bluekuja [n=andy@ubuntu/member/bluekuja] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F7423E.versanet.de] has joined #ubuntu-meeting
=== anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-meeting
=== pochu [n=emilio@155.Red-88-23-230.staticIP.rima-tde.net] has joined #ubuntu-meeting
=== Dayylin [n=dayylin@dsl-216-227-91-136.fairpoint.net] has joined #ubuntu-meeting
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-meeting
=== rraphink [n=raphink@wormhole.x-echo.com] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== MarkusT [n=tsb@sethi-hosting.de] has joined #ubuntu-meeting
=== MarkusT [n=tsb@sethi-hosting.de] has left #ubuntu-meeting []
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== Martinp23 [n=Martinp2@wikimedia/Martinp23] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== freeflying [n=freeflyi@123.116.98.63] has joined #ubuntu-meeting
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-meeting
=== bluekuja [n=andrea@ubuntu/member/bluekuja] has joined #ubuntu-meeting
=== j_ack [n=jack@p508DBE55.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== luigifab [n=fabrice@dyn-88-123-131-221.ppp.tiscali.fr] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:40:213:2ff:fe05:abdb] has joined #ubuntu-meeting
=== luigifab [n=fabrice@dyn-88-123-131-221.ppp.tiscali.fr] has left #ubuntu-meeting []
=== DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== lfittl_ [n=lfittl@2001:6f8:107e:40:213:2ff:fe05:abdb] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:40:213:2ff:fe05:abdb] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== Lure_ [n=lure@external-1.hermes.si] has joined #ubuntu-meeting
=== elkbuntu [n=melissa@ppp30-116.lns1.syd6.internode.on.net] has joined #ubuntu-meeting
=== DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-meeting
=== nixternal_ [n=nixterna@ubuntu/member/pdpc.active.nixternal] has joined #ubuntu-meeting
=== AndyP_ [n=andyp@cpc3-cwma2-0-0-cust15.swan.cable.ntl.com] has joined #ubuntu-meeting
=== gpocente1 [n=gauvain@69.60.114.100] has joined #ubuntu-meeting
=== bashelie1 [n=bashelie@193.34.16.167] has joined #ubuntu-meeting
=== ajmitch_ [n=ajmitch@port166-123.ubs.maxnet.net.nz] has joined #ubuntu-meeting
=== Riddell [i=jr@kde/jriddell] has joined #ubuntu-meeting
=== BlueT_ [n=matthew@blog.psinfo.com.tw] has joined #Ubuntu-Meeting
=== neversfelde [n=neversfe@nrbg-4db4408f.pool.einsundeins.de] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== txwikinger [n=txwiking@sblug/member/txwikinger] has joined #ubuntu-meeting
=== hagi [n=hagi@adsl-84-227-86-79.adslplus.ch] has joined #ubuntu-meeting
=== mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F7423E.versanet.de] has joined #ubuntu-meeting
=== cyphase [n=cyphase@c-76-102-74-27.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== dholbach_ [n=daniel@i59F7423E.versanet.de] has joined #ubuntu-meeting
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== rtg_ [n=rtg@rtg.theglobal.net] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== ExpresS [n=chris__3@dyn-91-168-162-220.ppp.tiscali.fr] has joined #ubuntu-meeting
=== finalbeta [n=gggggggg@d54C6865D.access.telenet.be] has joined #ubuntu-meeting
=== j_ack [n=jack@p508DBE55.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== profoX` [n=wesley@d54C0E764.access.telenet.be] has joined #ubuntu-meeting
=== finalbeta [n=gggggggg@d54C6865D.access.telenet.be] has joined #ubuntu-meeting
=== bashelier [n=bashelie@193.34.16.167] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
=== bashelier [n=bashelie@193.34.16.167] has left #ubuntu-meeting []
=== slackwarelife [n=slackwar@host79-118-dynamic.56-82-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== Susana_ [n=Susana@bl6-9-106.dsl.telepac.pt] has joined #ubuntu-meeting
=== Lure_ [n=lure@89-212-19-55.dynamic.dsl.t-2.net] has joined #ubuntu-meeting
=== Lure_ [n=lure@89-212-19-55.dynamic.dsl.t-2.net] has joined #ubuntu-meeting
=== lionel [n=lionel@ip-61.net-82-216-103.rev.numericable.fr] has joined #ubuntu-meeting
=== bashelier [n=bashelie@193.34.16.167] has joined #ubuntu-meeting
=== doko [n=doko@dslb-088-073-071-104.pools.arcor-ip.net] has joined #ubuntu-meeting
=== ompaul [n=ompaul@freenode/staff/gnewsense.ompaul] has joined #ubuntu-meeting
=== DarkSun88 [n=Ma@ubuntu/member/darksun88] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== shawarma [n=sh@atlas.linux2go.dk] has joined #ubuntu-meeting
=== BuffaloSoldier [n=firdaus@ubuntu/member/BuffaloSoldier] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:30:216:36ff:fe17:3cef] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:30:216:36ff:fe17:3cef] has joined #ubuntu-meeting
=== juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting
=== mars [n=mars@AMarseille-156-1-44-174.w90-27.abo.wanadoo.fr] has joined #ubuntu-meeting
=== rpereira [n=rpereira@ubuntu/member/rpereira] has joined #ubuntu-meeting
=== wsjunior [n=wsjunior@164.41.9.10] has joined #ubuntu-meeting
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== DarkSun88 [n=Ma@ubuntu/member/darksun88] has left #ubuntu-meeting ["Sto]
=== sacater [n=sacater@colchester-lug/member/sacater] has joined #ubuntu-meeting
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== finalbeta [n=gggggggg@d54C6865D.access.telenet.be] has joined #ubuntu-meeting
=== j_ack [n=jack@p508dbe55.dip0.t-ipconnect.de] has joined #ubuntu-meeting

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!