[00:58] <Megiddo> when is the next ubuntuforums council meeting?
[06:51] <huats> morning
[06:52] <dholbach> hiya huats
[06:54] <huats> hey dholbach
[06:56] <emgent> @schedule rome
[06:57] <persia> emgent, The bot doesn't know the schedule since the transition to the new calendar.  If you (or anyone) can make SupyBot understand Google Calendar and recurring events, it can be reenabled.
[06:58] <ScottK> \o
[06:58] <huats> morning scottK
[06:58] <didrocks> hello ScottK
[06:59] <ScottK> ola
[07:00] <dholbach> hello everybody! :)
[07:00] <dholbach> soren: around?
[07:00] <soren> o/
[07:00] <dholbach> yoohoo
[07:00] <dholbach> didrocks, huats, Laney: alive and doing well as well? :)
[07:01] <didrocks> dholbach: alive, for sure, at least ;)
[07:01]  * jono high-fives everyone :)
[07:01] <dholbach> didrocks: nervous? ;-)
[07:01] <huats> alive yeah.... and sleeping an bit :)
[07:01] <dholbach> we have an action-packed agenda: https://wiki.ubuntu.com/MOTU/Council/Meeting
[07:01] <didrocks> dholbach: no, it's ok. Just surprised to see huats wake up so early :p
[07:01] <dholbach> let's first chat a bit with Didier Roche
[07:01] <dholbach> :-)
[07:01] <dholbach> https://wiki.ubuntu.com/DidierRoche/MOTUApplication
[07:02] <dholbach> didrocks: you said that you worked on the bzr-desktop documentation - how did that work out generally?
[07:03] <dholbach> is it an easy, intuitive process? something that could be done by default?
[07:03] <didrocks> dholbach: there were an original and deprecated documentation for bzr-desktop team. As I am found of Vcs, I wanted to try to put some packages in bzr
[07:03] <didrocks> so, asking for some tips to james_w, I try to make it easier to use in the process
[07:03] <didrocks> and rewrote the documentation
[07:04] <didrocks> I think now it's quite easy to use. Putting a package in bzr is quite easy nowadays
[07:04] <didrocks> and then, updating a package in bzr is just fantastic :)
[07:04] <didrocks> I think that, as usual, the first step is the harder one
[07:04] <didrocks> but then, it's a gain of time, when you have to diff between two revision, and so on…
[07:05] <dholbach> right
[07:05] <dholbach> all the desktop packages just store the packaging in bzr, right?
[07:05] <dholbach> erm... some of the desktop packages :)
[07:05] <didrocks> we are putting them one by one :)
[07:05] <didrocks> using bzr merge mode
[07:05] <didrocks> and not everyone
[07:05] <dholbach> right, but you don't store the actual source there, right?
[07:05] <didrocks> yes, the merge mode is used to only store debian/ folder
[07:06] <dholbach> could some of the DesktopTeam/Bzr docs go into DistributedDevelopment?
[07:06] <didrocks> I think, yeah, there is some updates to do accordingly to branch destination, but I think I can handle that easily
[07:07] <dholbach> super
[07:07] <didrocks> I have to discuss with james_w about synchronisation
[07:07] <dholbach> ah... talking about documentation: did you document the dh_install --list-missing pbuidler hook? :-)
[07:07] <didrocks> because ATM, packages in ~desktop-team aren't synchronised if someone do not use bzr
[07:07] <didrocks> dholbach: it's on my schedule
[07:07] <didrocks> I want to better document hook
[07:07] <dholbach> didrocks: great, it's going to be handy for lots of others as well
[07:08] <didrocks> dholbach: it's written in the ~desktop documentation one
[07:08] <dholbach> didrocks: where's that?
[07:08] <didrocks> but also, I want to change some little things in the proposed hook
[07:08] <didrocks> dholbach: https://wiki.ubuntu.com/DesktopTeam/Bzr
[07:08] <didrocks> (in updating a package)
[07:08] <didrocks> but, for instance, there is a hook that install/remove/install/purge…
[07:09] <didrocks> it's using depkg -i *.deb
[07:09] <didrocks> dpkg
[07:09] <didrocks> but when you use pbuilder, the external runtime dependency aren't install
[07:09] <didrocks> I was thinking of changing it for dpkg -i *.deb || apt-get install -f
[07:09] <didrocks> to avoid crashing on unresolved dependency
[07:10] <dholbach> didrocks: you could take a look at the check-symbols script, I think kees added some functionality there to do something similar
[07:10] <didrocks> dholbach: ok, I will, I just have used this script once and I have to review huats' work on it :)
[07:11] <ScottK> Is it OK if I jump in with a question?  I need to get to bed.
[07:11] <persia> ScottK, Yes.
[07:11] <dholbach> ScottK: fire away
[07:11] <ScottK> didrocks: I see you used to use KDE.  Have you tried KDE4 yet? (this isn't my actual question)
[07:11] <didrocks> ScottK: hehe. I was sure it was KDE related :)
[07:12] <didrocks> ScottK: I saw KDE 4.2 in FOSDEM and I was really impressed
[07:12] <ScottK> In the Kubuntu team we are also using bzr to store the debian dir.  The basic is https://wiki.kubuntu.org/Kubuntu/Ninjas/ReleasePackaging
[07:12] <didrocks> especially with the "activities" dimension
[07:12] <didrocks> I will have a look at the Ninjas' documentation
[07:12] <ScottK> I was wondering if given your interest in bzr and desktop team you might be interested in working with us a bit and see how the two work flows compare.
[07:13] <ScottK> See what we can learn from each other ...
[07:13] <didrocks> so, yes, KDE 4.2 is a great step forward. I really want to see 4.4 when activities will be bind to worspakces
[07:13]  * ScottK didn't pick the names ...
[07:13] <didrocks> ScottK: for sure
[07:13] <didrocks> ScottK: I will have a look and see how we can bind our workflows
[07:13] <ScottK> vorian: ^^^ Be sure to grab this one the next release.
[07:14] <dholbach> that sounds like a good idea
[07:14] <ScottK> I don't know that it makes sense to 'bind' them, but see what we can learn from each other.
[07:14]  * ScottK sits down.
[07:14] <dholbach> thanks scottK
[07:14] <persia> didrocks, One of your endorsements mentions small mistakes in upload candidates.  What strategies do you expect to use to avoid these in the future?
[07:15] <didrocks> persia: my mistakes were mostly in my first uploads (something like september?)
[07:15] <didrocks> I was more typos and stuff like that
[07:15] <didrocks> (I remember a LP:# ...)
[07:15] <didrocks> persia: I think having commit rights is well different
[07:15] <didrocks> and this kind of responsibality will make you check things 3 or 4 times :)
[07:16] <didrocks> and as I said "when I don't know, I ask"
[07:16] <persia> Fair enough.
[07:16] <soren> didrocks: You mention the server team a bit in your application. How have you found working with the server team? Is there anything we could do to improve?
[07:16] <didrocks> seb128 and dholbach  are used that I bothered them with question
[07:17] <didrocks> soren: I must say that I worked less recently with the desktop team. desktop team is time consuming :)
[07:17] <didrocks> but well, I really want to get involved in both team
[07:17] <didrocks> I find there very kind people and I think it's easy to get involved
[07:17] <didrocks> I hope that, for instance, integration of upstrart, writing event script can make people join the team
[07:17] <didrocks> upstart*
[07:18] <didrocks> for improvement, well
[07:18] <didrocks> I think more call for volonteer in special project can be a great help in that
[07:18] <soren> Really? That's interesting.
[07:19] <didrocks> as I get involved with removal of "multiuser" in init scripts :)
[07:19] <soren> I think we often tend to aim wide to reach more people, but perhaps we should be more specific and just ask more often?
[07:20] <didrocks> yeah, because people are some times, a little bit afraid, I reckon
[07:20] <dholbach> that reminds me of james_w saying "if people scratch their own itches, maybe we need more itching powder" :)
[07:20] <soren> Heh :)
[07:20] <didrocks> knowing that "I can help on that" is easier for them to start
[07:20] <didrocks> dholbach: that's true :)
[07:20] <dholbach> didrocks: one thing I was really interested to read was your experience with Africedu - was it an experience you'd recommend to somebody else? would you do it again? what was the most challenging thing for you?
[07:20] <didrocks> Africedu was really a great experience
[07:21] <didrocks> I think I can share the video (30 minutes) of all the project
[07:21] <didrocks> I would recommend to everyone who has a lot of time (one year project)
[07:21] <dholbach> didrocks: I'd be very very very interested to see it
[07:21] <didrocks> the non governemntal organization still exists
[07:21] <soren> dholbach: Don't get any ideas. We need you here :)
[07:21] <didrocks> it has 10 years now
[07:22] <didrocks> every one, with a new team a new African country
[07:22] <didrocks> so, it's really a human adventure
[07:22] <didrocks> within the team (working together…)
[07:22] <dholbach> that sounds absolutely fantastic
[07:22] <didrocks> and in communication, working with people with different way of living, culture…
[07:22] <didrocks> sharing knowledge, etc.
[07:23] <didrocks> the most challening part is as usual
[07:23] <didrocks> money!
[07:23] <didrocks> it's was quite hard to raise enough founds
[07:23] <didrocks> to ship computers there
[07:23] <didrocks> the most easy part is to find computers :)
[07:23] <dholbach> Ok, let's chat about that some other time again - maybe you should write a long blog post about what you did there :-)
[07:23] <dholbach> soren, persia: any more questions?
[07:24] <persia> Also, you mention an interest in a content control mechanism.  Last month, it was mentioned that Ubuntu ME and ichthux both claim to have one on their websites.  Is your solution similar to the ones used there, or independent?
[07:24] <didrocks> dholbach: for sure, it's quite old now, but why not, posting with the video :)
[07:24] <soren> No, I'm good :)
[07:24] <didrocks> persia: my solution is independant.; I search a lot time for such controls
[07:24] <didrocks> but there aren't at all user friendly to me
[07:25] <didrocks> you can find the result of my research at https://edge.launchpad.net/gchildcare
[07:25] <didrocks> (if you want, I can give you more direct pointers)
[07:25] <didrocks> but they are not integrated in the desktop environment
[07:25] <didrocks> I really want to follow some KISS rules
[07:25] <persia> Do you have any plans to coordinate with others to build a content control model that can be shared by all interested flavours?
[07:26] <didrocks> I have already a guy with another team who joined me
[07:26] <didrocks> and a OOo developper who wants to develop a plugin on it
[07:26] <didrocks> (so, I have still to develop the plugin mecanism ;))
[07:26] <persia> OK.  I'm good.
[07:26] <dholbach> Votes
[07:26] <dholbach> +1
[07:27] <soren> +1!
[07:27] <persia> +1
[07:27] <dholbach> congratulations didrocks!
[07:27] <didrocks> dholbach: thanks \o/
[07:27] <dholbach> :-)
[07:27]  * persia wonders if we oughtn't use MootBot
[07:27] <huats> congratulations my friend !
[07:27] <jono> congrats didrocks!! :)
[07:28] <dholbach> persia: maybe next time? :)
[07:28] <didrocks> thanks huats , it will be your turn soon :)
[07:28]  * didrocks hugs jono
[07:28] <huats> didrocks: let's see...
[07:28] <dholbach> next up: https://wiki.ubuntu.com/ChristopheSauthier/MOTUApplication
[07:28] <persia> dholbach, Sounds like a plan.
[07:28] <huats> hey everyone
[07:29] <dholbach> huats: you've been quite involved in the Desktop team as well - what was your experience like? what do you think should be easier?
[07:29] <huats> I think my experience was great :)
[07:29] <huats> the guy are really great
[07:29] <huats> seb128 is always present by instance
[07:30] <huats> may be it might be interesting to continue the work that was started by norsetto to know the states of the various packages
[07:30] <huats> I think that right now the centralised model we are using in the distribution of work is not optimal
[07:30] <dholbach> what could be improved there? have a link to the page?
[07:31] <huats> and a webpage listing the various states would be better
[07:31] <persia> http://norsetto.890m.com/desktop_packages.php
[07:31] <dholbach> persia: gracias
[07:31] <huats> thanks persia
[07:31] <huats> I think integrating that and most of all, using it might be a more  efficient way
[07:32] <huats> to distribute the work
[07:32] <huats> I have talked a bit with seb about that
[07:32] <persia> huats, You mention you dislike the merging process, and raise this tracker in discussion of the Desktop Team experience.  How would you adjust or improve the workflow if you were responsible for a new definition?
[07:32] <huats> clearly it was a question of lack of time if it hasn't been done so far
[07:32] <dholbach> do you have examples of what should be changed on there to make the Desktop team more efficient?
[07:33] <huats> persia: I will start with your question (sorry dholbach)
[07:33] <dholbach> huats: take your time
[07:33] <huats> persia: I said it was one of the thing I like the least
[07:33] <huats> since there was something to fond :)
[07:33] <huats> found
[07:33] <huats> as I said
[07:34] <huats> I haven't done tons merges
[07:34] <huats> and that is probably the reason
[07:35] <huats> persia: I really think that may be using bzr (or svn in the debian collaboration) might be a solution
[07:35] <huats> to ease the process
[07:35] <huats> besides
[07:35] <persia> huats, How so?  Do you mean the manual merge effort, or the tracking of necessary variance?  You mention working upstream to avoid needing to merge (which is nice), but there are cases where we cannot do that.
[07:36] <huats> I do think that the workflow is great as it is, and I don't see how we can simplify it
[07:37] <huats> persia: one of the advantage of using a VCS might be the revision grouping of modifications
[07:37] <huats> in the same revision you will likely to find things that are related
[07:37] <huats> so you can sort them more easily, and keep the one you need
[07:38] <huats> the manual merge effort still have to be here...
[07:38] <huats> and of course there are cases where the upstream collaboration is not possible...
[07:39] <huats> persia: did I answer your question and can deal with dholbach one ?
[07:40] <persia> Sure.
[07:40] <huats> dholbach: so improvments...
[07:40] <huats> so far we are working mainly on a centralized way, where people go to the channel and ask seb : what can I do...
[07:41] <huats> he is the only one who is keeping records of the stuffs that are needed to do
[07:41] <huats> it might be better to use a common place to store that
[07:41] <huats> there used to be a wiki page
[07:41] <huats> but it was not very useful...
[07:42] <huats> since you have to deal with colors and stuffs like that
[07:42] <huats> having the same kind of page that persia pointed out in the url
[07:42] <huats> might be better
[07:42] <dholbach> so you're saying that it's not clear enough to newcomers what needs doing and what needs special attention?
[07:43] <huats> you can annotate it, saying that you wokr on that (to avoid dupplicate work)
[07:43] <huats> exactly
[07:43] <huats> and you have the various versions available...
[07:43] <dholbach> sounds like a good topic for ubuntu-desktop@, what do you think? :)
[07:43] <huats> well it helps for the beginners AND for people who are daily working on it
[07:44] <huats> absolutly
[07:44] <huats> :)
[07:44] <huats> there was a thread already
[07:44] <huats> (in september if I remember well)
[07:45] <huats> but it was too close of the intrepid release I think...
[07:45] <dholbach> that might be
[07:45] <huats> (and you need some time to be able to set an infrastucture)
[07:45] <huats> even if in that case, it is almost done
[07:45] <huats> (apparently vuntz is using the same kind of stuffs in the opensuse team)
[07:46] <dholbach> huats: can you give us a quick update from the MOTU Mentoring Reception?
[07:46] <huats> dholbach: sure :)
[07:46] <huats> we have currently something like 20 mentee in the junior program
[07:46] <huats> and 2-3 in the senior one
[07:47] <huats> we are a bit short on mentors available everywhere except in europe (the location is important because we try to match mentee/mentors in the same timezone)
[07:47] <huats> currently the main problem is that people sometime drop the mentoring program after a few days...
[07:48] <huats> We have noticed that if your mentee is still here after 2 weeks you have good chances to keep him
[07:49] <huats> I am thinking of asking every mentee to have like a bugpage, where he put the things he did...
[07:49] <huats> (using the example of the great didrocks)
[07:49] <dholbach> sounds like that would help to keep track of what the mentees are doing
[07:49] <didrocks> (I told myself, "hum… it reminds me something"… ;))
[07:49] <huats> so that it will be easier for us (the mentoring team) to notice people who are not doing stufs lately....
[07:50] <huats> and so we can contact him quite fastly enough...
[07:50] <huats> dholbach: exactly
[07:50] <huats> currently I am sending an email to every mentors (something like every2 monthes)
[07:50] <huats> and I am dealing with the answers...
[07:50] <dholbach> huats: who's helping out in the mentoring reception at the moment? is it just you?
[07:51] <huats> dholbach: were a 3 in the reception team
[07:51] <huats> porthose and nxvl
[07:51] <huats> but they are currently quite busy
[07:51] <huats> so for some monthes I a bit alone... but they promised me they will be back ;)
[07:51] <huats> and I trust them :)
[07:51] <dholbach> ok :)
[07:52] <dholbach> a question that was bound to come up: Mr 4k: how do we get those 4000 people in Paris to help out in Ubuntu development?
[07:52] <dholbach> :-)
[07:52] <huats> LOL
[07:52] <huats> by doing more and more stuffs in France :)
[07:52] <jono> I think it should be a requirement of his approval
[07:52] <jono> at least 50% become MOTU in a year :)
[07:52] <huats> jono: thanks :)
[07:52] <huats> I might need some help in the mentoring reception then :)
[07:53] <huats> dholbach: I think bugs jams are a very good start
[07:53] <dholbach> huats: so you're going to do the "developers developers developers" dance in Paris next time?
[07:53] <huats> we are doing one in paris for the global one
[07:53] <huats> (didrocks chairing it)
[07:54] <huats> and I am doing one in Toulouse too
[07:54] <didrocks> (http://blog.didrocks.fr/index.php/post/What-to-do-after-Fosdem-Bug-jam! for more information)
[07:54] <huats> yeah, if we are doing it with didrocks :)
[07:54] <dholbach> didrocks, huats: promise? :)
[07:54] <dholbach> ok... I'm all set :-)
[07:55] <dholbach> soren, persia: any more questions?
[07:55] <huats> you are of course invite to take pictures ;)
[07:55] <huats> or to participate
[07:55] <huats> :)
[07:55] <soren> Nope, I'm good :)
[07:55] <dholbach> huats: I'm sorry, I don't know how to translate "developer" into French :)
[07:55] <huats> the same word
[07:55] <didrocks> dholbach: développeur (2 p) :)
[07:55] <huats> developpeur
[07:56] <dholbach> that's easy enough then :)
[07:58] <persia> soren, Anything?
 Nope, I'm good :)
