[00:00] <michazoet> \o/
[00:00] <_Lux> Good Morning czajkowski
[00:00] <juliux>  The assocation is the supporting institute for the German Ubuntu Communities. Since 2006 we are doing a lot of conference appearances and release parties. Starting 2007 we have our yearly Ubuntu conference called Ubucon
[00:00] <juliux>  At the moment we are busy to improve the integration of all parts of the team especially to integrate the Ubuntu developer. But this is a long time goal;)
[00:00] <juliux> And sorry for the late wiki pages changes.
[00:00] <czajkowski> I think juliux is rather prepared :(
[00:00] <czajkowski> :)
[00:00] <juliux> ;)
[00:00] <juliux> czajkowski: ;)
[00:00]  * _Lux and Julius prepared the text ;-)
[00:00] <paultag> juliux, it's OK, I'm actually on the -de mailing list, so it's no problem :)
[00:00] <czajkowski> so tell us how you organise folks into doing things
[00:00] <juliux> btw i think that was the fast reapproval ever;) only one week preparation
[00:00] <juliux> paultag: cool
[00:01] <_Lux> czajkowski: What exactly do you want to know?
[00:01] <_Lux> Unfortunately we are a very splitted team, working on different aspects of Communiy
[00:02] <_Lux> One of our main tasks is to integrate all back into one big team
[00:02] <czajkowski> yes how do you orgnise that
[00:02] <juliux> in the past we used mailinglists for that and face to face discussions
[00:02] <_Lux> We have a central mailing list for LoCo-Activities which we use to coordinate
[00:02] <_Lux> Last week we started an IRC round table
[00:03] <v4vortex> yes, and it was a good start!
[00:03] <Jiraiya> indeed
[00:03] <itnet7> _Lux: How many people attend your Ubucon's?
[00:04] <_Lux> itnet7: 150-200 (correct juliux?)
[00:04] <itnet7> Very nice turnouts!
[00:04] <_Lux> itnet7: They are coming from all over Germany and Switzerland and Austria
[00:04] <huats> and may be France next time :)
[00:05] <_Lux> We are in Germany not so big in size but big in terms of people
[00:05] <paultag> juliux, _Lux, how have the translation efforts from within the LoCo been going for German?
[00:05] <czajkowski> yes I've seen your jams they are rather impressive
[00:05] <juliux> itnet7: in 2008 we had 200 in 2009 300
[00:05] <itnet7> That is really great!
[00:06] <juliux> paultag: the translation team is more working for upstream translations
[00:06] <czajkowski> Have you faced any issues??
[00:06] <juliux> paultag: most of them are translation for gnome and kde
[00:06] <juliux> czajkowski: yes;) splitting a locoteam into to parts kubuntu and ubuntu
[00:06] <paultag> juliux, Outstanding. I caught a glimpse of that about a year ago when I had a small change for Evolution :)
[00:06] <\Lux> paultag: We have a very active translation team whcih has an onw forum in our officical forum
[00:06] <paultag> \Lux, would you mind posting those links?
[00:07] <czajkowski> juliux: how did ye go about solving that issue ?
[00:07] <\Lux> mompls
[00:07] <juliux> czajkowski: but that happens allreay in 2005/2006
[00:07] <juliux> czajkowski: the solutions  that we have to locoteams so we are only covering *buntu but not kubutnu
[00:07] <\Lux> paultag: Here it is: http://forum.ubuntuusers.de/forum/lokalisierung/
[00:07] <paultag> thank you \Lux :)
[00:07] <juliux> czajkowski: they are doing there own thing but there are some contact points at fairs or at the ubucon
[00:07] <czajkowski> ok
[00:07] <\Lux> paultag: welcome
[00:07] <czajkowski> sound sgood
[00:08] <czajkowski> are there any other comments you'd like to make to the council
[00:08] <juliux> paultag: the cfp is still open;)
[00:08] <czajkowski> itnet7: leogg huats paultag any other comments
[00:08] <huats> juliux, please correct the team contact, since it was still smurf on the wiki page (may be you have already changed that)
[00:08] <paultag> I'm all set, thank you czajkowski :)
[00:08] <juliux> huats: _Lux and i will take that over
[00:08] <paultag> juliux, my German is that of a three year old ;)
[00:08] <huats> otherwise please  continue that way !
[00:08] <itnet7> Not really, I am very impressed with their team!
[00:08] <paultag> juliux, but I'd love to watch :)
[00:08] <\Lux> paultag: like my English
[00:09] <paultag> \Lux, :)
[00:09] <czajkowski> [vote] Please vote on the German LoCo Re approval
[00:09] <MootBot> Please vote on:  Please vote on the German LoCo Re approval.
[00:09] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[00:09] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[00:09] <paultag> +1
[00:09] <MootBot> +1 received from paultag. 1 for, 0 against. 0 have abstained. Count is now 1
[00:09] <itnet7> +1
[00:09] <MootBot> +1 received from itnet7. 2 for, 0 against. 0 have abstained. Count is now 2
[00:09] <leogg> +1
[00:09] <MootBot> +1 received from leogg. 3 for, 0 against. 0 have abstained. Count is now 3
[00:09] <czajkowski> +1
[00:09] <MootBot> +1 received from czajkowski. 4 for, 0 against. 0 have abstained. Count is now 4
[00:09] <MootBot> Private +1 vote received. 5 for, 0 against, 0 have abstained. Count is now 5
[00:09] <czajkowski> [endvote]
[00:09] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[00:09] <czajkowski> whoooo
[00:09] <itnet7> Very cool!!!
[00:09] <paultag> Really outstanding work \Lux, juliux. Keep up the great work
[00:09] <czajkowski> very nice
[00:09] <czajkowski> well done
[00:09] <juliux> \o/
[00:09] <juliux> thank you very much
[00:09] <huats> congrats german team !
[00:09] <\Lux> thanks a lot \o/
[00:09] <itnet7> \o/ juliux and team!
[00:09] <czajkowski> 9 LoCo teams re approved and 2 new teams approved tonight!
[00:09] <Jiraiya> thank you guys :)
[00:10] <juliux> sleep well!
[00:10] <v4vortex> yes, thanks a lot
[00:10] <czajkowski> [endmeeting]
[00:10] <czajkowski> #endmeeting
[00:10] <MootBot> Meeting finished at 18:10.
[00:10] <czajkowski> grrrrrr
[00:10] <czajkowski> bot!
[00:10] <v4vortex> yeah, and sleep well (its 01am here)
[00:10] <v4vortex> :)
[00:10] <leogg> thanks everybody
[00:10] <juliux> cu
[00:10] <Jiraiya> and have a good night, all of you
[00:10] <czajkowski> nn folks
[00:10] <\Lux> Good night, I have to get up at 5:00 hrs
[00:10] <paultag> Thanks everyone, good night / morning :)
[00:11] <paultag> \Lux, Gute nacht, schlaft gut ;)
[00:11] <\Lux> paultag: you too :-))
[14:57] <zul> gday
[14:57] <mjeanson> hi
[14:58] <kirkland> [o]
[14:58] <ttx> ]o[
[14:59] <mathiaz> \u\
[14:59] <Daviey> \o
[14:59] <jmdault> o/
[15:00] <jjohansen> o]
[15:00] <ttx> ok, let's get started !
[15:00] <ttx> #startmeeting
[15:00] <MootBot> Meeting started at 09:00. The chair is ttx.
[15:00] <RoAkSoAx> o/
[15:00] <ttx> Welcome to the Ubuntu Server team meeting !
[15:00] <zul> wheee
[15:00] <ttx> Agenda is at: https://wiki.ubuntu.com/ServerTeam/Meeting
[15:00] <ttx> Scribe is: zul !
[15:01] <ttx> [TOPIC] Review ACTION points from previous meeting
[15:01] <MootBot> New Topic:  Review ACTION points from previous meeting
[15:01] <ttx> * mathiaz to fix the "server fixed bugs" broken script
[15:01] <smoser> \o
[15:01] <mathiaz> ttx: still on my TODO
[15:02] <ttx> ttx to follow up with ivoks/RoaKSoax on cluster stack state : DONE
[15:02] <ttx> * mathiaz to propose removal of dovecot-postfix on MLs
[15:02] <mathiaz> ttx: that has been done
[15:02] <mathiaz> ScottK: ^^
[15:02] <zul> and the fix has been uploaded
[15:02] <mathiaz> zul: great thanks
[15:02] <ttx> mathiaz: without a strong consensus, I see
[15:03] <mathiaz> ttx: about the fix or the removal?
[15:03] <mathiaz> ttx: I'm fine with the fix
[15:03] <ttx> abouit the removal :)
[15:03] <mathiaz> ttx: as long as the use of dovecot-postfix.conf has been discarded
[15:03] <ttx> mathiaz: does that prove the need for a UDS session on taht subject, to set expectations for the Maverick cycle ?
[15:04] <mathiaz> ttx: not specifically
[15:04] <mathiaz> ttx: there may be a more generic what to do with the mail server though
[15:04] <ttx> mathiaz: yes
[15:04] <ttx> [TOPIC] Lucid release status
[15:04] <MootBot> New Topic:  Lucid release status
[15:04] <ttx> So the RC is in the oven, should be released tomorrow
[15:05] <ttx> Today's focus is on ISO testing coverage
[15:05] <ttx> We don't expect a server ISO/images respin, so please test the heck out of them
[15:05]  * kirkland is on it
[15:06] <ttx> Don't forget to register your test results... and mark the tests you started as "started" for coordination
[15:06] <ttx> On the remaining RC bugs side... I assigned most of them to the team, at the very least you should look into them and comment whether they can and should be fixed by release day, or as a post-release SRU
[15:07] <ttx> the watch list is updated at: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[15:07] <ttx> that's the team main focus for after-RC
[15:08] <ttx> Finally, you have some remaining work items in specs
[15:08] <ttx> See http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04.html
[15:08] <ttx> Most of them are about UEC testing/validation so we should be ok, but don't forget those :)
[15:08]  * hggdh kicks evolution and its 1G  resident memory
[15:09] <ttx> Questions on release management, priorities for the next week, etc. ?
[15:09] <zul> nyet
[15:10] <hggdh> pas
[15:10] <ttx> About post-RC fix vs. early SRU: it's mostly the release team decision based on the impact of the proposed patch vs. how impacting is the bug.
[15:10] <ttx> but you should be able to make an educated guess :)
[15:10] <ttx> ok, moving on to:
[15:10] <ttx> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[15:10] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[15:11] <ttx> hggdh: how is it going in QA land ?
[15:11] <hggdh> life is not as good as I expected ;-)
[15:11] <kirkland> ttx: hggdh has been doing a heck of a job testing UEC
[15:11] <kirkland> ttx: shaking out some hard issue
[15:11] <hggdh> we are still going along, though. All of you have been extremely helpful on my bugs
[15:12] <hggdh> er. not *mine*, I mean
[15:12] <ttx> yes, we still have a stream of issues in UEC stresstesting and cloud images boot
[15:12] <hggdh> yes. Right now it seems the more we poke, the more bugs fall
[15:12] <ttx> kirkland, smoser: I kept you out of the other server bugs so that you can concentrate on those
[15:13] <kirkland> hggdh: that's our job ;-)
[15:13] <ttx> hggdh: you seem to have the Gift !
[15:13] <hggdh> mathiaz scripts have helped a lot, BTW
[15:13] <kirkland> ttx: thanks, much appreciated, we're actively working those
[15:14] <hggdh> ttx: right now, this is pretty much what I can tell you... sorry
[15:14] <ttx> hggdh: the regression build rig seems to have triggered a few recent messages
[15:14] <ttx> hggdh: do you plan to have a maverick spec to cover what we should do now with this ?
[15:14] <hggdh> hum. I have not looked at my emails today, but I do not remember any from yesterday (except atlas, but this is not aq worry)
[15:15] <ttx> hggdh: they were from this morning.
[15:15] <hggdh> ttx: you mean the regression rig? Yes, I do have some ideas. We should keep it, and expand it
[15:15] <ttx> hggdh: planning a UDS session / blueprint on the subject ?
[15:16] <kirkland> hggdh: ttx: i suggest some "barriers", that would allow a topo to deploy with one button
[15:16] <kirkland> hggdh: ttx: rather than triggering each system individually
[15:16] <hggdh> I am going to put it in the QA pool of ideas, and someone will decide on it
[15:16] <kirkland> hggdh: ttx: possibly as simple as an early command that sleeps/waits until its dependendent systems are installed
[15:17] <ttx> kirkland: I was talking about the build regression rig, the thing that rebuilds a set of package daily
[15:17] <hggdh> kirkland: yeah, something like that. I would also like to have at least one more rig
[15:17] <ttx> and mails out tons of errors :)
[15:17] <ttx> ah, plenty of interesting discussions coming up in Brussels.. volcano smoke allowing.
[15:18] <hggdh> heh
[15:18] <ttx> Other questions for QA team ?
[15:18] <hggdh> everybody says smoke is bad to our health
[15:18] <hggdh> no, we are good
[15:19] <ttx> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:19] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[15:19] <ttx> hggdh: thanks !
[15:19] <ttx> jjohansen: o/
[15:19] <hggdh> ttx: just an aside -- we should talk, when possible, on the autonmated server tests
[15:19] <jjohansen> hey
[15:19] <jjohansen> so not much has changed on the kernel side since last week
[15:20] <ttx> jjohansen: which is good :)
[15:20] <smoser> no issues found in ec2 testing related to kernel
[15:20] <jjohansen> a little more debug info shaken out, and a couple more bugs showing up
[15:20] <smoser> other than possibly bug 567334
[15:21] <jjohansen> right
[15:21] <ttx> I don'ty have any new burning issue myself... but it's sometimes difficult to be aware of existing kernel bugs affecting server
[15:21] <smoser> jjohansen, i wonder if you've proposed a blueprint or some mechanism to get official time to trial paravirt-ops kernels on ec2
[15:22] <jjohansen> smoser: not yet
[15:22] <jjohansen> it will come I still need to poke that beast a little bit this week
[15:22] <smoser> i know how difficult or unlikely getting that to work is, but *I* would really like it, and I know it'd make your job much easier if you didn't have thousands of lines of patches
[15:23] <jjohansen> hehe, well that is motivation to get it working :)
[15:23] <zul> what no more hulking patch?
[15:24] <ttx> ok, any other questions/concerns to transmit to the kernel team ?
[15:24] <kirkland> jjohansen: no progress on that oops?
[15:24] <kirkland> jjohansen: that we're seeing in some UEC guests?
[15:25] <kirkland> jjohansen: seems to be only on certain hardware
[15:25] <jjohansen> kirkland: no :(
[15:25] <kirkland> jjohansen: alrighty, thanks
[15:25] <kirkland> jjohansen: i suspect this will need an SRU eventually
[15:25] <ttx> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)
[15:25] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)
[15:25] <jjohansen> though that isn't the only bug we have seen that is hardware specifi
[15:25] <kirkland> jjohansen: right
[15:25] <ttx> mathiaz: o/
[15:26] <mathiaz> a few bugs from karmic:
[15:26] <mathiaz> bug 156636
[15:26] <mathiaz> bug 494141
[15:27] <mathiaz> Both should be decline IMO
[15:27] <ttx> not fixed in dev release
[15:27] <ttx> so not candidates for SRU
[15:28] <mathiaz> that's all as far as I can say
[15:28] <mathiaz> given that the bugs-fixed-lately script is broken
[15:28] <ttx> ok, that was fast !
[15:29] <mathiaz> anything worth fixing in SRU from last week?
[15:29]  * kirkland wagers that the SRU portion of this meeting is about to get a lot more interesting in about ~2 weeks :-)
[15:29] <mathiaz> kirkland: right
[15:29] <mathiaz> kirkland: I'll add the lucid nominations list once lucid is released
[15:29]  * ttx wagers that there should be an interesting discussion about SRU handling at UDS in ~3 weeks :-)
[15:29] <kirkland> ttx: oh?  changes on the way?
[15:29] <RoAkSoAx>  /join #ubuntu-ha
[15:29] <mathiaz> which means that the first (few?) meetings may see more SRU activity
[15:30] <ttx> kirkland: well, we should at least discuss if our current process fits the bill for Lucid
[15:30] <kirkland> ttx: ah
[15:30] <kirkland> mathiaz: i think so ...  there's a number of things we'll want to fix for Lucid that didn't make release
[15:30] <kirkland> mathiaz: and probably a number of new issues that come up as people upgrade
[15:31] <ttx> i'm not sure it gives us the tracking information we'll need, so far
[15:31] <mathiaz> Are then any plans to put dedicated ressource on lucid SRU?
[15:31] <mathiaz> the same way as we did for Hardy?
[15:31] <ttx> that's a good question and I don't know the answer.
[15:32] <ttx> [ACTION] ttx to confirm with jib lucid SRU resource allocation
[15:32] <MootBot> ACTION received:  ttx to confirm with jib lucid SRU resource allocation
[15:32] <zul> i think we should because most users probably wont upgrade until .1
[15:32] <zul> imho
[15:32] <ttx> mathiaz: could you explain what happened in hardy, for reference ?
[15:33] <mathiaz> ttx: IIRC some of the desktop team members spent time on hardy SRUs.
[15:33] <mathiaz> ttx: until enf of June IIRC
[15:33] <mathiaz> ttx: ask pitti or seb128
[15:33] <ttx> zul: yes, we need a way to track and coordinate the amount of work we'll all do in that area... and possibly someone dedicated to tracking it
[15:33] <zul> ttx: I wa working on SRU for the hardy point release
[15:33] <kirkland> ttx: yeah, zul worked on hardy.1, and i worked on hardy.2
[15:34] <ttx> noted, thanks !
[15:34] <ttx> [TOPIC] Maverick call for blueprints
[15:34] <MootBot> New Topic:  Maverick call for blueprints
[15:34] <ttx> So UDS is nearing and volcano smoke seems to clear out
[15:35] <zul> volcano smoke is overblown
[15:35] <ttx> If you want to suggest a UDS session topic, feel free to file an Ubuntu blueprint !
[15:35] <ttx> name is server-maverick-*
[15:35] <ttx> and approver must be set to "Jos Boumans"
[15:35] <ttx> at tha point only one was filed:
[15:35] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-wbemcim-providers
[15:36] <ttx> I also set up a page to braindump and track the propsoed sessions:
[15:36] <ttx> https://wiki.ubuntu.com/ServerTeam/MaverickIdeaPool
[15:36] <ttx> I'll add a lot more sessions from the team internal braindump in the next hours/days
[15:37] <ttx> so no need for the Canonical server team to spend time on editing that page
[15:37] <ttx> but everyone else is more than welcome to do so !
[15:38] <ttx> [TOPIC] Open Discussion
[15:38] <MootBot> New Topic:  Open Discussion
[15:38] <ttx> anything/anyone ?
[15:39] <padhu> What about lucid?
[15:39] <ttx> padhu: what what about lucid ?
[15:39] <ttx> padhu: it goes out next week
[15:40] <ttx> hopefully :)
[15:40] <padhu> In time?
[15:40] <ttx> team: is sleeping getting any better ?
[15:40] <ttx> padhu: at this point, yes...
[15:40] <mathiaz> ttx: still on track
[15:41] <ttx> padhu: but being late is, by essence, unpredictable.
[15:41] <padhu> Happy to hear it. I am waiting eagerly
[15:41] <ttx> padhu: I'd advise you to downlaod and test the RC which goes out tomorrow ! That will make the release all the more enjoyable to you.
[15:42] <ttx> the sooner we know wbout bugs, the sooner we can fix them.
[15:42] <zul> ttx:yep
[15:42] <ttx> ... and by definition, no significant change is expected between RC and final.
[15:42] <padhu> oh
[15:43] <padhu> i will try
[15:43] <ttx> [TOPIC] Announce next meeting date and time
[15:43] <MootBot> New Topic:  Announce next meeting date and time
[15:43] <ttx> Same place, same time, next week, in the middle of the release frenzy
[15:43] <ttx> i'll be in London next week, hopefully I'll be able to spend time on the meeting
[15:44] <ttx> Thanks everyone !
[15:44] <ttx> #endmeeting
[15:44] <MootBot> Meeting finished at 09:44.
[15:47] <padhu> Bye....
[16:00] <barry> hi everybody!  meeting time...
[16:00] <barry> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is barry.
[16:00] <barry> [TOPIC] agenda
[16:00] <MootBot> New Topic:  agenda
[16:00] <barry> https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0421
[16:00] <barry> [LINK] https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0421
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0421
[16:01] <ev> hello
[16:01] <james_w> hi
[16:01] <padhu> Hi
[16:01] <mvo> hi
[16:02]  * slangasek waves
[16:02] <cjwatson> hi
[16:02] <doko_> hi
[16:02] <barry> [AGENDA]
[16:02] <barry> [TOPIC] agenda
[16:02] <MootBot> New Topic:  agenda
[16:03] <barry> lool, cjwatson, slangasek, ev, doko, james_w, Keybuk, barry, mvo, tremolux
[16:03] <barry> paste fail
[16:03] <mvo> tremolux is on vacation
[16:03] <barry> [TOPIC] lightning round
[16:03] <MootBot> New Topic:  lightning round
[16:03] <barry> order: cjwatson, slangasek, ev, doko, james_w, Keybuk, barry, mvo
[16:04] <cjwatson> done: various last-minute installer bug fixes (esp. 543838, 546964, 558382, 566965); branding fixes per design team; generally trying to keep on top of late-breaking bugs
[16:04] <cjwatson> todo: head-scratching over part of bug 567345, which is looking like a busybox shell bug
[16:04] <cjwatson> --
[16:06] <slangasek> done: some spit'n'polish on plymouth and mountall; todo: fix the last few big ugly bugs in plymouth for release; and oh yeah, that RC thing is this week
[16:06] <slangasek> --
[16:06] <ev> in progress: Trying to figure out why wubi is setting automatic-ubiquity on the kernel command line for the cd boot helper option.  Trying to get to the bottom of some broken migration-assistant and debconf interaction that's in turn breaking hw-detect (bug 234835, bug 536673).  CD testing && bug fixing.
[16:06] <ev> todo: Get to the bottom of bug 567243.  Figure out why ubiquity is still cutting off text for some users/languages (bug 560114).  Fix usb-creator breaking on non-FAT partitions (bug 566390).
[16:06] <ev> blocked: Need a release team review on bug 566552.
[16:06] <ev> --
[16:07] <doko> done:
[16:07] <doko>  * openjdk-6 1.8 release, lucid upload
[16:07] <doko>  * more sun-java6 updates (twice, first with the wrong debian sources)
[16:07] <doko>  * eglibc memcpy/strcmp fixes, rebuilds
[16:07] <doko>  * maverick toolchain preparations
[16:07] <doko>  * llvm regression fixes
[16:07] <doko>  * fix some build failures
[16:07] <doko> todo:
[16:07] <doko>  * file bug reports for test rebuild failures
[16:07] <doko>  * need help with that ipv6 networking bug
[16:07] <doko> --
[16:07] <james_w> working on a bunch of fixes and merges for both Ubuntu and bzr-builddeb etc. Will continue the same.
[16:07] <james_w> --
[16:09] <james_w> probably a little early for the stranded Keybuk?
[16:09] <barry> ;)
[16:09] <barry> bug reporting script (from cjwatson) - blocked on lazr.restfulclient; bug
[16:09] <barry> 552777 (cj2.0); bug 485944 (python-virtualenv debian 1.4.5 sync); pep 3147
[16:09] <barry> (landed!); python packaging/udd testing
[16:09] <barry> --
[16:09] <barry>
[16:09] <cjwatson> pep 3147 landed> great!
[16:10] <james_w> woo!
[16:10] <slangasek> james_w: I have no sympathy for him :)
[16:10] <mvo> fixes in software-center for final release, fixes in update-manager, debugging upgrade issues,  Support-timeframe: prepare final merge into LP production BLOCKED on exact seed definition that we support for 3y, currently working on OOo pre-depends hell
[16:10] <mvo> --
[16:10] <barry> \o/
[16:10] <james_w> slangasek: you're stranded in a different way :-)
[16:11] <barry> [TOPIC]  * Outstanding actions from last meeting
[16:11] <MootBot> New Topic:   * Outstanding actions from last meeting
[16:11] <barry> none that i'm aware of
[16:11] <james_w> barry: lazr.restfulclient> we need an upgrade in the distro for that?
[16:11] <barry> james_w: we do
[16:11] <barry> james_w: i don't have the bug in front of me, but it's a problem with path name lengths
[16:11] <barry> in the cache
[16:12] <james_w> yeah, I remember
[16:12] <barry> james_w: i was going to work on that today
[16:12] <barry> [TOPIC]  * Outstanding feature freeze exceptions
[16:12] <MootBot> New Topic:   * Outstanding feature freeze exceptions
[16:13] <barry> slangasek: anything to say about this one?
[16:13] <james_w> barry: it's in Debian fwiw
[16:13] <barry> james_w: yep, i think it's a fairly simple sync
[16:13] <slangasek> outstanding feature freeze exceptions> remember that we'll be face-to-face in three weeks time in Belgium before you ask for a feature freeze exception the week of RC :)
[16:14] <james_w> so we should ask for them in three weeks?
[16:14] <slangasek> yes, that's fine
[16:14] <barry> volcanos permitting of course :)
[16:15] <cjwatson> French trains permitting in my case I think
[16:15] <cjwatson> (hey, let's take out all the plausible modes of travel at once!)
[16:15] <barry> :)
[16:15] <barry> [TOPIC]  * Farming out tasks that aren't being handled
[16:15] <MootBot> New Topic:   * Farming out tasks that aren't being handled
[16:15] <barry> milestoned bugs:
[16:15] <barry> https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=21447
[16:16] <barry> targetted bugs:
[16:16] <barry> https://bugs.launchpad.net/ubuntu/lucid/+bug
[16:16] <slangasek> if anyone is blocked on the release team for feedback regarding critical fixes (ev, just followed up to the bug you mentioned above), please ping directly; I can't guarantee that the bug queue will get flushed in time
[16:16] <slangasek> mvo: bug #522225 - defer, since you have your hands full with OOo?
[16:16] <mvo> slangasek: sorry, yes
[16:16] <ev> slangasek: already replied to your reply :)
[16:16] <mvo> slangasek: OOo and LP maintenance time
[16:16] <cjwatson> is that the right milestone list?  I wasn't expecting 0
[16:16] <ev> but noted
[16:16] <slangasek> no, it's not
[16:17] <slangasek> 21439
[16:17] <cjwatson> I think it should be =21439
[16:17] <doko> slangasek: I'll ping on visualvm (fix ftbfs, and installability) bug #560138
[16:17] <barry> cjwatson: ah, yes the template doesn't get updated automatically ;)
[16:17] <cjwatson> oh, I promised to do a last double-check of oem-config/debconf and defer
[16:17] <cjwatson> 530027
[16:18] <cjwatson> I'll do that today
[16:18] <slangasek> cjwatson: thanks
[16:18] <cjwatson> bug 540790?
[16:18] <mvo> -updates
[16:18] <cjwatson> and bug 552560?
[16:18] <mvo> for that we need to prod LP again, I can do that
[16:19] <cjwatson> mvo: 540790 milestone bumped
[16:19] <mvo> thanks
[16:19] <cjwatson> I don't see anything else for our team there
[16:20] <slangasek> 553745... not sure that one's going to get fixed, I think Keybuk had a better handle on it than I do
[16:21] <slangasek> 559761 should get done, that one's well understood
[16:21] <barry> slangasek: do you know what's up with the mountall hangs?  i'm still seeing comments on that one, but can no longer reproduce it here
[16:21] <slangasek> barry: "the mountall hangs" is a bit vague, do you have a bug #?
[16:21] <barry> ah, yeah, sec...
[16:22] <cjwatson> 559761 is fix committed already?
[16:22] <slangasek> cjwatson: it's committed in mountall, but the code it's calling in plymouth is buggy and sometimes causes deadlocks again
[16:22] <slangasek> reading when we should be writing, instead of writing when we should be reading like last time
[16:22] <cjwatson> oh, yes, I see you backed it out
[16:23] <barry> slangasek: it's bug 527666 which is fix committed, but still taking in lots of comments
[16:24] <slangasek> oh; there are some issues with mountall not getting notified properly of LVs, which is causing trouble for people
[16:24] <slangasek> I can't reproduce that at all here, unfortunately
[16:24] <slangasek> may be a race condition of some kind
[16:25] <barry> yep.  i've been unable to reproduce it since the fix committed
[16:25] <barry> anything else on milestoned or triaged bugs?
[16:25] <slangasek> oh, bug #566308 has a useful description
[16:26] <slangasek> maybe someone found our bug
[16:26] <slangasek> nothing else from me
[16:27] <barry> slangasek: thanks
[16:27] <barry> [TOPIC] sponsorship queue
[16:27] <MootBot> New Topic:  sponsorship queue
[16:27] <barry> http://people.ubuntu.com/~dholbach/sponsoring/
[16:27] <MootBot> LINK received:  http://people.ubuntu.com/~dholbach/sponsoring/
[16:27] <doko> cjwatson: could you build busybox with a non-multiarch enabled glibc and recheck with it?
[16:28] <barry> anything to say about sponsorship, or should we just move on?
[16:28] <cjwatson> doko: quickest way to do that?
[16:28] <cjwatson> sponsorship at this point would only be appropriate for RC bugs anyway
[16:29] <barry> [TOPIC] Any business from activity reports
[16:29] <MootBot> New Topic:  Any business from activity reports
[16:29] <doko> cjwatson: rebuild using https://edge.launchpad.net/~doko/+archive/ppa. should I provide a busybox build? which arch?
[16:29] <cjwatson> doko: i386 if you could ...
[16:29] <doko> ok, will do
[16:29] <cjwatson> thanks
[16:30] <cjwatson> you think it might be due to one of these fancy SSE memcpy optimisations or something?
[16:30] <mvo> I think I forgot (or was too busy) to send my report, I will do that later today
[16:30] <doko> just want to exclude that
[16:30] <barry> mvo: no, it's my fault.  i forgot i was chair today so only asked for them ~1h ago  ;)
[16:31] <barry> [TOPIC] good news
[16:31] <MootBot> New Topic:  good news
[16:31] <mvo> openoffice finished building on my machine
[16:31] <barry> so, it's official, i've joined foundations (official start is may 1, but i'm not moving back to lp)
[16:31] <cjwatson> doko: ok; I could also try with different kvm cpu emulations if you can suggest ones that would be useful to narrow things down
[16:32] <cjwatson> barry: great news
[16:32] <ev> barry: woo! Great to have you on the team!
[16:32] <oubiwann> barry: woo! welcome to platform!
[16:32] <barry> thanks guys!
[16:32] <slangasek> after the next mountall/plymouth uploads, users will be reliably notified of problems mounting filesystems at boot \o/
[16:32] <slangasek> barry: congrats!
[16:32] <mvo> welcome barry!
[16:32] <james_w> welcome barry!
[16:32] <oubiwann> slangasek: nice...
[16:33] <ev> we'll find out in a little under an hour and a half who the summer of code students are.  There are some foundations projects on the list.
[16:34] <oubiwann> ev: any idea if there's going to be an intersection of SoC projects and UDS sessions?
[16:34] <barry> ev: do we know if any of the gsoc's will be at uds?
[16:34] <james_w> I don't think there will be many SoC students at UDS
[16:34] <ev> oubiwann: I don't know offhand if any potential students are attending
[16:35] <mdeslaur> slangasek: sweet!
[16:35]  * doko is otp
[16:36] <barry> any other good news?
[16:36] <slangasek> doko: bug #560138> you didn't subscribe ubuntu-release, *and* you set it confirmed yourself, so this wasn't even in the queue for review... :)  does this need an FFe, or is it a bugfix release?
[16:36] <barry> [TOPIC] AOB
[16:36] <MootBot> New Topic:  AOB
[16:37] <ev> the volcano seems to have subsided enough to not ruin the release sprint
[16:37] <ev> I think
[16:38] <cjwatson> maaaaybe
[16:38] <cjwatson> assuming katla doesn't go off in which case we're all screwed
[16:38]  * barry books his QEII tickets
[16:38] <cjwatson> amusingly I watched the "Journey to the Centre of the Earth" remake last night ...
[16:39]  * oubiwann laughs
[16:39] <barry> if there's no other business...
[16:40] <barry> #endmeeting
[16:40] <MootBot> Meeting finished at 10:40.
[16:40] <barry> thanks everybody!
[16:40] <barry> oh woops, we need a chair for next week
[16:40]  * james_w volunteers
[16:40] <barry> james_w: thanks!
[16:41] <doko> slangasek: well, I did confirm the uninstallability, and the ftbfs :) just got the sources today from sun. it's a bug fix release, building with netbeans 6.8.  it has new version for two of its plugins
[16:41] <barry> have a good day everybody, maybe see you in 2.5 weeks
[16:41] <ev> thanks!
[16:41] <slangasek> thanks!
[16:41] <mvo> thanks
[16:41] <persia> Whoever owns the agenda for this meeting: would you mind updating the sponsoring URL to http://qa.ubuntu.com/reports/sponsoring/index.html ?
[16:41] <ev> see you next week (possibly) / at UDS (possibly)
[16:42] <slangasek> doko: confirm> but an FFe request is a process bug, if you set it confirmed yourself then it's not in the release team's pending queue
[16:42] <slangasek> doko: anyway - is this something that needs an FFe, or is it just a bugfix release?
[16:42] <barry> persia: will do
[16:42] <persia> barry: Thanks.
[16:43] <cjwatson> persia: I've updated the template, minus the "index.html"
[16:43] <barry> cjwatson: thanks
[16:43]  * barry saw your lock :)
[16:43] <cjwatson> yeah, sorry, acquired the lock before you said
[16:43] <persia> I don't expect we'll change the implementation soon, but that's even more flexible :)
[16:44] <doko> slangasek: bug fix, it was broken by the netbeans-6.8 upload. will allow us to remove some old netbeans libs as well
[16:45] <slangasek> doko: if it's bugfix-only, you don't need an FFe, just upload
[16:48] <doko> slangasek: it's uploaded
[16:50] <slangasek> doko: ah, ok - grabbing now
[17:59]  * marjo waves
[17:59]  * schwuk waves back
[18:00]  * bdmurray flaps arms
[18:00] <marjo> #startmeeting QA Team
[18:00] <MootBot> Meeting started at 12:00. The chair is marjo.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <marjo> [TOPIC] Agenda
[18:00] <MootBot> New Topic:  Agenda
[18:00] <marjo> # SRU testing -- sbeattie (Steve Beattie)
[18:00] <marjo> # Bug Day status -- pvillavi
[18:00] <marjo> # ISO RC testing -- ara
[18:01] <marjo> [TOPIC] SRU testing -- sbeattie
[18:01] <MootBot> New Topic:  SRU testing -- sbeattie
[18:01] <sbeattie> Once again, a very quiet week on the SRU front.
[18:01] <sbeattie> SRU Activity report for the past week (since 2010-04-07):
[18:01] <sbeattie> * karmic: 2 new packages in -proposed (boost1.38, kpackagekit)
[18:01] <sbeattie>       and 2 packages pushed to -updates (keepalived, postgresql-8.4)
[18:01] <sbeattie> * jaunty: 1 package pushed to -updates (postgresql-8.3)
[18:01] <sbeattie> * intrepid: no SRU activity
[18:01] <sbeattie> * hardy: 1 package pushed to -updates (postgresql-8.3)
[18:01] <sbeattie> * dapper: 1 packages pushed to -updates (postgresql-8.1)
[18:01] <sbeattie> Thanks to VTWoods, Wolfgang Pietsch, and Sean for testing SRUs this week.
[18:02] <sbeattie> That said, once lucid is released, SRUs will definitely pick up.
[18:02] <marjo> sbeattie: people are busy with ISO testing?
[18:02] <sbeattie> It sure seems that way.
[18:02] <marjo> thx sbeattie
[18:03] <marjo> [TOPIC] Bug Day status -- pvillavi
[18:03] <MootBot> New Topic:  Bug Day status -- pvillavi
[18:03] <pedro_> On Thursday 15 we had a bug day based on Software Center, the Community contribution was awesome as always: https://wiki.ubuntu.com/UbuntuBugDay/20100415
[18:03] <pedro_> ~126 bugs were triaged that day, Thanks a lot to our hug days heroes: om26eer, yofel, vish, charlie-tca, jibel, hernejj, kamusin,  etali and malev for their extraordinary work!
[18:04] <pedro_> Tomorrow we're having a bug day for Evince: https://wiki.ubuntu.com/UbuntuBugDay/20100422
[18:04] <pedro_> There's plenty of bugs to be triaged so if you have some time and want to learn a bit more about bug triage join us, we'll be glad to help you to start
[18:05] <pedro_> that's all from here marjo
[18:05] <marjo> thx pedro_
[18:05] <marjo> [TOPIC] ISO RC testing
[18:05] <MootBot> New Topic:  ISO RC testing
[18:05] <marjo> the ISO testing seems to be going well
[18:06] <marjo> anybody can help out with http://iso.qa.ubuntu.com/qatracker/build/all/untested ?
[18:06] <fader_> marjo: I should have some cycles this afternoon to pick up some more
[18:06] <fader_> Got the mythbuntu tests done yesterday :)
[18:06] <marjo> there are a few upgrade paths still not covered, so if you have some time & equipment, please consider
[18:07] <Daviey> fader_: you rock!
[18:07] <marjo> helping out for full coverage!
[18:07] <marjo> fader: thx!
[18:07] <fader_> :D
[18:07] <marjo> fader: i don't remember, can you cover amd64
[18:07] <marjo> ?
[18:07] <fader_> marjo: Yep
[18:07] <fader_> In a VM
[18:08] <marjo> ok, thx; i think bladernr and ameetp can also cover amd64, right?
[18:08] <bladernr> marjo:  aye
[18:08] <marjo> on real HW
[18:08] <ameetp> marjo: yeah
[18:08] <marjo> bladernr, ameetp: can you please consider
[18:08] <marjo> thx; would appreciate it
[18:09] <marjo> according to ara, the optional test cases are also getting covered nicely
[18:09] <marjo> thx to everyone who's helping w/ the testing; this phase is looking very good
[18:09] <marjo> any questions on ISO testing?
[18:10] <marjo> folks: any new topics for today?
[18:11] <davmor2> covering m-a now but also in the middle of hell :)
[18:11] <marjo> davmor2: m-a?
[18:12] <davmor2> Migration-Assistant
[18:12] <marjo> davmor2: thx!
[18:12] <cr3> marjo: I've been trying to get the release team to acknoweldge whether a bug in checkbox was release critical or not, still no luck
[18:12] <marjo> cr3: thx for the update
[18:13] <cr3> sbeattie: ^^^ do you think you could help with that?
[18:13] <sbeattie> cr3: which bug?
[18:14] <cr3> sbeattie: see bug #567568 for my proposal which has a comment detailing the specific problems which might be release critical
[18:15] <cr3> sbeattie: I'm perfectly comfortable releasing this as an SRU, but I just wanted to get acknoweldgement
[18:16] <sbeattie> cr3: okay, I think the issue may have been that it was against the checkbox project, and not the checkbox package in ubuntu.
[18:16] <bdmurray> wouldn't the release team notice the bug better if it was filed against ubuntu had was targeted to Lucid?
[18:16] <sbeattie> but I'm fixing that and will target it to lucid.
[18:17] <cr3> sbeattie: thanks!
[18:17] <sbeattie> cr3: it won't make it for rc as it's on the isos and would require a respin.
[18:19] <marjo> cr3: i can't believe that the release team would consider this a "release critical", specially 8 days from release; SRU here we come
[18:19] <marjo> [TOPIC] Release Status
[18:19] <MootBot> New Topic:  Release Status
[18:20] <marjo> down to the wire, the QA team work items look great
[18:20] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa.html
[18:20] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa.html
[18:20] <marjo> only hggdh & sbeattie have work items left until release
[18:20] <marjo> no pressure!
[18:20] <sbeattie> heh
[18:21] <marjo> thx to everyone for meeting all your commitments, per milestone basis, very nice work!
[18:21] <marjo> folks: any other topics for today?
[18:22] <marjo> if not, i propose we adjourn the meeting
[18:22] <marjo> going once
[18:22] <marjo> going twice
[18:22] <marjo> meeting adjourned
[18:22] <cr3> houray!
[18:22] <marjo> thx everyone! keep testing!
[18:22] <fader_> Thanks all
[18:22] <marjo> #endmeeting
[18:22] <pedro_> thanks
[18:22] <MootBot> Meeting finished at 12:22.
[20:00]  * stgraber waves
[20:01] <highvoltage> howdy!
[20:01] <highvoltage> gobby document is on gobby.ubuntu.com
[20:01] <stgraber> just going to get some water, will be back in a sec
[20:01] <highvoltage> docname: edubuntu-maverick-brainstorming
[20:01] <highvoltage> we'll start that a bit later so if you still need to install gobby (or get water) you'll have time
[20:02] <stgraber> ;)
[20:02]  * stgraber looks for the old gobby clinet
[20:02] <stgraber> client even
[20:03] <highvoltage> I'll give a technical summary on the last week so long
[20:04] <highvoltage>  * We had to drop translations from the edubuntu-slideshow since it made the experience way too inconsistant
[20:04] <highvoltage> (something we'll specifically remember to add and promote for maverick)
[20:05] <highvoltage>  * Bunch of bug fixes, mostly beating the live ltsp and ltsp installer stuff into shape, it's about ready for release with the last upload I made today
[20:06]  * stgraber is commenting a bit on gobby
[20:06]  * Lns waves to everyone
[20:06] <highvoltage> hey there Lns!
[20:06] <Lns> hi highvoltage =) sorry i'm late..will probably have to leave early too
[20:07] <highvoltage> Lns: no problem, glad you're here!
[20:07] <bencrisford> hullo everyone :)
[20:07] <Lns> hi bencrisford
[20:07] <highvoltage> we don't really have any big technical or community issues for this meeting, are we all ready to add the ideas to gobby?
[20:08] <bencrisford> highvoltage: mind if i mention the blueprint i found
[20:08] <highvoltage> bencrisford: fire away
[20:08] <highvoltage> 21:01 < highvoltage> gobby document is on gobby.ubuntu.com
[20:09] <highvoltage> 21:01 < highvoltage> docname: edubuntu-maverick-brainstorming
[20:09] <highvoltage> Lns ^^^ you probably missed that
[20:09] <bencrisford> well in the last few meetings we've been talking about team restructuring i.e. deleting inactive/unnecessary ones, fixing needed ones and generally organising and cleaning up
[20:09] <Lns> highvoltage: thanks.. gobby?
[20:10] <bencrisford> then the other day i happened to find a blueprint on exactly this (you might have seen it) assigned to JohnEd
[20:10]  * bencrisford finds blueprint
[20:12] <bencrisford> https://blueprints.edge.launchpad.net/ubuntu/+spec/education-launchpad-groups
[20:12] <bencrisford> there it is
[20:12] <bencrisford> 3 years old
[20:12] <bencrisford> but still relevent
[20:12] <highvoltage> mhall119: I see you joined us on gobby, have you put any thought into perhaps having a gnome-based qimo session in the future?
[20:12] <mhall119> I've been thinking about it, yeah
[20:13] <mhall119> I'll have to figure out all the gnome-settings, since they're different from how Xfce does it
[20:13] <mhall119> but it should be possible to make a Qimo-Gnome session
[20:13] <highvoltage> mhall119: most of it goes into gconf, which actually makes it quite easy to change
[20:14] <mhall119> that's what I thought
[20:14]  * stgraber just moved a few stuff around on gobby and commented on pretty much everything ;)
[20:15] <highvoltage> stgraber: yeah I think things like central authentication should be done from a server team perspective
[20:15] <highvoltage> stgraber: and when it's ready it's just something that we include
[20:15] <highvoltage> (even though it's edubuntu'ish people doin it in the server team)
[20:16] <highvoltage> (I hope I'm making sense)
[20:16] <stgraber> yeah, we can probably give a hand at the server team guys to make that happen
[20:16]  * bencrisford is sad that no-one is interested in the blueprint he found :(
[20:16] <bencrisford> j/k
[20:16] <bencrisford> :P
[20:16]  * stgraber is proudly running ldap+kerberos+gosa at home ;)
[20:16] <highvoltage> I opened it in a tab, haven't looked at it yet
[20:16] <highvoltage> stgraber: nerd!
[20:17] <bencrisford> highvoltage: ok ;) :)
[20:17] <highvoltage> (I've been wanting to do it too for years)
[20:17] <stgraber> highvoltage: well, "home" means over 120 VMs and 10 hosts on 2 continents, 3 countries and 5 physical sites ;)
[20:17] <stgraber> highvoltage: so it's kind of a necesity
[20:17] <highvoltage> bencrisford: yeah that blueprint should probably be added under a ==community== heading
[20:18] <bencrisford> ooh, in the posh gobby doc?
[20:18] <bencrisford> highvoltage: ^?
[20:18] <highvoltage> yes bencrisford
[20:19] <stgraber> bencrisford: btw, are you going to UDS ?
[20:19] <highvoltage> one thing I'd really like to see is getting our script repository being used more
[20:19] <bencrisford> stgraber: fraid not
[20:19] <highvoltage> there's lots of people writing a bunch of useful scripts to simplify admin work that they might want to share but perhaps they're just not aware of a platform
[20:20] <highvoltage> perhaps we should have sessions where we show people how to use bzr and get their scripts up, and also document the scripts on help.ubuntu.com
[20:20] <bencrisford> highvoltage: should I link to that blueprint though?  because its still assigned to JohnEd
[20:21] <bencrisford> RichEd* my bad :P
[20:21] <highvoltage> bencrisford: I'm sure we can get an LP admin to change that for us, so yes
[20:21] <bencrisford> highvoltage: ok, RichEd has been gone a long time then?
[20:21] <stgraber> bencrisford: he no longer works for Canonical
[20:21] <bencrisford> stgraber: ah ok
[20:22] <highvoltage> highvoltage: yep, for more than 2 years iirc
[20:22] <stgraber> highvoltage: more like a year. Barcelona was the first UDS without RichEd, last met him in Mountainview, CA
[20:23] <highvoltage> stgraber: wow, it really feels longer, he was very unavailable for a long time before he left, so I'm probably just thinking of that too
[20:24] <stgraber> yeah
[20:25] <highvoltage> hmm, I'm not sure why but it feels like we're missing something
[20:26] <highvoltage> I guess the next steps would be to make blueprints of stuff we know that we want to do and link them to these items on the wiki page
[20:26] <highvoltage> (busy pasting to https://wiki.ubuntu.com/Edubuntu/Specifications/Brainstorming/Maverick)
[20:27] <highvoltage> things like Sugar and OpenLDAP/Kerberos have always been somewhat tricky
[20:27] <highvoltage> but we can note down any and all risks inside the specification
[20:28] <highvoltage> we should probably split all those items into a few sessions at UDS, the LTSP and authentication items would fall under the server track
[20:29] <highvoltage> you guys are a bit more quiet than usual tonight :)
[20:30]  * highvoltage ads the actions I just mentioned to the doc
[20:30] <stgraber> that's because we are half on irc half on gobby ;)
[20:30] <highvoltage> heh, ok :)
[20:31] <highvoltage> stgraber: did you get that link from akgraner with the interview questions?
[20:31] <stgraber> highvoltage: nope
[20:31]  * stgraber checks
[20:31] <stgraber> nope
[20:31] <highvoltage> stgraber: ok I'll ping you with it after the meeting
[20:32] <stgraber> ok
[20:32] <bencrisford> what interview's that then? :)
[20:32] <highvoltage> I copied the gobby doc contents to the wikipage
[20:32] <highvoltage> (more like, moved it to avoid conflicts)
[20:34] <highvoltage> bencrisford: akgraner is doing an interview with us about Edubuntu, to spread some awareness
[20:34] <bencrisford> highvoltage: thats awesome :), where's is being published?
[20:34] <highvoltage> stgraber: heh, I see you're used to mediawiki formatting atm :)
[20:34] <highvoltage> bencrisford: ubuntu fridge, planet, etc
[20:35] <stgraber> highvoltage: yeah, unfortunately ... I'd love to get rid of that believe me ;)
[20:35] <mhall119> highvoltage: is she doing to get it on Ubuntu User or FCM?
[20:36] <highvoltage> mhall119: probably in Ubuntu User at minimam, not sure about FCM, she did say before but that was a while ago so I'm not 100% sure if it will make FCM as well
[20:36] <mhall119> cool
[20:37] <highvoltage> tomorrow I'll contact our web guys who seem to be a bit rare on IRC when we have meetings :)
[20:37] <highvoltage> we'll try to co-ordinate so that our site is up by the time we get to release
[20:38] <highvoltage> our meeting next week is the day before release, so we can then check through everything and make sure all our release work items are done
[20:39] <bencrisford> awesome :)
[20:40] <stgraber> yep, we really need to hurry on the website as it'll be extremely hard to update next week
[20:40] <highvoltage> oh right due to bandwidth constraints?
[20:40] <bencrisford> highvoltage: btw, just read your edubuntu blog post, thanks for the mention :)
[20:40] <stgraber> nope, due to not having any sysadmin available ;)
[20:41] <highvoltage> heh, ok
[20:41] <highvoltage> bencrisford: you're welcome!
[20:42] <highvoltage> Anyone have anything else for this meeting? I think we got most of the ideas that has been mentioned up until now down
[20:42] <highvoltage> and I think we have a good idea of what we should be doing for the next few days
[20:43] <stgraber> nope, nothing to add here. Seems like we'll get a great release for 10.04 ! congrats everyone
[20:43] <highvoltage> *nod* congrats and thanks!
[20:44] <highvoltage> Meeting adjourned!
[20:44] <highvoltage> *GONG*
[20:44] <bencrisford> highvoltage: :( so its the end of the BONG ?
[20:45] <highvoltage> bencrisford: unfortunately, yes. :)
[20:45] <bencrisford> it doesnt seem right, that the BONG that has served us so well should just be left to gather dust highvoltage


