/srv/irclogs.ubuntu.com/2008/06/21/#ubuntu-meeting.txt

=== johnc4511 is now known as johnc4510-laptop
=== riot_l1 is now known as riot_le
=== asac_ is now known as asac
=== stgraber_ is now known as stgraber
=== protonchris_ is now known as protonchris
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Xubuntu Community | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 21 Jun 19:00 UTC: How to run a Bug Jam | 22 Jun 18:00 UTC: Ubuntu Mozilla Team | 24 Jun 15:00 UTC: Server Team | 24 Jun 18:00 UTC: LoCo Council | 25 Jun 17:00 UTC: QA Team
cody-somerville:)17:57
cody-somervilleI gotta run. j1mc is going to host the meeting for me :)17:57
cody-somervilleHave fun fellows17:57
j1mchi all - who all is here?17:59
TheSheepcody-somerville: so I guess the meeting is cancelled?19:11
techno_freakoh?19:12
jcastro10 minutes until "How to Run a Bug Jam"!19:49
ccmgood luck with it, jcastro :)19:55
greg-gno luck needed ;)19:55
ccmright. just kind of an idiom :)19:56
jcastroheh19:57
jcastrogreg-g: do you know how to control the bot?19:58
greg-gno clue19:59
jcastroheh, no worries19:59
jcastrook, I guess we should start with introductions20:00
jcastroI'm jorge castro, I'm on the ubuntu community team.20:00
greg-gHello everyone!  Welcome to the second session of "How to Run a Bug Jam"20:00
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: How to run a Bug Jam | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 22 Jun 18:00 UTC: Ubuntu Mozilla Team | 24 Jun 15:00 UTC: Server Team | 24 Jun 18:00 UTC: LoCo Council | 25 Jun 17:00 UTC: QA Team | 25 Jun 22:00 UTC: Platform Team
greg-gmy name is Greg Grossmeier and the leader of the Michigan (US) LoCo Team20:00
jcastroso if you're here from the meeting please say hello!20:01
jcastroand what team you're representing. (or if you're just hanging out)20:01
jacobi might be ducking in and out (was in here yesterday) but I suppose i'm here. Hello from Ohio!20:01
greg-gHello jacob20:02
* chuckf representing MarylandTeam20:02
greg-gwelcome20:02
jcastroI see Maryland already has all their stuff filed out on the wiki20:02
nxvljcastro: #startmeeting20:03
jcastronxvl: ah20:03
chuckflargly, yeah20:03
jcastro#startmeeting20:03
jcastrolike that?20:03
jcastrook whatever, let's get started!20:03
jcastrohttps://wiki.ubuntu.com/GlobalBugJam20:03
nxvlyes, mathiaz always use something like that20:03
jcastrothis is the main page we're going to use for coordinating the jam20:03
greg-gand tips for how to run it: https://wiki.ubuntu.com/GlobalBugJam/Prep20:04
jcastrohttps://wiki.ubuntu.com/GlobalBugJam/Prep20:04
jcastroand this page is what we're going to discuss today20:04
* nxvl represents Peru20:04
jcastroso if you remember one thing, it's that last URL. :)20:04
jcastroOk, before we get into the nitty gritty20:04
jcastrothe first thing that is most important for the Jam20:04
jcastrois that everyone has a good time.20:04
* greg-g nods20:05
jcastroIf 300 people show up20:05
jcastroand you only triage 1 bug, then that's totally fine20:05
jcastrothe idea is to get Local teams together and having a good time20:05
jcastroso down the road when you want to do a social event, you'll know how to do a jam and can do one whenever you want20:05
jcastrowe would like to see LoCos just running jams on their own and doing what their members want to do20:06
jcastroso hopefully we can make these fun so people want to do them20:06
jcastroso for example20:06
jcastrowe just had a jam in michigan20:06
jcastroand due to weather only 3 people showed up20:06
jcastrobut we still had a great time20:06
* greg-g and me being in California20:06
jcastroso you should measure success by how good a time people had, and how you take notes to make things better next time, etc.20:06
jcastrodon't use raw numbers or bug counts as your measurement of success20:07
jcastrothose are just great side effects. :)20:07
jcastroAny questions so far?20:07
chuckfnope20:07
jcastrogreg-g: want to go into venues?20:07
jcastrowe can alternate on topics20:07
greg-gsure20:07
siretartFYI, we are having a BugJam right now in nueremberg, with 15 attendees (including myself) :)20:07
greg-gsiretart: nice!20:07
jcastrosiretart: oh well, that's awesome!20:08
nxvljcastro: i have a doubt20:08
greg-g?20:08
nxvljcastro: the idea of the GBJ is to fix bugs or just to triage them, or both of them?20:08
jcastronxvl: fix would be nice, but shoot for triage20:08
* greg-g nods20:08
jcastronxvl: people should know how to triage20:08
nxvljcastro: so the goal is triaging, but if you fix them it's even nicer?20:09
jcastroand as your bug jams progress your team can go as advanced as they want20:09
jcastroyep, of course. :D20:09
greg-gSo, Venues...20:09
greg-gYou need some place that has power, internet, and places to sit for everyone that is going to show up (obviously)20:09
greg-gbut, it also needs to be conducive to listening to one person talking for a little bit and asking questions20:09
greg-gsome good places are offices of Open Source Friendly businesses or even Library conference rooms (where Michigan had ours)20:10
greg-gwhere is your bug jam going on siretart ?20:10
jcastroI bet in a pub. :)20:11
greg-g(feel free to answer later siretart ) another place we have done things for our team is at a person's house20:11
greg-gThere we had the essentials plus nice seating and food and drinks20:11
greg-gso really, anywhere that is comfortable and conducive to group work.20:12
greg-gand, cheap :)20:12
greg-gany questions on venues? or other suggestions before we move on?20:13
chuckfcolleges20:13
jcastroColleges are always good20:13
greg-ggood one20:13
chuckfthe cis groups tend to have presentation/work rooms available on weekends20:13
nxvlwe are thinking on running ours on a starbucks20:13
jcastrobecause you can link up with like a computer club or ACM or something and get more participation20:13
greg-gjust make sure you have a way for everyone to get internet access where ever you are20:14
chuckfalso check with local lugs see if they have inet friendly places20:14
greg-gyep.  and in general, communicating with the LUGs is a good idea20:14
jcastroIt also doesn't hurt to ensure that there's enough power plugs for everyone, if not, just ask people to bring along power strips or whatever20:14
chuckfand a wireless ap for the group to work off of depending on the venue20:15
greg-gyep20:15
greg-gif there aren't any more venue questions, lets move on to Promotion20:15
jcastrook20:16
jcastroso the biggest thing to help with promotion is to ensure that your loco is on the wiki page20:16
jcastrosince we'll be blogging/twittering, and generally pointing people to that page20:16
jcastroalso, your local team mailing list20:16
jcastroand your local lug mailing list is another place where you might want to send a mail20:17
jcastrolots of LoCo people are also local LUG people so with that overlap it's easy to get the word out20:17
jcastroother places to get the word out include local computer stores and shows20:17
nxvli'm running some packagin jams here for the university lugs and telling them about the GBJ20:18
jcastrolike, before they went out of business, our local CompUSA had a bulletin board where people could post stuff20:18
greg-gnxvl: good deal20:18
jcastroand in general, blogging about it on planet ubuntu, your blog, twitter, etc. etc. is a good way to promote it20:18
nxvlso i prepare people to fix bugs and know how to do them and also i invite them to stay tunned for it20:18
jcastroand if you've noticed we've put the word out on podcasts as well20:18
jcastroany other ideas for promotion?20:19
jcastrooh, your local area in the ubuntu forums if you have one20:19
greg-galong with the LUGs, be sure to contact the local ACM chapter at the university (if there is one)20:19
jcastropointing people to the wiki page so they can get the date/time information, etc.20:19
nxvljcastro: another way to promote event is to exchange publicity for content20:19
nxvlon the local magazines20:19
jcastrolocal university clubs are great, I used to ask CS professors to announce LoCo stuff20:19
nxvlor newspapers20:19
jcastronxvl: ah, right, local media.20:20
nxvlyou give them some content for them to make articles20:20
nxvland ask them to mention the event20:20
jcastroIt would be cool if you could get like a local newspaper, magazine, or radio/tv news or something to cover your event20:20
jcastroin return for highly technical articles. :D20:20
greg-gthats a great idea20:20
jcastrogreg-g: we need to do that!20:20
greg-gnoted20:20
jcastroanything else for Promotion before we get to the "Pre-Bug Jam Checklist of Awesome"?20:21
nxvlwe have used it in some other events and it works fine20:21
nxvl:D20:21
greg-gChecklist of Awesome:20:22
greg-gFirst thing that is critical on the Checklist of Awesome is: ensuring everyone has a Launchpad Account20:22
greg-gwithout that, the participants can't make any bugs better themselves20:22
greg-gChecklist of Awesome number 2: 5-a-day preparedness20:23
greg-gdoes everyone know what 5-a-day is?20:23
* chuckf does20:23
nxvl5-a-day rocks!20:23
greg-gwell, quickly, 5-a-day is a way to have the amount of work you are doing on bugs to be recorded.  but not only for you, but your loco team as well20:24
greg-gthere are instructions at wiki.u.c/5-a-day20:24
greg-gChecklist of Awesome number 3: what package(s) does your group love?20:24
chuckfand there's not a problem of just cutting people loose to decide what they want to handle themselves right?20:25
greg-gto make things like this matter to the participants you don't want to triage bugs for a package no one uses.  Find popular packages that need some love, and get a list out for that package.  At the end of the day people will feel like they really helped20:25
greg-goh right, you can break up into groups and have people interested in similar things work together20:25
greg-g4 or so people per group is probably a good number, depending on how many people come20:26
jcastrochuckf: yeah, the idea is if people want to work on a specific project, then let them break out into groups or whatever20:26
greg-gChecklist of Awesome 4: irc channel for pasting links20:26
jcastrochuckf: some locos might want to target one thing for their entire group, or a specific upstream. Whatever works for you.20:27
greg-gmake sure everyone knows where the loco's irc channel is and how to get on20:27
chuckfk20:27
greg-gChecklist of Awesome 5: have fun!20:27
chuckfand there will, i assume, be a gbj room set up on the weekend20:27
greg-gwell, #ubuntu-bugs will have a bunch of experienced bug triagers20:28
jcastroit'll be in ubuntu-bugs20:28
jcastroso I think the best thing to do20:28
greg-gand then your loco team can be in your channel for more direct communication20:28
jcastrois have people idle in there that want to, but use your local channel for noisier conversation20:28
greg-g(or use gobby)20:28
jcastrobut there should be at least one person in #ubuntu-bugs from your group to coordinate with everyone20:29
greg-gright20:29
jcastroin case you're loco is working on say a certain list of bugs20:29
jcastrowe don't want another loco to come along and start working on the same list20:29
jcastroso we'll use #ubuntu-bugs for your loco to say "we're working on foo!" or whatever20:29
greg-gand, that Checklist of Awesome can be found on the GlobalBugJam/Prep wiki page (I'll add some more to it later).  So, go over that and send out instructions for the simple things before the day of the event20:30
nxvlgreg-g: don't forget about gpg keys20:30
jcastroplease note the tags for the 5-a-day application!20:30
greg-glike "No Launchpage account? No worries!" kinda thins20:30
greg-gnxvl: key signing?20:30
nxvlgreg-g: not, just for people to have gpg keys20:31
chuckfthey are not needed for bug triaging20:31
chuckfI thought20:31
jcastroyeah20:31
greg-gright20:31
jcastrothey're not20:31
nxvlyes, but most of them will want to fix some bugs20:31
greg-gnot needed, but if people ask about them you can do a 1 on 1 with them to set it up20:31
chuckfthough our team is having a tutorial/signing over the next month20:32
nxvlsince there are some really bitsize ones20:32
nxvland it will be great for people to fix them20:32
nxvl:D20:32
jcastroyeah that's fine20:32
jcastrojust don't start off a jam with "and now we're going to do a massive keysigning"20:32
greg-gnxvl: if you have some experienced packagers on hand to help out with that, yeah20:32
greg-gright, takes a lot of time20:32
jcastrodon't want to scare people off too early!20:32
nxvlgreg-g: i am :D20:32
greg-gnxvl: good deal20:33
chuckfour keysigning will be the prior week so it'll be out of the way:)20:33
jcastrogood idea20:33
chuckfwe should be done by the start of this20:33
chuckf:)20:33
jcastroheh20:33
greg-gchuckf: that is a good way to do it.  at some other event like a basic get-together20:33
chuckfours is going to be a the nsa crypto museum20:34
chuckf:)20:34
greg-gnice20:34
greg-ghere is the rundown:20:35
greg-gChecklist of Awesome: 1) Launchpad 2) 5-a-day 3) Popular Packages 4) IRC channel information  5) FUN!20:35
greg-gnext item on the agenda?20:35
nxvl6) Friends!20:35
jcastroRunning it!20:35
jcastroOK, so something we've had success with20:35
jcastrowas a presenter go over a few examples20:35
jcastroso new people get an idea of what to do20:35
nxvlgreg-g: don't forget about the most important part of a community!20:36
jcastroif you have experienced triagers already there, you can break them off into groups with other peopole20:36
greg-gnxvl: beer?20:36
nxvlgreg-g: no, friends!20:36
jcastroso new people have an experienced person in their group to help them20:36
jcastroor you can have one smart person up front answering questions20:36
* greg-g smiles at nxvl 20:36
jcastrowhat we did is started working on our own list of bugs20:36
jcastroand if someone had a question they would yell out the number, and then the person connected to the projector would load it up20:37
jcastroand we would look through it, and decide what to do20:37
chuckfare there any 'demo' bugs in the system that we can use?20:37
jcastroif not, then one person would ask in #ubuntu-bugs20:37
jcastrochuckf: there will be a premade list of bugs, but I should ask about some demo bugs20:37
jcastrothat's a good idea20:37
greg-gnoted20:37
jcastrothe lists of bugs will be made available before the jam20:38
jcastroso basically your loco picks one of the parts of the list20:38
jcastroand starts working on it20:38
chuckfmaybe have a 'gbj-marylandteam' bug20:38
nxvljcastro: also if there are no experienced triagers or packagers, it's cool to have meetings with tome people on the community and start working with them and teaching20:39
jcastrochuckf: wolfger runs our jams, and he's experienced, so usually he just finds a bug in real time and triages it on the spot20:39
nxvls/no/just one/g20:39
jcastronxvl: yep, if everyone is brand new I expect most of the time you will just be teaching20:39
jcastrowhich is why we don't put an emphasis on the amount of bugs you triage20:39
* greg-g nods20:39
chuckfand it's difficult to quota volunteers:)20:40
jcastroat the very minimum, if you get lost, frustrated, or it's turning into a disaster, you can always concentrate on just teaching people little things.20:40
jcastroyeah20:40
jcastroI suspect we'll get a few reports that start off with "We started triaging and then decided to go to the pub instead."20:40
jcastroSo whatever works for you. :D20:41
greg-g:)20:41
greg-gSo, what to do after the GBJ is over?  Good question20:41
nxvljcastro: heh20:41
nxvlgreg-g: key signing and beers20:42
nxvl:D20:42
greg-g1) Put our pictures online (flickr or something) with tags that will help people find them (global-bug-jam-2008 or similar)20:42
chuckftake the spouses/friends out to dinner for abandoning them all day:)20:42
greg-gboth good suggestions :)20:42
greg-g2) beer20:42
greg-g3) spouse/friend dinner20:42
greg-g4) get feedback from the participants20:42
greg-glike how it went, what to do differently next time, etc20:43
greg-gnot formal questionaire or anything, just take notes20:43
greg-g5) plan some future bug jams!20:43
greg-g6) Blog it, blog it, blog it20:43
jcastroyeah, do like a quick feedback thing at the end, where people can say what sucked, what rocked, etc.20:44
jcastroand then put those notes on your loco wiki20:44
greg-gyeah, just generally take some notes on how well it was executed20:44
greg-gright20:44
jcastroso you can say "don't go to this place again!" or "this place was real friendly!"20:44
jcastrothings like that20:44
greg-gincluding information on the venue you used (good/bad/ugly)20:44
jcastroalso, if you could put the feedback in your loco monthly report, that would be great. Also your local list.20:45
jcastrowe'd like to get as much feedback as to how the event went across the world20:45
jcastroeven if it's bad!20:45
greg-gyeah, if it didn't work, it is good to know why20:45
greg-gare there any other questions at this time?20:46
xander21cThe idea is to make it fun instead to be too academic type20:46
greg-gcorrect!20:46
jcastrocool cool!20:46
jcastrothis is going to rock.20:46
greg-gheck yeah, I'm excited for August 8-10th20:47
jcastroany other questions?20:47
xander21cnxvl and I are looking for a fun place with wifi :) in Lima20:47
nxvlyes20:47
jcastroif you think of some later, track me down on irc or you can mail me at jorge at ubuntu.com20:47
nxvlxander21c: i find a nice Starbuck that we can use20:48
chuckfwhat time zone are we starting from:)20:48
xander21cnxvl: nice :)20:48
greg-gchuckf: whenever it is August 8th for you20:48
nxvlchuckf: just any, that's why it's so many days20:48
nxvlxander21c: just use 9th and you will hace no change to fail20:48
nxvl:D20:48
nxvls/ xander21c / chuckf /g20:49
xander21calso can make and advocacy showing Ubuntu + compiz20:49
* chuckf was making a joke after the FF release day compaints20:49
chuckfcomplaints20:49
greg-gchuckf: :)20:49
jcastrochuckf: we're kind of flexible on start/end times20:50
jcastrowhatever works for you20:50
jcastrogreg-g: will you be back for ours?20:50
greg-g:( no20:50
jcastrodang20:50
greg-gI'll be online though as much as I can20:50
snap-lgreg-g: bummer20:50
* nxvl too20:51
nxvllet's make GBJ as cool as we can!20:51
greg-gany other questions/ideas from anyone?20:51
nxvlit need to rock!20:51
greg-git WILL rock! ;)20:52
jcastrowith people like you nxvl how can we fail!20:52
* nxvl HUGS jcastro and greg-g 20:54
* greg-g hugs nxvl back20:54
greg-gand with that: thanks everyone for coming and go have great Bug Jams!20:55
chuckfthanks for the chat!@20:56
greg-gthank you20:56
greg-g... for running a bug jam :)20:57
chuckfkrispy kreme for breakfast and pizza for lunch, what more incentive do I need???20:57
jcastrohave a good one guys!20:58
* jcastro hugs everyone20:58
chuckfoh, helping make the software I use better is just a side benefit:)20:58
greg-gmy best to everyone!20:58
nxvljcastro: be carefull of everyone huging you!21:00
nxvljcastro: as in the flash hug21:00
nxvl:P21:00
jcastroheh21:00
juliux,v _stink_21:01
* xander21c see u later guys21:27
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 22 Jun 18:00 UTC: Ubuntu Mozilla Team | 24 Jun 15:00 UTC: Server Team | 24 Jun 18:00 UTC: LoCo Council | 25 Jun 17:00 UTC: QA Team | 25 Jun 22:00 UTC: Platform Team | 26 Jun 10:00 UTC: MOTU School Session - Apport retraces
=== cody-somerville_ is now known as cody-somerville

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