19:05:51 #startmeeting One Hundred Paper Cuts meeting for 19th Feb 2013 19:05:51 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:51 19:05:51 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:23 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:33 notgary: Thanx! 19:06:43 #meetingtopic Review of previous meeting minutes 19:07:13 #meetingtopic One Hundred Paper Cuts meeting for 19th Feb 2013 19:07:25 #topic Review of previous meeting minutes 19:07:31 That's better 19:07:45 The agenda for this meeting can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/19Feb2013 19:08:13 Item 1, review of the last meetings minutes 19:08:50 which can be found here https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings/24Jan2013#Outcome 19:08:57 The first relevant part was Developer week 19:09:09 OH, I'm still supposed to talk about all thouse items? 19:09:20 Yep 19:09:29 they're on this weeks agenda though 19:09:32 so don't worry 19:09:48 No problem, carry on. 19:10:09 the original plan for Developer Week was to produce a couple of videos 19:10:22 One showing the user how to download and build the source for Rhythmbox 19:10:27 and another doing the same for Unity 19:10:34 Neither were done :P 19:10:45 which is what I was supposed to do. 19:10:47 :P 19:11:03 I'm going to put them off for the Global Jam next weekend 19:11:29 and try and get a Google+ Hanhout going with Jose, so people can watch them in real time and ask questions 19:11:58 Ubuntu communty on G+ is getting some traction now 19:11:58 We also decided we needed a more coherent strategy for attractting new contributors 19:12:08 I've noticed 19:12:09 :P 19:12:17 G+ seems to be setting some as well 19:12:21 but I digress :P 19:13:01 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:09 Jeez I'm bad at getting things done :P 19:13:28 The next item we decided on was to hold regular meetings 19:13:58 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:17 well, about the per week meetings 19:14:29 Shoot 19:14:29 its good if you need to quickly be in touch with people 19:14:54 but is hard to promote, I mean, if you have a meeting too often you loose some traction 19:15:31 how so? 19:15:54 sorry, phone 19:17:13 What do you mean by 'lose some traction'? Do you think people will lose interest if we have too many meetings? 19:18:11 druellan: you still there? 19:18:38 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:41 notgary: this is focused on papercuts? 19:18:51 cprofitt: yep 19:18:56 * cprofitt nods 19:19:27 I'd taken the idea from the weekly meetings the kernel and desktop team were having 19:19:33 thinking it might be good for us too 19:19:52 I think regular meetings help keep a team focused 19:20:08 that was my thinking 19:20:12 but regular does not have to be a every week or every other week 19:20:32 irc meetings can cause some to feel they are losing touch with the team if they can not make meetings 19:20:39 Yes, I have the feeling that per week maybe can be too often 19:20:45 with the timezone issue that is often a fact of life 19:21:04 since a papercutter is more a hobbyst than a regular contrbutor 19:21:24 I think ensuring that you summarize the meetings on the mailing list and the wiki helps avoid that 19:21:37 but with one team I was on decision were made in meetings via vote 19:21:51 and some people became frustrated because they were never able to vote 19:22:31 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:48 So it;s a lot less formal 19:22:50 notgary: I think that is an excellent idea 19:23:04 not so much a meeting, but a 'work' session 19:23:13 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:26 perhaps extend that to having team members be able to fill time slots 19:23:45 that would allow people in different TZs to mentor too 19:23:56 Great idea 19:24:43 Shall we vote on it, since it might be our last meeting for a while :P 19:24:46 your team is one I have wanted to get involved with for a while, but the three children keep be busy 19:25:52 Excellent. Well I hope you manage to find some time. Even just an hour a week can make a world of difference 19:26:07 Anyway 19:26:19 Lets move onto this weeks agenda 19:26:32 #topic what are we working on 19:27:08 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:20 And I'd like to try that out here 19:27:22 I'll go first 19:27:47 I'm currently putting together ideas for some events during the global Jam next weekend 19:27:58 I've left it too late to organise a physical event 19:28:05 So I'm going to host it in IRC this time round 19:28:17 It'll run along two tracks 19:28:25 Bug triage and development tutorials 19:28:37 Those videos I mentioned earlier, about how to build some of the packages 19:28:46 Will be reorded then 19:28:49 *recorded 19:29:13 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:32 and try and touch as many of them as possible, forwarding relevant ones to the paper cuts team in the process 19:29:43 Not really got a lot of problems with it so far 19:29:51 druellan: over to you 19:30:41 Well, I was trying to get into a meeting :P 19:30:45 :) 19:30:58 To expose the topics I posted on the wiki 19:31:31 You mean the ones you were going to discuss last time? 19:31:35 Basically, since I was away on holidays, somehow disconnected 19:32:18 I found diffucult to understand what was going on in here, so, thats way I proposed this topics to discuss 19:34:07 Would you prefer to discuss them outside of the meeting, such as on the mailing list or IRC? 19:34:18 It seems like you're having some connection issues. 19:34:41 Yes, sorry I'm a bit complicated right now 19:34:49 No worries mate 19:34:59 I send a mail to you and the ninja list explaining some of the ideas 19:35:06 Cool 19:35:14 If you like I can try to quickly explain them here 19:35:28 (if I remember all of them :p) 19:35:51 The wiki: the landing page. 19:35:52 Impressions about the new wiki organization. 19:35:53 The new Dojo. 19:35:54 Whats everybody doing right now? Milestones and crowdfixing bugs. 19:35:55 Papercuts Ninjas: to fix, to triage or both (why I need to be a ninja)? 19:35:56 Papercutters superninjas? 19:36:00 thats what you posted to the wiki agenda 19:36:27 Wow, seems like there was some kind of collision there 19:36:56 Yes, half of them I don't remember whats about, but I'll try 19:37:08 If you can't remember, then don;t worry about it just now 19:37:19 Just write it in an email. that'll be better for all. 19:37:29 The thing is, when we started focusing in apps 19:37:47 The cycle where tied to a calendar 19:38:00 say, one app per mouth, is that correct? 19:38:10 mounth 19:38:52 Sorry about that 19:38:54 Wow, you're all right? 19:39:09 Got my IRC client a bit messed up when I pasted multiple lines of text in 19:39:42 No prob 19:39:43 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:01 I'll try to expose the main idea now if you like 19:40:10 If it's not too much troubble 19:40:50 I was saying, if I'm not mistaken, when we started focusing on one app per cycle 19:41:14 Cycles where tied to a calendar , say, one per month, is that correct? 19:41:32 Yep 19:42:09 Well, when we discovered that GTK+ and Compiz where important, things started to behave more kahotic 19:43:00 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:27 I see what you're saying 19:43:46 If, for example 19:43:56 we are currently on "Nautilus Cycle" 19:44:44 First, we can have a title on the wiki saying: "we are currently healing Nautilus, come along" 19:44:59 We can on advance have some sort of tutorial in place, in the dojo 19:45:28 If people come here trying to learn how to patch, is more likely that other devs can help them 19:46:12 And, we can advertise cycles this way 19:47:07 Just and idea 19:48:31 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:36 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:22 Rhythmbox cycle was very successful 19:50:30 we can give it a proper closure 19:51:05 Indeed 19:51:22 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:55 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:05 Anyway 19:52:10 we'll do things that way 19:52:16 Next item 19:52:29 #topic Review of original goals for Raring 19:52:35 https://wiki.ubuntu.com/OneHundredPaperCuts/Raring 19:52:46 I put that together at the start of the Raring cycle 19:52:55 and proceeded to not look at it again until last week :P 19:53:12 I won;t go into the details with the little time we have left 19:53:34 but there's a lot of stuff on there that I'd like to try and focus on clearing 19:53:39 before the end of the cycle 19:53:53 such as clearing the backlog of New and Incomplete 19:53:54 bug 19:53:56 yes, the "indentify bugs" table was a good idea 19:54:35 The Global Jam events I mentioned earlier will help us with that table 19:55:00 If we have a lot of volunteers on IRC over that weened all working through the backlogs 19:55:08 we should be all set for the next cycle 19:55:16 with a healthy backlog of bugs to see us through 19:55:34 But yeah 19:55:44 I just wanted to bring this to people's attention 19:55:55 Are you going to propose Nautilus and Rhythmbox, or anything they can catch? 19:56:37 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:00 Ok 19:57:35 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:03 druellan: BobJonkman: cprofitt You guys got anything you'd like to add? 19:58:11 Or any other lurkers out there? 19:58:24 Nothing from me.... 19:58:27 I think thats all, next meeting I can talk about other things on that list 19:58:48 Cool 19:58:58 Well if no one has anything else, then... 19:59:00 #endmeeting