[00:08] <mpt> ^_^
[00:08] <mpt> Hey lifeless
[00:08] <mpt> Accept no imitations!
[00:08] <lifeless> o/
[00:17] <lifeless> mpt: speak up :)
[00:20] <mpt> At least once we get the graph showing something sensible, it should be moving around just as much five years from now as it is the first week
[00:20] <mpt> (That's not a goal, but it would be an emergent property of doing the right thing)
[00:23] <mpt> There's a tradeoff between alerting developers promptly to a sudden problem (which should show up as a dip in the graph), vs. being accurate (which requires taking a longer-duration sample)
[00:23] <mpt> compare http://arewefastyet.com/ (which used to be much more interesting than it is now)
[00:24] <mpt> Agreed on only a few days old by default
[00:25] <mpt> I can hear lifeless fine
[00:25] <mpt> but at the expense of hearing it 10 seconds late
[00:25] <mpt> (where by "it" I mean "everything", sorry lifeless)
[00:28] <mpt> (or more likely, increases)
[00:29] <mpt> They're correlated to the extent that more computers make it a bit more likely that their problems will be unique
[00:29] <mpt> We could fiddle that somehow by only counting machines that have reported at least 2 problems, or somethng like that
[00:32] <lifeless> mpt: they are, OTOH more machines also means more reporting of common problems :)
[00:32] <mpt> sure
[00:32] <lifeless> mpt: so both more density and a longer tail, if you do a histogram
[00:32] <mpt> exactly
[00:54] <mpt> Oh, lifeless has eyes now
[00:54] <lifeless> o-o
[00:55] <udsbotu> uds-jb-1: 5 minutes left in this session!
[00:56] <udsbotu> uds-jb-1: 4 minutes left in this session!
[00:57] <udsbotu> uds-jb-1: 3 minutes left in this session!
[00:58] <udsbotu> uds-jb-1: 2 minutes left in this session!
[00:59] <udsbotu> uds-jb-1: 1 minute left in this session!
[01:00] <udsbotu> uds-jb-1: This session has ended.
[01:00] <lifeless> wow, skype uses a full core
[01:00] <lifeless> nonstop, fingers burning on keyboard
[16:11]  * cmagina is currently running a multi node hadoop on arm
[16:11] <cmagina> via openjdk
[16:41] <dannf> it isn't uncommon for a lot of network traffic to "take out" a bmc - even on modern intel-based systems
[16:45] <dannf> broadcast ping will suffer from ^
[16:49] <dannf> right - i'm just saying that "network storms" can make some bmcs unresponsive
[16:49] <dannf> but yeah, unicast response helps that
[16:50] <udsbotu> uds-jb-1: 5 minutes left in this session!
[16:50] <dannf> heh
[16:51] <udsbotu> uds-jb-1: 4 minutes left in this session!
[16:52] <udsbotu> uds-jb-1: 3 minutes left in this session!
[16:53] <udsbotu> uds-jb-1: 2 minutes left in this session!
[16:54] <udsbotu> uds-jb-1: 1 minute left in this session!
[16:55] <udsbotu> uds-jb-1: This session has ended.
[17:40] <udsbotu> uds-jb-1: 5 minutes left in this session!
[17:41] <udsbotu> uds-jb-1: 4 minutes left in this session!
[17:42] <udsbotu> uds-jb-1: 3 minutes left in this session!
[17:43] <udsbotu> uds-jb-1: 2 minutes left in this session!
[17:44] <udsbotu> uds-jb-1: 1 minute left in this session!
[17:45] <udsbotu> uds-jb-1: This session has ended.
[17:59] <xnox> mpt: are you attending this session? would you like g+ and or skype?
[18:00] <mpt> xnox, Skype would be good, thanks
[18:03] <mpt> You don't have to stay here, I'm also listening to the streaming audio
[18:05] <Chipaca> mpt: i can give you video via skype or g+ if you wish
[18:09] <mpt> If submitting from a PPA is a common action, maybe we should add a link to that from the PPA page (showing up if you're the PPA admin)
[18:12] <ajmitch> https://wiki.ubuntu.com/AppReviewBoard/Submissions/Request
[18:17] <mpt> The #1 problem with changelogs is that they currently aren't written for users
[18:18] <mpt> The problem with putting any changes in the description is that it doesn't know which version you currently have installed
[18:19] <mpt> I can, but the audio lags behind reality by about 10 seconds so I'd almost certainly interrupt someone
[18:19] <mpt> :-)
[18:25] <mpt> Adding a link wrapped in a permission would be, like, 20 lines of diff
[18:25] <mpt> It's not rocket surgery
[18:25] <ajmitch> just setting up LP & writing tests can take some time :)
[18:32]  * mpt waves to akk
[18:33] <akk> hi, mpt
[18:49] <udsbotu> uds-jb-1: 5 minutes left in this session!
[18:49] <ChipaPhone> mpt, battery running out
[18:50] <mpt> no worries
[18:50] <ChipaPhone> so is the session:)
[18:50] <udsbotu> uds-jb-1: 4 minutes left in this session!
[18:51] <udsbotu> uds-jb-1: 3 minutes left in this session!
[18:52] <udsbotu> uds-jb-1: 2 minutes left in this session!
[18:53] <udsbotu> uds-jb-1: 1 minute left in this session!
[18:54] <udsbotu> uds-jb-1: This session has ended.
[19:00] <Chipaca> ahhh.... moar batteries
[19:04] <mpt> https://wiki.ubuntu.com/NotificationDesignGuidelines
[19:14] <mpt> How about *nearly* full home/usr partition?
[19:14] <mpt> because it's likely to become full in the near future
[19:16] <mpt> Possibly-crappy network info might belong in the Network settings panel
[19:17] <mpt> (I haven't seen the screenshot you're referring to)
[19:18] <mpt> Maybe a nearly-full warning should be megabyte-based, not percentage-based
[19:18] <mpt> ah, joy, notify-osd fallback
[19:23] <mpt> That sounds like reasonable
[19:24] <mpt> For each kind of warning, the design needs to include what advice to offer
[19:24] <mpt> on how to fix the problem
[19:25] <mpt> ---
[19:25] <mpt> You don't care that a USB key is nearly full either, probably -- more about /home and /usr
[19:25] <mpt> ---
[19:26] <mpt> ... For each warning type, we also need to think about when to present it -- for example, if a problem happens that will prevent you from logging in, we should present that not just immediately, but also when you try to log out, shut down, etc
[19:34] <mpt> ---
[19:35] <mpt> I suggest that each event have one work item for the design and one work item for the implementation
[19:35] <mpt> It's unlikely that they will all be designed, or all implemented, at once
[19:36] <mpt> ok :-)
[19:49] <mpt> ---
[19:49] <mpt> That software update redness is going away in 12.10
[19:49] <mpt> (because software updates itselfis going away from the system menu)
[19:50] <mpt> Update Manager already tells you if you need to restart. If you don't immediately, you're not any less secure than you were before you installed the update.
[19:51] <mpt> No, it's an alert box
[19:52] <mpt> https://wiki.ubuntu.com/SoftwareUpdates#alert
[19:52] <mpt> (but that may need work to highlight when updates are security updates)
[19:55] <udsbotu> uds-jb-1: 5 minutes left in this session!
[19:56] <udsbotu> uds-jb-1: 4 minutes left in this session!
[19:57] <mpt> Yes, I'd love to help with the design
[19:57] <udsbotu> uds-jb-1: 3 minutes left in this session!
[19:58] <udsbotu> uds-jb-1: 2 minutes left in this session!
[19:58] <mpt> Lunchtime for me too
[19:59] <udsbotu> uds-jb-1: 1 minute left in this session!
[20:00] <udsbotu> uds-jb-1: This session has ended.
[22:05] <benonsoftware> Yay :D
[22:08] <daker_> 5/5
[22:08] <sagaci> HEY ALL YOU PEOPLE
[22:08] <benonsoftware> Hiya sagaci
[22:09]  * benonsoftware is sitting in a chair waiting
[22:09] <benonsoftware> I have no sound :(
[22:09] <sagaci> watch the etherpad
[22:10] <daker_> benonsoftware: the stream is working
[22:10] <benonsoftware> daker_: I have no sound card :(
[22:10] <benonsoftware> I will :P
[22:10] <daker_> ah
[22:10] <benonsoftware> I will download the audio once it's finished though
[22:11] <benonsoftware> Hiya philipballew
[22:12] <philipballew> hello benonsoftware
[22:12] <benonsoftware> Let's get started :D
[22:12] <benonsoftware> BDFL?
[22:13] <JoseeAntonioR> Benevolent Dictator For Life
[22:13] <benonsoftware> Ah
[22:14] <daker_> +1 for social media
[22:15] <daker_> weekly/monthly hangout on G+ ?
[22:18] <philipballew> daker_, you down to help with me on a once a month google hangout?
[22:18] <daker_> will try
[22:18] <benonsoftware> I'll help out if I can get WiFi
[22:19] <benonsoftware> Credit to philipballew for Classroom sessions
[22:20] <benonsoftware> I'm all for helping setup the sessions, just need people to run them
[22:20] <philipballew> daker_, ill add me and you to the wiki
[22:20] <benonsoftware> May I say something about the elections?
[22:21] <philipballew> go for it
[22:21] <benonsoftware> I suggest we have a election for all couincil members soon as it has been a long time since one has happened and some are not active with Ubuntu and IRC anymore
[22:22] <benonsoftware> Daniel Bugl is one person who  has stopped using IRC for a while
[22:24] <benonsoftware> I would say 3 months is too short
[22:24] <benonsoftware> I would say 12 months
[22:25] <benonsoftware> philipballew: have you gotten a response from the other council members yet?
[22:26] <philipballew> no
[22:27] <benonsoftware> Hmm, that is troubleing
[22:27] <philipballew> hints the reelection I guess
[22:27] <benonsoftware> philipballew: Yes, that is why electiuon would be good
[22:28] <benonsoftware> But who should run?, how do we say you can/cannot run for election?
[22:28] <benonsoftware> By, Should every current council member allowed to campaign if that means can they run again I would say yes
[22:29] <bilal> benonsoftware: yes, every current member would be a candidate for the next election by default
[22:29] <bilal> they could opt out though
[22:29] <benonsoftware> Yes
[22:30] <benonsoftware> philipballew: As you are TL when do you rthink will be a good time to run elections?
[22:32] <benonsoftware> What was that?
[22:37] <benonsoftware> Ah, never mind
[22:40] <benonsoftware> Sorry about that
[22:48]  * benonsoftware has to leave shortly
[22:48] <bilal> benonsoftware: we've wrapped up
[22:48] <bilal> benonsoftware: so... :)
[22:49] <benonsoftware> Ah, okies
[22:49] <benonsoftware> Could someone ping me once the audi ofile is uploaded
[22:55] <udsbotu> uds-jb-1: 5 minutes left in this session!
[22:56] <udsbotu> uds-jb-1: 4 minutes left in this session!
[22:57] <udsbotu> uds-jb-1: 3 minutes left in this session!
[22:58] <udsbotu> uds-jb-1: 2 minutes left in this session!
[22:59] <udsbotu> uds-jb-1: 1 minute left in this session!
[23:00] <udsbotu> uds-jb-1: This session has ended.
[23:14] <mpt> hi
[23:52] <mpt> The hardware IDs are already not personally identifiable. The privacy issue has never been the presence of the hardware ID, it's been that the crash report might contain *other* personally identifable information. Right?
[23:54] <udsbotu> uds-jb-1: 5 minutes left in this session!
[23:55] <udsbotu> uds-jb-1: 4 minutes left in this session!
[23:56] <udsbotu> uds-jb-1: 3 minutes left in this session!
[23:57] <udsbotu> uds-jb-1: 2 minutes left in this session!
[23:58] <udsbotu> uds-jb-1: 1 minute left in this session!
[23:59] <udsbotu> uds-jb-1: This session has ended.