[12:30] <nictuku> hi, I need to give the ownership of #ubuntu-br to someone else, and I wanted to know what you think is the best to do. is this a fine place to discuss that?
[12:31] <nictuku> I would either give licio the ownership, or to someone that already manages other channels
[12:33] <HedgeMage> nictuku: Check with Seveas... he's the best person for that sort of info
[12:35] <Burgwork> nictuku, -locoteams is a good place
[12:35] <nictuku> thank you
[12:35] <Seveas> nictuku, /msg chanserv set #ubuntu-br contact licio
[12:35] <Seveas> and give him the channel password
[12:35] <Seveas> that's all 
[12:35] <Hawkwind> Simple as that :P
[12:36] <nictuku> well, I know *how* to
[12:38] <nictuku> the brazilian locoteam has collapsed in disputes, and I don't want to make that worse. It would be nice if I we found a 'neutral' way out.
[12:40] <licio> hot potato in my hands
[12:40] <licio> :P
[12:43] <Burgwork> nictuku, the best way is simply not say anything and let it cool down
[12:45] <nictuku> Burgwork, I've done that for months, and now things are frozen in the community
[12:47] <Burgwork> hmm
[12:47] <Burgwork> shall we move into -locoteams?
[03:01] <nictuku> hey, jono = jsgotangco ?
[03:01] <jsgotangco> hell no
[03:01] <jsgotangco> ;)
[03:01] <jsgotangco> jono is probably asleep now
[03:01] <nictuku> blame tab completion
[03:01] <nictuku> hehe /nickserv info j<tab>
[03:23] <brendonjt> !schedual auckland
[03:23] <brendonjt> !scheduale auckland
[03:24] <brendonjt> !schedule auckland
[03:25] <Hawkwind> Try @schedule
[03:26] <brendonjt> @schedule auckland
[03:26] <Ubugtu> Schedule for Pacific/Auckland: 13 Sep 08:00: Technical Board | 14 Sep 08:00: Edubuntu | 14 Sep 19:00: Ubuntu Development Team | 20 Sep 00:00: Community Council | 21 Sep 00:00: Edubuntu | 22 Sep 03:00: Ubuntu Development Team
[05:00] <PWill> http://digg.com/linux_unix/Ohio_Linux_Fest_2006
[03:30] <GNAM> @schedule rome
[03:30] <Ubugtu> Schedule for Europe/Rome: 12 Sep 22:00: Technical Board | 13 Sep 22:00: Edubuntu | 14 Sep 09:00: Ubuntu Development Team | 19 Sep 14:00: Community Council | 20 Sep 14:00: Edubuntu | 21 Sep 17:00: Ubuntu Development Team
[03:31] <Hobbsee> @schedule sydney
[03:31] <Ubugtu> Schedule for Australia/Sydney: 13 Sep 06:00: Technical Board | 14 Sep 06:00: Edubuntu | 14 Sep 17:00: Ubuntu Development Team | 19 Sep 22:00: Community Council | 20 Sep 22:00: Edubuntu | 22 Sep 01:00: Ubuntu Development Team
[03:31] <Hobbsee> hmmm.
[03:34] <zul> @schedule montreal
[03:34] <Ubugtu> Schedule for America/Montreal: 12 Sep 16:00: Technical Board | 13 Sep 16:00: Edubuntu | 14 Sep 03:00: Ubuntu Development Team | 19 Sep 08:00: Community Council | 20 Sep 08:00: Edubuntu | 21 Sep 11:00: Ubuntu Development Team
[03:34] <zul> sweeet..
[03:36] <Hobbsee> zul: i envy you.  except for that dev team meeting time.
[03:37] <zul> yeah those meetings are fun
[03:37] <Hobbsee> lol
[03:37] <zul> especailly im zombie the next day
[03:39] <Hobbsee> hehe.  i refuse to do meetings like that :P
[03:40] <Fujitsu> I managed to catch an 8am CC meeting, that wasn't too bad.
[03:46] <Hobbsee> true
[05:39] <dholbach> simira: ROCK ON!
[05:39] <dholbach> simira: how's it going?
[05:43] <simira> dholbach: not too bad. I just don't know enough to help many :p
[05:43] <simira> but Tollef is
[05:43] <simira> dholbach: did you get the link to my dog's website? We visited yesterday
[05:43] <dholbach> simira: send it again!
[05:43] <simira> http://odin.err.no
[05:44] <dholbach> haha :)
[05:44] <dholbach> HOW! CUTE! :)
[05:44] <simira> :)
[05:46] <simira> he'll get cuter in a couple of weeks 
[05:47] <dholbach> sure :-)
[05:52] <simira> you saw the link to the other pics as well?
[05:54] <mvo_> simira: very cute picture!
[05:54] <dholbach> how sweet
[05:54] <mvo_> simira: is update-manager working better for you recently btw?
[05:55] <simira> mvo_: I must admit I have been lazy (or was it busy) lately... not tested much. But it seems to work mostly, I am just a bit annoyed by it not wanting to install everything
[05:56] <mvo_> simira: it should be better about this now and give you (at least) the option to do this
[05:58] <simira> mvo_: I'll do a knot test after release on Thursday and give you some feedback then
[05:58] <simira> and I love both dogs and cats :)
[05:58] <mvo_> simira: thanks! make sure you update the system after installing knot, because some recent fixed did not made it into knot for the main-freeze
[05:59] <simira> mvo_: I update almost every day, normally.
[07:37] <imbrandon> @schedule us/chicago
[07:38] <imbrandon> @schedule us/central
[07:38] <Ubugtu> Schedule for US/Central: 12 Sep 15:00: Technical Board | 13 Sep 15:00: Edubuntu | 14 Sep 02:00: Ubuntu Development Team | 19 Sep 07:00: Community Council | 20 Sep 07:00: Edubuntu | 21 Sep 10:00: Ubuntu Development Team
[09:55] <mdz> good evening
[09:56] <zul> afternoon
[09:56] <ajmitch> morning
[09:57] <mdz> good UTEvening
[09:57] <mdz> imbrandon: are you here?
[09:58] <mjg59> mdz: I don't quite make it 20:00 UTC yet
[09:58] <mdz> mjg59: about 1 minute 20 away by my clock
[10:00] <mdz> reviewing the applicant lists, it seems we have imbrandon for -core-dev and thelinuxfr for -dev
[10:00] <mdz> but I don't think either is present
[10:00] <mjg59> Give them a few minutes?
[10:00] <mjg59> I don't think we've got any other business
[10:00] <mdz> is there anyone present who is here to apply for development team membership?
[10:01] <mdz> mjg59: I missed the previous meeting due to holidays; assuming one happened, anything I should know about?
[10:01] <mjg59> mdz: Nope
[10:03] <mdz> the agenda is empty, so I'm going to idle and continue with other work, but be nearby for the next hour or so in case something appears.  please nudge me if so
[10:04] <mdz> Keybuk and sabdfl are both otherwise engaged, for the record
[10:05] <imbrandon> mdz sorry
[10:05] <imbrandon> i am late
[10:05] <mdz> imbrandon: no worries
[10:06] <imbrandon> soo am i up now ?
[10:06] <mdz> imbrandon: Yes. Would you like to tell us about your application for -core-dev?
[10:06] <imbrandon> sure ...
[10:07] <mdz> mjg59: (ping in case you decided to idle as well)
[10:07] <mjg59> mdz: Here
[10:07] <imbrandon> oh wow , ok my klipper is not letting me paste so i will do this by hand
[10:08] <imbrandon> sorry , wiki with full explanation at http://wiki.kubuntu.org/imbrandon
[10:08] <imbrandon> and i have been working as a MOTU and member of the community for a while now and concentrate on
[10:09] <imbrandon> the "gadgets" of ubuntu like ipods and digital cameras making sure they work well OOTB as much as possible
[10:09] <mdz> imbrandon: according to Launchpad, you've been a member of ubuntu-dev for a bit over one month now.  is that correct?
[10:09] <imbrandon> yea, just over a month or so
[10:10] <imbrandon> i brought Riddell tonio and raphink ( and crimsun ) to cheer for me too
[10:10] <imbrandon> ( if they made it )
[10:10] <imbrandon> they all work with me daily
[10:10] <mdz> imbrandon: but you've been doing packaging work for longer than that?  I see you maintain at least one package in Debian as well
[10:10] <mdz> raphink is here at least
[10:10] <raphink> sorry to come only now
[10:11] <Nafallo> crimsun did just speak on #launchpad.
[10:11] <imbrandon> yes sir i package apt-mirror in debian
[10:11] <imbrandon> and manitain it
[10:11] <imbrandon> and try to work with debian as much as possible ( but we are ahead on most things versiuon wise in KDE )
[10:11] <imbrandon> but hopefully that wont be that way for long
[10:12] <mdz> are you a DD, or are your Debian uploads sponsored by someone (if so, who?)
[10:12] <mdz> and who generally sponsors your Ubuntu uploads?
[10:13] <mdz> (to main)
[10:13] <imbrandon> anibal is my DD sponsor ( plus i'm interviewing for a company atm too that a few DD's work at that also handle KDE )
[10:13] <imbrandon> Riddell, and tonino do 90%  of my uploads to main
[10:13] <imbrandon> i mostly work on amarok and kubuntu default settings
[10:14] <imbrandon> but i have been known to touch all of kde when needed
[10:14] <imbrandon> ( oir ubuntu for that matter )
[10:14] <mjg59> raphink: So how have you found working with imbrandon?
[10:15] <imbrandon> i work very closely with the konversation and amarok teams upstream also
[10:15] <raphink> mjg59: he's been doing great work
[10:15] <mjg59> raphink: What areas have you been working with him on?
[10:15] <raphink> I can tell :)
[10:15] <raphink> tonio is not here but he told me lately that he's very happy with imbrandon
[10:15] <raphink> esp. as we are not so numerous on Kubuntu lately
[10:16] <raphink> mjg59: packaging mostly I think
[10:16] <raphink> not recently, but I've looked at his packages in the past and they were very good
[10:16] <imbrandon> heh yea our numbers are small but we get the job done
[10:16] <mdz> imbrandon: I've noticed that quite a few of your uploads also incorporate changes from other people.  what tools are you using to coordinate this work?
[10:17] <imbrandon> i also tend to sponsor a few uploads too and am active on ubunutu-universe-sponsors
[10:17] <mdz> is there a revision control repository for, e.g. amarok?
[10:17] <imbrandon> mdz yes and no , we do most of our colab directly on IRC and there is a invite only amarok developers list i participte in
[10:18] <imbrandon> ( riddell and hobbsee are both members too )
[10:18] <imbrandon> iirc
[10:18] <mdz> imbrandon: so they email patches to you and you apply them to the package?
[10:18] <imbrandon> as for mergin mostly bzr and svn
[10:18] <imbrandon> in the case of amarok yes, with konversation its all svn
[10:19] <mdz> imbrandon: it's interesting that the amarok list is invite-only.  do you feel that works well for them?
[10:19] <imbrandon> well its mostly for spam reasons i think ( and so it dosent turn into a support list ) but anyone can get invited if they ask
[10:19] <imbrandon> sanely in the -dev chan
[10:20] <imbrandon> and the packagers tend to get the patches and version before the general public so we can have it ready for the distro on release day also
[10:20] <imbrandon> ( konversation and other kde projects also do this )
[10:21] <mdz> imbrandon: how does limiting subscription (as opposed to posting) prevent spam?
[10:21] <imbrandon> well its a google list so limiting sub/posting is tied togather afaik
[10:22] <imbrandon> and the archives are open to the public also
[10:22] <imbrandon> so its not totaly closed , just limited i would say
[10:22] <mdz> imbrandon: I've never seen spam from a subscriber of a list; usually it's restricting posts to subscribers only which helps prevent spam
[10:22] <mdz> which is orthogonal to restricting subscription
[10:23] <imbrandon> right , i was totaly speculating on the reasons , i would probably have to poke eean or marke to find out /exactly/ why
[10:23] <imbrandon> tbh
[10:23] <imbrandon> ( amarok list admins and devlopers _
[10:23] <imbrandon> )
[10:23] <mdz> just curious
[10:24] <mdz> what's your experience with the launchpad bug tracker?  do you feel that it works well?
[10:24] <imbrandon> heh /me wishes riddell would poke in soon
[10:24] <imbrandon> yea i think it works exceptionaly well compared to say bugs.kde.org
[10:24] <imbrandon> although the kde BTS is getting better
[10:25] <imbrandon> and the debian BTS is hard to use for non-debian users and new members
[10:25] <imbrandon> imho but still useable
[10:25] <imbrandon> but LP far outwieghs that plus
[10:25] <mdz> what do you do with bugs which are reported to Ubuntu, but are not specific to Ubuntu and affect KDE upstream as well?
[10:25] <imbrandon> the ability to use bzr and other tools directly from it is nice
[10:26] <imbrandon> when i can, most of the time i stay within the kubuntu relm but track them upstream also when needed / warented
[10:26] <imbrandon> and try to bring it to the attn of the right developers on irc upstream if i know them
[10:27] <mdz> are you using bzr for Ubuntu development today?  I'm interested to know if it's working well for you
[10:27] <imbrandon> one thing i have noticed about LP though that makes it hard but is beeing worked on iirc is the ability to mark as fixed in a release but wontfix etc in another release ( eg dapper or edgy )
[10:28] <imbrandon> yes i use bzr to track apt-mirror ( as there is no upstream rcs so me and the only orther developer oped to just use LP bzr )
[10:28] <imbrandon> and also for konversation ( thats synced with svn )
[10:28] <mdz> imbrandon: can you show me that branch in LP? it doesn't seem to be registered to your LP account yet
[10:29] <imbrandon> that me and mez both activly keep tabs on
[10:29] <imbrandon> sure there should be an apt-mirror product with that as the only branch
[10:29] <imbrandon> same for konversation
[10:30] <mdz> there it is
[10:30] <imbrandon> also Riddell keeps the kubuntu-website in bzr so we can all branch from it and make sugestions as needed with code patches 
[10:30] <mdz> https://launchpad.net/products/apt-mirror/+branches
[10:30] <imbrandon> ( i just learned that today so i will be using that more )
[10:31] <imbrandon> yes sorry i'm at a console that dosent ahve a www browser atm ( have to do this all from memory )
[10:31] <mdz> so it's stored on the supermirror under ubuntu-dev, meaning that any member of ubuntu-dev can commit to it.  do others commit directly to it?  has that worked well for apt-mirror?
[10:31] <imbrandon> its worked very well for apt-mirror and its still fairly new so no other developers have shown intrest in it 
[10:31] <imbrandon> but
[10:31] <imbrandon> they are welcomed to ;)
[10:32] <imbrandon> but it keeps me and the other developer thats not in the ubuntu community in sync
[10:32] <mdz> imbrandon: I see you're a member of the backporters team and the bugsquad team. are you active on either of those?
[10:32] <imbrandon> very active in backports ( infact ask kamoin i bug him regularly ) and active in ubuntu-sponsors
[10:33] <imbrandon> as far as bugsquad i do alot of lp bug work and squishing and bugdays but dont much
[10:33] <imbrandon> partisipate int he irc much of -bugsquad
[10:33] <imbrandon> just becouse of time constraints mostly
[10:34] <imbrandon> ubuntu-universe-sponsors
[10:34] <imbrandon> *
[10:34] <imbrandon> tbh i think at time me and crimsun are the only ones working on ubuntu-*-sponsors heheh but he is lightning fast ;)
[10:35] <imbrandon> s/time/times
[10:36] <imbrandon> crimsun, just spoke up in -motu , i cant paste from there if someone would please do the honors ;)
[10:36] <imbrandon> ( sorry i'm on a dead irssi link atm )
[10:36] <mdz> I wasn't in #ubuntu-motu at the moment; crimsun is in this channel though if he has something to say
[10:36] <Lure> [22:34]  <crimsun> sorry, just got called away to a meeting. If imbrandon needs my backing for TB, I've worked with him on various packages (konversation and apt-mirror come to mind immediately), and he has my +1.
[10:37] <imbrandon> thanks lure
[10:37] <mdz> imbrandon: what would you say are your reasons for wanting to join -core-dev? what difference would it make in the work that you currently do?
[10:38] <imbrandon> well i think i have alot to contribute and i do that now with alot of work in main ( amarok and konversation )
[10:38] <imbrandon> it would help our workflow but thats not the "main" reason
[10:39] <imbrandon> just that i know i can handle it , love to do it, and ....
[10:39] <mdz> what is the main reason?
[10:39] <imbrandon> kubuntu needs the love ;)
[10:39] <imbrandon> serouisly , its something i like to do and alot of my work so far has been main type work
[10:39] <mdz> it's unusual to join the core team after such a short time as a member of the development team as a whole
[10:40] <imbrandon> well some of that was i joined -motu late , and then wanted to show that i could do main work well
[10:41] <imbrandon> as even before i was motu i was active in alot of this
[10:41] <mdz> -core-dev isn't simply about the main component, but about being a consistent, long term contributor, closely involved with the project, and taking responsibility for the quality of the distribution
[10:41] <imbrandon> mdz definately , and i ( myself and others i work with daily ) think i show and do that imho
[10:42] <imbrandon> i definately keep the quality high and work on kubuntu and floss in generall daily ( even as a JOB heh )
[10:42] <mdz> imbrandon: we're now in feature freeze and will release a beta of Edgy quite soon.  what will you do differently over the next few weeks leading up to the release?
[10:42] <imbrandon> and feel i can adhear to high standards i and everyone expects fof ubuntu
[10:43] <imbrandon> mostly makeing sure the polish and all the "little" touches are put into k-d-s ( outlined more clearly on my wiki as to exacty changes )
[10:43] <bddebian> Except for spelling apparently ;-P
[10:43] <mdz> (the beta, that is)
[10:43] <imbrandon> bddebian, yea i'm not at my normal computer heh
[10:44] <bddebian> I'm joking, sorry :)
[10:44] <imbrandon> mdz, that and we keep a list of "critical:" pre release bugs
[10:44] <imbrandon> that i work to keep down top
[10:44] <imbrandon> too*
[10:44] <mdz> imbrandon: what about the mechanics of what you do, such as uploading packages? how will that change?
[10:45] <imbrandon> well i wouldent have to go though the sponsor routine daily if thats what you are asking 
[10:45] <imbrandon> right now my workflow go's
[10:45] <imbrandon> like this .... hehe
[10:45] <mdz> imbrandon: I mean in relation to the release
[10:45] <imbrandon> ok well in relation to release 
[10:46] <imbrandon> the workflow is concentrated on showstopers and major bugs in the desktop
[10:46] <imbrandon> instead of "new crack" in kde
[10:46] <imbrandon> for lack of a better word, making sure we have all major bugs from upstream closed and any in our kds packages that need addressing
[10:47] <imbrandon> to put that final touch on the release
[10:47] <imbrandon> kds == kubuntu-default-settings
[10:47] <mdz> what I'm trying to get at is what you will consider when you make a decision about changing something in the distribution, and how that will change as we approach release
[10:48] <mdz> does that make sense?
[10:48] <imbrandon> ohhh 99% of our clab is done via kubuntu meeting and in kubnutu-devel with riddell tonio crimsun 
[10:48] <mdz> it's critically important for a core developer to be aware of the release preparation process and bear it in mind when making uploads
[10:48] <imbrandon> and quite a few other active members 
[10:49] <imbrandon> mdz, exactly i pay close attn to that
[10:49] <imbrandon> infact just this moring when the ubntu-dev topic changed i made the
[10:49] <mdz> for example, an announcement went out today regarding the upcoming knot release.  what would you do differently now, compared to before that announcement went out?
[10:49] <imbrandon> change in k-devel to make sure everyone saw it also
[10:50] <mdz> in terms of your uploads
[10:51] <imbrandon> well i try to stay very current with the happening in both -devel channels and the ML and as far as uploads naturaly in the freeze it gets cleared by riddell or other relevant person ( you ?)
[10:51] <imbrandon> and
[10:51] <imbrandon> non freeze for knot e.g now leading to release "the beta" only bug fixes and everything is triple checked and 
[10:51] <imbrandon> revied by someone else if its code i'm not familiar with
[10:52] <imbrandon> reviewed*
[10:52] <imbrandon> but i tend to stick with things i know when it comes to crunch time
[10:53] <mdz> imbrandon: so to use an example, one week ago you uploaded amarok 2:1.4.3-0ubuntu1.  would you make that same upload today?  why or why not?
[10:54] <imbrandon> that one i would becouse it was critical bugfixes to 1.4.2 ( showstopers ) thus the fast release from 1.4.2
[10:54] <imbrandon> and ONLY bugfixes
[10:54] <imbrandon> if it hadent been then
[10:54] <imbrandon> i would have stiped out the relvant patches and only applied those to 1.4.2 and if it was today 
[10:54] <imbrandon> i would do the same 
[10:55] <imbrandon> ( the patches )
[10:55] <mdz> in tollef's announcement, as with other milestone freezes, he said that all uploads to main required approval from the release team
[10:55] <mdz> so it would not be appropriate to make that same upload now
[10:55] <imbrandon> yes and that was given by kamoin iirc
[10:55] <imbrandon> ( and i think noted in the changelog )
[10:56] <imbrandon> if not its definately on LP ( i do all uvfe in LP for that reason )
[10:56] <mdz> it wasn't in the changelog, but that would have been an exception to the upstream version freeze
[10:56] <imbrandon> yes that was my mistake not to include it in the changelog but it is documented on LP
[10:57] <imbrandon> as a bug against amarok with the title uvf in it
[10:58] <mdz> my point is that even if it had been granted a UVF exception yesterday, if you were preparing an upload today, it shouldn't be uploaded yet due to the milestone freeze. make sense?
[10:58] <imbrandon> say 1.4.4 comes out tomarrow ( and knot freeze is over ) that will be stripped to patchess against 1.4.3 for bug fixes only
[10:58] <Nafallo> except approval from Tollef that is... :-)
[10:59] <imbrandon> ahh right ,yea no uploads for the knot , i unerstand that i guess i missed your question
[10:59] <imbrandon> or that part of
[11:00] <imbrandon> so if i was to do it litterly TODAY yes i would prepar it and hold off till 48hours or so when the kknot milstone is released
[11:00] <imbrandon> ( and have done so in the past , iirc 1.4.2 came out in the knot 2 freeze )
[11:00] <mdz> right, I was literally asking whether you would do the same thing *today*, not whether your upload last week was OK :-)
[11:01] <imbrandon> ahh ok , sorry i missed that part
[11:01] <mdz> I have no further questions. mjg59?
[11:01] <imbrandon> yes i understand the milstone freezes though , as i said i was the one that added it to the k-devel topic so everyone would note it this morning
[11:01] <imbrandon> ;)
[11:01] <imbrandon> sorry for not being clear
[11:02] <mdz> thanks for your patience in this discussion, I know it's been long
[11:02] <mjg59> imbrandon: Are you happy with being able to upload stuff that could break everyone's systems?
[11:02] <imbrandon> no problem at all, thanks for letting me be a bit late ;)
[11:02] <imbrandon> mjg59, yup as i'm confident that i can NOT break everyones system heh
[11:03] <mdz> but I'm sure you understand that this is a great responsibility and it's important that we establish whether you understand that
[11:03] <imbrandon> we're all human but i do tend to check very well and do ask for opinions when its code i'm not familiar with
[11:03] <imbrandon> definately
[11:04] <mdz> mjg59: I'm ready for a vote when you are
[11:04] <Lure> I can say that imbrandon typically publish his work on his server for review, particularly for larger changes (kdebase...) so I can say he is very conservative in this part
[11:04] <mjg59> mdz: Sure, go head
[11:05] <mjg59> Sorry, my connection is becoming alarmingly laggy
[11:06] <mdz> +1 from me.  please remember to take this responsibliity very seriously, and be conservative with regard to the release process.  when in doubt, ask.  even if you don't doubt, asking for confirmation never hurts!
[11:06] <mjg59> I'm inclined to go with +1, for working closely with upstream and seeming to have a good sense of the responsibilities
[11:06] <imbrandon> ;)
[11:06] <imbrandon> mdz, definately
[11:06] <mdz> imbrandon: congratulations and welcome
[11:06] <imbrandon> thansk guys ;)
[11:06] <Lure> imbrandon: congrats and great to have you in core-dev
[11:06] <imbrandon> ( now to get on my normal box ) heh
[11:06] <ogra> congrats imbrandon !
[11:06] <imbrandon> yay \0/
[11:06] <pitti> imbrandon: welcome!
[11:07] <mdz> is there any other business for the TB tonight?
[11:07] <imbrandon> heya pitti thanks
[11:07] <Nafallo> imbrandon: congratulations :-)
[11:07] <rodarvus> imbrandon, congratulations!
[11:07] <LaserJock> congrats imbrandon 
[11:07] <imbrandon> ok sorry to run, i have to go get on my "real" system , this console is killing me
[11:07] <LaserJock> imbrandon: party at my place? ;-)
[11:07] <imbrandon> bb in 5 min
[11:07] <imbrandon> LaserJock, ypu yup
[11:07] <mdz> imbrandon: double congrats then
[11:07] <pitti> imbrandon: wow, congrats again
[11:08] <ogra> imbrandon, nice :)
[11:08] <imbrandon> hehe the postr SHOULD still be on planet , but thanks ;)
[11:08] <mdz> last call for TB business
[11:08] <Nafallo> imbrandon: congrats, I'm sure you will be up many nights now :-P
[11:08] <imbrandon> ok <detached> back in a sec
[11:08] <rodarvus> imbrandon: heh, nice. congratulations on that too :)
[11:08] <pitti> mdz: has there been any word on the usplash status?
[11:08] <mdz> pitti: more specifically?
[11:08] <pitti> mdz: i. e. will we go with the SVGA patch or revert to VGA?
[11:09] <mjg59> kamion has it working with framebuffer
[11:09] <mdz> as far as I'm aware, the only outstanding issue is powerpc
[11:09] <mdz> and I saw an upload from colin which I thought might address that
[11:09] <pitti> well, and amd64+nvidia
[11:09] <mjg59> There's a reversion on amd64 systems with nvidia hardware
[11:09] <ogra> right, he said it was fixed for him
[11:09] <mjg59> I'm confident that's repairable, and if not we can fall back for that specific case
[11:09] <mdz> I'm confident we should push ahead with it then
[11:09] <pitti> ok, thanks for the heads-up!
[11:10] <pitti> glad to see that it doesn't need to be reverted completely
[11:10] <pitti> (and eager to see it actually working :-P)
[11:10] <mdz> if there's a bug report open about the nvidia issue, I'd appreciate a subscription.  if not, there should be one
[11:10] <mdz> TB adjourned, thanks everyone
[11:10] <slomo> pitti, mdz: it works fine for me on ppc too with the latest upload