=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Foundations | Continued development of the Ubuntu error tracker | Url: http://summit.ubuntu.com/uds-q/meeting/20488/foundations-q-crash-database/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [00:08] ^_^ [00:08] Hey lifeless [00:08] Accept no imitations! [00:08] o/ [00:17] mpt: speak up :) [00:20] 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] (That's not a goal, but it would be an emergent property of doing the right thing) [00:23] 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] compare http://arewefastyet.com/ (which used to be much more interesting than it is now) [00:24] Agreed on only a few days old by default [00:25] I can hear lifeless fine [00:25] but at the expense of hearing it 10 seconds late [00:25] (where by "it" I mean "everything", sorry lifeless) [00:28] (or more likely, increases) [00:29] They're correlated to the extent that more computers make it a bit more likely that their problems will be unique [00:29] We could fiddle that somehow by only counting machines that have reported at least 2 problems, or somethng like that [00:32] mpt: they are, OTOH more machines also means more reporting of common problems :) [00:32] sure [00:32] mpt: so both more density and a longer tail, if you do a histogram [00:32] exactly [00:54] Oh, lifeless has eyes now [00:54] o-o [00:55] uds-jb-1: 5 minutes left in this session! [00:56] uds-jb-1: 4 minutes left in this session! [00:57] uds-jb-1: 3 minutes left in this session! [00:58] uds-jb-1: 2 minutes left in this session! [00:59] uds-jb-1: 1 minute left in this session! [01:00] uds-jb-1: This session has ended. [01:00] wow, skype uses a full core [01:00] nonstop, fingers burning on keyboard === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-1.log === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Cloud & Server | ARM Server Deployment | Url: http://summit.ubuntu.com/uds-q/meeting/20448/servercloud-q-arm-deployment/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [16:11] * cmagina is currently running a multi node hadoop on arm [16:11] via openjdk [16:41] it isn't uncommon for a lot of network traffic to "take out" a bmc - even on modern intel-based systems [16:45] broadcast ping will suffer from ^ [16:49] right - i'm just saying that "network storms" can make some bmcs unresponsive [16:49] but yeah, unicast response helps that [16:50] uds-jb-1: 5 minutes left in this session! [16:50] heh [16:51] uds-jb-1: 4 minutes left in this session! [16:52] uds-jb-1: 3 minutes left in this session! [16:53] uds-jb-1: 2 minutes left in this session! [16:54] uds-jb-1: 1 minute left in this session! [16:55] uds-jb-1: This session has ended. === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Foundations | Plan for future x32 ABI support | Url: http://summit.ubuntu.com/uds-q/meeting/20335/foundations-q-x32-planning/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [17:40] uds-jb-1: 5 minutes left in this session! [17:41] uds-jb-1: 4 minutes left in this session! [17:42] uds-jb-1: 3 minutes left in this session! [17:43] uds-jb-1: 2 minutes left in this session! [17:44] uds-jb-1: 1 minute left in this session! [17:45] uds-jb-1: This session has ended. === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-1.log === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Community | MyApps submission experience and expectations for upstreams | Url: http://summit.ubuntu.com/uds-q/meeting/20412/community-q-upstream-myapps/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [17:59] mpt: are you attending this session? would you like g+ and or skype? [18:00] xnox, Skype would be good, thanks [18:03] You don't have to stay here, I'm also listening to the streaming audio [18:05] mpt: i can give you video via skype or g+ if you wish [18:09] 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] https://wiki.ubuntu.com/AppReviewBoard/Submissions/Request [18:17] The #1 problem with changelogs is that they currently aren't written for users [18:18] The problem with putting any changes in the description is that it doesn't know which version you currently have installed [18:19] I can, but the audio lags behind reality by about 10 seconds so I'd almost certainly interrupt someone [18:19] :-) [18:25] Adding a link wrapped in a permission would be, like, 20 lines of diff [18:25] It's not rocket surgery [18:25] just setting up LP & writing tests can take some time :) [18:32] * mpt waves to akk [18:33] hi, mpt [18:49] uds-jb-1: 5 minutes left in this session! [18:49] mpt, battery running out [18:50] no worries [18:50] so is the session:) [18:50] uds-jb-1: 4 minutes left in this session! [18:51] uds-jb-1: 3 minutes left in this session! [18:52] uds-jb-1: 2 minutes left in this session! [18:53] uds-jb-1: 1 minute left in this session! [18:54] uds-jb-1: This session has ended. === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Foundations | Degraded Hardware Notifications aka 'things you rather not see' | Url: http://summit.ubuntu.com/uds-q/meeting/20497/foundations-q-degraded-hw-notification/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [19:00] ahhh.... moar batteries [19:04] https://wiki.ubuntu.com/NotificationDesignGuidelines [19:14] How about *nearly* full home/usr partition? [19:14] because it's likely to become full in the near future [19:16] Possibly-crappy network info might belong in the Network settings panel [19:17] (I haven't seen the screenshot you're referring to) [19:18] Maybe a nearly-full warning should be megabyte-based, not percentage-based [19:18] ah, joy, notify-osd fallback [19:23] That sounds like reasonable [19:24] For each kind of warning, the design needs to include what advice to offer [19:24] on how to fix the problem [19:25] --- [19:25] You don't care that a USB key is nearly full either, probably -- more about /home and /usr [19:25] --- [19:26] ... 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] --- [19:35] I suggest that each event have one work item for the design and one work item for the implementation [19:35] It's unlikely that they will all be designed, or all implemented, at once [19:36] ok :-) [19:49] --- [19:49] That software update redness is going away in 12.10 [19:49] (because software updates itselfis going away from the system menu) [19:50] 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] No, it's an alert box [19:52] https://wiki.ubuntu.com/SoftwareUpdates#alert [19:52] (but that may need work to highlight when updates are security updates) [19:55] uds-jb-1: 5 minutes left in this session! [19:56] uds-jb-1: 4 minutes left in this session! [19:57] Yes, I'd love to help with the design [19:57] uds-jb-1: 3 minutes left in this session! [19:58] uds-jb-1: 2 minutes left in this session! [19:58] Lunchtime for me too [19:59] uds-jb-1: 1 minute left in this session! [20:00] uds-jb-1: This session has ended. === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-1.log === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Community | Ubuntu Youth Team | Url: http://summit.ubuntu.com/uds-q/meeting/20717/community-q-ubuntu-youth/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [22:05] Yay :D [22:08] 5/5 [22:08] HEY ALL YOU PEOPLE [22:08] Hiya sagaci [22:09] * benonsoftware is sitting in a chair waiting [22:09] I have no sound :( [22:09] watch the etherpad [22:10] benonsoftware: the stream is working [22:10] daker_: I have no sound card :( [22:10] I will :P [22:10] ah [22:10] I will download the audio once it's finished though [22:11] Hiya philipballew [22:12] hello benonsoftware [22:12] Let's get started :D [22:12] BDFL? [22:13] Benevolent Dictator For Life [22:13] Ah [22:14] +1 for social media [22:15] weekly/monthly hangout on G+ ? [22:18] daker_, you down to help with me on a once a month google hangout? [22:18] will try [22:18] I'll help out if I can get WiFi [22:19] Credit to philipballew for Classroom sessions [22:20] I'm all for helping setup the sessions, just need people to run them [22:20] daker_, ill add me and you to the wiki [22:20] May I say something about the elections? [22:21] go for it [22:21] 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] Daniel Bugl is one person who has stopped using IRC for a while [22:24] I would say 3 months is too short [22:24] I would say 12 months [22:25] philipballew: have you gotten a response from the other council members yet? [22:26] no [22:27] Hmm, that is troubleing [22:27] hints the reelection I guess [22:27] philipballew: Yes, that is why electiuon would be good [22:28] But who should run?, how do we say you can/cannot run for election? [22:28] By, Should every current council member allowed to campaign if that means can they run again I would say yes [22:29] benonsoftware: yes, every current member would be a candidate for the next election by default [22:29] they could opt out though [22:29] Yes [22:30] philipballew: As you are TL when do you rthink will be a good time to run elections? [22:32] What was that? [22:37] Ah, never mind [22:40] Sorry about that [22:48] * benonsoftware has to leave shortly [22:48] benonsoftware: we've wrapped up [22:48] benonsoftware: so... :) [22:49] Ah, okies [22:49] Could someone ping me once the audi ofile is uploaded [22:55] uds-jb-1: 5 minutes left in this session! [22:56] uds-jb-1: 4 minutes left in this session! [22:57] uds-jb-1: 3 minutes left in this session! [22:58] uds-jb-1: 2 minutes left in this session! [22:59] uds-jb-1: 1 minute left in this session! [23:00] uds-jb-1: This session has ended. === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-1.log === ChanServ changed the topic of #ubuntu-uds-junior-ballroom-1 to: Track: Foundations | If a crash is already fixed by an update, prompt to install it | Url: http://summit.ubuntu.com/uds-q/meeting/20329/foundations-q-updates-from-crash-reports/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-1.ogg.m3u [23:14] hi [23:52] 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] uds-jb-1: 5 minutes left in this session! [23:55] uds-jb-1: 4 minutes left in this session! [23:56] uds-jb-1: 3 minutes left in this session! [23:57] uds-jb-1: 2 minutes left in this session! [23:58] uds-jb-1: 1 minute left in this session! [23:59] uds-jb-1: This session has ended.