/srv/irclogs.ubuntu.com/2006/04/04/#ubuntu-meeting.txt

=== teknicaL [n=Admin@c-68-46-127-247.hsd1.pa.comcast.net] has joined #Ubuntu-meeting
=== zorba64 [n=zorba64@dsl-210-211-115-140.qld.veridas.net] has left #ubuntu-meeting []
=== teknicaL is now known as tekN1X
=== Jozo__ [i=jozo@viola.uninea.fi] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== Burgwork [n=corey@ubuntu/member/burgundavia] has left #ubuntu-meeting ["Leaving"]
=== Jozo_ [i=jozo@viola.uninea.fi] has joined #ubuntu-meeting
=== tekN1X is now known as teknic[a] L`AwAy
=== poningru [n=poningru@n128-227-55-122.xlate.ufl.edu] has joined #ubuntu-meeting
=== j_ack [n=nico@p508D9211.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== ealden [n=ealden@203.76.211.214] has joined #ubuntu-meeting
=== Ap4ch3 [n=coco@appleboy.claranet.co.uk] has joined #ubuntu-meeting
=== Ap4ch3 [n=coco@appleboy.claranet.co.uk] has left #ubuntu-meeting ["Leaving"]
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== dark_light [n=dark@20132191161.user.veloxzone.com.br] has joined #ubuntu-meeting
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: Dapper Development Status | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 30 Mar 16:00 UTC: Edubuntu Cookbook | 31 Mar 21:00 UTC: Documentation Team | 03 Apr 09:00 UTC: Community Council | 05 Apr 12:00 UTC: Edubuntu | 05 Apr 14:00 UTC: Xubuntu
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-meeting
=== dholbach [n=daniel@i577B061C.versanet.de] has joined #ubuntu-meeting
=== pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-meeting
mdzgood morning all03:57
dholbachhey mdz03:57
=== fabbione waves
pittiJaneW: there now - sort of03:58
mdzKamion,mvo,doko,infinity,Riddell,Mithrandir,iwj,Kinnison,BenC,ogra,JaneW: ping03:58
=== infinity [n=adconrad@loki.0c3.net] has joined #ubuntu-meeting
Kamionhere03:58
dokogood morning03:58
Kamioniwj is on holiday03:58
Riddellpong03:58
mdzright, so he is 03:58
=== seb128 thinks that's a stupid slot to have a meeting :p
mdzas is Keybuk03:58
mvohello03:59
=== Kinnison is here
=== sistpoty [n=sistpoty@ubuntu/member/sistpoty] has joined #ubuntu-meeting
mvoogra is not here for important personal reasons04:00
mdzI thought he retracted that04:01
mdzSMSed Mithrandir, JaneW, BenC04:01
KamionI suspect ogra has a good excuse if he doesn't make it, anyway.04:02
dholbachMithrandir was replying on IRC some minutes ago04:02
mdzKamion: indeed04:02
MithrandirI'm here04:02
mdzdholbach: would you ring JaneW and BenC? we'll need to start without them04:04
mdzRiddell: you're up first04:04
dholbachmdz: right04:04
Riddelldone:04:04
Riddell kde espresso syncing with gtk frontend04:04
Riddell kde 3.5.2, qt 3.3.6, amarok 1.3.9 uploaded04:04
Riddell flight 6 testing and CD resizing04:04
Riddellnext week04:04
Riddell flight 6 then solid kde espresso hopefully04:04
mdzRiddell: how is kde espresso overall?04:04
mdzI haven't had a chance to try it yet04:04
Kamionnor I, not since the UI sprint04:05
mdzany regressions in 3.5.2?04:05
Riddellstill a long TODO list, but should be in a decent shape for beta release time04:05
=== whiprush [n=jorge@64.62.190.212] has joined #ubuntu-meeting
Riddellonly 1 minor problem in kdeartwork, overlapping files04:05
mdzgood04:05
mdzwhat's happening with kubuntu-documentation?04:05
dholbachnarf, our wiki hates me, I'll keep trying04:05
Riddellthere's been some god activity on the desktop guide, but I should upload an updated version soon04:06
dholbachah ok04:06
mdzok04:06
mdzthanks04:06
mdzseb128: ready?04:06
seb128this week: bug triage and fixing04:06
seb128next week: keep on bug triage and fixing04:06
mdz:-)04:07
seb128:)04:07
mdzhow long is the bug list?04:07
mdzhave the bug days helped?04:07
mvolol04:07
seb128you don't want to know about the list :p04:07
=== mvo loves this status update
mdzI do04:07
seb128it doesn't go down 04:07
seb128the previous bug day has been nice04:07
mdzseb128: is gnome .2 scheduled yet?  will we have another point release for dapper?04:07
seb128and there is some new active people04:07
JaneWargh - sorry....04:07
seb128yeah, .2 is somewhere during may04:08
mdzoh good04:08
seb128let me look at it04:08
mdzlet me know when there is a fixed date04:08
seb128bug days could use some extra distro team people out of dholbach and me04:08
dokoseb128: no more pango updates please ;)04:08
mdzI think we should have a bug day where the entire team participates04:09
fabbionelike tomorrow?04:09
seb128 May 29th04:09
seb12804:09
seb128GNOME 2.14.2 Tarballs Due04:09
seb12804:09
seb128May 31st04:09
seb12804:09
seb128GNOME 2.14.2 Stable Release 04:09
fabbionefor the X HUG DAY?04:09
seb128according to http://live.gnome.org/TwoPointFifteen04:09
mdzseb128: argh, bad timing04:09
=== Kinnison would be pleased to do a long stint on tomorrow's bug day if that would be helpful
mdzsure, tomorrow.  I think everyone will be here except iwj04:09
dholbachmdz: benC said he was in connecticut and was taking a day off today and tomorrow04:09
dholbachmdz: and he had notified you04:10
MithrandirI'll be busy shoving flight-6 out the door, but if you lot are busy triaging bugs, that sounds good.04:10
infinityBenC's bug list is generally so drastically different from everyone else's that he may not derive much value from a bug day anyway.04:10
mdzdholbach: right, ok04:10
mdzso no BenC for bug day tomorrow04:10
Kamioninfinity: it would probably be useful for somebody to teach the bugsquad how to triage kernel bugs04:11
mdzhe can attend the next one04:11
Kamionif installer bugs are anything to go by, they will need training04:11
mdzbut let's all join in tomorrow04:11
infinityKamion: It could be, but it takes a certain knowlege of the kernel before you can even begin.04:11
dholbachbut adding stuff to wiki.ubuntu.com/DebuggingProcedures might be a good start (anyway)04:11
mdzinfinity: they can at least learn what information is needed and help getting reports fleshed out04:12
=== JaneW as an update from sivang
infinitymdz: True that.04:12
mdzJaneW: saw it already04:12
JaneWmdz: ah right. ok04:12
mdzthanks seb12804:13
mdzpitti: ?04:13
pittireducing-duplication:04:13
pitti * talked with Adam about php5-sqlite; package will be split off to universe04:13
pitti * TODO: check with seb128 about getting rid of gtk+1.2 (quite many packages still use it)04:13
pittiDB2 packaging:04:13
pitti * DONE:04:13
pitti   - automatic instance setup04:13
pitti   - reasonable package splitting (server, dev, gui, doc, l10n, metapackage for everything)04:13
pitti   - integrated DAS startup/shutdown04:13
pitti   - Java SDK deb from the bundled IBM JDK and integrate the GUI stuff to work OOTB04:13
pitti   - proper package descriptions04:13
pitti   - got many hints and a lot of testing help from sivang04:13
pitti   - checked status with mdz, packaging features are deemed sufficient for now04:13
pitti   - sivang ran officla certification test suite, passed; I have the logs04:13
pitti * TODO: fix some packging issues (mainly daemon stopping and cleaning on purge)04:13
pittigeneral stuff done this week:04:13
pitti * brought language pack imports up to date, fixed import bugs04:13
pitti * bug triage from hell (sub'ed to many packages and cleaned up bug reports)04:13
pitti * bug fixing, mostly in Utopia related stuff04:13
pittiplan for next week:04:13
pitti * finally dive into triaging printing bugs04:13
pitti * cupsys 1.2 final is about to be released, upstream did a ton of bug fixes since our current snapshot; evaluate svn commit changelog for new features, test current RC1 whether it breaks stuff (further :/), ask for UVF exception if appropriate04:13
pitti * CD/espresso testing04:13
pittisorry, bit longish04:13
mdzpitti: are rosetta updates flowing smoothly now?04:14
Mithrandirpitti: can I borrow you for flight-6 testing on ppc tomorrow?04:14
fabbioneMithrandir: i have ppc too if you need04:14
pittimdz: you mean production code updates? 04:14
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
mdzpitti: I mean translation updates via langpacks04:14
pittiMithrandir: of course, full speed for testing and bug triage tomorrow04:14
Mithrandirfabbione: the more the merrier, so sounds good. :-)04:15
pittimdz: ooh, carlos recently started to produce tarballs; I didn't look at them yet, will do ASAP04:15
mdzMithrandir: hmm, flight-6 and bug day both tomorrow?04:15
fabbioneMithrandir: just ping me when it's time04:15
pittimdz: but he fixed the worst bugs recently04:15
Mithrandirmdz: flight-6 was planned for today, but didn't make it.04:15
infinityMithrandir: I'm prepared to shut off the cronjobs on drescher and drive them by hand, if we need fast turnaround time on the archive for Flight releases.  Waiting forever and a day could really tire us out.04:15
mdzMithrandir: what were the showstoppers?04:16
seb128Mithrandir: tomorrow beeing friday for you?04:16
infinitymdz: It's a good match to do them together, since bugs can be triaged without uploads happening. :)04:16
pittiright, and while installs progressing...04:16
Mithrandirmdz: not booting on some amd64s, for instance.04:16
Mithrandirseb128: tomorrow is Thursday.04:16
seb128k, so not the same day as bug day 04:16
fabbioneMithrandir: it is thursday in our TZ :P04:17
Mithrandirfabbione: it's thursday after I've slept.04:17
fabbioneahah04:17
mdzok, so flight-6 thursday and bug day friday?04:17
seb128hum, sleep :)04:17
seb128mdz: correct04:17
mdzgood04:17
mdzthanks pitti04:17
Mithrandirseb128: yes, this thing some of us do, once in a while.04:17
mdzogra: next?04:17
pittimdz: what will happen with db2 now?04:17
mdzpitti: let's talk about it after the meeting04:18
pittimdz: after the packaging fixes?04:18
pittiright04:18
dokopitti: no ooo files in carlos' rosetta export04:18
mdzmvo: next?04:19
mvoDid:04:19
mvo- bugtriage04:19
mvo- work on the dist-upgrade tool, should be in good shape now (polish, ui, better progress reporting, better error recovery)04:19
mvo- debugged/found bug in gksu that caused the debconf-gnome problems of the dist-upgrade-tool (fix in dapper, needs to go into breezy-updates too, send mail to kov about it)04:19
mvo- fontconfig-voodoo/font work,communication (sil)04:19
mvo- work on the gnome-app-install data extractor, fixed various bugs, blacklisted various entries04:19
mvo- smallish bits on the qt-language-selector04:19
mvo- misc stuff, fixes (gdebi, update-manager, software-properties, apt, notification-daemon, synaptic, gnome-app-install, manual upgrade testing)04:19
mvoWill do:04:19
mvo- more bug-fixing/bugtriage04:19
mvo- push for the auto-dist-upgrade test chroot setup04:19
mvo- get the dist-ugprade tool into the archive, my currend idea is to add a "--development" option for people who want to upgrade to the current development release 04:19
Kamionmvo: is that the same gksu problem we encountered on the live CD?04:19
Kamiongksudo didn't work until sudo had been run once, or something like that04:19
mdzmvo: is the upgrade tool firmly in breezy-updates now?  any feedback from that?04:19
mvoKamion: no, this seems to be something different, too clearly cleanup 04:20
Kinnisonmvo: tomorrow can we please go through the bits needed to get the upgrade tool signed on cron.daily?04:20
Kamionmdz: there's a launchpad bug blocking getting python-vte into breezy-updates/main04:20
mvomdz: not in breezy-updates yet (but prepared for it), the missing bit was how to activate prompting for the devel version04:20
mvoI would like to do it with "--developemtn" to only get people using it who can handle a commandline04:21
mdzKamion: do you have a bug numbe?04:21
mdznumber, even04:21
Kamionbug 3602204:21
mvoKinnison: yes, that would be good04:21
mvoKinnison: I talked to elmo about it briefly about it04:21
Kinnisonmvo: let's talk tomorrow and let the meeting continue for now04:22
mvoany objections about the "update-manager --development" approach for prompting for upgrades to a development release?04:22
mdzKamion: ok, will see that it is chased04:22
infinitymvo: Sounds good to me.04:22
Kamionmdz: thanks04:22
mvoit will prompt normally when the official release is out04:22
mdzmvo: how do manual dist-upgrades look so far?  any problems?04:22
mvomdz: no, recent upgrades on i386 look very good04:23
mdzmvo: have you implemented a scheme to allow us to suppress notifications of the availability of dapper+1 to dapper users, per sabdfl's request?04:23
mvomdz: jbailey had trouble last week with amd64 and OO though04:23
infinityI recently dist-upgraded a friend who had ubuntu-desktop, kubuntu-desktop, and a bunch of other crap installed, and it was nearly flawless.  I should try this again and file some bugs on the 2 or 3 issues.04:23
mvomdz: IMHO we need to show notifications for dapper users but offer a way to "don't show this again". because a lot of dapper users will want to upgrade04:23
mdzI saw a conffile prompt in some random X package recently04:23
mvowe should make it clear in the release notes that this is a upgrade to a not 3y support version04:24
mdzmvo: we can argue it later, but need to allow for his request to be satisfied04:24
mvomdz: yes, thanks04:24
mdzmvo: I agree that we should offer "don't show this again" in any case04:24
mdzdo we already have the ability to display a note before the upgrade, where we could explain about the support lifetime etc.?04:25
mvomdz: yes, we display release notes04:25
mvothat is, anything that is in the release notes-uri :)04:26
mdzok, thanks mvo04:26
mdzMithrandir: next?04:26
Mithrandirlast week: finished up the Korean keyboard work, some XKB work, some bug triage.  Also, flight-6 preparations today and tomorrow.  Some espresso hacking too (timezone selector).04:26
Mithrandirnext week: more espresso hacking, popcon, general bug gardening04:26
Mithrandirblocked on: soyuz being slow; see bug 36535.  This is already problematic for flights and will be worse when we get closer to release.04:26
mdzhow is the new xkeyboard-config working out?04:26
Mithrandira bit rough in the beginning, but upstream's responsive and I think we have most of the issues worked out now.04:27
mdzwill follow up with LP on 3653504:27
MithrandirAdam has a bug about building out of incoming too.  If we could get both, I'd be thrilled.04:28
mdzMithrandir: be sure the next Flight announcement includes a note about new X keyboard bits and requests explicit attention to testing04:28
Mithrandirmdz: ok.04:28
mdzbuilding out of incoming is likely to be harder04:28
mdzrolling substantial new features into soyuz is a slow process in production04:28
mdzthere might be low-hanging fruit on performance optimization though04:28
seb128mdz: fixes the issue with GNOME keymaps selections, we got a compose:ralt issue which got worked with upstream and fixed, out of that seems to work nicely04:28
mdzI will speak with kiko04:28
Mithrandirthanks.04:29
Mithrandirseb128: did you get the X parts of that fixed too?04:29
=== Kinnison knows of one bit of low-hanging fruit on the publisher
Kinnisonand can probably come up with one or two speedups04:29
Kinnisonpossibly enough to make 30m cron.dailys reliable04:29
seb128Mithrandir: svu fixed it with xkeyboard-config changes only in fact04:29
Mithrandirseb128: oh, cool.04:29
infinityKinnison: We'd love you forever.04:29
mdzKinnison: please send an email to me+kiko with your ideas to discuss04:30
MithrandirKinnison: that'd be very, very nice.04:30
Kinnisonmdz: Sure04:30
mdzthanks04:30
KamionKinnison: I need to have a clear window where I can manipulate publishing records safely04:30
infinityKinnison: As we approach beta, this will become critical.04:30
Kinnisoninfinity: *nod*04:30
KinnisonKamion: I understand04:30
KamionKinnison: if that window is of the form "it's safe to manipulate publishing records while publish-distro is running", all the better :-)04:30
mdzseb128: you recommend it for breezy-updates as well?04:30
mdzseb128: (assuming feedback from flight 6 is positive)04:30
seb128probably yep04:31
mdzok04:31
infinityKinnison: I'll poke you later with more on this topic, including concerns/feedback from others about same.04:31
mdzthanks Mithrandir04:31
Kinnisoninfinity: thanks04:31
mdzKinnison: next04:31
Kinnisongnome-power-manager (PowerManagementInterface): Rewound a bunch of partial patches to prepare 2.14.0-0ubuntu1 upload for after flight-6. Went through even more bugmail. Scouring of CVS to get a list of changesets for upstream to produce a 2.14.1 release for us.04:31
Kinnisongparted: reviewed patch by dholbach04:31
Kinnisonmetacity: fixed bug in the patch I created last week; continued to chat with upstream about this. They remain unconvinced as yet.04:31
Kinnisonlaunchpad: worked on a test set for the uploader and started to integrate it into the launchpad test suite.04:31
Kinnisonlp-ongoing: I will finish this test suite integration. I imagine there'll be another production rollout soon. 04:31
Kinnisondistro-ongoing: Otherwise continue with gnome-power-manager, acpi related stuff, gparted, etc. I've promised Colin I'll help pick up some espresso UI bits.04:32
Kinnison[end] 04:32
mdzyou're around for bug day, right?04:32
KinnisonYes04:32
mdzgreat04:32
mdzare you tracking acpi/PM/laptop related issues in malone?04:32
KinnisonI am on the bug contacts for acpi-support04:32
Kinnisonand I'm tracking most of them04:32
KamionKinnison: do you need any help from me on the gparted 0.2 merge?04:33
mdzI hear some murmurings about suspend-to-RAM regressions from various people04:33
mdzI don't know whethere they're kernel or userland related04:33
infinitymdz: On upgrades, or fresh installs?04:33
KinnisonKamion: dholbach is doing well on that. Once he has a 0.2.3 I'll review it and test it with my harness04:33
Kamionthere was talk about that being due to the change in the kernel/user memory split; I understood mjg59 was on top of that04:33
mdzinfinity: unclear; is there expected to be a difference?04:33
fabbionemdz: it can make a difference04:33
Kinnisonmdz: I also have "mail mdz+kiko about speedups for publisher" and "work out what building out of incoming would entail"04:34
infinitymdz: Earlier today, a theory was developed that because gfxboot lets you pick a resolution (and then puts that resolution in a vga= line in your bootloader!), people are inadvertently using vesafb where they would previously have has vga16fb.04:34
mdzKinnison: mjg59 doesn't seem to have much time for it these days; if you could chat with him and see if you can help fill in, that would be grand04:34
Kinnisonmdz: I'll add that to my list04:34
infinitys/have has/have had/04:34
Kamioninfinity: that can easily be turned off, if we're confident that nobody will ever need to use vga= to get a visible usplash04:34
infinitymdz: mjg59 did, however, just commit a kernel patch that fixes suspend-to-disk on macihnes with massive gobs of RAM (tested on my 2GB laptop)04:35
mdzKinnison: I fully expected build-from-incoming to be a longer-term thing; don't spend too much time on it right away unless you already know otherwise04:35
Kinnisonmdz: I wouldn't be coding it up, just looking to produce a better estimate of the job04:35
Kinnisonmdz: in case we decide we need it as release approaches04:35
mdzinfinity: perhaps we should disable that04:35
mdzsince it presumably doesn't affect X anyway04:35
mdzKinnison: sure, but it's lower priority than bugs04:36
Kinnisonmdz: noted04:36
pittimdz: btw, it should; it's one of the few ways we could fix the silly default resolution if resolution can't be detected automatically04:36
Kamionmdz: the reason vga= was copied was that it used to be necessary to get a usable console on some machines. Theoretically that shouldn't be the case any more now that we default to 640x40004:36
Kinnisonmdz: where does "speed up publisher" come in my priority list?04:36
pittithat's still an ugly problem we haven't decided on04:36
Kamionpitti: VESA resolutions probably aren't a particularly good set of options for X though04:36
mdzKinnison: mail me your list and I'll sort it for tomorrow04:37
Kinnisonmdz: okay04:37
infinityKamion: Let's continue this bootloader/vga thing out of band.04:37
pittiKamion: maybe, but it's the only input the user can give on the live CD...04:37
infinitypitti: You too. ;)04:37
pittiyes, it's in a bug report, too04:37
mdzpitti,infinity: chat with fabbione about it; he has a todo item for a more graceful VESA fallback04:37
=== fabbione sighs...
fabbioneyeah04:37
mdzthanks Kinnison04:38
mdzJaneW: I think Keybuk has been on vacation for most of the time since the last meeting, any update?04:38
JaneWmdz: no, I'll mail him...04:38
mdzJaneW: nah, as I said I think he was on holiday all but a day or so04:39
mdzKamion: next?04:39
Kamionthat day I think he spent on n-m04:39
Kamionubuntu-express-copy-filesystem: Estimated install copying time fixed.04:39
Kamionubuntu-express-base-system: Timezone defaults fixed. Started in on sorting out network configuration; would have finished this evening but for laptop hardware problems. Looked at apt-setup this morning, but it turned out to be a bit more than the simple job I was hoping, so stepping back for a bit to rethink. Mithrandi04:39
Kamionr's doing timezone->country->locale inferring.04:39
Kamionue-partitioning-tool: Fixed manual partitioner not to assume ext3 (too late for Flight CD 6 though).04:39
Kamionmisc: Various random installer bug fixing. Trying to cope with checking up on all the bugs that triagers are closing for me (not all accurately; installer bugs require different treatment to say desktop bugs because it can be much harder to persuade people to re-test, and bugs are often very hardware-specific).04:39
Kamionnext-week: Bug day tomorrow; perhaps I can do some education on installer bugs. Breezy CD images, this time for real; sorry pitti.04:39
Kamionsorry for screen-induced paste breakage04:39
mdzKamion: what are we doing about network configuration in espresso?04:40
Kamionmdz: I tried to use netcfg, but it's difficult at present because that tries to bring interfaces up and down04:40
mvoKamion: I would be interessted to talk to you about the eta copy time thing later, I did something like it in the upgrader too04:41
mdzthere's an outside chance that NM will happen for the installed system, but we can't count on it04:41
Kamionmdz: so I'm just doing clone-and-hack of netcfg's logic for writing the standard network configuration files, plus copying certain bits from the live filesystem (/etc/network/interfaces mainly)04:41
mdzif we need to remove it from live as well so that we can do network configuration sanely, that's reasonable04:41
Kamionmvo: I doubt it's related - espresso's problem was that it was using cpio for the copy and thus losing track of progress due to buffering on cpio's stdin04:41
mdzis the live boot still configuring interfaces even though we're installing NM?04:42
Kamionmdz: yeah, the disconnect between live and installed is going to be awkward unless n-m remains installed after espresso installs04:42
Kamionmdz: it's doing all the configuration it ever did, i.e. write out auto dhcp stanzas for each interface04:42
Mithrandirmdz: yes, but NM manages those interfaces so it's not harmful.04:42
mdzoh, so NM is ignoring everything on live anyway?  that's less than ideal04:42
Kamionn-m considers stanzas of that form to mean that it can manage the interfaces04:42
Kamionmdz: no04:42
mdzoh04:42
mdzhow clever of it04:43
Kamionthis configuration is probably ok; however if 04:43
Mithrandirnm manages all interfaces on live.04:43
Kamionthe user actually does any meaningful setup with n-m, they'll be a bit surprised that it's no longer available on install04:43
KamionI could perhaps try to detect whether they've fiddled with n-m and if so keep n-m installed, or something04:43
mdzpossibly04:43
infinityGood thing you can't do anything useful with n-m, except for picking a wireless network. :)04:43
infinity(No static IP setup or anything in N-M yet)04:43
Kamioninfinity: WPA configuration now04:43
infinityOh, and that.04:44
mdzthat could be frustrating04:44
Kamionanyway, out-of-band?04:44
mdzyes04:44
mdzwhen Keybuk is back, let's talk about what to do with NM04:44
mdzthanks Kamion04:44
mdziwj has been on holiday...04:44
mdzinfinity: next?04:44
infinitylast week buildd: Sorting out build failures in main, we're now down to exactly one FTBFS package (syck on amd64) which I'm investigating, everything else it up to date.04:44
infinitylast week distro: General bug fixing and bug triaging in packages I maintain, and elsewhere (such as network-manager), preparing for Flight-6.04:44
infinitynext week buildd: More of the same, making sure everything is building, also need to get livefs and security building on hppa/sparc in the DC.  I also need to get MOTU up to speed on their FTBFS issues ASAP.04:44
infinitynext week distro: More and more triaging and bugfixing in packages I maintain solo and in teams, and help Tollef with the Flight-6 release.04:45
infinityNOTE: I don't mind terribly fixing FTBFS bugs, it's a big part of my job, and I'm rather good at spotting build problems, but PLEASE, don't use that as an excuse to not test builds before you upload.  Pretty please.04:45
infinitySCARIER NOTE: Due to unfortunate changes upstream in libmysqlclient15, it would be in our best interest to sync their new (ABI incompatible) version and do a mass rebuild of reverse deps.  This needs discussion.04:45
mdzgreat news on buildability, thanks for that04:45
mdzdo we have a strategy for a test build for dapper?04:45
fabbioneinfinity: +1 on the rebuild04:45
infinityWe should discuss the MySQL thing, I just wanted to toss it out there so people don't freak out when it happens.04:45
mdzinfinity: please send an email re: mysql04:46
infinitymdz: We have no particularly wonderful strategy there yet.  I need to discuss with Kinnison to see if LP can do it for us, and if not, get elmo to set it up in wanna-build.04:46
infinitymdz: Will do.04:46
Kamionubuntu-devel-announce on mysql maybe? (or maybe once we've decided)04:46
mdzinfinity: ok, please start that ball rolling so we don't have to rush later04:46
infinityKamion: I can announce it, but rebuilds are fairly simple, not sure it's worth the hassle.04:46
fabbioneinfinity:  i can do w-b for sparc here. 24 instances of buildd will be way faster than the machines at the DC04:46
mdzKamion: ubuntu-devel and CC me for the discussion; announce once we'v edecided04:46
mdzfabbione: that is a damn fine idea04:47
fabbionemdz: that'd be only sparc tho..04:47
infinitysparc only would catch 99% of the FTBFS bugs anyway.04:47
mdzright, but we have relatively few i386-specific packages and could test them manually04:47
infinityBut it's no hassle to get it going in the DC, really, just need to get elmo to do his end (cut an archive snapshot)04:47
fabbionemdz: can you sponsor a set of earplugs for me, pretty please? :P04:48
infinityI suspect LP isn't ready for us to do these things natively yet.04:48
mdzinfinity: elmo is a busy man04:48
fabbionemdz: but yes we can do it04:48
fabbioneinfinity: you can get console here and go with it04:48
mdzfabbione: noise canceling headphones, you mean ;-)04:48
infinityfabbione: Do you still have a local mirror?04:48
fabbionemdz: exactly04:48
mdzok, thanks infinity04:48
mdzfabbione: next?04:48
fabbioneinfinity: yes04:48
fabbione* server-candy: Missing/buggy: apache2 for "central snakeoil SSL setup" and kernel -server as default from CD install. No other progresses.04:48
fabbione* ubuntu-cluster: Waiting ocfs2-tools release for new userland to sync with the kernel that will allow (finally) full desync later. Release is taking a bit longer, pinged upstream, no answer yet. Got the SAN almost up and running. Missing to configure the 2x2Gb fiber switches and get some controllers around different machines to start testing.04:48
fabbione* last week: X bug fixing/triage/headackes/larting/bashing/killing/... redhat-cluster-suite bug fixing and a bit of sparc bug fixing, got mono working on sparc with David Miller :)04:48
fabbione* next week: bug fixing + X hug day tomorrow. Prepare redhat-cluster-suite breezy-update for a missing init script. Wacom in04:48
fabbioneX needs love very soon (found a can of worm looking at the bugs). Going to announce sparc CDs later today since they have bee04:48
fabbionen finally tested.04:48
fabbione* bug work has bottle necks on malone missing ability to do multiple bug processing. (Discussed with LP people already)04:48
fabbioneinfinity: i have all in the local mirror04:48
=== robertj [n=robertj@66-188-77-153.dhcp.athn.ga.charter.com] has joined #ubuntu-meeting
mdzfabbione: I am following up on your LP requests to assist with X triage04:49
fabbionemdz: yes i saw your first mail, thanks04:49
fabbioneoh i have been a bit sick yesterday04:50
fabbioneotherwise everything is on track04:50
fabbioneX is in bad shape.. we will make it rocking04:50
mdzspoke with kiko at length today and will again tomorrow regarding all of the priority LP activity for us04:50
fabbionein a year or two04:50
fabbionemdz: great thanks04:50
mdzfabbione: we run on 1-hour days, so we should be able to squeeze a year in before dapper ;-)04:50
mdzthanks fabbione04:50
mdzdoko: next?04:50
fabbioneanyway more seriously.. the biggest issue was the ati driver and we got upstream very close to us04:50
doko- toolchain-roadmap: glibc i386 on amd64 fixed, patch comparision (unstable vs. dapper) beeing addressed.04:51
doko- toolchain-roadmap-ng: blocked (Martin Michlmayer and Ben Hutchings did a Debian unstable rebuild with gcc-4.1 on mips and amd64, which is looking good)04:51
doko- openoffice.org: two new locales, bug fixes, finding that we import all message strings as translated into rosetta, en-au dictionary and thesaurus available (jdub, for your slides ;-), working on OOo 2.0.2 packages for breezy (low prio)04:51
doko- other: preparing ttf-dejavu updates, ttf-dejavau font backport, looking for fonts for printing, python-2.4.3 candidate04:51
doko- plans for next week: focus in font/printing bugs and printing related packages04:51
mdzdoko: any particular bug focus for you beyond ooo?04:51
Riddelldoko: is fontforge up to date enough for dejavu?04:51
mdzworking with pitti on printing?04:51
dokomdz: ^^^ font/printing bug04:52
dokosure, working with pitti on this would be good04:52
mdz(in case no one had noticed yet, I sometimes start writing responses before I finish reading the paste, to save time ;-) )04:52
pittiyep04:52
dokoRiddell: any particular reason to ask?04:52
=== fabbione disables mdz's readahead
mdzdoko: you'll be here for bug day?04:52
dokoyes04:52
mdzgreat04:52
Riddelldoko: I remember looking at dejavu earlier in dapper cycle and fontforge wasn't up to date enough for the latest versions04:52
mdzdoko: do rosetta and ooo like each other these days?04:53
dokoRiddell: asking upstream DejaVu04:53
dokomdz: so, so. OOo does copy the english string to the translated string, and rosetta imports that, so we have 100% OOo translations04:54
dokodiscussing with carlos how to solve this04:54
mdzdoko: is there hope to have rosetta import/export for ooo for dapper?04:55
dokono exports for OOo yet; I'd like to have a tarball in the data center, not having to write 20 emails and fetching these via http04:55
infinityAutomation is elation.04:55
dokomdz: the import is working, the workaround for me is to remove the strings, if en-US == translated lang04:56
mdzso we have import but not export04:56
mdzok, running out of time04:56
mdzthanks doko04:56
mdzdholbach: next?04:56
dholbachicon-mission: icon page complete, workflow with art team implemented (apt-ftparchive is unhappy sometimes, need to investigate)04:56
dholbachthis week (done): finished technical aspects of the icon world, *started* catching up with bug triage04:56
dholbachthis week (todo): bug day, more bug triage, catching up with motu uvf04:56
dholbachnext week: bug triage, working on organising the motu dapper fixage04:56
mdzdholbach: where do we stand on sabdfl's icon priorities?04:56
dholbachmdz: you mean the page?04:56
mdzdholbach: I mean actually getting the icons we need from the artist04:57
dholbachmdz: there was no update of Dave yet, he was supposed to report back this week04:57
dholbachI can mail him.04:57
mdzok, please do04:57
dholbachright504:57
mdzok, before we close up04:57
mdzgood news, thanks to elmo, syncs should start happening again very soon04:58
sistpotyyay :)04:58
=== mvo applauds
mdzhow is everyone feeling about the release schedule changes?04:58
dokomdz: on which basis, we did request syncs for specific versions, which are supserseeded in unstable04:58
mdzdoko: I will be reviewing the pending requests with elmo04:59
mdzand will figure out what to do with those04:59
Kamionwe can sync from snapshot.debian.net if need be, I'm sure04:59
KamionI have one other issue04:59
mdzin the coming week I will be pressing hard on bugs, trying to get a handle on what is going on in Malone04:59
mdzworking with kiko to get better reports for us04:59
Kamionbootable Intel Mac CDs require non-root HFS+ writing support04:59
Kamionwe have no way to do this using free software, and even with non-free software we only get formatting, not other writing05:00
JaneWmdz: can I help with that? (bug reports)05:00
mdzJaneW: possibly; ping me tomorrow about it?05:00
JaneWmdz: sure05:00
Kamionif somebody would like to work on this (ideally adding an HFS+ hybrid option to mkisofs), please let me know; otherwise it'll have to wait until later in the cycle when I'm a bit more out from under the espresso mountain05:00
seb128mdz: schedule change will permit to fix a lot of small glitches which is nice05:00
fabbionemdz: i don't mind the change in the schedule, but it might kill my presence at the next spec writing orgy :/05:01
mdzKamion: intel mac support isn't an explicit target for us; it's a nice to have but I'm happy to let it be a later one-off (by us or community-contributed) based on the final dapper CD if necessary05:01
Kamionmdz: we can do one-offs relying on somebody invoking root access to build the HFS+ piece, I *think*05:01
JaneWKamion: can you send me espresso %ages - when the time is more sane please?05:01
mdzKamion: happy to bounty the work if a candidate is available05:01
Kamionalthough haven't tested that theory yet05:01
Kamionbut it's not feasible for autobuilding05:01
mdzok, if anyone has outstanding issues, please mail or call05:02
Kamionmdz: nice-to-have> understand, I just thought I'd mention since an increasing number of people are asking about it05:02
KamionJaneW: yes05:02
mdzit's late for most of you, thanks for staying up05:02
JaneWKamion: ta05:02
mdzgood night all05:02
JaneWThanks everyone, sorry I was late (set the alarm time but forgot to turn it on)05:02
fabbionenight guys05:02
dokogood night05:02
seb128'night05:02
dholbachnight guys05:03
infinity'Night, Europe. :)05:03
=== dholbach stays up
=== fabbione stays up too
pitticu later05:03
=== mvo considers his options
pittithanks everyone05:03
seb128dholbach: you are crazy?05:04
=== Mithrandir goes to bed.
fabbionesleep for one hour to wake up my wife is no option05:04
fabbioneseb128: dude.. i need to take you out partying with me sometime05:04
Mithrandirremember, it's still flight-6 freeze, so please don't upload stuff to main until flight-6 is out.  Which should be in < 12 hours.05:04
dholbachseb128: i couldn't sleep any more, so I got up... I can just stay up05:04
fabbioneseb128: 5am will be the normal05:04
Burgundaviamdz: intel mac is an awesome marketing win05:04
seb128dholbach: good joke05:04
dholbachseb128: I mean it05:05
=== dAndy [i=[U2FsdGV@rita.cat.pdx.edu] has joined #ubuntu-meeting
seb128dholbach: k, I want all the desktop bugs cleaned when I wake up in some hours, start NOW05:05
seb128and have fun :p05:05
=== seb128 goes to sleep
dholbachseb128: sure i'll have fun - sleep tight05:05
=== kyral_ [n=Chris@ubuntu/member/kyral] has joined #ubuntu-meeting
=== infinity [n=adconrad@loki.0c3.net] has left #ubuntu-meeting []
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has left #ubuntu-meeting ["Bye!]
=== sistpoty [n=sistpoty@ubuntu/member/sistpoty] has left #ubuntu-meeting []
=== j_ack [n=nico@p508D9211.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 30 Mar 16:00 UTC: Edubuntu Cookbook | 31 Mar 21:00 UTC: Documentation Team | 03 Apr 09:00 UTC: Community Council | 05 Apr 12:00 UTC: Edubuntu | 05 Apr 14:00 UTC: Xubuntu | 06 Apr 08:00 UTC: Dapper Development Status
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has left #ubuntu-meeting ["Ex-Chat"]
=== poningru [n=poningru@n128-227-55-122.xlate.ufl.edu] has joined #ubuntu-meeting
=== mattw [n=mattw@opal.cat.pdx.edu] has joined #ubuntu-meeting
=== freeflying-ibook [n=freeflyi@61.190.65.15] has joined #ubuntu-meeting
=== freeflying_ [n=freeflyi@61.190.65.15] has joined #ubuntu-meeting
=== pavka [n=pavka@195.39.44.217] has joined #ubuntu-meeting
=== harisund [n=harisund@ip24-255-87-152.br.br.cox.net] has joined #ubuntu-meeting
=== harisund [n=harisund@ip24-255-87-152.br.br.cox.net] has left #ubuntu-meeting ["Leaving"]
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== freeflying-ibook [n=freeflyi@61.190.65.15] has joined #ubuntu-meeting
=== Xnos [n=marco@201.137.170.123] has joined #ubuntu-meeting
=== zenbum [n=zenbum@c-71-198-208-194.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== Blippe [n=henryson@1-1-11-41a.f.sth.bostream.se] has joined #ubuntu-meeting
=== freeflying-ibook [n=freeflyi@61.190.65.15] has joined #ubuntu-meeting
=== highvoltage [n=Jono@196.36.161.235] has joined #ubuntu-meeting
=== lucas [n=lucas@ubuntu/member/lucas] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== spiritz [n=spiritz@61.12.41.143] has joined #ubuntu-meeting
=== jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== doko [n=doko@dslb-088-073-099-240.pools.arcor-ip.net] has joined #ubuntu-meeting
=== _spiritz [n=spiritz@61.12.41.143] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== mvo [n=egon@p54A66F78.dip.t-dialin.net] has joined #ubuntu-meeting
=== Den [n=knoppix@dhcp-40-162.EECS.Berkeley.EDU] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== lbm [n=lbm@x1-6-00-13-10-7a-d1-e4.k233.webspeed.dk] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== cassidy [n=cassidy@f1-pc174.ulb.ac.be] has joined #ubuntu-meeting
=== ChristmasCpp [n=christma@86.104.196.200] has joined #ubuntu-meeting
ChristmasCpphy all01:54
ChristmasCppd01:54
=== ChristmasCpp [n=christma@86.104.196.200] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== ChristmasCpp [n=christma@86.104.196.200] has left #ubuntu-meeting []
=== Meyer [i=mariomey@meyer.ubuntubrasil.org] has joined #ubuntu-meeting
Seveas@schedule Amsterdam02:36
UbugtuSchedule for Europe/Amsterdam: 30 Mar 18:00: Edubuntu Cookbook | 31 Mar 23:00: Documentation Team | 03 Apr 11:00: Community Council | 05 Apr 14:00: Edubuntu | 05 Apr 16:00: Xubuntu | 06 Apr 10:00: Dapper Development Status02:36
=== akulah [n=akulah@izvoru-comimpex.sebis.arad.astral.ro] has joined #ubuntu-meeting
=== highvolt1ge [n=Jono@196.36.161.235] has joined #ubuntu-meeting
=== ealden [n=ealden@203.76.212.130] has joined #ubuntu-meeting
=== ChristmasCpp [n=christma@86.104.196.200] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== Hirion [n=hirion@draugr.de] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== olive_ [n=olive@o.o6.fr] has joined #ubuntu-meeting
=== olive_ is now known as olive
=== _mvo_ [n=egon@p54A65BEC.dip.t-dialin.net] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== j_ack [n=nico@p508D8E51.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Pygi [n=mario@83-131-253-80.adsl.net.t-com.hr] has joined #ubuntu-meeting
=== Yagisan [n=jamie@60-240-205-203.tpgi.com.au] has joined #ubuntu-meeting
=== Yagisan [n=jamie@60-240-205-203.tpgi.com.au] has left #ubuntu-meeting []
=== Bluekuja [n=bluekuja@host235-236.pool8254.interbusiness.it] has joined #ubuntu-meeting
=== azeem_ [n=mbanck@host109.natpool.mwn.de] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: Edubuntu Cookbook | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 31 Mar 21:00 UTC: Documentation Team | 03 Apr 09:00 UTC: Community Council | 05 Apr 12:00 UTC: Edubuntu | 05 Apr 14:00 UTC: Xubuntu | 06 Apr 08:00 UTC: Dapper Development Status
=== flint [n=flint@montpeliervt-cuda1-24-50-146-184.sbtnvt.adelphia.net] has joined #ubuntu-meeting
=== spacey [n=herman@ubuntu/member/spacey] has joined #ubuntu-meeting
=== kjcole [n=kjcole@ubuntu/member/kjcole] has joined #ubuntu-meeting
spaceyhi05:58
spaceyPygi: ping05:59
spaceyogra: ping05:59
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu05:59
Pygispacey, shhhhh ;)05:59
spaceyhttps://lists.ubuntu.com/archives/edubuntu-devel/2006-March/001265.html06:00
spaceyfor the Agenda06:00
PygiHello everyone06:00
spaceyi feel quite loneeeeely06:00
PygiWelcome to the Edubuntu cookbook meeting06:00
Pygiwe'll wait for a few more minutes to give everyone a chance to attend06:01
spaceylets wait for a few minutes06:01
kjcoleWork emergencies. I'll be in and out of this meeting...06:01
flintkjcole, i will be here...06:01
flintspacey, elkner is teaching class...06:02
spaceyplease read up on the agenda06:02
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
spaceyi'm limited in time06:02
spaceyso i want to stick close to the poings06:02
spaceyitems06:02
spaceyand keep it structured06:02
spaceyif you have any other items not related to the item in discussion please keep it to the end of the meeting06:03
flintwhere is the agenda?  I have both references up.  06:04
spacey<spacey> https://lists.ubuntu.com/archives/edubuntu-devel/2006-March/001265.html06:04
spacey<spacey> for the Agenda06:04
flintgotcha...06:04
spaceyogra: there?06:04
spaceyhighvoltage will be a bit later06:05
spaceybut we can start before that06:05
flintRegarding item 1) Define purpose and role of the book I believe that the cookbook motif should be reconsidered...06:05
spaceyflint: please hold on06:05
spaceytill we start06:05
Pygiflint: hold on ;)06:05
spaceyi actually hoped ogra could be here06:05
spaceybut he seems out of it06:06
spaceywho is here now that intends to attend to the meeting?06:06
=== Pygi raises hand
spacey..06:07
spaceyflint?06:07
flintpresent06:07
spaceytoo bad ogra is not here yet06:08
spaceybut we'll start06:08
spaceyregarding point 1)06:08
spacey1) Define purpose and role of the book.06:08
spaceywe wrote up: https://wiki.ubuntu.com/HowToCookEdubuntu/PurposeAndRole06:08
=== HedgeMage [i=me@freenode/staff/HedgeMage] has joined #ubuntu-meeting
spaceyAnything that should be added there?06:08
flintHedgeMage, hello!!!06:08
spaceyin anyones opinion06:08
HedgeMagehi flint 06:09
spaceyPygi: 06:09
HedgeMageI miss anything?06:09
spaceyHedgeMage: we just started06:09
spacey<spacey> 1) Define purpose and role of the book.06:09
spacey<spacey> we wrote up: https://wiki.ubuntu.com/HowToCookEdubuntu/PurposeAndRole06:09
spaceyHedgeMage: agenda: <spacey> https://lists.ubuntu.com/archives/edubuntu-devel/2006-March/001265.html06:09
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
spaceyPygi: you think its pretty complete now? or should we cover it more specificly?06:09
HedgeMagethanks, spacey 06:10
Pygispacey: fine for now, but needs update...some other issues are of greater concern...06:10
kjcolecrisis du moment solved.06:10
spaceyPygi: what kind of update?06:10
=== kjcole is Kevin Cole
spaceygreat another soul06:11
Pygispacey: more detailed usage cases, etc.06:11
spaceyok06:11
spaceygood 06:11
spaceyanyone else?06:11
spaceyHedgeMage: flint?06:12
flintI believe that a re-write of the Tuxlab would be the best way to get this out the door.06:12
Pygiflint: it can help, that is sure, but not in the way you think...06:12
spaceyflint: you read my earlier posts to the list?06:12
flintThe tuxlab book is pretty well structured and would be a better framework rather than starting with a whole new framework.06:13
Pygia lot of stuff is too edubuntu specific06:13
flintPygi, we are writing to edubuntu... eh?06:13
spaceymost of the tuxlab stuff should be covered elsewhere06:13
HedgeMageI'm just jumping in, and this may end up being a seperate document from how-to-cook, but there needs to be something out there for teachers on using technology effectively in the classroom once they have it...06:13
Pygiflint: don't you know what this meeting is? :-/06:13
HedgeMageMost teachers either let that computer gather dust, or let it make their lives *more* complicated/difficult, instead of less06:14
spaceyHedgeMage: what technology do you point out here?06:14
spaceywhat piece of the technology06:14
flintPygi, oh I understood that this was specifically for edbuntu did i get this wrong?  it happens to old folks like me :^)06:14
Pygiflint: well, this is for edubuntu :)06:14
spaceyflint: https://lists.ubuntu.com/archives/edubuntu-devel/2006-March/001236.html06:15
spaceyplease read up06:15
flintPygi, I will not send myself to the home then... 06:15
spaceyHedgeMage: can you be mroe specific06:15
kjcoleflint, pygi I think you misunderstand each other: I think Pygi was saying that the Tuxlab book isn't edubuntu specific enough.06:15
HedgeMagespacey: I'd try to touch on what teachers can do with the computers in their classroom, both one-computer-per-class settings and lab settings06:16
Pygikjcole: ++06:16
flintspacey, I looked over your spec and you want to get someting out the door, done.  do this the quickest and best way. what every engineer in life does is take the last version and build from there.06:16
HedgeMagespacey: have you ever worked in a school where computers are very new to 90% of the teachers?06:16
spaceyHedgeMage: yes i do06:16
spaceyat least they don't know anything about it06:16
spaceythey just click on the icons06:16
spaceyHedgeMage: the key software is covered in the chapter list06:17
spaceybasicly that is your main point right? to make them familiar with available software?06:17
HedgeMagespacey: nope, more than that06:17
spaceyPygi: what i said might be something to add as usecase btw :P06:18
spaceyHedgeMage: example?06:18
HedgeMagespacey: Teachers need to know how to integrate this new stuff into their lesson plans, how to figure out what lessons will benefit and which won't, and how to integrate it into the way they teach06:18
flintthe tuxlab howto covers the subject in 14 chapters and an appendix.06:18
HedgeMagespacey: okay, two typical teachers from my mom's school to illustrate:06:18
Pygiflint: as said, tuxlab book is not edubuntu specific enough, and while we are surely to use it, we won't just copy it06:19
kjcoleThe Use Cases listed should perhaps also include students.  And the table of contents can be structured to allow more advanced users to skip introductory material.06:19
flintHedgeMage, you validly bring up the subjects of curriculum development and education.  sadly we are not equiped for that yet.  we have no foundation...06:19
=== HedgeMage nods to flint
Pygikjcole: perhaps there will even not be introducory material ...06:20
=== flint nods back... :^)
spaceyflint: your either not specific enough or completely off topic. Rewrite tuxlabs is not our goal06:20
spaceysaying stuff like that has no foundation06:20
flintspacey, what I am suggesting to you is that the frivolity of the cookbook is not expeditious.  we need to get something out now.06:21
spaceyPygi: i think we have some extra ideas for usecases06:21
spaceyflint: we are here because we want something out06:21
HedgeMageflint: I started a project on this once... humorously titled "Help! The computer ate my classroom!"... I may restart it, but in the mean time, I think integrating a little (even a short chapter) of introductory material somewhere, at least to get teachers thinking about it as they learn to use the software.06:21
flintjonathan did a serviceable job with the tuxlab howto.  we fix it and move on schedule.06:21
kjcoleIf you hope to recruit newcomers, then I think introductory material is essential.  I don't see many educators who have computers already set up by an IT person saying "Gee, let's throw out everything I know and hope that something I never heard of is better."06:21
HedgeMage*I think it might be beneficial06:22
spaceyHedgeMage: can you write some ideas about this stuff in an email and send it to list, we might be able to do something with it then06:22
spaceyi want to move on to the next topic now06:22
flintHedgeMage, stop the presses!!!! I am very interested.  is there a url where we may see this?06:22
HedgeMagespacey: sure thing... Won't happen until the weekend though06:22
spaceyHedgeMage: ok06:22
spacey2) Set deadlines for Dapper version.06:22
spaceywe setted up some deadlines06:22
HedgeMageflint: I'll pop it back on my website and include info in the list email06:22
=== HedgeMage listens to spacey
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu/Deadlines06:22
spaceyany comments on that06:23
spaceythose deadlines are needed to get everything in dapper06:23
flintapril 15 th is the deadline for filing US income taxes... ech!06:23
spaceyi don't think it needs much discussion06:23
spaceyespecially because ogra is not here06:24
spaceyso we can move on06:24
flintspacey, nice job...06:24
spacey3) Define scope. What do we want in the book and what not.06:24
spaceythis point should be defined a bit more specificly06:24
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu/Scope06:24
spacey\but it should give a good impression 06:24
kjcoleBenefits of thin-client computing would seem appropriate to me...06:25
flintHedgeMage, thanks mail the url to (flint@flint.com)06:25
kjcoleWhy does that work better on the web?06:25
spaceykjcole: i think it has a better place on the edubuntu website06:25
Pygikjcole: you know, we don't have many time to write it all....and we have little people :)06:26
HedgeMageflint: will do06:26
spaceybecause06:26
spaceythe cookbook is something you use during installation06:26
spaceyif you read about the benifits its before hand06:26
spaceyits a must have on the website06:26
kjcoleAh.  So, that narrows the scope considerably if it's really only an installation howto.06:27
HedgeMagespacey: we're reaching for something like the Gentoo Handbook, an exhausted how-to-get-this-thing-going sort of document, correct?06:27
Pygiuh,uh, not only during installation06:27
spaceyand its not useful to dupliclicate in a book06:27
HedgeMages/exhausted/exhaustive (freudian slip?)06:27
spaceyPygi: ok true06:27
spaceyand after06:27
spaceybut not really before imho06:27
spaceyHedgeMage: its more to cover the basics06:27
spaceyget people to know how things work06:27
spaceywhere to look things up06:27
HedgeMagespacey: okay, gotcha06:27
spaceywe don't want to duplicate ubuntu documentation06:27
spaceythats a waste of effort06:28
=== HedgeMage nods
spaceybut they should know where to find it06:28
HedgeMagemakes sense.06:28
spaceymake the reader familiar with the system and ways06:28
spacey4) Collaboration method. Wiki? Docbook?06:29
spaceyWe intend to use the wiki for now06:29
spaceysee link06:29
kjcoleSo, Installation, Troubleshooting, Optional Configuration Tweaks and you're done.  Bascially.  Right?06:30
spaceykjcole: a bit more06:30
spaceyalso introduction to the key software06:30
spaceykjcole: see chapter layout 06:30
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu/CollaborationMethod06:30
spacey5) Revise current chapter layout.06:31
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu/Chapters06:31
spaceythats the current layout i propose06:31
spaceyneeds some revision06:31
spaceyand actually i wanted to discuss which points each chapter should cover06:31
kjcoleWiki +1.  It seems to be the lowest rung on the ladder.06:31
Pygialso, articles for chapters should be written06:31
spaceybut i don't think this meeting is useful for that06:31
spaceyshould be more of a work meeting for that, between authors06:32
spaceyPygi: what do you think06:33
spaceythat was 6) Define what each chapter should cover.06:33
spaceybtw06:33
spaceygreat we are going *really* fast06:34
spaceyitem: 7) Assign roles and responsibilities06:35
spaceyhttps://wiki.ubuntu.com/HowToCookEdubuntu/RolesAndResponsibilities06:35
kjcoleDoes the intro cover the "What's inside?" part of things?06:35
spaceykjcole: whats inside... the book?06:35
HedgeMagespacey: somewhere in here will we want to touch on getting a *very minimal* web presence up?  most schools, at least in the US, making a change like this will have to be very aware of having something to show to the community at large, to keep their support.06:35
spaceyHedgeMage: webpresence for us?06:36
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
spaceythere is www.edubuntu.org06:36
kjcolespacey: No.  Earlier it was said that the book should give people an idea of what edubuntu software's included.  I didn't see a specific chapter for that, so I'm guessing in the Introduction.06:36
spaceykjcole: let me check06:37
HedgeMagespacey: no, for schools06:37
spaceyHedgeMage: i think its out of scope, webservers are ubuntu documentation scope06:37
spaceykjcole: ah yes i see its not in the list, i had it in mind06:37
spaceybut didn't know where to put it06:38
HedgeMagespacey: okay.06:38
spaceyi guess it should come after the introduction06:38
kjcolespacey: sounds good to me.06:39
spaceyPygi: note :P06:39
HedgeMagekjcole: nice catch :)06:39
kjcoleHedgeMage: One of very, very few, I'm afraid.06:39
HedgeMagekjcole: :P06:40
spacey<spacey> item: 7) Assign roles and responsibilities06:40
spacey<spacey> https://wiki.ubuntu.com/HowToCookEdubuntu/RolesAndResponsibilities06:40
spaceyto finish up with that06:40
spaceyare there more reponsibilties for the roles or more roles needed?06:40
kjcoleBTW, no one liked the "Appetizers, etc" well enough to keep that?  Just too silly?  Or not easy to map to?06:40
spaceykjcole: its quite funny06:41
spaceyi wasnt thinking about naming the parts yet06:41
spaceybut we'll probably use it06:41
spaceyany comments on item 7?06:41
HedgeMageI'll jump in and do *something* just not sure what/where :)06:42
spaceyHedgeMage: if you decide to write a part just be sure to finish it 06:43
kjcoleWell, I wasn't very good at managing...  I did a lot of conversion of material between docbook, Lore and wiki.  Plus some rehashing of the content of Tuxlab.  But I've never done the LTSP stuff and am not in a classroom.  So, I'm not sure at this point what I can contribute.06:44
spaceyi have to go now06:44
spaceysorry for that06:44
spaceyhave to visit doctor06:44
kjcolespacey: ta-ta.06:44
spaceyPygi will take over from me06:44
HedgeMagespacey: go, be healthy, see you later.06:44
spaceyand finish things up06:44
kjcoleIs it just me, or did it just get very quiet in here? ;-)06:46
spaceyPygi: :p06:46
HedgeMagelol06:46
Pygiok, let's finish this up ....06:46
Pygican anyone here be certain he'll be able to contribute, and what exactly?06:47
=== highvoltage [n=Jono@mtngprs7.mtn.co.za] has joined #ubuntu-meeting
HedgeMagePygi: I can donate about 15 hours between now and the first deadline, just not sure where I'll be the most useful.06:48
kjcoleIf it's on the wiki, I can review for grammar and style, I think.06:48
highvoltagehi06:48
Pygihello highvoltage06:48
highvoltagehi Pygi 06:49
Pygihighvoltage, pm please06:49
highvoltageok06:49
PygiHedgeMage, will write it down06:49
kjcolePygi: (I guess that falls under "Linguistic Quality Assurance".)  Other than that, I'm really not certain.  I suppose I can try to test according to the book.  I keep hoping to recruit a "virgin" to do that sort of thing, but no luck yet.06:51
Pygikjcole: ok, we'll see what we will do ...06:52
HedgeMagePygi: may I drop you a quick /msg ?06:52
PygiHedgeMage: please do06:53
highvoltagei'll catch up on the meeting details i've missed so far on the logs06:54
kjcoleOne problem I see w/ testing is, to quote the wiki, a definition of "People with basic ICT skills".  As a programmer, I have a lot of experience (+27 years) with COMPUTERS.  But I wouldn't know a router from a hub from a switch if I fell over them.06:55
=== cassidy [n=cassidy@physInfo-mac26.ulb.ac.be] has joined #ubuntu-meeting
kjcoleMost would interpret "basic ITC skills" as "knows how to turn computer on, knows how to install Microsoft Office, knows how to dial tech support."06:57
=== Kinnison [n=dsilvers@haddenham.pepperfish.net] has joined #ubuntu-meeting
HedgeMagelol07:00
Pygiah07:04
kjcoleSo, when testing, there should be a "lowest common denominator".  If I test, I'm going to pretend to be fairly ignorant of anything other than Windoze and an ethernet cable to a wall.  Things like public/private IP addresses?  I don't know what that is: When I turn on my Windoze machine at work it just "gets e-mail and lets me browse the web"...07:04
Pygikjcole: wrong attitude07:05
Pygiwe are not to write what an IP is07:05
Pygiout of scope07:05
kjcolePygi: So, for setting up Edubuntu, I won't need to know anything about DHCP configuration stuff?07:06
=== johnshaft [n=scott@adsl-66-218-52-72.dslextreme.com] has joined #ubuntu-meeting
Pygiyou will, but for that you have ubuntu docs ;)07:06
Pygikjcole: how much "pages" do you expect the book to have? infinite? :P07:08
kjcolePygi, So the person setting up should get savvy with setting up a straight Ubuntu server before doing the Edubuntu setup?07:09
Pygihm, no, we'll put info how it should be configured, but won't explain why is it configured that way07:09
kjcolePygi, That works.  ;-)07:09
PygiKISS07:10
Pygi;)07:10
Pygifor normal users, it works ;)07:10
PygiKeep it simple, stupid :-P07:10
Pygianyway, I think we can end with the meeting 07:10
Pygieveryone agrees?07:11
Pyginot that there are people to disagree :P07:11
kjcolePygi: I like the short and sweet (or the simple and stupid).  I'm just trying to think like someone who's been asked to set this thing up, but doesn't have the time to go reading lots of different docs.07:11
kjcolePygi: Yeah.  Seems kind of quiet again.  And it's getting near my lunchtime...07:12
=== HedgeMage nods
HedgeMagePygi: btw, any chance this could end up being the permanent meeting time?  1200 UTC is 4am for me... that just doesn't work on a weekday (I need sleep occassionally)07:18
=== mario_ [n=mario@83-131-247-18.adsl.net.t-com.hr] has joined #ubuntu-meeting
kjcoleBye...07:37
Pygibye07:37
=== didier [n=didier@84.4.205.114] has joined #ubuntu-meeting
=== Bluekuja [n=bluekuja@host123-174.pool8250.interbusiness.it] has joined #ubuntu-meeting
=== lucas [n=lucas@ubuntu/member/lucas] has joined #ubuntu-meeting
=== hunger [n=tobias@p54A6216B.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== wold [n=wold@ev-217-129-81-225.netvisao.pt] has joined #ubuntu-meeting
=== GNAM [n=giocauno@host86-241.pool80183.interbusiness.it] has joined #ubuntu-meeting
GNAMwhere's log of "dapper status" of today?08:12
dholbachread the topic please08:12
GNAMi've read08:12
GNAMand not found08:13
dholbachhttp://people.ubuntu.com/~fabbione/irclogs/08:13
=== G0SUB [n=ghoseb@ubuntu/member/g0sub] has joined #ubuntu-meeting
=== lamont [n=lamont@mib.fc.hp.com] has joined #ubuntu-meeting
flintHedgeMage, you still here?08:14
=== cassidy [n=cassidy@d83-182-4-234.cust.tele2.be] has joined #ubuntu-meeting
=== GNAM [n=giocauno@host86-241.pool80183.interbusiness.it] has left #ubuntu-meeting []
HedgeMageflint: back now :)08:25
HedgeMageflint: what's up?08:26
Pygiwelcome back HedgeMage08:28
=== ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 31 Mar 21:00 UTC: Documentation Team | 03 Apr 09:00 UTC: Community Council | 05 Apr 12:00 UTC: Edubuntu | 05 Apr 14:00 UTC: Xubuntu | 06 Apr 08:00 UTC: Dapper Development Status | 11 Apr 20:00 UTC: Technical Board
HedgeMagethanks :)08:31
=== dilagoo [n=dilago@20132205140.user.veloxzone.com.br] has joined #ubuntu-meeting
=== Den [n=knoppix@dhcp-40-162.EECS.Berkeley.EDU] has left #ubuntu-meeting ["Konversation]
=== dilagoo [n=dilago@20132205140.user.veloxzone.com.br] has left #ubuntu-meeting []
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== didier [n=didier@84.4.205.114] has left #ubuntu-meeting ["Konversation]
flintHedgeMage, sorry for the temporal chop, I suddenly gotta make a living on this silly box.... anyway, please email me your document url, i think that it may tie into my plans for work domination... buahahahahahahahahahahahahahahahahahaha08:43
HedgeMagelol08:43
HedgeMageflint: I have to find it and pop it online again (probably this weekend)... I lost a lot of data when last we moved, and I'm going to have to grab it from a backup08:44
=== quidam- [n=quidam@200.84.182.195] has joined #ubuntu-meeting
=== HedgeMage grumbles about stupid army movers
flintI try to reflect on the question "our army or their army" :^)08:46
HedgeMageflint: US Army08:46
HedgeMageflint: my husband is in the military08:46
flintHedgeMage, did my time... http://www.flint.com/flint/vita_sf.html  ended up running like a scared rabbit from a burning 5 sided building... not fun.08:47
=== HedgeMage nods.
flintHedgeMage, ...funny story that... NOT!08:48
=== Pygi [n=mario@83-131-245-103.adsl.net.t-com.hr] has joined #ubuntu-meeting
=== kyral_ [n=Chris@ubuntu/member/kyral] has joined #ubuntu-meeting
=== Bluekuja [n=bluekuja@host123-174.pool8250.interbusiness.it] has joined #ubuntu-meeting
=== j_ack [n=nico@p508D8E51.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== Nirvana [n=marco@CPE0080c8292db5-CM000f9f5158ce.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== Xoxe [n=Xoxe@68.Red-80-25-62.staticIP.rima-tde.net] has joined #ubuntu-meeting
=== Hirion [n=hirion@draugr.de] has left #ubuntu-meeting []
=== na7e [n=na7e@205.213.122.126] has joined #ubuntu-meeting
=== teknicaL [n=Admin@c-68-46-127-247.hsd1.pa.comcast.net] has joined #Ubuntu-meeting
=== teknicaL is now known as tekN1X
=== harisund [n=harisund@204.90.50.252] has joined #ubuntu-meeting
=== harisund [n=harisund@204.90.50.252] has left #ubuntu-meeting []
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting

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