[00:12] <highvoltage> oh man I'd so love to be late for my own funeral one day
[00:12] <highvoltage> they could put it on my gravestone "He was even late for his own funeral"
[00:13] <highvoltage> (bit too morbid?)
[00:13] <charlie-tca> not me, I plan to be early!
[08:25] <benonsoftware> Question: When is the next Asia Oceania meeting?
[08:41] <elky> o.O
[09:57] <davidcalle> Morning all
[09:57] <MooDoo> davidcalle: morning
[16:00]  * mvo waves
[16:01] <jhunt> o/
[16:01] <bdmurray> \o
[16:01]  * slangasek waves
[16:02]  * stgraber waves
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is slangasek.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <hannie_> Hi, I'm here for the first time and I am going to "listen"
[16:03] <slangasek> hannie_: welcome :)
[16:04] <slangasek> [TOPIC] lightning round
[16:04] <MootBot> New Topic:  lightning round
[16:04] <hannie_> thanks
[16:04] <slangasek> $ echo $(shuf -e cjwatson barry doko csurbhi stgraber jhunt mvo ev vorlon bdmurray)
[16:04] <slangasek> stgraber doko cjwatson ev vorlon csurbhi bdmurray jhunt mvo barry
[16:04] <slangasek> stgraber: start the ball rolling :)
[16:04] <stgraber> Fixed and released Edubuntu.
[16:04] <stgraber> Worked on Arkose, blog post to come soon. I basically did a complete rewrite to python and porting to LXC.
[16:04] <stgraber> Spent a bit of yesterday working on bug 482419.
[16:04] <stgraber> Rest of the week will most likely be spent working on Arkose, getting it in shape for an upload and blogging about it as soon as possible (code is in lp:~arkose-dev/arkose/trunk)
[16:04] <stgraber> Will review and upload a new sssd later this week too now that ding-libs go accepted in the archive (missing build-dep for the new sssd).
[16:04] <stgraber> (done)
[16:05] <stgraber> (as in, release alpha-1 of Edubuntu, obviously ;))
[16:05] <barry> stgraber: is arkose compatible w/python3? :)
[16:05] <stgraber> barry: not yet, but converting should be really easy :) I have a few print that python3 won't like.
[16:05] <slangasek> sru for 482419 accepted into -proposed, thanks :)
[16:06] <barry> stgraber: it would be fun to try.  i'd be happy to help!
[16:07] <slangasek> doko:
[16:07] <doko> - various GCC/gnat/gcj multiarch packaging fixes
[16:07] <doko> - track down unity-2d-places crash to qt4-x11 violating strict aliasing rules (with didrocks)
[16:07] <doko> - track down autogen build failure
[16:07] <doko> - track down binutils regressions
[16:07] <doko> - update GCC packages
[16:07] <doko> - syncs and merges
[16:07] <stgraber> barry: ported ;) was just 7 lines to change
[16:07] <doko> and multiarch enabled packages building now for unstable
[16:07] <barry> stgraber: you rock!
[16:08] <slangasek> yay for multiarch :)  will be flushing patches to Debian soon...
[16:08] <doko> (done)
[16:08] <slangasek> then maybe we can have one or two base libraries back in sync
[16:09] <cjwatson> any more word on the dpkg patch review?
[16:09] <slangasek> none
[16:10] <slangasek> it's not critical-path for getting other packages back in sync, but it's obviously not good for Debian to not have the feature :/
[16:10] <slangasek> cjwatson:
[16:11] <cjwatson> On holiday Wed-Fri, so not much activity this week.  (I did a fun d-i port to the Yeeloong mipsel netbook in my vacation, among other things ...)
[16:11] <cjwatson> Got back to live-build.  As I get into more detail the list of work items has been growing, but I think it's now complete and the remaining items are fairly easy.  I should finish this later this week.
[16:11] <cjwatson> Belatedly pushed lupin changes for bug 610898 to lucid/maverick.
[16:11] <cjwatson> Moved Kubuntu seeds to ~kubuntu-dev branches.
[16:11] <cjwatson> --
[16:11] <cjwatson> Last week, finally managed to fix iSCSI boot (bug 728088).
[16:11] <cjwatson> Continuing to help out with GHC transition.
[16:12] <psurbhi> cjwatson, cool! that must have been nasty!
[16:12] <psurbhi> the iscsi boot bug
[16:13] <cjwatson> yes, as ever having direct access to an affected machine helped enormously
[16:13] <cjwatson> I don't know how much your code does with networking as yet, but you might like to have a look at the fix
[16:14] <psurbhi> ok
[16:14] <psurbhi> thanks! i will do that
[16:15] <cjwatson> the configure_networking interface right now is *nasty*
[16:16] <cjwatson> definitely needs redesigning rather than emulating
[16:16] <slangasek> cjwatson: glad that live-build porting is reaching a conclusion.  Do you know where the ARM team sits with porting their images over?
[16:17] <cjwatson> I've done testing on x86 builds that are more or less equivalent from the build-script point of view to ARM images
[16:17] <cjwatson> I have no remaining compatibility items that are specific to ARM
[16:18] <slangasek> ok, great
[16:18] <cjwatson> (fixes were: making '--initramfs none' actually work, for jasper; using mkfs.ext2/ext3 rather than genext2fs; creating swap file in ext2/ext3 images)
[16:18] <cjwatson> so I intend to big-bang all flavours and architectures at once
[16:19] <slangasek> \o/
[16:20] <slangasek> do the release team get a training session on live-build before alpha-2? :)
[16:20] <slangasek> ev:
[16:21] <ev> - Spent the vast majority of the week fighting PyGI.  Got fairly fair in the
[16:21] <ev>   ubiquity conversation, but hit a bit of a wall trying to port a custom
[16:21] <ev>   widget (timezone map).  Putting down for the moment so as to not waste too
[16:21] <ev>   much time on one workitem.
[16:21] <ev> - Worked on re-proposal email for measuring installation failure and success.
[16:21] <ev>   I'm going to suggest that we dive straight in to the full implementation,
[16:21] <ev>   putting a checkbox on the slideshow and crash dialog for "send data to help
[16:21] <ev>   improve experience."  Leaving this checked, as will be the default, will
[16:21] <ev>   collect data on installation failure and success, but also the installer
[16:21] <ev>   version, CD data, and some additional information that would provide a
[16:21] <ev>   better picture around the failing installs.
[16:21] <ev> - Read Microsoft's paper on the design of Windows Error Reporting, and replied
[16:21] <ev>   to the Ubuntu Metrics team with my thoughts on how we can feed this into the
[16:21] <ev>   design of the automatic crash reporting.  They've largely automated the
[16:21] <ev>   traditional bug feedback loop.  Instead of the user having to file a bug,
[16:21] <ev>   the developer looking it over and asking the user for more information, or
[16:21] <ev>   providing an instrumented build for the user to try, both with a very long
[16:21] <ev>   feedback loop, if a developer sees crashes coming through that require more
[16:21] <ev>   information, they hit a flag in WER that tells subsequent clients to
[16:21] <ev>   automatically collect the additional required data, or even provide a stack
[16:21] <ev>   trace against every malloc call with a garbage collection done at the end to
[16:21] <ev>   provide verbose information on the leak, all happening with the users only
[16:21] <ev>   pressing "yes, I'd like to help Microsoft fix this."  And of course, they
[16:21] <ev>   have a means of feeding updates back to the system if the bug is already
[16:21] <ev>   fixed.
[16:22] <ev> - Met with Christian to discuss the design work needed on Wubi this cycle.  I
[16:22] <ev>   need to provide him with a screencast of the install process.
[16:22] <ev> - Fairly long call with Rick, Allison, and others to discuss the state of
[16:22] <ev>   Platform Futures.
[16:22] <ev> (done)
[16:22] <slangasek> ev: documentation of pygi still a problem?
[16:22] <cjwatson> did my mail about EU privacy law concerns reach you?  I haven't seen any replies to it, and am not sure if that's due to delivery problems or because everyone's blowing me off as a loon :)
[16:22] <ev> it's a ghetto.
[16:23] <ev> cjwatson: they did and I was reading it over this morning
[16:23] <ev> I suspect the opt-out nature of the re-proposal addresses that point, but I'm happy to run things by Amanda
[16:23] <cjwatson> a checkbox (as opposed to hiding it in preseeding) would satisfy my concerns there, I think
[16:23] <cjwatson> I don't recall its position on opt-in vs. opt-out
[16:25] <cjwatson> but not hiding it is the main thing
[16:25] <ev> indeed
[16:25] <ev> I will fight hard on it being checked by default though
[16:25] <ev> I don't think we're going to get good data with opt-in
[16:25] <cjwatson> I don't think I personally feel strongly on that at any rate
[16:26] <ev> and then there's the whole publishing battle, but I had a good chat with mdz on that
[16:26] <cjwatson> we should think about Wubi though, it will need the same checkbox (since its second stage is noninteractive)
[16:26] <ev> indeed, there's already a workitem for it
[16:26] <ev> way ahead of you ;)
[16:29] <cjwatson> heh, ok :)
[16:31] <psurbhi> did vorlon, get dc?
[16:31] <cjwatson> looks like it
[16:32] <psurbhi> ok
[16:32] <cjwatson> psurbhi: want to go ahead?
[16:32] <psurbhi> i will paste in my status
[16:32] <psurbhi> yeah
[16:32] <psurbhi> *) short week - thursday, friday - off.
[16:32] <psurbhi> *) working on writing the initctl command for changing the root filesystem
[16:32] <psurbhi> *) done.
[16:32] <cjwatson> heh, short and sweet :)
[16:33]  * slangasek shakes his fist at freenode
[16:33] <slangasek> what'd I miss? :)
[16:33] <cjwatson> will paste
[16:33] <slangasek> (did my own report make it through?)
[16:34] <barry> slangasek: nope
[16:34] <cjwatson> nope
[16:34] <slangasek> k, repasting
[16:34] <slangasek> * merged new pam upstream version, sweeping up the CVEs for oneiric
[16:34] <slangasek> * moving some of our patches a little closer to upstream
[16:34] <slangasek> * coordinating multiarch fixes into Debian
[16:34] <slangasek> * various other syncs/merges (most .la files dropped last cycle for multiarch are now syncs again)
[16:34] <slangasek> * will look at nfs-utils, rpcbind this week
[16:34] <slangasek> (done)
[16:34] <slangasek> questions?
[16:35] <slangasek> psurbhi: initctl command for changing root filesystem> is this the same thing as serializing state to let upstart re-exec itself, or are you doing it a different way?
[16:36] <psurbhi> slangasek, its achieving what run-init does in initramfs through upstart
[16:36] <psurbhi> so actually it could let any init be execed (could be upstart or /bin/sh etc)
[16:36] <cjwatson> no state passing
[16:36] <slangasek> ah, ok
[16:36] <psurbhi> yeah, no state passing yet
[16:36]  * slangasek nods
[16:37] <slangasek> bdmurray:
[16:37] <bdmurray> bug stats for foundations-bugs with arsenal work, push changes to collect-team-bugtotals in arsenal to gather bug stats about packages the team is    subscribed to, updating collect-team-bugtotals to get bugs tagged apport- or regression-
[16:37] <bdmurray> added bug reported acknowledgement for update-manager (telling people to tag bugs distribution-upgrade)
[16:37] <bdmurray> updated apt's apport package installation failure routine to include /var/log/apt/history.log and not report ENOENT bug
[16:37] <bdmurray> wrote an update-manager apport hook, proposed branch for merging and had it merged / sponsored
[16:37] <mvo> bdmurray:  \o/
[16:37] <bdmurray> update packages-with-most-bugs-recently.py mailing list parsing script which returns most recent packages with bugs counts
[16:37] <bdmurray> patch pilot
[16:37] <bdmurray> wrote some apport bug patterns for foundations-bugs
[16:37] <bdmurray> phone call with allison regarding bug workflow / lifecycle survey
[16:38] <bdmurray> done
[16:38] <jhunt> Lots of Upstart merging again. All natty feature code sent as individual
[16:38] <jhunt> patches to upstart-devel and now applied to lp:upstart. Cookbook update
[16:38] <jhunt> (lots more in progress due to merging). Ubuntu merge still TODO -
[16:38] <jhunt> somewhat of a conflict extravaganza! :) Mailed Coverity re scanning
[16:38] <jhunt> Upstart+libnih codebases - no response yet... Now starting to discuss
[16:38] <jhunt> Oneiric plans on MLs. Experimentation with Abstract Jobs.  Ongoing
[16:38] <jhunt> investigations into chkconfig-like tool for Upstart.
[16:38] <jhunt> ✔
[16:38] <slangasek> so as of this week, that means apport will only be sending us useful bug reports ;)
[16:39] <jhunt> psurbhi: do we have a list of jobs that need to pass state btw?
[16:39] <psurbhi> i thought that was plymouth and something else
[16:39] <psurbhi> mentioned on the blueprint
[16:40] <mvo> Short week, last thursday public holiday, friday vacation
[16:40] <mvo> squid-deb-proxy: merge/cleanup debconf support, add pkgblacklist, add .d directories for destination/source/pkgblacklist, add udeb
[16:40] <mvo> apt: work on abi-break branch that merges the various abi-break branches together, add distro as query string to the mirror method, make mirror ignore "#" lines, SoC work
[16:40] <mvo> update-notifier: honor global disabled apport properly
[16:40] <mvo> software-center: branch review/merges, make qml branch pyflakes clean, adds model tests for the qml branch, merge basic qml UI to trunk, work on improved "enum-style-idea" branch and merge to trunk, upload new version
[16:40] <mvo> (done)
[16:40] <barry> python3.1 rdeps eradicated (bug 791423 still outstanding); bug 634387 and bug 659738 (double motd banner); foundations-o-dhpython-transition (should have wiki page and status email rsn); foundations-o-python-versions (working on py3-on-cd data); released python 2.6.7; patch pilot; platform futures meeting; udd stakeholders meeting; done.
[16:41] <slangasek> will be nice to finally put that motd bug to rest
[16:42] <barry> slangasek: indeed.  do you have any thoughts on which patch to accept for lucid?
[16:42] <slangasek> incidentally, I was going to pull lp:ubuntu/sysvinit to look at some of the history of the maintainer script, and bzr tells me it's no longer there :P
[16:42] <psurbhi> jhunt, i dont really recollect which one it was.. but its some process that needs to be stoped just for the switch..! cjwatson, do you happen to know this?
[16:42] <slangasek> (it used to be, because I have a branch of it locally!)
[16:43] <barry> slangasek: sadly, i did not have a branch of it and had to use apt-get source.  don't know what happened to it :(
[16:43] <psurbhi> jhunt, i will find this out and let you know!
[16:43] <slangasek> barry: are there competing options now?  I thought the '&& ! [ -L ... ]' was the only proposal on the table
[16:43] <cjwatson> psurbhi: udev?
[16:43] <jhunt> psurbhi: thanks
[16:43] <cjwatson> but that needs to be stopped to move it to the new root
[16:43] <slangasek> barry: I guess I should raise a udd bug on that; losing the existing branch is rather an unpleasant failure mode
[16:43] <psurbhi> yes, i thought it was udev, but we could just restart it without the state, it will just be slower without the state maybe..?
[16:43]  * cjwatson tries to grep
[16:43] <barry> slangasek: i thought there was another option (backporting oneiric's full change to lucid), but i like the !-L option a lot.  maybe i should just upload that and be done with it :)
[16:44] <cjwatson> $ grep -r '/dev/\.initramfs/.*pid' /usr/share/initramfs-tools/
[16:44] <cjwatson> /usr/share/initramfs-tools/scripts/init-top/plymouth:/sbin/plymouthd --mode=boot --attach-to-session --pid-file=/dev/.initramfs/plymouth.pid
[16:44] <psurbhi> i did remember discussing udev as that process at the UDS
[16:44] <cjwatson> /usr/share/initramfs-tools/scripts/init-top/bootchart:echo $! > /dev/.initramfs/bootchart.pid
[16:44] <barry> slangasek: bzr bug, yes definitely!
[16:44] <cjwatson> /usr/share/initramfs-tools/scripts/init-bottom/plymouth:if [ -f ${rootmnt}/dev/.initramfs/plymouth.pid ]
[16:44] <cjwatson> so I think NOT udev but plymouth and bootchart
[16:44] <psurbhi> yes! thats it .. bootchart! :) thanks a lot!
[16:44] <slangasek> barry: having looked at the differences, backporting the full change makes me nervous.  I might be less nervous if I had VCS history to look at ;P
[16:44] <psurbhi> jhunt ^ so thats it - plymouth and bootchart :)
[16:44] <jhunt> slangasek: lp:~jamesodhunt/sysvinit/for-slangasek
[16:45] <barry> slangasek: agreed and agreed!
[16:46] <jhunt> psurbhi: thanks. state saving does seem like an awful lot of work for just two jobs though :)
[16:46] <slangasek> jhunt: I think that's about the same as what I have here, and predates all the interesting changes... :)
[16:46] <cjwatson> state saving is more useful for upgrades
[16:46] <barry> slangasek: okay, i'll upload the !-L patch to lucid-proposed
[16:46] <slangasek> jhunt: thanks anyway though :)
[16:47] <barry> slangasek: and there's always `bzr import-dsc`
[16:47] <slangasek> yeah...
[16:48] <slangasek> [TOPIC] AOB
[16:48] <MootBot> New Topic:  AOB
[16:48] <slangasek> anything else today?
[16:49] <cjwatson> not urgent right now, but we should probably start planning for the rally soon
[16:50] <slangasek> yes
[16:50] <ev> the idea of installing updates after downloading them in ubiquity came back up today
[16:50] <ev> I'm inclined to do it
[16:50] <slangasek> there's a wiki page seeded where you can post your agenda items for the rally; one sec
[16:50] <cjwatson> slangasek: ah, good
[16:51] <cjwatson> ev: how would we get over the problems raised last tme (essentially, what to do if you finish installation before you're finished upgrading)?
[16:51] <ev> cjwatson: let it keep going until it's done, presumably with a cancel button if it hasn't started installing packages yet
[16:51] <mvo> could we use unattended-upgrades in minimal-steps mode for this? it will still have a delay, but smaller
[16:51] <cjwatson> or minimal-chunks mode perhaps?
[16:51] <cjwatson> snap
[16:51] <mvo> :)
[16:52] <slangasek> https://wiki.canonical.com/UbuntuPlatform/Rally/Oneiric/Foundations
[16:52] <ev> I am unfamiliar with this. Can you please point me at your manifesto? ;)
[16:54] <cjwatson> /usr/bin/unattended-upgrade:upgrade_in_minimal_steps()
[16:54] <mvo> ev: /etc/apt/apt.conf.d/50unattended-upgrades has some text, look for minimal seps
[16:54] <mvo> steps even
[16:54] <ev> thanks to the both of you
[16:55] <cjwatson> remind me to spend some time optimising man-db, I bet I could speed up minimal-steps mode some
[16:55] <mvo> that would be great!
[16:55] <cjwatson> (though actually I don't know how much of the slowness there is per-run and how much is per-file)
[16:55] <mvo> the code in u-n is currently pretty simple (== navie) there is lots of room for improvement there as well
[16:56] <cjwatson> alternatively buxy's work on reorganising triggers would help too
[16:59] <slangasek> anything else before we adjourn?
[16:59] <slangasek> #endmeeting
[16:59] <MootBot> Meeting finished at 10:59.
[16:59] <slangasek> thanks, all
[16:59] <stgraber> thanks!
[16:59] <barry> thanks!
[16:59] <mvo> thanks
[16:59] <psurbhi> thanks
[16:59] <slangasek> please start plugging your rally agenda items into the wiki as you think of them
[17:00] <jhunt> thx
[17:00] <ev> thanks
[17:00] <pc_magas> Kalispera
[17:01] <pc_magas> Twn euxaristiwn einai simera?
[17:01] <pc_magas> xaxaxaxa
[17:01] <pc_magas> Sorry
[17:59] <pedro_> hello
[18:00] <patrickmw> hey
[18:00] <bdmurray> hey
[18:00] <patrickmw> jinx
[18:00] <jibel> hello
[18:00] <bdmurray> lets get going then
[18:00] <bdmurray> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is bdmurray.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <bdmurray> the agenda is available at https://wiki.ubuntu.com/QATeam/Meetings
[18:01] <bdmurray> [TOPIC] Previous Actions
[18:01] <MootBot> New Topic:  Previous Actions
[18:01] <bdmurray> bdmurray working on bugs with WORKAROUNDS
[18:02] <bdmurray> So I queried the Launchpad database for ubuntu bug tasks with the word WORKAROUND in the description and found there are about 700
[18:03] <bdmurray> Our guidelines say to use all caps but I might expand the query to not be case sensitive and also check comments just to see if maybe more are hiding
[18:03]  * charlie-tca made it, too
[18:04] <bdmurray> But regardless we have a starting number so that we can try and get workarounds used more and see what happens
[18:04] <charlie-tca> I think that would be a good idea. Not everybody follows the example so closely.
[18:05] <bdmurray> right and we'd also talked about adding a tag to bugs with workarounds so I could rerun the query and automatically update bugs which are following it closely and produce a list to manually review for the others
[18:06] <bdmurray> [ACTION] bdmurray to query more liberally for workaround usage
[18:06] <MootBot> ACTION received:  bdmurray to query more liberally for workaround usage
[18:06] <bdmurray> next then
[18:06] <bdmurray> [TOPIC] Community Efforts/Testing
[18:06] <MootBot> New Topic:  Community Efforts/Testing
[18:07] <bdmurray> jibel: ?
[18:07] <jibel> I'm here
[18:07] <jibel> Last week was alpha1 iso testing.
[18:07] <jibel> You'll find results on the wiki:
[18:07] <jibel> https://wiki.ubuntu.com/QATeam/ReleaseReports/OneiricAlpha1TestReport
[18:08] <jibel> [LINK] https://wiki.ubuntu.com/QATeam/ReleaseReports/OneiricAlpha1TestReport
[18:08] <MootBot> LINK received:  https://wiki.ubuntu.com/QATeam/ReleaseReports/OneiricAlpha1TestReport
[18:08] <jibel> The major issues discovered are:
[18:08] <jibel>  * unity-2d crashes which is a problem between gcc 4.6 and qt4-x11 violating strict aliasing rules. doko and didrocks are on it. Fix uploaded 1.5 hour ago.
[18:08] <jibel>  * gnome-user-share crash: need porting to gtk3: Fixed
[18:08] <jibel>  * nautlius background not redrawing: Fixed
[18:09] <jibel>  * missing windows buttons: Fixed
[18:09] <jibel>  * No USB support on beagle/beagleXM
[18:09] <jibel>  * RAID1 Test Failed on server. Need someone to confirm.
[18:09] <jibel>  * Ubiquity on Kubuntu failed
[18:09] <jibel> Very few installer and Unity bugs. But since most of us are testing in VMs unity received little testing compared to unity-2d.
[18:10] <jibel> The laptop tracker for Oneiric is opened.
[18:10] <jibel> https://lists.ubuntu.com/archives/ubuntu-qa/2011-June/001615.html
[18:10] <jibel> [LINK] https://lists.ubuntu.com/archives/ubuntu-qa/2011-June/001615.html
[18:10] <MootBot> LINK received:  https://lists.ubuntu.com/archives/ubuntu-qa/2011-June/001615.html
[18:10] <jibel> Time to test alpha 1 on real iron.
[18:10] <jibel> Thanks to primes2h for coordinating this effort.
[18:10] <jibel> Alpha 2 testing will start on July 5th (https://wiki.ubuntu.com/OneiricReleaseSchedule)
[18:10] <jibel> Followed by a week of ATI/nVidia proprietary driver testing
[18:10] <jibel> and 10.04.3 the week after.
[18:11] <jibel> that's all from me
[18:11] <charlie-tca> o/
[18:11] <jibel> any question ?
[18:11] <jibel> charlie-tca, i'm all ears
[18:11] <charlie-tca> general information under community testing.
[18:11] <charlie-tca> Xubuntu seeded lightdm as default on the cd today
[18:11] <charlie-tca> We will be giving a pretty good test
[18:12] <patrickmw> woot!
[18:12] <charlie-tca> ..
[18:13] <bdmurray> thanks jibel
[18:13] <bdmurray> [TOPIC] Automated/Systems Testing
[18:13] <MootBot> New Topic:  Automated/Systems Testing
[18:13] <patrickmw> hello
[18:13] <patrickmw> Kernel SRU:
[18:13] <patrickmw> - dbench ready in kernel sru ppa
[18:13] <patrickmw> - ltp in progress
[18:13] <patrickmw> - yet to be completed: tbench, signaltest, tiobench, qrt
[18:13] <patrickmw> - initial process defined for daily sru kernel testing vs release testing
[18:13] <patrickmw> * Started reviewing ubuntu-server-iso-test project to locate
[18:13] <patrickmw>  entry points for implementing kernel sru testing reqs
[18:14] <patrickmw> Package testing:
[18:14] <patrickmw> - collected ~60 packages from engineering teams
[18:14] <patrickmw> - started adding active development branches to daily builds.  premliminary results are showing no successful test executions (for package containing tests).  after digging a bit, some of the 'test' dirs have updated timestamps that several years back.
[18:14] <patrickmw> questions?
[18:15] <bdmurray> thanks patrickmw
[18:15] <bdmurray> [TOPIC] Engineering Team Bug Status
[18:15] <MootBot> New Topic:  Engineering Team Bug Status
[18:16] <bdmurray> pedro_: how are things?
[18:16] <pedro_> hola bdmurray, things are going good here
[18:16] <pedro_> i don't have much to share except for
[18:16] <pedro_> the bug day we're running tomorrow: https://wiki.ubuntu.com/UbuntuBugDay/20110609
[18:17] <pedro_> Nautilus is our next target and we already have a person smashing bugs like crazy (thanks brendan)
[18:17] <pedro_> so please join us if you wanna learn a bit more about nautilus and how to perform bug triage , as always we'll be at #ubuntu-bugs
[18:17] <bdmurray> wow, that's great!
[18:17] <pedro_> ..
[18:18] <bdmurray> This past week I wrote an update-manager apport hook which has landed in Oneiric
[18:19] <bdmurray> I also got some fixes in apt which will prevent some apport-package bug reports from being filed and add in /var/log/apt/history.log to the apport-package bug reports which will provide some more context for what the user was doing
[18:19] <bdmurray> Depending on how both of those work out in Oneiric I plan on SRU'ing them to previous releases
[18:20] <jibel> bdmurray, yay
[18:20] <charlie-tca> Thank you, that always helps!
[18:20] <pedro_> nice :-)
[18:20] <bdmurray> I've also been working with arsenal to gather bug stats for packages related to foundations-bugs
[18:21] <bdmurray> ..
[18:21] <bdmurray> [TOPIC] Other Topics
[18:21] <MootBot> New Topic:  Other Topics
[18:22] <bdmurray> are there are other topics to discuss today?
[18:23] <bdmurray> okay then on to the last item
[18:24] <bdmurray> [TOPIC] Next Chair
[18:24] <MootBot> New Topic:  Next Chair
[18:25] <bdmurray> patrickmw: perhaps you'd be interested?
[18:25] <patrickmw> some of us will be in London next week and might be available
[18:25] <patrickmw> including me
[18:26] <patrickmw> I will accept the following week :)
[18:26] <bdmurray> pedro_: then maybe you? ;-)
[18:26] <pedro_> sure :-)
[18:26] <patrickmw> thanks, pedro_
[18:26] <pedro_> no problem
[18:27] <bdmurray> pedro_: and let's not let patrickmw off the hook next week!
[18:27] <patrickmw> lol
[18:27] <bdmurray> [ACTION] pedro to chair next meeting on 2011-06-15
[18:27] <MootBot> ACTION received:  pedro to chair next meeting on 2011-06-15
[18:27] <bdmurray> #endmeeting
[18:27] <MootBot> Meeting finished at 12:27.
[18:27] <bdmurray> Thanks everyone
[18:27] <pedro_> heh
[18:27] <jibel> thanks bdmurray
[18:28] <pedro_> thanks bdmurray
[18:28] <patrickmw> you rock, bdmurray
[18:28] <charlie-tca> thank for chairing, bdmurray
[21:01] <apachelogger> good morning everyone
[21:01] <apachelogger> who's here for the kubuntu meeting?
[21:01] <DarkwingDuck> o/
[21:01] <ulysses> \o
[21:02] <yofel_> o/
[21:02] <fabo> o/
[21:03] <apachelogger> ScottK, neversfelde: council ping :P
[21:03] <ScottK> Hello
[21:03] <neversfelde> Hi
[21:04] <apachelogger> I think we should be starting with the new council, DarkwingDuck is going to join us as a new member and "replacing" (for lack of a better word) rgreening.
[21:05]  * DarkwingDuck waves
[21:05] <apachelogger> I'd like to take the opportunity and thank Rod for his work on the Kubuntu Council over the past 2 years :)
[21:06] <ScottK> +1
[21:06] <neversfelde> +1
[21:06] <ScottK> apachelogger: They are about the same size, so I think replacing is fine.
[21:06] <apachelogger> lol
[21:07] <DarkwingDuck> +1
[21:07] <DarkwingDuck> :P
[21:07] <apachelogger> moving on to memberships... as I cannot get hold of rbelem and c2tarun, perhaps fabo wants to start
[21:07] <fabo> sure
[21:07] <fabo> https://wiki.kubuntu.org/FathiBoudra
[21:08] <fabo> https://launchpad.net/~fboudra
[21:09] <fabo> I had previously Kubuntu membership (expired now)
[21:09] <apachelogger> fabo: I suppose it only expired recently?
[21:09] <fabo> mostly active these days on Debian side as Qt/KDE maintainer
[21:10] <fabo> apachelogger: no, it's been since several months
[21:10] <fabo> but I wasn't much active on Ubuntu side
[21:11] <fabo> I'm going back to be active again
[21:11] <fabo> merging and helping on Qt/KDE issues
[21:11]  * ScottK can confirm that.  fabo was active in helping review proposed Qt changes today and recently.
[21:12] <apachelogger> fabo: how do you like the debian <-> kubuntu relationship, anything that could be improved there?
[21:12] <fabo> it's also motivated by the fact that I'm working for Linaro and have interest to make KDE rocks on ARM
[21:12]  * apachelogger likes KDE on ArrM
[21:13] <fabo> apachelogger: we know each other definitely and IMO have a good collaboration
[21:13] <fabo> Debian Qt/KDE team doesn't move from his territory (channel) but the most impportant is here: communication, sharing work
[21:14] <apachelogger> fabo: what do you think sets Kubuntu apart from other KDE software using distributions?
[21:15] <fabo> apachelogger: innovation. Kubuntu takes some risk by sometime changing KDE defaults.
[21:16] <fabo> e.g rekonq
[21:16] <fabo> and other piece of software previously in kubuntu history
[21:17] <DarkwingDuck> fabo: you think that is good or indifferent?
[21:17] <ScottK> Well we're still holding onto userconfig and bambee is going to get it into kdeadmin.
[21:17] <fabo> deb packages too :) .oO(after being MeeGo packager for 1 year)
[21:18] <fabo> DarkwingDuck: it's good but as I said sometime risky (unity?)
[21:19] <DarkwingDuck> :) thankfully unity wasn't a risk *we* took.
[21:19] <fabo> it helps to differentiate from others
[21:19]  * DarkwingDuck nods
[21:21] <apachelogger> any more questions?
[21:22]  * ScottK votes +1.
[21:22] <DarkwingDuck> +1
[21:22] <apachelogger> +1
[21:22] <neversfelde> +1
[21:22] <apachelogger> fabo: congrats, welcome back :)
[21:22] <fabo> thanks for your support!
[21:22] <neversfelde> fabo: wb
[21:23] <DarkwingDuck> welcome back fabo
[21:23] <ScottK> What's next?
[21:24]  * ScottK needs to switch use his phone for a bit.
[21:24] <apachelogger> making every council member an admin of the team as to not depend on JR so much
[21:24] <apachelogger> currently he is the only admin
[21:25] <apachelogger> advantages: other council members can add new members after election, other council members can accept team memberships
[21:25] <apachelogger> I feel latter is a frequent enough use case
[21:25] <apachelogger> thoughts?
[21:26]  * ScottK-droid waves.
[21:26] <apachelogger> ScottK-droid: did you get that last bit?
[21:26] <DarkwingDuck> i think its a good failsafe if anything else
[21:26] <ScottK-droid> Yes. Sounds good.
[21:26] <ulysses> valami bőrfejű
[21:27] <apachelogger> neversfelde: objections?
[21:28] <neversfelde> apachelogger: sounds good
[21:28] <apachelogger> ok, let's get Riddell_ to implement that then :)
[21:28] <DarkwingDuck> +1
[21:28] <apachelogger> staying ont he topic of team memberships: I propose making the kubuntu-members team invite only
[21:29] <apachelogger> currently the membership application process requires one to apply for membership there *and* add oneself to a meeting for membership grilling
[21:30] <apachelogger> while this makes it generally easy to make someone member (as we just need to accept the request on the team) it also enables people to apply without merit
[21:30]  * Quintasan is late
[21:30] <apachelogger> ever so often I clean out such pointless applications to the launchpad team, pointing people to the wiki page that describes the application process
[21:30] <apachelogger> which is quite the waste of time
[21:31] <apachelogger> if we made the team invite only, we could get rid of that while not really loosing anything
[21:31] <ScottK-droid> Ok
[21:32]  * Quintasan is not council but +1
[21:32] <DarkwingDuck> +1
[21:33] <neversfelde> +1
[21:35] <apachelogger> changed
[21:35] <apachelogger> Quintasan: perhaps you want to bring up your neon stuff before we dive into UDS?
[21:36]  * ScottK-droid suggests Rodrigo is probably pulling a Rodrigo and we should make him a member anyway.
[21:36] <DarkwingDuck> +1
[21:36] <apachelogger> +1
[21:36] <apachelogger> then again
[21:36] <apachelogger> ...
[21:36] <apachelogger> no grilling would be a bit unfair to others
[21:37] <maco> pulling a rodrigo?
[21:37] <DarkwingDuck> we know what he has done/is doing consistently
[21:37] <apachelogger> how about we just grill him randomly?
[21:37] <DarkwingDuck> ++
[21:37] <maco> apachelogger: im not sure id call what you lot gave me a "grilling" ... maybe toasting
[21:37] <ScottK-droid> Napping during sessions ..
[21:37] <apachelogger> some sort of applying heat anyway :P
[21:37] <Quintasan> uhhh
[21:38] <Quintasan> okay, so here is a quick idea, can we get Project Neon featured on kubuntu.org in some way?
[21:38] <apachelogger> DarkwingDuck, ScottK-droid, neversfelde: lets just try to get a quorum at a time where he is not pulling a rodrigo and vote then
[21:38] <DarkwingDuck> apachelogger: +1
[21:39] <Quintasan> apachelogger: I can try calling him :P
[21:39] <apachelogger> Quintasan: if you could define the way you imagine it woudl be more discussable
[21:39] <ScottK-droid> Ok
[21:40] <DarkwingDuck> Quintasan: you mean a writeup/news blurb? or, a what is/how to?
[21:40] <Quintasan> DarkwingDuck: yofel is already doing a monthly write up on what have we done in PN
[21:41] <Quintasan> maybe we can somehow pull it into Feature Tour?
[21:41]  * Quintasan thinks it is somehow risky
[21:42] <Quintasan> or under the community tab
[21:42] <ScottK-droid> Not feature tour.
[21:42] <ScottK-droid> Community sounds good.
[21:42]  * apachelogger notes that the new site will have a section for development related stuff, perhaps it might be suitable there
[21:43] <Quintasan> or just stick "Adventurous users might want to try Project Neon to experience the bleeding edge features that KDE has to offer" to the end on new KDE packages announcement
[21:44] <Quintasan> apachelogger: Oh, cool, if we ever get a new site ;)
[21:44] <DarkwingDuck> we will. :) its on my todo from UDS
[21:44] <Quintasan> cool
[21:44] <yofel> yay
[21:44] <apachelogger> I think community should be good for now
[21:44] <neversfelde> Quintasan: what's the advantage featuring neon on kubuntu.org?
[21:44] <ScottK-droid> I like community for now and devel on the new site.
[21:45] <apachelogger> AS LONG AS we make it very clear that it might be breaking stuff
[21:45] <neversfelde> apachelogger: ++1
[21:45] <ScottK-droid> Definitely
[21:45] <Quintasan> neversfelde: We can attract people who want to work on KDE (and Kubuntu therefore)
[21:46] <DarkwingDuck> so, build it into the new site.
[21:46] <neversfelde> our target audience are beginners and every developer should be able to find neon without having it on the website?
[21:47] <ScottK-droid> When we have on.
[21:47] <ScottK-droid> One
[21:47] <apachelogger> neversfelde: that requires the developer to actually think of the possibility of having a thing like neon
[21:47] <Quintasan> I was about to write that
[21:48] <apachelogger> Also, if you look for kubuntu nightly you will find the old neon stuff
[21:48] <claydoh> sorry I'm late
[21:48] <Quintasan> and, we do not have anything else apart from ProjectNeon on w.k.o
[21:48] <neversfelde> apachelogger, Quintasan: it was mentioned at least on prolinux
[21:48] <Quintasan> What is that?
[21:48] <apachelogger> german linux news website
[21:48] <DarkwingDuck> ill do a writeup on it as well
[21:49] <Quintasan> :O
[21:49] <apachelogger> neversfelde: yet that did not help anything recent get on the first page of google search for kubuntu nightly kde
[21:49] <Quintasan> Where, where, I want to see :P
[21:50] <apachelogger> http://www.pro-linux.de/news/1/16807/kde-sc-taeglich-aktuell-mit-projekt-neon.html
[21:50] <claydoh> is it easy to test out individual neon bits while in a normal desktop?
[21:51] <yofel> :O
[21:51] <Quintasan> claydoh: nope, we install everything in /opt and have a separate X session entry
[21:51] <claydoh> i.e kmail2
[21:51] <Quintasan> so we don't break your stable KDE settings
[21:51] <neversfelde> users do not read warnings :) never
[21:52] <claydoh> no, they do not. I sure don't
[21:52] <ScottK> Well, after a certain point that's on them.
[21:52] <Quintasan> claydoh: That's why we separated neon from normal kde install :P
[21:52] <ScottK> I'd say let's wrap this up.
[21:53]  * ScottK says +1 for including and leaving it up to the appropriate web minion to figure out exactly where.
[21:53] <DarkwingDuck> +1
[21:53] <Quintasan> +1
[21:53] <apachelogger> +1 iff implications are made clear
[21:53] <neversfelde> 0
[21:53] <apachelogger> even though users will not read them :P
[21:53] <claydoh> +1 for whatever it is that i missed :)
[21:54] <apachelogger> next up: UDS results, is anyone prepared for that?
[21:54] <DarkwingDuck> good, im glad you volunteered claydoh
[21:54] <apachelogger> cause I fell asleep while working on it on the train home from kde sprint ^^
[21:54] <DarkwingDuck> i *was* then my hdd failed
[21:54] <apachelogger> right, let's make something up then ^^
[21:54] <claydoh> DarkwingDuck: what did i get volunteered for? does it involve cookies?
[21:54] <ScottK> https://wiki.kubuntu.org/Kubuntu/Todo
[21:54] <ScottK> It's pretty much all there.
[21:55] <apachelogger> right
[21:55] <DarkwingDuck> claydoh: yup. :P:P
[21:55] <apachelogger> accessibiity IMHO is very doable, very important, very nice and very important, also it is important
[21:55] <claydoh> I can't eat cookies anymore :( or not many
[21:55] <ScottK> So if anyone doesn't like what's there, now is the time to speak up.
[21:55] <DarkwingDuck> cept the wiki/h.k.o stuff. need to put that up there
[21:55] <ScottK> True.
[21:56] <ScottK> DarkwingDuck can fix that later though.
[21:56] <DarkwingDuck> ill get that up when my lappy works
[21:56]  * Quintasan got his share of workload and has no complaints
[21:56] <apachelogger> community is all very awesome and we need to blog, blog and also blog, eventually blogging might also be a good thing
[21:56] <ScottK> apachelogger: Our accessibility dev has been slightly distracted this week with making it so ubiquity-kde can actually install stuff.
[21:57] <Quintasan> apachelogger: tomorrow, I'm having last two tests, so I can do some bloggin about uds and stuff
[21:57] <maco> howdy
[21:57] <claydoh> we need to put topics into a hat, so that everyone can draw one and blog on it
[21:57] <apachelogger> so we should find someone to take care of ubiquity-kde so that our accessibility dev can work on important things :)
[21:57]  * Quintasan hands cookies to maco
[21:57] <apachelogger> Quintasan: uds is yesterday's news unless you have something terribly awesome :P
[21:57] <ScottK> apachelogger: You scared the pythonic people so badly with your bashing they've all gone but maco.
[21:57] <maco> apachelogger: eh im going to be having my hands in ubiquity *anyway* since part of the a11y stuff is making ubiquity setup a11y tools by default if theyre used during install
[21:58] <maco> i cant really make ubiquity install and setup that stuff at the end if i cant get to the end of ubiquity
[21:58] <JontheEchidna> Hey guys, sorry I'm late. Was playing videogames in Windows, so nobody was able to tell me that my in-my-head UTC conversion was off. :(
[21:58] <apachelogger> ScottK: time to port ubiquity to a sane language then :P
[21:58] <Quintasan> apachelogger: yeah, really, I should have written something while I was on a plane :P
[21:58] <Quintasan> JontheEchidna: sup, I was late due to that as well :P
[21:58]  * apachelogger files a bug
[21:58] <apachelogger> so
[21:59] <ScottK> apachelogger: python3 port is planned.
[21:59] <apachelogger> council is all green, which is awesome
[21:59] <Quintasan> Oh God.
[21:59] <JontheEchidna> and also I am being told that my sister has a piano recital that I have to go to in a few minutes
[21:59] <apachelogger> Thanks to ScottK for handling the elections so smoothly!
[21:59] <Quintasan> yeah, good job
[21:59] <ScottK> Let's have a quick +1 from the council on specs then.
[21:59] <ScottK> Thanks.
[21:59] <JontheEchidna> +1 on specs, no objections here
[21:59] <apachelogger> +1
[21:59] <DarkwingDuck> +1
[22:00] <ScottK> neversfelde: ?
[22:00] <ScottK> Riddell_: ?
[22:00] <neversfelde> +1
[22:00] <neversfelde> sorry, still working
[22:00] <ScottK> No problem.
[22:00] <apachelogger> jr does not seem to be around
[22:00] <JontheEchidna> 4 is a majority though
[22:00] <ScottK> Nope.  Just thought I'd try again.
[22:00] <ScottK> Yep.
[22:00] <Quintasan> apachelogger: another idea, do we want plasma-active in neon?
[22:00] <apachelogger> Quintasan: lets talk about this later
[22:01] <apachelogger> for now let's move to a related topic
[22:01] <ScottK> Quintasan: I think up to the Neon devs.  Not a matter for Kubuntu meeting.
[22:01] <apachelogger> burndown charts!
[22:01] <ScottK> No
[22:01] <apachelogger> like: http://status.chrisjohnston.org/ubuntu-oneiric/group/topic-oneiric-edubuntu.html
[22:01] <apachelogger> I, as chart fanboi, find them awesome
[22:01] <ScottK> Pointless bureacracy that don't measure anything useful.
[22:02] <apachelogger> ScottK: bureacracy?
[22:02] <ScottK> paperwork
[22:02] <Quintasan> PROTIP: We would have someone actually make that work
[22:02] <apachelogger> ScottK: as far as I know the only thing we'd have to change is use the spec whiteboards for TODO tracking
[22:02] <apachelogger> rather than the wiki page
[22:02] <JontheEchidna> As long as it's just generating graph porn, then I am ok with that
[22:03] <apachelogger> which quite frankly might not be a bad idea, as the todo is getting longer and longer and longer every time
[22:03] <apachelogger> combined with the crappyness of the wiki it makes editing that page a bit of an adventure IMO
[22:03]  * Quintasan wonders how are those graphs actually beneficial
[22:03]  * ScottK needs to go.
[22:03] <DarkwingDuck> im +1 using spec whitboards vice wiki todo
[22:04] <DarkwingDuck> then again, im a fanboi like apachelogger
[22:04] <Quintasan> Hmmm, true, while they may have no benefits at all they would be faster than w.k.o for sure
[22:04] <Quintasan> Gotta love 500 erros on wiki
[22:04] <DarkwingDuck> uggh
[22:05] <DarkwingDuck> plus moin moin == -1
[22:05]  * apachelogger notes that there is implicit advantage from them charts, which is you can point people there and go "uhhh, we are so awesome and efficient and get work done so quickly"
[22:05] <JontheEchidna> If somebody is willing to make pretty graphs and policy will not be driven by them, I'd say go ahead
[22:05] <Quintasan> or people can go there and go "wtf, those derps at #kubuntu-devel are doing nothing"
[22:05] <DarkwingDuck> tracking progress, tasks, its so much more efficent
[22:05] <apachelogger> JontheEchidna: I reckon there is a script for the graph creation
[22:06] <Quintasan> if the work is not progressing as smoothly as expected
[22:06] <apachelogger> also it ought to be possible to do it by parsing the wiki page: BUT the slowness of the wiki gets in the way there too
[22:06] <maco> Quintasan: or "woah, they're getting behind, i'd better be helpful!"  (...probably not)
[22:06] <apachelogger> ^^
[22:06]  * Quintasan thinks that never happens
[22:07] <Quintasan> and unfortunately never will
[22:07] <maco> yes, graph creation from wiki page TODOs is automated
[22:07] <maco> no no bad brain
[22:07] <DarkwingDuck> or, "how does a dozen people produce such quality work?"
[22:07] <maco> from *launchpad* is automated
[22:07]  * Quintasan is opposed to using wiki to generate this stuff
[22:07] <Quintasan> If we want it to show something at all then no wiki :P
[22:08] <apachelogger> is anyone strongly opposing the idea of using the lp spec whiteboards for todo tracking rather than the monolithic wiki page?
[22:09] <JontheEchidna> I sometimes browse the monolith looking for things to do
[22:09] <JontheEchidna> I would not like to see that go away
[22:09]  * maco is asking jono/jcastro how to make burndown charts from blueprints
[22:09] <Quintasan> not really, I don't care how the work list is stored as long as we get stuff done
[22:09]  * Quintasan could even use Etherpad if we really had to
[22:09] <DarkwingDuck> lol
[22:09] <Quintasan> s/we/he
[22:09] <apachelogger> https://wiki.ubuntu.com/WorkItemsHowto#Generator scripts
[22:09] <JontheEchidna> I would be willing to maintain the monolithic wiki todo if nobody wants to
[22:10] <apachelogger> JontheEchidna: better idea
[22:10] <apachelogger> ....
[22:10] <apachelogger> since we can probably access the whiteboards using lp api
[22:10] <maco> if you look at http://people.canonical.com/~platform/workitems/oneiric/canonical-community.html you'll see that it does list what specs need work
[22:10] <apachelogger> we could just have a cron job run a script that gets the data and puts it in a monolithic html page
[22:11] <apachelogger> oh
[22:11] <apachelogger> JontheEchidna: perhaps html-report mentioned on the link I pasted is doing just that
[22:11] <apachelogger> "html-report generates a HTML report with a by-blueprint, by-assignee, and by-workitem list."
[22:11] <JontheEchidna> cool
[22:11] <Quintasan> brb
[22:11] <DarkwingDuck> i like that better then the wiki
[22:12] <apachelogger> +1
[22:12] <DarkwingDuck> +1
[22:12] <JontheEchidna> shiny
[22:13] <apachelogger> neversfelde opinions on this?
[22:14] <apachelogger> one question that remains: do we want to switch now (as in for oneiric already) or for oneiric+1
[22:15] <JontheEchidna> if somebody wanted to, they could use this cycle as a test, and have the new stuff concurrent with the current stuff, then switch in +1
[22:15] <JontheEchidna> imo
[22:15] <DarkwingDuck> +1
[22:15] <Quintasan> rbelem: \o/
[22:15] <DarkwingDuck> rbelem: welcome
[22:15] <rbelem> :-D
[22:15] <apachelogger> sounds good to me, let's do that, given I find someone to do the sync ^^
[22:15] <DarkwingDuck> :D
[22:16] <Quintasan> apachelogger: Grill a Rodrigo
[22:16] <rbelem> hahah :-D
[22:16] <neversfelde> apachelogger: no :) because I could not dollow the discussion in the last minutes
[22:16] <apachelogger> now that rbelem is here, let's continue with his membership app before he falls asleep :P
[22:16] <DarkwingDuck> lol
[22:16] <apachelogger> neversfelde: you'll like it :P
[22:16] <DarkwingDuck> i think we lost ScottK though
[22:16] <rbelem> sorry for being so late
[22:16] <rbelem> :-(
[22:17] <apachelogger> DarkwingDuck: I might be mistaken but for membership we only need 3 acks
[22:17] <neversfelde> apachelogger: kk
[22:17] <DarkwingDuck> apachelogger: well, scott already voted
[22:17] <apachelogger> ah, true
[22:17] <apachelogger> + JontheEchidna is still here :P
[22:17] <apachelogger> so
[22:17] <apachelogger> ...
[22:17] <apachelogger> https://wiki.ubuntu.com/RodrigoBelem https://launchpad.net/~rbelem
[22:17] <DarkwingDuck> lets do it!
[22:17] <apachelogger> rbelem: can you tell us a bit about yourself and your work on kubuntu
[22:18] <rbelem> oki
[22:18] <rbelem> I'm founding member of ubuntu brasil
[22:19] <rbelem> i done lot's of loco team stuff in the begining
[22:19] <rbelem> *did
[22:20] <JontheEchidna> gotta go, but +1 pre-emptively
[22:20] <rbelem> two years ago i started writing the ubuntu mobile book
[22:20]  * ScottK-droid is +1 on rbelem
[22:21] <rbelem> and end up here :-D
[22:21] <DarkwingDuck> rbelem: still working on kubuntu-mobile?
[22:21] <rbelem> DarkwingDuck, yup
[22:22] <apachelogger> rbelem: what are you future plans for kubuntu?
[22:22] <rbelem> my main goal is to have kubuntu running on mobile phones and tablets
[22:23] <rbelem> and contribute to kde as an ubuntu member
[22:23] <apachelogger> are we going to achieve world domination with it?
[22:24] <apachelogger> mobile and tablet stuff that is
[22:24] <rbelem> yup :-D
[22:24] <apachelogger> awesome :D
[22:24] <DarkwingDuck> rbelem: do you have it running on yourmilestone yet?
[22:24] <DarkwingDuck> *your milestone
[22:24] <rbelem> and i want to write a second edition of the book
[22:24] <neversfelde> +1 on rbelem
[22:24] <neversfelde> sorry, have to leave
[22:24] <apachelogger> rbelem: what qualifies you best for becoming a kubuntu member?
[22:25] <rbelem> the work i've been doing with filesharing
[22:25] <Quintasan> Yeah, thumbs up for that
[22:25] <rbelem> and now the first stable release that we will do
[22:25]  * Quintasan hands rbelem cookies
[22:25] <rbelem> :-D
[22:25] <DarkwingDuck> I'm +1
[22:26] <apachelogger> you have been around for ages it seems, my final question is: what took you so long to consider membership? :P
[22:26] <Riddell_> good evening
[22:26] <DarkwingDuck> Hey JR
[22:26] <Quintasan> \o
[22:26] <rbelem> apachelogger, i already was a member some time ago
[22:27] <apachelogger> rbelem: so you expired?
[22:27] <rbelem> apachelogger, nope, i had i fight with another brazilian ubuntu member
[22:27] <rbelem> he said that i was doing nothing
[22:28] <rbelem> so i decided that i would apply again when i have some relevant contributions
[22:28] <apachelogger> I see
[22:28] <apachelogger> well
[22:29]  * Quintasan thinks filesharing is relevant enough
[22:29] <DarkwingDuck> and the work on Mobile
[22:29] <apachelogger> I for one do not only believe that there are plenty of contributions but they are also incredibly awesome and important and relevant \o/
[22:29] <apachelogger> +1 for being awesome
[22:29] <rbelem> :-D
[22:29] <DarkwingDuck> +1 for membership
[22:29] <Quintasan> rbelem: Looks like you're in :P
[22:29] <DarkwingDuck> :)
[22:29] <apachelogger> Riddell_: you might want to throw in a +1 at this point
[22:29] <Quintasan> +1 from ScottK and JontheEchidna as well
[22:30] <DarkwingDuck> :D
[22:30] <Riddell_> rbelem for membership?
[22:30] <Riddell_> +1 from me
[22:30] <apachelogger> yes
[22:30] <Quintasan> :D
[22:30] <apachelogger> 6/6 votes in favor of membership :D
[22:30] <neversfelde> +1
[22:30] <apachelogger> rbelem: welcome
[22:30] <DarkwingDuck> There we go.
[22:30] <DarkwingDuck> Welcome rbelem
[22:30] <neversfelde> welcome rbelem
[22:30] <rbelem> thank you very much guys
[22:30] <rbelem> :-D
[22:30]  * Quintasan throws confetti at rbelem
[22:31] <rbelem> that's really important to me :-)
[22:31] <DarkwingDuck> apachelogger: I have to run... Don't forget about tasking Riddell_ with the LP Stuff. :P:P
[22:31] <ScottK-droid> Are we done?
[22:31] <apachelogger> yes, I am too tired to do UDS-post discussion stuff, we can do that on the ML
[22:31] <apachelogger> thank you everyone for attending!
[22:31] <rbelem> :-D
[22:31] <apachelogger> Riddell_: please make every kubuntu council member an admin of kubuntu council as per voting earlier
[22:32] <Riddell_> ok
[22:32] <apachelogger> Riddell_: no rush though, whenever you find the time :)
[22:32]  * Quintasan goes back to books
[23:38] <valorie> eek, did I miss the meeting?
[23:38] <valorie> damn it
[23:38] <valorie> ah, my phone is dead, thus no alarm for it