=== juan-arg55669 is now known as juan-arg [02:05] wow this site exists [02:05] i mean... channel (now I look stupid) === dcd is now known as deadcandance [02:40] holas [06:10] exit === vilde_ is now known as MLP [12:29] What is this room for? [12:30] for gaming [12:31] Gaming1: /topic and /join #ubuntu-classroom-chat === popey changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Next session starts at 15:00 UTC on 27 October === leonel_ is now known as leonel === atoponce is now known as encryptz === encryptz is now known as atoponce === blueyed__ is now known as blueyed === uhutu is now known as barcc === magnus_ is now known as CBA === CBA is now known as magnus_ === magnus_ is now known as _magnus_ === barcc is now known as barcc_ === barcc_ is now known as barcc === popey changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Next session starts when the speaker arrives [16:21] here :) [16:21] yeah [16:21] Hello, I will try and talk about Xubuntu [16:22] My name is Radomir Dopieralski and I'm a xubuntu user since Dapper [16:22] TheSheep: you here in place of Cody? [16:22] popey: seems so, at least until Cody shows up, I don't know what happened [16:22] popey: this is a little improvised [16:22] popey: is this ok? [16:23] well it would be nice to get hold of cody of course [16:23] I will step down as soon as he appears [16:24] it's fine by me [16:25] As you might already all know, Xubuntu is an Ubuntu derivative, with GNOME environment replaced with XFCE [16:26] It shares the Ubuntu repositories and most of its core, so the main difference is a different set of default applications and different default settings [16:27] The applications were chosen to make the desktop still as useful and powerful as possible, while limiting the memory footprint and keeping everything fast. [16:27] So, for example, we have Abiword and Gnumerica instead of Openoffice [16:28] GQview instead of gThumb [16:28] the general rule of thumb is that we prefer GTK applications that don't have GNOME dependencies [16:29] although Xubuntu also includes some applications with GNOME dependencies stripped entirely or reduced to minimum [16:30] These applications have a -gtk suffix added in the repositories [16:31] As you can see, Xubuntu is a nice thing to use if you have older hardware [16:31] But it's also very good for people who just don't like to waste memory or cpu power on bells and whistles [16:32] Many xubuntu users use it on computers that could easily run Ubuntu [16:33] QUESTION: is the web browser still Firefox? [16:34] picard_pwns_kirk: yes, we still use Firefox [16:34] QUESTION: I don't know if you can answer this one, but is the plan to do future releases at the same time as the regular Ubuntu? [16:35] keithcleaveruk: so far the releases were synchronized with Ubuntu, with maybe a day of delay, but I'm not sure about the current plans [16:35] QUESTION: Is there a list of Xubuntu-prefered applications available somewhere? [16:36] Lardarse: for the current, up-to-date list, just check the dependencies of the xubuntu-desktop package [16:37] http://packages.ubuntu.com/gutsy/metapackages/xubuntu-desktop [16:37] vinze: not really an answer to my question - we have lots of old hardware here in africa - even 486 pcs [16:38] < mzungu> QUESTION: what would be the minimum hardware specs to [16:38] comfortablr run Xubuntu? [16:38] Lardarse, the default packages are at http://cdimage.ubuntu.com/xubuntu/releases/gutsy/release/xubuntu-7.10-desktop-i386.manifest [16:39] mzungu: a pentium class processor seems to be a must, and at least 64MB of ram to even get this running. Personally I was running a stripped-down xubuntu on P90 and 96MB ram [16:39] mzungu: it wasn't comfortable, but it was possible to get the work done [16:40] QUESTION: Would this be something you could run on a Crusoe processor or even an ARM processor? What's the smallest form of computer on which Xubuntu can run? Are there any embedded Xubuntu machines? [16:40] ok - so a 166 pentium 1 with 64mb is ok? [16:42] Xubuntu is not really a perfectly streamlined, light ditribution for very old hardware -- there are much better distributions for that. Xubuntu tries to strike a balance between user-friendliness and lightness. [16:43] desertc: I don't know about architectures like ARM, my guess is xubuntu may be too heavy for them. [16:44] Xubuntu can be easily further stripped down, the cups and hplip daemons disabled, screen resolution lowered, many services removed [16:44] However, at some point you really need to recompile the kernel [16:45] This xubuntu doesn't do by default [16:45] < desertc> QUESTION: Are there some situations where you've seen Xubuntu where you thought it was especially well suited? [16:45] desertc: my desktop :) [16:45] QUESTION: Xubuntu is just regular Ubuntu with different apps and a different window manager, right? [16:46] desertc: but seriously, we use it in our computer laboratories on the university, over 300 workstations [16:46] desertc: we have mixed hardware, but all the workstations must have the same software -- so xubuntu fits here nicely [16:46] desertc, also, it's very well suited to run from a USB drive due to its lightness [16:47] desertc: xfce has also some buildin kiosk functionalities, so you can use it for setups where the users are not supposed to be playing with settings [16:48] picard_pwns_kirk: mostly yes, we also have different default settings, so there are differences in what services start, etc. [16:48] picard_pwns_kirk: but the core is the same [16:49] picard_pwns_kirk: in particular, it's possible to make Xubuntu from Ubuntu manually, by just isntalling some packages and changin some settings [16:50] About the future plans of Xubuntu [16:50] I don't know the absolutely current status, I've heard Jani is stepping back, but I don't want to spread rumors [16:50] TheSheep, that's correct [16:50] I can tell about the plans from several months ago [16:51] Lionel (mr_pouit) is the new lead dev I believe [16:51] Gutsy includes some more GNOME dependencies than Feisty did [16:51] in particular, on gnome-vfs [16:51] the decission was made because these libraries are not really so heavy in gnome [16:52] and becuase "removing dependencies" on them would mostly consists of copy-pasting code from them [16:52] they are pretty straightforward [16:53] we are looking forward to the gvfs library, I hope some dependencies can be easily resolved when it's out [16:54] I think the worst problem so far is that we don't have a working and maintained cd burning application [16:54] Gutsy includes GNOME's Brasero [16:56] We also don't have such excellent documentation, although most of the howtos and docs work in xubuntu the same as in GNOME [16:56] On the plus side, the help channel is much less busy, so it's much easier to get help tehre [16:56] there [16:57] We are always looking for people willing to help. [16:58] Programmers who know GTK and can 'strip the deps' are of course very needed, but the distrubution always needs more hands to help [16:58] We need people to package applications (especially ones not included in Ubuntu) [16:58] and to maintain them. [16:59] We need people to triage bugs and write documentation [17:00] We are much smaller group than the ubuntu dev team, so there are definitely more opportunities to do something really cool [17:00] plus, the xfce environment is really well designed and sleek, so it's a pleasure to work with it. [17:01] thanks very much TheSheep for stepping in! [17:01] to reasume, I think that Xubuntu is definitely worth a try for everyone. It's different from gnome or kde, but people who like it, like it very much. [17:02] Thank you everyone for you attention [17:02] Thanks TheSheep [17:02] * popey cheers for TheSheep [17:02] /,e seconds popey [17:02] */me [17:02] TheSheep, you deserve a medal for making it through this talk as well as you did. === popey changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Current session: Ubuntu Women - Elizabeth Bevilacqua [17:03] Welcome to the Ubuntu Open Week Session on the Ubuntu Women Project! [17:03] I am Elizabeth Bevilacqua. I currently work as a Debian (and now some Kubuntu!) SysAdmin for a small Linux firm outside of Philadelphia, Pennsylvania in the United States. [17:03] Aside from Ubuntu Women work, I'm currently heavily involved with the LoCo Teams projects, specifically with my own state of Pennsylvania and the greater work of the US Teams Mentoring program. On the technical side I contribute upstream as a Debian Package Maintainer. [17:04] In this session I'm going to start out by discussioning some of the frequently asked questions about the Ubuntu Women project and then will open the floor for your questions. [17:04] First of all, the official website for the Ubuntu Women project is http://ubuntu-women.org. From there you can get to all our other resources, including our Mailing list, Forums, Launchpad and Wiki. [17:04] I became involved in the Ubuntu Women project as soon as I found out about it in early 2006. Vidya Ayer is the founder of the project, spurred on by some unfortunate experiences within the LoCo team she was involved with. [17:05] Vidya modeled the project closely after the Debian Women (http://women.debian.org) project, which many have said was quite a sucessful project, with the Debian Project now boasting several female Developers, not the mention the work of Debian Women in writing guides, developing mentoring partnerships and changing how women are treated within the project. [17:05] Unlike the Debian Women project, however, the Ubuntu project does not only seek out women to contribute via development. Instead our focus is on the broader Ubuntu project, seeking to get women involved everywhere and to eventually become members and key contributors to the project. [17:06] The first question I tend to get when discussing the project is "Why?" To answer this simply, there aren't a lot of women using and involved with Linux projects, and we feel strongly that more would be valuable to the project. [17:06] As such, our project seeks to give an entry point for women looking to join the Ubuntu project. [17:07] We provide this entry point by showing women that other women are already here (it can be intimidating to be the only woman in the room, or feel like it!), provide resources to help women get involved, and to link up women directly with the project contacts and mentors they need to successfully enter the project. [17:08] The project is simply used as a springboard to get women out there in the main project, and provides a support infrastructure if problems are encountered with their involvement. So we're not trying to be a separate entity in the project, in fact... [17:08] Just recently the project began to form a partnership with the Classroom project (https://wiki.ubuntu.com/Classroom) which will enable us to leave behind our separate Courses program and encourage women to contribute and lead classes and promote the classes through our various outlets. [17:09] At this point you may be asking why there aren't projects for other IT minorities. There are! The Ubuntu for All project (https://wiki.ubuntu.com/UbuntuForAll) is the umbrella group under which other groups interested in equality and opportunity for minorities exist. [17:09] If you feel there is a need to address a currently unaddressed minority group, please feel free to stand up and take a leadership position in making this happen. [17:10] In addition to lowering the barriers of entry for women in the project, our list provides a forum to discuss issues facing women with Ubuntu and the wider Free and Open Source Software world. [17:10] Sometimes heated, these discussions bring out the opinions of a variety of men and women with various backgrounds and help us address the appropriate issues with as much feedback as possible. [17:12] Another question folks often have is how they can help out with the project, or with having women feel more comfortable and accepted within F/OSS itself. Our wiki page on ChallengingSexism is a nice place to start: http://wiki.ubuntu-women.org/ChallengingSexism [17:12] A couple of the best articles are: [17:12] HowTo Encourage Women in Linux: http://www.faqs.org/docs/Linux-HOWTO/Encourage-Women-Linux-HOWTO.html which might be of particular interest to LoCo teams since there are a lot of real life examples [17:13] Dorothea Salo: What Some Folks Can Do, If They Choose: http://cavlec.yarinareth.net/archives/2007/03/30/what-some-folks-can-do-if-they-choose/ which discusses how men can stand up when they see sexist or other inappropriate behavior that drives people away (not just women!) [17:13] I'm looking forward to a day when this project is not required, and with your help we can accomplish this! [17:13] Now I want to go ahead and open the floor for questions. [17:14] QUESTION: what do you feel is the main factor behind the gender discrepancy in IT today? [17:15] Sodki: It's hard to pinpoint a main factor, but in many countries there is a history of steering women toward "softer" skills, I know first hand in the US that some women are actually /discouraged/ from following technical careers [17:15] popey> QUESTION: How do you feel about the assertion that ubuntu women may well represent the views and opinion of geek women but not that of the average non-geek woman. This pre-supposes that there is a difference between those two categories (which I personally believe there is)? [17:16] popey: we try to offer a balanced view within Ubuntu Women, but we really need folks to speak up so they will be heard [17:16] I've actually gotten feedback telling me the opposite [17:16] may iclarify? [17:16] please do [17:17] as a man it is difficult to make comments about ubuntu women (IMO) [17:17] we are often seen as cleary unable to see the point from a womans side [17:18] gotcha [17:18] however I know of men who show women (in their life) who are non geeks - the stuff that ubuntu women, debian women (and other groups and individuals) put forward [17:18] and generally the non-geek women (that I have spoken to) would say that those opinions dont match theirs [17:18] and that they dont feel represented [17:18] is that fair? [17:19] well I want to encourage anyone who has an opinion about the direction of the project to speak up and let us know [17:19] It is [17:19] In India, we are not discouraged, at least i was not, to take up technical fields [17:19] i think it'd be very hard to have a set of views that *all* women think. [17:19] the direction we're going in is based on the feedback we received from each other, and if the non-geek women won't speak up, we don't know how they feel :( [17:20] no, I'm not saying you need to represent all women [17:20] unless it's an incredibly broad, sweeping statement. [17:20] but that there is a distinct polarity between geek and non-geek women [17:20] but the group is called "ubuntu women" not "ubuntu geek women" [17:21] the trouble is that currently the husbands and boyfriends of "non-geek women" are the only ones speaking up [17:21] it's difficult to have a discussion through a proxy [17:21] i don't find there to be a difference when i poll my non-geek wife's opinions for reference in these matters [17:21] agree with popey, is your aim to have more women using ubuntu, or more women contributing to the ubuntu project? [17:21] the latter [17:22] of course, so I want to invite women of all perspectives to speak up and let us know what they want from the project [17:22] as a geek woman, I really can't speak for them [17:22] The two are quite different fields [17:23] AidyFS, the latter is the main goal [17:23] Cillian> QUESTION: Is it not possible that by creating a project for only women you might be aiding the separation of them from the bulk of the community? [17:24] Cillian: That's something we get often. I don't believe this is the case since we don't really have any technical projects within the Ubuntu Women project. Our work is to draw women into Ubuntu, make them feel welcome and give them the tools they need [17:24] from there they go out into the wider community and contribute [17:24] Cillian, its not restricted to women, rather men have been a part of UW since its inception 2 years ago. [17:24] * svaksha is Vidya Ayer, sorry should have introduced myself [17:24] QUESTION: So how is the project going? Is the mentoring progressing as you expected? Are you finding that people are interested in participating? What have some of the highlights for you been? [17:25] our first server admin was a man [17:25] So ubuntu-women is more of a woman friendly zone than a woman only zone? [17:25] and even today we have a man as the list admin [17:25] Cillian: yes [17:25] yep [17:25] desertc: it's chugging along, currently our big project is working with the Ubuntu Classroom project [17:26] we used to have a Courses program, but it became increasingly obvious to us that it was a wasted effort and wasn't successful - we want to make contributions to the main project and take advantage of the courses/classes in the main proejct [17:26] desertc, getting mentors to hold regular courses has been a tough task, but we are not giving up :) [17:26] and people are very much still interested in participating! [17:27] yes, they are [17:28] I am not going to claim that some of the bigger women within the Ubuntu project are in their positions because of our work [17:28] but I have started bumping into more women since the project lauched, and some have said that it was helpful to see the UW project existing [17:28] pleia2: you'll need to repeat, i think [17:29] oh, no, that looks right [17:29] yeah I think I'm good [17:29] QUESTION: is it just non-geek women that feel excluded? what about non-geek men? [17:30] cjb_ie: I haven't really heard much from non-geek men TBH [17:31] Q: Have there been some landmark moments for you? [17:32] more [17:32] desertc> QUESTION: Have there been some landmark events for you, in the project, where you felt the effort was especially effective? [17:33] desertc: I think seeing the increase in women we've worked with become Members is really exciting [17:33] Ubuntu Members that is [17:33] in my LoCo team there are 3 Ubuntu Members, 2 of us are women :) [17:33] it's encouraging to me and the rest of the team [17:35] QUESTION: What kind of relationship would you like to see between LoCo teams and Ubuntu Women? [17:35] Vorian: Good question! I'd really like to see a closer relationship [17:36] there has been discussion in the past of Ubuntu Women having localized chapters, but LoCo teams are really where we need to be getting involved in keeping with the aims of the project [17:36] unfortunately much of the trouble encountered by women in Ubuntu is via the LoCo teams [17:37] I'm wondering if it would be useful for us to write up some sort of document to help out LoCo teams, to get them to attract more women, something modeled after the HowTo Encourage Women in Linux that focuses on LUGS [17:37] * svaksha nods [17:38] any more questions? [17:39] ok, we're going to unmod the channel for some open discussion [17:40] Q:moving forward what can we all do to attract women (geeky and non) to the community? [17:41] good question [17:41] first it helps to be mindful of the existance of women in the project so there is a welcome space to invite them to [17:41] I know in my loco team it's very open to women participating, and that's very exciting [17:42] from there just attract them like any other person to Ubuntu, find out from women you know what their interests are and tailor your presentation of Ubuntu to fit that [17:43] the channel is open for discussion for the remainder of the scheduled time. [17:44] Any ideas of particular things an individual can do to help? [17:44] ty for the answer [17:44] Cillian: http://cavlec.yarinareth.net/archives/2007/03/30/what-some-folks-can-do-if-they-choose/ <-- this link is great for that [17:44] Thanks [17:44] mostly what we need are people speaking up when the see something that is inappropriate [17:45] this isn't just about attracting women, Linux has a reputation for being a boys club with locker room humor, it drives off a lot of folks [17:45] As I mentioned in -chat, I was impressed with mailing list posts such as this one from a female Chinese developer who chose to help Ubuntu because of her interaction with your chatroom: [17:45] https://lists.ubuntu.com/archives/ubuntu-women/2007-October/001183.html [17:45] desertc: thanks! in situations like hers we work to pinpoint her skills, what she wants to do, and try to link her up with the proper resources [17:46] I think there is a good deal to be said for "birds of a feather" groups, to encourage people to participate because they feel comfortable with the people around them. [17:46] desertc: there are a lot of detractors, but the women groups really have helped me, I'm pretty sure I wouldn't be as involved with Ubuntu without it [17:47] I've noticed a lot of people seem to regard IRC as a large part of the community, but I'd like to note it's not just rough for women - I think you need to be generally thick skinned when on IRC, it's often a tough crowd to get on with [17:47] honestly the reminders about appropriateness help me, as i tend to fall back into locker-room made rather easily - despite best intentions - sad to say [17:48] desertc, support and guidance (minus sarcasm and locker room humor) in the technical aspects goes a long way in the learning process [17:48] Cillian: I agree, I'd really like to see this change, the ops do a great job but IRC as a medium has a tendancy to just be abrasive and things can get out of hand quickly [17:49] pleia2: I recall a comic strip - Completely normal person + anomymity + audience = complete jerk [17:49] I have been considering lately all the different ways people can get involved with the Free Software / Ubuntu communities. Most of the ways is not specific to programming. It's great to have an organization spreading that message to people who might not otherwise be interested. [17:49] desertc: I would argue the community has proportionally too many programmers compared to translaters, UI people, graphic designers, etc. [17:50] Cillian: if anomymity was our only problem I'd be happy, there have been incidents where very well known folks in the project have made inappropriate remarks, it's a culture that we'd like to see changed to attract a variety of folks [17:50] This is everyone's perception of "Linux participation", that you have to be a kernel hacker. It's a misperception. [17:50] Cillian, UW does not discriminate along those lines, a designer is as important as a programmer [17:50] Cillian: I can't imagine stepping into a project as a 'ui human' [17:51] Cillian: I mean, programmers are usually welcome, because they fix things, ui people seem to only add broken things [17:52] desertc: not being specific about involvement has been important to our project, many will scream about stereotypes *ducks* but more women ARE involved in softer skills than the technical stuff for whatever reason, and Ubuntu makes those contributions feel valued [17:52] one of the reasons I love this project so much :) [17:52] without usabilty, software is not really useful imo [17:52] * pleia2 nods [17:52] TheSheep: Of course programmers are essential, but what systems like Windows have above linux is not the quality of code, but (in some places) user interface design, artwork and general polish [17:53] Cillian: yes, what I mean, it's hard a usability man to join a project, you are kind of an enemy [17:53] If there are any usability people looking for a friendly project, I could use one :) [17:54] Cillian, also Windows had a head-start, Linux was always perceived as geeky [17:54] svaksha: Which is was, due largely to the mass of programmers making things and nobody making it look nice and be easy [17:54] Cillian, Gnome has a usability project [17:54] pleia2: The Classroom Project was part of your focus, too? This is a great resource. I would have almost liked a classroom topic this week on using the #ubuntu-classroom. [17:55] Heh [17:55] desertc: yes, the Classroom project has been quiet of late, but we're looking to revitalize it, I think it's a very important project [17:55] Question: do you think that encouraging women (particlarly those who aren't involved with development) to spread the word to other people would help get more women icontributing to the project? [17:55] In ubuntu Evan D works on usability issues, i think [17:55] Lardarse: absolutely [17:55] Is there much going on in here outside of the open weeks? I've never bothered to pop in apart from them [17:56] Lardarse: I am taking some of the credit for the bump in women members in my LoCo team - if women are already there in a project or in an event, more are apt to come [17:56] this goes for our local LUG as well [17:56] it's very hard to be the first/only one [17:57] * svaksha agrees :) [17:57] WRT Classroom - MOTU holds Q&A sessions here, but not much activity aside from that [17:57] we're planningsome though :) [17:58] Question: (maybe this was already asked and I missed it..damn facebook!) But what in you experience has been the most successful way of encouraging women to get involved in the open source community? [17:58] Gareth: one on one support [17:59] find their specific needs and talents and mentor them [17:59] and now we must wrap this up :) [17:59] What about exposing them to open source software in general? [17:59] that's great too! [17:59] Gareth: Show off your compiz bling to them :) [17:59] show them what it has to offer, might spark an interest in involvement :) [17:59] * Vorian applauds pleia2 [17:59] thanks! [17:59] show everyone your compiz bling! [17:59] thanks pleia2 [17:59] * Cillian cheers [18:00] well done [18:00] * svaksha cheers for pleia2 [18:00] thanks everyone [18:00] * jedijf too [18:00] * AidyFS gives pleia2 a cookie === popey changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Current session: LoCo teams - Aaron Toponce [18:01] ok. welcome everyoen [18:01] for this discission, i will be referring mainly to 3 resource pages: [18:01] https://wiki.ubuntu.com/LoCoTeams [18:01] https://wiki.ubuntu.com/LoCoTeamKnowledgeBase [18:01] https://wiki.ubuntu.com/LoCoFAQ [18:02] i have a lot to cover, so i'll be getting to the questions in groups, rather than as they come [18:02] please remember to ask your questions in #ubuntu-classroom-chat [18:02] ok. let's get started [18:02] first, what exactly is a "LoCo Team"? [18:03] LoCo stands for Local Community [18:03] it's important to remember that an Ubuntu LoCo is a Special Interest Group (SIG), not a Linux Users Group (LUG) [18:03] as such, the purpose of ubuntu LoCo Teams is to build ubuntu in their respective community, and not general linux [18:04] although, people from all linux distros are more than welcome to join the team and learn more about ubuntu [18:04] loco teams are a collection of members all running ubuntu looking to learn more about the distro and to spread loco advocacy in their area [18:05] we advocate its use to organizations, schools and corporations [18:05] generally, we meet on a regular basis, like once a month, or more often, pending the team [18:05] we can meet in person, online (IRC), jabber muc, etc [18:06] generally, loco teams are usually free for participation and membership, although that's up to the specific team [18:07] asking for donations in not unheard of, and more than appropriate to help float some of the costs that a loco team uses, in terms of cds, t-shirts, posters, etc [18:07] finally, goals and vision can vary from team to team. they could consist of translation, support, advocacy, etc [18:07] ok. so, now that we know a little bit about what it is, why create a team? [18:08] well, cemputer users of simialr interests like to meet with each other and discuss what they learn and do with ubuntu [18:08] loco team members also enjoy advocating ubuntu together and discussing their success stories and where ubuntu is being deployed [18:08] of course, friendships are built, and a community is born [18:09] so, that brings me up to joining a loco team [18:09] loco teams are built around peopraphic locations [18:09] a fairly expansive list can be found at https://wiki.ubuntu.com/LoCoTeamList [18:10] if you are looking to see if a team exisits in your area, check there. chances are good that it does [18:10] joining a team generally means finding the teams IRC channel and joining online [18:11] of course, you can join their mailing list, add yourself to their wiki page, join the launchpad membership roster [18:11] once joined, the team will usually ask for participation and contribution to the team [18:12] sitting idle on a team, by not helping to beild the loco team or contribute, is generally discouraged [18:12] once joined, look at which talents you have, how you can contribute, how much time you have to contribute, and get started [18:13] it varies from team to team, but whatever you can do is great [18:15] sorry [18:15] family just came over celebrating our baby news [18:15] ok. let's look at starting a loco team [18:16] it's important to note first off that loco teams are not to replace existing LUGs/SIGs [18:16] rather, loco teams are designed to work hand-in-hand with existing LUGs to help spread ubuntu [18:17] much like a python SIG would be helping to spread python in a more general programming group [18:17] of course, the loco team wants to build team membership, and a great resource is the regional lugs, just be careful, would be my advice [18:18] keep the relationship strong between the local lugs in the area [18:18] now, you should not start a team in the same area, if you think that the loco team is not performing well, or as you would run it [18:18] rather, you should work with the existing loco leader to see what you can do to help make the team succeed [18:19] so, if you're sure that there is not a team in your area, after checking all the available resources, and "googling", then the first thing to do is to get those resources setup [18:21] mailing lists, irc, wiki pages are the essential resources that need to be setup [18:21] a team should not be worrying about setting up a cms site for the team [18:21] however, launchpad is a good resource to manage team membership [18:22] a loco team should be setup geographically by country, or by state in the U.S. [18:23] however, there are situations that metting in person is not appropriate, because the area is so large, so creating a smaller team under the country umbrella team or umbrella state team could work [18:23] i would advise to work with the umbrella loco team leader in that situation, and see what's best [18:24] ok. i've covered a lot of content up to this point. are there any questions in -chat that i can answer? [18:25] well, if no questions, i'll contiue with running and participating in a loco team and the difference between approved and non-approved teams [18:27] running a loco team can take a great deal of time to execute and execute well [18:27] running a team effectively takes a great deal of work and contributions from all team members not just the team leader and a couple of members here and there [18:28] running a team consists of install fests, local community work, advocation to schools, corporations, etc. [18:28] money is usually involved with running a team, but can be greatly minimized to a fow dollars per year per member if the team is run correctly and effectively [18:28] this includes money for food, t-shirts, mugs, posters, CD-, etc [18:28] *CDs [18:29] ok. now, i'm sure that some of you have heard about getting a team approved [18:30] what is it and why would you want your team approved? [18:30] there are a few incentives on getting an approved team [18:30] incentives such as CDs from Canonical, booth setups with kiosk materals as well as a sense of pride and accomplishment [18:31] cjb_ie> QUESTION: are loco teams meant to address anything in particular? unsurprisingly, localisation springs to mind - but anything else? [18:32] getting approved means an active team, with a good userbase, and active community involvement [18:32] it varies from team to team, but generally a good rule of thumb is 2-3 large community events, such as booths or install fests, large membership list, an active mailing list and regularly scheduled meetings [18:33] to get approved, create an application for approval on your team wiki, get in contact with jono to find out whether or not you can apply for approval from the CC [18:33] ok. questions [18:33] cjb_ie> QUESTION: are loco teams meant to address anything in particular? unsurprisingly, localisation springs to mind - but anything else? [18:33] :) [18:34] cjb_ie: advocacy advocacy advocacy. what a team should be focused on is getting schools, corporations, organizations, etc coverted to ubuntu === nikolam is now known as nikolam-away- [18:34] there are many ways to do it, and execute, but it's mainly important to get out there and talking [18:35] QUESTION: Are there any other teams like the Ubuntu US LoCo project for other groups around the world that are interested? And if not, who are some good people to talk to for mentoring? [18:36] nixternal: i am not aware of any teams like the US Teams Mentoring project in other areas. however, there are good people to get in contact with., such as: [18:36] Vorian, jono, nixternal (hehe), elkbuntu, pleia2 and others [18:36] if you stick around for 2.5 more hors, i will also be talking about the mentoring project and how it's made the US Teams successful [18:37] groovy [18:37] ok. i'm going to finish up with conflicts that may arise in loco teams, and how to resolve them, as well and misc resources and stuff [18:37] so, conflicts: they suck, but they happen from time to time === MrM is now known as mrmonday [18:38] the important thing to do when conflicts arise is not panic. they do NOT need to be taken to the CC whenever one arises [18:39] canflicts in a loco team should be taken care of in the team. if escalated, loco leaders such as those i just mentioned, can help point members in the right dircetion to get the conflict resolved [18:39] it's very possible that the conflict you are facing has been faced before and already resolved [18:40] also, 90% of problems come from a lack of communication between members. team members need to be united in purpose and vision, and open 100% to make it execute smoothly [18:40] i have seen a couple conflicts arise here and there, and in every case, when the team members got talking, it was resolved quickly and effeciently [18:41] the last topic that i have planned is a few odd-ball misc items that don't really fit, but i feel should be covered [18:42] one is a hot topic that has been on the mailing lists: tax exemption and liability coverage [18:42] both of these items need to be covered on a team-by-team basis [18:42] canonical will NOT provide an umbrella organization for loco teams to fall under [18:43] if a team feels they need it, they are more than welcome however, to go after it [18:43] *anything* that will make the team succeed should be looked at, even if it's tax exemption and liability coverage [18:44] ok. question time [18:44] BonesolTeraDyne> QUESTION: Is there a central place for LoCo teams to get tips on what kind of events they could hold, or how to present Ubuntu or possible new users\companies\etc...? [18:44] BonesolTeraDyne: there are resources all over the wiki, and even the forums. i don't know of specific pages off hand, but a few good resources that can get you pointed in the right direction would be: [18:45] https://wiki.ubuntu.com/LoCoTeams and #ubuntu-locoteams [18:46] of course, there is also the ubuntu-contacts mailing list and launchpad page, which will get you in contact with the major loco leaders directly [18:46] BonesolTeraDyne: but that's a *great* question. something that should be all over the wiki if it's not already [18:46] thanks. That answers the question quite nicely. [18:46] we should bring that up to the next loco doc day, where we work on filling holes and creating pages for loco teams [18:46] cool [18:47] to summarize this meeting at a 30,000 foot level: [18:47] * loco teams are ubuntu-specific teams, not lugs [18:48] * loco teams are about advocating ubuntu to anyone and everyone [18:48] * loco teams are build around geographic boundaries, tying regional people together [18:48] * joining a loco team is always encouraged, and more than welcome [18:49] * identify your talents to help buld the team and make the community stronger [18:49] * donate whatever time you can to building that community [18:49] * start a loco team if one does not exist in your area [18:49] * mailing list, wiki page and irc channel are the "essentials" for loco team resources [18:50] * running a team does not require money, but there's nothing wrong with asking for donations. :) [18:50] * the team sholud strive for approval by jono and the CC [18:50] * resolve conflicts within the team, and pull in loco team leaders only as needed [18:51] * LOCO TEAMS ROCK! [18:51] it looks like i have about 9 minutes to answer any questions, or to fill any holes that i may have missed [18:52] nicely done atoponce :) [18:52] Vorian: thank you [18:52] Thanks for a great presentation [18:52] :) [18:52] np [18:52] i think everyone is sleeping. :) [18:52] thanks atoponce [18:53] BonesolTeraDyne: np [18:53] Lardarse> QUESTION: Do you think that people who are not sure what they can offer to a LoCo should be put off from joining one? [18:53] atoponce, ^ [18:54] Lardarse: absolutely not. being active, even if you're not contributing, is okay. for example: [18:54] participating on the team mailing list or forums are a great way to be involved with the team [18:54] attend the meetings, and talk to friends about ubuntu [18:55] if everyone in the loco team did that, then every team would be 10x stronger than they currently are [18:55] good question. [18:56] :-) === nikolam-away- is now known as nikolam [18:57] thanks again atoponce :) [18:57] Vorian: np [18:58] everyone, come back for the loco teams mentoring project if you're still interested in loco teams [18:58] in 2.5 hours here [18:58] \o/ mentors! [18:58] or, 2 hours now. :) [18:58] * atoponce can count. promise! [18:58] come back? who said we were going to leave? :-) [18:58] exactly [18:59] Lardarse: good response. :) [18:59] /c === Vorian changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Current session: Ubuntu Studio - Cory Kontros [18:59] albeit a little too slow to be funny... [18:59] <_MMA_> Hi all. My name is Cory Kontros and I'm the lead on Ubuntu Studio. http://ubuntustudio.org My intro will be short. I'll post info with pauses so people can read. Then I'll open it up to questions. [19:00] <_MMA_> Our project aims to bring together the best in the free-software world for multimedia production as well as spotlight these applications and help them gain a wider audience. We also work to maintain a good relationship with upstreams and the Debian-multimedia team as this will only better that apps in Ubuntu Studio and raise the bar for Linux multimedia creation as a whole. [19:00] <_MMA_> The project started from a couple of Ubuntu users that were also users of DeMuDi. http://en.wikipedia.org/wiki/DeMuDi The project started simply as a guide for Dapper (https://help.ubuntu.com/community/UbuntuStudio/DapperPreparation) but was expanded to be a true Ubuntu-based, DeMuDi replacement. Simple beginning. :) [19:00] <_MMA_> I will be sighting info from our Wiki page. https://wiki.ubuntu.com/UbuntuStudio [19:00] <_MMA_> [19:01] <_MMA_> Our project provides packages suites of applications geared toward specific tasks. [19:01] <_MMA_> * Audio - All applications deemed necessary to provide a working PC studio environment. [19:01] <_MMA_> * Audio-Plugins - A collection of DSSI and LADSPA plugins. [19:01] <_MMA_> * Video - A collection of various video editing/creation apps. [19:01] <_MMA_> * Graphics - A collection of 2D/3D manipulation applications and plugins. [19:01] <_MMA_> A listing of packages can be found: https://wiki.ubuntu.com/UbuntuStudio/PackageList [19:01] <_MMA_> [19:02] <_MMA_> With our Gutsy release we have also met 4 of our major goals. [19:02] <_MMA_> * Provide a true realtime patched kernel. [19:02] <_MMA_> * Support AMD64. [19:02] <_MMA_> * All packages in the Ubuntu proper repos. [19:02] <_MMA_> * Clean up the "Sound&Video" menu. [19:02] <_MMA_> The team feels these will go along way toward improving the Ubuntu Studio users experience. [19:02] <_MMA_> [19:03] <_MMA_> We are a very small team an are always on the lookout for people who can give solid help. Currently we are looking for people to help with: [19:03] <_MMA_> * ISO testing [19:03] <_MMA_> * Documentation [19:03] <_MMA_> * Artwork for Gutsy. https://wiki.ubuntu.com/UbuntuStudio/Artwork/OfficialHardyIncoming (this includes all aspects for the "look&feel of Ubuntu Studio-Gutsy as well as the website.) [19:03] <_MMA_> * Knowledgeable help with packaging and technical issues around Linux audio. [19:03] <_MMA_> The front page of our wiki gives various ways to contact us about involvement. https://wiki.ubuntu.com/UbuntuStudio [19:03] <_MMA_> [19:04] <_MMA_> So with that I'll open it up. :) Please post questions to #ubuntu-classroom-chat prefixed with "QUESTION:" [19:04] c [19:04] ugh [19:04] sorry [19:04] join #ubuntu-classroom-chat [19:06] desertc: Thereis no upgrade path, as it uses ubuntu Gutsy as base. If you only want to install either audio, audio plougins, video, or graphics, you only need in stall the ubuntustudio-audio, -video, -graphics, or -audio-plugins as needed. [19:06] <_MMA_> ? I didnt see the question here. [19:06]