[07:58] <dholbach> persia: anything else from you?
[07:58] <soren> What dholbach said :)
[08:01] <persia> Nothing else from me.
[08:01] <dholbach> OK
[08:01] <dholbach> Votes
[08:01] <persia> +1
[08:01] <dholbach> +1 from me
[08:02] <dholbach> soren: Señor Hansen? :)
[08:03] <soren> +1 from me too!
[08:03] <dholbach> congratulations huats!
[08:03] <dholbach> :-)
[08:03]  * didrocks hugs huats 
[08:03]  * pochu cheers huats :)
[08:03] <didrocks> congrats my friend :)
[08:03] <huats> thanks guys !
[08:03] <jono> congrats huats! :)
[08:03]  * soren had an angry baby that needed a bit of attention.. Sorry.
[08:03]  * huats hugs didrocks dholbach pochu persia soren
[08:03] <dholbach> soren: I thought you wanted to keep the suspense high :)
[08:03] <dholbach> Laney: around?
[08:04] <didrocks> dholbach: I'm sure of that, soren likes this ^^
[08:04] <jono> soren, drama queen...making huats wait :)
[08:04] <huats> ;)
[08:04] <soren> jono: Yeah, I'm like that. :)
[08:04] <jono> hehe
[08:04] <huats> soren: I knew it
[08:04] <jono> Laney...a man named after my very first guitar amplifier
[08:04] <dholbach> no surprises there
[08:04] <jono> that has to be a reason for approval
[08:04]  * jono chuckles
[08:04] <dholbach> I hope Laney is not having second thoughts
[08:05] <didrocks> jono: :)
[08:05] <dholbach> quoting from https://wiki.ubuntu.com/IainLane/MOTUApplication - section Areas of Improvement: "Iain is unfortunately not very good at applying for MOTU when he should, often waiting some months too long. "
[08:06] <didrocks> dholbach: that's quite a good quotation which can be verified :)
[08:06] <pochu> I guess he hasn't practiced very much :)
[08:07] <didrocks> I am sorry, I really have to go to work now (more than one hour of transportation, Paris \o/)
[08:07] <persia> Well, perhaps this is the practice run :)
[08:07] <didrocks> so you later guys and thanks again ;)
[08:07] <didrocks> see*
[08:08] <dholbach> persia, soren: should we wait a few minutes for Laney to show up or organise an impromptu meeting or ask to show up in the next meeting?
[08:08] <dholbach> or is there a different option you see?
[08:09] <persia> I'm for waiting up to 7 minutes, and then asking for attendance at the next meeting.
[08:09] <soren> I'm with persia.
[08:09] <dholbach> alrighty
[08:09] <soren> Unless the time is bad for Laney, though.
[08:09] <dholbach> AFAIK he lives in the UK.
[08:09] <persia> Well, that's the asking part.  If it's not good, we can expect him to respond, or reschedule.
[08:10] <soren> Ok, so 1700 UTC should be good for him, I suspect.
[08:11] <huats> he was here at the begnning of the meeting
[08:12] <dholbach> huats: I don't think he replied here
[08:12] <soren> He was?
[08:12] <persia> Not in my backscroll, but perhaps not set Away.
[08:12] <huats> dholbach: oh
[08:13] <huats> may be I mixed it indeed...
[08:13] <dholbach> last thing he said yesterday in #ubuntu-motu:    [23:11 UTC]  * Laney cuddles Debian      :)
[08:14] <huats> :)
[08:17] <dholbach> persia: do you think you can send Laney a mail about it?
[08:17] <persia> Sure.
[08:17] <dholbach> I'd take the action points of processing the applications of huats and didrocks :)
[08:18] <dholbach> Next meeting: Feb 26th, 17:00 UTC.
[08:18] <dholbach> Any other business?
[08:19] <dholbach> Going once
[08:19] <dholbach> twice
[08:19] <dholbach> Thanks everybody. Adjourned.
[08:21] <huats> dholbach: I have to go
[08:21] <huats> (going to work)
[08:21] <dholbach> huats: have a great day
[08:21] <huats> thanks everyone
[08:21] <huats> dholbach: I am sure it will :)
[09:44] <Laney> oh CRAP!
[09:52] <soren> o/
[09:52] <dholbach> We're back for an impromptu meeting of the MOTU Council because of mis-scheduling... or something.
[09:52] <Laney> :$
[09:52] <dholbach> persia: want to drive MootBot?
[09:53] <boredandblogging> there is an irc council meeting in a few minutes
[09:53] <dholbach> boredandblogging: takes ~an hour?
[09:54] <dholbach> I mean... does your meeting roughly take an hour?
[09:54] <soren> #ubuntu-mc-meeting?
[09:54] <boredandblogging> dholbach: an hour should be fine
[09:54] <persia> soren, Not logged.
[09:54] <dholbach> soren: we could do it afterwards?
[09:54]  * persia won't be available in an hour
[09:54] <soren> persia: Point.
[09:55] <dholbach> geser, soren, Laney: would you guys be there?
[09:55] <Laney> I'm here all day
[09:55] <soren> Yes.
[09:55] <Laney> besides 1-2pm
[09:55]  * dholbach would be there too
[09:55] <geser> dholbach: that would also give me an hour for a crash review of Laney application
[09:55] <dholbach> excellent
[09:55]  * Laney sets numerous alarms
[09:55] <dholbach> let's recovene in an hour then
[09:55] <Laney> !schedule
[09:55] <Laney> erm
[09:56]  * Laney cannot remember the command
[09:56] <persia> Laney, It's disabled for now.
[09:56] <Laney> right
[09:56] <dholbach> thanks boredandblogging
[09:56] <persia> Laney, Essentially, Supybot needs a plugin to parse Google Calendar feeds.
[10:04] <boredandblogging> elky, jussi01, Pici, Pricey: ping
[10:04] <elky> o hai
[10:04] <jussi01> o/
[10:04] <boredandblogging> hello!
[10:05] <jussi01> where is nal?
[10:05] <elky> not here unless he has to be, i'd guess
[10:06] <Pricey> pong
[10:07] <boredandblogging> should we give nalioth a couple of minutes?
[10:08] <elky> he appears to be detached, judging by his /away
[10:08] <jussi01> Pici: said he is busy, no?
[10:08] <elky> we also have a quorum here, and a queue waiting behind us
[10:09] <boredandblogging> true
[10:09] <jussi01> well lets et it hppening
[10:09] <elky> someone got a link to an agenda?
[10:09] <boredandblogging> https://wiki.ubuntu.com/IrcTeam/IrcCouncil/MeetingAgenda
[10:10] <jussi01> ok
[10:10] <boredandblogging> then let me start
[10:10] <boredandblogging> i realize me being on the council is a bit odd
[10:10] <boredandblogging> been around the community for a couple of years
[10:11] <boredandblogging> spend quite a bit of time on irc
[10:11] <boredandblogging> while I haven't done any ops work
[10:11] <boredandblogging> think I've been involved in lots of different aspects
[10:11] <boredandblogging> and hope that I can be of some help
[10:11] <boredandblogging> particularly in helping the Irc Team communicate better with the rest of the community
[10:12] <boredandblogging> even though Irc so important
[10:13] <boredandblogging> it seems, at least to me, that its hard for the rest of the community
[10:13] <boredandblogging> to know whats is going on with it
[10:13] <boredandblogging> just want to help smooth all that part out :-)
[10:13] <boredandblogging> thats all I got
[10:14] <boredandblogging> anything more on that or shall we move on?
[10:15] <jussi01> I got nothing to add. elky Pricey??
[10:15] <jussi01> except, welcome ;)
[10:15] <boredandblogging> jussi01: thanks
[10:15] <elky> no, i'm distracted in several directions at the moment. dont expect immediate answers.
[10:16] <jussi01> ok, lets move on, if Pricey wants say something then he can in a min.
[10:16] <Pricey> not sure its a dicussion point
[10:17] <boredandblogging> then IRC contributors team?
[10:19] <Pricey> Currently we have the ubuntu-irc team, for 'reccomended operators'.
[10:19] <Pricey> (I don't think it is technically needed any more for ubottu bt access)
[10:19] <Pricey> The CC asked we start thinking about a process for approving Ubuntu membership.
[10:20] <elky> define 'contributor' in terms of IRC. and what scope this involves in terms of what channels
[10:20] <Pricey> yeah...
[10:21] <Pricey> This isn't like the forums, we can't easily see other people's activities unless we were personally in that channel and have logs.
[10:22] <jussi01> should it not then be limited to publically logged chans?
[10:22] <Pricey> jussi01: i've heard the user with the nick "asiudj" has been great, can you go review logs for him on planet.ubuntu.com and come back to us with a report?
[10:22] <elky> jussi01, depends. do you want to trawl #ubuntu logs anyway?
[10:23] <jussi01> hrm
[10:24] <boredandblogging> ask them to provide some evidence from logs in irclogs.u.c?
[10:24] <Pricey> bah, i was reading planet, yeah meant irclogs.
[10:25] <elky> boredandblogging, the problem with doing that is that you'll guaranteed get the good stuff, and not the bad stuff like them telling someone to stfu or rm....
[10:25] <Pricey> boredandblogging: that could be very selective and overwhelming. I want about 3 months contribution I think, and reviewing 60+ days of logs to see what he's done in this other random channel?
[10:27] <boredandblogging> elky: is that the problem with any evidence that a candidate would submit?
[10:27] <elky> boredandblogging, forums are far more searchable than mbs of irc logs.
[10:27] <boredandblogging> true
[10:28] <Pricey> the original memberhsip teams didn't mind that what the candidate produced would be selective, regional ones still don't
[10:28] <Pricey> so i htink we can ignore that
[10:29] <Pricey> but they base a lot of "is this person a good contributor to ubuntu's irc community" on cheers from the ircc for example
[10:29] <Pricey> and we wouldn't have cheered for that unless we had 1st hand experience with the person over a long time.... an operator
[10:31] <elky> yeah. i'm not sure there's a list of checkboxes you can draw up for that either
[10:31] <elky> it'd be a list of 1. and 100% interpretive
[10:31] <Pricey> we have just cheered if we felt they deserved it
[10:32] <elky> exactly
[10:32] <elky> jussi01, Pici, boredandblogging any input?
[10:33] <Pricey> Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | Check out the scheduled meetings at http://fridge.ubuntu.com/calendar
[10:33] <Pricey> bah
[10:34] <boredandblogging> not sure how to do it without some logs
[10:34] <Pricey> operators that operate in the main ubuntu channels are going to be the easiest people to talk abot
[10:34] <Pricey> *about
[10:35] <boredandblogging> would people to able to nominate themselves?
[10:36] <Pricey> well we haven't got any kind of process written down yet, but i assume so as everyone else does it that way
[10:36] <elky> i kind of hope not. we'd have every second banned person applying.
[10:36] <Pricey> and that's not going to make it fun, i see what you're getting at
[10:36] <elky> especially the ones who actually tell us they're going to get us sacked and take down the channels
[10:36] <elky> those are the most fun of all.
[10:39]  * elky prods the screen.
[10:39] <boredandblogging> like RMBs, why not ask for testimonials from operators when users nominate themselves?
[10:39] <Pricey> See if I had my way, we would probably only really be dealing with main ubuntu operators, maybe a very small number of people who would probably have turned down +o etc. That's probably not good enough.
[10:41] <Pricey> What kinds of people do we envisage coming to us for membership?
[10:41] <elky> boredandblogging, the problem with this is a textbook Catch-22. Anyone who wants to be an op is clearly insane and should not be. Anyone who doesn't want to be is clearly sane and shoud.
[10:42] <elky> the ones of us who are -- are the gulliable few from the second category
[10:44] <boredandblogging> are we setting the bar too high? this team is to recognize their good work
[10:44] <boredandblogging> not giving them the keys to anything
[10:45] <Pricey> Is there a demand for this process? Can you think of more then 5 people you would suggest come to membership for this?
[10:45] <elky> Pricey, well, if you want my honest, battleworn and slightly cynical opinion: the people who are least qualified to. the genuine ones are not actually going to ask.
[10:48] <elky> Pricey, currently no. I dont even know who the active helpers are at this present time.
[10:50] <elky> we're running out of time too
[10:50] <jussi01> Sorry guys, had a very important phone call
[10:50] <elky> boredandblogging, Pricey, Pici, jussi01
[10:50] <elky> i think we need to think about this point some more. can we move on to the last so we can hand over to the patient motus?
[10:51] <jussi01> 1 sec
[10:51] <jussi01> I honestly can see some demand for mebership through IRC contribution, BUT! it seems to me, people hwo actually contribute on IRC also contribute other places, so should be handled buy the regional board
[10:52] <Pricey> Unless they are someone from #ubuntu-ops? In which case, they might just contribute there?
[10:53] <elky> in which case we've probably already assimilated them. all ops should be members first, imho.
[10:53] <elky> but, this needs to be thought about some more, and we're out of time.
[10:53] <jussi01> yes, but still why should we deal with it? they go to the regional board, with us in tow, and the regional bord makes the decision - we just cheer/give evidence
[10:54] <elky> boredandblogging, you have another item waiting. were you invisaging that taking any more than 5 minutes?
[10:55] <boredandblogging> no, its just grunt work stuff...
[10:55] <boredandblogging> thinking we should post logs, summaries, do the team reports, etc, et
[10:55] <elky> that sounds like volunteering then.
[10:55] <jussi01> I see no real reason to make 'yet anothe member approval place'
[10:55] <boredandblogging> i can kick off the reporting
[10:55] <boredandblogging> unless someone else wants to do it
[10:56] <elky> boredandblogging, we already post logs... or more to the point canonical does on our behalf.
[10:56] <elky> secondly, summaries of what?
[10:56] <elky> 'hi, we banned joe, billy and mary bob today.
[10:56] <boredandblogging> any decisions, highlights of these meetings
[10:57] <Pricey> bullet pointsont he wiki?
[10:57] <boredandblogging> Pricey: yeah
[10:57] <Pricey> i think the rest of ubuntu would like these reports summarised in the monthly team reports too
[10:57] <boredandblogging> yes, the monthly team reports
[10:57] <elky> Pricey, saying what exactly though?
[10:58] <elky> there's absolutely no way i could summarise a month of my op stuff
[10:58] <boredandblogging> no, just summarizing the council meeting
[11:00] <boredandblogging> is that it for today?
[11:00] <elky> uh ok then. i dont actually see anything reportworthy from this meeting though.
[11:00] <dholbach> bullet points are OK :)
[11:01] <jussi01> thats it for me
[11:01] <jussi01> hi dholbach
[11:01] <dholbach> hiya jussi01
[11:01] <boredandblogging> someone want to set up the next meeting?
[11:02] <elky> boredandblogging, want is probably the wrong word to use.
[11:02] <boredandblogging> hah, we can do it later
[11:02] <elky> good. because now that this is over, i can have friday drinks.
[11:02] <boredandblogging> elky: have fun
[11:02] <jussi01> same day, same time next month? :P
[11:03] <jussi01> Ok, then, meeting over. MOYU's all yours :)
[11:03] <dholbach> gracias!
[11:03] <jussi01> MOTU's ;)
[11:03] <elky> jussi01, dunno at this point. friday evenings are not the stable type for organising things.
[11:03] <boredandblogging> thanks  everyone
[11:03] <dholbach> Laney, geser, soren, persia(?)? :)
[11:04] <Laney> howdy
[11:05] <dholbach> I hope everybody else is busy sponsoring and reviewing
[11:05]  * dholbach is not going to accept any other excuses :)
[11:05] <jpds> Morning.
[11:05]  * persia really isn't here, despite what the client may claim.
[11:05] <dholbach> persia: ok
[11:06] <dholbach> soren, geser: around? well prepared? :)
[11:06] <soren> Yes.
[11:07] <geser> yes, I'm ready for a second try :)
[11:07] <dholbach> #startmeeting
[11:07] <MootBot> Meeting started at 05:07. The chair is dholbach.
[11:07] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[11:07] <dholbach> [TOPIC] https://wiki.ubuntu.com/IainLane/MOTUApplication
[11:07] <MootBot> New Topic:  https://wiki.ubuntu.com/IainLane/MOTUApplication
[11:07] <dholbach> hiya Laney :)
[11:07] <Laney> hello
[11:07] <Laney> apologies for the false start
[11:08] <dholbach> no worries, I think we as the MC want to show that we're flexible after ... some public display of procrastination with other applications :)
[11:08] <Laney> heh
[11:08] <dholbach> Laney: so you're interested in getting stuff upstream earlier and in a more streamlined way - do you have any ideas on how we could do that? is there anything missing today?
[11:08] <Laney> Well
[11:09] <Laney> I don't think there's really anything wrong with our processes
[11:09] <Laney> just that they don't really emphasise the importance of getting stuff back to our upstreams as much as they should (IMO)
[11:09] <dholbach> is it a matter of education and documentation, you think?
[11:09] <Laney> pretty much
[11:10] <Laney> Asking for bug links before sposoring patches, for example
[11:10] <dholbach> volunteering for a UDW session next time? :)
[11:10] <Laney> I'd be happy to do that!
[11:10] <dholbach> excellent :)
[11:10] <dholbach> do you make use of the submittodebian tool?
[11:10] <Laney> yeah, that's how I submit bugs back
[11:10] <dholbach> nice
[11:11] <Laney> it seems to work well
[11:11] <Laney> except I wish it would know how to ignore maintainer field changes
[11:11] <dholbach> sounds like a feature request :)
[11:11] <dholbach> you mention agda in your application, what is it?
[11:11] <Laney> yeah, I started working on it
[11:11] <Laney> ah yes
[11:11] <dholbach> great
[11:11] <Laney> this is a dependently typed programming language which I'm using in my PhD
[11:12] <Laney> (DTP is a language where types can depend on values - a simple example is you can have a type of vectors of a certain length)
[11:12] <dholbach> ah I see
[11:12] <Laney> having better types in your programs gives more assurances that what you're writing is correct
[11:12] <dholbach> Have you found somebody else with an interest in it already to start getting it in Debian/Ubuntu?
[11:13] <Laney> I talked to sistpoty a while ago and he said he'd be happy to look at it too
[11:13] <dholbach> ok
[11:13] <dholbach> In your application you say: "I also support the mighty Nottingham Forest, currently battling their way to safety in the Championship after a shaky couple of months in the relegation zone." - what does that mean exactly? :)
[11:13] <Laney> but I discovered that we're missing some dependencies
[11:13] <Laney> hah!
[11:14] <Laney> This is the football team in my city
[11:14] <Laney> http://en.wikipedia.org/wiki/Nottingham_Forest
[11:14] <MootBot> LINK received:  http://en.wikipedia.org/wiki/Nottingham_Forest
[11:14] <dholbach> ahhh, it was a bit misleading - I was expecting some tree hugging activity going on there ;-)
[11:14] <Laney> sadly nothing so noble
[11:15] <dholbach> geser, soren: do you have questions too?
[11:15] <geser> yes :)
[11:15]  * Laney hides
[11:16] <soren> geser: You go first.
[11:17] <geser> Laney: I read that your are interested in haskell packages and also done a ghc transition already. I've helped with haskell transitions in the past and it was a hell to get the build order right. What's your impression from the haskell transition?
[11:17] <Laney> geser: Yes. Basically I just built all of the packages and then drew a graph of which ones had unsatisfiable build-deps
[11:17] <Laney> debian-haskell are talking about how to get past this
[11:18] <Laney> I think a current idea is to use provides in a clever way
[11:18] <geser> so the haskell packages are in a usable state currently in jaunty again?
[11:19] <Laney> Until the next GHC upload breaks everything, yes
[11:19] <Laney> but we probably won't get another one this cycle
[11:19] <Laney> and things should be better for 6.10
[11:19] <Laney> so maybe we only have to do this pain once more...
[11:19] <soren> Does every ghc upload break things?
[11:20] <Laney> They don't guarantee ABI stability
[11:20] <Laney> so potentially
[11:20] <soren> I mean... Even one without any changes in it? Is it that strict?
[11:20] <soren> Or just ones that actually change internal data structures?
[11:20] <Laney> the problem this time was slightly different though
[11:20] <soren> Or whatever.
[11:20] <Laney> the maintainer +dfsged the upstream version
[11:20] <Laney> and therefore a lot of the dependent packages had to be rebuilt
[11:21] <geser> Laney: and a last question: what's your impression/expierence with working with Debian in general?
[11:21] <Laney> but in general, every upstream release (not each Debian one) will break ABI
[11:21] <Laney> geser: Mixed to be honest
[11:21] <geser> why?
[11:22] <Laney> I love working with packaging teams in Debian, because you get a lot of people with specialist knowledge all working together on a focused set of packages
[11:22] <Laney> but I've found some maintianers unwilling to work with me on things
[11:22] <Laney> some people prefer to do everything themselves
[11:23] <geser> soren: your turn
[11:23] <Laney> and separately, I always feel guilty asking individuals for sponsorship
[11:23] <geser> so the Ubuntu sponsoring models is better?
[11:23] <soren> I'm good, actually. My question was already answered.
[11:24] <Laney> geser: I prefer it because sponsors can take from it when they choose
[11:24] <Laney> instead of being pinged
[11:25] <dholbach> geser, soren: all set?
[11:25] <soren> Yes!
[11:25] <Laney> a lot of Debian teams have more DDs than contributors, so there's a lot of blocking on a single personw
[11:25] <geser> yes, you can take over now again
[11:25] <Laney> which doesn't feel fair to me
[11:25] <dholbach> [VOTE] Should Iain Lane become a MOTU?
[11:25] <MootBot> Please vote on:  Should Iain Lane become a MOTU?.
[11:25] <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
[11:25] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:25] <soren> +1!
[11:25] <dholbach> +1
[11:25] <geser> +1
[11:25] <MootBot> +1 received from dholbach. 1 for, 0 against. 0 have abstained. Count is now 1
[11:25] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[11:25] <soren> +1
[11:25] <MootBot> +1 received from soren. 3 for, 0 against. 0 have abstained. Count is now 3
[11:25] <dholbach> #endvote
[11:26] <dholbach> err
[11:26] <dholbach> ... whatever
[11:26] <dholbach> [AGREED] Iain Lane to become MOTU
[11:26] <MootBot> AGREED received:  Iain Lane to become MOTU
[11:26] <Laney> it's [ENDVOTE]
[11:26] <Laney> ;)
[11:26] <dholbach> [ENDVOTE]
[11:26] <MootBot> Final result is 3 for, 0 against. 0 abstained. Total: 3
[11:26] <dholbach> thanks Laney :)
[11:26] <Laney> \o/
[11:26] <soren> \m/
[11:26] <Laney> nice one chaps
[11:26] <dholbach> [TOPIC] Any other business?
[11:26] <MootBot> New Topic:  Any other business?
[11:26] <dholbach> nothing from me
[11:27] <soren> Nor me.
[11:27] <geser> nope
[11:27] <dholbach> #endmeeting
[11:27] <MootBot> Meeting finished at 05:27.
[11:27] <dholbach> thanks a bunch everybody!
[11:27] <dholbach> congratulations Laney :)
[11:27] <Laney> thanks a bunch
[11:27]  * dholbach will do the honours
[11:27] <dholbach> Laney: shall I directly add you to ubuntu-universe-sponsors? :)
[11:28] <Laney> yes please
[11:28] <dholbach> thanks
[15:01] <slangasek> morning
[15:01] <robbiew> hi
[15:01] <ScottK> o/
[15:01]  * lool waves
[15:01] <dendrobates> o/
[15:02] <pgraner> Yo
[15:02] <pitti> hello
[15:02] <cjwatson> hiya
[15:03] <pitti> don't we have the release team meeting now?
[15:04] <slangasek> yes
[15:04] <slangasek> still doing a head count
[15:04] <slangasek> mdz and rickspencer send their regrets
[15:04]  * rtg is here
[15:04] <slangasek> lool: will davidm be joining us also?
[15:04] <lool> slangasek: No, he gave me his apologies
[15:04] <slangasek> ok
[15:04] <lool> He had a conflicting meeting
[15:04] <pgraner> slangasek: rtg will be the kernel rep this week
[15:05] <slangasek> Riddell, sbeattie: ping?
[15:05] <sbeattie> hey
[15:05] <slangasek> morning
[15:05] <Riddell> hi
[15:05] <slangasek> #startmeeting
[15:05] <MootBot> Meeting started at 09:05. The chair is slangasek.
[15:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:05] <slangasek> and we're off :)
[15:06] <slangasek> [TOPIC] Outstanding actions
[15:06] <MootBot> New Topic:  Outstanding actions
[15:06] <slangasek> I sent out a list of these after the last meeting; I'll skip the ones that I know are resolved
[15:07] <slangasek> (or that are going to be covered later)
[15:07] <slangasek> robbiew: is dbarth on the google calendar invite list for this meeting?
[15:07] <slangasek> I forgot to include him on the agenda mail :(
[15:07] <robbiew> slangasek: yes
[15:07] <slangasek> ok
[15:07] <slangasek> but unavailable today, I guess
[15:08] <lool> slangasek: I invited him, didn't see him right now
[15:08] <slangasek> pgraner: hmm, looks like we have a carry-over item to discuss milestones in the kernel team
[15:08] <lool> robbiew: I didn't seem him in the google calendar event
[15:08] <robbiew> hmm
[15:08]  * lool added him now
[15:08] <robbiew> thnx...strange
[15:08] <slangasek> pgraner: and we didn't get a chance to talk about the "kernel to userspace" communique during the sprint - at the end of the meeting, can we schedule some time to talk about these two items?
[15:08] <robbiew> I added him, but perhaps it didn't update for all meetings
[15:08] <pgraner> slangasek: we can talk later this afternoon if you want...
[15:09] <slangasek> lool: did you chase up bug #299847?
[15:09] <lool> slangasek: I delegated to ogra
[15:09] <lool> ogra: ^
[15:09] <ogra> yeah
[15:09] <pgraner> slangasek: I'm in calls for two hours right after this meeting....
[15:09] <lool> And asked that he sends his findings on the bug
[15:09] <slangasek> pgraner: ok - at the end of the meeting, let's figure out a time that works?
[15:09] <ogra> seems the porter boxes and buildds have issues all other armel devices dont show
[15:09] <pgraner> slangasek: ack
[15:10] <cjwatson> ogra: but on the upside at least it reproduces on the porter box, eh?
[15:10] <ogra> i'm just testbuilding on qemu, it builds fine on all my arm devices here
[15:10] <ogra> yes
[15:10] <slangasek> lool, ogra: where does that leave us, then?  with a critical bug that needs fixed on the buildd/porter boxes, or a standing disabled testsuite for release?
[15:10] <lool> slangasek: We'll continue investigating to understand severity of the issue, the fact that it only happens on one kernel / hardware seems to imply it might not be critical for the other platforms
[15:10] <ogra> porter shows the same behavior as the buildds
[15:10] <slangasek> lool: right; do we have to worry about misbuilds?
[15:11] <lool> Hard to say what might be using the same interface; I don't this particular package or other perl packages in the stack are in danger though
[15:11]  * ogra waits for the qemu build to get to the make test stage just this very moment
[15:11] <lool> I just fear we discover this causes a class of syscalls to misbehave
[15:11] <lool> Hopefully not creating broken binaries
[15:12] <slangasek> ok
[15:12] <lool> slangasek: So we'll continue debugging, nothing to report here apart slow progress in the research
[15:13] <ogra> qemu is fine too btw
[15:13] <slangasek> alright.  Given the size of the "makes a class of syscalls misbehave" unknown, we probably need a final assessment of this well before beta - what are the chances we'll know what's going on two weeks from now at the next meeting?
[15:13] <ogra> (i wouldnt have expected differently)
[15:14] <lool> ogra: Do you think you can finish investigation, perhaps with help from kernel or foundation folks?
[15:14] <ogra> yeah, kernel and IS i think
[15:14] <ogra> i have no clue what they are running on these machines
[15:14] <lool> The kernel is older than the ubuntu jaunty armel ones, so this might be a cause
[15:15] <ogra> right
[15:15] <pgraner> ogra: ping amitk if you need kernel assistance
[15:15] <lool> (the buildd hardware is not supported by our jaunty kernels)
[15:15] <slangasek> ok, moving on
[15:15] <slangasek>  * slangasek to ask armel/versatile/d-i to be added to ISO tracker
[15:15] <ogra> pgraner, yep, i'll also need someone from IS to assist
[15:15] <lool> slangasek: Could you also add NSLU2 and N2100 images?
[15:15] <slangasek> I thought I did the asking, but I don't find it in my logs and it's not done; so I'll follow up on this today :/
[15:15] <slangasek> lool: we're building all of those images currently?
[15:15] <lool> slangasek: Also, make sure to reference the netboot images
[15:15] <ogra> slangasek, versatile and nslu2 are netboot only
[15:16] <lool> slangasek: We do, as inherited from Debian
[15:16] <ogra> not sure about n2100
[15:16] <lool> slangasek: NSLU2 is one of the board we have available in the mobile team and we're trying to enable
[15:16] <slangasek> ok, so what we need is 'netboot arm' added to the tracker
[15:16] <slangasek>  * lool, davidm to provide MID test case documentation for the ISO tracker
[15:16] <slangasek> lool: was this done?
[15:16] <lool> slangasek: I delegated to persia
[15:16] <ogra> slangasek, a link to a howto on the wiki and to the dir that holds the netboot image would suffice
[15:16] <lool> persia: ^
[15:17] <lool> I know he was blocking on the move of testcases to testscases.qa.u.c
[15:17] <slangasek> hmm, ok
[15:17]  * persia is currently drafting, and expects to have something on the wiki soon.  Integration with testcases.qa.ubuntu.com will take longer due to issues with multiple flavour support for that site.
[15:18] <lool> persia: Will you be done on Monday, before A5 testing begins?
[15:18] <slangasek> Riddell: I see bug #289907 is fixed, kudos
[15:18] <persia> Should be done in a couple hours.
[15:18] <slangasek> and that's it for outstanding actions - everything else was taken care of
[15:18] <persia> Is Alpha 5 next week?  https://wiki.ubuntu.com/JauntyReleaseSchedule says the week after.
[15:19] <slangasek> alpha 5 on the 26th
[15:19] <lool> Sorry, it's in two weeks, I'm confused with FF
[15:19] <slangasek> would have had the answer more quickly if gnome-panel's calendar wasn't broken for me right now ;)
[15:19] <slangasek> ok, team reports
[15:19] <slangasek> [TOPIC] QA team
[15:19] <MootBot> New Topic:  QA team
[15:20] <sbeattie> The QA team is still looking for new features to test on an upcoming testing day
[15:20] <sbeattie> Please add them to https://wiki.ubuntu.com/Testing/UbuntuTestingDay/Features
[15:20] <sbeattie> Daily smoke testing continues apace: https://wiki.ubuntu.com/Testing/DailySmoke
[15:20] <seb128> slangasek: use evolution directly ;-)
[15:20] <sbeattie> We're ramping up a new person for hardware testing (fader), but he's still figuring out our infrastructure, so we don't have anything to report on that front.
[15:20] <slangasek> seb128: I have enough apps left open without adding evo :(
[15:20] <fader> Also in QA, I'm working on getting the hardware certification tests running on a regular basis across all the hardware I have access to
[15:21] <fader> But I am currently blocking on access to some systems and on some work by cr3 and schwuk
[15:21] <fader> Hopefully next week I'll be able to say at least a little something useful :)
[15:21] <slangasek> :)
[15:21] <sbeattie> that's all for us for this week.
[15:21] <slangasek> ok, cheers
[15:22] <slangasek> skipping over Desktop for the moment, at pitti's request
[15:22] <pitti> I'm ready
[15:22] <slangasek> oh
[15:22] <pitti> but as you wish
[15:22] <slangasek> [TOPIC] Desktop team
[15:22] <MootBot> New Topic:  Desktop team
[15:22] <pitti> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:22] <slangasek> well then :)
[15:22] <pitti> is our detailled report
[15:22] <pitti> summary, we are still struggling with a couple of Xish bugs, but by and large the largest blocker is getting the Dx work into jaunty
[15:23] <slangasek> do you have code drops scheduled for that?
[15:23] <pitti> we are asking daily, but we won't get them until next Monday or Tuesday
[15:23] <pitti> so far we only have a few internal testers
[15:24]  * slangasek nods
[15:24] <slangasek> is there a need for a wider call for testing?
[15:24] <pitti> we'll send one out as soon as it lands
[15:24] <slangasek> or should the focus be on getting the code landed in jaunty?
[15:24] <slangasek> ack
[15:24] <pitti> oh, internal testin?
[15:24] <slangasek> I meant public
[15:25] <pitti> it should land in jaunty proper ASAP
[15:25] <slangasek> pitti: the status for bug #320632 says "debugging going on" - who's driving this?  based on conversations had with the kernel team during the sprint, I wonder if the remaining issue isn't a kernel regression
[15:25] <pitti> however, on the bright side, all the necessary bugs are filed now
[15:26] <slangasek> a plus :)
[15:26] <pitti> bugs> for the packages we need to fix for notifications
[15:26] <pitti> 320632> I'll talk to bryce
[15:26] <slangasek> also, is there any other potentially-disruptive spec work we should expect to see landing between now and alpha-5?
[15:27] <pitti> the language selector shoudl get a better UI
[15:27] <slangasek> rtg: do you have any insight into bug #320632?  Could the issue with side-scroll not working be related to that kernel regression, and is that synaptics reset issue now fixed in the kernel?
[15:27] <pitti> but it doesn't change functionality, so it's only intrusive in terms of UIF
[15:27] <rtg> slangasek: I have no idea
[15:28] <slangasek> who would know? apw?
[15:28] <ScottK> WRT bugs for notificatios related changes. I've seen bugs filed on Universe packages for this.
[15:28] <ScottK> I don't think MOTU is in a position to maintain a bunch of diff for this  and the changes should just be in Main.
[15:29]  * ScottK had thought that was the plan.
[15:29] <slangasek> [ACTION] slangasek to follow up with kernel team (apw) on the question of bug #320632 being a kernel bug
[15:29] <MootBot> ACTION received:  slangasek to follow up with kernel team (apw) on the question of bug #320632 being a kernel bug
[15:29] <pitti> ScottK: still good for having them, to attach upstream bug refs and patches to them
[15:29] <ScottK> pitti: I think the Ubuntu tasks should be wontfix though.
[15:30] <pitti> ScottK: for all of them? I don't see why interested people shouldn't do/take them if they want
[15:30] <slangasek> that sounds like a discussion we should take to #ubuntu-devel after?
[15:30] <ScottK> OK
[15:30] <slangasek> pitti: anything else from your team?
[15:30] <pitti> not right now
[15:30] <pitti> hopefully we'll have some better news next week
[15:30] <slangasek> [ACTION] ScottK, pitti, slangasek to follow up on question of DX patches for universe
[15:30] <MootBot> ACTION received:  ScottK, pitti, slangasek to follow up on question of DX patches for universe
[15:31] <rtg> slangasek: the only synaptics patch that I'm aware of is the reset issue (which allows synaptics touchpads to be correctly identified)
[15:31] <slangasek> pitti: "we're not breaking the release" is pretty good news as it stands, thanks ;)
[15:32] <slangasek> rtg: right - I think the upshot of that bug is that the synaptics X driver now thinks all touchpads support scroll methods that they don't
[15:32] <slangasek> rtg: anyway, I've taken an action to discuss this further after the meeting
[15:32] <rtg> slangasek: hmm, I'll sic Andy on it since he did the bug work.
[15:32] <slangasek> [TOPIC] Mobile team
[15:32] <MootBot> New Topic:  Mobile team
[15:32] <lool> Our jaunty roadmap is more or less tracked at <https://wiki.ubuntu.com/MobileTeam/Roadmap>.
[15:32] <lool> Since last meeting we dropped/postponed endangered specs and we discussed blockers at the sprint, either with foundations or kernel people; in particular toolchain changes (to enable FPU notably) are out of the picture for jaunty (303232).  However we expect to work on random libs to add VFP (FPU-enabled) flavours to t
[15:33] <lool> hem ASAP; the list is discussed in 303232.
[15:33] <lool> We assigned actions on other teams such as kernel actions to identified individuals where applicable (e.g. armel config fixes, or missing syscalls on armel).
[15:33] <lool> We'd like to link to netboot images as part of the alpha 5 release announcement even if these aren't self-contained; we will be testing them against the archive around alpha time.
[15:33] <lool> We're looking at some potential last minute work on the kernel to add a new flavour, but it remains uncertain that this will land in time for FF.
[15:33] <lool> Finally, we will try to integrate the Poulsbo driver in jaunty as we receive it; first and biggest code drop is expected in the next 10 days.
[15:33] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:33] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[15:33] <slangasek> [LINK] https://wiki.ubuntu.com/MobileTeam/Roadmap
[15:33] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[15:33] <lool> (That's about all the release worthy stuff which I've got)
[15:34] <lool> Basically the vfp lib stuff is in flux right now, and the biggest other items are out of our control
[15:35] <slangasek> lool: does the state of bug #303232 need to be updated to reflect your comments?  If we're not making toolchain changes, gcc-4.3 seems like the wrong package for the bug to be against?
[15:35] <lool> slangasek: Yes; I'll update the bug when I have a list of bugs for library changes as I don't want to let the submitter think we're dropping the ball on the topic
[15:35] <slangasek> ok
[15:35] <lool> (Got an early list of libs earlier today only)
[15:36] <slangasek> you'll open tasks on each of the libs that are going to be changed?  (You said 'list of bugs')
[15:36] <lool> No, I think I'll open new bugs, one for each lib, due to prior bad experience with a bug with a long list of tasks
[15:36] <lool> Perhaps I'll link them to this bug, or another meta bug
[15:37] <slangasek> lool: bug #319729 wasn't on your report webpage, but was in the agenda - anything to say about the status there?  Is the course of action clear for resolving it?
[15:37] <lool> I'm happy to follow the best recommended practice here; I just have had poor experience with things like transition bugs or libv4l enablement and the like
[15:37] <slangasek> [ACTION] slangasek, cjwatson, lool to discuss inclusion of ARM netboot images in the alpha-5 release announcement
[15:37] <MootBot> ACTION received:  slangasek, cjwatson, lool to discuss inclusion of ARM netboot images in the alpha-5 release announcement
[15:38] <lool> slangasek: Thanks for pointing it out, I will ad it to our "roadmap"; it's in the hands of the kernel team to bring this problem up to upstream now
[15:39] <slangasek> ok; I see amitk is assigned to it
[15:39] <slangasek> when we expect him to have an answer back from upstream?
[15:39] <lool> (added to our "roadmap")
[15:39] <slangasek> s/when we/when do we/
[15:39] <lool> slangasek: I don't know; I asked for this during the sprint and reminded by email recently
[15:39] <lool> 2 days ago
[15:40] <lool> I tried subscribing to the upstream list since a month myself, but my subscription is pending moderation
[15:40] <rtg> frankly, I doubt if he's had time to pursue it.
[15:40] <lool> (tried via email and via web)
[15:40] <lool> pgraner: Could you make sure amitk has enough time for this, or assign somebody else?
[15:40] <slangasek> lool: put another way: what's an appropriate deadline by which this needs to be done, in order to keep ARM on track?
[15:40] <ogra> they probably only accept snailmail subscriptions :)
[15:41] <lool> slangasek: That's a good question, neither do we know how much ubuntu breaks without this support; I'm told udev will deadlock randomly due to races
[15:41] <ogra> slangasek, to be honest nobody has seen the bug that can introduce yet
[15:41] <pgraner> lool: we are going to have to let a contract to get that done, I'm in process now of working thru it. However I've been on travel for weeks
[15:41] <lool> slangasek: So anytime our release team is happy for us to add the syscalls to the kernel, and before release I guess?
[15:41] <slangasek> hmm, right
[15:41] <lool> pgraner: Sure, thanks
[15:42] <slangasek> lool: so it's clear that the solution will be to get the syscalls added?
[15:42] <slangasek> as long as that much is clear, we have some time to get the implementation sorted
[15:43] <lool> slangasek: I was told by NCommander that this didn't seem to be overly complex -- but he underlined that he isn't enough into kernel stuff to judge -- so that would be the preferred solution, yes
[15:43] <lool> I don't know whether any other exist; AFAIK, newer udev just relies on that unconditionally
[15:43] <slangasek> ok
[15:43] <pgraner> slangasek, lool: do we have a bug that *demonstrates* this behavior
[15:44] <ogra> we would need to ask Keybuk to provide a testcase
[15:44] <lool> pgraner: No; I think Keybuk might have more information as he pointed out this syscalls as required for future upstart
[15:44] <ogra> he brought it up
[15:44] <lool> ISTR he mentionned upstart / init hanging without them
[15:44] <lool> *these
[15:44] <ogra> and udev
[15:44] <cjwatson> it's a race, so a deterministic reproducer will be tough ...
[15:44] <pgraner> lool: If we do this it will be expensive and I find it hard to believe if its that big of an issue it has not been fixed upstream yet
[15:44] <lool> I don't think he saw udev hanging
[15:44] <Keybuk> pselect() ?  it's part of POSIX!
[15:44] <NCommander> Keybuk, glibc provides an emulation of it if the kernel doesn't
[15:44] <Keybuk> it's not been done upstream because Russell King simply doesn't implement anything he doesn't need
[15:45] <cjwatson> NCommander: the emulation doesn't fix the race
[15:45]  * NCommander is now backish for five minutes.
[15:45] <lool> pgraner: New udev only came out recently; perhaps it's fixed in 2.6.29 and we don't have it?  I don't know
[15:45] <Keybuk> NCommander: the emulation suffers the exact race condition the syscall was designed to avoid
[15:45] <pgraner> Keybuk: Is the definitely needed for Jaunty? If not we can work it for 9.10
[15:45] <NCommander> Keybuk, no, I know, I'm just saying why glibc has it even though our kernel doesn't :-)
[15:45] <Keybuk> pgraner: if the syscall is not implemented in the kernel, you will have random hangs in any program that uses pselect() or ppoll()
[15:45] <lool> Keybuk: We plan to ship products based on jaunty/arm and tell people to install it; is it a serious issue which will prevent the use of jaunty?
[15:45] <Keybuk> lool: I believe it is a critical issue
[15:46] <lool> THanks
[15:46] <slangasek> Keybuk: can you quantify the probability of such hangs?
[15:46] <Keybuk> slangasek: no, it's a race condition
[15:46] <Keybuk> I can describe it
[15:46] <Keybuk> you have a main loop
[15:47] <cjwatson> a small test program that loops a zillion times around pselect would probably be vaguely helpful
[15:47] <Keybuk> your main loop, like just about every other, is a loop around a select() or poll() call that sleeps until there is activity
[15:47] <Keybuk> you want that woken up by a particular signal
[15:47] <Keybuk> but you don't want those signals otherwise being delivered to your process
[15:47] <slangasek> Keybuk: maybe this would be better left for after the meeting then, we've already overrun the mobile team's slot
[15:47] <Keybuk> so you set a signal mask to include that signal
[15:47] <Keybuk> and before you select()
[15:47] <Keybuk> restore the original signal mask
[15:47] <Keybuk> select() with the original signal mask (so the signal can be caught)
[15:47] <Keybuk> then restore the previous signal mask again after
[15:48] <slangasek> Keybuk: #ubuntu-devel or elsewhere, please
[15:48] <Keybuk> the race is that the signal can be delivered between the calls to sigprocmask() and select()
[15:48] <lool> slangasek: Any other question on the list of things I dumped?
[15:48] <Keybuk> if that happens, you will stay in sleep even though the signal has been delivered
[15:48] <slangasek> lool: nope, thank you
[15:48] <slangasek> [TOPIC] Kernel team
[15:48] <MootBot> New Topic:  Kernel team
[15:49] <rtg> need wireless-crda promoted to main (which pitti has promised to do)
[15:49] <slangasek> rtg: bug #308387 is a one-liner control file change that's been lingering for a bit; who can take care of getting this fix into the next kernel upload?
[15:49] <rtg> slangasek: I think its done
[15:50] <rtg> "Added libdrm-dev as a 'Replaces' to linux-libc-dev" in 2.6.28-8.21 changelog.
[15:51] <slangasek> rtg: ah, you closed it an hour ago, ok :)
[15:51] <slangasek> wireless-crda> I don't have a bug number on my watch list for that, is there an open bug that should be escalatd?
[15:51] <rtg> slangasek: yeah, I've been slogging through several
[15:51] <rtg> there is an MIR
[15:52] <slangasek> bug #325801
[15:52] <rtg> yes
[15:52] <slangasek> what does not having wireless-crda block us on?
[15:52] <lool> slangasek: wireless-crda was just added to Ubuntu a couple of days ago
[15:52] <pitti> saw it a couple of hours ago, will get to that asap
[15:52] <rtg> The kernel won't install because wirel;ess-crda is a dependency
[15:52] <lool> MIR has been set in progress some hours ago
[15:53] <lool> By Kees IIRC
[15:53] <pitti> lool: but not approved,  right?
[15:53] <pitti> (yet)
[15:53] <lool> in progress is approved AFAIK; albeit I had some comments against it
[15:53] <slangasek> targeted to jaunty now
[15:53] <lool>        Status: New => In Progress
[15:54] <slangasek> rtg: er. why is it a depends instead of a recommends, which is what was suggested in the bug log?
[15:54] <rtg> because its a requirement for CRDA. why wouldn't it be a depends?
[15:54] <slangasek> definitely an alpha-5 issue if the kernel can't be installed, though ;)
[15:54] <pitti> depends sounds too strong, there are certainly pleny of systems without any wifi at all?
[15:54] <cjwatson> when I was asked about this, I said Recomments
[15:55] <cjwatson> Recommends
[15:55] <cjwatson> for pitti's reason
[15:55] <lool> Yes, I wasn't personally sure whether this should be pulled by some higher level meta package or the kernel itself; I don't mind where but I want it to be optional in some use cases as well
[15:55] <rtg> I'll defer to you guys. I just think it really needs to be installed.
[15:55] <pitti> rtg: recommends just means that people can uninstall it, it'd still be installed by default
[15:55] <slangasek> rtg: recommends -> installed by default, but users who don't have wifi can uninstall it for a slimmer system
[15:55] <rtg> we have no kernels that do not also have wireless.
[15:55] <lool> There was the question of upgrades; hopefully people don't turn off recommends
[15:56] <slangasek> lool: users who do that are shooting themselves in the foot generally
[15:56] <rtg> slangasek: CRDA is really small.
[15:56] <cjwatson> I actually wondered why this isn't simply part of udev
[15:57] <rtg> 'cause its not part of the udev upstream
[15:57] <cjwatson> "why this isn't simply part of udev upstream"
[15:57] <slangasek> right; anyway, Recommends vs. Depends doesn't need to be hashed out here and now
[15:57] <rtg> disparate developers I guess
[15:57] <cjwatson> maybe that's something that needs to be talked about
[15:58] <slangasek> rtg: do you know if there's progress on bug #261318?
[15:58] <slangasek> ... right, 'fix released', guess so
[15:58] <slangasek> (bah, developer race conditions)
[15:58] <rtg> I was looking at that. I thought we revereted to tochiba_acpi (which should fix the probnlem)
[15:59] <rtg> toshiba_acpi, even
[15:59] <slangasek> sounds right
[16:00] <slangasek> the last bug I had on the list is #88746
[16:00] <slangasek> IIRC I targeted this to jaunty because someone had already accepted a nomination for hardy
[16:00] <rtg> bug 88746
[16:00] <slangasek> but I don't know that anyone is working on it currently?
[16:00] <slangasek> (or if it's even actionable, honestly)
[16:01] <rtg> oh, that one. there are 472 comments.
[16:01] <slangasek> yes
[16:01] <rtg> I've never been able to get a handle on it.
[16:01] <slangasek> what would help us get a handle on it?
[16:02] <slangasek> do we need to get users to give us PCI IDs for their USB controllers, and get them to confirm that the devices work at USB2.0 speeds under !Linux?
[16:02] <rtg> danged if I know. get a platform that exhibits the problem?
[16:02] <rtg> looks like upstream has declined the bug report as invlaid
[16:03] <rtg> uh, nevermind. I misread that
[16:04] <slangasek> is there someone on the kernel team who could take care of distilling this bug?  or should we ask the QA team for help?
[16:04] <rtg> lets put it this way, I have no plans to address this bug before release.
[16:05] <slangasek> well, it's also been marked as an SRU candidate for hardy; so if we're not going to handle the bug we should follow through on documenting this in the bug state
[16:06] <rtg> sure
[16:06] <slangasek> [ACTION] slangasek to follow up on bug #88746
[16:06] <MootBot> ACTION received:  slangasek to follow up on bug #88746
[16:07] <slangasek> rtg: anything else we should discuss before moving on?
[16:07] <rtg> CRDA was the big item for me.
[16:07] <slangasek> ok
[16:07] <slangasek> [TOPIC] Foundations team
[16:07] <MootBot> New Topic:  Foundations team
[16:07] <slangasek> cjwatson:
[16:07] <slangasek> robbiew: you too, though I guess I saw cjwatson preparing the report :)
[16:08] <robbiew> I'll defer to cjwatson, as I would just be a "parrot" for cjwatson's report..
[16:08] <cjwatson> hah
[16:09] <cjwatson> ok, bugs first
[16:09] <cjwatson> 325690: (udev breaks cryptsetup initramfs hook) - fix committed
[16:09] <cjwatson> 323602: (kernel upgrade fails when casper is installed(?)) - this is probably bug 292159, which I've discussed with Evan and we'll get fixed after FF
[16:09] <cjwatson> 322482: (update-manager fails over remote GDM) - almost certainly not really an update-manager problem, as Steve points out, but it's true that there are lots of things that can go wrong in this scenario and a warning does seem called for; we'll get this fixed after FF, just need to figure out the best detection method
[16:09] <cjwatson> 313218: (IPv6 causes slow Internet access) - still on my plate for as soon as I get feature work out of the way; there's been good progress upstream for at least a workaround
[16:09] <cjwatson> 303515: (passwd gives wrong return code on failure) - this one's Steve's, likely to make progress upstream within the next few weeks
[16:09] <cjwatson> 311228: (extra translations not installed for the default language) - fix committed
[16:09] <cjwatson> 44194: (wpasupplicant interfaces don't start right with separate /usr partition) - I meant to discuss this at the sprint but didn't have time. One possible fix would be for all necessary binaries and libraries to be outside /usr, and to use somewhere like /var/run in case the root filesystem is not writable yet.
[16:09] <cjwatson> 309215: (python-numpy vs. pygtk package split) - still an open question
[16:09] <cjwatson> 325257: (migration-assistant incompatible with encrypted home directories) - per security team comments on lack of encrypted swap, we're going to have to disable encrypted home on the desktop CD, so this is moot for jaunty but we'll look at it anyway
[16:10] <cjwatson> regarding feature freeze, major things yet to land are a couple more installer changes (including manual package selection for server installs and some more timezone map changes in ubiquity), python2.6, update-manager/computer-janitor merge, hwclock and console changes for boot performance
[16:10] <slangasek> (ack on 44194, that was my thought as well)
[16:10] <cjwatson> I NEWed python2.6 source earlier and should be able to NEW the binaries before leaving for the day
[16:11] <cjwatson> (I'll be offline all weekend)
[16:11] <cjwatson> robbiew: any other relevant feature bits I'm missing?
[16:11] <robbiew> no...not that I'm aware of
[16:12] <cjwatson> hmm, python2.6 failing on lpia not a good sign
[16:13] <cjwatson> anyway, yeah - my general feeling from our last foundations meeting was that it's a bit of a sprint to the finish, but that most people are fairly well on track
[16:13] <slangasek> sounds good, thanks
[16:13] <slangasek> [TOPIC] Server team
[16:13] <MootBot> New Topic:  Server team
[16:13] <slangasek> dendrobates: hi-yo
[16:14] <dendrobates> slangasek: nothing big from us.
[16:15] <slangasek> dendrobates: I gave you two bugs in the agenda so you didn't feel left out :)  is jdstrand owning bug #305264?  we discussed at the sprint that the openldap behavior should be changed so it's consistent when built with gnutls vs. openssl
[16:15] <ScottK> I'll toss in that clamav 0.95 is expected in ~ 1 month another set of "let's break all the libclamav rdepends" changes.  They promise though that this is the one true last redesign.
[16:16] <slangasek> or if not jdstrand, is there someone else on your team who can drive it?  (mathiaz?)  I'm happy to make sure the Debian openldap packages follow suit, but I don't have time right now to figure out what needs patching
[16:16] <robbiew> dendrobates is on a call, so he may need to follow up via email
[16:16] <slangasek> ScottK: heh
[16:16] <slangasek> robbiew: ah, thanks
[16:17] <slangasek> ScottK: and 0.95 is intended for jaunty?
[16:17] <robbiew> has his head in the clouds ;)
[16:17] <dendrobates> slangasek: mathiaz should handle anything ldap related.
[16:17] <slangasek> [ACTION] slangasek to follow up with mathiaz on bug #305264
[16:17] <MootBot> ACTION received:  slangasek to follow up with mathiaz on bug #305264
[16:17] <ScottK> slangasek: I'd say so if we can unbreak the rdepends in a reasonable time.
[16:17] <ScottK> I've talked with Debian and upstream about a svn snapshot in experimental soonish so we can start working.
[16:18] <slangasek> ok, great
[16:18] <slangasek> dendrobates: thanks
[16:18] <slangasek> [TOPIC] MOTU
[16:18] <MootBot> New Topic:  MOTU
[16:18] <slangasek> ScottK: still you, then :)
[16:18] <ScottK> Yeah.
[16:18] <ScottK> We got a volunteer for our 5th person, so it seems we'll be fully manned.
[16:19] <slangasek> excellent
[16:19] <ScottK> My biggest concern right now is Lenny releasing 5 days before feature freeze, what will get uploaded and what that does to the sponsorhip quueu
[16:19] <ScottK> for some better spelling of queue
[16:19] <slangasek> hmm
[16:19] <cjwatson> you can always say no to merges :)
[16:20] <ScottK> We also have a charter we're working with other MOTUs to clarify what it is we are supposed to be doing.
[16:20] <ScottK> It's sort of grown organically up to now.
[16:20] <slangasek> right; based on my experience with Debian post-release uploads, saying no might be a good idea anyway :)
[16:20] <ScottK> heh.
[16:20] <james_w> perhaps a mail to -motu@ would not go amiss?
[16:20] <ScottK> That's it for MOTU I think.
[16:20] <ScottK> james_w: For the post-release question?
[16:20] <cjwatson> I think Mark Hymers' mail to d-d-a is apposite
[16:21] <ScottK> We'll deal with it one way or another.
[16:21] <cjwatson> "We'll drop an email to d-d-a again once this happens and then go and hide somewhere while everyone uploads a new version of every package to sid simultaneously :-)"
[16:21]  * slangasek grins
[16:21] <james_w> ScottK: to explain that there will be an explosion of things in MoM, and we probably don't want them all
[16:21] <ScottK> Ah.
[16:21] <ScottK> Makes sense.
[16:22] <ScottK> james_w: I have to drop offline shortly after this meeting, would you draft something?
[16:22]  * lool suggests we sponsor beer to Debian to make sure everybody is drunk for long after the release
[16:22]  * ScottK suspects lool is wearing his Debian hat when he suggests that.
[16:22] <james_w> ScottK: I'll draft it and let you take a look
[16:22] <slangasek> [ACTION] james_w to draft an email to -motu about handling of post-lenny-release MoM explosion
[16:22] <MootBot> ACTION received:  james_w to draft an email to -motu about handling of post-lenny-release MoM explosion
[16:22] <lool> ScottK: argh!
[16:22] <ScottK> That's it for MOTU.
[16:23] <slangasek> lool: I'm not sure why you think that would reduce upload frequency, as opposed to upload quality ;)
[16:23] <slangasek> ScottK: thanks :)
[16:23] <lool> haha
[16:23] <slangasek> [TOPIC] General feature update
[16:23] <MootBot> New Topic:  General feature update
[16:23] <ScottK> james_w: You can mail me, as I'll be getting mail.
[16:23] <slangasek> (AKA: AOB?)
[16:24] <pitti> thanks slangasek
[16:24] <ScottK> It looks like we now have functional kernels/libdrm on all the ports archs.
[16:24] <slangasek> goodgood
[16:24] <slangasek> I think all the other features I'm aware of being in the pipe have been covered, so...
[16:25] <ScottK> I've been working on getting the rebuild sequence right for KDE.
[16:25] <ScottK> On hppa I will be blocked by Bug #311952
[16:25] <ScottK> I'd appreciate it if someone could talk to the LP people about that one.
[16:26] <ScottK> (since the bot isn't helping, it's a PAS problem that makes it so kdebidings gets skipped on hppa)
[16:26] <slangasek> ah, hmm
[16:26] <slangasek> cjwatson: I think we also need to talk through management of P-a-s for Ubuntu now that Debian has moved to git
[16:27] <slangasek> pkern sent a mail to u-devel, I don't think there was any followup there
[16:27] <ScottK> For intrepid, we have KDE 4.1.4 in -proposed and it is just lacking verificaton of https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/318866
[16:27] <ScottK> Unfortunately haven't found someone with a USB printer to test it.
[16:27] <ScottK> I was wondering if sru-verification could take that one on so we can get the set pushed to -updates.
[16:28] <cjwatson> slangasek: yes, we'll need to grab infinity for that
[16:28] <cjwatson> slangasek: assuming that we can't just continue to pull it
[16:28]  * ScottK sits down.
[16:29] <slangasek> sbeattie: can you help with that KDE SRU verification ScottK mentions above?
[16:29] <sbeattie> ScottK|slangasek: yeah, I can take a poke at that one.
[16:29] <slangasek> thanks
[16:29] <ScottK> sbeattie: Thanks.
[16:30] <ScottK> pitti: Once that one is verified, I think we can push 4.1.4 (all package bugs tagged kde4.1.4.)
[16:30] <pitti> \o/
[16:30] <slangasek> and I'll summarily truncate "Hardware testing, ISO size" since I think everything's been said which needs to at this point
[16:31] <jdstrand> slangasek: IIRC we wanted to SRU the gnutls bug. I can take it
[16:31] <jdstrand> dendrobates: ^
[16:31] <slangasek> so I think were done here - thanks, all
[16:31] <slangasek> #endmeeting
[16:31] <MootBot> Meeting finished at 10:31.
[16:31] <pitti> thanks all