[02:03] <xubuntu82d> Hello Everyone, I am a student developer, working as an intern. I am really grateful to the xubuntu community and want to contribute to opensource. if there is anything i can start with.
[02:06] <Unit193> Well hey, glad you found something that worked for you then!  Are you a programming student or doing something else?
[02:06] <xubuntu82d> yes, i am a programming student
[02:07] <xubuntu82d> i know C, C#, java, Python, i have been learning CI/CD, openshift and docker lately
[02:07] <Unit193> OK, so several of the Xubuntu applications are python, and Xfce stuff upstream are all C.
[02:07] <xubuntu82d> also playing around with opencv.
[02:08] <xubuntu82d> where can i start ?
[02:09] <Unit193> That's a very good question!  I normally do a lot of the packaging so I basically just keep on trucking, I can't say for sure where a good start would be but I think Sean or Simon could steer you in the correct direction.  As Simon is in Europe, he's offline now and won't be around again until at least the morning though.
[02:11] <Unit193> We have a mailing list which we usually use for announcements, and we use this channel to discuss things that crop up.  Due to timezones and busy schedules, it sometimes is hard to catch someone active so we usually either have a bouncer (znc, etc) or use something web based like irccloud if either of those could help you?
[02:11] <xubuntu82d> Thank you! i will stick around.
[02:11] <Unit193> A lot of the Xubuntu stuff is hosted https://github.com/xubuntu, and Xfce stuff is over at https://gitlab.xfce.org/explore/groups?sort=name_desc
[02:12] <Unit193> Perhaps arraybolt3[m] has some ideas for introduction points as well.
[02:13] <xubuntu82d> i see, interesting. I can start with xfce. I will see what i can work on. i really appreciate the guidance
[02:13] <arraybolt3[m]> xubuntu82d: If you don't want to set up an IRC bouncer, you might try using Matrix via element.io - that will catch messages for you even when you go offline.
[02:14] <Unit193> I do apologize for being unable to point you in a good starting point right now, but someone that is a little better organized should be around eventually.
[02:14] <arraybolt3[m]> (Sometimes the Matrix bridge goes down, though, so have IRC handy too so that you can still connect even if Libera glitches out.)
[02:14] <Unit193> If you do register on Xfce's gitlab, poke me with your username so I can give you fork privs.
[02:14] <xubuntu82d> No worries, that's plenty to start with. I will setup the bouncer, and start with xfce
[02:45] <xubuntu82d[m]> Matrix is cool
[02:46] <arraybolt3[m]> xubuntu82d: 👍
[07:33] <ochosi> xubuntu82d[m]: sure, I guess there are some onboarding docs for xfce over at https://docs.xfce.org/contribute/start
[07:33] <ochosi> if you have questions feel free to reach out
[21:47] <Unit193> Oh!  I did upload xfce4-notifyd, just never sync'd it.