[00:24] <xnox> interesting meeting =)
[00:58] <freeflying> I missed it :)
[12:46]  * smartboyhw wonders why the topic is AOB....
[12:46] <ogra_> likely because someone forgot to close their meeting
[12:47] <soren> That would be pitti.
[12:47] <smartboyhw> oops
[12:47] <ogra_> yeah, the backlog says so
[12:48] <soren> I've just poked him about it.
[12:48] <soren> #endmeeting
[12:48] <soren> Yeah, he has to do it.
[12:48] <soren> Was worth a try, though :)
[13:01] <xnox> #endmeeting
[13:02]  * xnox failed at highjacking pitti's nickname
[13:02] <smartboyhw> Eh doesn't work:P
[13:19] <pitti> #endmeeting
[13:19] <meetingology> Meeting ended Tue Feb 19 13:19:23 2013 UTC.
[13:19] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-18-21.07.moin.txt
[13:19] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-18-21.07.html
[13:19] <smartboyhw> Clap Clap Clap
[13:19] <pitti> sorry about that
[13:19] <pitti> longest TB meeting EVAR
[13:20] <soren> No harm done.
[13:20] <smartboyhw> :)
[13:20] <soren> smartboyhw just wodered why the topic said "AOB".
[13:20] <smartboyhw> soren, Any Other Business
[13:20] <soren> Sure, I know.
[13:21] <ogra_> now you know twice ;)
[13:22] <smartboyhw> lol
[13:22] <ogra_> soren, its like counters on websites ... twice is better ;)
[14:54] <AlanBell> fwiw anyone with a member cloak can op up in this channel and it listens to operators as if they were chair
[14:55] <AlanBell> so you can get ops by /msg chanserv op #ubuntu-meeting and then #endmeeting even if it wasn't your meeting to end
[14:55] <AlanBell> soren: ogra_ xnox ^^
[14:56] <xnox> awesome.
[16:01] <jamespage> o/
[16:01] <m_3> hola
[16:01] <yolanda> hi
[16:02]  * Daviey has to offer his apologies, clashing event.
[16:02] <Daviey> smoser: chairing?
[16:05] <arosales> hello
[16:06] <smoser> i can chair.
[16:06] <smoser> sorry.
[16:06] <smoser> here now.
[16:06] <smoser> #startmeeting ubuntu-server
[16:06] <meetingology> Meeting started Tue Feb 19 16:06:13 2013 UTC.  The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:06] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:06] <smoser> https://wiki.ubuntu.com/ServerTeam/Meeting
[16:06] <smoser> #topic Review ACTION points from previous meeting
[16:07]  * smoser looks for logs to get action items
[16:07] <smoser> http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-16.01.html
[16:08] <smoser> Daviey, you're listed there as send request for testing
[16:08] <smoser> did we send? i dont think so.
[16:08] <Daviey> smoser: sort of "no".
[16:08] <smoser> we did release a alpha-2 cloud images . (http://cloud-images.ubuntu.com/releases/13.04/alpha-2/)
[16:08] <smoser> hm...
[16:09] <smoser> ok, so we'll re-action that? i really do think we should make an effort there.
[16:09] <Daviey> +1
[16:09] <smoser> #ACTION Daviey send call for alpha-2-ish testing
[16:09] <meetingology> ACTION: Daviey send call for alpha-2-ish testing
[16:10] <smoser>     ACTION: jamespage to milesone documentation updates (zul, 16:38:45)
[16:10] <smoser> jamespage, ^
[16:10] <jamespage> not done yet
[16:10] <smoser> #ACTION: jamespage to milesone documentation updates [carryover]
[16:10] <meetingology> ACTION: : jamespage to milesone documentation updates [carryover]
[16:10] <smoser> #topic Raring Development
[16:11] <smoser> release tracking: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server
[16:11] <jamespage> action was actually to ensure that any doc updates in BP's are milestoned appropriatly
[16:11] <smoser> jamespage, ah. ok. do you need help there?
[16:12] <smoser> ok. so release tracking link up there. maas is the biggest thing. and the qemu-kvm.
[16:12] <smoser> hallyn, do you have a handle on the qemu-kvm bug ?
[16:12] <jamespage> smoser, nah - its OK - I'll do it
[16:12] <smoser> bug 1092715	
[16:12] <jamespage> that one is killing me slowly
[16:13] <hallyn> smoser: yes, i just need to talk to pitti again
[16:13] <hallyn> smoser: there is a real bug in udev,
[16:13] <smoser> hallyn, please do... that is a real pain
[16:13] <hallyn> but i want to just work around it
[16:13]  * smoser is tired of 'chmod 666 /dev/kvm' 
[16:13] <hallyn> all right, i'll talk to him today or tomorrow
[16:13] <hallyn> (depending on his tz)
[16:13] <jamespage> lol
[16:13] <smoser> roaksoax, maas and release tracking ?
[16:14] <smoser> err... sru. i think we're nearing it.
[16:14] <smoser> hm.. we'll maybe come back to that.
[16:14] <roaksoax> smoser: well, bigjools had to adapt a patch to django so that it would be done in the maas side instead. But since I just learned he is with leave... then we'll have to ping someone else on the MAAS team
[16:15] <roaksoax> s/to django/for django/
[16:15] <smoser> roaksoax, ok. please do follow up there. i'm sure we can find someone on maas team to accomplish.
[16:15] <smoser> blueprints: http://status.ubuntu.com/ubuntu-raring/group/topic-raring-servercloud-overview.html
[16:15] <roaksoax> smoser: other than that, is merging the latest fixes we have left for it
[16:16] <smoser> please just be responsible with your blueprints. try to get them into a state that reflects where they actually are, remember that feature freeze is coming up, and ping jamespage, daviey, or I if you are concerned about their status.
[16:16] <smoser> release schedule at https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule . feature freeze is March 7.
[16:17] <smoser> #Ubuntu Server Team Events
[16:17] <smoser> #topic Ubuntu Server Team Events
[16:17] <smoser> anyone have anything here ?
[16:18] <smoser> i think that jcastro is going to scale this week.
[16:18] <smoser> http://www.socallinuxexpo.org/
[16:18] <smoser> and talking ther eabout juju.
[16:18] <smoser> anyone have anything else ?
[16:19] <smoser> ok. moving on.
[16:19] <smoser> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:20] <smoser> this topic should probably be up for consideration on removal. doesn't seem to have been very busy recently.
[16:20] <smoser> moving on
[16:20] <smoser> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:20] <smb> Finally tracked down an elusive Xen bug that was paining Precise
[16:20] <smb> but potentially lurked around till now. That is currently going
[16:20] <smb> upstream and then back (bug 1011792).
[16:20] <smb> Not sure I got more beside my struggles with libvirt. ;-P Any
[16:20] <smb> questions?
[16:20] <smb> ..
[16:21] <smoser> smb, i would love for you to fix my interest in providing 'console=ttyS0' everywhere on command lines and have that not screw things up when there is not ttyS0
[16:22] <smoser> most recently causing issues at 1122245
[16:22] <smb> smoser, I could imagine our method of fixing your interest might be incompatible...
[16:22] <hallyn> put the bat away....
[16:22] <smb> :)
[16:23] <smb> The problem seemed that the kernel itself has no issue... it is hard to tell user-space what to use...
[16:23] <smoser> smb, well, any ways i dream of fixing it from user-space are basically doomed.
[16:23] <smoser> as the kernel has this nice buffer on writes to /dev/console
[16:23] <smoser> so things work for a while, and then randomly faily.
[16:24] <smoser> so, its really toufh to come up with a way that user space could "fix" the situation  or work around it.
[16:25] <smoser> so, my request is really that you just try to think of a way that writes to /dev/console could never fail.
[16:25] <smb> smoser, I try to think on it. Though not promising too much
[16:26] <smoser> k
[16:26] <smoser> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:26] <smoser> (smb, thank you for being prepared for your section).
[16:27] <smoser> rbasak not present, moving on.
[16:28] <smoser> #topic Open Discussion
[16:28] <smoser> o. i have one topic here, that is "QA".
[16:28] <smoser> in 2 repsects
[16:28] <smoser> a.) should we change/remove/update that section of our meeting ? it seems not to have much in it.
[16:29] <smoser> b.) are we having a call for testing, and what should that mean ? what manual tests do we have around still ? what things should we ask people to test?
[16:29] <smoser> anyone have comments on that? i'm largely talking to myself today.
[16:29] <jamespage> most 'ISO' tests are now automated
[16:29] <jamespage> if we where going to call for testing I would think two things would be good
[16:30] <jamespage> 1) write dep-8 tests - we have a big list
[16:30] <jamespage> 2) exercise stuff off-piste - generalist testing
[16:30] <roaksoax> I think 1) makes lots of sense
[16:31] <roaksoax> to get the community engadged
[16:31] <hallyn> should we invite gema for this section?
[16:31] <hallyn> or have jamespage represent?
[16:32] <roaksoax> jamespage: represent!!
[16:32] <jamespage> hallyn, tbh some of the reason the dep-8 bp is going nowhere is that I'm focussed elsewhere
[16:32] <roaksoax> :)
[16:32] <hallyn> jamespage: perhaps we should be discussing that
[16:32] <arosales> smoser: m_3 will also join jcastro at scale11x this week.
[16:33] <hallyn> though of course, i doubt we'll find anyone not swamped right now
[16:33] <m_3> yeah, wasn't gonna correct anything
[16:33] <hallyn> but maybe the bp needs a team of 2-3 ppl
[16:33] <jamespage> yeah - its just down the priority list
[16:34] <smoser> ok. so in our "requeest for testing" we should generally ask people to test either ISO or cloud images and try to accomplish their generic specific work loads.
[16:35] <jamespage> hallyn, I think its a good point - if we are going to move to a rolling release inbetween LTS releases of server then knowing when stuff is bust is really importnat
[16:35] <smoser> hoping to have things fallout that are not found in our testing. and also request that if they are able to add dep-8 tests, that'd be wonderful.
[16:35] <jamespage> smoser, I think that would be great!
[16:35] <m_3> should we add in requests for charm testing (i.e., /tests dir in each charm)?
[16:35] <m_3> or is that best left separate?
[16:36] <smoser> i would leave that out of "Ubuntu server raring call for testing", m_3.
[16:36] <smoser> i dont think begging for such things is bad, but just that it doesn't fit there.
[16:36] <m_3> ack
[16:36] <smoser> jamespage, so do you think we should move you to the name in '()' for qa section ?
[16:37] <jamespage> smoser, no - I want direct engagement with the QA team in this meeting
[16:37] <jamespage> its been lacking and I think we a suffering for it
[16:37] <smoser> ok. so can you take an action there ? or do you want me to draft a mail requesting participation
[16:37] <jamespage> smoser, but I'll take an action to go discuss with gemma
[16:37] <smoser> #action jamespage discuss QA representation at Server TeamMeeting
[16:37] <meetingology> ACTION: jamespage discuss QA representation at Server TeamMeeting
[16:38] <smoser> i'm going to #endmeeting if noone has any objections?
[16:38] <roaksoax> i do
[16:38] <roaksoax> have something to bring up
[16:38] <roaksoax> I've been considering dropping HA support for OCFS2 with pacemaker/corosync. The soon to be released pacemaker 1.1.9 has improved performance for large clusters (up to 16 node clusters). However, this requires corosync 2.X. Upgrading would mean dropping the support for OCFS2 in Pacemaker/Corosync because OCFS upstream has not updated its code to support the changes that have been made on the corosync side. From [1], we currently support Option 
[16:38] <roaksoax> [1]: http://theclusterguy.clusterlabs.org/post/34604901720/pacemaker-and-cluster-filesystems
[16:40] <smoser> roaksoax, i suggest raising on ubuntu-server and ubuntu-cloud
[16:40] <roaksoax> smoser: ack!
[16:40] <smoser> #topic Announce next meeting date, time and chair
[16:41] <smoser> next meeting is same time, same place, 7 days from now.
[16:41] <smoser>  Tuesday 2013-02-26 at 1600 UTC
[16:41] <smoser> chair will be the honorable hallyn.
[16:41] <arosales> smoser: thanks for chairing
[16:41] <smoser> #endmeeting.
[16:41] <meetingology> Meeting ended Tue Feb 19 16:41:40 2013 UTC.
[16:41] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-16.06.moin.txt
[16:41] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-16.06.html
[16:41] <jamespage> thanks smoser!
[16:42] <Daviey> thanks smoser
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <meetingology> Meeting started Tue Feb 19 17:00:18 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <cking> \o
[17:00] <henrix> o/
[17:00] <smb> \o
[17:00] <bjf> o/
[17:00] <sconklin> o/
[17:00] <sforshee> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing new to report this week
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team.html
[17:02] <ogasawara> || apw       || hardware-r-kernel-config-review       || 3 work items ||
[17:02] <ogasawara> ||           || hardware-r-delta-review               || 3 work items ||
[17:02] <ogasawara> ||           || foundations-r-secure-boot             || 1 work item  ||
[17:02] <ogasawara> ||           || foundations-r-aarch64                 || 1 work item  ||
[17:02] <ogasawara> ||           || foundations-r-upstart-user-session-enhancements || 1 work item ||
[17:02] <ogasawara> || ogasawara || hardware-r-kernel-config-review       || 2 work items ||
[17:02] <ogasawara> ||           || hardware-r-kernel-version-and-flavors || 2 work items ||
[17:02] <ogasawara> ||           || hardware-r-arm-kernel-maintenance     || 1 work item  ||
[17:02] <ogasawara> ||           || hardware-r-kernel-misc                || 1 work item  ||
[17:02] <ogasawara> || ppisati   || hardware-r-kernel-config-review       || 1 work item  ||
[17:02] <ogasawara> || smb       || servercloud-r-libvirt                 || 1 work item  ||
[17:02] <ogasawara> ||           || servercloud-r-xen                     || 2 work items ||
[17:02] <ogasawara> || rtg       || hardware-r-delta-review               || 1 work item  ||
[17:02] <ogasawara> The above summarizes the remaining work items owned by individuals on
[17:02] <ogasawara> our team for the rest of the 13.04 cycle.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Raring Development Kernel (ogasawara)
[17:02] <ogasawara> We have rebased the Raring kernel to the final upstream v3.8 release and
[17:02] <ogasawara> uploaded.  We also made a few misc config changes and added some i915
[17:02] <ogasawara> fixes.
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara>  * Raring:
[17:02] <ogasawara>   * Thurs Mar 07 - 13.04 Feature Freeze
[17:03] <ogasawara>   * Thurs Mar 21 - 13.04 Beta Freeze
[17:03] <ogasawara>   * Thurs Mar 28 - 13.04 Beta Release
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (henrix)
[17:03] <henrix> Currently we have 30 CVEs on our radar, with 2 CVEs added and 3 CVEs retired this week.
[17:03] <henrix> See the CVE matrix for the current list:
[17:03] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <henrix> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <henrix> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <henrix> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
[17:04] <henrix> Due to an high priority CVE, all the stable kernels are being respined this week.
[17:04] <henrix> Current opened tracking bugs details:
[17:04] <henrix>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <henrix> For SRUs, SRU report is a good source of information:
[17:04] <henrix>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <henrix> Future stable cadence cycles:
[17:04] <henrix>  * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:04] <henrix> Note: The week of March 28 is the week the last Hardy and Oneiric kernels will be built.
[17:04] <henrix> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Feb 19 17:05:06 2013 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-17.00.html
[17:22] <cprofitt> is anyone here for the Ubuntu Friendly meeting?
[17:28] <vibhav> cproffit: o/
[17:29] <SergioMeneses> cprofitt, o/
[17:30] <SergioMeneses> cprofitt, vibhav I think we can tall by mailing list
[17:30] <vibhav> Sure
[17:32] <cprofitt> hey vibhav
[17:32] <cprofitt> good to see you
[17:33] <vibhav> :)
[17:33] <cprofitt> we are in #ubuntu-quality right now if you want to join us there
[17:33] <vibhav> Sure
[17:33] <cprofitt> sorry that the meeting did not get off the ground this time around
[18:56] <notgary> Anyone here?
[18:59] <notgary> Anyone here?
[19:00] <druellan> Hi Chris
[19:01] <notgary> Hey Dario, how's it going?
[19:02] <druellan> Fine, but I've just got back from my holidays, and my clients are killing me with emails :P
[19:03] <notgary> Sounds like a whole load of fun :)
[19:03] <notgary> Is anyone else in here for the paper cuts meeting?
[19:04] <notgary> druellan: guess it's just you and me tonight :)
[19:05] <druellan> Haha, oh well
[19:05]  * BobJonkman is lurking
[19:05] <notgary> #startmeeting One Hundred Paper Cuts meeting for 19th Feb 2013
[19:05] <meetingology> Meeting started Tue Feb 19 19:05:51 2013 UTC.  The chair is notgary. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:05] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:06] <notgary> BobJonkman: The lurk away my friend. If you have anything to say, then just go ahead and say it. don;t worry about interrupting
[19:06] <BobJonkman> notgary: Thanx!
[19:06] <notgary> #meetingtopic Review of previous meeting minutes
[19:07] <notgary> #meetingtopic One Hundred Paper Cuts meeting for 19th Feb 2013
[19:07] <notgary> #topic Review of previous meeting minutes
[19:07] <notgary> That's better
[19:07] <notgary> The agenda for this meeting can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/19Feb2013
[19:08] <notgary> Item 1, review of the last meetings minutes
[19:08] <notgary> which can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/24Jan2013#Outcome
[19:08] <notgary> The first relevant part was Developer week
[19:09] <druellan> OH, I'm still supposed to talk about all thouse items?
[19:09] <notgary> Yep
[19:09] <notgary> they're on this weeks agenda though
[19:09] <notgary> so don't worry
[19:09] <druellan> No problem, carry on.
[19:10] <notgary> the original plan for Developer Week was to produce a couple of videos
[19:10] <notgary> One showing the user how to download and build the source for Rhythmbox
[19:10] <notgary> and another doing the same for Unity
[19:10] <notgary> Neither were done :P
[19:10] <notgary> which is what I was supposed to do.
[19:10] <notgary> :P
[19:11] <notgary> I'm going to put them off for the Global Jam next weekend
[19:11] <notgary> and try and get a Google+ Hanhout going with Jose, so people can watch them in real time and ask questions
[19:11] <druellan> Ubuntu communty on G+ is getting some traction now
[19:11] <notgary> We also decided we needed a more coherent strategy for attractting new contributors
[19:12] <notgary> I've noticed
[19:12] <notgary> :P
[19:12] <notgary> G+ seems to be setting some as well
[19:12] <notgary> but I digress :P
[19:13] <notgary> I had planned to reach out to Daniel Holbach to discuss some new ideas for getting people interested in contributing to Ubuntu, which I didm;t get round to doing
[19:13] <notgary> Jeez I'm bad at getting things done :P
[19:13] <notgary> The next item we decided on was to hold regular meetings
[19:13] <notgary> We didm;t do so well for the couple of weeks after that one, but hopefully this one we're in now will be the start of a new dawn for paper cuts meetings :)
[19:14] <druellan> well, about the per week meetings
[19:14] <notgary> Shoot
[19:14] <druellan> its good if you need to quickly be in touch with people
[19:14] <druellan> but is hard to promote, I mean, if you have a meeting too often you loose some traction
[19:15] <notgary> how so?
[19:15] <druellan> sorry, phone
[19:17] <notgary> What do you mean by 'lose some traction'? Do you think people will lose interest if we have too many meetings?
[19:18] <notgary> druellan: you still there?
[19:18] <druellan> I'm here, sorry. Yes, I believe that cen be the case, but we can use the current schedule to prove me wrong
[19:18] <cprofitt> notgary: this is focused on papercuts?
[19:18] <notgary> cprofitt: yep
[19:18]  * cprofitt nods
[19:19] <notgary> I'd taken the idea from the weekly meetings the kernel and desktop team were having
[19:19] <notgary> thinking it might be good for us too
[19:19] <cprofitt> I think regular meetings help keep a team focused
[19:20] <notgary> that was my thinking
[19:20] <cprofitt> but regular does not have to be a every week or every other week
[19:20] <cprofitt> irc meetings can cause some to feel they are losing touch with the team if they can not make meetings
[19:20] <druellan> Yes, I have the feeling that per week maybe can be too often
[19:20] <cprofitt> with the timezone issue that is often a fact of life
[19:21] <druellan> since a papercutter is more a hobbyst than a regular contrbutor
[19:21] <cprofitt> I think ensuring that you summarize the meetings on the mailing list and the wiki helps avoid that
[19:21] <cprofitt> but with one team I was on decision were made in meetings via vote
[19:21] <cprofitt> and some people became frustrated because they were never able to vote
[19:22] <notgary> I wanted to use the meetings as a place where team members would come together in real time, and where new contributors could come in and speak with them. Perhaps a better idea than a single hour long meeting each week could be "On tuesday's between 6pm and 10pm you're guaranteed to find paper cutters on IRC. Come talk to them"
[19:22] <notgary> So it;s  a lot less formal
[19:22] <cprofitt> notgary: I think that is an excellent idea
[19:23] <cprofitt> not so much a meeting, but a 'work' session
[19:23] <druellan> cprofitt: well, a meeting per two week or per mounth you get sure you make the time to assits, per week is usually more difficult if you're bussy or your timezone
[19:23] <cprofitt> perhaps extend that to having team members be able to fill time slots
[19:23] <cprofitt> that would allow people in different TZs to mentor too
[19:23] <notgary> Great idea
[19:24] <notgary> Shall we vote on it, since it might be our last meeting for a while :P
[19:24] <cprofitt> your team is one I have wanted to get involved with for a while, but the three children keep be busy
[19:25] <notgary> Excellent. Well I hope you manage to find some time. Even just an hour a week can make a world of difference
[19:26] <notgary> Anyway
[19:26] <notgary> Lets move onto this weeks agenda
[19:26] <notgary> #topic what are we working on
[19:27] <notgary> One thing I've learned from my job is that it's very useful for team members to briefly tell each other what they're working on and what problems they're currently facing with the task
[19:27] <notgary> And I'd like to try that out here
[19:27] <notgary> I'll go first
[19:27] <notgary> I'm currently putting together ideas for some events during the global Jam next weekend
[19:27] <notgary> I've left it too late to organise a physical event
[19:28] <notgary> So I'm going to host it in IRC this time round
[19:28] <notgary> It'll run along two tracks
[19:28] <notgary> Bug triage and development tutorials
[19:28] <notgary> Those videos I mentioned earlier, about how to build some of the packages
[19:28] <notgary> Will be reorded then
[19:28] <notgary> *recorded
[19:29] <notgary> I also want to try and get some people together and trawl through the backlog of bugs on some of the core GTK+ packages
[19:29] <notgary> and try and touch as many of them as possible, forwarding relevant ones to the paper cuts team in the process
[19:29] <notgary> Not really got a lot of problems with it so far
[19:29] <notgary> druellan: over to you
[19:30] <druellan> Well, I was trying to get into a meeting :P
[19:30] <notgary> :)
[19:30] <druellan> To expose the topics I posted on the wiki
[19:31] <notgary> You mean the ones you were going to discuss last time?
[19:31] <druellan> Basically, since I was away on holidays, somehow disconnected
[19:32] <druellan> I found diffucult to understand what was going on in here, so, thats way I proposed this topics to discuss
[19:34] <notgary> Would you prefer to discuss them outside of the meeting, such as on the mailing list or IRC?
[19:34] <notgary> It seems like you're having some connection issues.
[19:34] <druellan> Yes, sorry I'm a bit complicated right now
[19:34] <notgary> No worries mate
[19:34] <druellan> I send a mail to you and the ninja list explaining some of the ideas
[19:35] <notgary> Cool
[19:35] <druellan> If you like I can try to quickly explain them here
[19:35] <druellan> (if I remember all of them :p)
[19:35] <notgary> The wiki: the landing page.
[19:35] <notgary> Impressions about the new wiki organization.
[19:35] <notgary> The new Dojo.
[19:35] <notgary> Whats everybody doing right now? Milestones and crowdfixing bugs.
[19:35] <notgary> Papercuts Ninjas: to fix, to triage or both (why I need to be a ninja)?
[19:35] <notgary> Papercutters superninjas?
[19:36] <notgary> thats what you posted to the wiki agenda
[19:36] <notgary> Wow, seems like there was some kind of collision there
[19:36] <druellan> Yes, half of them I don't remember whats about, but I'll try
[19:37] <notgary> If you can't remember, then don;t worry about it just now
[19:37] <notgary> Just write it in an email. that'll be better for all.
[19:37] <druellan> The thing is, when we started focusing in apps
[19:37] <druellan> The cycle where tied to a calendar
[19:38] <druellan> say, one app per mouth, is that correct?
[19:38] <druellan> mounth
[19:38] <notgary> Sorry about that
[19:38] <druellan> Wow, you're all right?
[19:39] <notgary> Got my IRC client a bit messed up when I pasted multiple lines of text in
[19:39] <druellan> No prob
[19:39] <notgary> druellan: Do you want to wait until later before discussion this stuff, to give you a bit of time to think about it?
[19:40] <druellan> I'll try to expose the main idea now if you like
[19:40] <notgary> If it's not too much troubble
[19:40] <druellan> I was saying, if I'm not mistaken, when we started focusing on one app per cycle
[19:41] <druellan> Cycles where tied to a calendar , say, one per month, is that correct?
[19:41] <notgary> Yep
[19:42] <druellan> Well, when we discovered that GTK+ and Compiz where important, things started to behave more kahotic
[19:43] <druellan> I think we're loosing the potential that an app per cycle can give us in terms of attracting more people to the project.
[19:43] <notgary> I see what you're saying
[19:43] <druellan> If, for example
[19:43] <druellan> we are currently on "Nautilus Cycle"
[19:44] <druellan> First, we can have a title on the wiki saying: "we are currently healing Nautilus, come along"
[19:44] <druellan> We can on advance have some sort of tutorial in place, in the dojo
[19:45] <druellan> If people come here trying to learn how to patch, is more likely that other devs can help them
[19:46] <druellan> And, we can advertise cycles this way
[19:47] <druellan> Just and idea
[19:48] <notgary> It sounds good. I've had some doubts about moving away for focused milestones as well. There's roughly two months left on the R-cycle, so we can move some things around and work on two apps during that time. How about Rhythmbox and Nautilus?
[19:49] <druellan> I think the key is to advertise we are now working on this or that, this way newcommers can know what to do
[19:50] <druellan> Rhythmbox cycle was very successful
[19:50] <druellan> we can give it a proper closure
[19:51] <notgary> Indeed
[19:51] <druellan> Oh, another thing, if we focus on an app per calendar, we can contact upstream in advnace and say: "this month we are going to bother you a lot!"
[19:51] <notgary> Yeah, that worked well for us with Rhytmbox. We contact them, and a week later they'd fixed a bunch of the bugs themselves :)
[19:52] <notgary> Anyway
[19:52] <notgary> we'll do things that way
[19:52] <notgary> Next item
[19:52] <notgary> #topic Review of original goals for Raring
[19:52] <notgary> https://wiki.ubuntu.com/OneHundredPaperCuts/Raring
[19:52] <notgary> I put that together at the start of the Raring cycle
[19:52] <notgary> and proceeded to not look at it again until last week :P
[19:53] <notgary> I won;t go into the details with the little time we have left
[19:53] <notgary> but there's a lot of stuff on there that I'd like to try and focus on clearing
[19:53] <notgary> before the end of the cycle
[19:53] <notgary> such as clearing the backlog of New and Incomplete
[19:53] <notgary> bug
[19:53] <druellan> yes, the "indentify bugs" table was a good idea
[19:54] <notgary> The Global Jam events I mentioned earlier will help us with that table
[19:55] <notgary> If we have a lot of volunteers on IRC over that weened all working through the backlogs
[19:55] <notgary> we should be all set for the next cycle
[19:55] <notgary> with a healthy backlog of bugs to see us through
[19:55] <notgary> But yeah
[19:55] <notgary> I just wanted to bring this to people's attention
[19:55] <druellan> Are you going to propose Nautilus and Rhythmbox, or anything they can catch?
[19:56] <notgary> anything they can catch. the goal I have for that weekend is to send as many bugs our way as possible, so we can pick out the good ones to work on during the S-Cycle
[19:57] <druellan> Ok
[19:57] <notgary> That's about it for me. We've covered everything I wanted to talk about, though maybe not in the order they were listed on the wiki :P
[19:58] <notgary> druellan: BobJonkman: cprofitt You guys got anything you'd like to add?
[19:58] <notgary> Or any other lurkers out there?
[19:58] <BobJonkman> Nothing from me....
[19:58] <druellan> I think thats all, next meeting I can talk about other things on that list
[19:58] <notgary> Cool
[19:58] <notgary> Well if no one has anything else, then...
[19:59] <notgary> #endmeeting
[19:59] <meetingology> Meeting ended Tue Feb 19 19:59:00 2013 UTC.
[19:59] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-19.05.moin.txt
[19:59] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-19.05.html
[19:59] <notgary> Thanks a lot for coming along
[19:59] <notgary> There were some excellent ideas tonight
[19:59] <druellan> what a cute bot
[19:59] <notgary> meetingology's excellent :)
[19:59] <notgary> https://wiki.ubuntu.com/meetingology
[19:59] <notgary> You can read more about it there
[20:00] <druellan> notgary: sorry I was not fully prepared for the topics
[20:00] <notgary> Don't worry about it. I was reading through my own topics as I was typing them in here :)
[20:00] <notgary> Anyway, if things are going to be less formal, no one'll have to worry about that in the future.