[11:56] <mvuelma> Good morning.
[11:57] <Destine> mvuelma, morning! Well, actually it's night for me, :-)
[11:58] <mvuelma> Oh, excuse me, Destine. So, good evening.
[12:00] <head_victim> Evening all, just organising ourselves for the 1200 UTC Ubuntu Membership Board Meeting
[12:04] <cyphermox> #startmeeting 1200 UTC Ubuntu Membership Board
[12:04] <meetingology> Meeting started Wed Oct 24 12:04:30 2012 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[12:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[12:04] <cyphermox> Hello and welcome to the Ubuntu Membership Review Board for the 1200 UTC meeting for October 24, 2012. The wiki page for the Review Board is available here: https://wiki.ubuntu.com/Membership/Boards
[12:05] <cyphermox> We will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off.
[12:05] <cyphermox> The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).
[12:05] <cyphermox> Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.
[12:05] <cyphermox> During this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.
[12:05] <cyphermox> When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the sum of those numbers is positive, then the applicant is now an official Ubuntu member! (feel free congratulate them!)
[12:06] <cyphermox> #voters cyphermox head_victim IdleOne destine
[12:06] <meetingology> Current voters: IdleOne cyphermox destine head_victim
[12:06] <cyphermox> Now, without any further ado, lets get started with the first applicant...
[12:06] <cyphermox> (just a second
[12:06] <IdleOne> Morning :P
[12:06] <IdleOne> :)
[12:06] <cyphermox> #subtopic Marta Vuelma (mvuelma )
[12:08] <cyphermox> mvuelma: are you around? (sorry if you're busy typing :)
[12:08] <mvuelma> Hello to all.
[12:08] <cyphermox> Hi!
[12:09] <mvuelma> May I start introducing myself?
[12:09] <cyphermox> of course :)
[12:09] <head_victim> Evening mvuelma :)
[12:09] <mvuelma> Well, let's go.
[12:10] <mvuelma> I live in Brazil and I started working with Linux in 2001. In 2010 I started my activities with Ubuntu community.
[12:11] <mvuelma> Desde esta data tenho participado de diversas formas na comunidade.
[12:11] <mvuelma> Since this date I have participated in various ways in the community.
[12:11] <mvuelma> Sorry, I wrote last words in Portuguese.
[12:12] <head_victim> That's ok, I've had whole IRC conversations via google translate before
[12:13] <mvuelma> I have done several events in various locations in the country. Lectures, courses.
[12:13] <head_victim> So I see you have some good testimonials, do you have any links showing you in action with the events, lectures and training?
[12:13] <IdleOne> https://launchpad.net/~mvuelma
[12:13] <IdleOne> https://wiki.ubuntu.com/MartaVuelma
[12:14] <mvuelma> Participate actively in supporting the user community and was chosen LoCoTeam Leader in my region.
[12:14] <cyphermox> #link https://launchpad.net/~mvuelma
[12:15] <cyphermox> #link https://wiki.ubuntu.com/MartaVuelma
[12:15] <mvuelma> Well, I think you may check more detailed information in my wiki.
[12:15] <cyphermox> (just making sure meetingology sees the links)
[12:16] <mvuelma> That's it!
[12:16] <IdleOne> mvuelma: can you tell us a bit more about ubuntu-br-rs ?
[12:17] <mvuelma> IdleOne, of course.
[12:17] <mvuelma> Here in Brazil, some LoCo Teams were inactive.
[12:18] <IdleOne> ah, ok so it is a sub-loco team of the -br loco?
[12:18] <mvuelma> It was the case of ubuntu-br-rs.
[12:19] <mvuelma> Yes, we are a sub-loco.
[12:19] <IdleOne> has the -rs team held any events?
[12:20] <mvuelma> As I have been promoting a series of events since last year here in my region, we change the vision of our group and we have several new members.
[12:20] <mvuelma> Right now, we are an active group again.
[12:21] <mvuelma> and we already have a schedule of events and activities for next year
[12:21] <IdleOne> link please
[12:22] <mvuelma> Sorry, not published yet.
[12:22] <IdleOne> what about past events, any blog posts you can link?
[12:22] <head_victim> Can you explain the events you've run recently and your involvement in them. We're trying to get a feel for the size and the content of them.
[12:23] <cyphermox> there are some posts on the mailing list for ubuntu-br-rs; I'm trying to read it with my limited understanding of portugese :)
[12:23] <cyphermox> #link https://lists.launchpad.net/ubuntu-br-rs/
[12:23] <mvuelma> May this link be in Portuguese?
[12:23] <cyphermox> mvuelma: of course
[12:24] <head_victim> I love chromium's google translate stuff, makes multi lingual issues disappear. Until it doesn't quite get it right.
[12:25] <mvuelma> This event occurs every year in my region, and this year was led entirely by me: http://www.ubuntubrsc.com/grupo-de-usuarios-do-ubuntu-br-marcou-presenca-no-fisl-13.html
[12:25] <destine> head_victim, nice to have learned spanish, which makes Portuguese easier.
[12:26] <head_victim> Ah I'm boring, english only here (even then some say I've barely conquered that)
[12:26] <mvuelma> It's the largest free software event in Latin America and was attended by over 7000 participants.
[12:26] <licio> Marta is a key member of ubuntu-br community, she has been supporting the team on the major conferences in Brazil
[12:27] <head_victim> licio: thanks for that
[12:27] <head_victim> mvuelma: reading the link now, seems perfect :)
[12:27] <IdleOne> Anybody else here to cheer for mvuelma ?
[12:27] <mvuelma> head_victim, thank you.
[12:27] <IdleOne> Now is the time folks :)
[12:28] <licio> Also, the guys from ubuntu-br-sc have a hangout on air every friday and she and Ursinha are always there to answers public questions ;)
[12:29] <licio> IdleOne, bad brazilian time :/ 10am. some are sleeping and the rest are working :(
[12:29] <head_victim> mvuelma: thanks for that link, are there any more? (Just asking, I like reading about what other locos are doing)
[12:30] <mvuelma> head_victim, yes, you may check this one: http://martavuelma.wordpress.com/2012/04/29/balanco-do-flisol-2012/
[12:30] <licio> head_victim, more in the plus page https://plus.google.com/+Ubuntu-BR-SC/posts
[12:31] <mvuelma> Flisol is a "Install Fest" event.
[12:31] <mvuelma> held in several cities in Latin America simultaneously
[12:31] <head_victim> I ran one here last year but was only able to get 20 or so along, your photos put that to shame.
[12:33] <cyphermox> #vote Marta Vuelma to join Ubuntu Members
[12:33] <meetingology> Please vote on: Marta Vuelma to join Ubuntu Members
[12:33] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[12:33] <IdleOne> +1
[12:33] <meetingology> +1 received from IdleOne
[12:33] <cyphermox> +1
[12:33] <meetingology> +1 received from cyphermox
[12:34] <head_victim> +1 Keep up the great work with the loco
[12:34] <meetingology> +1 Keep up the great work with the loco received from head_victim
[12:34] <destine> +1
[12:34] <meetingology> +1 received from destine
[12:34] <cyphermox> #endvote
[12:34] <meetingology> Voting ended on: Marta Vuelma to join Ubuntu Members
[12:34] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[12:34] <meetingology> Motion carried
[12:34] <IdleOne> Congrats mvuelma and welcome :)
[12:34] <destine> mvuelma, congrats!
[12:34] <cyphermox> mvuelma: congrats!
[12:34] <tiagoscd> mvuelma congrats :)
[12:34] <mvuelma> Thank you everyone!
[12:34] <cyphermox> please, add your blog to planet.ubuntu.com when you have a chance ;)
[12:34]  * Ursula cheers
[12:35] <NikTh> Congrats mvuelma  :)
[12:35] <mvuelma> I am very happy with this recognition.
[12:35] <mvuelma> cyphermox, I'll do that.
[12:35] <head_victim> mvuelma: good work doing what you have, the challenge is to keep it going into the future :)
[12:35] <mvuelma> head_victim, certainly, this is the challenge
[12:36] <mvuelma> head_victim, and let's make this challenge a reality
[12:36] <cyphermox> I don't think we have other applicants, so unless there is other business to discuss, I'll end the meeting.
[12:37] <head_victim> cyphermox: none other listed on the wiki
[12:37] <cyphermox> great!
[12:37] <head_victim> Should we formalise the mailing list conversation abotu going to monthly?
[12:37] <tiagoscd> mvuelma is making a great job at brazilian community
[12:37] <cyphermox> there was such a conversation?
[12:37]  * cyphermox fails at reading email
[12:38] <head_victim> Perhaps it was in the channel
[12:38] <head_victim> Hmm
[12:38] <head_victim> tiagoscd: yes, she is doing great work
[12:38] <cyphermox> well, if it was on IRC, we should definitely take it to the mailing list and make sure the CC knows about it, at least
[12:38] <tiagoscd> head_victim, I'm sad because I've no time to make a testimonial for her
[12:38] <cyphermox> tiagoscd: chiming in here is just as good :)
[12:39] <licio> mvuelma, congrats! well deserved!
[12:39] <head_victim> tiagoscd: don't be sad, her application was successful!
[12:39] <mvuelma> licio, thank you so much!
[12:40] <cyphermox> #endmeeting
[12:40] <meetingology> Meeting ended Wed Oct 24 12:40:02 2012 UTC.
[12:40] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-24-12.04.moin.txt
[12:40] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-24-12.04.html
[14:59]  * slangasek waves
[14:59] <jodh> o/
[15:00]  * stgraber waves
[15:02] <slangasek> #startmeeting
[15:02] <meetingology> Meeting started Wed Oct 24 15:02:17 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:02] <slangasek> [TOPIC] Lightning round
[15:03] <slangasek> $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox stokachu)
[15:03] <slangasek> bdmurray xnox slangasek doko jodh stgraber stokachu barry cjwatson ogra ev infinity
[15:03] <bdmurray> bug review of update-manager / ubuntu-release-upgrader bug reports
[15:03] <bdmurray> analysis and testing of bug 346386 / bug 24061
[15:03] <bdmurray> wrote a new test case for bug 346386
[15:03] <bdmurray> wrote a test case for ubuntu-release-upgarder bug 1065806
[15:03] <bdmurray> quantal-proposed upload for ubuntu-release-upgrader bugs 1070043, 1065806
[15:04] <bdmurray> quantal-proposed upload for apport bug 1039220
[15:04] <bdmurray> precise-proposed upload for apport-symptoms bug 1070542
[15:04] <bdmurray> sru verification of apt bug 346386, 1050779, 1050791
[15:04] <bdmurray> sru verification of apport bug 1050853
[15:04] <bdmurray> sru verification of coreutils bug 1038468
[15:04]  * mvo hugs bdmurray
[15:04] <bdmurray> sru verification of update-notifier bug 946718
[15:04] <bdmurray> sru verification of ubuntu-release-upgrader bug 1068389
[15:04] <bdmurray> test case creation for apt bug 1065429
[15:04] <bdmurray> reported ubuntu-release-upgrader bugs 1067542, 1067393, 1068874
[15:04] <bdmurray> tested vmware player 5 installer in quantal
[15:04] <bdmurray> release noted bug 993056
[15:04] <bdmurray> setup rls-r-tracking reports on cranberry
[15:05] <bdmurray> ⌁ done ⌁
[15:05] <xnox> * Quantal Released. Yeah!
[15:05] <xnox> * Did merges (see lp:~xnox/*/r-proposed, mostly partman-* and related
[15:05] <xnox>   packages). Still some todo.
[15:05] <xnox> * Staging ubiquity bugfixes in lp:~xnox/ubiquity/r-proposed
[15:05] <xnox> * Helping with python3.3 transition at the archive opening
[15:05] <xnox> * Added ubiquity slide decks https://wiki.ubuntu.com/Ubiquity/SlideDecks to
[15:05] <xnox>   unblock design team on changes to installer.
[15:05] <xnox> ..
[15:05]  * xnox also started py3.3 by default ppa
[15:06] <slangasek> xnox: mm?  I thought that was already in hand (barry)
[15:06] <doko> he's at a conf today
[15:07] <slangasek> yes
[15:07] <xnox> me and doko finished up rebuilding public modules yesterday. and we'd rather get it done earlier than later.
[15:07] <slangasek> ok
[15:07]  * xnox has nasty python bugs for barry =)
[15:08] <infinity> slangasek: You're up. :P
[15:08] <slangasek>  * Secure Boot follow-through: getting support for efi variable writing, efifb quirking
[15:08] <slangasek>  * UDS prep
[15:08] <slangasek>  * debugging heat issues on my laptop in quantal
[15:08] <slangasek>  * preliminary look at fixing cross-bootstrapping issues in raring (http://people.linaro.org/~wookey/buildd/quantal/sbuild-ma/status.html)
[15:08] <slangasek> (done)
[15:09] <doko> - quantal: two last java ftbfs for the release
[15:09] <doko> - gcc multiarching: libgfortran-dev split & cross fixes
[15:09] <doko> - gcc x32: gcc bits are ready, blocked on eglibc for further testing
[15:09] <doko> - gcc aarch64: integrated fixes
[15:09] <doko> - gcc upstream: armhf-triplet patches upstreamed, fixed libgo ftbfs on trunk
[15:09] <doko> - binutils update to 2.23 just to find out that the upstream release is incomplete
[15:10] <doko> - raring opening: binutils & gcc bits in place, waiting for kernel headers 3.7 (not anymore for the opening), and eglibc ...
[15:10] <doko> - raring opening: python3.3 is supported, most extension modules are built for 3.3, bug fixes and no change uploads.  test rebuild can start now
[15:10] <doko> - finished openjdk security updates (not yet published)
[15:10] <doko> (done)
[15:10] <jodh> * misc: on holiday yesterday.
[15:10] <jodh> * upstart:
[15:10] <jodh>   - Fixed bug 1049820 and bug 888910.
[15:10] <jodh>   - Added new test for stateful re-exec.
[15:10] <jodh>   - Currently chasing down a test race issue.
[15:10] <jodh> * TODO:
[15:10] <jodh>   - get stateful-reexec into raring.
[15:10] <jodh>   - blueprints and UDS planning.
[15:10] <jodh> ⃕
[15:11] <stgraber>  - On vacation Friday, Monday and Tuesday
[15:11] <stgraber>  - Release
[15:11] <stgraber>   - Released Ubuntu 12.10
[15:11] <stgraber>  - Networking
[15:11] <stgraber>   - Went through the bug reports, prepared some uploads for when raring opens
[15:11] <stgraber>  - Container
[15:11] <stgraber>   - Reviewed a few branches, fixed a bunch of upstream bugs, next upstream daily build should be good
[15:11] <stgraber>  - Installer
[15:11] <stgraber>   - Did some tests on the preseed generator script. Mostly working, need to check if I can do something
[15:11] <stgraber>     about the remaining keys easily. Will be uploaded as part of installation-report in raring.
[15:11] <stgraber>  - UDS
[15:11] <stgraber>   - Submitted usual networking session
[15:11] <stgraber>   - Planned session on making dist upgrade a bit more reliable (especially lts-to-lts)
[15:11] <stgraber>   - Going through notes to figure out if there's something else than should be discussed at UDS
[15:11] <stgraber>  - TODO
[15:11] <stgraber>   - Some more UDS preps
[15:11] <stgraber>   - The usual merges
[15:11] <stgraber>   - Push all lxc fixes to a bugfix branch so 0.8 can finally be released
[15:11] <stgraber> (DONE)
[15:12] <stokachu> Nothing on fire at the moment, requested a backport for pbuilder-scripts in precise, still working on appmenu-gtk multiarch solution. done.
[15:13] <infinity> cjwatson: I think we're barryless.
[15:13] <cjwatson> Spent all week working on raring-proposed -> raring auto-migration, both the migration code itself ("britney") and the necessary Launchpad patches.  I'm currently waiting for one LP database patch to be deployed, and then for an LP code patch to be reviewed, landed, and deployed; after that we should be able to turn this all on, open raring, and start auto-syncs.
[15:13] <cjwatson> ..
[15:13] <slangasek> ogra_:
[15:13] <cjwatson> (Oh, for clarity, those patches are the ones that forcibly redirect all uploads to -proposed.)
[15:14] <ogra_> done:
[15:14] <ogra_>  * internal project work, to be presented at UDS
[15:14] <ogra_>  * registered some specs
[15:14] <ogra_> todo:
[15:14] <ogra_>  * go to UDS, flesh out the spec content
[15:14] <ogra_>  * test multiarch cross compiling
[15:14] <ogra_> ..
[15:14] <ev> - Spending most of my time on my UDS plenary.
[15:14] <ev> - We discovered that our current calculation for average errors per calendar
[15:14] <ev>   day (number of errors / unique users in the past 90 days) is incorrect. We
[15:14] <ev>   have good reason to believe that it is what caused the large spike around
[15:14] <ev>   release in the 12.10 graph:
[15:14] <ev>   https://bugs.launchpad.net/errors/+bug/1069827
[15:14] <ev>   We've been working on a fix for this. I implemented an early solution, but
[15:14] <ev>   we found out again that is was wrong. We'll be taking this to canonical-tech
[15:14] <ev>   and http://stats.stackexchange.com.
[15:14] <ev> - Fixed a number of small issues in http://errors.ubuntu.com. We now identify
[15:14] <ev>   private bugs rather than treating them as regressions.
[15:14] <ev> - Fixed some issues in the juju deployment code for the entire whoopsie daisy
[15:14] <ev>   project. Discussions with juju people on how to best represent the
[15:14] <ev>   schema creation dependency that the retracers have on the main daisy
[15:14] <ev>   instance.
[15:14] <ev> (done)
[15:15] <infinity> Last week:
[15:15] <infinity>  - Released a new version of some operating system or other
[15:15] <infinity>  - Worked on the opening of raring
[15:15] <infinity>  - Several merges, bug fixes, and SRUs relating to the opening
[15:15] <infinity>  - Worked on eglibc 2.16 4-way merge between Debian, Ubuntu, schepler, and wookey
[15:15] <infinity>  - Discussed glibc 2.17 roadmap with upstream
[15:15] <infinity>  - Meetings, meetings, and more meetings
[15:15] <infinity>  - Spent some time cursing at bug 997359 (jodh: Can we get this fixed?)
[15:15] <infinity> This week:
[15:15] <infinity>  - Finish up eglibc 2.16, including making future merges much less effort
[15:15] <infinity>  - Revisit kernel cleanup, time permitting
[15:15] <infinity>  - Do some pre-UDS prep and blueprinty things
[15:15] <infinity>  - UDS
[15:15] <infinity> ☭
[15:15] <doko> finished? don't see it
[15:15] <jodh> infinity: I'm waiting for feedback on https://bugs.launchpad.net/libnih/+bug/997359/comments/2 :)
[15:15] <cjwatson> I think "this week" is a to-do
[15:16] <infinity> jodh: I realise there's a "rebootstrap nih/glibc every time" workaround for the above, but it would be lovely to just fix it.
[15:16] <slangasek> infinity: do you expect 2.16 to land this week?
[15:16] <infinity> slangasek: Yeahp.
[15:16] <slangasek> ok cool
[15:16] <cjwatson> You have until, uh, not quite sure if you want it before britney's all ready.
[15:17] <cjwatson> Probably Friday by this point (which is a bit unfortunate since I'm meant to be on holiday).
[15:17] <cjwatson> Might end up turning it on from the hotel :)
[15:17] <infinity> A pre-UDS one day rest?
[15:17] <infinity> Oh crap, it's almost the end of the year.  I should take a holiday sometime too.
[15:17] <cjwatson> My family'll be with me so hacking time a bit limited.  We'll see.
[15:18] <infinity> La la la.
[15:18] <slangasek> infinity: APPROVED
[15:18]  * slangasek whistles and runs away
[15:18] <slangasek> [TOPIC] Bugs
[15:18] <ogra_> infinity, heh, me too
[15:19] <slangasek> bdmurray: I guess we might be in a weird spot for this since raring has no new bugs and we're not putting as much effort into quantal SRUs... but any that you think we need to fix though?
[15:19] <infinity> jodh: Your maybe in comment #2 is a bit vague, but without digging into it further, I say "yes, that would be lovely". :P
[15:20] <xnox> Hmm.... we will have 12.04.2 on the New Years Eve.
[15:20] <bdmurray> slangasek: no, not yet.  however I've been trying to verify the fix for bug 1066445 so that the apt sru which fixes bug 346386 can be released.
[15:21] <bdmurray> I've had no luck getting the failure in bug 1066445 though
[15:21] <cjwatson> xnox: 31 Jan, not 31 Dec :-)
[15:21] <slangasek> that's the one that cjwatson suggested randomly permuting the cache size on, yes?
[15:21] <bdmurray> right, I've tried much smaller cache sizes
[15:21] <cjwatson> Yeah, it's probably a right pig to reproduce if you're unlucky
[15:22] <xnox> cjwatson: Oh good =)
[15:22] <infinity> Trying to reproduce on precise?
[15:22] <cjwatson> If it helps, you can use 'apt-cache gencaches' rather than 'apt-get update' (after the first time), which will be a lot faster since it doesn't download anything
[15:22] <bdmurray> would regression testing, dist-upgrades with the -proposed apt, be sufficient?
[15:22] <bdmurray> infinity: yes on precise
[15:22] <slangasek> yeah, I'm kinda thinking we should just call it good with the regression test
[15:23] <cjwatson> I suspect regression testing may be all we can realistically get, in the absence of a deliberately malicious fuzzer tool
[15:23] <slangasek> especially if we're pushing another apt SRU right behind it, the impact on users of having an extra SRU is minimal
[15:23] <cjwatson> Which arguably might be a good idea given the nature of this code
[15:23] <cjwatson> But it's not something we can knock together quickly
[15:24] <cjwatson> Unfortunately we don't have a /var/lib/apt/ tarball from that bug, otherwise reproduction would be a matter of dropping that in place and running 'apt-cache gencaches'
[15:25] <bdmurray> okay, I'll do one more test with apt from -proposed and then comment on the bug and tag it v-done
[15:25] <slangasek> sounds good
[15:25] <cjwatson> Do make sure you're testing on amd64
[15:26] <cjwatson> slangasek: BTW, the reason it's more likely when upgrading to quantal than when upgrading within precise is bigger Packages files with more Multi-Arch entries
[15:26] <bdmurray> I am - is that mentioned in the bug at all?
[15:26]  * infinity just tried i386 and amd64 and failed to reproduce.
[15:26] <slangasek> cjwatson: fun
[15:26] <cjwatson> bdmurray: No, but it only bit amd64 originally
[15:26] <jodh> I wonder if bug 1016040 might have indirectly fixed bug 1066445?
[15:27] <cjwatson> jodh: Not that way round
[15:28] <slangasek> bdmurray: is that everything?
[15:28] <bdmurray> slangasek: that is all I have for today
[15:28] <slangasek> bdmurray: ok, thanks
[15:28] <slangasek> [TOPIC] UDS
[15:28] <slangasek> blueprints
[15:29] <slangasek> anything that you expect to have a session on at UDS, get your blueprint registered and proposed for uds-r by *tomorrow*
[15:29] <slangasek> and *before* Monday, I want everyone to have gone through the schedule and subscribed themselves to the sessions they plan to attend
[15:30] <slangasek> for any session that you would ask to have moved to work around a conflict, you should be marking yourself "participation essential"
[15:30] <slangasek> I do not want you coming to me during the week and asking to move sessions because of a conflict - *tell the system* that it's a conflict and let the auto-scheduler do its job, please :)
[15:31] <cjwatson> jodh: So - I suppose it's possible, but I think it's relatively unlikely as my observations while debugging 1066445 were that it tended to crash immediately
[15:31] <slangasek> (ok, if you only find out during the week that you have to be at two sessions at once, come to me all the same - but don't let this happen for things you should know about in advance)
[15:31] <slangasek> clear?
[15:32] <ogra_> slangasek, what if we bribe you with lots of beer for it ?
[15:32]  * infinity gets the impression that slangasek feels strongly about this topic.
[15:32] <ogra_> dont work ?
[15:32] <ogra_> :)
[15:32] <cjwatson> jodh: It seems unlikely since the crash was due to dereferencing a pointer into memory that had only *just* been deallocated - I don't think there's any way it could end up overwriting a stat buffer or similar
[15:33] <slangasek> ogra_: my fee for moving sessions during the week is that I will look at you with an evil eye
[15:33] <slangasek> this is a flat rate and not subject to negotiation
[15:33] <ogra_> hahaha
[15:33] <ogra_> k
[15:33] <slangasek> also of note:
[15:33] <infinity> slangasek: Your evil eye tends to be accompanied with a friendly smile, it's rather confusing.
[15:33] <slangasek> this time around we're trying something different in terms of session types
[15:33] <ogra_> infinity, thats what makes it so scary
[15:34] <slangasek> in addition to blueprint sessions, we can also have workshop sessions
[15:34] <slangasek> (workshop/hacking sessions)
[15:34] <ogra_> sweet !
[15:34] <slangasek> and also, presentation sessions
[15:34] <slangasek> SO
[15:34]  * xnox thinks the laser strength shooting from the evil eye will vary in kW 
[15:34]  * ogra_ fells like rolled back 6 years 
[15:34] <ogra_> *before* we started scheduling everything madly
[15:34] <slangasek> for the first one, if you're being asked for blueprints to be added to UDS for the umpteenth time, and are thinking "we don't need another session on that, we just need to sit down and DO it"
[15:35] <slangasek> - then there's a possibility of doing just that.  Let me know and we'll see if scheduling a workshop session instead of a blueprint session makes sense.
[15:35] <infinity> Is there a way to represent that in the LP UI?
[15:35] <infinity> Like, a blueprintless blueprint? :P
[15:36] <infinity> Or do we need to ask someone (like you) to schedule a workshoppy thing?
[15:36] <ogra_> informational ?
[15:36] <infinity> ogra_: Informational would seem to map better to the presentation sessions.
[15:36] <ogra_> indeed
[15:36] <slangasek> and for the second one, if there are topics that you think it would be useful to share with the larger Ubuntu community - like something you'd really like to give as a plenary but there wasn't a slot for - feel free to propose a presentation session
[15:36] <ogra_> but could be abused for it
[15:36] <stgraber> slangasek: is summit actually still reading the participation essential bit from LP? the UI suggests that it only uses LP to check if you want to attend and that you need to poke the track lead to be marked as essential (the UI says "If you feel that your participation is required for this topic, please contact Steve Langasek..."). Not that I have any conflict at the moment, just found it a bit confusing...
[15:36] <slangasek> infinity: you ask a track lead to add it
[15:36] <infinity> slangasek: Check.
[15:37] <slangasek> stgraber: I'm not sure; the summit UI is showing ALL subscribers to ALL sessions with a star.  I'll look into that today and get back to you
[15:37] <infinity> We could nick higlight cjohnston intentionally for once, and ask him.
[15:38] <slangasek> stgraber: http://summit.ubuntu.com/uds-r/attendee_review/21047/foundations-r-prior-release-feedback/ appears to reflect the blueprint P.E. status
[15:38] <infinity> Though he's probably so fed up with people actually wanting cjwatson that he no longer responds.
[15:38] <cjwatson> It happens both ways round ...
[15:39] <stgraber> slangasek: ok. I also got one case where I had to manually subscribe on summit as even though I was subscribed on LP it wouldn't show it on summit. But as I said, no conflict so far, so I'll start pinging people if a conflict shows up...
[15:39] <slangasek> stgraber: so there appears to be an additional flippy bit that I have access to, to make people "required" as opposed to "very interested in attending"
[15:39] <slangasek> but I'm hoping they aren't making me set that for every single person who's required to be in a session, because that would be horrid and non-scalable
[15:40] <slangasek> [TOPIC] AOB
[15:40] <slangasek> any other topics burning a hole in the pockets of your minds?
[15:40] <infinity> slangasek: Ugh.  So, essential isn't actually essential?
[15:41] <infinity> "Please mark me super-duper-essential"?
[15:41] <slangasek> infinity: I don't know.  There's a perception on the part of other track leads that the launchpad field has been abused by people who aren't essential, which has never been my experience
[15:41] <slangasek> so it may be that the scheduler has two different levels now
[15:41] <slangasek> "try to schedule around this person" vs "require this person"
[15:41] <doko> so do we open the archive in any case tomorrow?
[15:42] <doko> regardless of any missing stuff?
[15:42] <slangasek> I'll try to get clarification.  But needless to say, I'm not going to go through by hand and edit status fields one by one for every one of you on summit. :P
[15:42] <cjwatson> doko: I don't think the "force everything into -proposed" stuff is going to have quite landed by then
[15:42] <infinity> slangasek: But that sounds like oodles of fun.  OODLES.
[15:42] <cjwatson> And we're so close by now, and that will make so much difference, that I'm not willing to open without that at this point
[15:43] <doko> ahh, ok.
[15:43] <cjwatson> My database patch is second in the queue, so that won't land until at least tomorrow morning (if I'm lucky)
[15:43] <doko> cjwatson, do you expect to happen his during UDS?
[15:43] <cjwatson> My code patch hasn't yet been completely reviewed, although I've had some comments
[15:44] <cjwatson> Then it needs to go through EC2 (~4 hours, strictly after the DB patch lands), buildbot (~40 mins), QA (not too arduous), and be deployed
[15:44] <cjwatson> Subject to review, it should be possible to get it all done before UDS
[15:44] <infinity> cjwatson: ndt or fdt?
[15:45] <cjwatson> infinity: fdt for the db patch, ndt for code
[15:45] <cjwatson> [fastdowntime / nodowntime]
[15:45] <infinity> Yeah, Friday sounds reasonable then.
[15:45] <doko> ok, I think, I'll send an email about when to expect the opening. will send you the draft
[15:46] <cjwatson> I thought I kind of covered that with my -devel mail earlier
[15:46] <cjwatson> But as you like
[15:48] <slangasek> ok - anything else?
[15:50] <slangasek> #endmeeting
[15:50] <meetingology> Meeting ended Wed Oct 24 15:50:20 2012 UTC.
[15:50] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-24-15.02.moin.txt
[15:50] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-24-15.02.html
[15:50] <slangasek> the end
[15:50] <slangasek> thanks all
[15:50] <ogra_> thanks slangasek !
[15:50] <xnox> cheers.
[15:50]  * ogra_ finally starts the break he tires to have since 9h
[15:50] <ev> thanks!
[15:50] <infinity> ogra_: That'll be one hell of a tasty coffee.
[15:51] <infinity> ogra_: Or awfully stale, if you brewed it 9h ago.
[15:51] <ogra_> haha
[15:51] <ogra_> no, i dont count making coffee as break
[15:51] <ogra_> its a button press and 30sec waiting
[15:52] <stgraber> thanks!
[15:52] <ogra_> its just that every time i tried to start that break something occured that didnt let me leave my desktop
[15:53]  * cjwatson sends ogra_ some really good kitten pictures
[16:03] <cjohnston> infinity: that doesn't sound like much fun, but whats up
[16:04] <infinity> cjohnston: Hah.  A bit late.  We were just ruminating about how marking people essential to sessions does or doesn't work these days.
[16:05] <infinity> cjohnston: slangasek seems to have discovered that it doesn't DTRT without individually setting a "no, I really mean it" flag, which is pretty unscalable.
[16:05] <cjohnston> I know.. was trying to get out the door.for the airport
[16:06] <cjohnston> agreed.. but so was allowing everyone to mark required as they want
[16:06] <bootlkjkgf> http://i599.photobucket.com/albums/tt71/Pittsburghistan/xb9yt0jpg-1.gif
[16:08] <cjohnston> we need a better algorithm for scheduling
[16:21] <ogra_> cjwatson, LOL !