=== dk__ is now known as CrossDK === rgreening_ is now known as rgreening === CrossDK is now known as DKcross === santiago-pgsql is now known as santiago-ve === olujicz_ is now known as olujicz === AndrewGe1 is now known as AndrewGee === Bram_ is now known as Bram [15:50] 10 minutes! [15:52] hi ppl [15:52] i know c/c++ and java to somewhat ok level [15:53] i want to help in floss software [15:53] by writing/fixing code [15:53] can anybody guide me from where i should start and how? [15:53] find a project on launchpad and dig in? [15:53] is there a good book on the tools used or some good resources> [15:54] dig in? [15:54] jcastro: what all should i know before i can dig in? [15:54] git?gtk? [15:54] or is there some good beginner's guide or something? [15:54] I would just browse a project and pull it with bzr and just start messing with it [15:55] there's no real guide afaik [15:55] start by fiding a project that interess you, then you will know what to learn to be able to contribute to it [15:55] or you could find a project you care about and mail their list asking for a place to start [15:55] what bram said! [15:55] (5 minutes until "How to Run A Jam" session!) [15:57] tgpraveen: are there any soft you use and you like that you think miss a feature or in witch one you want to invest ? (avoid soft like firefox or the entire gnome/kde :p) [15:57] yeah, start with something small [15:58] Bram: i am intrested in telepathy/empathy [15:58] tgpraveen: also, if you search launchpad for "bitesize" bugs there are usually little one liners and stuff you can fix [15:58] tgpraveen: #telepathy on freenode I believe. [15:58] project and i hang out in their irc channel and file a lot of bugs and all but dont know how i [15:58] should start with the code part [15:59] their really needs to be a nice starting point/beginner's guide explaining and guiding to stuff like what the version control tools are, what toolkits are etc [15:59] tgpraveen: oh I know some of the dev of this project, do you know glib and others gnome techno ? [15:59] tgpraveen: yeah that's been a problem for a long time [15:59] they do a lot of C and some python and if my memory is good they uses git [15:59] Bram: no i am absolute beginner [16:00] unfortunately lots of projects do things differently, so one true guide would be difficult [16:00] Bram: so what so what gnome technology should i specifically learn [16:00] ok, who is here for the How to Run a Jam session? [16:00] should i begin with learning glib? if so what is best way to do so? [16:00] me :) [16:01] woo! [16:01] jcastro: me to [16:01] :D [16:01] ok, let's give it a few minutes for the stragglers [16:01] and then we'll begin [16:01] https://wiki.ubuntu.com/Jams [16:01] for those of you who want to cheat [16:02] first time to ubuntu-mx, so want to know what to do in a better way xD [16:02] tgpraveen: I don't know exactly what techno they use but start hacking in C/glib and start to learn how to use git [16:02] tgpraveen: btw it's a big project but I think if you ask them they will find some small bugs that you can fix [16:04] Bram: ok i have started with learning git. what do u mean by hacking in glib? reading their docs? [16:04] tgpraveen: make some c code using the glib [16:05] ok, let's get started [16:05] tgpraveen: we have a session now in this channel [16:05] hmm... ok. Bram jcastro thx for ur help bye [16:05] can you guys move the discussion to -chat or something? [16:05] tgpraveen: don't leave permanently! [16:05] jcastro: ok [16:05] tgpraveen: check out the gnome love project as well [16:05] it's designed to get people started [16:06] that will at least move in you the right direction [16:06] ok, so this session is How to Run a Successful Jam [16:06] please holler if you're here for that and from what local team you are from [16:07] yep, from Ubuntu-Quebec [16:07] ok, so the reason we are doing these sessions [16:07] is to give people some best practice knowledge on how to run jams, and share good ideas [16:07] and tell you what NOT to do, heh [16:07] ok, so in October we are having what we call the Ubuntu Global Jam [16:07] https://wiki.ubuntu.com/UbuntuGlobalJam [16:08] we do one of these per cycle [16:08] in the past we called them the Ubuntu Global Bug Jam [16:08] because all we did was bugs, but this year we're going bigger because that's how we roll [16:08] so the idea is that over a weekend, ubuntu local teams from around the world go do awesome things. [16:08] https://wiki.ubuntu.com/UbuntuGlobalJam/Events [16:09] so right now locos are signing up to do bug jams, installfests, translation jams, whatever your team feels they can contribute to the most. [16:09] the fundamental thing to remember about jams is that they're ALL about your local team [16:09] the goal of all these jams is for your loco team to get together and have a good time. [16:10] when you start off with a jam some locos get bent around the axle on details [16:10] like "we only triaged X amount of bugs, we failed!" [16:10] don't think of it that way [16:10] the coordinated work around the world is great and helps ubuntu tremendously, but getting your loco together and forming those bonds is the key there [16:11] our first jam was pretty much a disaster [16:11] by the time you do a few they will be second-hand [16:11] so don't worry too much if you have a bug jam and you don't get through alot of bugs or something [16:11] the main key is to develop your local team [16:11] any questions so far? [16:12] ok [16:12] So, we happen to have a place where we write down all the good practices on running jams: [16:12] https://wiki.ubuntu.com/Jams [16:12] The most annoying bit is figuring out a venue [16:12] this can be difficult or easy, depending on where you live [16:13] usually what we do is assign one person to deal with a venue [16:13] and then they call around or whatever [16:13] one thing to remember is the audience of your loco [16:13] so for example if you have a bunch of teenagers who want to help you wouldn't want to have your jam in a pub where they can't get in. :D [16:14] power and internet access is pretty important as well [16:14] In our loco we find that having a projector is useful [16:14] if someone in the jam "gets stuck" on something we put it up on the projector [16:14] and then the group discusses how they would triage that bug [16:14] or work on that piece of code [16:14] or whatever [16:15] so if you have access to a projector that helps people collaborate [16:15] it also encourages people to discuss things out loud instead of migrating to their little groups and sticking their heads in a laptop for hours without talking to people. [16:15] how suitable would it be to have the jam in a university? [16:15] universities are perfect [16:15] for a couple of reasons [16:16] first off, they have a bunch of students and student organizations [16:16] they also have good internet connections [16:16] and projectors [16:16] when we did installfests here we got with the local computer science department at the university [16:16] and they lent us routers, switches, cables, all sorts of stuff [16:16] the dean even stopped by! [16:17] students are always motivated (more than us old people), so I encourage you to definatly take advantage of hosting at a university [16:17] you can even sometimes have interested professors stopping by [16:17] which is nice because you can tell them about linux and open source, and hopefully get them interested [16:18] if they get interested they will want more information, so your loco can help them with that [16:18] (projector == bug manager ?) [16:18] Bram: what do you mean? [16:18] 17:14 In our loco we find that having a projector is useful [16:18] yeah [16:18] so what we do, is we break up into teams [16:18] and start triaging bugs [16:18] (we do bug jams) [16:18] and then when someone gets stuck [16:18] we put the bug on the projector [16:19] and then we all talk about how we should triage it [16:19] and usually a more experienced person will say "we should mark this bug as confirmed" (or whatever) [16:19] then people agree and/or discuss [16:19] then we go back to our bug lists. [16:19] we use it as a "I need help from the group" type thing [16:20] you can also use it to put your todo list up there [16:20] or use a whiteboard if available, etc. [16:20] Any other questions on venue or equipment? [16:21] yes, I do have a question: [16:21] Ok, the next step is promoting your event [16:21] this is where you get alot of bang for the buck [16:21] you want to post to local lists [16:21] so here, we try to promote it to local lugs, local python and java groups, and other techie groups in the area [16:22] putting up posters at universities has also been useful for us. [16:22] some of the larger locos like France have signs and all sorts of goodies already premade and ready to be modified [16:22] you can post on loco-contacts to ask around for resources other local teams have made [16:22] there are a ton of things on the wiki you can remix and reuse to make nice looking posters if you want [16:23] also blogging about it, getting it on the ubuntu weekly news, things like that always help [16:23] and don't forget mentioning it on the forums! [16:23] one useful place I've seen people have good success with is their local computer store [16:24] usually you can put off a little sheet with your list address or something and stick it on the bulletin board. [16:24] this is a good random way of getting people interested in open source in general. [16:24] sometimes we try to have a jam and random new people just show up [16:25] which we don't plan for but when it happens you should look at it as a good opportunity to educate them about ubuntu, give them a CD, and answer questions [16:25] even if they're only vaguely interesting at the minimum when they go home they will say "wow, what a nice bunch of people" :) [16:25] having beers works to :p [16:26] When it comes to the jam itself really the only way to learn it is to do it [16:26] yes, beer helps! [16:26] we coordinate with other locos during the jam to see what's going on [16:26] in fact last year the guys from chicago called us to see how we were doing. [16:26] and we shared some tips over the phone [16:27] absolutely do not be afraid to ask other, more established locos for help and guidance. [16:27] annoted xD [16:27] We added docs jams this time too [16:27] so an easy one to get started with would be to ask around what people are interested in when they get there [16:27] and then maybe go to the wiki page of that thing [16:27] and collectively fix it [16:28] a great tool to use for this is gobby [16:28] which is a collaborative text editor [16:28] you can grab the wiki page, everyone can work on different parts at the same time, and then one person can just upload it [16:28] or you can grab a bunch of wiki pages [16:28] and assign them to teams or whatever [16:29] I like to try to assign people into little teams [16:29] usually like, an experienced person with a new person [16:29] so that they can learn from each other [16:29] that way, by the time the next jam starts, you'll have 2 experienced people. :D [16:29] but you can organize however you want [16:29] some people just want to show up and they already have a list of things to work on [16:29] so just let them do their thing [16:29] some people want more detailed tutorials on how to do stuff [16:30] that's fine too [16:30] as long as your group feels it's doing something valuable then anything goes. [16:30] sometimes we've had plans and new people show up and we end up just spending the whole time telling new people how to report a bug or something. [16:31] and that's ok. [16:31] so while your jam is running it's important to talk to the rest of the world [16:31] we have people in irc saying hi to each other and talking about what they are working on [16:31] you mean, other locos?? [16:31] yep [16:31] :) [16:31] this is where the whole "Global" thing comes in [16:31] actually, putting the global channel on the projector would be fun too [16:32] it makes you feel like the entire planet is working on ubuntu at the same time [16:32] but it's also good for coordinating work [16:32] one group might say "hey, over here in michigan-us we are working on amarok bugs, anyone want to help out?" or whatever [16:32] you can also have friendly competitions as well [16:33] which I think all the germans do, heh [16:33] while the event is happening you should be telling the world about it [16:33] and taking pictures and everything. [16:33] one thing we learned was that by taking pictures of everyone having a good time this helps you next time when you are working on planning it [16:34] because people see the pictures and say "wow, I should have gone, I will go to the next one, look at all those beers!" [16:34] besides, it's good for the posters [16:34] and of course we encourage you to put them on posters, etc. [16:34] yep! [16:34] and on your wiki as well [16:34] we like to showcase the diversity of our local teams, so the more pictures you put up, the cooler the posters and presentations look. :D [16:35] this helps build up buzz and excitement [16:35] ok, so let's talk about some things to avoid [16:35] first off, it's important that your venue stuff is squared away [16:35] having 50 geeks show up to a pub with no internet is a buzzkill [16:36] or someone forgets to make a reservation or whatever. [16:36] also you should pick a location that is open and is agreeable to most people [16:37] when I planned our first release party for ubuntu here in 2005, I did it in a bar and there were a bunch of people smoking [16:37] and people who were nonsmokers were choking to death [16:37] so just something to think about [16:37] (now we try to have them outside, heh) [16:37] also you should ensure that you're not leaving people out because they might not be experienced with ubuntu [16:38] "sorry you can't participate this is for developers only" or whatever wouldn't be right [16:38] but you all know that, that's common sense. :D [16:38] any other bad ideas? [16:39] oh [16:39] you should definately do a team report at the end [16:39] https://wiki.ubuntu.com/TeamReports [16:39] basically you just fire off a mail [16:39] telling us how many people showed up [16:39] and what you learned, links to pictures, whatever [16:40] this helps us see how well the event is running and things we need to fix in our planning [16:40] it also helps us be able to map out resources better [16:40] so for example if it's like "we tried to have a bug jam in mexico but jorge never told me how to get started" would be a good one. :D [16:41] xD [16:41] it also helps us link up locos to each other [16:41] xD [16:41] so for example if you had a doc jam and it went ok, maybe next time we can ask a doc team member to join you on irc to give you tips, things like that [16:41] any questions? That pretty much covers it. [16:42] sweet :D [16:42] hey, I have a question [16:42] of course, when you get good ideas, feel free to add them to the wiki [16:42] jorgevazq: shoot! [16:42] here in Mexico we have been thinking about streaming parts of the jam [16:42] oh [16:43] that is a good idea! [16:43] since we can't all move to mexico city [16:43] stupid question: have you ever tried to make a jam on irc ? [16:43] if you have the bandwidth to do that, that would be great [16:43] cool =) [16:43] Bram: for people that don't have locos they participate in irc [16:43] Bram: but IRC is less... personal [16:43] Bram: in fact the Club Ubuntu virtual loco is one of the larger participants [16:43] and the purpose of jams is to unite the LoCos [16:44] Bram: what we do here since the jam is all weekend is also jam on irc before and after the actual event [16:44] that's a good idea [16:44] also [16:44] it's a good idea to tell people things on irc before the event [16:44] like "I will need help learning how to do foo and bar" [16:45] ah question: I'm assuming not all LoCos have events running all through the weekend, correct? [16:45] no [16:45] the weekend is there just so locos can be flexible to plan stuff [16:45] you don't need to have a 48 hour jam [16:45] heh [16:45] also, you don't even need to do it on that weekend. [16:45] this is just a timed event [16:45] your loco can jam whenever you want [16:46] do it as many times as you want in a cycle, whatever works for you [16:46] you can also have targetted jams too [16:46] like, "hey guys, it's 5 weeks until release, anyone wanna jam and triage some bugs?" [16:46] :O [16:46] (didn't know that) [16:46] how long do the jams normally last for, what times do you find best to run them? [16:47] ours are about 3 hours? [16:47] we do them in the afternoon so we can go to dinner after [16:47] they don't all have to be boring and stuff either [16:47] have a picnic, or relax too [16:48] jorgevazq: we have totally social jams too, but most people just call those normal loco meetings. [16:48] oooh oohh, for pictures [16:48] normal pictures of people are fine [16:48] but try to have a group picture [16:48] hoho, so they don't have to look like they're hacking a bank [16:48] because we put a bunch of those together to make mashups and stuff [16:49] just people javing fun [16:49] no, you can also have good jams without computers [16:49] you can tutorials, lightning talks, remember, the purpose of the jam is to improve your local team [16:49] so if you want to have a 5 hour session on how to use the gimp or something, then rock on with that. [16:50] can we try other crazy stuff, like translating ubuntu to Mexican-Spanish?? [16:50] yep [16:50] sweet [16:51] if you look on the events list you can do "Translations Jams" [16:51] in fact, those are new, I don't think anyone has done that yet [16:51] that would be a cool way to break some new ground [16:51] any other questions before I wrap up? [16:54] ok well I hope you found this session informative [16:54] I certainly had a good time! [16:54] as always, please feel free to post to the loco list if you have questions [16:54] or feel free to mail me at jorge@ubuntu.com if you need help [16:54] which loco are you from? [16:54] I am from michigan [16:54] in the us. [16:54] cool... greetings from mexico [16:55] I am hoping to go to mexico for vacation! [16:55] jcastro: thanks for this session o/ [16:55] jcastro: we just finished running a packagejam today in south africa. 11 people :) [16:55] stefanlsd: that's great! [16:55] stefanlsd: hey you do the gears PPA right? [16:56] jcastro: yeah [16:56] hero. [16:56] I am running it with mozilla prism so I have a nice offline gmail thing on my laptop [16:56] it's totally great [16:56] i'd be happier if i could actually get it through revu. ^ awesome! [16:56] ok, I am going to go have lunch, everyone have a great weekend! [16:56] lol [16:56] would be a nice idea [16:56] stefanlsd: yeah I have been trying to find a gears upstream to help us with that license thing [16:56] same to you :D [16:56] stefanlsd: I will find you on monday and we can talk! [16:57] cheers everyone! [16:57] see you later [16:57] =) [16:57] jcastro: kk. thanks. cheers :) [16:57] we'll be in touch... i hope === lex79 is now known as lex === lex is now known as lex79 === yofel_ is now known as yofel === Quintasan is now known as mzajac [18:55] La primera charla de la tarde "Dale el efecto wow a tu escritorio" [18:56] Laura Delgado comienza cambiando el fondo del escritorio === mzajac is now known as Quintasan === rgreening is now known as Barbie === Barbie is now known as Chewie === Chewie is now known as Vader === Vader is now known as hsitter === hsitter is now known as not_hsitter_hone === not_hsitter_hone is now known as rgreening