[00:00] <udsbotu> uds-jb-2: This session has ended.
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-2/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-2.log
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Track: Hardware | Kernel Team Round Table - Tuesday | Url: http://summit.ubuntu.com/uds-q/meeting/20457/kernel-team-round-table-tuesday/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-2.ogg.m3u
[16:50] <udsbotu> uds-jb-2: 5 minutes left in this session!
[16:51] <udsbotu> uds-jb-2: 4 minutes left in this session!
[16:52] <udsbotu> uds-jb-2: 3 minutes left in this session!
[16:53] <udsbotu> uds-jb-2: 2 minutes left in this session!
[16:54] <udsbotu> uds-jb-2: 1 minute left in this session!
[16:55] <udsbotu> uds-jb-2: This session has ended.
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Track: Foundations | Refine our SRU process to be more agile while avoiding too many pitfalls | Url: http://summit.ubuntu.com/uds-q/meeting/20626/foundations-q-more-agile-sru-process/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-2.ogg.m3u
[17:39] <udsbotu> uds-jb-2: 5 minutes left in this session!
[17:40] <udsbotu> uds-jb-2: 4 minutes left in this session!
[17:41] <udsbotu> uds-jb-2: 3 minutes left in this session!
[17:43] <udsbotu> uds-jb-2: 2 minutes left in this session!
[17:43] <udsbotu> uds-jb-2: 1 minute left in this session!
[17:45] <udsbotu> uds-jb-2: This session has ended.
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-2/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-2.log
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Track: Desktop | General X.org plans for Quetzal | Url: http://summit.ubuntu.com/uds-q/meeting/20573/desktop-q-xorg-general/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-2.ogg.m3u
[18:50] <udsbotu> uds-jb-2: 5 minutes left in this session!
[18:52] <udsbotu> uds-jb-2: 4 minutes left in this session!
[18:53] <udsbotu> uds-jb-2: 3 minutes left in this session!
[18:54] <udsbotu> uds-jb-2: 2 minutes left in this session!
[18:55] <udsbotu> uds-jb-2: 1 minute left in this session!
[18:56] <udsbotu> uds-jb-2: This session has ended.
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-2/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-2.log
[18:59]  * manjo waves 
[19:02] <manjo> hey harry
[19:04] <manjo> yep
[19:05] <manjo> no I have a copy
[19:06] <manjo> I am looking at a pdf I got in the mail
[19:07] <manjo> the pdf I have has around 50 pages is that the right now you guys are projecting ?
[19:10] <manjo> is this a private session ?
[19:10] <manjo> ok
[19:15] <manjo> I have asked for a drive from WD already for opal
[19:16] <manjo> they are working on shipping me one
[19:16] <manjo> and also the 4k/4k drive
[19:48] <manjo> https://wiki.ubuntu.com/UEFI-howto wiki to build OVMF
[19:48] <manjo> on linux
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Track: Foundations | Replace archive admin shell access with API clients | Url: http://summit.ubuntu.com/uds-q/meeting/20288/foundations-q-replace-archive-admin-shell-access/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-2.ogg.m3u
[22:32] <Laney> http://people.ubuntu.com/~laney/import-blacklist.py http://people.ubuntu.com/~laney/sync-blacklist.py
[22:40] <linuxtech> Sorry for being off topic for the API issues, but it is on topic for the Ubuntu archives.  I think we need something that reduces the downloading  required to keep systems updated and secure. Fedora does it with yum,  deltarpm and presto and we could be doing it with apt-sync and/or  debdelta or perhaps something else.  Why hasn't this been done?  And can we get it done this development cycle?
[22:40] <linuxtech> If this isn't the appropriate time or place to bring this up, would you please tell me whom I should contact or what list I should post it?
[22:48] <linuxtech> No one in the session checking irc?
[22:55] <udsbotu> uds-jb-2: 5 minutes left in this session!
[22:55] <linuxtech> Michael who?
[22:55] <linuxtech> Thanks!
[22:56] <udsbotu> uds-jb-2: 4 minutes left in this session!
[22:57] <udsbotu> uds-jb-2: 3 minutes left in this session!
[22:58] <udsbotu> uds-jb-2: 2 minutes left in this session!
[22:59] <udsbotu> uds-jb-2: 1 minute left in this session!
[23:00] <udsbotu> uds-jb-2: This session has ended.
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/junior-ballroom-2/ - http://ubottu.com/uds-logs/%23ubuntu-uds-junior-ballroom-2.log
=== ChanServ changed the topic of #ubuntu-uds-junior-ballroom-2 to: Track: Other | Create "agents" to deal with bugs and alert people about them | Url: http://summit.ubuntu.com/uds-q/meeting/20704/other-q-bug-agents/ | Audio: http://icecast.ubuntu.com:8000/junior-ballroom-2.ogg.m3u
[23:13] <Ursinha> hello
[23:14] <Ursinha> this is #ubuntu-uds-junior-ballroom-2
[23:14] <Ursinha> and this is the pad for this session: http://summit.ubuntu.com/uds-q/meeting/20704/other-q-bug-agents/
=== wylde_ is now known as wylde
[23:38] <jbicha> what's the difference between the sponsors team and the patch reviewers team? do we need 2 separate groups?
[23:53] <jbicha> what about automatically unprivating the retraced bugs?
[23:53] <komputes> would that be safe?
[23:53] <Ursinha> jbicha, is it safe to say that every retraced bug doesn't have sensitive information?
[23:53] <Ursinha> komputes, that
[23:53] <Ursinha> :)
[23:54] <jbicha> the bug control guidelines are as long as it doesn't have a stacktrace or contains obviously private info, it can be made public
[23:55] <Ursinha> jbicha, how can you automatically tell a bug has no obvious private info?
[23:55] <udsbotu> uds-jb-2: 5 minutes left in this session!
[23:55] <jbicha> and by "emailing the last one to upload", you're not going to email the Debian developer in case of directly-synced-from-Debian packages, right?
[23:55] <jbicha> when do apport crash bugs contain private info?
[23:56] <udsbotu> uds-jb-2: 4 minutes left in this session!
[23:57] <lifeless> jbicha: all the time
[23:57] <udsbotu> uds-jb-2: 3 minutes left in this session!
[23:57] <lifeless> jbicha: core files have whatever was in the process space; this could be the contents of an email, passwords, etc
[23:58] <jbicha> sorry that's what I meant, once the CoreDump.gz is removed, what private info is left?
[23:58] <udsbotu> uds-jb-2: 2 minutes left in this session!
[23:59] <jbicha> because I mark bugs as public all the time & as long as there isn't a CoreDump, I've basically not seen bugs that should still be private
[23:59] <udsbotu> uds-jb-2: 1 minute left in this session!
[23:59] <jbicha> it's a pain when I triage gnome-shell bugs, having to manually unprivate all the crash bugs