=== jasono is now known as Jasono === _LibertyZero is now known as LibertyZero [07:21] is this a place where i can get help on my ubuntu troubles? [16:13] * JackyAlcine will be right back. [16:58] Hey TLE [16:58] Hey [17:00] hey hey, hello everyone! [17:00] ello there [17:01] let's wait for a couple of minutes for people to come in and then let's start rolling [17:01] Hello dpm [17:01] hey AJenbo, how's it going? [17:01] hey TLE :) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Global Jam Bootcamp - Current Session: How to run a translations jam - Instructors: dpm [17:01] Hallo [17:01] hi MeanEYE [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/28/%23ubuntu-classroom.html following the conclusion of the session. [17:04] right, it seems that the session is moderated, so while we are sorting this out, feel free to chat on #ubuntu-classroom-chat [17:04] ok, let's get started! [17:05] so, good morning/afternoon/evening everyone! [17:06] today we're going to talk about running a translations jam during the Ubuntu Global Jam event [17:07] the aim is for it to be useful for both new and experienced translation teams [17:07] so it'd be cool if you could share your experiences on running jams too [17:08] as I say, in the meantime we can talk on #ubuntu-classroom-chat, and I can forward the conversation in the main channel [17:08] First of all, are there any translations people around? [17:09] Anyone who's run a translations jam before? [17:10] so we've got AJenbo from the Ubuntu Danish translation team [17:11] and TLE also from the Danish team [17:11] who've run a few small events [17:11] ok, let's start with the dates [17:12] You've probably heard that we are running the Ubuntu Global Jam (UGJ) very soon :) [17:12] * WHAT: Ubuntu Global Jam [17:13] * WHEN: weekend of the 1st-3rd Apr [17:13] * WHERE: all over the world! [17:13] You'll find all the info you need (and more!) on: [17:13] https://wiki.ubuntu.com/UbuntuGlobalJam [17:13] There you'll find links for every type of jam we are proposing (translations, packaging, documentation, upgrade, testing, etc.) [17:14] Remember that the idea is not that each LoCo runs all types of jams. [17:14] The idea is that there are several options each team can consider, and then decide the type or types of jams that you'd like to run when you are getting together [17:15] and of course, the other main idea is that you get to see your Ubuntu friends once more and have some fun :-) [17:15] In the case of translations jams, you'll also find more info here: [17:16] https://wiki.ubuntu.com/Jams/Translations [17:16] The important thing here is also to add your details on the UGJ event on the LoCo Directory here: [17:16] http://loco.ubuntu.com/events/global/567/detail/ [17:17] it's very encouraging for all teams to see that they are participating in a truly global event [17:17] improving Ubuntu and having a good time [17:18] we've got 35 registered events all over the world already, which is quite impressive [17:18] Also importantly, registering your event on the LoCo directory will give visibility to your team and more people might be interested in coming along to the local events. [17:19] ok, so before we get into the details, any questions so far about what the global jam or anything related? [17:20] dpm: Is there a way to make those events a bit more easy to find. I know a lot of people who use Ubuntu but have no clue UGJ or UDS exist. Some advertisement would be nice or perhaps advertising closest events based on geo-ip data to the user who visits Ubuntu.com [17:21] we do advertise those events on the Ubuntu Planet, on http://loco.ubuntu.com/ and all the usual Ubuntu channels, and we rely on the community to spread the word as much as possible [17:23] geo ip seems like a good idea, so my suggestion would be that if you've got a clear idea on a specification or on an implementation for ubuntu.com [17:23] you'd file a bug on https://bugs.launchpad.net/ubuntu-website/ [17:23] which will get to the attention of the website developers and you'll be able to contribute too [17:24] Translations jams allow you making your favourite OS accessible for thousands of people in your language [17:25] I always have to think that when I'm doing translations [17:25] for some people it even means it's the only OS available in their language [17:27] ok, it seems we've sorted out the moderation on the channel [17:27] so feel free to comment on the main channel if you want from now on [17:27] Anyway, for those new to translations: [17:27] Translations in Ubuntu are done by the awesome people in Ubuntu Translation teams, which you can see here: [17:28] https://translations.launchpad.net/+groups/ubuntu-translators [17:28] They are the ones responsible for submitting and reviewing translations in each language [17:29] But do not worry: everyone can submit translation suggestions without having to be in one of the translation teams, so that you can contribute easily since day 1. The members of the translation team will act as reviewers to see that your suggestion is ok, doesn't contain any typos, etc. [17:29] So it's important to get in touch with them once you've done a bunch of suggestions, so that they are aware of them, and they can give you some feedback. [17:29] This feedback will greatly help you on your way to becoming an Ubuntu translator, if you are not one already :) [17:30] Before or after the Jam is a good time to get involved in those teams, and perhaps apply to join them. [17:30] It is always a good thing to make sure there is at least a member of the Launchpad translation team at the Jam, be it physically or remotely, so that he or she can accept translation suggestions on the spot, or provide some feedback on improvement. [17:31] The other useful thing in translation jams is to set goals: [17:32] For example, before the jam you could decide you want: [17:32] * To have ubuntu-docs or kubuntu-docs fully translated after the jam [17:32] * To have the Ubuntu Slideshow in the installer fully translated after the jam [17:32] * To have all the applications in the first page of http://translations.launchpad.net/ubuntu translated [17:32] * To translate the package descriptions of the Featured category in Software Center [17:33] * etc. [17:33] Basically, it's up to you and your team which goals you want to set [17:34] Remember to widely announce your jam in your region or local area [17:34] In the danish team we hacked ul10n-stats to produce a list of what packages needs to be translated for get to 100% translated UI [17:35] AJenbo_, that's really cool, let's talk about this in a while, I've been hacking on ul10n-stats recently with the same purpose :) [17:36] have a look at the latest revisions from trunk, I think you'll like it :) [17:36] AJenbo_, anyway, you were telling me the Danish team was thinking of ways of better promoting events, could you share it with the rest of the audience? [17:37] We are going to run an ad campain og google using some of the free cupons they keep sending us. [17:38] We adwords you have the ability to specefy a region so you can make the ad specific to the local event [17:38] s/We/With [17:38] wow, so you've been thinking about using it for promoting Ubuntu events? [17:39] yes [17:39] cool :) [17:39] so here's a great suggestion for other teams ^^ [17:40] ok, so going back to doing translations, [17:40] during the jam [17:40] you should definitely check out Nightmonkey if you are setting a goal for translations of package descriptions. [17:40] I talked about it a while ago: http://davidplanella.wordpress.com/2010/02/26/translating-software-descriptions-with-nightmonkey/ [17:41] During the jam you can use several tools to coordinate the goals I was talking about earlier, assign translations, keep track on who's translating and reviewing what, etc [17:42] Gobby (apt://gobby) and the Ubuntu wiki will come to your rescue [17:42] you can, for example, prepare these goals in the wiki before the jam [17:42] and then use gobby for real-time communication. This can be useful in either case: if you are running a jam somewhere where you are physically together, or remotely [17:43] since that's another possibility [17:43] we encourage running jams as a physical meeting [17:43] but that's not always possible [17:43] especially for LoCos that encompass really distant areas [17:44] in that case, running an IRC jam can also be fun [17:44] One important note on the goals, though: [17:44] It's fantastic to achieve them, but sometimes in jams you get a lot of new people coming along, and you spend quite a lot of time telling them about Ubuntu, about how the translations process goes, etc. [17:46] So you just have to remember that this training part is also very important. It is very rewarding to get new contributors to your translation team and help better localizing Ubuntu in your language [17:46] And it is fun as well ;) [17:46] Regarding new contributors, [17:46] another tip is to prepare some short presentation on how the translation process works, so that you don't have to explain it every time all over again [17:47] You can run the presentation at the beginning of the jam or put it somewhere and point people to it when they've got questions [17:47] As you'll see that people come at any time during the day [17:47] (don't expect everyone to come by first thing in the morning ;) [17:47] And might not have seen your presentation if you are running it e.g. in the morning [17:48] Another thing you can do during translation Jams is to get together to prepare translation guidelines for your team [17:48] As you all or part of the team will be together in one place, it is a great opportunity to put the guidelines in writing [17:48] and make the translation process a lot easier [17:48] You'll find more info on translation guidelines on: [17:48] https://wiki.ubuntu.com/Translations/KnowledgeBase/TranslationGuidelines [17:49] And again, remember you'll find more info on how to run translations and other types of jams on: [17:49] https://wiki.ubuntu.com/Jams/Translations [17:50] Anyway, I think that's mostly what I wanted to cover for today [17:50] Does anyone have any questions? [17:50] Or would like to share past experiences with jams? [17:51] There are 10 minutes remaining in the current session. [17:53] in any case you'll find that and more info on https://wiki.ubuntu.com/UbuntuGlobalJam [17:53] When new people come and try to translate it might be a good idea to have them on a relaxed rule set but with guidence so that they have an easy transition to becomming part of the translation team [17:54] AJenbo_, yeah, definitely, take it easy with beginners, and let them feel welcome! [17:54] They might not be ready to commit there privat email to a busy mail list either. [17:56] yeah, that's also a good point too, and that's also why a meeting in person, getting to know people from the mailing list can be really useful and less scary to newcomers [17:56] There are 5 minutes remaining in the current session. [17:56] Is there a simple tutorial for people new to whole translation deal? If not that might be a good idea. Most of us are not familiar with applications and rules when it comes to translation. [17:57] MeanEYE, definitely. We've got https://wiki.ubuntu.com/Translations/QuickStartGuide, which is always a good resource to point new translations contributors to [17:58] and local teams have got their own resources and guides too [17:59] ok, so I think that was all for me today. All I need to say is thanks a lot for your participation and see you at the Global Jam! [17:59] Thanks. [17:59] I'll now leave you in the able hands of the man with the unpronounceable nickname "The do's and dont's of bug triaging", with hggdh. [18:00] heh [18:00] see you all! [18:00] heh [18:00] Cheers! [18:00] Hello. My name is Carlos de-Avillez. I am one of the administrators for the BugSquad and BugControl teams on Ubuntu. I have been around bugs for pretty much all my professional life -- causing them, or finding them, or fixing them (or all three in sequence ;-). [18:00] I started with Ubuntu in 2006, when I was trying to (yet again) find a Linux distribution that I felt more confortable with, and that did not need me to spend a lot of time tweaking the kernel, etc. And guess what... Ubuntu won! :-). I then joined the community, and started being active beginning of 2007. [18:01] Now, as usual, questions should be asked on the #ubuntu-classroom-chat channel. If you want to ask a question, write it there, and precede it with 'QUESTION:'. For example: [18:01] QUESTION: What does 'hggdh' mean? [18:01] heh [18:01] Let's get into the class now. [18:01] Something in Hebrew I think ;) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Global Jam Bootcamp - Current Session: The do's and dont's of bug triaging - Instructors: hggdh [18:01] indeed [18:01] First, who we are (https://wiki.ubuntu.com/BugSquad) [18:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/28/%23ubuntu-classroom.html following the conclusion of the session. [18:02] The BugSquad is the team responsible for *triaging* bugs opened against Ubuntu and its packages. The term 'triage' is pretty much taken from medicine -- determining the priority of treatments based on the severity of a condition (see http://en.wikipedia.org/wiki/Triage). [18:02] Different from medical triage, though, we do not expect human death as a consequence of delayed treatment. [18:02] which is, BTW, good! [18:03] But we still need to triage: there are many more bugs than triagers; we have to be able to prioritise the bugs; we _should_ be able to address _all_ bugs eventually. [18:03] For us, then, triage is the process of analysing a bug, collecting enough data to completely describe it, and marking the bug 'Triaged', and give it an importance. [18:04] Triage ends there -- it is not our responsibility to *solve* the bug: once the issue is identified, and all necessary and sufficient documentation has been added to the bug, triaging *ENDS*, and the bug goes on to a developer/maintainer to be worked on. [18:04] Again: triaging *ends* when a bug status is set to Triaged (see https://wiki.ubuntu.com/Bugs/Status). [18:04] This does not mean we do not solve bugs ourselves. Most of us wear a lot of hats, on (possibly) more than one project. But _triaging_ ends when the bug is set to Triaged. [18:05] It is no longer a BugSquad interest. [18:05] Now, another important point is being able to differentiate between bugs (errors in a programme/package) and support issues (how to use a programme/package, how to set up something). We only deal with *bugs*. [18:06] Support requests should be redirected to one of the appropriate fora: http://askubuntu.com/, https://answers.launchpad.net/, http://ubuntuforums.org/, an appropriate IRC channel, etc. [18:06] With that in mind... [18:07] DO: follow the advices and recommendations from https://wiki.ubuntu.com/BugSquad/KnowledgeBase: they can be used not only for finding more about your own issues, but *ALSO* for triaging somebody else's bugs. [18:08] if you do not agree with something there, please bring it up on #ubuntu-bugs, or the bugSquad mailing list. We will be happy to correct any issue (er, actually, we will probably tell you we agree, and ask *you* to update it) [18:08] DO: read https://wiki.ubuntu.com/BugSquad/KnowledgeBase. Really. No kidding. [18:09] DO: read the Code of Conduct (http://www.ubuntu.com/community/conduct). A nice exposition of the CoC is also at https://wiki.ubuntu.com/CodeOfConductGuidelines. [18:09] (if you wish to be a member of the BugSquad (and, eventually, of Bug Control), we require that you sign it.) [18:10] This -- the CoC -- is perhaps the major difference between Ubuntu and other projects: we try very hard to live by it. *NOT* signing it does not free one from been required to be civil. So... [18:10] DO: be nice. Say 'please', and 'thank you'. It does help, a lot. Follow the Golden Rule (http://en.wikipedia.org/wiki/The_Golden_Rule), *always*. [18:11] DO: keep in mind that English is the official language on https://bugs.launchpad.net, but _many_ UBuntu bug reporters are *not* native speakers of English. This means that many times we will get bugs that are badly written in English (or not in English at all). [18:12] or, a few times, in something that sort of seems like English, but certainly it is just a passing resemblance... [18:12] so: [18:12] DO: Try to understand. Ask for someone else to translate it if you do not speak (er, read) the language (hint: the #ubuntu-translators and #ubuntu-bug channels will probably have someone able to translate). Be nice -- always. "I cannot understand you" is, most of the times, *not* nice ;-) [18:13] DO: ask for help on how to deal with a bug if you are unsure. Nobody knows it all, and we all started ignorant on bug triaging (and, pretty much, on everything else ;-). We have a mailing list (Ubuntu-bugsquad@lists.ubuntu.com), and we are always at the #ubuntu-bugs channel on freenode. [18:14] We will be more than happy to help out on procedures and requirements. [18:14] Please note that we do not _triage_ bugs on #ubuntu-bugs, or the ML -- we will answer and help on procedures and requirements. We will, though, point out deficiencies and missing data, and suggest actions. [18:16] DO: _understand_ the problem. A lot of times we see a bug where a _consequence_ is described, but not the _cause_. The triager should do her/his best to understand which is which, and act accordingly. This may mean changing the bug's package, or rewriting the description, etc. [18:17] The point here is: if we do not understand what is the problem, then how can we correct it? [18:17] There are many ways to do that (er, _understand_, not solve); most will require learning ;-) [18:18] yeah, study. More. [18:19] But look at it in a different way: I am only good on what I do because I *keep* on learning. [18:20] most processes & procedures for understanding a problem also have never been really ported/adapted to computing (differential diagnosis -- medicine --, fault trees -- nuclear reactors, rockets --, etc). So... right now, the best way is to learn more. To keep on learning. With time you will be able to _intuitively_ see a consequence. [18:21] (I would personally love to see differential diagnosis ported to computing, I think there is really something there) [18:21] jsjgruber asked: So should bug reports reflect symptoms or causes? [18:22] jsjgruber: bug reports should have both, as much as possible: you see a bug due to a consequence (incorrect output, unexpected termination, etc) [18:23] but we should try to discern between cause and consequence (so an ideal bug report will have both: "given that input, this error happens") [18:23] a bug report with only consequence is not (yet) fixable -- we will still have to find out *what* *causes* the issue [18:24] Also, it is important to keep in mind that *correlation is not causation* (see http://en.wikipedia.org/wiki/Correlation_does_not_imply_causation). [18:25] not necessarily what seems to be connected is indeed connected [18:25] (I think this was once called the first law of correct startistic) [18:25] statistics [18:25] DO: Try to ask and find answers for some questions: WHAT did happen? WHY did it happen? WHICH COMPONENTS are involved? HOW did it happen? HOW can it be REPEATED? What has CHANGED (if it worked before)? [18:25] mdevenish asked: Do you need to be assigned a mentor to join the bug squad? [18:26] mdevenish: no, not at all. [18:26] mdevenish: we do strongly suggest that you frequent #ubuntu-bugs [18:27] most of the questions asked to mentors are routinely answered there [18:27] DO: add a comment on every action you take on the bug (changing status, importance, package, etc). Although for you it may be crystal-clear the reasons for taking an action, this may not be true for others (in fact, a lot of times it is not clear, at all...). [18:28] the above is much more important than it seems: we, working on a bug, know exactly *why* we took an action [18:28] jsjgruber asked: If two different symptoms have the same cause should one be marked as a duplicate of the other? [18:28] but... usually, nobody else knows why... [18:29] jsjgruber: hum. Careful there -- but yes, one single cause may produce different symptoms [18:30] so we should go to what I stated above on understanding what happened [18:30] DO NOT: add comments like "me too", "I also have it", "also a problem here", etc. These comments just pollute the bug, making it more difficult to find out what happened, where we are, and what is the next step. [18:31] (I hate to page thru a 200-comment bug, trying to find out something that really helps the work on the bug) [18:32] instead, mark it as "also affects me". Much cleaner. [18:32] (and subscribe to it, if you wish to know when the issue is resolved) [18:32] DO: if you are starting on triage, browse the open bugs (there are about 80,000 of them) and look for one you feel _confortable_ with (or less unconfortable ;-). Ideally, you should be able to reproduce it. It does help if you start with bugs on packages you yourself use. [18:32] I will repeat the last sentence in a slightly different way: [18:33] DO NOT work on bugs involving packages YOU do not use/undertand. === vRBa is now known as vRBa-ZR [18:34] chadadavis asked: There needs to be some kind of 'me too' (just one) to mark the bug as confirmed, no? [18:34] If you do not know how to use a package, how will you be able to say this is, or is not, a bug? [18:35] chadadavis: yes. If you can confirm the issue of an existing bug, you can mark it Confirmed. But... in this case I would like a bit more than a "mee too", I would like to to know HOW it was reproduced, WHAT VERSIONS, and WHAT HAPPENED [18:36] in other words: changing a bug status should *ALWAYS* be done together with an explanation of the reasoning [18:36] And do get on to #ubuntu-bugs, and ask for help there when in doubt. We do not bite... really ;-) [18:36] Oh, since we are here: [18:36] DO NOT: change a Triaged bug to New/Incomplete/Confirmed -- a triaged bug is OUT OF SCOPE for triaging. It is not our problem anymore (while wearing the triager's hat). [18:37] as a developer/maintainer, I *can* move a bug from Triaged to New/Incomplete/Confirmed -- or even close it INVALID/WONTFIX, etc [18:37] but, as a triager, IT IS OUT OF SCOPE [18:38] DO NOT: assign yourself (or any other person) to a bug. Bug assignment is a clear, official, signal that "the assignee is actively working on resolving this issue". Nobody else -- including the developers/maintainers -- will touch this bug anymore. Instead... [18:38] DO: so... if you are triaging, and have asked a question/requested action from the OP (Original Poster), *subscribe* to the bug. Nothing is worse than a fire-and-forget action. [18:39] DO NOT: confirm your own bugs. *EVER*. The fact that you see/experience a bug does not necessarily _make_ it a real bug. It may be something on your setup... [18:39] DO: follow suggested actions. For some packages we have more detailed 'howtos'. These are described under the https://wiki.ubuntu.com/DebuggingProcedures page. It is always a good idea to check them (and update/correct as needed). [18:40] these suggested actions are the result of years of painful learning. Most of the time they ARE correct (but, perhaps, dated?) [18:41] Now, a lot of the packages we offer on Ubuntu come from different projects -- Debian, Gnome, GNU, etc. We call these projects -- where real development usually takes place -- "upstream". By the same reasoning, we say we are "downstream" from them. [18:41] (it also happens that Ubuntu is 'upstream' in some packages) [18:41] The ideal scenario is we have our packages identical to what upstream provide, no local patchs (except, probably, for packaging details). [18:42] Having local changes increases the delta (the difference between what we provide and what upstream provides), and makes updates/upgrades more costly. So our patches, ideally, should be provided to the upstream project, and discussed there (and hopefully accepted). [18:43] Bugs affecting upstream projects have to be communicated upstream. This usually means doing a similar triage as we do here for a specific upstream (looking for an identical bug on the upstream project, and opening one if none is found). So. [18:43] DO: Look upstream, and open a new bug if needed; then *link* this upstream bug to ours (and ours to theirs). [18:43] BUT... [18:44] Many upstreams have different rules on how to open/work with/close a bug. Ergo, [18:44] DO: follow upstream's processes when working upstream (in an old saying, "when you enter a city, abide by its laws and customs"). [18:44] Finally... (and this is not a DO/DO NOT): [18:45] Thank you. I am glad you were here, and I hope you help us out. And we are always (er, at least there is always someone logged it, we also have a life) available to help and discuss triaging work. [18:45] uff. my fingers hurt ;-) [18:45] questions, folks? [18:46] then closing remarks: [18:47] pretty much all of us on triage work started as volunteers; most of us are still volunteers: we *like* Ubuntu [18:47] I personally like the CoC, I think this is perhaps the most remarkable thing on the Ubuntu project [18:48] and this is it. Thank you [18:48] Thank you hggdh [18:49] my pleasure, Nigel [18:50] Alright, next up is YoBoY from the French loco, we have 10 mins to go and we [18:50] and we'll wait [18:51] There are 10 minutes remaining in the current session. === drkenobi_work is now known as drkenobi-w [18:56] There are 5 minutes remaining in the current session. === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Global Jam Bootcamp - Current Session: How the French team rocks their global jam - Instructors: YoBoy [19:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/28/%23ubuntu-classroom.html following the conclusion of the session. [19:02] Hi, I'm YoBoY, one of the actual French loco Team contact, and one of the administrators of the french documentation. I'm also planning the next global jam in Paris [19:03] I'm here to explain how we make our global jam event rocks. [19:03] Our last Jam in Paris, we had more than 50 people who come to learn how to contribute. We made workshops to learn how to test, report bugs, triage bugs and write documentation. [19:04] In Paris, we have lot of users who want to help, but they don't know how to and where to start. [19:04] Most of them don't have programing skills. [19:05] Our Jams are more learning sessions. [19:05] We try to give everyone the basis to start contributing on their own, and find what they can do to the Ubuntu project. [19:05] Let me explain how we proceed to make a Jam. [19:06] I - find a good venue. [19:06] we need lot of space, with network [19:07] It's not easy to have that type of venue in Paris on the week end, and we need to make the reservation more than one month before the event [19:08] II - find people who can help make the workshops. [19:08] We try to cover lot of aspects of contribution. [19:09] To do that, we need members knowing how things works, how to use Launchpad, report bugs, translate, etc... [19:09] If you can do it alone, it's fine. [19:09] But if you plan to do more than one workshop, you need help. [19:10] To find this rare persons, start asking on classic channels (IRC, forum, mailing lists). [19:11] Don't be afraid to ask everywhere, not only on your local channels. Some Ubuntu members are not always registered on the loco teams, but they can help if you ask them. [19:13] This first two points are the most difficult for us because we always have lot of people who came to our events [19:14] to help around 50 people we need at least 10 members who can help using Launchpad and the other tools [19:16] how about people leaving other nation ? if they like you to help in it [19:16] I'm not sure to understand the question :) [19:17] Everyone is welcome to join, to help or to participate [19:18] The French Team is already composed by lot of people all around the world. we always promote also events in other part of the world if we can. [19:18] Vanillalite asked: Did you guys have prefunding to get started or was getting money to say rent the meeting site part of the process? [19:19] no money, everything is free [19:22] We think here the knowledge should stay free. A part of our visitors are students, asking them to pay something is not good. [19:22] if someone wants to come to France to your Jam, many countries don't have have local Jams, could your LoCo help with accomodation and similar things ? [19:24] Yes, we always try to accomodate people who want to come to help. We already are doing this for our Ubuntu Party (100 benevolents coming from everywhere in France and from outside France ;) ) [19:24] Next point [19:24] III - promote the event. [19:25] If you want to have people to join, you need to promote the event. [19:25] Blog about the global jam, promote it on your local planet, on mailing lists, on your forum. And do it more than once. Give some useful links to prepare for the event, answer every questions. [19:29] For this Jam, the first post announcing the date, the venue, and some good reading was make last month. [19:29] and another one, with the real content (translation, documentation, testing, reporting bugs, ...) last week [19:30] This week we plan to make another post, and use the forum and the mailing lists [19:31] We are proud this year to have a workshop on translation. Lot of people ask for that type of workshop, but it's really not easy to find someone to explain how translation work [19:32] MeanEYE asked: Is French Jam one of popular jams? [19:32] Don't know if the Global Jam is popular, or if it's just because it's an Ubuntu event :) [19:34] Paris is a wonderful city. lot of people love free software, and lot of people like Ubuntu. [19:34] Like I said, our last jam we had more than 50 people, it's a big Jam [19:35] Other countries are doing "smaller" jams, but with more real contributions, real work on the bugs, the translations, or other things [19:35] we can't really compare [19:37] I think our work it's to open the doors, let people see what they can do, how we make Ubuntu, how free softwares work. [19:38] Last point of our Jams [19:38] IV - Have fun ! [19:38] :D [19:38] Don't forget, the best part in a Jam is to meet people. [19:39] We always start in Paris with a lunch for the members who organize the Jam. We need energy, and it's a good moment to talk. [19:39] And at the end of the day, everyone can join us at a pub to share a drink and talk about Ubuntu and free softwares. [19:40] It's for me the best part of the events, taking time to talk with new friends. [19:43] Everyone in the Ubuntu community, is doing his best to invite new people to contribute to Ubuntu. The Global Jams is a great opportunity for that. [19:45] If you can have these 4 points, I'm sure your Jam will rocks too :) [19:45] questions ? [19:46] MeanEYE asked: UGJ is twice a year. Right? === em is now known as emma [19:46] Yes, The Ubuntu Global Jam for each releases [19:47] so it's twice a year [19:48] MeanEYE asked: What's the best way to get in touch with some LoCo or it's members before comming to Jam? [19:48] I think you can start with the LoCo Directory [19:49] loco.ubuntu.com [19:49] You can see information of the loco teams, and their events [19:50] You can also start by posting in the forum of the loco team [19:51] some teams, like mine, are very complicate in their organisation (lot of irc channels, mailing lists, ...). Posting a comment on the blog post of the event is also a good first contact [19:51] There are 10 minutes remaining in the current session. [19:52] MeanEYE asked: Should you contact LoCo member so they know the amount of people to expect? [19:54] yes, you can tell the organiser of the jam you are coming. It's important if you come to help, not just to assist. [19:55] we can have 70 people in our venue, we plan to have around 50, so for us it's not really important [19:56] But for other jams, where the venue is smaller, it's good to tell them you are comming [19:56] There are 5 minutes remaining in the current session. [19:57] by the way, don't forget to take network wire, ... or ask what they need ^^ [20:00] ok, thanks everyone, it's time for me to leave :) [20:00] Have good jams and don't forget to have fun :) [20:00] \o/ [20:00] Thanks YoBoY [20:00] And next up, we have itnet7, Give him a cheer folks [20:01] YAY!!!! [20:01] j/k [20:01] Hey there everyone and welcome to "Global Jam Florida Style" itnet7 here, one of the leaders of the Florida Team, and also on the LoCo Council here to talk abou the Florida Team and our Jams .... === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Global Jam Bootcamp - Current Session: Global Jam Florida style - Instructors: itnet7 === apachelogger is now known as javalogger [20:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/28/%23ubuntu-classroom.html following the conclusion of the session. [20:02] The Florida Team has always partipated in UGJ's. Our first Ubuntu Global Jam was in Orlando. When we first held an UG Jam we tried to have it in one City, thinking that it would be an opportunity for us to meet up with others that we have worked with and collaborated with Online. [20:03] Unfortunately, due to rising fuel costs, and time constraints.... [20:03] We decided to encourage others to host an event nearby if they would like to be involved. We are holding two events, One in Lakeland and the other in Melbourne. [20:04] For those of you that haven't had a chance to participate yet. The Ubuntu Global Jam is a global online and in Real Life event where people come together and use their talents to work the upcoming release of Ubuntu. During this time typically teams will work on: Bug triaging, Documentation revision, Packaging and Translations, etcetera. [20:05] The idea is to borrow some suggestions from https://wiki.ubuntu.com/UbuntuGlobalJam [20:06] but also feel free to come up with your own ideas and ways that you can help to improve the next release! [20:06] For example... in Lakeland...mhall119 and other attendees are going to work on the Summit Scheduler for UDS. They will collaborate to fix bugs and add new enhancements to the Summit Web-Application. http://loco.ubuntu.com/events/team/729/detail/ to see further info about this event. [20:07] any questions so far? [20:07] well that brings me to a good point [20:07] If you, yourself or others around you are involved with Ubuntu but haven't already organized an event, we currently have 35 events on the LoCo Directory [20:08] There are some pretty good descriptions up there, that can give insight on to what is planned and could possibly help you generate a few ideas of your own! [20:09] We have had around 15-20 in attendance at our Jams [20:09] All with different technical levels, and skills [20:09] and everyone collaborates and has a really great time! [20:10] It's important to note that you don't really need to have that many people come in order to host an Ubuntu Global Jam [20:10] Even if it's only one or two at most, that would still be awesome, and you're still contributing :-P [20:10] :-) [20:11] We usually mail our team mailing list about 2 - 4 weeks in advance to let everyone know where we are planning to hold our events [20:12] We're hoping that this encourages them to either drive to one of our events, or host their own! [20:13] In the Melbourne, FL event... I plan to try and take about 5-10 people throught the beginning step of getting their accounts up to speed in Launchpad [20:13] and then showing them the basics of triaging bugs [20:14] I also plan on bringing some thumbdrives with Natty Beta 1 on it in case any one that hasn't wants to take Natty for spin (live). [20:15] Our event in Melbourne is scheduled for 4 hours, which is a pretty decent amount of time. We are planning to go out afterward and have dinner as a group [20:16] Another big thing is to try and get 1 or 2 people (Depending on how many show up) to take some pictures during the event [20:18] This is another way to contribute, by sharing pictures afterward, there is a good chance you will encourage others to also host their own events in the future. It also will encourage them to attend your events in the future. [20:18] Dent, Tweet, Buzz, Facebook, Re-Dent, Re-tweet, Re-buzz, Like [20:19] Do your best to share progress [20:19] and if you're working towards goals, share youre accomplishments [20:20] If someone brand new that has never been to an Ubuntu Global Jam attends, and sumbit's his/her first bug dent it to #ugj [20:22] Or if you're working on a patch and it's accepted during your jam, then brag about that too! [20:23] It keeps everyone in the loop, and allows for us to all share in each other's accomplishments [20:27] Here are some pictures of our previous jams.... [20:27] https://wiki.ubuntu.com/GlobalBugJam/Stories?action=AttachFile&do=get&target=fl_loco_Globaljam_022009_sm.jpg [20:28] http://www.flickr.com/photos/sanguinetangox/3981704091/in/pool-1277863@N23/ [20:31] So, Venues... Here in the US we are able to reserve conference rooms in our Public Libraries. We are required to submit and application, with the date and time we would like to reserve it [20:31] I am sure it's similar around the world [20:32] pleia2 asked: What kind of venues does the FL team use? [20:32] Our libraries have decent enough wifi to install and application or two, but not much more than that [20:32] the plus side, it's free to reserve a room usually [20:33] You just want to verify whether or not you are allowed to bring in drinks and snacks, as we've seen some libraries in Florida that wouldn't let us bring in any food/beverages [20:34] Local Coffee Shops are also a great place, (Starbucks included of course) [20:35] but you can probably take you're time and locate a nice family owned coffee shop that would be glad for you to have your event there! [20:38] You can check with Hotels as well. Especially if you have some friends that work there. You can also ask for a Hotel Manager and let him know you're not selling anything and ask if he would allow you to use one of their small conference rooms [20:42] We also have some restaurants near us that have "Community Rooms" that they let us use. In return each of us orders stuff to eat and drink throughout the time we're there [20:43] It's a good idea to call around and see what places have what if you're unsure [20:45] If you think of a great place, call them and check and make sure they have wifi, and ask if a group of your size needs reservations, and find out of there is any cost to reserve, (some places do try to charge small fees to reserve to guarantee they don't lose out on potential business) [20:47] We have held our events in coffee Shops and Libraries mostly [20:47] and try to schedule a social event afterwards... Like Dinner and/or a Movie [20:50] I was asked: Did you throw beach parties as a part of UGJ? [20:50] So far, not yet! [20:50] It would be a good idea with a little more planning to potentially have a bbq at the beach as the social event [20:50] barbeque [20:51] With tethering and netbooks we could probably work at one of the pavillions! [20:51] Good idea [20:51] There are 10 minutes remaining in the current session. [20:51] We haven't yet, but it has potential :-) [20:52] At the beaches here, they are more like County Parks [20:53] They have huge Pavillions just off of the beach. A lot of them have power outlets and a shady nice breeze! [20:54] If anyone has any specific questions drop me a line at itnet7ubuntucom [20:55] mhall119 wanted to share with everyone that his event started with only he and one other person in mind, and now it has grown to 6 or 7 [20:55] so please be encouraged! [20:56] There are 5 minutes remaining in the current session. [20:56] two people are enough to get started, and your jam can be equally successful with only two!! [20:58] Well I'd like to thank everyone that is taking part in the UGJ bootcamp and thanks to nigelb for putting this together!! [20:59] Or I should say the Classroom Team!! [20:59] Thanks for having us share! === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Global Jam Bootcamp - Current Session: Ubuntu-NC's ideas about global jam - Instructors: akgraner [21:01] Hi all! [21:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/28/%23ubuntu-classroom.html following the conclusion of the session. === yuho is now known as Lancer [21:02] Thanks itnet7 and YoBoY...you all are awesome sessions to follow not sure I can add to what you have said but I'll try..:-) [21:02] My name is Amber Graner and I'm part of the North Carolina LoCo Team [21:03] I've organized on local global jam and one virtual global jam [21:03] before I get started how many people in the channel have attended a global jam? === pak33m is now known as Guest62795 [21:04] (you can answer in #ubuntu-classoom-chat) [21:05] alrighty.. so I have to say Ubuntu Global Jam is one of my favorite Ubuntu events [21:06] and here's why - you are only limited by your imagination as to what the event can be [21:06] there was discussion in the NC loco team in 2009 about what a global jam *had* to be [21:06]