/srv/irclogs.ubuntu.com/2012/05/02/#ubuntu-meeting.txt

=== bdmurray_ is now known as bdmurray
=== SaMe is now known as SergioMeneses
=== smb` is now known as smb
=== Guest77193 is now known as yofel
=== yofel is now known as Guest53016
=== Guest53016 is now known as yofel_
=== lool- is now known as lool
=== Tonio__ is now known as Tonio_
=== ikonia_ is now known as ikonia
=== doko_ is now known as doko
=== chuck_ is now known as zul
kanliotyawn14:12
=== txwikinger2 is now known as txwikinger
* stgraber waves15:02
infinityo/15:02
* xnox high-515:02
evhi15:02
* slangasek waves15:03
* ogra_ shores15:03
slangasek#startmeeting15:03
meetingology`Meeting started Wed May  2 15:03:37 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:03
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 #votesrequired15:03
slangasek[TOPIC] Lightning round15:04
=== meetingology` changed the topic of #ubuntu-meeting to: Lightning round
slangasek$ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox)15:04
slangasekdoko stgraber cjwatson slangasek barry xnox jodh ogra ev infinity bdmurray15:04
slangasek$15:05
ogra_15:05
slangasek£15:05
slangasekdoko: you first :)15:05
doko- gcc updates for quantal15:06
doko- investigate and fix arm biarch builds15:06
doko- may 1st was bank holiday15:06
doko(done)15:06
stgraberWas off Friday and Tuesday:15:06
stgraber- Blueprints15:06
stgraber - Registered community-q-edubuntu, foundations-q-ltsp, foundations-q-iso-tracker and foundations-q-networking15:06
stgraber- Installer15:06
stgraber - Merged some dconf improvements and turned on compositing in the installer.15:06
stgraber - Fixed some netboot bugs and turned on cifs support in casper.15:06
stgraber - Merged os-prober from Debian15:06
stgraber- Release15:06
stgraber - ISO testing15:06
stgraber - Ubuntu/Edubuntu 12.04 release.15:06
stgraber- TODO this week15:06
stgraber - Look for any missing blueprint and register them15:06
stgraber - Continue with merges (currently working on ifupdown)15:06
stgraber - Push some SRUs (nagios-nrpe and ldm are currently on my list)15:06
stgraber(DONE)15:07
cjwatsonRelease sprint.  Nothing went too badly wrong. :-)15:07
cjwatsonOpened quantal and got auto-syncs running.  Some degree of fighting with Launchpad, but less than usual.  Piles of merges.15:07
cjwatsonRemoved the data.tar.xz dpkg Pre-Depends requirement from Launchpad.15:07
cjwatsonSorted out a few specs.15:07
cjwatsonGot a bit carried away with update-manager and ubiquity Python 3 porting.  Lots of dependencies still, and I haven't got much into bytes/unicode data modelling, but making good progress on tests.15:07
cjwatson.15:07
slangasek * upstart in Debian:15:08
slangasek  * prereq patches for lsb, sysvinit, and debhelper are done or pending15:08
slangasek  * hacking on invoke-rc.d to implement the Debian policy proposal (doing what /lib/init/upstart-job does currently)15:08
* infinity nudges Mr Manager.15:08
slangasek  * plymouth patches wanted for mountall, looking at it this week15:08
slangasek * SRUs for multiarch libraries, hdparm, other things15:08
slangasek * fix upgrade issue in libnfsidmap (bug #933870)15:08
ubottuLaunchpad bug 933870 in libnfsidmap (Ubuntu) "libnfsidmap2 fails to install" [High,Fix released] https://launchpad.net/bugs/93387015:08
slangasek * don't restart kdm on eglibc upgrade (bug #985735)15:08
ubottuLaunchpad bug 985735 in eglibc (Ubuntu) "update-manager restarts KDM and interrupts update process" [High,Fix released] https://launchpad.net/bugs/98573515:08
slangasek * help fix upgrade issues with python (bug #986374)15:08
ubottuLaunchpad bug 986374 in python2.7 (Ubuntu) "oneiric->precise upgrade failed: E:Internal Error, Could not early remove python-minimal" [Critical,Fix released] https://launchpad.net/bugs/98637415:08
slangasek * sponsor upstart fixes from James15:08
slangasek * merges merges merges15:08
slangasek * python3 porting: bluez ported (thanks Laney for the upload), gdb breaking my brain15:08
slangasek * UDS planning - get those blueprints in, everybody!15:08
barryslangasek, cjwatson: \o/15:09
* barry assumes slangasek is done...15:10
barry(reporting for last two weeks)  py3 porting status: debian bug 669301 (py3 packaging for python-openssl, should probably temporarily delta this into quantal).  freedesktop bug 48904 (backward compat problem w/ dbus.gobject_service).  worked on packaging for python-mode.el for sid.  released flufl.* packages with updated cheeseshop py3 trove classifiers.  also spent some time on bug 924079 before release, but punted.  reviewed debian bug15:10
barry625509 (debian-python port).  reviewed slangasek's patch for bluez py3.  bug 990145 (remove gwibber dependency on mx.DateTime).  bug 992195 (remove duplicity dependency on GnuPGInterface).  TODO: will be sprinting w/local pythonistas tomorrow on pep 420 (namespace packages for py3.3) and continue with bug 992195.  done.15:10
slangaseker yes, sorry15:10
ubottuDebian bug 669301 in pyopenssl "pyopenssl: Build the Python 3 version of the package" [Wishlist,Open] http://bugs.debian.org/66930115:10
ubottuFreedesktop bug 48904 in python "switching from pygobject2 to pygi in 1.0 was an incompatible change" [Normal,Reopened: ] http://bugzilla.freedesktop.org/show_bug.cgi?id=4890415:10
ubottuLaunchpad bug 924079 in apt (Ubuntu Oneiric) "do-release-upgrade fails to upgrade from Oneiric to Precise: Couldn't configure pre-depend libtinfo5 for libncurses5, probably a dependency cycle" [High,Triaged] https://launchpad.net/bugs/92407915:10
ubottuLaunchpad bug 990145 in Gwibber "Remove dependency on mx.DateTime" [Undecided,New] https://launchpad.net/bugs/99014515:10
ubottuLaunchpad bug 992195 in Duplicity "Remove dependency on GnuPGInterface" [Undecided,In progress] https://launchpad.net/bugs/99219515:10
xnox did hr/new employee procedure tasks, some are still pending15:11
xnox- finished testing lvm2 merge, it got updated in debian,15:11
xnox  remerged, needs further retest15:11
xnox- did one sync request (libgpg-error)15:11
xnox- finishing up merging sudo, should be ready for sponsorship later15:11
xnox- created uds spec, wrt failing hardware notifications15:11
xnox- just did a merge proposal for boost1.49 transition tracker15:11
xnoxNEXT15:11
infinityjodh: You're up, since you were disconnected for the randomizer. ;)15:12
slangasekxnox: I'd like to upload lvm2 .88 now and worry about .95 later, especially since .88 is the most recent version that I know upstream recommends15:12
xnoxslangasek: ok.15:12
slangasekxnox: but I'll test it on my own system first before doing so15:12
slangasekeither way, good to have one of our top packages knocked off of http://qa.ubuntuwire.org/oldmerges/ :)15:13
* ogra_ wonders if there is actually a human being behind the jodh nick :)15:13
* ogra_ just moves forward for now 15:13
ogra_done:15:14
ogra_* more compiz upgrades right before/on release15:14
ogra_* omap, omap4 and ac100 release image tests15:14
ogra_* may 1st was labour day in germany ...15:14
ogra_* packaged the new nvidia tegra armhf driver (sadly very buggy on the ac100 atm (suspiciously looks like the GPU hardlocks15:14
ogra_  after a while, nvidia devs are notified)) (the test package can be found at http://people.canonical.com/~ogra/nvidia-tegra/ atm)15:14
ogra_todo:15:14
ogra_* merges: i only have procps on the list, feel free to drop stuff on me, else i'll randomly grab bits off the list15:14
ogra_* pondering if we shouldnt have a spec for MBR and partition table backup/restore15:14
ogra_  (i know that came up various times in the past but i couldnt find a spec for it)15:14
ogra_UDS:15:14
ogra_registered https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-embedded-rootfs15:14
ogra_registered https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-hwpack-integration15:14
ogra_(done)15:14
slangasekev:15:15
ev- http://errors.ubuntu.com is live, though due to a programming error, things15:15
ev  went down over the weekend. Fortunately, the system is designed to cope with15:16
ev  this and clients resent crashes when it came back up on Monday. We're still15:16
ev  getting things hooked into the webops pager system.15:16
ev- Fixed a few bugs that have arisen in the web side of the crash database15:16
ev  since release.15:16
ev- Fixed a critical bug in apport as version 2.0.1-0ubuntu7. We were directing15:16
ev  people to launchpad.net post-release.15:16
ev- We now have (the start of) a web API for the crash reporting statistics.15:16
ev  This was initially written to provide webops with a means on monitoring the15:16
ev  health of the retracers.15:16
ev- Created the 12.04 USB disks for the store.15:16
ev- As it turns out, 4 i386 and 4 amd64 retracer instances wasn't enough15:16
ev  post-release. Initial testing suggests we could get by with about 16 of15:16
ev  each. We'll also need a lot more disk space, as between the backlog of core15:16
ev  dumps and the per-retracer per-release caches we're quickly eating up the15:16
ev  existing disk. Worked with webops to rememedy the immediate problem. New15:16
ev  hardware is on order.15:16
ev- Registered blueprints for UDS:15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-metrics15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-updates-from-crash-reports15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-fix-ddebs15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-bucketing-improvements15:16
ev  - https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-phased-updates15:16
ev- Worked with Matthew to try to write a better mean time between failures15:16
ev  algorithm. Mathematicians wanted.15:16
ev- Built out support to collect statistics on the release, package, version,15:16
ev  year, month, and day level (and combinations therein).15:16
ev- Started moving the web UI to consuming its own API to generate the charts,15:16
ev  in support of being able to switch chart views via fancy-pants AJAX.15:16
ev- Discussed the http://errors.ubuntu.com design with Matthew, Kate, and Colin.15:16
ev  If you get a chance, I'd love your thoughts in reply to the email I sent15:16
ev  about it on April 13th.15:16
ev(done)15:16
evI'll post some fun stats during AOB15:16
infinityev: When will errors.ubuntu.com be usable by !canonical people (or will it ever?)15:16
infinity- Release sprint last week:15:17
infinity  - 12.04 got released, rather uneventfully15:17
infinity  - 12.10 got opened while no one was looking15:17
infinity- This week:15:17
infinity  - Fixed d-shlibs to deal with the armhf linker15:17
infinity  - Fixed a few bugs in the fpc/armhf bootstrap15:17
infinity  - Worked on fixing some llvm/clang-on-arm issues15:17
infinity  - Rebootstrapped the tex* stack to sort out an15:17
infinity    accidental out-of-order sync that blew up the world15:17
infinity  - Registered and fiddled with spec for UDS.15:17
infinity...15:17
evinfinity: well, I'm not shouting about it from the rooftops yet as the code could use some performance improvements15:17
evand I really, really, really don't want Hacker News hitting it15:17
evjust yet15:17
slangasekev: speaking of retracers, I noticed the backtraces shown in the errors reports don't appear to be a 'bt full' - is there any plan to make this available?15:18
infinityev: Sure, but I mean it's currently behind SSO demanding that you're in the canonical group. :)15:18
slangasekit's relevant often enough that I think we should have it by default15:18
evinfinity: but the game plan is canonical group + bug control being able to access the actual reports15:18
evjust like on launchpad15:18
* infinity nods.15:18
Laneyuse ubuntu-dev instead for now, or bugcontrol?15:19
evslangasek: can you provide me with an example?15:19
evit's definitely not intentional15:19
slangasekev: looking15:20
* bdmurray starts then15:20
bdmurraybug triage of ubiquity, iso-testing and update-manager bug reports15:20
bdmurrayinvestigation into reporters submitting dist-upgrade bugs multiple times15:20
bdmurrayclosed apport-package reports regarding package install failures due to not a debian package15:20
bdmurraywrote a bugbot routine for 'not a debian format archive bug reports'15:20
bdmurrayclosed texinfo bug reports due to a syntax error in /etc/environment15:21
bdmurraywhoopsie apport-package duplicate bug consolidation into bug 98899515:21
bdmurraytried to recreate bug 987956 regarding ubiquity15:21
bdmurraywrote a bug pattern for bug 93754615:21
ubottuLaunchpad bug 988995 in whoopsie-daisy (Ubuntu) "package whoopsie 0.1.32 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1" [Undecided,Confirmed] https://launchpad.net/bugs/98899515:21
ubottuLaunchpad bug 987956 in ubiquity (Ubuntu) "Installer Deletes Contents from Separate HOME partition without WARNING!" [High,Incomplete] https://launchpad.net/bugs/98795615:21
ubottuLaunchpad bug 937546 in nautilus-dropbox (Ubuntu) "package nautilus-dropbox (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2" [Undecided,Invalid] https://launchpad.net/bugs/93754615:21
bdmurrayreported apport bug 989929 regarding checking if a package is an ubuntu package15:21
ubottuLaunchpad bug 989929 in apport (Ubuntu) "does not check ubuntuness of packages being removed or upgraded" [High,Confirmed] https://launchpad.net/bugs/98992915:21
bdmurrayconversion of harvest opportunities from direct launchpad database queries to using the api15:21
bdmurrayblogged regarding duplicate bug title consolidation15:21
bdmurraycreated a list of people who improved bug reports during the precise dev cycle for skaet15:21
bdmurrayinvestigation into remastersys and emailed contact person regarding bug 98427615:21
ubottuLaunchpad bug 984276 in casper (Ubuntu Precise) "installing casper on a non live system causes update-initramfs to fail" [Medium,Confirmed] https://launchpad.net/bugs/98427615:21
bdmurraycreated a launchpad development virtual machine15:21
bdmurraycreated a couple of blueprints for Q15:21
bdmurraydone15:21
slangasekev: "no symbol table info available", so maybe this was a missing debug symbol problem. https://errors.ubuntu.com/oops/008aa98e-92ea-11e1-b399-2c768aafd08c15:21
dokomsg infinity did you give back gcc-4.7? these mysterious give backs become annoying ...15:22
dokooops15:22
slangasekbdmurray: texinfo> can you give us a bug about fixing texinfo to not muck around in /etc/environment where it doesn't belong?15:22
infinitydoko: I did a mass-give-back of the world yesterday, nothing today...15:22
infinitydoko: But that wouldn't have hit PPAs, if your PPA upload is what got given-back.15:23
dokoright15:23
bdmurrayslangasek: yes, will do15:23
slangasekta15:23
slangasekjodh: your turn, if you're around :)15:24
jodh- boot/upstart: - Raised MP on quantal upstart to fix compile error.15:24
jodh- planning/blueprints:15:24
jodh  - discussions around multiseat.15:24
jodh  - service readiness:15:24
jodh    https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-upstart-service-readiness15:24
jodh  - ptrace limitations:15:24
jodh    https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-upstart-overcome-ptrace-limitations15:24
jodh- libs/nih: bug 776532 (required for Upstart quantal work). Wrote tests and15:24
jodh  tested. Approved by Keybuk.15:24
ubottuLaunchpad bug 776532 in libnih "nih_dir_walk_scan passes incorrect value to file filter" [Undecided,Triaged] https://launchpad.net/bugs/77653215:24
jodh- TODO:15:24
jodh  - ConsoleKit+logind investigations + multiseat blueprint with robert_ancell.15:24
jodh  - upstart job disabling blueprint.15:24
jodh  - upstart state passing blueprint.15:24
jodh15:25
* slangasek feels all integrated15:25
* infinity feels dirty15:26
stgraberjodh: can you make sure I'm subscribed to the multiseat blueprint? (I have an interest because of past experience with these and because of LTSP)15:26
jodhstgraber: will do.15:27
slangasekjodh: please also register a general "upstart roadmap" blueprint - we should have that session again just to make sure we're still aligned with what people need15:27
cjwatsonI didn't even know there *was* a quadruple integral operator.15:27
jodhslangasek: ack.15:27
stgraberjodh: thanks15:28
slangasekanyone have questions over the above?15:28
slangasek[TOPIC] UDS blueprints15:30
=== meetingology` changed the topic of #ubuntu-meeting to: UDS blueprints
slangasekso with UDS half a week away, any remaining blueprints you mean to have on the schedule need to get in the system ASAP15:31
slangasektomorrow at the latest15:31
cjwatsonI've got "btrfs sync-up with server team" and "automated bootloader testing" to do from our call yesterday15:31
cjwatsonwill register those today15:31
slangasekand by Friday at the latest, please have a look at what's on the schedule for UDS and get yourself subscribed to the sessions you need to be at15:31
slangasekso that the autoscheduler can do its work over the weekend15:31
slangasekinstead of having it throw conflicts at us Monday :)15:32
slangasekcjwatson: thanks15:32
infinity(For the record, if people have sessions they think I should be at, feel free to subscribe me)15:32
ogra_infinity, do we have an arm v8 spec btw ?15:33
infinityYep.15:33
slangasekI expect that as usual none of you should have any trouble finding things to occupy your time at UDS; but if anyone should happen to feel they don't have enough that they're participating in, let me know15:33
ogra_(assuming it would be yours if it exists)15:33
infinityogra_: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-aarch64-porting15:33
ogra_thx15:33
* ogra_ subscribes15:34
infinityCleverly hidden under the arch name that no one knows.15:34
ogra_hehe15:34
cjwatsonAnyone know if wookey's already planning to set up a quantal sbuild-ma buildd in time for UDS?15:34
slangasekev, bdmurray: incidentally, do you think one session about the crashdb is sufficient? (https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database)15:34
cjwatsonI'd ask him directly but he's not on IRC right now15:34
slangasekhe's on #multiarch@OFTC :)15:35
slangasek(I don't know)15:35
evslangasek: as in should we have foundations-q-crash-database-2?15:35
infinityI was just about to mention he was on oftc. :P15:35
* ogra_ sees him in #linaro15:35
evor are you asking if we should split it out into more specs?15:35
slangasekev: as in, are there subtopics that warrant an hour of their own :)15:35
cjwatsonah, I'll ask him there15:35
evslangasek: I'll give that a think tonight15:36
evit does link to some subtopics15:36
evbut yeah, maybe the mean time between failures is an hour talk itself15:36
slangasekev: if it's simpler we can just block out multiple hours for the umbrella blueprint15:37
evyeah, lets do that15:37
slangasekthough sometimes that just means the first topic takes two hours and you never get to the end of the list ;)15:37
evheh15:37
evI'll still think about how we can further break this down tonight15:37
evbut lets tentatively plan for two hours15:38
slangasekany other concerns about blueprints at the moment?15:38
ogra_any suggestions about hving a blueprint for a partition table and MBR backup restore ?15:38
ogra_*having15:38
ogra_(mentioned in my report above)15:38
slangasekogra_: I wasn't sure I understood the use case for this15:39
ogra_having backups of your partition table in case you falsely change it ?15:39
slangasekwho does that though? :)15:39
ogra_being able to restore a messed up MBR a user fiddled to death15:39
ogra_dunno, i kno win the past having grub do backups on grub-update came up15:40
cjwatsonupdate-grub doesn't touch the partition table or the MBR15:40
ogra_(and we had such discussions for u-boot as well)15:40
cjwatsonYou may be thinking of grub-install15:40
ogra_oh, indeed, wrong term, sorry15:40
slangasekright, and grub-install doesn't get run except at install time15:41
cjwatsonI dunno, it seems like a special case of having good system backups15:41
ogra_k, so its moot15:41
* xnox .oO(UEFI)15:41
slangasekogra_: I suspect we can't justify a session for it - but thanks for bringing it up15:41
ogra_right, might make more sense in context of an advanced backup tool15:41
cjwatson... which we still don't do well15:41
slangasekdo we want system backups on the agenda?15:42
slangasekor would that need to be desktop / server instead of foundations?15:42
evdon't we have deja dup?15:42
evit sometimes manages to back up to u115:42
cjwatsonev: Have you ever tried to do system restores based on duplicity backups?15:42
cjwatsonI have.  It doesn't work.15:42
evcjwatson: yikes15:42
ogra_heh ... sometimes15:42
cjwatson(Among its faults, it stores file ownership by user/group name rather than number, so you can't reliably restore from a live CD without having to spend ages fiddling with permissions afterwards.  It's obviously meant as a single-user backup tool, not a system backup tool.)15:43
cjwatsonslangasek: I suspect nobody has time for it this cycle :-)15:44
slangasekright-o15:44
slangasekmoving on then15:44
slangasek[TOPIC] Bugs15:44
=== meetingology` changed the topic of #ubuntu-meeting to: Bugs
cjwatsonMaybe I should talk to mterry and see if duplicity can be bludgeoned into the right shape, since it's clearly desktop's direction15:44
evcjwatson: noted - my experience with it has been fairly light15:44
* xnox bacula - is ok for system backups15:44
slangasekbdmurray: are there any bugs showing up post-release that we should be worrying about SRUing?15:44
barryduplicity is one of those py3 application ports, so there's even more to bludgeon mterry with :)15:44
slangasek(ones that we aren't already)15:45
* stgraber uses a central backuppc server with rsync for all the Linux systems, works great but not exactly something we can fit in the default install15:45
bdmurrayslangasek: well, I ran across bug 988995 which reminded me of another bug15:45
ubottuLaunchpad bug 988995 in whoopsie-daisy (Ubuntu) "package whoopsie 0.1.32 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1" [Undecided,Confirmed] https://launchpad.net/bugs/98899515:45
bdmurraybug 52389615:46
ubottuLaunchpad bug 523896 in shadow (Ubuntu) "useradd: cannot lock /etc/passwd; try again later." [Medium,Confirmed] https://launchpad.net/bugs/52389615:46
=== duanedes1gn is now known as duanedesign
cjwatsonstgraber: Right, roughly me too, but it's all home-grown15:47
evyeah, I did ask about that in #ubuntu-devel15:47
evI'm not sure what else we can do if /etc/passwd is locked15:47
slangasek523896> the blocker there was that we haven't reached consensus with the upstream yet, so I was reluctant to diverge :/15:47
slangasekev, bdmurray: what's surprising is the large number of reports of it *being* locked, all of a sudden15:48
slangasekWhy should users not be seeing locked /etc/passwd until installing whoopsie?  Is it just that the stale lock has been there for years, but nothing has tried to add a new user on upgrade?15:49
infinityCould be that.15:50
infinityWe don't add new users all that often.15:50
infinityUnless you install something that does so, of course.15:50
cjwatsonQuite a few packages add users; odd that whoopsie would be a particularly common victim15:51
slangasekso unless we think whoopsie is somehow misbehaving and *causing* the lock, the right thing to do is to fix the underlying lock15:51
slangasekcjwatson: quite a few packages in the default desktop install that will add them on upgrade?15:51
cjwatsonI suppose it could be like man-db being victimised by trigger bugs15:51
cjwatsonMaybe not upgrade, no, though whoopsie's surely not the first15:52
cjwatsonWell, first in this case :)15:52
cjwatsonAnyway, I see no relevant misbehaviour in whoopsie.postinst15:52
slangasekyep15:52
slangasekand whoopsie certainly shouldn't be working around the lock if it's not buggily causing it in the first place15:53
slangasekso the thing to do is to get the lock cleared (e.g., at boot)15:53
slangasekcjwatson: any objections to clearing that lock file at boot?15:53
cjwatsonSeems fair15:54
infinitySeems reasonable (ish) to me, if we've confirmed that shadow/passwd inconsistency is avoided in other ways.15:54
slangasekok15:54
slangasekbdmurray: any others?15:54
evhttps://errors.ubuntu.com/ still lists that python-central bug, which has been floating near or at the top since release. Don't know if it's my parsing of the launchpad crash bugs data being broken or if we really still don't have a bug reported for it.15:54
bdmurrayIs that thought that there may be some deliquent package leaving the lock?15:54
evapols for jumping in there15:54
infinityev: doko uploaded a fix, we just need to get it through SRU land.15:55
evhttps://errors.ubuntu.com/oops/00104e3a-9071-11e1-b51d-2c768aafd08c15:55
evah yay15:55
infinityev: And his fix *did* reference a bug, so maybe your matching isn't working?15:55
evwell it will only match apport filed bugs15:55
infinityI think it was.15:55
evokay, I'll have a look then15:55
evI'm sure I'm failing to parse a special character properly15:55
slangasekI thought doko hand-filed the bug15:56
infinityev: https://bugs.launchpad.net/ubuntu/+source/python-central/+bug/95593615:56
ubottuLaunchpad bug 955936 in python-central (Ubuntu) "pycentral crashed with NameError in run(): global name 'arch' is not defined" [High,In progress]15:56
evcheers15:56
infinityslangasek: Nope.15:56
slangasekbdmurray: well, one of the scenarios that caused the lock was if there's a crash while using the guest session15:56
slangasekbdmurray: so there's a bug there somewhere, but I wasn't able to spot it when I looked at the time15:56
infinityslangasek: Yeah, one might wonder why the guest session is locking passwd?15:57
evinfinity: added a note to investigate - thanks15:57
slangasekinfinity: yep15:57
bdmurrayev: is it because the bug has a python traceback and the error doesn't?15:57
slangasekinfinity: where exactly is the fix for bug #955936?  it's not in the unapproved queue15:57
ubottuLaunchpad bug 955936 in python-central (Ubuntu) "pycentral crashed with NameError in run(): global name 'arch' is not defined" [High,In progress] https://launchpad.net/bugs/95593615:58
cjwatsonit's in -proposed15:58
infinityslangasek: Accepted.15:58
infinity^15:58
slangasekoh15:58
slangaseksorry, was confused by the 'in progress'15:58
slangasekwhich is from the wrong task15:58
cjwatsonI guess we'll auto-copy it to quantal once it's verified15:58
slangasekok then15:58
evbdmurray: no, the signatures are not matched somehow. I think it's because I'm incorrectly parsing the signature on our end to what people.canonical.com/~ubuntu-archive/apport... is expecting15:58
bdmurrayslangasek: that's all I had for bugs15:59
slangasekok, thanks15:59
slangasek[TOPIC] AOB15:59
=== meetingology` changed the topic of #ubuntu-meeting to: AOB
slangasekone minute, talk fast ;)15:59
evSome crash database statistics for you:15:59
ev  - 5,066,166 crashes received since March 20th. That's right, 5 million.15:59
ev  - 263,280 crashes received on release day and 426,729 the next day.15:59
ev  - Thanks to having to constantly purge the cache, we're retracing one 12.0416:00
ev    crash every 47.44 seconds. Our best time was on release day with a full16:00
ev    cache. We retraced one crash every 25.15 seconds.16:00
ev  - 8,874 unique problems were seen today (with many instances of those16:00
ev    seen). Yesterday we saw 12,468 unique problems. Keep in mind that this is16:00
ev    greatly influenced by how quickly we can retrace crashes (and it currently16:00
ev    incorrectly places the crashes in the day bucket for today, regardless of16:00
ev    whether it actually happened days ago and we've only just retraced it). On16:00
ev    release day we only saw 1,604 unique problems.16:00
ev  - We've received reports from 364,359 people.16:00
slangasekwow16:00
ogra_geez, 5mio !16:00
infinityTake-home message: (A) we actually have users, (B) software sucks?16:00
slangasekwhat's the distribution of duplicates look like?  https://errors.ubuntu.com/ seems to only give a rolling frequency16:01
evthe retracer hardware is causing serious pain. The numbers will shoot up much higher once we sort that.16:01
xnox(C) we can now act in more real-time to real problems users are hitting *right now*16:01
ogra_still if we say we have 20mio users thats like a quater of them having crashes :)16:01
slangaseki.e., I'm pretty sure there've been more than 858 instances of the python-central issue, and that the number shown was higher yesterday :)16:01
evinfinity: yes, and yes16:01
cjwatson(D) maybe we need a more agile SRU process16:01
infinitycjwatson: Indeed.16:01
ogra_++ on that16:01
infinitycjwatson: Do we have a bikeshed session for that?16:01
slangaseknot currently16:02
evslangasek: yeah, the counts look a bit suspicious. I've been investigating but everything checks out so far.16:02
infinityWe probably should.16:02
slangaseksomeone want to schedule one?16:02
evthe code for month and year ranges will land soon16:02
slangasekinfinity: thanks for volunteering :)16:02
evin the web ui that is, it's already on the backend16:02
infinity>:(16:02
* infinity goes to register.16:02
evxnox: yes, this is entirely realtime data and we'll soon have realtime updates on the page itself16:02
evso you can watch a crash climb16:02
slangasekev: well, I'm *sure* the numbers were higher when I loaded the page yesterday - I remember a four-digit count for the top crashers16:03
evit's per day at the moment16:03
evyou'll be able to select month and year soon16:03
evand break down by releases, packages, and versions16:03
slangasekok16:04
evand matthew is working on a mockup UI to be able to select date ranges, I believe16:04
slangasekwould be good to understand things like: what percentage of all crashes does a given crash represent, are users likely to run into this same crash multiple times or just as a one-off, etc16:04
evas that was one of skaet 's requirements16:05
evslangasek: reply to my email :)16:05
slangasekheh :)16:05
slangaseknoted ;)16:05
evIRC is far too lossy for this sort of thing16:05
evcheers!16:05
slangasek#endmeeting16:05
=== 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
meetingology`Meeting ended Wed May  2 16:05:44 2012 UTC.16:05
meetingology`Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-02-15.03.moin.txt16:05
meetingology`Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-02-15.03.html16:05
slangasekthanks everyone :)16:05
slangaseksee you in Oakland!16:05
stgraberthanks!16:05
barrythanks!16:06
jodhthanks!16:06
* xnox sunny california here we come!16:06
xnoxthanks!16:06
evthanks!16:06
highvoltageyay, sun!16:06
ogra_thanks!16:06
infinityslangasek: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-more-agile-sru-process16:06
ogra_highvoltage, they call it oracle nowadays16:06
highvoltageew, oracle!16:06
slangasekinfinity: schedulimated16:08
=== greg_g is now known as greg-g
=== yofel_ is now known as yofel
AlanBellevening all18:58
AlanBell#startmeeting IRC team18:58
meetingology`Meeting started Wed May  2 18:58:14 2012 UTC.  The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/meetingology.18:58
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 #votesrequired18:58
=== 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 | IRC team Meeting | Current topic:
AlanBellhi all, who is here for the IRCC meeting?18:58
ikoniapresent18:59
Myrtti_o/18:59
oCeanyessir18:59
AlanBelllets give it a few minutes for others to pop along19:00
AlanBellhi funkyHat and topyli19:02
topylio/19:02
funkyHatHi ô/19:02
AlanBellhttps://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda19:03
AlanBellok, lets get started19:03
AlanBellwe don't have to clear out in a hurry at the end of the hour, but lets try and get through it by then anyhow19:03
AlanBell#topic Review last meetings action items19:04
=== 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 | IRC team Meeting | Current topic: Review last meetings action items
AlanBell#progress people to provide feedback on the ubottu-fr trial on bug 89250019:04
ubottuLaunchpad bug 892500 in ubuntu-community "eir is still not fit for purpose in #ubuntu" [Undecided,In progress] https://launchpad.net/bugs/89250019:04
topylido we have any?19:04
AlanBellonly a little bit of feedback provided, anyone got anything else to add about ubottu-fr19:04
oCeanHave not really been able to actually test it19:05
oCeanOr more honestly, Ignored it, since it's confusing to have to work with multiple bots19:05
oCeanAnd I still think that the list with bugs filed for eir is valid for any bot handling our bans/mutes19:06
ikoniaI've fed back on ubuntu-fr, I think it's the way to go19:06
AlanBellum, ok, but that doesn't help us to get to the goal of not having multiple bots19:06
ikoniait needs trimming down though19:06
ikoniabut you can only do that once you've picked a direction to develop19:06
oCeanCan we assume, with little feedback there is, others have ignored it too?19:07
AlanBellok, I like the idea of using the ubottu-fr code too19:07
AlanBellthat seems likely19:08
topyliyeah19:08
oCeanI think that is because we are not sure which way we're going19:09
ikoniayes, pick a path and lets go !19:09
ikoniaget behind it like it or not19:09
ikoniaI'll even shut up about eir if that's the way you want to go19:09
ikoniabut lets get stuck in19:09
oCeanI definitely agree19:09
ikoniaat least there has been discussion this time19:10
ikoniathought/testing behind it19:10
ikoniaget some opinions etc,19:10
AlanBellit is something we can maintain as well19:10
ikoniaAlanBell: the work niko has done makes it pretty much "too good" out of the box, so we should be able to trim it back19:11
LjLi think we can do trials, but either we all say "ok, we're trialling ubottu-fr, so let's ONLY use ubottu-fr for a month [or whatever] and nothing else", or otherwise we'll all continue using what we're used to19:11
ikoniarather than develop it19:11
ikoniaLjL: yeah, the dual bot thing has confused me a bit19:11
AlanBellok, lets move on for now, we will come back to the eir bug in a second19:11
ikonialets wade in, one way or another19:11
AlanBellthat is a fair point about not using multiple bots, thats why we moved eir out of the way19:11
ikoniahas it gone ?19:12
AlanBellso that it would still process expiries19:12
ikoniaI thought we where still supposed to be using it19:12
ikoniait was still in #ubuntu picking up bans the other day19:12
AlanBellit is in #ubuntu-ops-monitor19:12
topyliwe just moved the control channel19:12
ikoniaAlanBell: yeah, but it's still picking up bans in #ubuntu, so it's not going to be phased out19:12
ikoniait's just not spamming #ubuntu-ops-team any more19:12
topyliright19:12
AlanBellwell it will pick them up if it is there19:12
AlanBellbut it is mainly there so that it will remove bans19:13
ikoniacan we dump it out of ubuntu for a while ?19:13
oCeanSure, most of us are still using eir19:13
ikoniaoCean: that's why LjL's point is valid19:13
oCeanyep19:13
AlanBellif someone has a ban set to expire in 30 days or so and we remove eir altogether then that removal won't get processed19:14
ikoniacould the council have a little think please and knock up a draft plan ?19:14
jussiit makes sense to use code that already fits with supybot if we are aiming for a single bot solution19:14
ikoniaAlanBell: could we not say "we'll work it out manually for a while"19:14
ikoniajust to phase it out, we can always phase it back in if it's decided eir is the way forward19:14
LjLi don't think eir needs to be removed, just for it to be made clear that it's not the one to be used (if it's decided so)19:15
ikoniaone way or another we'll have to deal with those bans19:15
ikoniaLjL: but it picks up every ban19:15
ikoniait will still have it in the database and the default nag of 2 days option (or whatever it is)19:15
oCeanAlanBell: I can still update the overview on somedom, so we can see which ban has expired19:15
oCeanthen remove manually19:15
ikoniais there a way to put it into read only mode19:16
ikoniaso it doesn't pickup anything new ?19:16
AlanBellprobably not19:16
oCeanAlso, I think eir can still remind us of exired bans even when eir is not in #u19:16
AlanBellnot without affecting other channels19:16
ikoniaahhh of course19:16
ikoniadidn't think of the other channels19:16
funkyHatHow many bans are likely to be in eir? Would it be feasible to move them manually to ubotu-fr after disabling eir in #u?19:16
oCeanfunkyHat: currently 10719:17
funkyHatOr script it if we can get a detailed enough output from eir19:17
ikoniafunkyHat: oCean 's script run weekly until they are phased out would probable work simpler19:17
ikoniajust review on a sunday or something for a month or two19:17
funkyHatOk19:17
ikoniahell, I'll take an action to do it if needed19:17
AlanBellsounds good19:17
oCeanexactly19:17
topylii'd be fine with that19:18
ikoniait's not exactly a long term issue, and probably just a simple way of phasing it out19:18
funkyHatYep, sounds good19:18
AlanBellwhat is the overlap between ubottu and ubottu-fr? Can we put bits of ubottu-fr into ubottu easily?19:18
ikoniaas I recall niko basically did a modular hot swap19:19
ikoniaso you can swap in / out what you want19:19
ikoniaubottu-fr was just a snapshot of ubottu's later code from what I recall19:19
ubottuikonia: I am only a bot, please don't think I'm intelligent :)19:19
LjLdo we want to phase it out before we know whether ubottu-fr is "good enough", though? do most of us currently know anything about ubuntu-fr? i'm still leaning towards something like yelling at every op "use ubottu-fr instead of eir for a month!", but without killing eir immediately19:19
tsimpsonthat depends on how ubottu-fr works, ubottu is a regular supybot with plugins. so as long as all the code is external to supybot, it should be fine19:20
LjLikonia: no, i don't think it is just that. it has been modified (the supybot core, that is) to my knowledge19:20
LjLthe good news, i seem to recall, is that the modifications are being pushed upstream (to supybot)... don't quote me on that, it's what i seem to recall hearing19:20
ikoniaLjL: I don't know, so I'm not stating anything factually19:20
AlanBellok, we need to have a chat with niko about this19:20
tsimpsonheh, good luck getting anything upstream in supybot19:21
nikothere is some core changes in ubotu-fr, that means, you can't use channel plugin of ubotu-fr without the full bot, but that means too that you can load any kind of ubottu plugin into ubotu-fr19:21
AlanBelloh that sounds fine then19:22
LjLniko: yeah, it's inconvenient, though, to rely on a non-standard supybot. should we need to put a bot up quickly, we can't just apt-get supybot or whatever19:22
oCeanBut LjL has a point, with so little review/trials done on ubotu-fr, how much do we trust it, to replace eir, and actually remove eir from #u19:22
AlanBellso we can load all the ubottu plugins into an ubotu-fr clone and bring it up as ubottu19:22
nikowget the tar files, sudo python setup.py install, and that's all19:22
funkyHatSo what are the issues with getting ubotu-fr code into supybot?19:23
ikoniatsimpson: I'm guessing you've had a tough time getting anything upstream ?19:23
nikoubotu-fr code is dedicaced for ircd-seven, that's the big point19:23
tsimpsonikonia: upstream seem dead19:23
ikoniaahh19:23
ikoniaso very hard then19:23
oCeanaren't we getting a little ahead with discussing merges etc?19:24
ikonianiko: would it be possible to make that part a "module" rather than part of the code base19:24
ikoniaoCean: sorry, yes19:24
ikoniaI got excited19:24
topyliwhy not fork it properly then, if upstream is not maintaining the original?19:24
nikoikonia: not really, too much stuff need to be done in core files, due to how supybot was written19:24
tsimpsontopyli: because the code is both insane, and ugly19:24
topyliok :)19:25
oCeanif we trust current ubotu-fr enough, I say remove eir, bring ubotu-fr in, and run,test,file bugs, etc19:25
ikoniaI have the impression tsimpson may not have had a good time19:25
AlanBellyeah, I think we need to jump in with both feet here19:25
AlanBellwe also need to get through this meeting :)19:26
oCeanIs there a manual/usage wikipage of some sorts on ubotu-fr usage?19:26
nikohttp://nicolas.coevoet.fr19:26
AlanBellI will mail the list with a plan to set up an ubottu-fr clone with the ubottu plugins loaded and get it to replace ubottu19:26
oCeanniko: I see very few lines under usage :)19:27
AlanBellwe can discuss on the mailing list and at UDS for those going or attending remotely19:27
oCeanOK19:27
AlanBelllets crack on with the agenda now19:27
AlanBell#topic Open items in the IRCC tracker19:27
=== 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 | IRC team Meeting | Current topic: Open items in the IRCC tracker
AlanBellthere are none \o/19:27
AlanBell#topic Review Bugs related to the Ubuntu IRC Council19:27
=== 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 | IRC team Meeting | Current topic: Review Bugs related to the Ubuntu IRC Council
topyliyay!19:27
AlanBell#subtopic bug 788503 IRC Guidelines too #ubuntu centric - tsimpson19:27
ubottuLaunchpad bug 788503 in ubuntu-community "IRC Guidelines too #ubuntu centric" [Undecided,In progress] https://launchpad.net/bugs/78850319:27
AlanBellok, I put the text we had on the wiki19:28
topyliyeah, thanks for that19:28
AlanBellhttps://wiki.ubuntu.com/IRC/Guidelines has been updated19:28
topyliit is improved19:28
AlanBellI think it is better than it was, if there are further improvements to be made then great, we can make them on the wiki19:28
topyliyes19:29
funkyHatSo is this done? ⢁)19:29
AlanBellI will close that bug now19:29
AlanBellfix released19:29
AlanBell#subtopic bug 884671 Ubuntu IRC operator recruitment is slow and ungainly - jussi19:29
ubottuLaunchpad bug 884671 in ubuntu-community "Ubuntu IRC operator recruitment is slow and ungainly" [Undecided,In progress] https://launchpad.net/bugs/88467119:29
AlanBellso for this one we have a new procedure of processing applications from existing core ops as fast as we can conveniently do it19:30
topylithis is streamlined a bit with the fast approval of "old" ops19:30
topyliyes19:30
AlanBellI think we have one to do from a couple of days ago, but generally we are responsive on this now19:31
AlanBellI also want to do a big call for ops for lots of channels and process all the queues to do an intake of operators for the Quantal cycle19:31
AlanBelland generally have an intake at the start of each development cycle19:31
AlanBellI think that makes operator recruitment regular and quite gainly19:32
AlanBellso I think that bug is fixed :)19:32
topyliwe could compile a list of channels and simply send out a call for ops. it's been a while19:32
AlanBellyup, and it is the start of the cycle19:33
topyliyes19:33
LjLJust for the record: I still think you should have a "procedure" (or lack of one, whatever makes it happen) for appointing ops outside of a semestral recruitment process or whatever. And I'm not sure I see how a new release makes new ops automatically needed, on the other hand. But this has been discussed a lot before, so I'm just saying this for the logs, basically.19:34
topyliwe can close the bug19:34
AlanBellfix released19:34
AlanBellnoted LJL19:35
AlanBell#subtopic bug 892500 eir is still not fit for purpose in #ubuntu -ikonia19:35
ubottuLaunchpad bug 892500 in ubuntu-community "eir is still not fit for purpose in #ubuntu" [Undecided,In progress] https://launchpad.net/bugs/89250019:35
AlanBellso on this one we look like going in the ubotu-fr direction, I will mail the list and get some actions together for this.19:35
AlanBell#subtopic bug 913541 there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group19:36
ikoniayeah, the ubottu-fr plan covers this19:36
ubottuLaunchpad bug 913541 in ubuntu-community "there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group" [Undecided,In progress] https://launchpad.net/bugs/91354119:36
AlanBellPici: did you get anywhere with this one?19:36
AlanBellum, pici hasn't said anything, maybe he is indisposed19:37
AlanBelllets move on19:37
AlanBell#subtopic bug 916247 devel wiki on ubottu.com needs some attention19:37
ubottuLaunchpad bug 916247 in ubuntu-community "devel wiki on ubottu.com needs some attention" [Undecided,In progress] https://launchpad.net/bugs/91624719:37
AlanBellwell this was full of spam, that got cleared up and locked down, migrating the data to wiki.ubuntu.com might be a good idea, but the formatting will need a lot of manual fixing and nobody is leaping forward to take on that rather dull task19:38
ikoniaI can help with it, I can't "do" it19:38
ikoniathe ubuntu wiki is a tough mistress19:38
AlanBellthe bug was the spam, which has been addressed, I don't think the devel wiki in itself is a major overhead to have just sitting there19:38
AlanBellI am inclined at this point to just leave it and close the bug19:39
topylimoving the content is a different issue really19:39
AlanBellok, commented and [C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C fix released then19:40
AlanBelloops19:40
topyliok19:40
AlanBellright, moving on19:40
AlanBell#topic end of the induction/probation period for the current intake of operators19:41
=== 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 | IRC team Meeting | Current topic: end of the induction/probation period for the current intake of operators
topylioh it's time is it?19:41
AlanBellso we have a bunch of operators from the #lubuntu area who are at the end of their 3 month intro period19:41
AlanBellthere have been a couple of resignations from people who for various reasons decided not to continue and I think one of them never showed up at all19:42
AlanBellwe should email them individually I think19:43
Myrttiremind us of the nicknames again?19:43
Myrttior shhould I go check myself :-P19:43
AlanBellhttps://launchpad.net/~irc-lubuntu-ops/+members#active19:43
topylii haven't noticed any serious worries with the lubuntu ops. those who are not active are another story19:44
* AlanBell tidies up a couple19:45
=== slangase` is now known as slangasek
* Myrtti nods19:46
AlanBellanyone know m0hi?19:46
topylinot me19:47
Unit193AlanBell: IAmNotThatGuy19:47
AlanBelloh, I have seen that nick19:47
SidewinderIAm... is currently in #ubuntuforums19:48
SidewinderShall I ask him to join here?19:48
AlanBellSidewinder: that would be great19:48
ikoniais he active in #lubuntu ?19:48
SidewinderK19:48
Myrttihe's on the channel19:48
Myrttithere hasn't been that much need for ops there...19:49
Myrttithen again I can't remember if he was on the lesson at -classroom either, and I don't know if he needs it19:49
topylioh maybe i should apply there myself, i like that kind of channels19:49
AlanBellyeah, I don't have any concerns really, as an Ubuntu Member19:49
SidewinderAlanBell, I politely paged IAmNot ThatGuy19:50
AlanBellok, thats fine, will chat later, I don't have any concerns really19:51
Myrttiidle 29minutes19:51
Unit193(There is no meeting directly after this)19:51
AlanBellok, lets move on19:51
AlanBell#topic Calling for new operators19:51
=== 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 | IRC team Meeting | Current topic: Calling for new operators
AlanBellok, new cycle new intake of operators19:51
topyliyes let's just do it19:52
funkyHatYep19:52
AlanBellI will update my list of everyone in the queue and do a call for ops19:52
AlanBellthen we can process the queues and get a new group in19:52
topyliok19:52
AlanBell#action AlanBell to sort out a call for ops19:52
meetingology`ACTION: AlanBell to sort out a call for ops19:52
Myrttiwhich channels are we looking for?19:52
Myrttiand do you want me to redo my classroom?19:53
AlanBellpretty much all the core channels and yes please Myrtti19:53
AlanBelland I want to get a few more classroom sessions scheduled too19:54
topyliyou did have a good subject which you might do every now and then if you have the energy19:54
Myrttimay I suggest a specific call for certain timezones?19:54
AlanBellgood point, what times are in need of coverage?19:54
MyrttiI think nighttime Europe is always in need19:55
Myrttifew extra eyes wouldn't be bad19:55
topyliso, pacific america?19:55
AlanBellok, kind of 00:00 to 08:00 UTC19:55
Myrttitopyli: or au/nz/jp19:56
AlanBelldoesn't really matter where people actually are, just what time they are on IRC19:56
Myrttidepends on the viewpoint19:56
Myrttiexactly19:56
topyliyeah :)19:56
AlanBellok, I will put something about that in the call for ops19:56
AlanBellok, moving on19:56
AlanBell#topic alignment of launchpad teams and channel access lists19:56
=== 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 | IRC team Meeting | Current topic: alignment of launchpad teams and channel access lists
AlanBellright now the access lists and launchpad teams are in approximate agreement at best19:57
AlanBellhttps://docs.google.com/spreadsheet/ccc?key=0Ankl5FhsdSiZdGZVV2ZuLVRwa2c5M3pqX3BEaUhXMFE19:57
AlanBellis all the access lists19:57
topylisomeone was helping with this, no?19:57
AlanBellanyone who pms me an email address can have edit access to thi19:57
AlanBellknome was helping to identify some issues19:58
AlanBellI was thinking of doing a bit of automation to get the launchpad groups and the access lists in the spreadsheet side by side19:59
AlanBellthen we can make them all match up19:59
ikoniahasn't Pici done work on this before19:59
ikoniamaybe worth checking19:59
EvilResistanceAlanBell:  i see one flaw there, though: not every nickname that patches on Launchpad is up-to-date here on Freenode19:59
EvilResistances/patches/is/20:00
AlanBellEvilResistance: that is a good point, but everyone in the core ops team does have a nick on their launchpad page (I checked)20:00
AlanBellif any don't tie up I will be asking them to change the launchpad nick to their account name20:00
EvilResistanceindeed, just wanted to point that out, you'd need to make sure the nicks are kept up to date ;)20:00
AlanBellit is done on account names rather than nicks20:00
topyliisn't it a requirement in the first place, so you can be an op? :)20:00
=== EvilResistance is now known as Resistance
AlanBellaccount  : Resistance20:01
Resistance:P20:01
AlanBellok, don't need to go through the spreadsheet line by line right now20:01
AlanBelloh, one thing20:02
AlanBellVotiA or VotriA or something else as the default? should it be the same over all channels?20:02
AlanBelland should people have founder flags?20:02
AlanBellsome channels have a wide assortment of flags for operators, it looks a bit messy but I guess it works fine20:03
ResistanceAlanBell:  from an ITSec point of view, i think that only members of IRCC should have the founder flag, anyone else who has founder flag has sort of a god power over a channel.20:03
topylii think we've just done VotiA, but i'm far from clueful in this20:04
AlanBellok, we will have a bit of a think about this and work out some conventions I think20:04
topyliyeah i agree, ops don't need founder flags20:04
AlanBellbit of a pici question20:04
AlanBell#topic UDS blueprint20:04
=== 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 | IRC team Meeting | Current topic: UDS blueprint
AlanBellso UDS is coming up next week20:05
AlanBellI am going in person, anyone else going to be there?20:05
MyrttiResistance +120:05
topylijust remote lurking. i'll probably be semi-actively following the community track20:06
Myrttiwasn't sponsored, so not going20:06
AlanBellwould you like to have an IRCC session set up so we can have a chat over the audio streaming thingie?20:06
topyliwhy not, if we have something to chat about :)20:07
AlanBellok, I will set one up then, I will try to get a morning slot for it20:07
AlanBell#action AlanBell to schedule UDS session20:08
meetingology`ACTION: AlanBell to schedule UDS session20:08
AlanBell#topic setting up an election of another council member20:08
=== 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 | IRC team Meeting | Current topic: setting up an election of another council member
AlanBellthere are 4 people on the IRCC, there should be 5 according to our charter20:08
topyliyeah20:08
AlanBellwe deferred fixing that into the Q cycle but I think we are now in a much better position to go ahead with it20:09
funkyHatAnd we are now in the Q cycle ⢁D20:09
topyliwe need to feel around for candidates20:09
MyrttiI'm happy I'm practically unelectable \o/20:09
AlanBell\o/20:09
MyrttiI can continue to heckle from the peanut gallery20:10
AlanBellmmm peanuts20:10
Unit193Yep, we can toss the peanuts at them. :D20:10
funkyHatI know of one potential candidate, and I remember someone else being mentioned too20:10
AlanBellok, not much more to say on this one, just wanted to announce it and get started on it20:10
AlanBellwe will talk to the CC about the process20:11
AlanBellfinal item now20:11
AlanBell#topic set up #ubuntu-discuss for on-topic non-support discussion and ramblings20:11
=== 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 | IRC team Meeting | Current topic: set up #ubuntu-discuss for on-topic non-support discussion and ramblings
AlanBellwe have had Canonical sending people into #ubuntu to join the discussion about ubuntu20:11
AlanBellpeople who don't have an active support problem20:12
Myrtti#ubuntu-project20:12
AlanBellthis isn't ideal so we talked to canonical about this issue and got it fixed20:12
AlanBellbut it would be nice to have an area for on-topic talk about ubuntu that isn't support20:12
AlanBelland isn't what -offtopic is20:12
ikoniathat was always my dream for -offtopic20:12
LjLyou can kill #ubuntu-offtopic, or you can talk about interesting things there and make it better, your call i guess20:13
ikoniaoption 2 is always my preference20:13
topylii'd use -ot20:13
topylior *continue* to use -ot, rather20:14
ikoniaI would if you could have a discussion in there20:14
funkyHatIt is quite possible to have a discussion in -ot20:14
AlanBellwell right now it is being used for a perfectly nice conversation about films20:15
SidewinderUnless you want to create an #ubuntu-offtopic-offtopic, which I wouldn't recommend.20:15
AlanBellSidewinder: more of an #ubuntu-ontopic20:15
SidewinderNot a bad idea; just non-support..20:16
AlanBellI don't want to remove #ubuntu-offtopic20:16
LjLso you want a channel for support, a channel for Ubuntu discussions that are not support, and a channel strictly for discussions that are not about Ubuntu20:16
LjLseems overkill to me20:16
LjLand a good way to kill either or both the "secondary" channels20:16
SidewinderThere is that.20:16
topylii think -ot is just fine for any ubuntu-related discussion. you're not required to talk about flashlights there. it's just for whatever is not support20:17
AlanBellit is possible that it won't be a viable channel long term, I don't know without trying it20:17
SidewinderI don't feel that ot is overly busy.20:17
guntbertmaybe make it more obvious in -ot that is is intended for discussion about ubuntu - not just a general "anything goes"20:17
funkyHatI don't see much issue with encouraging more ubuntu-related discussion in -ot. At the moment it's not a terribly busy channel20:17
LjLguntbert: well but it's not. it's for both things20:17
funkyHatguntbert: well it is a general channel too20:18
guntbertLjL: ok, (I said 'not just' :-)20:18
SidewinderIf it ain't broke, don't fix it. IMHO20:18
topyliit's not broken. sure, we could always tend to it better, but that's not the channel's fault as such20:19
AlanBell"Join the discussions in #ubuntu on Freenode" is what the canonical stuff said20:19
guntbertI see one problem: quality discussion just don't happen there - do they?20:19
AlanBell"Join the discussions in #ubuntu-offtopic on Freenode" would be a strange thing for them to say to customers20:19
topyliquality discussion does happen in -ot. just not all the time20:19
LjLso the issue is the channel name?20:19
topyliAlanBell: that's true20:19
Sidewinderguntbert, I think they do; it's not just limited to that.20:20
SidewinderLjL, I think the name's fine, but that's just me.20:20
AlanBellLjL: partly, yes, and partly because someone arriving in a totally off-topic discussion might be confusing20:20
topylicanonical could say "join #ubuntu for support and #ubuntu-offtopic for general discussion"20:21
funkyHatI think arriving to see an off topic discussion is better than joining a dead channel20:21
LjLAlanBell: make #ubuntu-chat or #ubuntu-discuss or whatever and redirect it to #ubuntu-offtopic if the issue is the channel name in "marketing", i don't think that's an issue. if the problem is the content, well i don't think it's an issue either, but i guess it might be20:21
guntberthow about doing it the freenode way?   #help = #freenode              so #ubuntu-offtopic = #ubuntu-discuss20:21
Sidewindertopyli, I think that's THE answer.20:21
Resistancei think topyli has the right idea there20:21
funkyHatMaybe if -ot gets too crowded we could rethink having a -discuss or -project channel20:21
funkyHat(assuming some of the crowd is actually project related ;)20:22
guntbertI too like topyli's proposal20:23
funkyHatYep20:24
AlanBellhow much of the crowd at the moment is made up of people who are developers on the project in some way?20:24
ikoniapretty much zero20:24
Resistancewhat ikonia said, at the most maybe 1%20:25
topyliin -ot? not too many20:25
ikoniaofftopic has nothing to do with ubuntu in any way20:25
ikoniaeven community20:25
ikoniapeople don't user/support/discuss ubuntu, it's just another defocus20:25
Myrttimost of the time it feels like -uk is better for that discussion ;-)20:25
ikoniaMyrtti: it is20:25
AlanBellyup20:25
topylii'm always talking about ubuntu or linux in -ot20:26
Myrttis/that//20:26
topyliexcept when i'm talking about something else :)20:26
SidewinderHeh,.20:26
ikoniatopyli: yes, your a rarer beast, as is ljl and a few others20:26
ikoniabut a lot of the users have no "ubuntu" reason to be there20:26
AlanBelland lots of people who do some contribution to ubuntu in some context don't really want to be there20:27
topylithere are a lot of people there who don't even use ubuntu anymore, but used to at some point and just like the people20:27
ikoniatopyli: I don't think you have to use it, but have an interest in it, follow it, be aware of it so you can actually participate20:27
ikoniabe "involved" in someway20:27
AlanBellboth are fine, I don't want to go shutting down -offtopic as a kind of defocusy chatter place20:27
topyliikonia: it would be more "ubuntu" that way for sure20:28
AlanBella lot of loco teams don't have active channels so -offtopic kind of takes that role a bit20:28
SidewinderCurrently it's just less strict.20:28
ikoniatopyli: at the moment there is no "ubuntu" community to that channel, beyond the fact that it has the ubuntu coc20:28
ikoniait's not made up of members/users/interested parties etc, its just people20:28
ikoniayou could chnge the channel name to offtopic and it would not have any difference to the users/content20:29
daxIf memory serves, the top three people in that channel don't use Ubuntu; topyli breaks the trend by being in 4th place :P20:29
ikoniaI don't think using it is a requirement20:30
Myrttitopyli: have you moved back to Ubuntu now?20:30
Myrtti:-P20:30
topylii'm back on ubuntu yes :)20:30
ikoniabut being part of the community, following it's disucssion/development etc20:30
ikoniabeing able to join in with it in some way20:30
daxI will refrain from discussing my opinions on whether AtomicSpark is part of the Ubuntu community, but I don't think I (#2) am :P20:30
AlanBellok, so how do we draw this item to a conclusion?20:31
topyliyeah you're an example of someone who *was* a part of the community for a long time and now just hang in there with old friends :)20:31
topyliAlanBell: well, frankly i'd do nothing but tell canonical to clarify their message20:32
SidewinderHomeostasis?20:32
Sidewindertopyli, +120:32
ResistanceI'm not on the Council, but I think that, at the least, telling Canonical to clarify their message is the first step, but that more in-depth research and discussion on this topic needs to be done to determine whether an Ubuntu discussion channel needs to exist separate from -offtopic20:33
SidewinderIf we were voting, that is..20:33
topylimaybe it will improve -ot if canonical starts sending people there, who are actually interested in discussing ubuntu20:33
funkyHatI agree. And if we want to have more ubuntu related discussion in -ot we need to just have more ubuntu related discussion20:33
funkyHatYes20:33
AlanBellwell I did that, and Mark said20:33
AlanBell * if there is a better IRC channel for general "hello, I'm interested in X with Ubuntu, where should I go?", then let me know and I'll update the team to use that for the cases where they do judge the audience to be developer or at least highly technical in nature.20:33
AlanBellthe other option is that canonical don't send people to IRC20:33
AlanBelland send them to askubuntu.com or something instead20:33
ResistanceAlanBell:  that'd be cutting out one of the big support communities, there.20:33
topyliwell the latter one does not sound very good20:33
Resistancei think IRC is better for real-time support, askubuntu.com and ubuntuforums.org take some time to actually get decent responses, and to be honest, there's more people on IRC who really know what they're talking about20:35
Resistance(at least, in comparison to askubuntu.com)20:35
AlanBellit isn't about support20:35
topylialso, it's not *so* terrible to come to the main channel, it's natural. it's just that people will use their energy to guide these people to the correct channels like -ot or -server or whatever20:35
topylii don't know how big this problem is for #ubuntu20:35
AlanBellthis was about their communications around ubuntu for android20:35
topyliis there *any* channel where people talk about ubuntu for android?20:36
topylidoes it even have anything to do with the community?20:36
LjL^20:36
LjLmaybe the problem is that Canonical and its developers should interact with the community, not "send" people to IRC when there's no way anyone can have a clue about the product20:37
daxDoes it have publicly accessible source-code anywhere?20:37
dax(because if not, it's not an Ubuntu community project, it's a Canonical project using Ubuntu branding)20:37
AlanBellhttp://paste.ubuntu.com/963188/20:38
AlanBellsilly pastbin with no wrapping20:38
topyliubuntu one has nicely settled on its own channel, it's not bothering us too much i think20:38
topyliat least that's how it used to be20:38
AlanBellso yes, there should be more canonical developers involved, but no they are not going to all join #ubuntu-offtopic and stay there20:39
topyliprobably not. they have jobs :)20:39
Myrttithis might be something that could be discussed in UDS...20:40
AlanBellthat is a good point20:40
AlanBellget some more canonical opinions on the matter too20:41
topyliyes. the devs will be there20:41
Myrttiindeed20:41
AlanBellok I will put it on the agenda of the UDS meeting20:41
SidewinderAlanBell, What's wrong with them joining #u? I for one have noticed some questions asked there that were not answered and I could not.20:41
MyrttiSidewinder: there is nothing to support20:42
AlanBellSidewinder: because they don't have a support question and the general feeling at the time was nobody wanted people turning up in #u wanting to "join the conversation"20:42
LjLSidewinder: that Ubuntu's policy has always (to my knowledge) been that it's a technical support channel only, not for opinions, information about products, discussion, etc - if we opened *that* door, a lot of stuff would come in20:42
MyrttiSidewinder: so it doesn't fit on a support channel at the moment20:42
AlanBellanyhow, lets discuss that more next week20:43
SidewinderOIC.20:43
AlanBell#topic Any Other Business20:43
=== 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 | IRC team Meeting | Current topic: Any Other Business
AlanBellanything else to discuss now?20:43
MyrttiAlanBell: #ubuntu+120:43
Myrtti(see -ops)20:43
AlanBellah right, shall we open it again?20:43
topyliif Q is open, why not?20:43
AlanBellcan't see any particular reason no to, the toolchain is open20:43
SidewinderLjL, I agree.20:43
AlanBelllets do it20:44
topyliyeah20:44
AlanBellok, anything else20:44
oCeanAlanBell: One more thing, since you skipped quite quickly through the "eir not fit for purpose"20:44
oCeanRecently I removed a lot of bans/mutes. Most of those had no comments at all, so I had to go through logs etc to see if they could be removed20:44
oCeanBecause I don't really want to go through all that again, and we don't want to do that if we're weekly reviewing which bans can be removed, I suggested changing eir's config (or for any new bot) to autoremove-after-expire.20:44
AlanBellok, I think if people are not commenting on bans they are fair game for removal20:45
oCeanSo if you want a ban/mute to stay, just make sure you btset it with an expire date and/or comment, or after 2 days it is gone and so preventing all these undocumented bans20:45
oCeanwe can agree, but others should be aware of it20:45
oCeansince even after a couple of days, we have lots of expired and uncommented bans again20:45
topylisounds good to me. an email to the list should handle the communication20:46
oCeanyup20:46
topylioCean: are you volunteering to compose this email? :)20:46
oCeansure, but it would not go out before the weekend20:47
topylibecause you would know what you're talking about, unlike me20:47
oCeandon t think we're in a hurry though20:47
topyliok20:47
AlanBellfine20:48
AlanBellanything else to discuss?20:48
AlanBell#endmeeting20:48
=== 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
meetingology`Meeting ended Wed May  2 20:48:42 2012 UTC.20:48
meetingology`Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-02-18.58.moin.txt20:48
meetingology`Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-02-18.58.html20:48
AlanBellthanks everyone20:48
oCean\o/20:48
topylinice, lots done20:48
SidewinderThank you, all.20:48
AlanBelllots of bugs closed :)20:49
funkyHatwoo20:49
funkyHatThank you everyone20:49
Myrttiplease poke iceroot on -ops when +1 is open20:49

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