=== 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-somerville | I gotta run. j1mc is going to host the meeting for me :) | 17:57 |
cody-somerville | Have fun fellows | 17:57 |
j1mc | hi all - who all is here? | 17:59 |
TheSheep | cody-somerville: so I guess the meeting is cancelled? | 19:11 |
techno_freak | oh? | 19:12 |
jcastro | 10 minutes until "How to Run a Bug Jam"! | 19:49 |
ccm | good luck with it, jcastro :) | 19:55 |
greg-g | no luck needed ;) | 19:55 |
ccm | right. just kind of an idiom :) | 19:56 |
jcastro | heh | 19:57 |
jcastro | greg-g: do you know how to control the bot? | 19:58 |
greg-g | no clue | 19:59 |
jcastro | heh, no worries | 19:59 |
jcastro | ok, I guess we should start with introductions | 20:00 |
jcastro | I'm jorge castro, I'm on the ubuntu community team. | 20:00 |
greg-g | Hello 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-g | my name is Greg Grossmeier and the leader of the Michigan (US) LoCo Team | 20:00 |
jcastro | so if you're here from the meeting please say hello! | 20:01 |
jcastro | and what team you're representing. (or if you're just hanging out) | 20:01 |
jacob | i might be ducking in and out (was in here yesterday) but I suppose i'm here. Hello from Ohio! | 20:01 |
greg-g | Hello jacob | 20:02 |
* chuckf representing MarylandTeam | 20:02 | |
greg-g | welcome | 20:02 |
jcastro | I see Maryland already has all their stuff filed out on the wiki | 20:02 |
nxvl | jcastro: #startmeeting | 20:03 |
jcastro | nxvl: ah | 20:03 |
chuckf | largly, yeah | 20:03 |
jcastro | #startmeeting | 20:03 |
jcastro | like that? | 20:03 |
jcastro | ok whatever, let's get started! | 20:03 |
jcastro | https://wiki.ubuntu.com/GlobalBugJam | 20:03 |
nxvl | yes, mathiaz always use something like that | 20:03 |
jcastro | this is the main page we're going to use for coordinating the jam | 20:03 |
greg-g | and tips for how to run it: https://wiki.ubuntu.com/GlobalBugJam/Prep | 20:04 |
jcastro | https://wiki.ubuntu.com/GlobalBugJam/Prep | 20:04 |
jcastro | and this page is what we're going to discuss today | 20:04 |
* nxvl represents Peru | 20:04 | |
jcastro | so if you remember one thing, it's that last URL. :) | 20:04 |
jcastro | Ok, before we get into the nitty gritty | 20:04 |
jcastro | the first thing that is most important for the Jam | 20:04 |
jcastro | is that everyone has a good time. | 20:04 |
* greg-g nods | 20:05 | |
jcastro | If 300 people show up | 20:05 |
jcastro | and you only triage 1 bug, then that's totally fine | 20:05 |
jcastro | the idea is to get Local teams together and having a good time | 20:05 |
jcastro | so 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 want | 20:05 |
jcastro | we would like to see LoCos just running jams on their own and doing what their members want to do | 20:06 |
jcastro | so hopefully we can make these fun so people want to do them | 20:06 |
jcastro | so for example | 20:06 |
jcastro | we just had a jam in michigan | 20:06 |
jcastro | and due to weather only 3 people showed up | 20:06 |
jcastro | but we still had a great time | 20:06 |
* greg-g and me being in California | 20:06 | |
jcastro | so 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 |
jcastro | don't use raw numbers or bug counts as your measurement of success | 20:07 |
jcastro | those are just great side effects. :) | 20:07 |
jcastro | Any questions so far? | 20:07 |
chuckf | nope | 20:07 |
jcastro | greg-g: want to go into venues? | 20:07 |
jcastro | we can alternate on topics | 20:07 |
greg-g | sure | 20:07 |
siretart | FYI, we are having a BugJam right now in nueremberg, with 15 attendees (including myself) :) | 20:07 |
greg-g | siretart: nice! | 20:07 |
jcastro | siretart: oh well, that's awesome! | 20:08 |
nxvl | jcastro: i have a doubt | 20:08 |
greg-g | ? | 20:08 |
nxvl | jcastro: the idea of the GBJ is to fix bugs or just to triage them, or both of them? | 20:08 |
jcastro | nxvl: fix would be nice, but shoot for triage | 20:08 |
* greg-g nods | 20:08 | |
jcastro | nxvl: people should know how to triage | 20:08 |
nxvl | jcastro: so the goal is triaging, but if you fix them it's even nicer? | 20:09 |
jcastro | and as your bug jams progress your team can go as advanced as they want | 20:09 |
jcastro | yep, of course. :D | 20:09 |
greg-g | So, Venues... | 20:09 |
greg-g | You need some place that has power, internet, and places to sit for everyone that is going to show up (obviously) | 20:09 |
greg-g | but, it also needs to be conducive to listening to one person talking for a little bit and asking questions | 20:09 |
greg-g | some good places are offices of Open Source Friendly businesses or even Library conference rooms (where Michigan had ours) | 20:10 |
greg-g | where is your bug jam going on siretart ? | 20:10 |
jcastro | I 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 house | 20:11 |
greg-g | There we had the essentials plus nice seating and food and drinks | 20:11 |
greg-g | so really, anywhere that is comfortable and conducive to group work. | 20:12 |
greg-g | and, cheap :) | 20:12 |
greg-g | any questions on venues? or other suggestions before we move on? | 20:13 |
chuckf | colleges | 20:13 |
jcastro | Colleges are always good | 20:13 |
greg-g | good one | 20:13 |
chuckf | the cis groups tend to have presentation/work rooms available on weekends | 20:13 |
nxvl | we are thinking on running ours on a starbucks | 20:13 |
jcastro | because you can link up with like a computer club or ACM or something and get more participation | 20:13 |
greg-g | just make sure you have a way for everyone to get internet access where ever you are | 20:14 |
chuckf | also check with local lugs see if they have inet friendly places | 20:14 |
greg-g | yep. and in general, communicating with the LUGs is a good idea | 20:14 |
jcastro | It 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 whatever | 20:14 |
chuckf | and a wireless ap for the group to work off of depending on the venue | 20:15 |
greg-g | yep | 20:15 |
greg-g | if there aren't any more venue questions, lets move on to Promotion | 20:15 |
jcastro | ok | 20:16 |
jcastro | so the biggest thing to help with promotion is to ensure that your loco is on the wiki page | 20:16 |
jcastro | since we'll be blogging/twittering, and generally pointing people to that page | 20:16 |
jcastro | also, your local team mailing list | 20:16 |
jcastro | and your local lug mailing list is another place where you might want to send a mail | 20:17 |
jcastro | lots of LoCo people are also local LUG people so with that overlap it's easy to get the word out | 20:17 |
jcastro | other places to get the word out include local computer stores and shows | 20:17 |
nxvl | i'm running some packagin jams here for the university lugs and telling them about the GBJ | 20:18 |
jcastro | like, before they went out of business, our local CompUSA had a bulletin board where people could post stuff | 20:18 |
greg-g | nxvl: good deal | 20:18 |
jcastro | and in general, blogging about it on planet ubuntu, your blog, twitter, etc. etc. is a good way to promote it | 20:18 |
nxvl | so i prepare people to fix bugs and know how to do them and also i invite them to stay tunned for it | 20:18 |
jcastro | and if you've noticed we've put the word out on podcasts as well | 20:18 |
jcastro | any other ideas for promotion? | 20:19 |
jcastro | oh, your local area in the ubuntu forums if you have one | 20:19 |
greg-g | along with the LUGs, be sure to contact the local ACM chapter at the university (if there is one) | 20:19 |
jcastro | pointing people to the wiki page so they can get the date/time information, etc. | 20:19 |
nxvl | jcastro: another way to promote event is to exchange publicity for content | 20:19 |
nxvl | on the local magazines | 20:19 |
jcastro | local university clubs are great, I used to ask CS professors to announce LoCo stuff | 20:19 |
nxvl | or newspapers | 20:19 |
jcastro | nxvl: ah, right, local media. | 20:20 |
nxvl | you give them some content for them to make articles | 20:20 |
nxvl | and ask them to mention the event | 20:20 |
jcastro | It would be cool if you could get like a local newspaper, magazine, or radio/tv news or something to cover your event | 20:20 |
jcastro | in return for highly technical articles. :D | 20:20 |
greg-g | thats a great idea | 20:20 |
jcastro | greg-g: we need to do that! | 20:20 |
greg-g | noted | 20:20 |
jcastro | anything else for Promotion before we get to the "Pre-Bug Jam Checklist of Awesome"? | 20:21 |
nxvl | we have used it in some other events and it works fine | 20:21 |
nxvl | :D | 20:21 |
greg-g | Checklist of Awesome: | 20:22 |
greg-g | First thing that is critical on the Checklist of Awesome is: ensuring everyone has a Launchpad Account | 20:22 |
greg-g | without that, the participants can't make any bugs better themselves | 20:22 |
greg-g | Checklist of Awesome number 2: 5-a-day preparedness | 20:23 |
greg-g | does everyone know what 5-a-day is? | 20:23 |
* chuckf does | 20:23 | |
nxvl | 5-a-day rocks! | 20:23 |
greg-g | well, 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 well | 20:24 |
greg-g | there are instructions at wiki.u.c/5-a-day | 20:24 |
greg-g | Checklist of Awesome number 3: what package(s) does your group love? | 20:24 |
chuckf | and there's not a problem of just cutting people loose to decide what they want to handle themselves right? | 20:25 |
greg-g | to 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 helped | 20:25 |
greg-g | oh right, you can break up into groups and have people interested in similar things work together | 20:25 |
greg-g | 4 or so people per group is probably a good number, depending on how many people come | 20:26 |
jcastro | chuckf: yeah, the idea is if people want to work on a specific project, then let them break out into groups or whatever | 20:26 |
greg-g | Checklist of Awesome 4: irc channel for pasting links | 20:26 |
jcastro | chuckf: some locos might want to target one thing for their entire group, or a specific upstream. Whatever works for you. | 20:27 |
greg-g | make sure everyone knows where the loco's irc channel is and how to get on | 20:27 |
chuckf | k | 20:27 |
greg-g | Checklist of Awesome 5: have fun! | 20:27 |
chuckf | and there will, i assume, be a gbj room set up on the weekend | 20:27 |
greg-g | well, #ubuntu-bugs will have a bunch of experienced bug triagers | 20:28 |
jcastro | it'll be in ubuntu-bugs | 20:28 |
jcastro | so I think the best thing to do | 20:28 |
greg-g | and then your loco team can be in your channel for more direct communication | 20:28 |
jcastro | is have people idle in there that want to, but use your local channel for noisier conversation | 20:28 |
greg-g | (or use gobby) | 20:28 |
jcastro | but there should be at least one person in #ubuntu-bugs from your group to coordinate with everyone | 20:29 |
greg-g | right | 20:29 |
jcastro | in case you're loco is working on say a certain list of bugs | 20:29 |
jcastro | we don't want another loco to come along and start working on the same list | 20:29 |
jcastro | so we'll use #ubuntu-bugs for your loco to say "we're working on foo!" or whatever | 20:29 |
greg-g | and, 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 event | 20:30 |
nxvl | greg-g: don't forget about gpg keys | 20:30 |
jcastro | please note the tags for the 5-a-day application! | 20:30 |
greg-g | like "No Launchpage account? No worries!" kinda thins | 20:30 |
greg-g | nxvl: key signing? | 20:30 |
nxvl | greg-g: not, just for people to have gpg keys | 20:31 |
chuckf | they are not needed for bug triaging | 20:31 |
chuckf | I thought | 20:31 |
jcastro | yeah | 20:31 |
greg-g | right | 20:31 |
jcastro | they're not | 20:31 |
nxvl | yes, but most of them will want to fix some bugs | 20:31 |
greg-g | not needed, but if people ask about them you can do a 1 on 1 with them to set it up | 20:31 |
chuckf | though our team is having a tutorial/signing over the next month | 20:32 |
nxvl | since there are some really bitsize ones | 20:32 |
nxvl | and it will be great for people to fix them | 20:32 |
nxvl | :D | 20:32 |
jcastro | yeah that's fine | 20:32 |
jcastro | just don't start off a jam with "and now we're going to do a massive keysigning" | 20:32 |
greg-g | nxvl: if you have some experienced packagers on hand to help out with that, yeah | 20:32 |
greg-g | right, takes a lot of time | 20:32 |
jcastro | don't want to scare people off too early! | 20:32 |
nxvl | greg-g: i am :D | 20:32 |
greg-g | nxvl: good deal | 20:33 |
chuckf | our keysigning will be the prior week so it'll be out of the way:) | 20:33 |
jcastro | good idea | 20:33 |
chuckf | we should be done by the start of this | 20:33 |
chuckf | :) | 20:33 |
jcastro | heh | 20:33 |
greg-g | chuckf: that is a good way to do it. at some other event like a basic get-together | 20:33 |
chuckf | ours is going to be a the nsa crypto museum | 20:34 |
chuckf | :) | 20:34 |
greg-g | nice | 20:34 |
greg-g | here is the rundown: | 20:35 |
greg-g | Checklist of Awesome: 1) Launchpad 2) 5-a-day 3) Popular Packages 4) IRC channel information 5) FUN! | 20:35 |
greg-g | next item on the agenda? | 20:35 |
nxvl | 6) Friends! | 20:35 |
jcastro | Running it! | 20:35 |
jcastro | OK, so something we've had success with | 20:35 |
jcastro | was a presenter go over a few examples | 20:35 |
jcastro | so new people get an idea of what to do | 20:35 |
nxvl | greg-g: don't forget about the most important part of a community! | 20:36 |
jcastro | if you have experienced triagers already there, you can break them off into groups with other peopole | 20:36 |
greg-g | nxvl: beer? | 20:36 |
nxvl | greg-g: no, friends! | 20:36 |
jcastro | so new people have an experienced person in their group to help them | 20:36 |
jcastro | or you can have one smart person up front answering questions | 20:36 |
* greg-g smiles at nxvl | 20:36 | |
jcastro | what we did is started working on our own list of bugs | 20:36 |
jcastro | and if someone had a question they would yell out the number, and then the person connected to the projector would load it up | 20:37 |
jcastro | and we would look through it, and decide what to do | 20:37 |
chuckf | are there any 'demo' bugs in the system that we can use? | 20:37 |
jcastro | if not, then one person would ask in #ubuntu-bugs | 20:37 |
jcastro | chuckf: there will be a premade list of bugs, but I should ask about some demo bugs | 20:37 |
jcastro | that's a good idea | 20:37 |
greg-g | noted | 20:37 |
jcastro | the lists of bugs will be made available before the jam | 20:38 |
jcastro | so basically your loco picks one of the parts of the list | 20:38 |
jcastro | and starts working on it | 20:38 |
chuckf | maybe have a 'gbj-marylandteam' bug | 20:38 |
nxvl | jcastro: 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 teaching | 20:39 |
jcastro | chuckf: wolfger runs our jams, and he's experienced, so usually he just finds a bug in real time and triages it on the spot | 20:39 |
nxvl | s/no/just one/g | 20:39 |
jcastro | nxvl: yep, if everyone is brand new I expect most of the time you will just be teaching | 20:39 |
jcastro | which is why we don't put an emphasis on the amount of bugs you triage | 20:39 |
* greg-g nods | 20:39 | |
chuckf | and it's difficult to quota volunteers:) | 20:40 |
jcastro | at 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 |
jcastro | yeah | 20:40 |
jcastro | I 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 |
jcastro | So whatever works for you. :D | 20:41 |
greg-g | :) | 20:41 |
greg-g | So, what to do after the GBJ is over? Good question | 20:41 |
nxvl | jcastro: heh | 20:41 |
nxvl | greg-g: key signing and beers | 20:42 |
nxvl | :D | 20:42 |
greg-g | 1) Put our pictures online (flickr or something) with tags that will help people find them (global-bug-jam-2008 or similar) | 20:42 |
chuckf | take the spouses/friends out to dinner for abandoning them all day:) | 20:42 |
greg-g | both good suggestions :) | 20:42 |
greg-g | 2) beer | 20:42 |
greg-g | 3) spouse/friend dinner | 20:42 |
greg-g | 4) get feedback from the participants | 20:42 |
greg-g | like how it went, what to do differently next time, etc | 20:43 |
greg-g | not formal questionaire or anything, just take notes | 20:43 |
greg-g | 5) plan some future bug jams! | 20:43 |
greg-g | 6) Blog it, blog it, blog it | 20:43 |
jcastro | yeah, do like a quick feedback thing at the end, where people can say what sucked, what rocked, etc. | 20:44 |
jcastro | and then put those notes on your loco wiki | 20:44 |
greg-g | yeah, just generally take some notes on how well it was executed | 20:44 |
greg-g | right | 20:44 |
jcastro | so you can say "don't go to this place again!" or "this place was real friendly!" | 20:44 |
jcastro | things like that | 20:44 |
greg-g | including information on the venue you used (good/bad/ugly) | 20:44 |
jcastro | also, if you could put the feedback in your loco monthly report, that would be great. Also your local list. | 20:45 |
jcastro | we'd like to get as much feedback as to how the event went across the world | 20:45 |
jcastro | even if it's bad! | 20:45 |
greg-g | yeah, if it didn't work, it is good to know why | 20:45 |
greg-g | are there any other questions at this time? | 20:46 |
xander21c | The idea is to make it fun instead to be too academic type | 20:46 |
greg-g | correct! | 20:46 |
jcastro | cool cool! | 20:46 |
jcastro | this is going to rock. | 20:46 |
greg-g | heck yeah, I'm excited for August 8-10th | 20:47 |
jcastro | any other questions? | 20:47 |
xander21c | nxvl and I are looking for a fun place with wifi :) in Lima | 20:47 |
nxvl | yes | 20:47 |
jcastro | if you think of some later, track me down on irc or you can mail me at jorge at ubuntu.com | 20:47 |
nxvl | xander21c: i find a nice Starbuck that we can use | 20:48 |
chuckf | what time zone are we starting from:) | 20:48 |
xander21c | nxvl: nice :) | 20:48 |
greg-g | chuckf: whenever it is August 8th for you | 20:48 |
nxvl | chuckf: just any, that's why it's so many days | 20:48 |
nxvl | xander21c: just use 9th and you will hace no change to fail | 20:48 |
nxvl | :D | 20:48 |
nxvl | s/ xander21c / chuckf /g | 20:49 |
xander21c | also can make and advocacy showing Ubuntu + compiz | 20:49 |
* chuckf was making a joke after the FF release day compaints | 20:49 | |
chuckf | complaints | 20:49 |
greg-g | chuckf: :) | 20:49 |
jcastro | chuckf: we're kind of flexible on start/end times | 20:50 |
jcastro | whatever works for you | 20:50 |
jcastro | greg-g: will you be back for ours? | 20:50 |
greg-g | :( no | 20:50 |
jcastro | dang | 20:50 |
greg-g | I'll be online though as much as I can | 20:50 |
snap-l | greg-g: bummer | 20:50 |
* nxvl too | 20:51 | |
nxvl | let's make GBJ as cool as we can! | 20:51 |
greg-g | any other questions/ideas from anyone? | 20:51 |
nxvl | it need to rock! | 20:51 |
greg-g | it WILL rock! ;) | 20:52 |
jcastro | with people like you nxvl how can we fail! | 20:52 |
* nxvl HUGS jcastro and greg-g | 20:54 | |
* greg-g hugs nxvl back | 20:54 | |
greg-g | and with that: thanks everyone for coming and go have great Bug Jams! | 20:55 |
chuckf | thanks for the chat!@ | 20:56 |
greg-g | thank you | 20:56 |
greg-g | ... for running a bug jam :) | 20:57 |
chuckf | krispy kreme for breakfast and pizza for lunch, what more incentive do I need??? | 20:57 |
jcastro | have a good one guys! | 20:58 |
* jcastro hugs everyone | 20:58 | |
chuckf | oh, helping make the software I use better is just a side benefit:) | 20:58 |
greg-g | my best to everyone! | 20:58 |
nxvl | jcastro: be carefull of everyone huging you! | 21:00 |
nxvl | jcastro: as in the flash hug | 21:00 |
nxvl | :P | 21:00 |
jcastro | heh | 21:00 |
juliux | ,v _stink_ | 21:01 |
* xander21c see u later guys | 21: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!