/srv/irclogs.ubuntu.com/2014/03/06/#ubuntu-meeting.txt

=== nudtrobert_ is now known as nudtrobert
=== hyperair is now known as minefield
=== minefield is now known as hyperair
=== smb` is now known as smb
=== Ursinha is now known as Ursinha-afk
* slangasek waves16:02
=== Ursinha-afk is now known as Ursinha
jodho/16:03
slangasek#startmeeting16:05
meetingologyMeeting started Thu Mar  6 16:06:00 2014 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:05
meetingologyAvailable commands: action commands idea info link nick16:05
slangasek[TOPIC] Lightning round16:06
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
slangasek$ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox stokachu)16:06
slangasekbdmurray slangasek barry doko stokachu cjwatson xnox stgraber jodh16:06
dokoslangasek, should you inject infinity into this shuffle?16:07
slangasekoh oops16:08
slangasek$ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox stokachu infinity)16:08
slangasekjodh barry slangasek doko bdmurray infinity stokachu cjwatson xnox stgraber16:08
xnoxoh, meeting16:08
slangasekand... I still have stokachu in there, so s/stokachu/caribou/, not that he's here :)16:08
slangasekyes, quickly quickly16:08
jodh* foundations-1305-upstart-work-items:16:08
jodh  - async tests have uncovered a race that needs to be resolved by16:08
jodh    reworking the state machine. Plan is to have a mini-sprint with16:08
jodh    xnox+cjwatson to work on this next week.16:08
jodh* upstart:16:08
jodh  - fixed bug 1288243.16:08
ubottubug 1288243 in upstart "reexec unit test consistently fails: single job producing output across a re-exec" [Undecided,Fix released] https://launchpad.net/bugs/128824316:08
jodh* other:16:08
jodh  - Fixed pbuilder+sbuild dep8 tests running in an lxc container (ppc64el+armhf).16:08
jodh  - Thanks to xnox for the Upstart MP backlog purge!16:08
jodhJ16:09
barryLP: #1284469 / python issue #19021 - trying to get a python 3.4 rc2 package with the Popen.__del__ fix.  currently have some autopkgtest failures so the cherry pick list is probably not complete.  alternatively: convince 3.4 RM to cherry pick the relevant changes into 3.4rc3.16:09
ubottuLaunchpad bug 1284469 in python3.4 (Ubuntu) "Exception on installing/reconfiguring python3" [High,In progress] https://launchpad.net/bugs/128446916:09
barrysystem-image: long q/a meeting about how to do automated tests.  wiki test plan updated.  s-i 2.2 ready for landing silo (along with a new u-d-m).  fixes: LP: #1277589, LP: #1287287, LP: #1250817, LP: #1286542, LP: #1279532, LP: #1287919.16:09
ubottuLaunchpad bug 1277589 in Ubuntu system image "Better protection against concurrent access" [Critical,Fix released] https://launchpad.net/bugs/127758916:09
barrythis week: hopefully returning to autopilot py3 and general py3.4 work.16:09
ubottuLaunchpad bug 1287287 in Ubuntu system image "Remove atomic rename workaround in client" [High,Fix committed] https://launchpad.net/bugs/128728716:09
barrydone16:09
ubottuLaunchpad bug 1250817 in system-image (Ubuntu) "Exceptions in the state machine (D-Bus) should result in UpdateAvailableStatus with an error_reason" [High,In progress] https://launchpad.net/bugs/125081716:09
ubottuLaunchpad bug 1286542 in Ubuntu system image "keyring DuplicateDestinationError when updating from custom s-i server" [Low,Triaged] https://launchpad.net/bugs/128654216:09
ubottuLaunchpad bug 1279532 in Ubuntu system image "Log dir path should be pass to udm to simplify debugging" [Low,Fix committed] https://launchpad.net/bugs/127953216:09
barryslangasek: you're up16:13
slangasek * buried in customer work all week16:13
slangasek * resumes coming in for the Java role; going to give some of these to doko for review, could use more volunteers to help pare these down16:13
slangasek(done)16:13
slangasekdoko:16:13
doko- Linaro Connect16:13
doko- fixing ftbfs16:13
doko- toolchain updates required for AArch64 and powerpc64le16:13
doko- +1 maintenance work16:13
doko- will be offline for the next 12 days, so pestering people to keep up with things while I'm away16:13
doko(done)16:13
bdmurraybug triage of foundations bugs16:14
bdmurrayuploaded ubuntu-release-upgrader with armhf and ppc64el test failure fix16:14
bdmurrayresearch into software-properties test failures and gnupg debian bug 73712816:14
ubottuDebian bug 737128 in gnupg "gpg exits with a fatal error about missing trustdb despite successfully having imported a key" [Normal,Open] http://bugs.debian.org/73712816:14
bdmurrayreported gnupg bug regarding trustdb (issue 1622)16:14
bdmurraytesting of bug 128078216:14
ubottubug 1280782 in ubuntu-release-upgrader (Ubuntu) "Unable to upgrade from 13.10 to 14.04 - tk8.5-lib fails to upgrade to libtk8.5" [High,Triaged] https://launchpad.net/bugs/128078216:14
bdmurrayuploaded an attempt to fix bug 1280782 regarding tk8.5-lib16:14
bdmurraytested bug 1280782 some more and uploaded tcltk-defaults to fix that upgrade issue16:14
bdmurraycommited a fix for ubuntu-release-upgrader bug 1160346 based on a patch from a community member16:14
ubottubug 1160346 in Release Upgrader "do-release-upgrade from Ubuntu 12.04 on Pentium-M fails, breaks system without any warning (This kernel does not support a non-PAE CPU)" [Undecided,New] https://launchpad.net/bugs/116034616:14
bdmurrayuploaded a fix for ubuntu-release-upgrader bug 1285545 based off jibel's patch16:14
ubottubug 1285545 in ubuntu-release-upgrader (Ubuntu Trusty) "P->T server upgrade failure: ubuntu-release-upgrader fails with OSError: [Errno 2] No such file or directory" [High,Fix released] https://launchpad.net/bugs/128554516:14
bdmurrayfixed linux package hook bug when creating duplicate signatures16:14
bdmurraymerge of colin king's kernel oops branch fixing some null pointers and memalloc issues16:14
bdmurrayadded a fix for kerneloops bug 1026300 with his changes16:14
ubottubug 1026300 in kerneloops (Ubuntu) "kerneloops crashed with SIGABRT in __assert_fail_base()" [Medium,Fix released] https://launchpad.net/bugs/102630016:14
bdmurraysubmitted RT regarding installing trusty gdb on the retracers16:14
bdmurraybackported trusty version of gdb to precise and tested it on the apport-retracers in canonistack (success)16:14
bdmurrayfixed an errors.ubuntu.com OOPS16:14
bdmurrayfixed an errors.ubuntu.com OOPS16:15
bdmurraymodified errors to sort OOPS on user page by date they occurred not alphabetically16:15
bdmurraysubmitted RT to have errors updated16:15
bdmurrayfixed errors tool to find a bucket for an instance16:15
bdmurrayworked on modifications to apport to install specific package versions when retracing instead of using the latest16:15
bdmurraytesting / improving whoopsie intergration-tests so we can move to prodstack16:15
bdmurrayreported apport bug 1287460 regarding xdg-open and preferred browsers16:15
ubottubug 1287460 in apport (Ubuntu) "system crash reports not opened with my default browser" [High,New] https://launchpad.net/bugs/128746016:15
bdmurraySRU team work and mentoring of arges16:15
bdmurray⌁done16:15
bdmurraybluetooth magicpad testing (trying to capture kerneloops)16:15
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
slangasekah, we put infinity in the rotation, but he's probably asleep due to Macao :)16:19
slangasekcjohnston:16:19
slangaseker16:19
slangasekcjwatson:16:19
cjwatsonCherry-picked several easy fixes (mostly build/packaging, and bug 1285790) from my libclick work and landed them in click 0.4.16, by way of CI Train practice.16:20
ubottubug 1285790 in click (Ubuntu) "click crashed with BrokenPipeError in run(): [Errno 32] Broken pipe" [Low,Fix released] https://launchpad.net/bugs/128579016:20
cjwatsonPushed libclick out for review.  Went through my own proofreading pass in parallel; found and fixed several bugs.16:20
cjwatsonStarted work on converting some known click clients (upstart-app-launch, unity-scope-click, clickmanager-plugin) to libclick.  Some of this will need library equivalents of "click info" and "click list", so started on those too.16:20
cjwatsonWorked on a branch to expose supported frameworks in libclick.16:20
cjwatsonLanding libclick at the moment.  http://bazaar.launchpad.net/~click-hackers/click/trunk/files/head:/click/tests/ (esp. gimock.py and some test file such as test_hooks.py) if you're interested in the crazy scheme I was talking about last week.16:20
cjwatsonFixed up python-tblib build problems (planning to use this for click later).16:20
cjwatsonMerged gnutls28 security fixes.16:20
cjwatsonAttempted to get ghc/arm64 building, prompted by a thread on ubuntu-devel-discuss; predictably failed.16:20
cjwatsonRooted my phone and set it up to dual-boot Ubuntu, so that I have a test system that doesn't make me want to throw things.16:21
cjwatson..16:21
xnox* python3:16:22
xnox  - unity8, ubuntu-ui-toolkit, ofono, a few more clicks all landed.16:22
xnox  - next up: land phablet-tools py2&3 support16:22
xnox  - next up: continue testing/landing remaining clicks16:22
xnox* touch-x86:16:22
xnox  - worked on fixing up x86 cross toolchain, it still does not build16:22
xnox  with ssp.16:22
xnox* upstart/touch printing:16:22
xnox  - fixed cups socket activation with upstart, it mostly was s/-F/-f/16:22
xnox  in the cups upstart job + correct typos. (both -F/-f mean16:22
xnox  foreground, both change fg variable 0 => 1/-1, most things test for16:22
xnox  !fg, apart from one small portion which closes all passed FDs when16:22
ubottuxnox: I am only a bot, please don't think I'm intelligent :)16:22
xnox  running with -F instead of -f)16:22
xnox  - reviewed a few upstart merge proposals. We should be good for a16:22
xnox  bugfix heavy upstart release.16:22
xnox* aa/+1:16:22
xnox  - disentangled libav8 NBS by fixing a few packages and uploading16:22
xnox  patches to port mplayer to libav9 from gentoo, thus there is little16:22
xnox  removal damage - two small leave packages. (mplayer on the other16:22
xnox  hand has a lot of reverse dependencies).16:22
xnox..16:22
dokox86 cross toolchain?16:23
cjwatsonx86 bionic I guess?16:23
xnoxyes.16:23
dokoahh, ok16:23
dokobased on which 4.x?16:23
cjwatsoncross for small values of cross16:23
xnoxdoko: 4.7, but it compiles bionic libc, somehow with missing symbols required for a working ssp. thus nothing links.16:24
stgraberLXC:16:24
stgraber - Fixed quite a few lxc-ls bugs (nested unpriv containers, stopped containers, dealing with invalid config, ...)16:24
stgraber - Fixed a small bug in the python3-lxc binding (missing exported function).16:24
stgraber - Fixed some more corner cases of lxc-download16:24
stgraber - Code reviews, testing and LXC on Android debugging16:24
stgraber - Preparing for LXC 1.0.1, scheduled for later today16:24
stgraberCGManager support for logind:16:24
stgraber - Got a patch covering all code paths we care about, now I just need to make this actually work...16:24
stgraber - Landing for this will be blocked by the cgmanager MIR and by its own FFe16:24
stgraberNetworking:16:24
stgraber - Re-applied our ifenslave-2.6 delta to the new ifenslave source16:24
stgraber - Started going through some of the bug reports16:25
stgraberSystem-image:16:25
stgraber - Reviewed and merge/rejected all pending MPs for system-image/server16:25
stgraber - Implemented code to rename channels and to create channel redirects (to transition users after a rename)16:25
stgraber - Tested the planned rename of all existing channels to ubuntu-touch/<channel name>16:25
stgraberOther:16:25
stgraber - Did a click landing.16:25
stgraber(DONE)16:25
slangasekok, any questions over status?16:26
slangasek[TOPIC] AOB16:28
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekanything else?16:28
bdmurraycould somebody look at bug 1288171?16:28
ubottubug 1288171 in python-apt (Ubuntu Trusty) "0.9.3 regression: Setting APT::Architecture now downloads wrong indexes" [High,New] https://launchpad.net/bugs/128817116:28
barryi will take a look16:29
xnoxcjwatson: re:click landings what about lp:~xnox/click/chroot-sessions?16:29
cjwatsonqueued :)16:29
barry(it's already on my radar, i.e. browser tab)16:29
cjwatsonI haven't forgotten, just been head-down on libclick16:29
xnoxcjwatson: ack.16:29
cjwatsonnothing else from here16:31
slangasek#endmeeting16:32
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Mar  6 16:32:39 2014 UTC.16:32
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-06-16.06.moin.txt16:32
slangasekthanks, guys!16:32
barrythanks!16:32
jodhthanks!16:32
stgraberthanks!16:34
czajkowskialoha17:00
dholbachhello17:00
YokoZarmorning17:00
czajkowskianyone here from the technical board17:01
czajkowski#startmeeting17:02
meetingologyMeeting started Thu Mar  6 17:02:29 2014 UTC.  The chair is czajkowski. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:02
meetingologyAvailable commands: action commands idea info link nick17:02
dholbachkees, mdeslaur, slangasek, stgraber: around?17:02
czajkowski#topic catch up with the Tech Board.17:02
=== meetingology changed the topic of #ubuntu-meeting to: catch up with the Tech Board.
slangasekdholbach: on the phone, but meaning to be around17:02
mdeslaursure, I'm here17:02
czajkowskislangasek: mdeslaur howdy folks17:03
slangasekheya17:03
mdeslaurhi17:03
czajkowskiSo how are things in the TB going ?17:03
czajkowskicare to give us an update ?17:03
* pitti waves hello17:03
slangasekseems pretty low-key, really17:04
slangaseknot much demand for our services :-)17:04
pittiI joined a few mins late, was there any question to the TB already?17:05
dholbachfor those of you who haven't been around in the last meeting - the CC catches up with governance and community teams as part of our meeting to see how things are going and to have a look at "operations" from a bit of a distance :)17:05
pittiah17:05
dholbachpitti, just generally asking how things have been going :)17:05
pittiwell, we actually skipped the last few meetings due to not having any agenda17:05
pittion the meetings we did have, things are usually going well, the biggest recent hiccup was the late re-election of the TB itself17:05
pittibut the day-to-day business is usually MREs and the like17:06
dholbachso the new TB members have settled in well in their low-key new activity? :)17:06
czajkowskipitti: yes we are sorry about that17:06
pittiit's been a while since we have had a long and difficult technical discussion17:06
pleia2o/17:06
pitticzajkowski: no worries, nobody's fault in particular17:06
czajkowskiand hopefully we won't let it go that late again, the issues there was so many boards expiring at the same time, including the CC.17:06
czajkowskiis it worth having a meeting even when there is a blank agenda so people can catch up17:06
YokoZarpitti: This is perhaps due to the LTS nature of Trusty making all reasonable decisions of this nature done well in advance, yes?17:07
czajkowskidoes the community know they can reach out to the TB ?17:07
pittiwe used to have a lot more topics, but that was in the days when ubuntu was driven a lot more by UDSes and community17:07
dholbachso when there's been long discussions and difficult decisions, how did you feel it generally went?17:07
pittiand also because there is not that much major change going on in the non-phone-y bits17:07
pittiYokoZar: yeah, that too17:07
pittidholbach: as they should go, really; I remember discussions like "should we install binary drivers by default", the OpenSSL vs. GPL debate, etc.17:08
czajkowskipitti: so how do you feel it is driven now considering we have online uds17:08
pittiwe had a thorough discussion, voting, annoucned it to the devel crowd, and there generally hasn't been any negative feedback about those17:08
czajkowskiwhich is great to see17:08
dholbachpitti, sure - I was just wondering if you were happy with that kind of discussions (so no major delays, everyone weighing in, decision making process is sufficiently refined, etc.)17:09
pittidholbach: oh yes; we could have had some speedier discussions for sure, but that's just the nature of timezones and (often) email-based communication, so not much to complain from my side17:09
czajkowskinods17:10
dholbachcool17:10
YokoZarWe put the TB on a 2 year cycle as well as the CC, do you guys feel it's correct for them to be replaced mid-way through an LTS cycle or should we move the elections to, say, just after the next LTS release rather than a few months before?17:10
dholbachI guess that's similar for the CC as well :)17:10
pitticzajkowski: as I said, the desktop/server bits don't have a lot of structural change these days, so nothing that bubbles up to the TB17:10
YokoZar(we had a similar argument ~ the CC itself)17:10
pittiwhat I am missing a bit is to discuss technical architecture of the phone17:10
czajkowskipitti: ah interesting17:11
czajkowskiwhere does that currently take place?17:11
dholbachpitti, do you have an example of what you feel would have warranted a discussion with the TB?17:11
pittithere's the ubuntu-phone@ ML and such17:11
dholbach(just to get an idea)17:11
pittiand most of the design decisions etc. are just fine17:11
pittithe main thing that comes to my mind is that in retrospect we should have discussed how to build the image-based upgrades without breaking /etc/ so hard17:12
czajkowskipitti: so you're saying you agree with them, but you'd like to see the TB perhaps involved more in the discussion or be involved more ?17:12
pleia2pitti: any thoughts from the tb regarding the init system stuff? (mark kind of announced it after debian made their decision "pending community discussion")17:12
pleia2seems like something the tb should have weighed in on first17:12
pittipleia2: ah, I deliberately didn't bring that up -- but yes, that'll most certainly be a bigger discussion that comes in the next cycle :)17:12
* pleia2 troublemaker :)17:13
pittipleia2: well, we will17:13
* pleia2 nods17:13
dholbachto be fair, Mark said "I will ask the Ubuntu tech board (many of whom do not work for Canonical) to review the position" :)17:14
pleia2yeah17:14
pitticzajkowski: yes, but this is the main issue I have really; and it's always easy to say in hindsight "we should have discussed that more", but not that easy to plan in advance17:14
dholbachbut yeah :)17:14
pitticzajkowski: so I don't want to stress that too much really; but I think we need a version 2 of that, and thus maybe the TB is a good forum to discuss that new design17:15
pittibut yeah, in general I think it's working ok17:15
czajkowskipitti: I agree17:15
czajkowskiso perhaps this is something we can raise and see if we can drive some discussion over to yo folks to get your experience in17:15
dholbachhow much of the discussion happens on the mailing list and how much in meetings? do non-TB members weigh in as well?17:15
czajkowskiand ask dholbach pointed out sabdfl did  say he would ask the TB17:16
pittipleia2: I'm sure cjwatson and slangasek have a super-huge desire to discuss upstart vs. systemd soon :-) (it's not like they wasted many months of their lifetime thinking about it already..)17:16
mdeslaurhehe17:16
pleia2pitti: yeah, I followed the debian discussions17:16
pittidholbach: historically, most in meetings due to the synchronous nature17:16
pittidholbach: these days, small things like MRE requests or the LTS lifetimes are happening mostly over email as that's more practical17:17
pittidholbach: and yes, we have non-TB members posting to the list17:17
dholbachyeah, that makes perfect sense17:17
cjwatsonpitti: it's on the vUDS schedule I believe17:17
pitticjwatson: ah, "fun" :)17:17
pleia2cjwatson: ah, great17:17
sabdflhi all, sorry to be late17:18
dholbachso it sounds like the TB processes are well-oiled machinery... is there anything which has been on your collective minds to be changed at some stage? or things which have repeatedly been put on the backburner?17:19
* pitti scratches head, nothing comes to my mind from the last 2 years really17:19
dholbacheven better :)17:19
YokoZarI'll reraise my question from earlier, as I believe it got skipped: We put the TB on a 2 year cycle as well as the CC, do you guys feel it's correct for them to be replaced mid-way through an LTS cycle or should we move the elections to, say, just after the next LTS release rather than a few months before?17:19
pittiI think the OpenSSL vs. GPL debate came up several times17:19
pleia2oh, so the CC kept having meetings that had no agenda for a while, which is when we started doing these check-ins, I wonder if something similar might be useful for TB and dev teams?17:20
slangasekYokoZar: I have no strong opinion on this... more important is to not leave a gap, as we did last fall17:20
pittiYokoZar: ah, I didn't think that was aimed at TB; as the elections were supposed to happen much much earlier, it would have even been during saucy I believe17:20
YokoZarRight around saucy release17:21
YokoZarwas original schedule I think17:21
pleia2yeah17:21
pittiYokoZar: I actually think it's quite a good time, as traditionally during the LTS cycles there's not that much to decide17:21
YokoZarpitti: hypothetically, though, if we replace the entire board it might make a bunch of new decisions17:22
czajkowskipitti: thanks for the udpate this has been great to her and nice to see a healthy TB17:22
czajkowskipleia2: indeed and I wondered if doing somehting similar for the TB would be useful for them to get to have more discussion here17:22
czajkowskiYokoZar: same could be said for any board at any given time tbh17:23
pittiYokoZar: yes, but that could happen at any point?17:23
YokoZarczajkowski: pitti: for sure, but would it be "less bad" after an LTS rather than before?17:23
pittiso yes, if we elect a board that makes silly decisions, something went wrong before that17:23
pittiYokoZar: yes, perhaps17:23
dholbachdid anyone see pleia2's question? I personally think it might be worth trying17:23
pittiYokoZar: but then a new board would actually be thrown into a time when there's potentially many discussions to make, which might be more overwhelming for new members?17:24
czajkowskipitti: mdeslaur slangasek how about whe you've  a blank agenda, still having a meeting17:24
czajkowskiso people can see a discussion and join17:24
czajkowskiwe've started doing this and it's been very useful17:24
mdeslaurthat's what we've done so far17:24
YokoZarNot sure how frequent it is for "lay folk" to pop into TB meetings and raise an issue, but it does happen with CC meetings from time to time17:25
czajkowskior you could arrange a catch up wth groups the tb has an interst in17:25
pittiwe usually do17:25
pittiwait a bit17:25
pittithen say "nothing to discuss" and end it again17:25
pittiYokoZar: it does happen quite often; in fact that's the norm, as these days the TB rarely raises issues by themselves17:25
pittii. e. someone adds an agenda item and then usually appears in the meeting17:25
dholbachgreat - as others have said... I'm quite happy with how the TB is working - I'm done with questions :)17:26
dholbachkeep up the good work everyone! :)17:26
YokoZarpitti: so perhaps around a time when it's too late to reasonably change things in the LTS cycle, but before hecticness of post-release.  Like around the next UDS we're having.17:26
pleia2thanks pitti :)17:26
YokoZarWhat if elections were considerably before terms starting?17:26
pittiYokoZar: yeah, sounds good17:26
YokoZarLike we vote around now, and incoming members start their term after LTS release17:27
pittiYokoZar: I don't like that very much, I must say; I think it's good for the old board to have a last meeting after the election to hand over, but not much more17:27
pittibut I don't have a strong opinion on that17:27
YokoZarRelatedly, I am encouraged by the lack of strong opinions regarding our election rules, it means our politics aren't particularly "politics" ;)17:28
czajkowskiany other questions folks before we wrap up17:28
* sabdfl is still reading the scrollback17:28
pittiYokoZar: or that things are mostly going well and all that's left to do is finetuning :)17:28
czajkowskiYokoZar: you just like running polls! admit it :P17:28
YokoZarThis is not an "admission" any more than one confesses to liking the sunrise17:30
pleia2hehe17:30
sabdflregarding init17:32
sabdflif the TB has a strong opinion different to the broad roadmap of "adopting systemd on an appropriate schedule" then i'm very open to hearing it17:32
pittisabdfl: probably the wrong place here, but FWIW, I agree to you17:33
pittisabdfl: seeing how much recent action there is in Debian towards adding native systemd packagse to stuff, I think in a year or so we'll have this robust enough17:33
pittisabdfl: with RHEL7 moving to systemd the server world ought to catch up quickly17:34
sabdflmy commentary was not to subvert the TB, but to express that there is no ideological attachment to code that 'belongs' to Canonical17:34
pittithe desktop world pretty much worked two years ago already, but our concern was the server back then17:34
sabdflwe'll move where works best, and i trust the TB to map that out17:34
pittiso for me it's not a question of "if", but "when/how"17:34
YokoZarSo, not understanding much of ubuntu-phone, how specific are the phone-related technical decisions that we can expect in the future?17:35
pittias long-term it seems much better to follow Debian than eternally diverging17:35
pittiYokoZar: they are actually meant to become less and less phone specific over time17:35
pittiYokoZar: "convergence"17:35
slangasekpitti: I don't believe that RHEL7 is doing anything that we'll significantly be able to leverage; too much of this is integration work which doesn't translate17:35
slangasekbut I'm not sure the CC meeting is the place to have this discussion :)17:36
pittiYokoZar: i. e. the phone is by and large a playground (excuse the wording, sabdfl) for trying out new technology like upgrades or display server17:36
pittiwithout the need for backwards compat17:36
YokoZarYes, I imagined that was the eventual goal of any reasonable implementation.17:36
YokoZarI would hope phone would soon be "absorbed" into the rest of Ubuntu governance smoothly17:36
pittiYokoZar: yes, AFAIUI that's the plan17:36
sabdflthis was a particularly difficult thing to watch unfold, since in a sense we were never consulted on an issue with major consequences for us, and we're a member of the family17:36
sabdflbut then, some would argue we had great representation at the table, only wearing different hats17:36
sabdflnothing more from me, thanks TB for checking in17:36
pittithe phone has laid a lot of new approaches to both technology (like Mir) and methods (like CI)17:37
YokoZarAnd, say, phone community == ubuntu community and phone tech decisions == ubuntu tech decisions with the same relevant governance17:37
pittiand they are certainly meant to be used on desktop in the future as well17:37
pittiin practice they are still quite separated these days, but I think that's mostly due to the LTS17:38
pittie. g. we can't/shouldn't land things like Mir/Unity 8 now17:38
pittiand likewise can't turn our upgrade mechanics upside down now17:38
czajkowskipitti: I like those honest decisisons where we admit things aren't ready even when we wish they were17:39
YokoZarDo you think the archive itself might continue some of this delta?  I vaguely worry about a future where we have, say, the arm arch for desktop packages have a lot of phone-specific deltas with a separate decision tree from the rest of the distro17:39
czajkowskiany other comments folks before we wrap it up17:40
mdeslaurthere is no archive delta for the phone at the moment17:40
dholbachYokoZar, that sounds like a summary for the work leading up to the next LTS - bringing unity8 to the desktop and making the convergence happen :)17:40
mdeslaurit's just using a different version of unity17:40
pittiYokoZar: yes, it's less along the lines of architecture and more of package selection17:41
pittiunity8-desktop-session-{mir,x11} in trusty :)17:41
pittiI expect that to become the default soon17:41
pittii. e. convergence to make a leap in 14.1017:41
YokoZarmdeslaur: Right, and perhaps if we do convergence especially "wrong" in the future we might have different versions of a lot of things on phone vs desktop17:41
pittisabdfl: btw, any chance we can get the u name before the release? it's needed in a couple of places, and last time we had to do a number of SRUs due to that17:42
YokoZarugh17:42
YokoZarI'll follow up with him (he left)17:42
YokoZarThough17:42
YokoZarI have hounded him with that question before17:42
pittiah17:42
YokoZarI suspect hearing it from the TB as well might help17:42
czajkowskiok thanks folks17:43
dholbachthanks a lot everyone!17:43
mdeslaurthanks!17:43
pittithanks everyone!17:43
YokoZarMark WILL delay the full name as long as possible for marketing/other purposes though17:43
YokoZarThank you folks17:43
dholbachDo we have any other business?17:44
czajkowski#action YokoZar Mail Mark re  U name for the TB to use for opening up next release17:44
meetingologyACTION: YokoZar Mail Mark re  U name for the TB to use for opening up next release17:44
czajkowski#endmeeting17:44
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Mar  6 17:44:44 2014 UTC.17:44
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-06-17.02.moin.txt17:44
dholbachthanks czajkowski17:45
slangasekthanks :)17:46
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
roadmrjuuust waiting for the precise package to actually be published21:58
spineau1no meeting today? :-(22:04
=== spineau1 is now known as spineau
spineauhggdh: hello, no meeting today?22:06
spineauPabloRubianes: hello, no membership meeting today?22:09
PabloRubianesspineau, I don't see other members from the board22:09
PabloRubianes:S22:09
PabloRubianeschecking22:09
cjohnston!rmb22:11
ubottucjohnston, cyphermox, Destine, ejat,  hggdh, IdleOne, iulian, micahg,  Pendulum, PabloRubienes, freeflying, jared, s-fox, amachu, and chilicuil. Meeting time.22:11
PabloRubianescjohnston, there's no quorum :S22:14
cjohnstonnope22:15
roadmr:(22:15
* spineau will go to bed a bit sad22:15
* toddy gives spineau a cookie22:17
hggdho/22:18
hggdhsorry, on a meeting up to now22:18
pleia2I can pitch in if you need a 4th22:20
IdleOneI'm also here22:20
IdleOnethat makes 522:20
pleia2oh good, no need for me :)22:20
spineauand I'm still here :)22:20
hggdh:-)22:20
IdleOnesomeone sit on the chair and get this started22:20
roadmr\o/22:20
hggdhok22:21
spineauhey hggdh22:21
hggdh#startmeeting Ubuntu membership Board22:21
meetingologyMeeting started Thu Mar  6 22:21:24 2014 UTC.  The chair is hggdh. Information about MeetBot at http://wiki.ubuntu.com/meetingology.22:21
meetingologyAvailable commands: action commands idea info link nick22:21
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu membership Board Meeting | Current topic:
hggdhspineau: long time :-)22:21
spineauhggdh: indeed, 2010?22:21
hggdhOK. We are now on the meeting. We will go by the order in the wiki.22:22
hggdhthe first one is ...22:22
hggdhrohsigma. Is he online?22:23
hggdhactually, rhosigma22:23
hggdhno...22:23
hggdh#topic -- spineau for Ubuntu Member22:24
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu membership Board Meeting | Current topic: -- spineau for Ubuntu Member
hggdhspineau: please go ahead and introduce yourself22:24
spineauok22:24
spineauHello, I'm Sylvain Pineau (Wiki: https://wiki.ubuntu.com/SylvainPineau, LP: https://launchpad.net/~sylvain-pineau)22:24
spineauI live in France and I'm working for the Hardware Certification Team at Canonical22:24
spineauMy main focus is QA automation for Ubuntu, I'm one of the core developper of Checkbox, the system testing application that we have on the CD since 2008.22:24
spineauI led a vUDS session last November to share the Checkbox roadmap for Trusty.22:24
spineauI'm also an upstream maintainer of several Checkbox dependencies in Debian22:24
spineauI contribute to kernel SRU testing and made various contributions to other test frameworks used by the community.22:25
hggdhI see you have some testimonials :-)22:26
spineauhggdh: indeed, and roadmr accepted to be online with uq22:26
spineauus22:26
* roadmr waves - here to support spineau22:26
hggdhroadmr: hi, I see you :-)22:27
hggdhI have no questions for you -- I know your work...22:27
spineauI didn't mention UEC ;-)22:27
IdleOneGo ahead and mention it a little22:28
hggdh#voters IdleOne hggdh cjohnston PabloRubianes22:28
meetingologyCurrent voters: IdleOne PabloRubianes cjohnston hggdh22:28
spineauUEC was Ubuntu Enterprise Cloud, I wrote some tests for it22:29
hggdhyeah. UEC was fun regarding tests...22:29
spineauit was using eucalyptus before we decided to use openstack22:29
cjohnstonspineau: do you do anything with a LoCo team or anything else? All I see on your wiki appears to be related to what you do for your job22:30
spineaucjohnston: I'm not involved with a French loco team, I'm too far from Paris TBH22:30
spineaucjohnston: I attended to some Perl Mongers meetings but that's  unrelated to ubuntu22:31
spineauUsually my main way to contribute is via triaging or via IRC22:33
IdleOneHow do you contribute via IRC specifically?22:33
spineauIdleOne: answering/asking questions22:34
spineauIdleOne: we created #checkbox to help people who wants to start using the checkbox toolset22:35
spineauon freenode22:35
hggdhspineau: anything more to add on community involvement?22:36
hggdhotherwise, time to vote22:37
hggdh#vote on spineau for Ubuntu member22:37
meetingologyPlease vote on: on spineau for Ubuntu member22:37
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)22:37
spineauhggdh: I provided QA support to other test frameworks over the past years22:37
IdleOne+022:38
meetingology+0 received from IdleOne22:38
spineauhggdh: outside of myu role at canonical22:38
PabloRubianes+022:38
meetingology+0 received from PabloRubianes22:38
cjohnston+0 I'd like to see my community involvement22:38
meetingology+0 I'd like to see my community involvement received from cjohnston22:38
IdleOnes/my/more/22:38
hggdh+1 -- I *know* you, so the plus one. But we need to see more community involvement22:38
meetingology+1 -- I *know* you, so the plus one. But we need to see more community involvement received from hggdh22:38
hggdh#endvote22:39
meetingologyVoting ended on: on spineau for Ubuntu member22:39
meetingologyVotes for:1 Votes against:0 Abstentions:322:39
meetingologyMotion carried22:39
cjohnstonIdleOne: ya.. that too22:39
hggdhspineau: unfortunately, I think the lack of visible community involvement was it.22:39
hggdhspineau: may I suggest you to beef up the wiki with more community work, and then reapply?22:40
spineauhggdh: I will, thank you22:40
IdleOnespineau: thank you. I hope to see you back in a few months22:41
hggdhspineau: please do no give up. I would be proud to have you as a member.22:41
hggdhso. Keeping on22:41
spineauok, again thank you for your time22:42
hggdhsince rhosigma is not online, I think this is it for this meeting.22:42
hggdh#endmeeting22:42
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Mar  6 22:42:23 2014 UTC.22:42
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-06-22.21.moin.txt22:42
cjohnstonThanks spineau and hggdh22:42
IdleOnepleia2: you still there?22:43
pleia2mhmm22:44
IdleOnedid you receive that invite to the rmb channel?22:45
pleia2yes, but it got lost in my status window that I never look at :)22:45
IdleOnelol, look at it please. we need some clarification22:45
IdleOneAlanBell: Does meetingology have a #command that allows the chair to set a required positive total for a motion to be considered as carried?23:08
=== emma_ is now known as emma
IdleOneoh it does23:13
IdleOne#votesrequired23:13
pleia2ah, nice :)23:13
* pleia2 learned something new23:13
IdleOneok so CC we need some help with that email I sent23:14
IdleOne:)23:14
IdleOnehmm, that doesn't do exactly what I thought it did23:15
IdleOnethat sets the number of votes needed for a vote to be consider "voted on"23:15

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!