/srv/irclogs.ubuntu.com/2008/11/13/#ubuntu-meeting.txt

=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 13 Nov 12:00: Mobile | 13 Nov 12:00: Ubuntu Mobile Team | 13 Nov 13:00: Desktop Team | 13 Nov 14:00: Ubuntu Java | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council
=== bazhang_ is now known as bazhang
=== doko_ is now known as doko
=== lionel_ is now known as lionel
=== schily_ is now known as schily
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Mobile Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 13 Nov 12:00: Ubuntu Mobile Team | 13 Nov 13:00: Desktop Team | 13 Nov 14:00: Ubuntu Java | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Ubuntu Mobile Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 13 Nov 13:00: Desktop Team | 13 Nov 14:00: Ubuntu Java | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council
davidm#startmeeting12:02
MootBotMeeting started at 06:02. The chair is davidm.12:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]12:02
davidmStevenK, persia lool ogra everyone here?12:03
* persia waves12:03
* ogra wiggles his hand in the air12:04
* StevenK shores12:04
* persia is broken, and retreats12:05
davidmHa12:05
loolhry12:05
davidmOK were are all here and accounted for :-)12:06
davidmWell sort of anyway, I'm on my first cup of coffee12:06
davidmhi amitk12:06
amitkhi davidm12:06
StevenKOkay, so we have persia, me, ogra, amitk and about 1/3rd of davidm12:07
lool...12:07
* persia completely failed to actually edit the agenda before the meeting, but wants to talk about using a desktop manager12:07
davidmThere ya go12:07
StevenKOh, sorry, lool. :-(12:07
StevenKI missed you in my haste to make a joke12:08
davidmOK we did not have a meeting last week as most were gone holiday, meetings or something eles12:08
davidmThe agenda page is pretty empty today.12:08
jcarpGreetings, is this the correct meeting for Ubuntu Mobile?12:09
persiajcarp, It is.12:09
amitkStevenK: 1/3rd of me too. The other 2/3rds is foraging for food12:09
davidmSo does anyone have anything status wise that is notable?  At this point we really have inports for the most part12:09
StevenKHaha12:09
ograimports, merges, spec writing ...12:09
ograthe usual post release - pre UDS stuff ...12:10
* lool was on VAC and will be away next week as well12:10
loolStevenK: I'm happy to take some merges from you as I don't think I have any remaining; if you have some GNOME-ish stuff in particular12:11
StevenKI've been on VAC for Monday and Tuesday, and working on non-public things for the past two days.12:11
StevenKlool: I suspect most of my merges will go away.12:11
ograwhere will they go then ?12:12
* ogra is in philosophical mood ....12:12
StevenKlool: I just need to look at them12:12
ograwow ... i wish mine were so easy12:12
ograbut moode ist that easily scared ... i guess i have to touch it (kees asked me to merge it)12:13
ogra*moodle12:13
davidmThen we have merges under control.12:14
davidmLets talk about UDS then quickly, do we have all spec's in place for UDS?  amitk do you have any input for UDS for us?12:15
* ogra hasnt set up the blueprints yet ... will do that on the weekend12:15
loolI think people have been thinking about specs, or discussions, but we need to make blueprints out of them12:15
amitkdavidm: i'd like to know what devices we should support out-of-the-box and what is broken in them12:15
ograblueprints and at least empty wikipages12:16
StevenKI need to sort out specs12:16
loolamitk: For now, I think we should revisit the jax10 and Q1U with jaunty and sum up what we miss12:16
* persia should write some specs as well12:16
amitkdavidm: eeePC, samsung Q1, jax1012:16
amitketc.12:16
* persia hopes the D4 can make that list12:16
amitklool: ack12:17
ograyes, we should look at eee12:17
ograbut we dont have HW in the team afaik12:17
loolAt least the jax10 needs quite some work, not all trivial12:17
davidmThat is a good question we should have some review of that at UDS, with an eye to what can really be supported.12:17
ian_brasilgps would be nice too12:17
loolI had in mind that we could have some wiki page per device with the main status for some support12:17
persiaPerhaps a session "Bring your MID or UMPC for review"?12:17
loole.g. bluetooth: works, wifi: restricted etc.12:18
loologra: You mean for the d4?12:18
persiacgregan had started something like that.  I'll see if I can find it, and move it to the right place.12:18
davidmpersia, thanks12:18
amitklool: I did such a page for a laptop-enabling here: https://wiki.ubuntu.com/AmitKucheria/LaptopEnablingOnHardy12:18
loolSince I'm subscribed to umpcportal, I saw a bunch of jax10 devices come out12:18
ogralool, for eeePC12:19
loolamitk: Cool; also, I wonder whether we should also provision some hardware support db12:19
loologra: Indeed12:19
ogralool, they are differing massively between the models :/12:19
davidmOK who is going to run with this for a spec and blueprint?12:19
StevenKpersia: I like it!12:19
loolHmm I'd like to understand better how this would work as a spec or blueprint12:20
davidmI like the original question, what devices are we supporting out-of-the-box12:21
davidmso we can come away with a target for JJ12:21
ograyeah12:21
persiaWell, it make sense as a session, and we can review what works and doesn't for each candidate HW, and then decide what needs fixing.12:21
amitkdavidm: and a list of bugs to fix12:22
persiaThe blueprint/spec probably has to be written post-session.12:22
persiaamitk, We can file the bugs in the session :)12:22
ograthe "Mobile BYO HW session" ?12:22
loolSo, if I take that into a session description: "Discussion on hardware support status for misc devices"?12:22
davidmlool, that seems to make sense to me12:23
loolOr is this about allocating time to support some devices, or about ways in which we should track hardware support status?12:23
persiaProbably worth adding a note somewhere that people should bring hardware.12:23
StevenKIt isn't so much a spec, though12:23
loolOk; hardware support status/testing hackfest session so to speak12:23
StevenKIt's more a roundtable12:23
* persia thinks it's about understanding what isn't supported so sensible allocation of resources can be made for makeing more work12:23
amitklool: "misc" devices? I would like a list of "first-class" devices12:23
persiaamitk, "first-class" would be the most popular of those brought to the session, no?12:23
loolamitk: I think your question lead to proposing a session for a similar question12:24
amitkpersia: no. you have obscure devices that are not available in most other parts of the world :-p12:24
loolamitk: In the end, we need to decide which devices we focus our efforts on12:24
persiaamitk, Well, that probably means I don't get "first-class" then (as much as I wish it were otherwise)12:24
amitkI am suggesting picking 3-4 of the most popular devices out there and supporting them12:24
davidm[action] davidm to add session for UDS on "Discussion on hardware support status for devices roundtable."12:24
MootBotACTION received:  davidm to add session for UDS on "Discussion on hardware support status for devices roundtable."12:24
loolConstrained with availability of the devices and time12:24
davidmOK I think we can work with this off-line to develop the topic12:25
davidmpersia, you had a topic you wanted to cover?12:25
persiaYes.12:26
persiaI want to switch MID to use a desktop manager for the session, rather than /etc/event.d/session12:26
ograhe wants to hire a desktop manager :)12:26
persiaInitial fiddling about with xdm is promising, but I wondered if others felt we ought use gdm or something.12:26
loolpersia: a desktop or display manager?12:26
ograhow well/bad supported is xdm ?12:26
persiaMaybe "display manager".  I'm not sure.12:27
ograthe latter :)12:27
ograi dont think xdm gets much attention anywhere12:27
ogranot even upstream12:27
persiaogra, It's in universe, but comes from the X sources, and is part of the ubuntu-desktop task.12:27
ograbut gdm is becoming a bad beast12:27
ograthe new gdm will run its own user session, fire up NM and GPM12:28
persiagdm just seems a little heavy for -mid, and I'm not sure if I can customise the session in a way that doesn't break anything else.12:28
ograand GSS12:28
ograin that state it wont be suitable for MID at all12:28
davidmpersia, for the record, why do would we want to switch from /etc/event.d/session to a  desktop manager?12:28
davidmYour thoughts behind this?12:28
davidmSo other folks looking in can understand12:28
loolpersia: I think Colin mentionned a lightweight display manager used for some project; it's really a dummy one12:29
loolpersia: But more importantly, I'm fine with the idea but would like to document the rationale behind it12:29
persiadavidm, Several benefits: it allows usernames other than "ubuntu", it allows several users, it allows use of oem-setup, it reduces race conditions, and it helps reduce the number of "touching this crashed X" bugs.12:29
ograits not hard to write a display manager either12:29
ograi wrote the first iteration of ldm over a weekend for ltsp12:30
loolI disagree with the first reason, find the second one not so important and think we should fix the fourth reason12:30
ograthe thing is that we want the functionallity, not necessarily the display manager itself12:30
persialool, something like slim?12:30
loolCould be12:30
loolI can tell that it would allow switching between environments/sessions12:30
persialool, OK.  First reason is that it's a simple way to implement it :)  There are other ways.12:31
loolAnd it would setup CK more elegantly12:31
loolI'm not too motivated with the multi-user use case, but I don't mind12:31
StevenKPersonally, I would prefer it.12:32
StevenKIt would save us a bunch of headaches12:32
* ogra wonders if slim or any other lightweight DM would actually help with any of that12:32
ogra(CK, PK etc i mean)12:32
ograi doubt they actually follow that concept closely12:33
ograit would mean much hackery on our side if they dont12:33
loologra: I think the DM I discussed with Colin was actually a proposal to fix CK support, but I might not recall exactly the motivation12:33
persiaogra, So you're suggesting writing a new one rather than extending one of those to do that?12:33
ograpersia, nope12:33
ian_brasilbe nice to start the accessibility layer with the DM too12:34
ograi'm just pointing out that kdm and gdm are currently the only ones giving us what we want out of the box12:34
ograand that if the patching gets to much it might be easier to write our own12:34
ograthat needs to be judged carefully before even starting work12:34
persiaWell, as previously noted, gdm is a little heavy, especially when one considers the future roadmap.12:34
ograright12:34
ograkdm would force qt in12:35
persiaRight, which leaves slim, xdm, wdm, etc.12:35
ograslim is likely not where we need it yet12:35
ogralogin.app (from windowmaker) very likely not either, nor xdm12:35
ograif you want CK and PK support you will need to patch12:36
ograand probably work against upstream12:36
persiaWell, is it worth trying to add CK and PK support to xdm?12:36
loolpersia: I really would like the reasons for using a dm to be crystal clear and solid12:36
loolMy concerns are that it will effectively augment used disk space and boot time12:36
ograsiwthcing environments and proper session handling would be the only reasons i see ...12:37
loolThat's fine if we have good reasons for using one12:37
ograthe latter should be fixable in the session script we use atm though12:37
loolYeah, that's the reason I would have as well12:37
persialool, I can see that.  I'm just trying to make a class of problems go away.  If you think it's really better to implement all of this in /etc/event.d/session, we can do it that way, but I feel that much of the problem is aldeady solved by a display manager.12:37
loolI know using startx breaks a couple of things and bring its own issues12:37
loolAnd switching sessions is desirable given that we have hildon and gnome based sessions12:38
ogralets put a review session on the UDS agenda12:38
ograand lets take a look at the effort involved for each solution12:38
ograand if we would work against upstream or not12:39
ograi imagine windowmaker people dont really desire PK/CK for example12:39
persiaOK.  I'll stop fiddlig with it and just write a spec then.12:39
davidm[action] persia to write a spec for UDS on using a desktop manager for MID12:39
MootBotACTION received:  persia to write a spec for UDS on using a desktop manager for MID12:39
loolI'm fine with the move, but think it's best to have a session on using a dm and which one to use12:40
persiadisplay manager :)12:40
davidm[action] persia to write a spec for UDS on using a display manager for MID (correction)12:40
MootBotACTION received:  persia to write a spec for UDS on using a display manager for MID (correction)12:40
ograyeah12:40
lifeless<troll> I don't know if scott would appreciate being used :>12:40
ograand review pro and con12:40
loolAlso, this will allow covering the two images, how the dm acts with e.g. UNR versus GNOME versus hildon, and will document why we use one12:40
ogralifeless, we're a team, he's alone ... no choice for him, muhahaha12:41
ogralool, for gnome environments we should stick with gdm12:41
davidmSounds good, OK we still have an empty agenda page so does anyone else have a topic for this meeting?  If not I'm inclined to close the meeting12:41
ograif you can run gnome on the HW gdm wont be to fat12:41
ograif you have a MID with 128M wasting 10M for an idling GDM you never use is different12:42
persiaThat's sortable separately, and can wait on the discussion.12:43
ograyeah12:43
loolLet's keep this for the session then?12:43
ograyep12:43
davidmAny additional topics for this meeting?12:44
ograeveryone should take a look at his favorite DM before UDS though :)12:44
StevenKHaha12:44
loologra: You don't want to know12:44
davidmendmeeting going once.........................................................................................12:44
StevenKMy favourite DM is xterm12:44
ograthats not a DM by debian definition :P12:44
* persia used to use emacs as a DM12:44
loolIf I ever tell you what I use, you'll call me partial12:44
ograhttp://packages.debian.org/lenny/x-display-manager12:45
MootBotLINK received:  http://packages.debian.org/lenny/x-display-manager12:45
davidmendmeeting going twice.............................................12:46
* ogra twiddles thumbs12:47
davidm#endmeeting12:48
MootBotMeeting finished at 06:48.12:48
davidmThanks12:48
ograthanks12:48
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Desktop Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 13 Nov 14:00: Ubuntu Java | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council | 18 Nov 16:00: Server Team | 18 Nov 17:00: Kernel Team
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Ubuntu Java Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council | 18 Nov 16:00: Server Team | 18 Nov 17:00: Kernel Team
=== Sp4rKy_ is now known as Sp4rKy
persiaWho's here for the Java meeting?14:06
* persia cancels the Java meeting for lack of attendance.14:23
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Ubuntu Java Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council | 18 Nov 16:00: Server Team | 18 Nov 17:00: Kernel Team | 19 Nov 17:00: QA Team
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 Nov 02:00: Americas Regional Board | 18 Nov 11:00: Community Council | 18 Nov 16:00: Server Team | 18 Nov 17:00: Kernel Team | 19 Nov 17:00: QA Team | 19 Nov 18:00: Platform Team
=== thunderstruck is now known as gnomefreak
=== thekorn_ is now known as thekorn
=== vorian is now known as stevie
=== njpatel is now known as njpatel_away
=== stevie is now known as vorian
=== njpatel_away is now known as njpatel

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