[16:53] <robbiew> \o/
[16:53] <Pici> \o
[16:53] <ev> with 7 minutes to spare
[16:53] <robbiew> ev: lol
[16:53] <jpds> Everybody paste what they want to say and read the logs later?
[16:53] <robbiew> screw it now...see ya all in Orlando!!1
[16:54] <barry> yay!
[16:54] <ev> lol
[16:55] <robbiew> Pici: any way to tell who +m the channel?
[16:55] <ev> view the logs?
[16:55] <Pici> robbiew: My log says it was czajkowski
[16:56] <czajkowski> oh I did last night in the meeting
[16:56] <czajkowski> feck my bad
[16:56] <Pici> tsk tsk
[16:56] <robbiew> czajkowski: booo!
[16:56] <robbiew> lol
[16:56] <czajkowski> makes it easier for voting
[16:57] <robbiew> czajkowski: yeah...but makes it hard to have discussions for meetings ;)
[16:57]  * robbiew spent 10min talking to himself...trying to figure out why no one would respond
[16:57] <czajkowski> you're sorted now
[16:57] <czajkowski> moving on nothing to see here. ...
[16:57] <robbiew> lol
[17:13] <charlie-tca> pc3200
[17:28] <charlie-tca> pc5000
[19:51] <mgariepy> mc
[19:54] <highvoltage> ! GNU Midnight Commander is already running on this terminal. !
[19:59]  * mhall119 is here
[20:00] <highvoltage> and just in time
[20:00] <mhall119> \o/
[20:00] <mhall119> not late today
[20:00] <highvoltage> your NTP is working great this week :)
[20:00] <highvoltage> Edubuntu meeting time!
[20:00] <highvoltage> anyone else present?
[20:00] <mgariepy> i'm here
[20:00] <highvoltage> as usual, here's the meeting agenda: https://wiki.ubuntu.com/Edubuntu/Meetings/Agenda
[20:01] <highvoltage> and just to keep everyone on their toes, here's the Natty Release Scedule https://wiki.ubuntu.com/NattyReleaseSchedule
[20:01] <highvoltage> first Alpha is all the way in December!
[20:02] <highvoltage> Monday we launched Edubuntu WebLive
[20:02] <highvoltage> it's been going quite well
[20:02] <highvoltage> http://edubuntu.org/2010-10-18/edubuntu-weblive
[20:02] <mhall119> where is that running?
[20:03]  * stgraber waves
[20:03] <highvoltage> *lots* of people have been tweeting and denting about it
[20:03] <highvoltage> and we've had close to 2000 people who tried it out
[20:03] <highvoltage> (will probably hit that mark before the meeting is over)
[20:03] <highvoltage> mhall119: it's running on stgraber's server in germanny
[20:03] <mhall119> ok
[20:03] <highvoltage> there's a japanese site that translated his blog wrong and said "it's being run by the German stgraber"
[20:03] <stgraber> ;)
[20:04] <mhall119> lol
[20:04] <highvoltage> I also *finally* got around to adding the banner on our website
[20:04] <alkisg> Hi all
[20:04]  * Lns stumbles in
[20:04] <highvoltage> it's been on my todo list since before we launched the website
[20:04] <highvoltage> http://edubuntu.org/
[20:04] <highvoltage> hey alkisg and Lns
[20:04] <Lns> hi highvoltage =)
[20:04] <highvoltage> they're simple and still need some work, but it's a start :)
[20:05] <alkisg> Nice banner but the first slide is about 30 pixels low for me, cutting half of the bottom letters and showing some gray on top
[20:06] <highvoltage> alkisg: ouch! what's your resolution there?
[20:06] <alkisg> Right now 1920x1080
[20:06] <mhall119> only one of the images looks like that for me
[20:06] <alkisg> The other 2 are fine
[20:06] <highvoltage> mind mailing me a screenshot?
[20:06] <highvoltage> (both of you?)
[20:07] <alkisg> http://imagebin.org/119444
[20:08] <highvoltage> alkisg: ah, that whitespace on the top certainly shouldn't be there, what version of Firefox is that?
[20:08] <alkisg> Stock lucid
[20:09] <mhall119> http://imagebin.org/119445
[20:09] <mhall119> using chromium-browser from the repos
[20:09] <alkisg> 3.6.10+build1+nobinonly-0ubuntu0.10.04.1
[20:09] <highvoltage> ah, I think I know what happenned
[20:09] <mhall119> but they sure look nice
[20:10] <highvoltage> (one moment)
[20:12] <bencrisford> *waves*
[20:13] <highvoltage> alkisg, mhall119: could you perhaps refresh? perhaps ctrl+r?
[20:13] <highvoltage> hmm, stgraber says he can still reproduce it :-/
[20:14] <highvoltage> ok I'll look at that after the meeting, that's really quite odd
[20:14] <mhall119> same result
[20:14] <alkisg> same, both firefox + chromium-browser
[20:15] <highvoltage> they both work fine here in firefox + chromium on maverick. just my luck :)
[20:15] <mhall119> strange that it's just the first
[20:16] <mhall119> almost makes me think it's a resolution issue or race condition
[20:17] <stgraber> found the issue
[20:17] <stgraber> highvoltage is fixing it ;)
[20:17] <highvoltage> and done
[20:18] <mhall119> confirmed fixed
[20:18] <alkisg> Yup
[20:19] <highvoltage> since we're fixing my broken stuff:
[20:19] <highvoltage> I did some documentation for LTSP Live and WebLive as well:
[20:19] <highvoltage> http://edubuntu.org/documentation/ltsp-live
[20:19] <highvoltage> http://edubuntu.org/documentation/weblive
[20:20] <highvoltage> might be a good idea to give it a read over and check for mistakes. should be mostly fine though :)
[20:21] <highvoltage> it's kind of weird not seeing the Edubuntu website in the Ubuntu font on your screenshots :)
[20:21] <highvoltage> or at least on the one
[20:21] <highvoltage> I guess we should perhaps make that an embedded font
[20:22] <highvoltage> stgraber is working on getting natty on weblive
[20:23] <highvoltage> will probably have something workable soon
[20:23] <highvoltage> besides that I can't think of anything else to update on :)
[20:23] <highvoltage> oh, hi bencrisford :)
[20:24] <mhall119> highvoltage: do you think Canonical would be willing to do an AWS trial for Edubuntu like they did for ubuntu server on 10/10/10?
[20:24] <highvoltage> mhall119: I don't know, we're talking to Canonical towards the end of next week
[20:24] <mhall119> ok
[20:25] <highvoltage> we'll probably also launch the edubuntu marketplace officially after that
[20:25] <highvoltage> http://edubuntu.org/marketplace
[20:26] <mhall119> highvoltage: as of right now, Zareason doesn't officially sell Qimo preloaded
[20:26] <mhall119> but it should be coming in the nearish future
[20:26] <highvoltage> I think Zareason currently has Linucity's description
[20:27] <mhall119> not quite, zareason's has more text
[20:27] <highvoltage> that doesn't make it right ;)
[20:27] <mhall119> actually, I think they may have eachother's text
[20:27] <highvoltage> probably
[20:27] <mhall119> zareason doesn't customize their installs with extra apps do they?
[20:27] <highvoltage> it's not a final page yet
[20:28] <mhall119> ok
[20:28] <highvoltage> mhall119: it's all just placeholder really, hence the big banner at the top with the big red border around it
[20:28] <mhall119> yeah, I did notice that ;)
[20:31] <highvoltage> should we cancel next week's meeting?
[20:31] <highvoltage> we'll mostly be in Orlando anyway
[20:31] <mhall119> yeah, I think we'll be talking about Edubuntu enough that week
[20:32] <highvoltage> indeed, I'm going to cancel next week's one then
[20:32] <highvoltage> so the next meeting will be 3 November
[20:33] <highvoltage> Hedgemage said that this meeting time doesn't work for her, so I said she can choose a better time,  but I haven't heard anything back yet
[20:35] <highvoltage> oh and mgariepy found a new bug in menueditor as well :)

