[00:00] http://minus.com/m7ZarkzJM/ [00:00] pmatulis: Seif said that the Ubuntu One integration bug should be fixed === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/grand-ballroom-a/ - http://ubottu.com/uds-logs/%23ubuntu-uds-grand-ballroom-a.log [00:00] jbicha: ah thanks [00:00] bug number? [00:01] pmatulis: follow up with seiflofty [00:02] jbicha: ty === vibhav is now known as Guest3189 === vibhav is now known as Guest82292 === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Track: Other | extending juju to the hud | Url: http://summit.ubuntu.com/uds-q/meeting/20814/other-q-juju-and-the-hud/ | Audio: http://icecast.ubuntu.com:8000/grand-ballroom-a.ogg.m3u [16:01] _____ ____ ____ _____ [16:01] / ____| / __ \ / __ \ | __ \ [16:01] | | __ | | | || | | || | | | [16:01] | | |_ || | | || | | || | | | [16:01] | |__| || |__| || |__| || |__| | [16:01] \_____| \____/ \____/ |_____/ [16:01] __ __ ____ _____ _ _ _____ _ _ _____ [16:01] | \/ | / __ \ | __ \ | \ | ||_ _|| \ | | / ____| [16:01] | \ / || | | || |__) || \| | | | | \| || | __ [16:01] | |\/| || | | || _ / | . ` | | | | . ` || | |_ | [16:01] | | | || |__| || | \ \ | |\ | _| |_ | |\ || |__| | [16:01] |_| |_| \____/ |_| \_\|_| \_||_____||_| \_| \_____| [16:04] morning [16:08] Hey guys, I am listening in, and I am interested in this and can answer detailed Juju questions. [16:09] ok [16:09] we are not ignoring IRC [16:09] :-) [16:12] Those would all just be packages IMO. [16:13] <-- A gatekeeper for the juju charm store. [16:14] I have some ideas on how to build processes around gathering and catering these workflows, as I've been in charge of doing that with juju :) [16:15] * SpamapS is Clint Byrum FYI :) [16:15] OH NOT THAT GUY! [16:15] nice palindromic nick [16:17] So you basically have two things. You have workflows for apps, and you have information providers that abstract system details to make it easier to write the workflows. [16:18] Thats the subtle power of Juju for cloud/server apps is that the charms are super easy to write because you don't have to learn "the cloud". [16:19] I don't think juju itself is useful for this. [16:19] but the ideas from juju map well to this idea [16:20] * cprofitt agrees [16:22] GOOD NAME! [16:22] voodoo is the evil version of juju [16:24] have you thought about how to collect and distribute these "charmlings" ? [16:26] Make them easy to write and/or record.. #1 reason charms get people excited is that they are easy to write. [16:26] * cprofitt agrees [16:26] Guys I have to go listen to another session. Very interesting stuff! [16:27] ping me in here if you need me and I'll come back to this audio feed [16:28] I'm more talking about how to distribute and collect them from/to users not on the actual machine. [16:28] Like if user A has an awesome workflow.. you don't want to wait until the next release of Ubuntu to get that to users. [16:29] juju charms are ways to extend Ubuntu post-release [16:29] something 'official' is useful for the user trust and adoption [16:29] vudu ;) [16:29] ok I'm off the audio feed.. cheers! [16:30] k [16:30] thanks for coming SpamapS !! === fenris is now known as Guest56365 [16:49] uds-gb-a: 5 minutes left in this session! [16:50] uds-gb-a: 4 minutes left in this session! [16:51] uds-gb-a: 3 minutes left in this session! [16:52] uds-gb-a: 2 minutes left in this session! [16:53] uds-gb-a: 1 minute left in this session! [16:54] uds-gb-a: This session has ended. === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/grand-ballroom-a/ - http://ubottu.com/uds-logs/%23ubuntu-uds-grand-ballroom-a.log === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Track: Desktop | Desktop Roundtable | Url: http://summit.ubuntu.com/uds-q/meeting/20830/desktop-q-desktop-roundtable/ | Audio: http://icecast.ubuntu.com:8000/grand-ballroom-a.ogg.m3u [18:18] one other thing back to xorg... flicker free resume from suspend? (I see a bunch of virtual console spam on resume each and every time... sorry no bug filed yet but happy to demo to anyone interested ;o) ) [18:22] drussell: System compositor should fix that (although isn't strictly necessary); we just need to not VT switch on suspend. [18:29] RAOF: cool, is there an already existing bug I can subscribe to? [18:31] drussell: Not that I can think of offhand, sorry. [18:31] RAOF: no worries [18:42] is there anything official (or 'officialish') about windicators? being a priority or not for 13.04, 13.10, etc [18:49] uds-gb-a: 5 minutes left in this session! [18:50] uds-gb-a: 4 minutes left in this session! [18:51] uds-gb-a: 3 minutes left in this session! [18:52] uds-gb-a: 2 minutes left in this session! [18:53] uds-gb-a: 1 minute left in this session! [18:54] uds-gb-a: This session has ended. === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Track: Cloud & Server | Next steps for Hadoop on Ubuntu | Url: http://summit.ubuntu.com/uds-q/meeting/20440/servercloud-q-bigdata-hadoop/ | Audio: http://icecast.ubuntu.com:8000/grand-ballroom-a.ogg.m3u [18:59] o/ [19:42] listening, no comments [19:42] thanks [19:43] you too brian [19:54] uds-gb-a: 5 minutes left in this session! [19:55] uds-gb-a: 4 minutes left in this session! [19:56] uds-gb-a: 3 minutes left in this session! [19:57] uds-gb-a: 2 minutes left in this session! [19:58] uds-gb-a: 1 minute left in this session! [19:59] uds-gb-a: This session has ended. === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/grand-ballroom-a/ - http://ubottu.com/uds-logs/%23ubuntu-uds-grand-ballroom-a.log === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Track: Community | Unblocking Developers | Url: http://summit.ubuntu.com/uds-q/meeting/20563/community-q-unblocking-developers/ | Audio: http://icecast.ubuntu.com:8000/grand-ballroom-a.ogg.m3u [22:08] _ _ _ _ _ _ [22:08] | |__ ___| | | ___ | |__ (_)_ __ _ __ (_) ___ ___ [22:08] | '_ \ / _ \ | |/ _ \ | '_ \| | '_ \| '_ \| |/ _ \/ __| [22:08] | | | | __/ | | (_) | | | | | | |_) | |_) | | __/\__ \ [22:08] |_| |_|\___|_|_|\___/ |_| |_|_| .__/| .__/|_|\___||___/ [22:08] |_| |_| [22:09] greetings Daniel [22:12] hey hey NMinker :) [22:12] * micahg waves from another room [22:13] I think overall we're doing a lot better with SRU/backport requests [22:14] Can we add lintian instructions to the packaging guide [22:14] that might catch quite a few things that a sponsor should flag [22:15] perhaps we can half a stripped down lintian profile for SRUs since quite a bit of stuff we wouldn't allow in an SRU [22:15] s/half/have/ [22:18] can we get requestbackport to warn if source changes for build deps are required? [22:19] micahg: hrm, seems doable [22:19] hmm, testing requirements for backports are much lower than SRU [22:20] i think that's actually false in practice [22:20] especially for anything with a reverse dep [22:20] there's no explicit reverse dep testing for srus [22:20] yes, well, we generally don't allow invasive changes in an SRU either :) [22:21] And I don't recall a case were builds/installs/runs wasn't sufficient (except in the case of rdepends) [22:21] right, usually bugs are found in the main archive version as well [22:23] o/ listening in now [22:23] * ScottK is just on IRC. [22:24] * micahg is also just on IRC [22:24] ScottK: what's an example of when a backport went wrong? [22:24] svn on hardy [22:24] Tested a selection of rdepends and got totally screwed. [22:24] flashplugin-nonfree on hardy [22:25] That one too. [22:25] That's actually the one non-rdepend one I can think of. [22:25] (I'd forgotten - painful memory) [22:25] ScottK: discussion in-room is about relaxing the testing requirements since notautomatic is on [22:25] ah, hardy, the first ubuntu i ever installed [22:25] we can possibly be a bit less conservative [22:26] I don't know what's less conservative than builds/installs/runs [22:26] broder: the issue is that NotAutomatic helps for rdepends in backports, not rdepends already in use on the system [22:26] ScottK: b/i/r on r-deps [22:26] the rdep testing is what's expensive [22:27] What it means is some stuff won't get backported. [22:27] I'm not sure how else to deal with it. [22:27] The official rule was no library backports. [22:28] We bent that via extensive testing. [22:28] When we didn't do the testing, we've gotten burned. [22:28] Not sure how to draw a line. [22:28] * broder nods [22:29] OTOH, if someone in ubuntu-backports wants to accept the risk, I don't strongly object to that as long as they also accept responsibility for cleaning up resulting messes. [22:29] ok. we're moving on to some other stuff; laney is going to follow up by mail [22:29] K. [22:30] ahem. [22:31] I feel that I am humbled by archive admins :) [22:31] SpamapS: aren't you an archive admin? [22:32] micahg: not technically ;) [22:32] micahg: I need to finish my training [22:32] re SRU self verification.. I think it would be fine IF we make the burden of proof higher than "works for me!" [22:34] The 7 day backing period needs to be backed by popcon numbers if thats what we're goign to use. [22:39] Isn't the role of a sponsor to educate and enable, not to do the work? [22:39] It's a balance. [22:39] Make it too hard and they give up and go away. [22:39] right [22:40] For the first upload, I don't care if their name in the changelog ends up being the only thing the didn't have to fix. [22:41] I like the idea of taking everything they've done, even if its not in the right place or format, and getting it into the archive. [22:42] I tend to draw the line at *creating* things like changelog entry or patch descriptions. [22:42] ah, yeah, i disagree with that [22:42] right, usually we come back to over 100 after UDS [22:42] i think we should not require people to care about ubuntu processes to fix ubuntu bugs [22:43] broder: agreed.. I will ask somebody "Can you describe the change?" or copy the change description from the bug description. I don't make them actually run 'dch' ;) [22:43] ah, sure [22:46] Yes thats what I do. [22:47] maybe a bot poking after 2 weeks of no activity? [22:47] I don't think you lose something by taking it off the list and instruct the contributor "When you've resolved X, please re-subscribe sponsors" or "Please change it back to Needs Review" [22:48] well, if the person no longer wishes to work on it, it can go back to triaged [22:48] Though it would be nice if the *age* was not lost. [22:50] not always true [22:52] I'd suggest 1 hr increments for community people [22:53] 1hr is enough to sponsor 2-4 debdiffs or 1-2 merge proposals [22:53] right, this is for normal stuff :) [22:54] * micahg has a bad habit of that as well :) [22:54] uds-gb-a: 5 minutes left in this session! [22:55] they close stuff other people leave open :) [22:55] They're just better than us [22:55] period [22:55] uds-gb-a: 4 minutes left in this session! [22:56] umm, whoever uploads is taking responsibility for the upload [22:56] uds-gb-a: 3 minutes left in this session! [22:57] uds-gb-a: 2 minutes left in this session! [22:57] depends on the bug I think [22:58] slangasek: I'd say anythiing that breaks the archive is the responsibility of the uploader [22:58] uds-gb-a: 1 minute left in this session! [22:59] uds-gb-a: This session has ended. [22:59] I have new on the video stuff once the new ones are done if they get done :) The New Boston said that they will put it on there site . His python video have 288,000 hits and more on his other ones he said sure he would put them on his video tutorial collection [23:00] s|new|news === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Currently no events are active in this room - http://summit.ubuntu.com/uds-q/grand-ballroom-a/ - http://ubottu.com/uds-logs/%23ubuntu-uds-grand-ballroom-a.log [23:01] please don't break th archive on Friday at EOD :) [23:03] that's what the sponsorship queue is for, alternatively, ask the patch pilot in #ubuntu-devel [23:05] some patch pilots manage to do patch review as well === ChanServ changed the topic of #ubuntu-uds-grand-ballroom-a to: Track: | Make Ubuntu fully proxy compatible | Url: http://summit.ubuntu.com/uds-q/meeting/20711/full-proxy-support/ | Audio: http://icecast.ubuntu.com:8000/grand-ballroom-a.ogg.m3u [23:20] I'm not able to listen to this session (listening to another one), but one difficulty is having proxy setups to test with [23:21] https://bugs.launchpad.net/ubuntu/+source/software-center?field.searchtext=proxy has some examples [23:21] Several of them are incomplete just because of difficulty in reproducing the problem [23:22] mpt: we can take care of this, I guess [23:54] uds-gb-a: 5 minutes left in this session! [23:55] uds-gb-a: 4 minutes left in this session! [23:56] uds-gb-a: 3 minutes left in this session! [23:57] uds-gb-a: 2 minutes left in this session! [23:58] uds-gb-a: 1 minute left in this session! [23:59] uds-gb-a: This session has ended.