[07:12] good morning [15:04] http://iloveubuntu.net/mass-effects-sam-hulick-created-sams-song-song-implemented-default-ubuntu-touch-sounds [15:04] well done! [15:07] jcastro: have a min? [15:07] jose, go [15:08] jcastro: at the end, are we having the shapado instance deployed? [15:08] at the end of what? [15:08] the conversation we had over emails [15:08] oh [15:08] let me check [15:09] ah [15:09] did you try the rack charm? [15:09] it got renamed to "rails" btw [15:09] you didn't tell me to try anything [15:10] or you did? [15:10] "Can we try with the rack charm? It would be a more cost-efficient solution." is my last mail from you [15:10] we can expense it on hpcloud or AWS if you wanna prototype [15:11] ah, by 'we' I thought you [15:11] I'll try and see what can I do, will reply to the email once I have any results [15:12] thanks jcastro! [15:12] hey [15:13] did you by any chance move the juju charm call stuff from the fridge calendar? [15:13] I did, it's on the ubuntuonair calendar [15:14] it needs to be on the fridge calendar [15:14] it broke all the invites [15:15] as I talked to the news team, the fridge calendar is used for #ubuntu-meeting [15:15] everything that's ubuntuonair is at the ubuntuonair calendar [15:15] ugh [15:15] I can try and fix the invites [15:15] no, don't touch anything please! [15:16] then, what should I do? [15:16] just leave it in there? [15:16] yes! [15:16] one calendar! [15:17] we don't need 453934084534 community calendars, I can barely get people to show up on time as it is! [15:17] I suggest we need a keep calm factoid for ubottu-.- [15:18] well, at the end it all shows up in the same page but with different colors :P [15:18] anyways, it'll remain on the fridge calendar [15:18] Only you can prevent calendar proliferation [15:19] :P [15:19] it also got moved to the wrong day, which is why everyone is confused [15:19] ah, don't blame me for that, I just changed the calendar, not the time/dat [15:32] dholbach, hey for tommorrow's hangout, is there a URL I can send people to now? [15:32] jcastro, ubuntuonair.com [15:32] sort of like "join us tomorrow, for more info see here:" [15:32] thanks [15:33] it's not updated yet though [15:34] dholbach, jcastro: what is "tomorrow's hangout"? I have not received any emails nor there is something in the calendar [15:37] jose, sorry [15:38] jose, 16-17 UTC tomorrow, "13.10 Wrap-Up" [15:38] speakers? [15:38] I got an email [15:39] onair@ubuntu.com didn't [15:39] yeah, sorry - it was still under discussion [15:40] jose, Pat McGowan, Jono Bacon, Jorge Castro, Michael Hall, Thomas Strehl and myself + guests [15:40] IRC nicks? [15:40] pmcgowan, jono, jcastro, mhall119, thostr_, kgunn [15:40] sorry, missed Kevin Gunn in the first line [15:41] dholbach, what is the plan for the show? [15:41] is everyone confirmed? [15:43] jono, do demos or share stories for the individual teams - I mailed everyone about it a couple of times, the time was free in their calendars, so far Jorge and I have demos, I'll mail everyone again and put it into the calendars [15:43] thanks dholbach [15:43] dholbach, can you set up a doc where we can coordinate who is doing wha [15:43] what [15:43] thanks! [15:44] jono, yep, doing that now [15:46] thanks dholbach [15:51] jono, done [15:55] dholbach, thanks! [15:57] anytime [15:59] all right, got to go - dinner's on the table :) [15:59] see you! [16:22] jono: hey, you're having your Q&A today, right? [16:49] jose, yep [16:49] will do it at 11am Pacific [16:49] great, thanks [16:49] is that the time in the cal? [16:49] 6pm UTC [16:50] it was 12 pacific, 19 (7pm) UTC [16:50] already moved it [16:51] thanks jose [16:51] :) [17:50] jose, setting up the hangout now [17:53] great, thanks [18:25] jono: please, make sure to tell people to subscribe to us at youtube.com/ubuntuonair and follow us on twitter at twitter.com/ubuntuonair [19:23] jono, I think the crashreport in saucy will hit the privacy discussion again. What is 'the community' doing for damage control? [19:26] khildin: we've had crash reporting enabled on the desktop for a long while now. what's the issue? [19:29] popey, I think this video explains quite well what is happening: it seems the crashreports send more info than needed, for instance IP adresses are sent with the crashreport https://www.youtube.com/watch?v=T6c90W1AGls [19:29] or better formulated: ip addresses are sent as part of the crashreport [19:31] he's wildly inaccurate [19:31] IMO Canonical/Ubuntu community should anticipate a LOT more on these kind of things to explain why certain info is sent... [19:32] popey, that's part of why I asked what is going to be done on damage control... [19:32] "so anything a computer does on your IP address is logged by the smart scope service" [19:32] is just wrong [19:33] maybe he is wrong... I can't judge that... I do know the guy is a popular video blogger and a lot of bad karma is spread this way [19:34] "I don't like that data being available to the public" [19:34] it isn't [19:36] itis available to the dev community? [19:37] that is more or less public isn't it? [19:37] no [19:37] he (and now you) are making incorrect assumptions about who has access [19:39] I make the assumption that the data is available for ubuntu (community)devs, is that a wrong assuption? [19:39] yes [19:39] then to whom is the data available? [19:41] not public, not all ubuntu community devs [19:43] every website you visit gets your ip address. [19:44] that's turning around the answer but ok, can you explain why it is necessary to add an IP address to the _content_ of a crashreport? I mean, what extra value does it have for, for example, a rythmbox crash to add the IP address?? [19:45] probably easier to read the documentation.. https://wiki.ubuntu.com/ErrorTracker [19:45] Pici, what I understand is that the IP address is added to the crashreport... that is something else than getting the ip addres of a visitor on a website [19:46] You're mixing two things up here. [19:46] probably... :) [19:46] (as a result of quidsup video blurring two things) [19:47] He showed IP address for smart scopes, he didn't say IP address went with crash reports. [19:47] but I am confronted with a discussion about this on facebook (Dutch linux group) and there are a lot of assumptions and accusations flying around... that's why I ask here how things realy are [19:50] https://wiki.ubuntu.com/SmartScopes1304Spec [19:52] and what are the changes for saucy? [19:53] smart scopes weren't in 13.04 [19:53] the crash reporter was [19:54] ah.. there were postponed and didn't make it to 13.04 [19:54] Correct [19:57] clear info popey... thnx.. I will add that last link to the discussion... It states clearly what is stored and what not, what is available to 3rd parties and what not... [19:57] i left two comments on his video [19:57] quidsup makes wild speculation that stuff is available to 3rd parties [19:58] which is fine, people can make accusations, but it leads to this conversation ☻ [20:00] it is important that these kind of stories get explained... otherwise it will do a lot of harm [20:00] I don't think it is a good thing to ignore this [20:17] I dont think we're ignoring it, by fully documenting it on the wiki ☻ [20:34] I love it when people make stuff up! [20:34] popey, were you around when the people on /r/linux were claiming that we NIHed Upstart as a response to systemD? [20:35] heh [20:36] In shocking news today people are finding out that an internet search tool is using the _internet_ to return results [20:37] in other news, web servers have logs [20:40] popey, he appears to be one of your countrymen [20:40] therefore I blame you [20:40] heh [20:41] he's coming to the release party, I'll introduce him to Ev so he can ask questions about stuff [20:42] http://media.tumblr.com/906b4f6c254db98c2b8bb01b064382b2/tumblr_inline_mlxce6wTJi1qz4rgp.gif [20:43] see what I did there? [20:43] ☻ [21:41] poor popey