[20:36] <highvoltage> anything else for this meeting? everyone's a bit more quiet than usual today, perhaps the calm before the storm?
[20:37] <mgariepy> well i didn't, LP#663994
[20:37] <mgariepy> ;)
[20:38] <highvoltage> whoah, in terminator I can right click on that and clock on "Open Link"
[20:38] <highvoltage> that's quite cool
[20:39] <highvoltage> anything else?
[20:39] <mhall119> UDS plans?
[20:40] <highvoltage> we basically have our sessions divided as we discussed on the lists. they still need to be scheduled, that's currently in process
[20:41] <mhall119> jcastro is going to find an empty slow for a Qimo planning session, hopefully on Friday
[20:41] <highvoltage> we'll have at least 3 formal sessions, and probably a lot more inbetween discussions and planning
[20:41] <mhall119> s/slow/slot/
[20:42] <highvoltage> ok great, I'm going to blog about the Edubuntu sessions when the schedule is finalised (will probably happen on monday morning), so let me know when it is and I'll include that as well
[20:42] <mhall119> also, for those coming, Monday evening the Ubuntu Florida Team is hosting a pizza party: http://loco.ubuntu.com/events/team/242/detail/
[20:42] <highvoltage> sounds fun :)
[20:43] <stgraber> mhall119: I'll be there ;)
[20:43] <stgraber> mhall119: arriving in Orlando tomorrow at noon
[20:43] <mhall119> stgraber: oh wow, coming in early
[20:43] <mhall119> stgraber: also, thanks for the contribution
[20:44] <stgraber> mhall119: no problem
[20:44] <mhall119> we aren't asking for outside contributions (otherwise it wouldn't really be 'hosted' by us), but we appreciate them anyway
[20:45] <stgraber> 2021 accounts created on weblive
[20:45] <highvoltage> wow, so it did pass 2000 during the meeting :)
[20:51] <highvoltage> ok, I guess that's it for this meeting!
[20:51] <highvoltage> thanks to everyone!
[20:51] <highvoltage> meeting adjourned! *GONG*
[20:51] <stgraber> see you in Orlando for these of you attending UDS !
[20:59] <jelmer> barry: Hi!
[20:59] <jelmer> barry: Is there going to be a UDD stakeholders meeting today?
[20:59] <barry> jelmer: we should do one, even if it's short.  james_w won't be able to join us
[21:00] <jelmer> oh :-(
[21:00]  * ajmitch is around but doesn't really have anything new to talk about
[21:01]  * jelmer is just glad he has remembered there was a meeting this time.
[21:02]  * ajmitch thought the next one was next week, actually 
[21:02] <jelmer> Next week is UDS
[21:03] <ajmitch> yes, I know you'll be discussing it in depth there
[21:04]  * jelmer won't actually.. I'll be at the GitTogether next week
[21:04]  * ajmitch won't be there but may try & participate remotely, if timezones favour it
[21:05] <barry> we're still 55m away from start
[21:05] <ajmitch> daylight saving time mucking me up again
[22:00] <barry> hi udd folks, ready to start?
[22:00] <barry> #startmeeting
[22:00] <MootBot> Meeting started at 16:00. The chair is barry.
[22:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:00]  * slangasek waves
[22:00] <barry> https://wiki.ubuntu.com/DistributedDevelopment/20101020
[22:00] <barry> [LINK] https://wiki.ubuntu.com/DistributedDevelopment/20101020
[22:00] <MootBot> LINK received:  https://wiki.ubuntu.com/DistributedDevelopment/20101020
[22:01] <poolie> hi all
[22:01] <barry> hi slangasek, poolie, jelmer, ajmitch
[22:01] <flacoste> hi
[22:01] <barry> hi flacoste
[22:02] <barry> james_w sends his apologies
[22:02] <flacoste> barry: thumper should join
[22:02] <barry> thumper: hi
[22:02] <jelmer> hi
[22:02] <thumper> hi
[22:02] <barry> the agenda link is: https://wiki.ubuntu.com/DistributedDevelopment/20101020
[22:03] <barry> [TOPIC] action items
[22:03] <MootBot> New Topic:  action items
[22:03] <barry>    * '''poolie to confirm charline to do user studies at UDS-N''' (ongoing)
[22:03] <barry>  
[22:03] <poolie> done, i think
[22:03] <poolie> i see i have a new mail from her
[22:04] <poolie> very slow, nm
[22:04] <poolie> let's say that's done
[22:04] <barry> poolie: thanks, i'm looking forward to that!
[22:04] <barry>    * '''poolie to organize a foyer poster''' (ongoing)
[22:04] <barry>  
[22:04] <poolie> not done yet, will do that today or tomorrow
[22:05] <barry> cool
[22:05] <barry>    * '''barry to start some sphinx docs to be well-integrated w/ wiki.u.c''' (ongoing)
[22:05] <barry>  
[22:05] <barry> not done
[22:05] <barry> but...
[22:05] <barry>    * '''barry to talk to dholbach about making sure udd is well advertised in pkg guide''' (ongoing)
[22:05] <barry>  
[22:05] <barry> will do that at uds
[22:06] <barry>    * '''barry/poolie to write up job announcements; barry posts to python job board, james_w/slangasek posts to debian-jobs, ubuntu-devel''' (ongoing)
[22:06] <barry>  
[22:06] <poolie> i know you've sent it to python because we got lots of applicants
[22:06] <barry> python jobs board post done.  poolie tells me we have some interesting candidates already
[22:06] <poolie> i haven't seen any from debian so i suspect that wasn't done
[22:06] <poolie> however we probably have a selection, so no more advertisement is needed atm
[22:06] <barry> nice
[22:07] <poolie> incidentally, i'm told that we'll soon have better recruiting management software
[22:07] <poolie> which should be nice for all involved
[22:07] <barry> indeed :)
[22:07] <poolie> (not hraspace :)
[22:07] <barry> i think we can mark this one done for now though, right?
[22:07] <poolie> yep
[22:07] <barry> thanks everyone
[22:07] <barry> [TOPIC] uds prep
[22:07] <MootBot> New Topic:  uds prep
[22:08] <barry> i believe we have 3 sessions scheduled, so it probably makes sense to prep for them.  i plan on at least looking at that over the next two days
[22:08] <slangasek> poolie: do you prefer that I not post it to debian-jobs then, given the tardiness?
[22:09] <poolie> slangasek: yes, better not too
[22:09] <slangasek> ok
[22:09] <poolie> feel free to post other job ads though :)
[22:09] <barry> probably the most work will be for the user session.  i'll have to ping james_w about that tomorrow so we're on the same page.
[22:10] <barry> does anybody have any thoughts about prepping for the sessions?
[22:11]  * ScottK reminds barry he's promised to sit down with me and watch my diff/patch method for porting clamav updates to all releases and see if UDD can help.
[22:11] <barry> ScottK: right, thanks.  we're also going to sit down with mvo for his feedback
[22:12] <barry> there is a "user feedback session" that this will probably be appropriate for, and i'll add action items to the blueprint for that
[22:12] <barry> [ACTION] barry to add ScottK and mvo feedback to uds session
[22:12] <MootBot> ACTION received:  barry to add ScottK and mvo feedback to uds session
[22:12] <ajmitch> you have a few usecases listed for the user feedback session?
[22:12] <barry> ajmitch: i was going to work off of the udd wiki page use cases
[22:13] <ScottK> Please don't distract ajmitch from fixing boost. ;-)
[22:13] <barry> one thing i'd really like to address is getting more reviews and sponsor landings from merge proposals
[22:13] <poolie> i guess all interested parties need to to subscribe to the sessions
[22:13] <ajmitch> ScottK: I can sense your impatience :)
[22:13] <poolie> as in, how to get more reviews?
[22:13] <ScottK> Me?  Impatient?
[22:14] <barry> poolie: well, right now mp's seem to be a black hole.  i don't think sponsors are tuned to looking at mps yet
[22:14] <poolie> :/ ok, that's a good thing to think about
[22:15] <barry> and since i can't sponsor, it's unclear in my mind what *should* be the workflow
[22:15] <thumper> barry: when talking to people about this, can you try to gather work-flow information?
[22:16] <thumper> barry: I'm keen to know how people do use MPs, and how they'd like to use them
[22:16] <ajmitch> there are a few different workflows depending on what's being sponsored
[22:16] <slangasek> solve the "bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from y local mirror" problem?
[22:16] <barry> thumper: sure.  aren't you keen on hooking that up to build-from-branch? :)
[22:16] <slangasek> +m
[22:16] <poolie> so popping up one meta-level, we want
[22:16] <poolie> - to help people understand how to use what is there
[22:17] <thumper> barry: I'm not sure I understand what you are suggesting
[22:17] <poolie> - to make sure we have a good triaged list of what's inadequate - either technically failing, or failing as process
[22:17] <poolie> - to recruit some people willing to try our solutions to the previous point
[22:18] <poolie> heh, so as far as actions:
[22:18] <poolie> - do we need more sessions?
[22:19] <barry> right now, i think "no"
[22:19] <poolie> - i propose we start a list thread to find problems and then carry that on at UDS
[22:19] <poolie> - if we want to go into them in detail i suggest we continue after the 'steering committee' bit of the meeting is over
[22:19] <poolie> therefore, done?
[22:19] <barry> poolie: i like your list. for me it really comes down to having a complete, end-to-end story for devs and sponsors
[22:20] <barry> poolie: thanks.  would you like to kick off that thread?
[22:20] <poolie> i will
[22:20] <barry> thanks!
[22:21] <barry> [ACTION] poolie to start list thread to find problems which can be carried on at UDS
[22:21] <MootBot> ACTION received:  poolie to start list thread to find problems which can be carried on at UDS
[22:21] <barry> any other uds related comments?
[22:22] <poolie> no
[22:23] <barry> [TOPIC] top bug
[22:23] <MootBot> New Topic:  top bug
[22:23] <barry> bug 295274
[22:23] <poolie> nice agenda item!
[22:23] <barry> james_w: and i are going to sprint on that at uds
[22:23] <poolie> that would rock
[22:24] <poolie> current top udd bugs for us: andrew is working on bug 655307
[22:24] <barry> indeed, both because i think it will eliminate a pain point (one which i witnessed first hand yesterday) and because it'll help get me acquainted with the code
[22:24] <poolie> or not
[22:24] <poolie> bug 653307
[22:24] <slangasek> bug 603395
[22:24] <poolie> heaven help us when we get to 7 or 8 digit bugs
[22:24] <poolie> slangasek: that's your nomination, 603395?
[22:24] <barry> we'll have to start tinyurl'ing them
[22:25] <poolie> barry: you know about pad.lv, right?
[22:25] <poolie> i guess it could fold them into base64 but .. shudder
[22:25] <slangasek> poolie: it's the one that breaks every UDD merge I do unless I remember it beforehand; maybe I'm the only one running into it?
[22:25] <barry> poolie: yeah, i was using the generic :)
[22:25] <slangasek> rather, it breaks the branches /after/ I've done a merge
[22:25] <lifeless> barry: hi
[22:25] <barry> lifeless: hi
[22:25] <lifeless> barry: I want you after this meeting :)
[22:25] <poolie> slangasek: i'll bump it up
[22:26] <ajmitch> most people probably use bzr branch instead of checkout?
[22:26] <barry> slangasek: i'll add it to "top bugs".  i haven't hit it because i always branch
[22:26] <barry> lifeless: ooooohhhh :)
[22:27] <slangasek> barry: am I wrong in thinking co is supposed to be cheaper than branch? maybe I should just be larting myself
[22:27] <poolie> a heavy checkout won't be much cheaper
[22:27] <poolie> its main effect is that commits synchronously update the master branch
[22:27] <poolie> a light checkout will be cheap to set up, but it has no local history  cache
[22:28]  * slangasek nods
[22:28] <slangasek> so maybe it's just a bad habit of mine; but it has taken its toll on a number of the UDD branches to date
[22:28] <barry> there is another problem that i always run into, but i haven't figured it out well enough to submit a bug report on.  it seems i always get weird merges in debian/changelog
[22:29] <slangasek> that's the new dpkg-mergechangelogs, I think
[22:29] <poolie> slangasek: it should be reasonably easy
[22:30] <barry> slangasek: hmm, it *seems* like when i merge a branch, i don't get conflicts, but i get some maintainer lines just getting overwritten and other changelog sections moved way down in the file.
[22:30] <poolie> barry: i think bzr builddeb has a hook that tries a smart merge of debian/changelog
[22:30] <barry> but as i said, i need to find a good reproducible test case and understand what's happening better.  i'm usually in yak shaving mode at that point so haven't stepped back to figure out what's going on
[22:30] <poolie> it may not be as smart as it thinks
[22:30] <slangasek> barry: bzr-bd calls dpkg-mergechangelogs, which is good, but doesn't mind when it rewrites the entire history of the changelog prior to the base revision, which is bad :)
[22:31] <barry> slangasek: ;)
[22:31] <barry> poolie: gotcha
[22:31] <barry> next time it happens, i'll at least get a bug reported
[22:31]  * ajmitch used to have the entire changelog appearing as a conflict, so it's improved :)
[22:31] <barry> any other top bugs that are buggin' ya?
[22:31] <slangasek> so I think this is just a bug in bzr-bd needing to be smarter about which changelog entries it passes to dpkg-mergechangelogs for merging
[22:32] <poolie> on our side, the speedup to lp-serve, which should cut ~2 seconds off ssh connection time, is still winding its way through the lp development meatgrinder
[22:32] <slangasek> ajmitch: you'd think it's an improvement, until you notice in the conflict-free diff that it's reordered all your history back to 1998 :)
[22:32] <barry> slangasek: gotcha, thanks, that's definitely helpful
[22:32] <poolie> it may be live next week
[22:32] <barry> poolie: nice
[22:32] <poolie> our next devops-type change after that is to get the package-importer moved into being a LOSA-run and monitored service
[22:33] <poolie> i've seen people complaining about some particular package imports failing
[22:33] <poolie> which is actually a great sign that they care
[22:33] <poolie> so i hope we will find some time to work on that
[22:33] <barry> yep.  do you think it's possible to drive import failures to zero?
[22:33] <ajmitch> barry: not really a bug, but is working with a package that uses a patch system going to be talked about at UDS?
[22:33] <poolie> one question: we're getting many questions from non-ubuntu bzr users about memory usage and large file handling
[22:33] <poolie> does anyone notice this as an issue in udd?
[22:33] <barry> ajmitch: we can.  it's definitely one on my list
[22:34] <slangasek> "large file handling" - er, in the working tree or in the repository?
[22:34] <poolie> both
[22:34] <slangasek> to me "large file" means "> 2GB", I've yet to run into such a file in UDD
[22:34]  * barry has not
[22:34] <poolie> the typical user complaint is "i'm doing game development and i have this multi-GB binary artwork asset"
[22:34] <slangasek> ah, heh
[22:34] <slangasek> ask the ubuntu-docs folks :)
[22:34] <poolie> k
[22:35] <poolie> i'm guessing the top performance thing for UDD would be network latency for branch/checkout/push?
[22:35] <slangasek> I think so
[22:35]  * barry too
[22:35] <ajmitch> those of us in NZ would readily agree :P
[22:36] <thumper> :)
[22:36] <poolie> any more top bug nominations?
[22:36] <barry> tbh, i'm not really affected by it ;)
[22:36] <barry> 5
[22:36] <barry> 4
[22:37] <barry> 3
[22:37] <barry> 2
[22:37] <barry> 1
[22:37] <slangasek> no, not that one
[22:37] <barry> [TOPIC] aob
[22:37] <MootBot> New Topic:  aob
[22:37] <poolie> i have one
[22:37] <jam> poolie: would that include wanting stacked branches/history horizons?
[22:37] <slangasek> bug 1 already gets enough attention ;)
[22:37] <barry> slangasek: :)
[22:38] <poolie> jam, i think at the moment plain roundtrips would be an easier place to start
[22:38] <poolie> eg the get_parent_map calls
[22:38] <poolie> but anything, really
[22:38] <jam> poolie: (I'm wondering if this is initial checkout, or ongoing updates)
[22:38] <poolie> so i'm applying for an Ubuntu developer membership
[22:38] <poolie> https://wiki.ubuntu.com/MartinPool/DeveloperApplication
[22:38] <barry> oh, looms push/pull!
[22:38] <ajmitch> what's the state of working with debian packaging branches that are in git?
[22:38] <poolie> i should have done it ages ago, but here it is now
[22:39] <poolie> if people would like to endorse me i'd appreciate it
[22:39] <poolie> and thanks to barry for already doing so
[22:39] <barry> np
[22:40] <barry> i'm confident you'll get ppu
[22:40] <slangasek> I maintain that having a documented, promulgated solution for UDD branch mirroring, including partial mirrors, is a key to making the workflow viable; lots of devs have local mirrors, and even with decent bandwidth waiting for a fresh download is too much downtime
[22:40] <slangasek> local package mirrors, that is
[22:41] <jelmer> ajmitch: They can be used, but their history is diverged from the history of the package imports.
[22:41] <poolie> i think you're right
[22:41] <slangasek> poolie: I think it's great that you're applying for dev membership, but I'm crap at writing endorsements for these things so hopefully your application doesn't hinge on me doing so
[22:41] <ajmitch> I'd agree there, being reliant on getting branches from 1 location at the moment is just a bit painful
[22:41] <poolie> slangasek: mind if i paste that?
[22:41] <slangasek> poolie: uh... I don't mind :)
[22:42] <poolie> i think you've even sometimes handled my small patches to debian years ago
[22:42] <barry> btw, jelmer perhaps: do you know, is there a lag between package upload and source package branch update? if so, what's the time frame?
[22:42] <slangasek> I can't recall but frankly am happy to assume that's the case :)
[22:42] <poolie> i wonder if we could have a eagerly caching proxy for connections to lp or something...
[22:43] <poolie> there may be something cheap we can do
[22:43] <poolie> slangasek: do you recall if there's a bug for mirroring?
[22:43] <jelmer> barry: Sorry, I don't know how often the package importer runs.
[22:44] <barry> k, np
[22:44] <slangasek> poolie: I haven't opened one, shall I do so?
[22:44] <poolie> i'll have a look, open one, and subscribe you
[22:44] <slangasek> ok, thanks
[22:45] <barry> anything else from the peanut gallery?
[22:46] <barry> in that case...
[22:46] <barry> #endmeeting
[22:46] <MootBot> Meeting finished at 16:46.
[22:47] <slangasek> cheers
[22:47] <barry> thanks everybody and hope to see you at uds
[22:47]  * ajmitch had some rants/other info about branch mirror that should be put somewhere
[22:47] <jam> see y'all next week
[22:49] <slangasek> ajmitch: would be great if you would post those, it might be just the right catalyst for someone to pick up this topic and run with it
[22:49] <ajmitch> slangasek: just found it, was a very brief irc conversation with lifeless awhile ago