/srv/irclogs.ubuntu.com/2013/02/19/#ubuntu-meeting.txt

xnoxinteresting meeting =)00:24
freeflyingI missed it :)00:58
=== bazhang_ is now known as bazhang
=== Quintasan_ is now known as Quintasan
=== Quintasan_ is now known as Quintasan
=== doko_ is now known as doko
=== mmrazik is now known as mmrazik|lunch
=== arun_ is now known as arun
* smartboyhw wonders why the topic is AOB....12:46
ogra_likely because someone forgot to close their meeting12:46
sorenThat would be pitti.12:47
smartboyhwoops12:47
ogra_yeah, the backlog says so12:47
sorenI've just poked him about it.12:48
soren#endmeeting12:48
sorenYeah, he has to do it.12:48
sorenWas worth a try, though :)12:48
=== smartboyhw_ is now known as smartboyhw
xnox#endmeeting13:01
* xnox failed at highjacking pitti's nickname13:02
smartboyhwEh doesn't work:P13:02
pitti#endmeeting13:19
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Feb 19 13:19:23 2013 UTC.13:19
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-18-21.07.moin.txt13:19
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-18-21.07.html13:19
smartboyhwClap Clap Clap13:19
pittisorry about that13:19
pittilongest TB meeting EVAR13:19
sorenNo harm done.13:20
smartboyhw:)13:20
sorensmartboyhw just wodered why the topic said "AOB".13:20
smartboyhwsoren, Any Other Business13:20
sorenSure, I know.13:20
ogra_now you know twice ;)13:21
smartboyhwlol13:22
ogra_soren, its like counters on websites ... twice is better ;)13:22
=== mmrazik|lunch is now known as mmrazik
=== Sweetsha1k is now known as Sweetshark
AlanBellfwiw anyone with a member cloak can op up in this channel and it listens to operators as if they were chair14:54
AlanBellso you can get ops by /msg chanserv op #ubuntu-meeting and then #endmeeting even if it wasn't your meeting to end14:55
AlanBellsoren: ogra_ xnox ^^14:55
xnoxawesome.14:56
jamespageo/16:01
m_3hola16:01
yolandahi16:01
* Daviey has to offer his apologies, clashing event.16:02
Davieysmoser: chairing?16:02
arosaleshello16:05
smoseri can chair.16:06
smosersorry.16:06
smoserhere now.16:06
smoser#startmeeting ubuntu-server16:06
meetingologyMeeting started Tue Feb 19 16:06:13 2013 UTC.  The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:06
meetingologyAvailable 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 #votesrequired16:06
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic:
smoserhttps://wiki.ubuntu.com/ServerTeam/Meeting16:06
smoser#topic Review ACTION points from previous meeting16:06
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Review ACTION points from previous meeting
* smoser looks for logs to get action items16:07
smoserhttp://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-12-16.01.html16:07
smoserDaviey, you're listed there as send request for testing16:08
smoserdid we send? i dont think so.16:08
Davieysmoser: sort of "no".16:08
smoserwe did release a alpha-2 cloud images . (http://cloud-images.ubuntu.com/releases/13.04/alpha-2/)16:08
smoserhm...16:08
smoserok, so we'll re-action that? i really do think we should make an effort there.16:09
Daviey+116:09
smoser#ACTION Daviey send call for alpha-2-ish testing16:09
meetingologyACTION: Daviey send call for alpha-2-ish testing16:09
smoser    ACTION: jamespage to milesone documentation updates (zul, 16:38:45)16:10
smoserjamespage, ^16:10
jamespagenot done yet16:10
smoser#ACTION: jamespage to milesone documentation updates [carryover]16:10
meetingologyACTION: : jamespage to milesone documentation updates [carryover]16:10
smoser#topic Raring Development16:10
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Raring Development
smoserrelease tracking: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server16:11
jamespageaction was actually to ensure that any doc updates in BP's are milestoned appropriatly16:11
smoserjamespage, ah. ok. do you need help there?16:11
smoserok. so release tracking link up there. maas is the biggest thing. and the qemu-kvm.16:12
smoserhallyn, do you have a handle on the qemu-kvm bug ?16:12
jamespagesmoser, nah - its OK - I'll do it16:12
smoserbug 109271516:12
ubottubug 1092715 in qemu-kvm (Ubuntu Raring) "udevadm trigger --action=change not working in quantal and raring" [High,Confirmed] https://launchpad.net/bugs/109271516:12
jamespagethat one is killing me slowly16:12
hallynsmoser: yes, i just need to talk to pitti again16:13
hallynsmoser: there is a real bug in udev,16:13
smoserhallyn, please do... that is a real pain16:13
hallynbut i want to just work around it16:13
* smoser is tired of 'chmod 666 /dev/kvm' 16:13
hallynall right, i'll talk to him today or tomorrow16:13
hallyn(depending on his tz)16:13
jamespagelol16:13
smoserroaksoax, maas and release tracking ?16:13
smosererr... sru. i think we're nearing it.16:14
smoserhm.. we'll maybe come back to that.16:14
roaksoaxsmoser: 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 team16:14
roaksoaxs/to django/for django/16:15
smoserroaksoax, ok. please do follow up there. i'm sure we can find someone on maas team to accomplish.16:15
smoserblueprints: http://status.ubuntu.com/ubuntu-raring/group/topic-raring-servercloud-overview.html16:15
roaksoaxsmoser: other than that, is merging the latest fixes we have left for it16:15
smoserplease 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
smoserrelease schedule at https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule . feature freeze is March 7.16:16
smoser#Ubuntu Server Team Events16:17
smoser#topic Ubuntu Server Team Events16:17
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Ubuntu Server Team Events
smoseranyone have anything here ?16:17
smoseri think that jcastro is going to scale this week.16:18
smoserhttp://www.socallinuxexpo.org/16:18
smoserand talking ther eabout juju.16:18
smoseranyone have anything else ?16:18
smoserok. moving on.16:19
smoser#topic Weekly Updates & Questions for the QA Team (hggdh)16:19
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Weekly Updates & Questions for the QA Team (hggdh)
smoserthis topic should probably be up for consideration on removal. doesn't seem to have been very busy recently.16:20
smosermoving on16:20
smoser#topic Weekly Updates & Questions for the Kernel Team (smb)16:20
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb)
smbFinally tracked down an elusive Xen bug that was paining Precise16:20
smbbut potentially lurked around till now. That is currently going16:20
smbupstream and then back (bug 1011792).16:20
smbNot sure I got more beside my struggles with libvirt. ;-P Any16:20
smbquestions?16:20
ubottubug 1011792 in linux-lts-backport-oneiric (Ubuntu) "Kernel lockup running 3.0.0 and 3.2.0 on multiple EC2 instance types" [Critical,Confirmed] https://launchpad.net/bugs/101179216:20
smb..16:20
smosersmb, 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 ttyS016:21
smosermost recently causing issues at 112224516:22
smbsmoser, I could imagine our method of fixing your interest might be incompatible...16:22
hallynput the bat away....16:22
smb:)16:22
smbThe problem seemed that the kernel itself has no issue... it is hard to tell user-space what to use...16:23
smosersmb, well, any ways i dream of fixing it from user-space are basically doomed.16:23
smoseras the kernel has this nice buffer on writes to /dev/console16:23
smoserso things work for a while, and then randomly faily.16:23
smoserso, its really toufh to come up with a way that user space could "fix" the situation  or work around it.16:24
smoserso, my request is really that you just try to think of a way that writes to /dev/console could never fail.16:25
smbsmoser, I try to think on it. Though not promising too much16:25
smoserk16:26
smoser#topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)16:26
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
smoser(smb, thank you for being prepared for your section).16:26
smoserrbasak not present, moving on.16:27
smoser#topic Open Discussion16:28
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Open Discussion
smosero. i have one topic here, that is "QA".16:28
smoserin 2 repsects16:28
smosera.) should we change/remove/update that section of our meeting ? it seems not to have much in it.16:28
smoserb.) 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
smoseranyone have comments on that? i'm largely talking to myself today.16:29
jamespagemost 'ISO' tests are now automated16:29
jamespageif we where going to call for testing I would think two things would be good16:29
jamespage1) write dep-8 tests - we have a big list16:30
jamespage2) exercise stuff off-piste - generalist testing16:30
roaksoaxI think 1) makes lots of sense16:30
roaksoaxto get the community engadged16:31
hallynshould we invite gema for this section?16:31
hallynor have jamespage represent?16:31
roaksoaxjamespage: represent!!16:32
jamespagehallyn, tbh some of the reason the dep-8 bp is going nowhere is that I'm focussed elsewhere16:32
roaksoax:)16:32
hallynjamespage: perhaps we should be discussing that16:32
arosalessmoser: m_3 will also join jcastro at scale11x this week.16:32
hallynthough of course, i doubt we'll find anyone not swamped right now16:33
m_3yeah, wasn't gonna correct anything16:33
hallynbut maybe the bp needs a team of 2-3 ppl16:33
jamespageyeah - its just down the priority list16:33
smoserok. 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:34
jamespagehallyn, 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 importnat16:35
smoserhoping 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
jamespagesmoser, I think that would be great!16:35
m_3should we add in requests for charm testing (i.e., /tests dir in each charm)?16:35
m_3or is that best left separate?16:35
smoseri would leave that out of "Ubuntu server raring call for testing", m_3.16:36
smoseri dont think begging for such things is bad, but just that it doesn't fit there.16:36
m_3ack16:36
smoserjamespage, so do you think we should move you to the name in '()' for qa section ?16:36
jamespagesmoser, no - I want direct engagement with the QA team in this meeting16:37
jamespageits been lacking and I think we a suffering for it16:37
smoserok. so can you take an action there ? or do you want me to draft a mail requesting participation16:37
jamespagesmoser, but I'll take an action to go discuss with gemma16:37
smoser#action jamespage discuss QA representation at Server TeamMeeting16:37
meetingologyACTION: jamespage discuss QA representation at Server TeamMeeting16:37
smoseri'm going to #endmeeting if noone has any objections?16:38
roaksoaxi do16:38
roaksoaxhave something to bring up16:38
roaksoaxI'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-filesystems16:38
smoserroaksoax, i suggest raising on ubuntu-server and ubuntu-cloud16:40
roaksoaxsmoser: ack!16:40
smoser#topic Announce next meeting date, time and chair16:40
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server Meeting | Current topic: Announce next meeting date, time and chair
smosernext meeting is same time, same place, 7 days from now.16:41
smoser Tuesday 2013-02-26 at 1600 UTC16:41
smoserchair will be the honorable hallyn.16:41
arosalessmoser: thanks for chairing16:41
smoser#endmeeting.16: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
meetingologyMeeting ended Tue Feb 19 16:41:40 2013 UTC.16:41
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-16.06.moin.txt16:41
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-16.06.html16:41
jamespagethanks smoser!16:41
Davieythanks smoser16:42
jsalisbury#startmeeting17:00
jsalisbury##17:00
jsalisbury## This is the Ubuntu Kernel Team weekly status meeting.17:00
meetingologyMeeting started Tue Feb 19 17:00:18 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable 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 #votesrequired17:00
jsalisbury##17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring17:00
jsalisbury# Meeting Etiquette17: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
jsalisburyRoll Call for Ubuntu Kernel Weekly Status Meeting17:00
ppisatio/17:00
cking\o17:00
henrixo/17:00
smb\o17:00
bjfo/17:00
sconklino/17:00
sforsheeo/17:00
jsalisbury[TOPIC] ARM Status (ppisati)17:01
=== meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati)
ppisatinothing new to report this week17:01
ppisati..17:01
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:01
jsalisburyRelease metrics and incoming bug data can be reviewed at the following link:17:01
jsalisbury[LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt17:01
=== meetingology changed the topic of #ubuntu-meeting to: Release Metrics and Incoming Bugs (jsalisbury)
jsalisbury..17:01
jsalisbury[TOPIC] Milestone Targeted Work Items (ogasawara)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Milestone Targeted Work Items (ogasawara)
ogasawara[LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork17:02
ogasawara[LINK] http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team.html17: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
ogasawaraThe above summarizes the remaining work items owned by individuals on17:02
ogasawaraour team for the rest of the 13.04 cycle.17:02
ogasawara..17:02
jsalisbury[TOPIC] Status: Raring Development Kernel (ogasawara)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: Raring Development Kernel (ogasawara)
ogasawaraWe have rebased the Raring kernel to the final upstream v3.8 release and17:02
ogasawarauploaded.  We also made a few misc config changes and added some i91517:02
ogasawarafixes.17:02
ogasawaraImportant upcoming dates:17:02
ogasawara * Raring:17:02
ogasawara  * Thurs Mar 07 - 13.04 Feature Freeze17:02
ogasawara  * Thurs Mar 21 - 13.04 Beta Freeze17:03
ogasawara  * Thurs Mar 28 - 13.04 Beta Release17:03
ogasawara..17:03
jsalisbury[TOPIC] Status: CVE's (henrix)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's (henrix)
henrixCurrently we have 30 CVEs on our radar, with 2 CVEs added and 3 CVEs retired this week.17:03
henrixSee the CVE matrix for the current list:17:03
henrix[LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html17:03
henrix[LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt17:03
henrix[LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt17:03
henrix..17:03
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
henrixDue to an high priority CVE, all the stable kernels are being respined this week.17:04
henrixCurrent opened tracking bugs details:17:04
henrix * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html17:04
henrixFor SRUs, SRU report is a good source of information:17:04
henrix * http://people.canonical.com/~kernel/reports/sru-report.html17:04
henrixFuture stable cadence cycles:17:04
henrix * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock17:04
henrixNote: 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:04
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:05
jsalisbury#endmeeting17: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
meetingologyMeeting ended Tue Feb 19 17:05:06 2013 UTC.17:05
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-17.00.moin.txt17:05
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-17.00.html17:05
cprofittis anyone here for the Ubuntu Friendly meeting?17:22
vibhavcproffit: o/17:28
SergioMenesescprofitt, o/17:29
SergioMenesescprofitt, vibhav I think we can tall by mailing list17:30
vibhavSure17:30
cprofitthey vibhav17:32
cprofittgood to see you17:32
vibhav:)17:33
cprofittwe are in #ubuntu-quality right now if you want to join us there17:33
vibhavSure17:33
cprofittsorry that the meeting did not get off the ground this time around17:33
notgaryAnyone here?18:56
notgaryAnyone here?18:59
druellanHi Chris19:00
notgaryHey Dario, how's it going?19:01
druellanFine, but I've just got back from my holidays, and my clients are killing me with emails :P19:02
notgarySounds like a whole load of fun :)19:03
notgaryIs anyone else in here for the paper cuts meeting?19:03
notgarydruellan: guess it's just you and me tonight :)19:04
druellanHaha, oh well19:05
* BobJonkman is lurking19:05
notgary#startmeeting One Hundred Paper Cuts meeting for 19th Feb 201319:05
meetingologyMeeting started Tue Feb 19 19:05:51 2013 UTC.  The chair is notgary. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:05
meetingologyAvailable 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 #votesrequired19: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 | One Hundred Paper Cuts meeting for 19th Feb 2013 Meeting | Current topic:
notgaryBobJonkman: The lurk away my friend. If you have anything to say, then just go ahead and say it. don;t worry about interrupting19:06
BobJonkmannotgary: Thanx!19:06
notgary#meetingtopic Review of previous meeting minutes19:06
=== 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 | Review of previous meeting minutes Meeting | Current topic:
notgary#meetingtopic One Hundred Paper Cuts meeting for 19th Feb 201319:07
=== 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 | One Hundred Paper Cuts meeting for 19th Feb 2013 Meeting | Current topic:
notgary#topic Review of previous meeting minutes19:07
=== 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 | One Hundred Paper Cuts meeting for 19th Feb 2013 Meeting | Current topic: Review of previous meeting minutes
notgaryThat's better19:07
notgaryThe agenda for this meeting can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/19Feb201319:07
notgaryItem 1, review of the last meetings minutes19:08
notgarywhich can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/24Jan2013#Outcome19:08
notgaryThe first relevant part was Developer week19:08
druellanOH, I'm still supposed to talk about all thouse items?19:09
notgaryYep19:09
notgarythey're on this weeks agenda though19:09
notgaryso don't worry19:09
druellanNo problem, carry on.19:09
notgarythe original plan for Developer Week was to produce a couple of videos19:10
notgaryOne showing the user how to download and build the source for Rhythmbox19:10
notgaryand another doing the same for Unity19:10
notgaryNeither were done :P19:10
notgarywhich is what I was supposed to do.19:10
notgary:P19:10
notgaryI'm going to put them off for the Global Jam next weekend19:11
notgaryand try and get a Google+ Hanhout going with Jose, so people can watch them in real time and ask questions19:11
druellanUbuntu communty on G+ is getting some traction now19:11
notgaryWe also decided we needed a more coherent strategy for attractting new contributors19:11
notgaryI've noticed19:12
notgary:P19:12
notgaryG+ seems to be setting some as well19:12
notgarybut I digress :P19:12
notgaryI 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 doing19:13
notgaryJeez I'm bad at getting things done :P19:13
notgaryThe next item we decided on was to hold regular meetings19:13
notgaryWe 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:13
druellanwell, about the per week meetings19:14
notgaryShoot19:14
druellanits good if you need to quickly be in touch with people19:14
druellanbut is hard to promote, I mean, if you have a meeting too often you loose some traction19:14
notgaryhow so?19:15
druellansorry, phone19:15
notgaryWhat do you mean by 'lose some traction'? Do you think people will lose interest if we have too many meetings?19:17
notgarydruellan: you still there?19:18
druellanI'm here, sorry. Yes, I believe that cen be the case, but we can use the current schedule to prove me wrong19:18
cprofittnotgary: this is focused on papercuts?19:18
notgarycprofitt: yep19:18
* cprofitt nods19:18
notgaryI'd taken the idea from the weekly meetings the kernel and desktop team were having19:19
notgarythinking it might be good for us too19:19
cprofittI think regular meetings help keep a team focused19:19
notgarythat was my thinking19:20
cprofittbut regular does not have to be a every week or every other week19:20
cprofittirc meetings can cause some to feel they are losing touch with the team if they can not make meetings19:20
druellanYes, I have the feeling that per week maybe can be too often19:20
cprofittwith the timezone issue that is often a fact of life19:20
druellansince a papercutter is more a hobbyst than a regular contrbutor19:21
cprofittI think ensuring that you summarize the meetings on the mailing list and the wiki helps avoid that19:21
cprofittbut with one team I was on decision were made in meetings via vote19:21
cprofittand some people became frustrated because they were never able to vote19:21
notgaryI 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
notgarySo it;s  a lot less formal19:22
cprofittnotgary: I think that is an excellent idea19:22
cprofittnot so much a meeting, but a 'work' session19:23
druellancprofitt: 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 timezone19:23
cprofittperhaps extend that to having team members be able to fill time slots19:23
cprofittthat would allow people in different TZs to mentor too19:23
notgaryGreat idea19:23
notgaryShall we vote on it, since it might be our last meeting for a while :P19:24
cprofittyour team is one I have wanted to get involved with for a while, but the three children keep be busy19:24
notgaryExcellent. Well I hope you manage to find some time. Even just an hour a week can make a world of difference19:25
notgaryAnyway19:26
notgaryLets move onto this weeks agenda19:26
notgary#topic what are we working on19:26
=== 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 | One Hundred Paper Cuts meeting for 19th Feb 2013 Meeting | Current topic: what are we working on
notgaryOne 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 task19:27
notgaryAnd I'd like to try that out here19:27
notgaryI'll go first19:27
notgaryI'm currently putting together ideas for some events during the global Jam next weekend19:27
notgaryI've left it too late to organise a physical event19:27
notgarySo I'm going to host it in IRC this time round19:28
notgaryIt'll run along two tracks19:28
notgaryBug triage and development tutorials19:28
notgaryThose videos I mentioned earlier, about how to build some of the packages19:28
notgaryWill be reorded then19:28
notgary*recorded19:28
notgaryI also want to try and get some people together and trawl through the backlog of bugs on some of the core GTK+ packages19:29
notgaryand try and touch as many of them as possible, forwarding relevant ones to the paper cuts team in the process19:29
notgaryNot really got a lot of problems with it so far19:29
notgarydruellan: over to you19:29
druellanWell, I was trying to get into a meeting :P19:30
notgary:)19:30
druellanTo expose the topics I posted on the wiki19:30
notgaryYou mean the ones you were going to discuss last time?19:31
druellanBasically, since I was away on holidays, somehow disconnected19:31
druellanI found diffucult to understand what was going on in here, so, thats way I proposed this topics to discuss19:32
notgaryWould you prefer to discuss them outside of the meeting, such as on the mailing list or IRC?19:34
notgaryIt seems like you're having some connection issues.19:34
druellanYes, sorry I'm a bit complicated right now19:34
notgaryNo worries mate19:34
druellanI send a mail to you and the ninja list explaining some of the ideas19:34
notgaryCool19:35
druellanIf you like I can try to quickly explain them here19:35
druellan(if I remember all of them :p)19:35
notgaryThe wiki: the landing page.19:35
notgaryImpressions about the new wiki organization.19:35
notgaryThe new Dojo.19:35
notgaryWhats everybody doing right now? Milestones and crowdfixing bugs.19:35
notgaryPapercuts Ninjas: to fix, to triage or both (why I need to be a ninja)?19:35
notgaryPapercutters superninjas?19:35
notgarythats what you posted to the wiki agenda19:36
notgaryWow, seems like there was some kind of collision there19:36
druellanYes, half of them I don't remember whats about, but I'll try19:36
notgaryIf you can't remember, then don;t worry about it just now19:37
notgaryJust write it in an email. that'll be better for all.19:37
druellanThe thing is, when we started focusing in apps19:37
druellanThe cycle where tied to a calendar19:37
druellansay, one app per mouth, is that correct?19:38
druellanmounth19:38
notgarySorry about that19:38
druellanWow, you're all right?19:38
notgaryGot my IRC client a bit messed up when I pasted multiple lines of text in19:39
druellanNo prob19:39
notgarydruellan: Do you want to wait until later before discussion this stuff, to give you a bit of time to think about it?19:39
druellanI'll try to expose the main idea now if you like19:40
notgaryIf it's not too much troubble19:40
druellanI was saying, if I'm not mistaken, when we started focusing on one app per cycle19:40
druellanCycles where tied to a calendar , say, one per month, is that correct?19:41
notgaryYep19:41
druellanWell, when we discovered that GTK+ and Compiz where important, things started to behave more kahotic19:42
druellanI 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
notgaryI see what you're saying19:43
druellanIf, for example19:43
druellanwe are currently on "Nautilus Cycle"19:43
druellanFirst, we can have a title on the wiki saying: "we are currently healing Nautilus, come along"19:44
druellanWe can on advance have some sort of tutorial in place, in the dojo19:44
druellanIf people come here trying to learn how to patch, is more likely that other devs can help them19:45
druellanAnd, we can advertise cycles this way19:46
druellanJust and idea19:47
notgaryIt 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:48
druellanI think the key is to advertise we are now working on this or that, this way newcommers can know what to do19:49
druellanRhythmbox cycle was very successful19:50
druellanwe can give it a proper closure19:50
notgaryIndeed19:51
druellanOh, 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
notgaryYeah, that worked well for us with Rhytmbox. We contact them, and a week later they'd fixed a bunch of the bugs themselves :)19:51
notgaryAnyway19:52
notgarywe'll do things that way19:52
notgaryNext item19:52
notgary#topic Review of original goals for Raring19:52
=== 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 | One Hundred Paper Cuts meeting for 19th Feb 2013 Meeting | Current topic: Review of original goals for Raring
notgaryhttps://wiki.ubuntu.com/OneHundredPaperCuts/Raring19:52
notgaryI put that together at the start of the Raring cycle19:52
notgaryand proceeded to not look at it again until last week :P19:52
notgaryI won;t go into the details with the little time we have left19:53
notgarybut there's a lot of stuff on there that I'd like to try and focus on clearing19:53
notgarybefore the end of the cycle19:53
notgarysuch as clearing the backlog of New and Incomplete19:53
notgarybug19:53
druellanyes, the "indentify bugs" table was a good idea19:53
notgaryThe Global Jam events I mentioned earlier will help us with that table19:54
notgaryIf we have a lot of volunteers on IRC over that weened all working through the backlogs19:55
notgarywe should be all set for the next cycle19:55
notgarywith a healthy backlog of bugs to see us through19:55
notgaryBut yeah19:55
notgaryI just wanted to bring this to people's attention19:55
druellanAre you going to propose Nautilus and Rhythmbox, or anything they can catch?19:55
notgaryanything 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-Cycle19:56
druellanOk19:57
notgaryThat'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 :P19:57
notgarydruellan: BobJonkman: cprofitt You guys got anything you'd like to add?19:58
notgaryOr any other lurkers out there?19:58
BobJonkmanNothing from me....19:58
druellanI think thats all, next meeting I can talk about other things on that list19:58
notgaryCool19:58
notgaryWell if no one has anything else, then...19:58
notgary#endmeeting19:59
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Feb 19 19:59:00 2013 UTC.19:59
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-19.05.moin.txt19:59
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-19-19.05.html19:59
notgaryThanks a lot for coming along19:59
notgaryThere were some excellent ideas tonight19:59
druellanwhat a cute bot19:59
notgarymeetingology's excellent :)19:59
notgaryhttps://wiki.ubuntu.com/meetingology19:59
notgaryYou can read more about it there19:59
druellannotgary: sorry I was not fully prepared for the topics20:00
notgaryDon't worry about it. I was reading through my own topics as I was typing them in here :)20:00
notgaryAnyway, if things are going to be less formal, no one'll have to worry about that in the future.20:00

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