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

=== PaulW2U is now known as G4MBY
=== vladk|offline is now known as vladk
=== ikonia_ is now known as ikonia
=== Ursinha is now known as Ursinha-afk
=== doko__ is now known as doko
=== vladk is now known as vladk|offline
=== Ursinha-afk is now known as Ursinha
cjwatsonhi folks15:01
cjwatson#startmeeting15:01
jodho/15:01
* mvo waves15:01
bhueyhey15:01
infinity\o/15:02
* stgraber waves15:02
cjwatsonone sec, was trying and failing to prepare a demo in time for the meeting :)15:03
* barry wavers15:03
cjwatsonlet's see, slangasek, sil2100, and doko are out, did I miss anyone?15:03
infinityI'm not here either.15:03
cjwatsonSure15:03
cjwatsonYour invisible paint is wearing off15:04
* infinity furiously applies another coat.15:04
cjwatson$ echo $(shuf -e barry stgraber jodh bdmurray cjwatson xnox caribou infinity mvo bhuey robru)15:04
* bhuey aims his Ghost Busters ray at infinity 15:04
cjwatsoncaribou jodh mvo xnox robru bhuey barry cjwatson infinity bdmurray stgraber15:04
cjwatson#topic Lightning round15:04
cjwatsonoh the bot is dead, whatevers15:04
caribouoh, I get to go first !15:04
bhueyruvly15:05
caribou* Qemu/KVM crash analysis : identified potential kernel mismatch15:05
caribou* Finished implementation of networked kernel crash dump. PPA available15:05
caribou* Backport of latest CVE to openssl 0.9.8 for precise15:05
caribou* Prepare SRU for MVO's backport of apt https fixes15:05
caribou(done)15:05
jodh* foundations-1305-upstart-work-items:15:05
jodh  - cgroup+async support: debugging state transitions and a race.15:05
jodh15:05
* jodh is the anti-ev :)15:06
mvohihi15:06
mvoHWE-End-of-Life:15:06
mvo- status meeting and meeting with jibel15:06
mvo- Debug/fix update-motd display issue15:06
mvo- Fix i18n issue, use localized dates, fix bug in update-support-status with fr\15:06
mvoench locale, new version for the PPA15:06
mvo- Optimize the speed (from 2s to 0.2s :)15:06
mvo- Review/sponsor #1328266 uploads15:06
mvo- Testing15:06
mvoapt:15:06
mvo- CVE-2014-047815:06
mvo- add hashtable stats to apt-cache stats/increase size15:06
ubottuAPT before 1.0.4 does not properly validate source packages, which allows man-in-the-middle attackers to download and install Trojan horse packages by removing the Release signature. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0478)15:06
mvo- Fix autopkgtest failure in utopic15:06
mvo- backport apt-ftparchive srccachedb feature to trusty-proposed and add fixes for #1274466, #132439915:06
mvo- work on debian/experimental ABI break branch for utopic15:06
mvoaptdaemon:15:06
mvo- Debug/fix autopkgtest failure15:06
mvoclick:15:06
mvo- lp:~mvo/click/chroot-tests (improve coverage for chroot.py)15:06
mvo- lp:~mvo/click/lp1324853 (get manifest from file)15:06
mvo- lp:~mvo/click/more-tests3 (integration tests for buildsource, pkgdir,15:06
mvo  framework)15:06
mvo- Work with seb on click for the desktop15:06
mvopython-apt:15:06
mvo- implement some suggestions from didrocks (thanks!)15:06
mvo- investigate landscape issue due to libapt changes15:06
mvomisc:15:06
mvo- patch pilot15:07
mvo- merge/upload lp:~mvo/update-notifier/use-apt-helper15:07
mvo(done)15:07
* mvo is not a anti-ev15:07
barrymvo: maybe the ant-y-ev or auntie-ev?15:07
infinitymvo: It filled more than a screenful, you're the new ev.  Deal with it.15:07
mvoinfinity: next thing is that you ask me how many shoes I have15:08
stgraberinfinity: sorta, mvo needs to learn to make longer sentences, then he'll officially be the ev replacement :)15:08
robruit all fit on my screen, what are y'all doing this meeting on your phones or something?15:08
bhueywhat's ev ?15:08
stgraberbhuey: former colleague of ours15:08
cjwatsonEvan Dandrea, used to work for foundations, notorious for extremely verbose reports15:08
infinitybhuey: Evan Dandrea, used to write novels for status updates.15:08
stgraberbhuey: s/colleague/teammate/15:08
barryloquacious15:09
cjwatson(now CI manager)15:09
infinityxnox: *poke*15:09
cjwatsonActually isn't xnox out too?15:09
stgraberhe's not on mumble, which is unusual, so I guess he's out yeah15:09
infinityOh, maybe.  People should learn to not join #-meeting unless they have a meeting.  Mashocists.15:09
bhueyyeah I met him15:09
cjwatsonhttp://irclogs.ubuntu.com/2014/06/12/%23ubuntu-meeting.txt:[15:24] <xnox>   - I'll be away most of next week. Flying out to Portland on Monday,15:09
cjwatsonhttp://irclogs.ubuntu.com/2014/06/12/%23ubuntu-meeting.txt:[15:24] <xnox>     returning on Thursday. Working on Friday. I should have15:09
cjwatsonhttp://irclogs.ubuntu.com/2014/06/12/%23ubuntu-meeting.txt:[15:24] <xnox>     intermittent internet connectivity throughout.15:09
cjwatsonso robru's turn15:09
robru* misc landings, troubleshooting misc build failures15:10
robru* reviewed packaging for various & sundry landings15:10
robru* progress continues on the CI NonFunctional Testing Web Frontend15:10
robru  - pushed a live demo at http://people.canonical.com/~rbpark/nf/15:10
robru  - fancy graphs and things15:10
infinityWow, how did that 'h' migrate to the left in that word?15:10
cjwatsonwhat's NonFunctional jargon for?  I'm guessing it doesn't mean broken :)15:10
cjwatsonperf testing?15:11
bhueyperf as in kernel perf ?15:11
robrucjwatson, yeah, that, but also any kind of test that isn't defined within the project itself15:11
infinitycjwatson: NonFunctional = Not written in Haskell?15:11
cjwatsonsorry perf as in short for performance rather than the perf tool15:11
stgraber:)15:11
cjwatsoninfinity: hey, I can sort of do functional programming in python with a few contortions :)15:12
robrucjwatson, so, like, this would include systemsettle or glmark or whatever. the kind of testing where there is no real hard pass/fail, but rather where you want to record some kind of number, and only fail if the number represents a serious regression, which can only be determined by comparing it to past results15:12
cjwatsonah, got it, so this would include bootcharts, memory use, etc.15:12
robrucjwatson, yes15:12
mvonice15:12
infinitycjwatson: There's something very wrong with you.15:13
cjwatsonmaybe I could steal you at some point to do that kind of graphing for various +1 maintenance metrics (build failures over time, say)15:13
cjwatsoncould do with some of that to make it easier to explain15:13
cjwatson(https://wiki.ubuntu.com/PlusOneMaintenanceTeam for those missing the jargon here)15:14
bhueyfunctional programming, bah15:14
cjwatsoninfinity: I said can, not do15:14
infinitycjwatson: ITYM https://wiki.ubuntu.com/JuanMaintenance15:14
robrucjwatson, sure. this thing we're making is going to be open to anybody to submit metrics into15:14
* barry wants funk-tional programming15:14
infinitycjwatson: vorlon's contribution to the wiki...15:14
cjwatsonSteve is a sick puppy15:14
bhueybarry: awesome15:14
robrucjwatson, but I'm just drawing pretty graphs, probably best to talk to thomi or fginther about getting your results actually in the system15:14
cjwatsonok15:15
cjwatsonright, bhuey's up I think15:15
bhueyvery sad status report15:15
bhueyLast week15:15
bhuey-experimented with the build environment more to see how all of the openjdk build trees are setup15:15
bhueyThis week15:15
bhuey-was able to track down with the help of the team how to revert an openjdk change and it's history. I was able to create two patches to fix the problem. Both compile now15:15
bhuey-kept compiling changes and kept running into my misunderstandings of how the packaging system builds and the order in which it builds them. I finally resolved them. It was basically a confusion of how the patches from debian/patches/ apply to all of the nest openjdk/ directories.15:16
bhuey-realized that I can use something like make -j12 in an openjdk/ directory so that I don't have to wait for a full build from dpkg-buildpackage15:16
bhuey-follow naming conventions for packaging and then upload it again15:16
bhueyNext week15:16
bhuey-move to a new icedtea 2.5 package. This should go fast as what I've tripped up on I was finally able to bypass.15:16
bhuey-start on TCK configuration. Bother IS for access to that QA machine15:16
bhuey...15:16
bhueydone15:16
infinityWhich QA machine?15:16
barryworking mostly on new "coverage service" dependency porting/packaging.15:16
bhueymove might happen today actually15:16
barrydebuntu: virtualenv bug triaging (debian bug 751233), virtualenv 1.11.6-2, python-chameleon 2.16-1, zope.deprecation 4.1.1 (needs another upload), nose-exclude 0.2.0-3 (debian bug #751990 - need to followup with openstack team), tox 1.7.1-1 (debian bugs #746236 #751193 #751803), zope.testrunner 4.4.3-1 (debian bug #751647), cherrypy3 3.3.0-1 (debian bugs #494342, #751642, #722671), python-venusian 1.0a8-215:17
ubottuDebian bug 751233 in python-virtualenv "missing licenses in debian/copyright" [Serious,Open] http://bugs.debian.org/75123315:17
ubottuDebian bug 751990 in python-nose-exclude "python-nose-exclude: Add Python 3 support" [Normal,Open] http://bugs.debian.org/75199015:17
ubottuDebian bug 746236 in tox "Missing Python3 support" [Important,Fixed] http://bugs.debian.org/74623615:17
ubottuDebian bug 751647 in python3-zope.testrunner "python3-zope.testrunner: Depends on python3.3, which is due to be removed soon" [Important,Fixed] http://bugs.debian.org/75164715:17
barryphone: system-image test debugging.  asyncio experiment.  triaged LP: #127413115:17
ubottuLaunchpad bug 1274131 in Ubuntu system image "UpdatePaused signal always returns percentage=0" [High,Triaged] https://launchpad.net/bugs/127413115:17
barryother: UOS, ci train monkeysheriff, landing team standup15:17
barrydone15:17
bhueyinfinity: albali15:17
cjwatsonTwo weeks of report as I was out for last week's meeting.15:17
cjwatsonUOS.  Main thing for me was the RTM archive plan presentation.15:17
cjwatsonMoved all germinate-related code out of Launchpad proper and into ubuntu-archive-publishing.  Used the opportunity to land parallelisation code, speeding the primary publisher up by a couple of minutes.15:17
cjwatsonAdded support for apt-ftparchive source caching to Launchpad.  We'll need to land and backport an apt SRU to finish this.15:17
cjwatsonOptimised the index generation stage of the PPA publisher, roughly doubling its overall speed.15:17
cjwatsonReviewed William's first couple of branches for the new builder reset protocol needed for scalingstack.15:17
cjwatsonLots more work on livefs-in-LP, which is now finally in the process of landing.15:17
cjwatson - Live demo!  https://dogfood.paddev.net/~ubuntu-cdimage/+livefs/ubuntu/trusty/ubuntu-desktop/+build/215:17
cjwatsonTons of transitional uploads trying to get -proposed a bit less full.15:18
cjwatsonFigured out the Jenkins madness necessary to get click onto the QA dashboard.15:18
cjwatson..15:18
stgraberbhuey: don't you have a CI/QA lab VPN?15:18
cjwatson(that may be the shortest duration between getting a demo going and presenting its URL)15:18
stgraberbhuey: (I just tried and I can get into albali just fine using mine + usual login/password)15:18
mvocjwatson: I uploaded the trusty-proposed sru today so hopefuly you are unblocked soon15:19
bhueystgraber: not that I know of15:19
infinity- Lots of kernel SRU wrangling15:19
infinity- eglibc->glibc migration15:19
infinity- SRU and partner reviews15:19
infinity- Dealing with random PPC stuff15:19
infinity- Shepherd the LibreOffice SRU15:19
infinity- Attempting to maintain sanity15:19
infinity15:19
cjwatsonmvo: yep, I saw it in the queue indeed, that was mostly a note to myself15:19
stgraberbhuey: ok, so sounds like that's what you should be asking IS for (they'll ask for Steve's confirmation)15:19
bhueystgraber: ok I get on that later today15:19
stgraberinfinity: how's that last point going? :)15:20
infinitystgraber: It's a losing battle.15:20
bhueySRU ?15:20
cjwatsonhttps://wiki.ubuntu.com/StableReleaseUpdates15:20
infinitybhuey: Stable Release... What he said.15:20
bhueyok15:20
bdmurraymodified daisy to use a tempfile for the coredump to help with swift errors and log the size of the coredump15:20
bdmurrayupdated daisy to cleanup leftover core files in /tmp/ (LP: #1330247)15:21
ubottuLaunchpad bug 1330247 in Daisy "daisy FE app not cleaning tmp cores" [Critical,Fix released] https://launchpad.net/bugs/133024715:21
bdmurrayworked with thedac regarding swift client exceptions in daisy15:21
bdmurraysubmitted daisy bug 1329427 regarding submitting the same crash15:21
ubottubug 1329427 in Daisy "you can submit the exact same crash multiple times" [High,New] https://launchpad.net/bugs/132942715:21
bdmurrayreported errors bug 1329820 regarding retracer stats for armhf15:21
bdmurraymodified daisy retracers to exit earlier if no oops is found (save time!)15:21
ubottubug 1329820 in Errors "no armhf data in retracers-average-processing-time" [High,New] https://launchpad.net/bugs/132982015:21
cjwatsoni.e. what we need to do in order to manage due diligence for changing stable releases15:21
bdmurraymodified daisy retracers to mark oops that are missing from before the cut over as failed that way it won't continuously retry them15:21
bdmurrayfixed daisy-retracer charm's cronjobs to set MAILTO15:21
bdmurrayinvestigation into and fixing of amqplib IOError from the daisy frontends15:21
bdmurrayinvestigation into building cassandra dpkg version type15:21
bdmurrayresearch into corefiles in swift that don't need to be there (LP: #1331212)15:21
ubottuLaunchpad bug 1331212 in Daisy "more core files in swift than in the retracing queue" [Undecided,New] https://launchpad.net/bugs/133121215:21
bdmurrayensured I have access to DSE-temp cassandra port 9160 for pycassa / lxc-errors15:21
bdmurraysubmitted RT regarding access to neem for OOPS from errors / daisy15:21
bdmurrayupdated errors OOPS page to have a link to the corresponding problem and system pages15:21
bdmurrayirc discussion with seb128 regarding unity8 crashes in the error tracker15:21
bdmurrayreview of stopped phased updates and override of some regressions (they exist in newcassandra)15:21
bdmurraysent email to ubuntu-devel regarding the error tracker changing databases15:21
bdmurrayinvestigation into corrupt crashes on armhf (its stripping of the symbols causing an issue on armhf) LP: #132550315:21
ubottuLaunchpad bug 1325503 in gdb (Ubuntu) "gdb reports 'corrupt stack' on armhf without symbols" [High,Confirmed] https://launchpad.net/bugs/132550315:21
bdmurrayfixed rls-u reports on cranberry15:21
bdmurray✔ done15:21
stgraberShort week, was off on Monday.15:22
stgraber 15:22
stgraberLXC:15:22
stgraber - Released LXC 1.0.4, uploaded to utopic and trusty-propsoed.15:22
stgraber - Processed all outstanding merge proposals and patches on the mailing-list.15:22
stgraber - Looked into yet another container escape exploit (this time working around15:22
stgraber   even our apparmor profile) and sent an e-mail to our lists to clarify the15:22
stgraber   situation and strongly recommend using unprivileged containers.15:22
stgraber - Working on a script to setup Unity8 under LXC, go the creation and15:22
stgraber   configuration part done, just need to add the integration bits with lightdm15:23
stgraber   before I can ship that to the Unity folks.15:23
stgraber - Some planning discussions with LXC upstream and our partners.15:23
stgraber 15:23
stgraberConferences:15:23
stgraber - My talk at LinuxCon North America has finally been accepted15:23
stgraber   (simulating the Internet using unprivileged LXC containers).15:23
stgraber   Been figuring out some of the details now (registration as speaker,15:23
stgraber   scheduling, ...)15:23
stgraber - Submitted a separate talk to the Linux Security Summit15:23
stgraber   (co-hosted with LinuxCon North America) on15:23
stgraber   "Application confinement with user namespaces".15:23
stgraber - Working on draft schedule for the Container hackfest, also co-hosted with15:23
stgraber   LinuxCon North America.15:23
stgraber - Starting to prepare some bits for the Linux Plumbers container mini-summit15:23
stgraber   in October (co-hosted with LinuxCon Europe in Dusseldorf).15:23
stgraber 15:23
stgraberOther:15:23
stgraber - SRU queue reviews.15:23
stgraber - Landing team work.15:23
stgraber - Hopefully finally fixed our longstanding systemd-logind bug. (bug 1309025)15:23
ubottubug 1309025 in systemd (Ubuntu Trusty) "systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL" [High,In progress] https://launchpad.net/bugs/130902515:23
stgraber - Fixed a couple of issues with the system-image server locking mechanism15:23
stgraber   (leading to copy failures).15:23
stgraber - Meeting on Ubuntu Touch image versioning.15:24
stgraber(DONE)15:24
cjwatsonstgraber: unpriv LXC containers seem kinda heavyweight for drawing cat pictures15:24
cjwatson(seriously, let us know if that's going to be videod)15:24
cjwatsonvideoed?15:24
infinitycjwatson: But it's thousands of nodes, each either serving or viewing a cat picture.15:24
infinitycjwatson: Oh, have you not seen his internet yet?  It's fun.15:24
cjwatsonI think I missed it15:24
infinityIt's even more fun when it exposes kernel bugs.15:25
bhueymeory related kernel bugs ?15:25
bhueymemory15:25
infinityIf only it were that simple.15:25
stgrabercjwatson: I did the demo at the cloud sprint, and indeed as infinity mentioned, as a result of this, I found at least 4 new network related kernel bugs15:25
infinityNo, routing tables losing their calm.15:25
infinityAnd other such fun.15:25
stgraberbhuey: nah, memory is fine, neighborhood tables overflowing isn't :)15:25
cjwatson#topic AOB15:26
bhueyyeah Linux kernel reall wasn't designed with LXC in mind15:26
stgraberthen you get fun things like random sendmsg returning EINVAL for no good reason and userspace processes not really liking it :)15:26
cjwatsonSo I think the only thing Steve wanted me to pass on while he's away was another reminder that if you were driving any sessions at UOS, please make sure that the output is captured in work items15:26
bhueystgraber: oh god15:26
cjwatsonso that http://status.ubuntu.com/ubuntu-u/canonical-foundations.html looks a bit less sad15:26
cjwatsonanything else?  going ...15:30
cjwatsongoing ...15:31
=== mhall119_ is now known as mhall119
=== vladk|offline is now known as vladk
infinity*crickets*15:31
cjwatsongone.  thanks all15:32
cjwatson#endmeeting15:32
barrythanks!15:33
mvothanks15:33
stgraberthanks!15:33
caribouthanks15:33
jodhthanks!15:34
* bhuey cries that it's over15:34
slangasekit's ok there'll be another one before you know it15:34
* cjwatson awards bhuey one and a half sarcasm points15:34
* bhuey removes tail call optimizations from all of cjwatson compilers15:35
cjwatsonnow that's just mean15:36
bhueyhahaha15:36
bhueytalk about stack smash15:36
bhueyit's now 'stack smack' talk15:37
* bhuey googles cat picture for cuteness15:37
bhueyok later15:37
bhueythanks15:37
=== vladk is now known as vladk|offline
=== brendand_ is now known as brendand
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
YokoZarHello17:00
mhall119o/17:00
czajkowskialoha17:00
dholbach*\o/*17:00
cprofitthello17:01
czajkowski#startmeeting17:01
czajkowskibah17:01
mhall119um...where's the meeting bot?17:02
czajkowskihiding17:02
czajkowskiin the mean time17:02
mhall119well that's not useful17:02
czajkowskiAGENDA: https://wiki.ubuntu.com/CommunityCouncilAgenda17:03
czajkowskianyone here from the DEsktop team ?17:03
seb128hey17:03
seb128sorry I got sidetracked17:03
seb128czajkowski, thanks for the reminder ;-)17:03
czajkowskinp17:03
czajkowskiseb128: anyone else where today from the desktop team with you?17:03
mhall119welcome seb12817:04
seb128no, it's only me (I think)17:04
czajkowskiok17:04
dholbachhey seb128!17:04
seb128hey dholbach mhall119 ;-)17:04
czajkowskiso this meeting is a chance to catch up with the CC, tell us how things are going anything we need to know and if the CC can help in any way17:04
cprofitthello seb12817:04
seb128hey cprofitt17:04
czajkowskiwe do this for various boards and teams and this year decided to talk with the desktop17:05
czajkowskivery informal so17:05
dholbachhow are you doing? how's life? how are things in desktop land? :)17:05
czajkowskihowdy :)17:05
mhall119dholbach: so many questions17:05
seb128haha17:05
seb128I don't have a specific agenda, that's likely to be boring :p17:05
seb128desktop is doing well, quite busy as usual17:05
mhall119seb128: does the desktop team still have the kind of community involvement it's had it the past?17:06
seb128our channel is quite active, work get done, we are happy with the quality17:06
seb128we try to keep on top of reviews, sponsoring, etc17:06
seb128mhall119, some, less than in the past17:06
mhall119seb128: why do you think there's been a decline?17:06
seb128several reasons17:07
seb128- we hired a part of our most active contributors base17:07
mhall119we seem to do that a lot :)17:07
seb128- we are enough "full timer" to keep on top of things17:07
seb128- we focus more on a "product" with unity, the convergence, etc17:08
seb128I would say that our "contributors" base is still somewhat around, but more focussed on e.g Ubuntu GNOME17:08
mhall119is out contributor on-ramp for those products working to allow those who want to contribute to do so easily?17:08
YokoZarWould you count "keeping up with bug triage" among those things?  I've always had the feeling that the desktop components in particular are just inundated with a big mess of launchpad bugs (though Gnome itself is no different)17:08
dholbachis there a good exchange between the Desktop team and the Ubuntu GNOME team?17:09
YokoZarMore so than basically every other component I mean17:09
seb128hum17:09
seb128mhall119, well, it's the same as it was17:09
seb128we could probably do better with documentation, tagging easy bugs, make "where to start" lists17:10
seb128but we never had been optimal doing that17:10
seb128bug triage... we keep on top of triaging/dealing with important issues mostly17:10
seb128there is lot of poor quality reports and wishlists that don't get lot of action though17:10
seb128but it's nothing new or specific to us17:11
seb128exchange between Desktop and Ubuntu GNOME teams are mostly good yes17:11
seb128Tim is on #ubuntu-desktop and active17:11
seb128there are some frictions on technical details sometimes17:11
seb128but that has to expected since we have somewhat conflicting goals17:11
czajkowskiseb128: what kind ?17:12
seb128we want quality and stability17:12
czajkowskiseb128: are they easy to resolve or ?17:12
seb128they would like to be uptodate17:12
seb128like we used to be17:12
seb128but we don't have the resources to manage uptodate and to stabilize that moving code17:12
dholbachseb128, do you feel that's going better now? things like the settings-daemon fork (for example), should make that better now, right?17:12
seb128dholbach, yes17:12
seb128it's going in the right direction17:12
seb128we still have friction points, but we resolved some and are working on resolving the remaining ones17:13
YokoZarThere was some tension in the past about gnome packages that we had basically forked but hadn't renamed, leading to Gnome in Ubuntu itself having some unity-specific changes that weren't necessarily desired.  Have we more or less handled that tension?17:13
mhall119are we doing well with the messaging around those kinds of forks?17:13
dholbachso you have a list and are slowly working through them?17:13
YokoZardholbach basically repeated my question17:13
YokoZaror said it first rather :P17:13
seb128yes, as you said we "forked" gnome-settings-daemon/gnome-control-center for Unity17:13
seb128named them unity-settings-daemon/unity-control-center17:13
seb128then unpatched the upstream variants17:14
seb128we have less patches on other components17:14
mhall119seb128: are Ubuntu GNOME and upstream GNOME happy with how we're doing that and why?17:14
seb128and where we have, we do try to change the behaviour only under Unity by checking the env17:14
seb128yes they are17:14
seb128it's a good move for everyone17:14
mhall119good to hear :)17:14
seb128so we know what to work on17:15
seb128but as usual, more to do that people doing it17:15
seb128so things take time17:15
seb128like it took us over a cycle to get done with g-s-d/g-c-c17:15
seb128but it's nobody's fault17:15
seb128we could just use more people helping ;-)17:16
dholbachseb128, do you feel that talking a bit more about what needs to get done might help?17:16
seb128I don't know17:16
mhall119is there interest from the community in working on that?  it seems like a necessary evil that nobody really is excited to work on17:16
seb128it's the sort of things you don't know until you try and see results17:16
seb128mhall119, no, not really, it's mostly "boring" work17:17
seb128nothing new, fancy or user visible17:17
seb128just implementation details to sort17:17
mhall119seb128: is it something that can be broken down into small contributions?17:17
seb128some bits can17:18
seb128some others are non-trivial changesets17:18
mhall119having a list of those bits might make it less daunting for somebody to help out17:18
seb128right17:18
dholbachmaybe a UOS like session with a blueprint might help(?)17:18
mhall119or a hackday like core apps do17:18
mhall119either one will take several hours away from somebody who might otherwise be doing the work though17:19
seb128right, that's not a new issue/tradeoff17:19
YokoZarTo be fair we do have plenty of boring tasks the community helps with anyway :P17:19
seb128thanks for pointing it out17:20
mhall119YokoZar: yes, but it's easier to motivate people when the task is interesting :)17:20
seb128I don't think there is lot of new there or to discuss17:20
mhall119seb128: is there anything the CC can do for the desktop team?17:20
czajkowskiseb128: any other issues you want to bring up ?17:21
mhall119any issues we can help resolve or organizational things we can do?17:21
seb128can anyone talk to the DMB about reviewing the application from our libreoffice maintainer who is ongoing for 1.5 years17:21
seb128and waiting for over a cycle with them looking at it17:21
seb128they said they would review it again but it seems like they are too busy to do it17:21
mhall119wow, that's not good, do you have a link to the application?17:21
seb128meanwhile Bjoern is waiting17:22
dholbachwe have a meeting with the DMB coming up next :)17:22
seb128https://wiki.ubuntu.com/BjoernMichaelsen/YourDeveloperApplication17:22
mhall119dholbach: what luck!17:22
czajkowskiseb128: has there been any reason for the delay?17:22
seb128czajkowski, bdrung was working with him, but he got too busy for that17:22
czajkowskibut still 1.5 years seem a bit crazy17:23
seb128and he took him some months before saying that it was stalled, time during which nothing happened17:23
czajkowskithank you for raising this and yes we can look into this17:23
seb128then he sent and email saying it would be better if somebody else would take that17:23
seb128but that got stalled since17:23
dholbachif bdrung is not around for the meeting now, I'm happy to take an action to discuss this17:23
seb128Laney trying to put the topic back17:23
seb128without luck17:23
seb128Laney doesn't want to get involved in that application though17:23
ScottKIt's not like it's 1.5 years without action.17:24
seb128because Bjoern and him work in the same team17:24
seb128no17:24
seb128there has been 2 reviews17:24
czajkowskiseb128: seems fair17:24
seb128and we think the issues got addressed17:24
seb128but now it has been over a cycle where it's pending on the DMB to review the application again17:24
ScottKInternally we've already asked the new DMB members to review his situation.17:24
seb128ScottK, that doesn't seem to happen though17:25
ScottKSo it's about as in progress as it can get.17:25
seb128people say that for over a cycle17:25
seb128not sure I trust it17:25
mhall119ScottK: has that review happened yet? how long ago where they asked?17:25
elfyhi - sorry I'm late17:25
ScottKmhall119: I don't know who has or hasn't looked at the history.17:26
mhall119ScottK: do you know how long ago they were asked to review it?17:27
ScottKI understand the frustration.  Not sure what more I can do.17:27
ScottKI don't recall.  It was recently though.  In the last few weeks.17:27
YokoZarAhh17:27
YokoZarI feel like we may be about to have the same conversation we had with the membership boards17:27
mhall119seb128: you said the application has been worked on, was there an issue before that the DMB asked to get resolved? and if so, has that been resolved now?17:28
seb128Laney wrote an email "maybe we should look at it again" like a month ago, but that didn't trigger lot of reply17:28
seb128bdmurray asked for some details like 3 weeks after that17:28
YokoZarwhereby some sort of more complete "system" for tracking folks in the pipeline is needed17:28
seb128he's the only one that responded so far it seems17:28
dholbachYokoZar, we should probably first find out how many cases like this there are17:28
seb128I don't have access to their mailing list though, I was just Cced on that particular email discussion17:28
ScottKHis situation is pretty unique.17:28
dholbachseb128, it sounds like the CC could try to help revive the discussion17:29
mhall119ScottK: in what way?17:29
czajkowskiScottK: roughly how long does it usually take for an application ?17:29
ScottKUsually just a few weeks.17:29
ScottKHis situation predates my dmb membership.17:30
mhall119ScottK: even with a unique situation, things shouldn't go this long without activity17:30
ScottKNot all activity is visible.17:30
seb128well, they shouldn't go that long with an update to the applicant17:30
mhall119ScottK: shouldn't it be visible to the applicant?17:30
seb128Bjoern is waiting to know what's going on for over a cycle17:30
seb128he basically gave up at this point17:31
mhall119ScottK: even a "we're reviewing it now and have questions about X, Y and Z"17:31
seb128I'm pushing for him because that's ridiculous17:31
ScottKI think a more correct status is that the last time the DMB voted, the answer was still no.  The new DMB members have been asked to review the record to see what their vote would be.17:32
czajkowskiseb128: so at this point we will chase up on things17:32
ScottKNo.17:32
czajkowskiand hopefully have bjorn an update one way or another at least to say it's been looked at17:32
ScottKDMB is a TB delegate AIUI.17:32
czajkowskibut thank you for bringin this to us17:32
mhall119ScottK: ok, so there was a vote, it was just a negative one17:32
ScottKThere have been several.17:32
ScottKAt least two, maybe more.17:32
seb128czajkowski, thanks17:32
mhall119ScottK: where the reasons for the negative vote given to the applicant, and where they resolved before it went up to vote again?17:33
YokoZarThank you both17:33
czajkowskiseb128: np but in future please bring things sooner to us :)17:33
seb128yeah17:33
seb128the application got voted in the past17:33
czajkowskiright so seb128 anything else before we move onto the next catch up17:33
seb128we believe the concerns have been addressed17:33
seb128but it has been stucked for a while now trying to get that re-reviewed17:33
seb128czajkowski, nothing from me no17:33
mhall119dholbach: czajkowski: so do we have an action item for this?17:34
dholbachyes, it's on the trello17:34
czajkowskimhall119: yes follow up with dmb on mail17:34
mhall119excellent17:34
mhall119thanks seb128 and ScottK17:34
dholbachthanks a bunch seb128!17:34
seb128thanks everyone for the discussion ;-)17:35
elfythanks seb12817:35
czajkowskiright so moving on17:35
czajkowskinext item is Catch up with the DMB17:35
czajkowskisorry for no bot :)17:35
czajkowskiso is there anyone here fomr the DMB17:35
elfyother than ScottK :)17:36
ScottKAFAIK, I'm it.17:36
dholbachhow about bdrung, bdmurray, xnox, Laney, micahg, stgraber?17:36
czajkowskiScottK: howdy so how are things in the land of DMB ?17:37
ScottKMostly quiet.17:37
ScottKCommunity involvement in development seems much less than in the past.17:37
czajkowskiScottK: Why is  that ?17:37
ScottKCanonical has organized itself so that not that many of it's people seem to care about upload rights.17:37
dholbach?17:38
ScottKMy guess is that people have pretty much given up on Ubuntu as a community project.17:38
mhall119ScottK: can you elaborate on that a bit?17:38
mhall119what exactly has changed in the organization?17:38
ScottKThe CI train process that's in place lets people upload code to PPAs that after some review gets copied into Ubuntu.17:38
ScottKYou don't need to be an ubuntu-dev to upload to those PPAs, so no incentive.17:39
ScottKOr less anyway.17:39
ScottKThere are some who apply.17:39
dholbachDo you feel that with some encouragement or some discussions this could be changed?17:39
dholbachOthers had to be convinced to apply for upload rights in the past too... :)17:39
mhall119ScottK: my understanding is that the CI process is changing, and that the changes will bring it more into alignment with how things used to be, is that correct?17:39
ScottKmhall119: My understanding is that the technical rights will better match the general archive permissions model, but the CI process will still work pretty much as it does now for individual developers.17:40
mhall119ScottK: also, is it a bad thing that the process for non-devs to get packages and changes into Ubuntu has become easier?17:40
ScottKmhall119: I think it's a bad thing that non-developers who happen to work for Canonical get a back door into the archive.  I'm glad it's being fixed.17:41
YokoZarAre we losing something from this organizational change?  Or is it more the case that Canonical staff who don't apply for developer status weren't doing much other than their canonical job17:41
ScottKGenerally that's all they do.17:42
ScottKThere doesn't seem to be much involvement with the broader community (that I can see).17:42
ScottKOf course a lot of stuff is happening around things like the phone where I don't necessarily see it.17:42
mhall119ScottK: and you think that community contributors are less active because canonical devs can upload through the CI process?17:42
ScottKNo.17:42
ScottKTwo issues.17:42
dholbachThis is not just "Canonical staff", but everyone who contributes to projects which use the CI process.17:42
ScottKdholbach: As a practical matter virtually everyone who uses CI works for Canonical.17:43
dholbachAlso I think it makes sense to mention that there are code reviews being done plus extensive automated testing.17:43
dholbachScottK, there are contributions outside Canonical17:43
ScottKThat's not inconsistent with what I said.17:43
ScottKEither way, bypassing the archive permissions model was a bad choice IMO.17:44
mhall119keeping the topic focused on community developers, are we actually seeing a decine in their involvement and if so what do you think is the primary cause of that decline?17:44
ScottKIt's less a community project than it used to be.17:44
ScottKIt's also less cutting edge.17:45
mhall119ScottK: why do you think the perception is that it's less of a community project?17:45
ScottKBecause it is less of a community project.17:45
mhall119is it because canonical staff are given more access than they had in the past? or have we done something that gives community *less* access?17:45
ScottKI don't think it's just a perception thing.17:45
ScottKCanonical is increasingly taking Ubuntu in it's own direction.17:46
ScottKNo one outside Canonical had any say in Unity, Mir, etc.17:46
dholbachHow? Where do you feel it should be easier to participate?17:47
YokoZarThis sentiment is not new, and ScottK is certainly not alone in it17:47
ScottKMy assumption, and I'm not alone in this, is that eventually things like Kubuntu will become impractical because Ubuntu will be too different from the rest of the FOSS world.17:47
dholbachAre there specific technical discussions to be had, which haven't yet?17:48
mhall119ScottK: so what do you think changed to cause this? or, inversely, what do you think can be changed to correct it?17:48
dholbachOr is this more of a hypothetical concern?17:48
dholbachI think this is an important subject, and we sort of touched upon it in the meeting with the Kubuntu Council.17:48
dholbachBut I feel like we're talking a bit less about DMB subjects now.17:48
mhall119ScottK: FWIW, I see a lot of "I feel it's this way because I see other people feel it's this way", but nothing I can actually change to fix it17:49
dholbachIf there are concrete technical matters which should be discussed, the CC would be happy to help bring the right people to a table.17:49
elfymhall119: that may well be the case - but it doesn't stop that being what people take home17:49
mhall119elfy: I don't disagree, but it's not enough to say there's a problem if we don't know what needs to be fixed17:50
mhall119it's like a bug report that says "Ubuntu's broken"17:51
elfy:)17:51
YokoZarThere have been some prominent "Ubuntu is less on its own" developments recently (eg Systemd)17:51
mhall119dholbach is right though, this is a separate discussion from the DMB catchup itself17:51
dholbachI don't feel like the systemd discussion can be classified as "Ubuntu was on its own".17:51
mhall119I think we should have this discussion though, so maybe we can schedule a time and day for it?17:52
dholbachI don't think that's fair. Nobody can expect a distro to move to a new init system that quickly. Especially if you have something that's well for you.17:52
ScottKI think the reduction in community DMB application is a consequence of this feeling.17:52
ScottKSo it's all DMB related.17:53
mhall119ScottK: I'm not saying it's not a DMB concern, just that it deserves a full hour (at least) on it's own17:53
ScottKI think it is what it is.17:53
mhall119trying to resolve it in a catch-up meeting wouldn't be giving it the attention it deserves17:53
YokoZardholbach: what I mean is that one possible outcome of the systemd/upstart discussion would be that Ubuntu would be the only distro in the world doing upstart while everyone else eventually went to systemd.17:53
YokoZarIf you have another dozen different fundamental differences like that between Ubuntu and rest of FOSSland, non ubuntu-specific projects on Ubuntu become harder.17:53
ScottKIt's not a direction the community picked and it's not a direction the community can change.17:53
dholbachScottK, what can't be changed?17:54
ScottKCanonical moving Ubuntu away from the rest of the FOSS world.17:54
ScottKI can be changed, but not from outside Canonical.17:54
ScottKI/It17:54
mhall119again, I think that if we can identify actual things, we can fix those actual things17:54
YokoZarI think it's worth keeping in mind as a general thing to be wary of, specifics may have to wait for a later time (or meeting)17:55
mhall119YokoZar: +117:55
dholbachIf anyone disagreed with a specific decision by anyone working for Canonical, we have discussion forums for this and it can be brought up with a board like the TB.17:55
YokoZarCatchup meetings are mostly about capturing this general wary sentiment, I'll note.  In that way this has been very helpful.17:55
ScottKdholbach: Not for the things that are sabfl'ed in.17:56
mhall119ScottK: I think it's important not to fall into fatalistic thinking like "It is what it is and it can't be changed", it can always be changed17:56
ScottKmhall119: I didn't say it couldn't be changed.17:56
seb128ScottK, the fact that unity uses Mir doesn't mean the community or Kubuntu or whoever has it forced on them17:56
ScottKFor now, that's true.17:56
dholbachand if there are specific issues, they can be discussed and the CC would be happy to help with those17:57
seb128the fact that it's "for now" is just an assumption that could turn to be false17:57
czajkowskiScottK: do you think the rest of the DMB feels the same17:57
dholbachScottK, do you feel the general operations of the DMB are going fine though?17:57
mhall119ScottK: so we have this channel for the next 3 minutes, are there any other DMB concerns that need to be brought up during this meeting?17:57
=== vladk is now known as vladk|offline
=== Quintasan_ is now known as Quintasan

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