[15:00] <dholbach> WELCOME EVERYONE TO DAY THREE OF UBUNTU OPEN WEEK!
[15:00] <dholbach> A few organisational things before we get started....
[15:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-classroom.html following the conclusion of the session.
[15:01] <dholbach> If you have to leave during the sessions or want to go back and read transcripts or watch videos later on again, they will be available on https://wiki.ubuntu.com/UbuntuOpenWeek
[15:01] <dholbach> Also... if you have questions, please ask all the questions you have!
[15:01] <dholbach> But please ask on #ubuntu-classroom-chat (so join this one as well if you're not there yet) and please prefix your questions with QUESTION: so they stand out
[15:02] <dholbach> and the bot and I can pick them up more easily
[15:02] <dholbach> just as an example   QUESTION: What's the name of your dog?
[15:02] <dholbach> would work well
[15:02] <dholbach> all rightie
[15:02] <dholbach> so somebody asked me earlier what the session "Ubuntu Development Team" was going to be about
[15:03] <dholbach> it's not about app development, but about working on Ubuntu, the platform, itself
[15:03] <dholbach> everything to do with Ubuntu, its packages, the archive, fixing bugs in Ubuntu, etc will be the subject now
[15:03] <dholbach> Do we have any first questions already?
[15:04] <dholbach> Let's see what we get through today, but what I'd like to cover in this session at least is a good overview over "how Ubuntu is put together"
[15:05] <dholbach> that (and the answers to a bunch of good questions) should help you get started as you will at least have heard of the most important things already
[15:06] <dholbach> if I'm going too fast or slow, or don't make sense or you're curious about something, speak up and ask your QUESTION: in #ubuntu-classroom-chat
[15:06] <dholbach> Ubuntu is made up of thousands of different components, written in many different programming languages. Every component - be it a software library, a tool or a graphical application - is available as a source package.
[15:06] <dholbach> Source packages in most cases consist of two parts: the actual source code and metadata. Metadata includes the dependencies of the package, copyright and licensing information, and instructions on how to build the package.
[15:07] <dholbach> What I called "metadata" here, is what often is referred to as "packaging" in discussions.
[15:07] <dholbach> Once this source package is compiled, the build process provides binary packages, which are the .deb files users can install.
[15:07] <dholbach> Every time a new version of an application is released, or when someone makes a change to the source code that goes into Ubuntu, the source package must be uploaded to Launchpad’s build machines to be compiled.
[15:08] <dholbach> The resulting binary packages then are distributed to the archive and its mirrors in different countries. The URLs in /etc/apt/sources.list point to an archive or mirror.
[15:09] <dholbach> Every day images are built for a selection of different Ubuntu flavours, such as Ubuntu Desktop, Ubuntu Server, Kubuntu, Xubuntu, Lubuntu, Ubuntu Studio, Ubuntu for phones/tablets, etc.
[15:10] <ClassBot> fossterer asked: So, just uploading 'source code' and 'metadata' to launchpad itself is enough? I'm assuming Launchpad itself does compilation
[15:10] <dholbach> fossterer, yes, that's the case
[15:10] <dholbach> it's basically (in most cases, there are exceptions) a tarball containing the "upstream" source code, plus a set of changes plus the metadata
[15:11] <dholbach> Launchpad has a vast array of build machines, which then do the compilation
[15:11] <dholbach> https://launchpad.net/builders/ has a list of the machines and what they're doing right now.
[15:11] <ClassBot> clue_h asked: is bazaar used for this?
[15:12] <dholbach> clue_h, yes, in a lot of places, that's the case
[15:12] <dholbach> for example do we have many projects which are done in Launchpad using bazaar, where daily builds happen automatically, so Launchpad (LP) will checkout the branch and do a build
[15:13] <dholbach> or builds of certain packages first go through a few rounds of automated testing and then land on the build machines
[15:13] <dholbach> in a lot of other cases this is done manually, so the source package (source + metadata) is uploaded manually
[15:13] <ClassBot> fossterer asked: But I remeber reading that 'Bazaar' is just another source control mechanism.. Is uploading to Launchpad integrated into it?
[15:13] <dholbach> fossterer, yes it is
[15:14] <dholbach> for example you can run            bzr branch lp:click-reviewers-tools            (just a random example)
[15:14] <dholbach> ... which will get you the source from Launchpad
[15:14] <dholbach> or       bzr branch ubuntu:gedit              will get you the source for the most recent gedit source package in Ubuntu
[15:15] <ClassBot> thmslld asked: What is the technical reason that third party packages are not always updated to the latest version in the Ubuntu Software Centre when a new version comes out. Will this change with Click packages?
[15:16] <dholbach> thmslld, there are a number of reasons for this and I'll deal with the question in more detail in just a bit - the short version is stability and just letting minimal fixes in for old releases
[15:16] <dholbach> as I said more details in just ab it
[15:16] <dholbach> a bit
[15:16] <dholbach> click packages I can probably talk about a bit as well
[15:17] <dholbach> it's a package format (VERY close to the .deb format) which is used on Ubuntu for phones/tablets for 3rd party apps
[15:17] <dholbach> it's very much stripped down, so packages have almost no access to things which can cause problems (ie "rm -rf /" in a postinst script)
[15:18] <dholbach> and the code in the packages is running heavily confined through apparmor
[15:18] <dholbach> this allows us to say "ok, we don't need a source code review of every single bit that goes in"
[15:18] <dholbach> which in turn allows us to give more power to app developers who can then choose to update their packages whenever they like
[15:19] <dholbach> this is currently just possible on Ubuntu for phones/tablets
[15:19] <dholbach> for regular Ubuntu we will have to answer a few more questions to get this done
[15:19] <dholbach> all right... back to where I was earlier :-)
[15:19] <dholbach> but keep the questions coming
[15:19] <dholbach> I like it when there's more interaction :)
[15:19] <dholbach> The images I talked about earlier can be used in various circumstances. There are images you can put on a USB key, you can burn them on DVDs, you can use netboot images and there are images suitable for your phone and tablet.
[15:20] <dholbach> Ubuntu Desktop, Ubuntu Server, Kubuntu and others specify a list of required packages that get on the image. These images are then used for installation tests and provide the feedback for further release planning.
[15:20] <dholbach> Ubuntu’s development is very much dependent on the current stage of the release cycle. We release a new version of Ubuntu every six months, which is only possible because we have established strict freeze dates.
[15:21] <dholbach> to see what a release cycle looks like, check out https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule - it's a timetable for the 14.04 release cycle
[15:21] <dholbach> With every freeze date that is reached developers are expected to make fewer, less intrusive changes. Feature Freeze is the first big freeze date after the first half of the cycle has passed.
[15:21] <dholbach> At this stage features must be largely implemented. The rest of the cycle is supposed to be focused on fixing bugs. After that the user interface, then the documentation, the kernel, etc. are frozen, then the beta release is put out which receives a lot of testing.
[15:21] <dholbach> From the beta release onwards, only critical bugs get fixed and a release candidate release is made and if it does not contain any serious problems, it becomes the final release.
[15:22] <ClassBot> fossterer asked: (Click Packages) This brings to my mind the 'Android Permissions model' which shows a user what all an app is capale of, if installed. Am I getting it right?
[15:23] <dholbach> fossterer, yes, that's similar in the click world as well - as an app author you have to specify which security permissions your app needs
[15:23] <dholbach> (I'll focus a bit less on apps for phone/tablet now, if that's OK)
[15:23] <dholbach> The next session will deal a bit more with App Development. :)
[15:23] <ClassBot> clue_h asked: what is the difference between alpha1 and alpha2 in the release cycle?
[15:24] <dholbach> clue_h, we just named the different milestones consecutively
[15:24] <dholbach> alpha 1, alpha 2, beta 1, beta 2, final
[15:24] <dholbach> this is to give users and testers an indication of how "complete" the image should feel
[15:26] <dholbach> Thousands of source packages, billions of lines of code, hundreds of contributors require a lot of communication and planning to maintain high standards of quality. At the beginning and in the middle of each release cycle we have the Ubuntu Developer Summit where developers and contributors come together to plan the features of the next releases.
[15:27] <dholbach> The next Summit is going to be called Ubuntu Online Summit though, and will be happening ... let me find the link.
[15:27] <dholbach> 10th – 12th June 2014
[15:27] <dholbach> http://www.jonobacon.org/2014/04/03/ubuntu-online-summit-dates/
[15:27] <dholbach> Every feature is discussed by its stakeholders and a specification is written that contains detailed information about its assumptions, implementation, the necessary changes in other places, how to test it and so on. This is all done in an open and transparent fashion, so you can participate remotely and listen to a videocast, chat with attendants and subscribe to changes of specifications, so you are always up to date.
[15:28] <dholbach> This is the beauty of Ubuntu: you can be part of it, you can be actively involved, you can meet the people and learn more.
[15:28] <dholbach> So be there at the next summit and find something which attracts you.
[15:28] <ClassBot> fossterer asked: 'Ubuntu Online Summit' is about "Ubuntu" itself but not the apps. Right?
[15:29] <dholbach> fossterer, So the way these summits worked up until now was that we had a multitude of simultaneous tracks.
[15:29] <dholbach> In each track there was always an hour long discussion about a specific feature or a specific initiative.
[15:29] <dholbach> The tracks had name like "App Dev 1" or "Client 2" or "Cloud/Server 1", "Foundations", etc.
[15:30] <dholbach> So a lot of focus was on App Development, but more on a meta level, like "how do we want these phone/tablet apps to work on the desktop in the future" or "how do we better teach how to write apps"
[15:30] <dholbach> ... less about specific apps
[15:30] <ClassBot> fossterer asked: To clarify, about 'Dash' rather than 'third party app'?
[15:31] <dholbach> So yeah, we talked about Ubuntu, the dash and other things, and about third party apps more on a meta level, if that makes sense.
[15:31] <dholbach> Not every single change can be discussed in a meeting though, particularly because Ubuntu relies on changes that are done in other projects. That is why contributors to Ubuntu constantly stay in touch.
[15:32] <dholbach> Most teams or projects use dedicated mailing lists to avoid too much unrelated noise. For more immediate coordination, developers and contributors use Internet Relay Chat (IRC). All discussions are open and public.
[15:32] <dholbach> Another important tool regarding communication is bug reports. Whenever a defect is found in a package or piece of infrastructure, a bug report is filed in Launchpad. All information is collected in that report and its importance, status and assignee updated when necessary. This makes it an effective tool to stay on top of bugs in a package or project and organise the workload.
[15:33] <dholbach> Most of the software available through Ubuntu is not written by Ubuntu developers themselves. Most of it is written by developers of other Open Source projects and then integrated into Ubuntu. These projects are called “Upstreams”, because their source code flows into Ubuntu, where we “just” integrate it.
[15:34] <dholbach> The relationship to Upstreams is critically important to Ubuntu. It is not just code that Ubuntu gets from Upstreams, but it is also that Upstreams get users, bug reports and patches from Ubuntu (and other distributions).
[15:34] <dholbach> This makes working in the Ubuntu project very interesting, as you're not working just on Ubuntu, but also collaborate with other projects.
[15:35] <dholbach> Sometimes different projects have different goals at a certain time, which makes things a bit more complicated now and then, but more on that in just a sec. :)
[15:35] <dholbach> The most important Upstream for Ubuntu is Debian. Debian is the distribution that Ubuntu is based on and many of the design decisions regarding the packaging infrastructure are made there. Traditionally, Debian has always had dedicated maintainers for every single package or dedicated maintenance teams.
[15:36] <dholbach> In Ubuntu there are teams that have an interest in a subset of packages too, and naturally every developer has a special area of expertise, but participation (and upload rights) generally is open to everyone who demonstrates ability and willingness.
[15:36] <ClassBot> fossterer asked: If I write an app,  say a game, and make the project avaialble on Launchapd, what else do I need make my project an "upstream"?
[15:37] <dholbach> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages explains how to get it into Ubuntu as a standard .deb package (which will work on the traditional Desktop, etc.)
[15:38] <dholbach> http://developer.ubuntu.com/publish/apps/ explains how to get your app into the software store for phones/tablets, which is a bit more straight-forward. ... Hopefully we are going to get these packages on the desktop very very soon. :-)
[15:39] <dholbach> So let's say you want to fix a bug in Ubuntu... getting a change into Ubuntu as a new contributor is not as daunting as it seems and can be a very rewarding experience. It is not only about learning something new and exciting, but also about sharing the solution and solving a problem for millions of users out there.
[15:39] <dholbach> Open Source Development happens in a distributed world with different goals and different areas of focus. For example there might be the case that a particular Upstream is interested in working on a new big feature while Ubuntu, because of the tight release schedule, is interested in shipping a solid version with just an additional bug fix. That is why we make use of “Distributed Development”, where code is being worked on in variou
[15:39] <dholbach> s branches that are merged with each other after code reviews and sufficient discussion.
[15:40] <ClassBot> gaberlunzie asked: to whom and how does one "demonstrate ability and willingness", as you say?
[15:41] <dholbach> gaberlunzie, So first of all, if you have a bug fix and don't plan to get involved much more, that bug fix is good enough. It'll be reviewed, tested and uploaded when it's ready.
[15:42] <dholbach> If you plan to get upload rights yourself, you will have to work as part of the team for a while, get your packages and fixes reviewed. Then you can write an application for getting upload rights.
[15:42] <dholbach> You can ask people you've worked with for support, and the Developer Membership Board will then make a decision.
[15:43] <dholbach> In Ubuntu, everybody has to go through this process, no matter if they're experienced Open Source developers, or work for Canonical or another company, everybody has to go through this.
[15:43] <ClassBot> fossterer asked: Does it mesn apt-get works anyway if I do a "sudo add-apt-repository" if I dont't go with publishing to Software Center? Launchpad itself gives a ppa address. Isn't it?
[15:43] <dholbach> fossterer, yes, you can set up a PPA and your users can add it and get your packages through that
[15:45] <dholbach> Ok.. so getting back to the case where an upstream project has great plans for a new big feature and Ubuntu has to stay on the old version because we release soon.
[15:45] <dholbach> If we wanted to integrate a good change from Upstream (without the big feature as we won't have enough time to integrate and test it properly), we'd do this:
[15:46] <dholbach> In the example mentioned above it would make sense to ship Ubuntu with the existing version of the project, add the bugfix, get it into Upstream for their next release and ship that (if suitable) in the next Ubuntu release. It would be the best possible compromise and a situation where everybody wins.
[15:46] <dholbach> Distributed revision control helps a lot there.
[15:47] <dholbach> Now is probably a good time to thmslld's question.
[15:47] <dholbach> The question was: why do some 3rd party apps get out of date in stable releases.
[15:47] <dholbach> (slightly paraphrased)
[15:48] <dholbach> First of all: we focus all Ubuntu developers always on one current release. At every single moment, there's just one development release at a time.
[15:48] <dholbach> Trying to work on different releases at the same time, would be hard, as you'd have to stay on top of things and fix bugs and implement features everywhere at the same time.
[15:48] <dholbach> This is also a problem where you quickly have not enough hands on deck.
[15:49] <dholbach> So what we do for old, stable releases is that we fix security bugs and hard-core, super important bugs.
[15:49] <dholbach> This is always done after a lot of testing.
[15:49] <dholbach> if you have millions of users using a stable release, you can't pull the rug under them.
[15:50] <dholbach> Sometimes a "harmless" and "obvious" one-line fix can break behaviour users relied on.
[15:50] <dholbach> if you have a look at the first few paragraphs of https://wiki.ubuntu.com/StableReleaseUpdates (which explains the process on how to get updates into a stable release), you will see a couple of examples of where this went wrong in the past.
[15:51] <ClassBot> There are 10 minutes remaining in the current session.
[15:51] <dholbach> So while it looks like a painful process and some apps or packages do get out of date, I hope it's a bit clearer now why this happens.
[15:51] <dholbach> The good thing is that a new Ubuntu release is always just 6 months (maximum) away. ;-)
[15:51] <dholbach> If you thought bug fixing looks interesting now... how to go about it?
[15:51] <dholbach> To fix a bug in Ubuntu, you would first get the source code for the package, then work on the fix, document it so it is easy to understand for other developers and users, then build the package to test it.
[15:52] <dholbach> After you have tested it, you can easily propose the change to be included in the current Ubuntu development release. A developer with upload rights will review it for you and then get it integrated into Ubuntu.
[15:52] <dholbach> When trying to find a solution it is usually a good idea to check with Upstream and see if the problem (or a possible solution) is known already and, if not, do your best to make the solution a concerted effort.
[15:52] <dholbach> Additional steps might involve getting the change backported to an older, still supported version of Ubuntu and forwarding it to Upstream.
[15:52] <ClassBot> johnjohn101 asked: can you explain the difference between regular, muliverse and universe?
[15:52] <dholbach> johnjohn101, sure
[15:53] <dholbach> we have "main" and "universe" which both open source software with free software licenses, which follow the DFSG (debian free software guidelines)
[15:53] <dholbach> and "restricted" and "multiverse" which contain the rest
[15:54] <dholbach> "main" and "restricted" is what gets on the standard images and what gets support from Canonical
[15:54] <dholbach> If you think about getting involved, here's what's you should consider:
[15:54] <dholbach> The most important requirements for success in Ubuntu development are: having a knack for “making things work again,” not being afraid to read documentation and ask questions, being a team player and enjoying some detective work.
[15:55] <dholbach> It's less about "knowing five programming languages"
[15:55] <dholbach> ... although that obviously doesn't hurt :)
[15:55] <dholbach> Good places to ask your questions are ubuntu-motu@lists.ubuntu.com and #ubuntu-motu on irc.freenode.net. You will easily find a lot of new friends and people with the same passion that you have: making the world a better place by making better Open Source software.
[15:56] <dholbach> One page you should definitely bookmark is http://packaging.ubuntu.com
[15:56] <ClassBot> There are 5 minutes remaining in the current session.
[15:56] <dholbach> along with English it's available in Spanish, Russian, Brazilian Portuguese, German and French as well
[15:56] <dholbach> and should explain the most important steps in Ubuntu Development
[15:56] <dholbach> Do we have any more questions? :)
[15:57] <ClassBot> j_f-f asked: Sorry I'm to late (RL) :  I'm a software Developer especially with C++. How can I help?
[15:57] <dholbach> nice one
[15:58] <dholbach> There are lots of things to be done in Ubuntu: you can help fixing build failures, you can help merging changes from Debian, you can help fixing bugs, help with transitions in the Ubuntu archive, etc
[15:59] <dholbach> if you have a look at packaging.ubuntu.com it links to a couple of places which have information about where to get started
[15:59] <dholbach> and the MOTU team is always happy to help as well
[15:59] <ClassBot> gaberlunzie asked: mentioning languages, what would be the top, say, 3 languages used in ubuntu dev?
[16:00] <dholbach> C, Python and C++ probably, but there's packages in every single language under the sun
[16:00] <dholbach> that's another beautiful thing in open source:
[16:00] <dholbach> you can get the source
[16:00] <dholbach> you can learn by reading and fixing it
[16:00] <ClassBot> fossterer asked: I see an application being used in the field of Networks (Academic) whose instalaltion is always clumsy with user having to edit scripts, install dependencies indvidually etc.
[16:00] <dholbach> fossterer, I'd suggest you have a chat with the folks in #ubuntu-motu about this
[16:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-classroom.html following the conclusion of the session.
[16:00] <dholbach> we're out of time for this session
[16:01] <dholbach> thanks a lot everyone!
[16:01] <dholbach> Luckily I'm also copresenting this session, so running over a little bit is a less rude ;-)
[16:01] <dholbach> Thanks a lot everyone for attending the last session. You all rock!
[16:02] <dholbach> so dpm, my co-host is going to be late, as he's in a call which is running over
[16:02] <dholbach> a likely story, if you ask me - more like having ice cream somewhere in the sun or something
[16:03] <dholbach> This session is about Organising Ubuntu App Dev Schools, which is a new initiative we started some weeks ago :)
[16:05] <dholbach> For this we put together materials for teaching the first steps of Ubuntu App Development to others. If you spend some time preparing yourself, you can get up to speed in just a little bit of time and then meet up with people in your LoCo team, your LUG, your university group or just some friends and tell them about it.
[16:06] <dholbach> We want to make it really really easy, because what's happening in Ubuntu right now is actually quite exciting and you can very easily benefit from it.
[16:06] <dholbach> Two things I love about Ubuntu's App Story are:
[16:07] <dholbach>  1. You write the code for an app once, and it will run on the phone, the tablet and soon on the desktop, the TV and elsewhere as well.
[16:09] <dholbach>  2. It got lots and lots easier. We had people working on Ubuntu's Core Apps, so apps which are installed by default on the Ubuntu phone image (like the calculator, calendar, clock and others), who had never used QML or HTML5 before, but they were up to speed in no time and contributed lots of excellent code.
[16:09] <dholbach> So in short: there's convergence (same code running on all devices) and the choice of technologies which helps you to get stuff done very quickly. :)
[16:10] <ClassBot> thmslld asked: Do you know of any plans for books on learning QML or QT5?
[16:11] <dholbach> We have quite a bit of information up on http://developer.ubuntu.com/
[16:12] <dholbach> This plus some toying around and reading API docs (if you have done a bit of development before) should put you into a position where you can write apps very quickly. That plus the community of engineers and volunteers who help out a lot.
[16:12] <dholbach> I'm sure there are books about Qt and QML development, I don't know (to be brutally honest) how good or how up to date they are. AFAIK they don't deal with Ubuntu App development though.
[16:13] <dpm> yes, I'd recommend starting with the tutorials on developer.ubuntu.com to get a feel for QML and how the tools work, and then you can dive into the details
[16:13] <dholbach> welcome dpm :)
[16:13] <dpm> hey, sorry for the delay
[16:13] <dholbach> no worries :)
[16:14] <dholbach> So let's say you are interested, you want to prepare for your LUG/LoCo/university/friends meet-up and talk about app development... what to do?
[16:14] <dpm> find a venue! :-)
[16:15] <dholbach> Some LoCo teams or LUGs have the privilege of having a venue they always go to, but if you don't, dpm probably has an idea what to do.
[16:15] <dpm> :-)
[16:16] <dpm> So generally finding a venue is the starting point of planning an app dev school
[16:16] <dpm> as dholbach is saying, perhaps your LoCo already has a regular meeting place, but if you don't,
[16:16] <dpm> it's worth looking for a local hackerspace or makerspace
[16:17] <dpm> or if the event is going to be smaller, an internet cafe or someone's place will do nicely too
[16:17] <dholbach> or ask in your university for a room, or a library
[16:17] <dpm> indeed
[16:18] <dpm> if you're going to talk about apps and show off the SDK it's also important that there's wifi if possible, and mains connection would be good too
[16:18] <dpm> It all depends on the size of the event you're planning
[16:18] <dpm> but generally folks will come with their laptops, so it's good to be prepared for that
[16:19] <dpm> so think about how big you're planning your event to be and start looking for an appropriate venue first
[16:19] <dpm> you can then work on the finer details about organizing food and beverages for participants,
[16:20] <dpm> chairs, tables, etc.
[16:20] <dpm> once you've organized a venue, you'll probably have a date too,
[16:21] <dpm> and from that point on, you can start promoting it!
[16:21] <dholbach> Yes :)
[16:21] <dpm> dholbach, where can one promote an app dev school event?
[16:21] <dholbach> A very good place to advertise the event is http://loco.ubuntu.com
[16:21] <dholbach> as Ubuntu users can very easily check out where events nearby are, etc
[16:22] <dholbach> also use the regular communication channels for your local Ubuntu team as well
[16:22] <dholbach> mailing lists, forums, facebook, twitter, google+ and other social media
[16:22] <dholbach> inform other LUGs in your city too
[16:23] <dholbach> if you put effort into the event, you might as well have people there :)
[16:23] <dpm> Talking about the LoCo portal, I hear this weekend there is a big App Dev School being organized by the Italian LoCo team! :) http://loco.ubuntu.com/events/global/2677/
[16:23] <dholbach> Awesome!
[16:23] <dholbach> Let people know
[16:23] <dholbach>  - when and where the App Dev School will be held. A map and simple directions will help.
[16:23] <dholbach> what to expect (apart from hot Ubuntu App Development love): maybe soft drinks, pizza?
[16:24] <dpm> yay!
[16:24] <dholbach> but you can probably also let people know in local computer retail stores or local cafés
[16:24] <dholbach> or local news media too
[16:24] <dholbach> Do we have any questions up until now about organising the event?
[16:25] <dpm> while we're waiting for that, another thing to mention
[16:25] <dpm> regarding logistics
[16:26] <dpm> is that it's useful to prepare a form for folks to sign up to your event
[16:26] <dholbach> ah yes
[16:26] <dpm> so that you know in advance an estimation of how many people will attend
[16:26] <dholbach> loco.ubuntu.com is helpful there as well :)
[16:26] <dpm> yes :)
[16:27] <dholbach> looks like we're fine up until now in terms of question... let's talk a bit about actually teaching Ubuntu App Development
[16:27] <dpm> you can use the form from there straight away or you can use your own one if you've already got one set up
[16:27] <dpm> ok
[16:27] <dholbach> sorry, I didn't mean to cut you off :)
[16:27] <dpm> I'd finished, let's talk about teaching :)
[16:27] <dholbach> awesome
[16:28] <dholbach> we have materials, right dpm? :)
[16:28] <dpm> oh yeah
[16:28] <dpm> So to ensure the presenters don't have to start from scratch, we've prepared a set of materials
[16:28] <dpm> that can be used to base presentations on
[16:29] <dpm> you can use them as they are, they are ready to go
[16:29] <dpm> or you can modify them to your needs
[16:29] <dpm> or translate them!
[16:29] <dholbach> Oh yeah... if you do, let dpm or myself know and we can upload them and link to them. :)
[16:30] <dpm> indeed, by now we've got translations into Chinese, Catalan, Spanish and Italian
[16:30] <ClassBot> fossterer asked: If I get to translate them, can I upload it to you?
[16:30] <dholbach> sure... you can just give me the link and I'll link to the presentations in the right places :)
[16:31] <dholbach> so whoever prepares a session can use your translated materials if that works better for them
[16:31] <dpm> yeah, let us give you the link to the materials in a minute so you can see how to do it
[16:31] <dpm> I was just building up the stage for them :)
[16:31] <dholbach> the slides we have contain speaker notes as well, which also helps with preparing for the sssions
[16:31] <dpm> yeah, these are quite useful indeed
[16:32] <dpm> The materials are there to help you get started, they are guidelines, and you can choose whether to use them fully or to roll your own
[16:32] <dpm> The main materials are slide decks you can download from here:
[16:32] <dpm> An indroduction to Ubuntu for phones/tablets - http://people.canonical.com/~dholbach/tmp/apps-presentations/Ubuntu,%20the%20new%20force%20in%20mobile.odp
[16:33] <dpm> Getting started with Ubuntu App Development - http://people.canonical.com/~dholbach/tmp/apps-presentations/Workshop%20-%20get%20started%20creating%20Ubuntu%20apps.odp
[16:33] <dholbach> we have two sets of slides, one being a general introduction to Ubuntu for phones/tablets, which sets the stage for the second, where you actually dive into the technical bits and help people get set up to use the Ubuntu SDK and then proceed to the hands-on programming part
[16:33] <dholbach> it always depends how experienced your audience is
[16:34] <dholbach> if you have programming experts who already know a lot about Ubuntu, you can probably zip through the presentations very quickly
[16:34] <dholbach> if your audience is less experienced you will need a full afternoon (4h or something)
[16:34] <dholbach> generally I'd recommend to ask early on
[16:35] <dpm> indeed, preparation is key
[16:35] <dholbach> and maybe even mention on the invitation that folks had at least toyed around a bit with programming in the past
[16:35] <dholbach> although I'm not 100% sure about that one
[16:35] <dholbach> dpm, what do you think?
[16:36] <dpm> dholbach, I actually agree, I think that participants should have a basic understanding of programming to get the most out of the session
[16:36] <dpm> Another set of materials that we've got are the tutorials on developer.ubuntu.com
[16:37] <dpm> To pick just two examples that illustrate writing QML and HTML5 apps:
[16:37] <dpm> http://developer.ubuntu.com/apps/qml/tutorial/building_your_first_qml_app/
[16:37] <dpm> http://developer.ubuntu.com/apps/html-5/tutorials/meanings-app-html5-tutorial/
[16:37] <dholbach> awesome
[16:37] <dpm> you can use these to get some ideas for easy apps to get the audience started writing real-world apps
[16:38] <dpm> If you you don’t have a preference, if you want to talk about HTML-5 or QML,
[16:38] <dpm> you could ask your audience for what they’re interested in.
[16:38] <dpm> If you have lots and lots of time, do both! :-)
[16:39] <dpm> Also as preparation for the session as an instructor
[16:39] <dholbach> if, during the time where you prepare for the sessions, you should have any questions: let us know, get in touch with the ubuntu app community - there's lots of folks who are happy to help you get started: http://developer.ubuntu.com/community/
[16:39] <dpm> you can learn more about the Ubuntu platform and technologies involved in creating apps watching the videos of some past Ubuntu events
[16:39] <dholbach> ah yes, good thinking!
[16:40] <dpm> such as the Ubuntu App Developer week :)
[16:40] <dpm> Here's a link to the past UADW where you can watch some interesting videos: https://wiki.ubuntu.com/summit.ubuntu.com/appdevweek-1403/
[16:40] <dholbach> on http://summit.ubuntu.com/appdevweek-1403/ you can see the timetable of last times event :)
[16:41] <dholbach> looks like dpm wanted to give you an obfuscated version of the URL instead ;-)
[16:41] <dpm> ah, thanks dholbach :)
[16:41] <dpm> any questions on materials, so far?
[16:42] <dpm> dholbach, shall we talk about actually giving the session, then?
[16:42] <dholbach> one thing I just thought of: if you have folks in the audience who don't run Ubuntu on their laptop, we have VirtualBox images prepared for you
[16:43] <dpm> ah yeah
[16:43] <dholbach> you can put these images on a usb key and pass them around during your presentation, so no matter if they run another linux or windows or use a mac, they can easily use Ubuntu and the Ubuntu SDK
[16:43] <dholbach> but that's now all I had on materials :)
[16:43] <dpm> we can also invite Windows and Mac folks in there, we're a very welcoming bunch :)
[16:44] <dholbach> so yeah... giving the session
[16:44] <dholbach> There are multiple ways to give the session. You could just demo everything, especially if you have a lot of people in the audience who didn’t bring a laptop, but in general there’s a lot of worth in everyone doing as much as they can on their own.
[16:45] <dholbach> There are different ways to run the session: you can for example run through the online tutorial step-by-step
[16:45] <dholbach> If you do...
[16:45] <dholbach> Ensure that every participant has successfully installed the SDK and has opened the page to the tutorial
[16:45] <dholbach> Start going through the tutorial yourself, and share your screen to show what you are doing with Qt Creator
[16:46] <dholbach> Don’t be too quick: divide your explanation into sections and make sure everyone is following before going to the next section. An easy way to determine a section is to use the code snippets in the tutorial to mark the start of the next section
[16:46] <dholbach> You can ask participants to copy and paste the code snippets directly from the tutorial’s web page.
[16:46] <dholbach> Make sure you explain what each section is doing by running the code snippet on Qt Creator yourself and asking the participants to do the same. You can then tweak parts of the tutorial to show particular aspects in more detail (e.g. ask participants to tweak height/width of the MainView and see what’s happening)
[16:47] <dholbach> Choose either to run the code on a device or on the emulator. A good compromise might be that the presenter runs on a device and those participants who don’t have one run it with the emulator
[16:47] <dholbach> Try not to just follow the tutorial 100%: it’s just a guideline, so try to bring something of your own or modify it to keep the audience engaged
[16:47] <dholbach> Questions so far? Could you imagine running an event like this now? :)
[16:48] <dholbach> This might now seem a bit hard and lots to prepare, but it's actually not that bad and you could also co-present together with a friend, which would make the whole thing more fun
[16:48] <dholbach> ... and allow you to run around answering questions together
[16:49] <dholbach> If you don't want to go through the tutorials, you could also ask your participants to run the tutorial themselves
[16:49] <dpm> Yes, even if you're not yet part of a LoCo, you can get in touch with a LoCo or with a bunch of friends in your area to organize the event
[16:49] <dholbach> yeah, that's right
[16:49] <dholbach> ubuntu-locoteams@lists.ubuntu.com is a good place to ask for help
[16:50] <dholbach> Another alternative: point them to the online tutorials and ask them to follow them, to ask if they’ve got questions at any point and to show you the end result.
[16:50] <dholbach> Whatever you decide to do, make sure you walk around the room and see if people run into issues or get stuck.
[16:50] <ClassBot> There are 10 minutes remaining in the current session.
[16:50] <dholbach> Any more questions?
[16:51] <dholbach> Sorry about that, jose just corrected me: it's loco-contacts@lists.ubuntu.com
[16:51] <dholbach> . o O { That's what I get for trying to write up mail addresses from the top of my head... }
[16:51] <dholbach> A few other things you might want to bear in mind during the session:
[16:51] <dholbach> Showing the app running on a device. If you have a device running Ubuntu and want to show how the app is working out, bring a webcam, so you can record what’s on the device’s screen and share it over the projector.
[16:52] <dholbach> Use the emulator. Using the emulator is very important as an app developer, so showing its use early on is very important to new app developers.
[16:52] <dholbach> Invite questions. Make sure you remind everyone that questions are welcome and that you’re happy to find out together with the audience how things work, how things can be made better and that it’s totally fine to ask, suggest or get involved.
[16:52] <dpm> - Get feedback. It’s important that we learn from the questions and suggestions of newcomers. Point your audience to our feedback form (https://www.surveymonkey.com/s/ubuntuappdevschool), so we can further improve the events.
[16:53] <dpm> - Ask the experts. If you don’t know the answer to a question: no problem. You can demonstrate first-hand how to get in touch with the app developer community. Either join IRC and ask the question there or try asking the question on askubuntu. This will show the audience how to get in touch with the world-wide community of app developers.
[16:53] <dpm> - Use a flipchart or a board. If available, it’s really useful to use a board to explain particular aspects of the code or the SDK with drawing quick diagrams or explanations.
[16:54] <dpm> And finally, to wrap up
[16:54] <dpm> Here's how you can get help:
[16:54] <dpm> - Ping me (dpm) or dholbach on the #ubuntu-app-devel channel
[16:55] <dpm> If we're not around, feel free to ask the question on the channel, and if there's someone around that can help, they'll try to answer
[16:55] <ClassBot> There are 5 minutes remaining in the current session.
[16:55] <dholbach> - For help with the organisation of the event, ask on loco-contacts@lists.ubuntu.com - ther are lots and lots of people who organised lots of events already.
[16:55] <dholbach> And yeah, for questions about app development, what dpm said. :-)
[16:56] <dpm> Check out http://developer.ubuntu.com/community/ for many other ways to get in touch with other fellow community members who are as excited about app development and willing to help as you
[16:56] <dholbach> Writing apps for Ubuntu has never been this easy and also getting them published. It'll take a bit until they'll be available on the Desktop, but it won't be too crazy long. This is definitely worth bringing up in your local team or with friends. :)
[16:57] <dholbach> Any more questions or shall we wrap this up?
[16:58] <dholbach> Ok, look like we're good.
[16:58] <dpm> I think we should be good to go, yes!
[16:58] <dholbach> Thanks a lot everyone! You're all heroes!
[16:58] <dholbach> Thanks a bunch dpm! :)
[16:58] <dpm> Indeed, thanks a lot everyone for listening in and thanks dholbach!
[16:59] <dholbach> Rock on!
[16:59] <dpm> \m/
[16:59] <dholbach> Next up is the Kubuntu Team - Quintasan, ovidiu-florin will take over the mic in just a sec.
[16:59] <Quintasan> Hmm
[16:59] <Quintasan> yes
[16:59] <ovidiu-florin> Hello world
[16:59] <Quintasan> Thanks dholbach and dpm for great session!
[17:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-classroom.html following the conclusion of the session.
[17:01] <Quintasan> So, Ladies and Gentlemen, welcome to the Kubuntu Team talk.
[17:02] <Quintasan> ovidiu-florin and I will be talking about some blue gears, unicorns, ninjas and whatnot
[17:02] <Quintasan> But first of all I'd like to introduce myself. My real name is Michał Zając, currently I'm studying and I have been contributing to Kubuntu since 2009
[17:03] <Quintasan> ovidiu-florin: you there?
[17:04] <ovidiu-florin> And I am Ovidiu-Florin Bogdan, software developer and Kubuntu enthusiast and promoter for a couple of years.
[17:04] <ovidiu-florin> And I am Ovidiu-Florin Bogdan, software developer and Kubuntu enthusiast and promoter for a couple of years.
[17:04] <ovidiu-florin> sorry for that, network lag
[17:05] <Quintasan> And we are going to talk about how *you* can contribute to Kubuntu
[17:05] <Quintasan> Kubuntu as any other open source project is looking for new people.
[17:06] <Quintasan> There are numerous different ways in which you can contribute, both directly and indirectly.
[17:07] <Quintasan> But before that you might want to ask *why* would you want to contribute.
[17:08] <ovidiu-florin> Kubuntu is a great Linux Distro that bring to the world the best of two worlds: Ubuntu and KDE combined
[17:08] <ovidiu-florin> it brings in the portability and stability of Ubuntu (as a base)
[17:09] <ovidiu-florin> and the beautifull and amazingly customizable Desktop environement from KDE
[17:10] <ovidiu-florin> toghether they make a great pair, great for the beginner and the advanced
[17:11] <Quintasan> so ovidiu-florin here joined us because he liked what we are doing, that's also a good reason
[17:11] <Quintasan> For me it was a mix of wanting to learn something new, testing myself and hoping that somewhen someone would think "Hey, those guys over there are doing a pretty good job." :)
[17:12] <Quintasan> Now that I think about it, that worked out.
[17:12] <Quintasan> Let's go back to *how* to contribue.
[17:13] <Quintasan> In general:
[17:13] <Quintasan> 1. You want to hang around #kubuntu-devel since this is Kubuntu Developers headquaters
[17:14] <Quintasan> 2. You can also join #kde-devel
[17:15] <Quintasan> 3. General support channels are also good to hang around, those are #kubuntu and #kde
[17:15] <Quintasan> ovidiu-florin: Anything I forgot?
[17:15] <ovidiu-florin> You can also state your opinion on our mail list
[17:15] <Quintasan> Which would be kubuntu-devel@lists.ubuntu.com
[17:16] <Quintasan> Time to get more specific.
[17:16] <Quintasan> As I said there are numerous ways to contribute, let me list them.
[17:16] <Quintasan> 1. Translations
[17:16] <Quintasan> 2. Testing
[17:16] <Quintasan> 3. Programming
[17:17] <Quintasan> 4. Packaging
[17:17] <Quintasan> 5. Working upstream
[17:17] <Quintasan> 6. Other related stuff
[17:17] <Quintasan> Let's talk about translations first.
[17:18] <Quintasan> Things that you can translate include Kubuntu and KDE documentation
[17:18] <Quintasan> as well as KDE applications
[17:19] <Quintasan> You can see the current edition of Kubuntu Docs on http://docs.kubuntu.org/
[17:20] <Quintasan> We work on the documentation here http://userbase.kde.org/Kubuntu
[17:20] <Quintasan> That should be pretty straightforward but if there are any questions please ask
[17:22] <Quintasan> KDE specific documentation can be found under http://userbase.kde.org as well as http://techbase.kde.org where the latter is more developer oriented
[17:23] <ovidiu-florin> Regarding translating KDE applications you can see a current status here: http://i18n.kde.org/stats/gui/stable-kde4/team/
[17:24] <ovidiu-florin> and from there you should get in contact with the translators for your language so they can guide you on how to start and how to translate
[17:25] <ovidiu-florin> usualy this involves using Lokalize, but some teams have their own system like Transifex or Pootle
[17:25] <ovidiu-florin> anyway, the main translation files are stored in the KDE SVN
[17:26] <ovidiu-florin> on the same page I just gave, you can find any instructions you may need and contact details
[17:26] <ovidiu-florin> if you need help feel free to ask us as well
[17:27] <Quintasan> Translating KDE applications benefits us indirectly (and also falls into Working upstream category ) since Kubuntu relies heavily on the upstream localization.
[17:27] <Quintasan> Let's move on to testing.
[17:27] <Quintasan> Testing includes:
[17:27] <Quintasan> 1. KDE updates testing
[17:27] <Quintasan> 2. ISO testing
[17:28] <Quintasan> and is relatively simple, in 1. you help us test if our packages are error free so users can seamlessly upgrade to newest KDE SC versions
[17:29] <ovidiu-florin> You get to test/use new versions of KDE software and Ubuntu Software before anyone else, before the new Kubuntu release.
[17:29] <Quintasan> Second thing involves downloading ISOs and installing them either in virtual machines or physical devices to see if the installation process works as one would expect it to
[17:30] <Quintasan> If you want to help us with testing then please hang in #kubuntu-devel, say you'd like to help with testing and we will be sure to tell you when there is anything you can test.
[17:30] <Quintasan> Next on the list is programming
[17:31] <Quintasan> This involves working on Kubuntu-specific applications such as our new shiny driver manager, Ubiquity frontend and some other applications
[17:32] <Quintasan> For reference - Ubiquity is the backend that Ubuntu and flavours use to install Ubuntu
[17:33] <Quintasan> Another thing that you can do is to work directly on KDE SC application
[17:33] <Quintasan> Which yet again benefits us indirectly since better code -> better user experience
[17:34] <Quintasan> Working on the code upstream requires you to have decent knowledge of C++/Qt. But fear not if you don't as there is extensive documentation as well as many tutorial over at TechBase
[17:35] <Quintasan> there is also KDE Dev Guide over at http://flossmanuals.net/kde-guide/ which will introduce you to KDE development
[17:35] <ovidiu-florin> There are also a few KDE applications that use Python
[17:36] <Quintasan> Yeah, I forgot about that
[17:36] <ovidiu-florin> for KDE development you can get all the help on the kde-devel mail list
[17:36] <ovidiu-florin> kde-devel@kde.cor
[17:36] <Quintasan> KDE has bindings for languages such as Python, Ruby etc. so you can write application in those languages
[17:36] <ovidiu-florin> sorry kde-devel@kde.org
[17:37] <ovidiu-florin> and untill you get a developer account you can also help out with other stuff
[17:37] <ovidiu-florin> like bug reporting and triaging
[17:37] <Quintasan> There is also QML which is not only used by Ubuntu ;)
[17:37] <ovidiu-florin> make patches and submit them on the review board
[17:38] <Quintasan> I think that pretty much covers code contributions
[17:39] <ovidiu-florin> http://techbase.kde.org/ tels you all you need to know about this
[17:39] <Quintasan> No questions so far :(
[17:40] <Quintasan> Well, let's move on then
[17:40] <ovidiu-florin> they don't know what their missing
[17:40] <ovidiu-florin> there's blue gold over here
[17:40] <Quintasan> Ah yes, packaging.
[17:41] <Quintasan> Indeed, blue gold over here
[17:41] <ovidiu-florin> this is kind of the core of Kubuntu contributions
[17:41] <Quintasan> A friendly reminder - you can ask questions in #ubuntu-classroom-chat by prefixing with QUESTION:
[17:42] <Quintasan> So back to packaging
[17:42] <Quintasan> In case you don't what packaging is - packaging involves taking software from upstream, writing a set of rules that tells the builders how to build the software and then putting that into Ubuntu repositories
[17:44] <Quintasan> You can start off by picking something maybe from http://kde-apps.org/ that's not yet in the repositories (or maybe the package needs an update) and giving it a go
[17:44] <Quintasan> If you need help then be sure to ask us in #kubuntu-devel
[17:44] <Quintasan> We are really friendly :)
[17:45] <ovidiu-florin> this is pretty chalenging since you have to make sure the package you make will bring in all dependencies
[17:45] <ovidiu-florin> it's pretty easy to miss one
[17:45] <Quintasan> Once you aquire some skill you can join the elite ranks of Kubuntu Ninjas who package the latest and the shiniest releases of KDE SC which end up in tons of computers powered by Kubuntu
[17:46] <ovidiu-florin> also you have to learn a few things about licensing
[17:46] <Quintasan> I didn't joke about the ninjas
[17:46] <ovidiu-florin> and the compatibility between them
[17:46] <Quintasan> as ovidiu-florin there are many things to learn but we are quite happy to guide you.
[17:46] <ovidiu-florin> he's not kidding, the ninjas are real
[17:47] <Quintasan> There is also Project Neon
[17:47] <Quintasan> Project Neon is a set of Launchpad recipes that provides nightly, daily, and weekly build of KDE
[17:48] <Quintasan> PN is aimed at people who run Kubuntu and would like to start contributing back to KDE or just want to test the bleeding edge.
[17:49] <Quintasan> If you'd like to know more then you can find us over at #project-neon as well as #kubuntu-devel
[17:49] <Quintasan> I think that's about it.
[17:50] <Quintasan> ovidiu-florin: anything to add?
[17:50] <ovidiu-florin> one sec
[17:50] <ClassBot> There are 10 minutes remaining in the current session.
[17:51] <ovidiu-florin> how to become a kubuntu member and why to do it.
[17:51] <Quintasan> ovidiu-florin: I mean about packaging :P
[17:51] <ovidiu-florin> oh, I think you've covered it.
[17:51] <Quintasan> Go on then
[17:52] <Quintasan> I think we have website magic and community stuff still left
[17:52] <ovidiu-florin> I'll be short
[17:53] <ovidiu-florin> a Kubuntu member is a contributor to Kubuntu, that (at least) for a period of time brought great contributions to Kubuntu and continues to support Kubuntu one way or another
[17:54] <ovidiu-florin> One great advantage of a Kubuntu member is that they have @kubuntu.org email addresses
[17:54] <Quintasan> Sounds kind of official :P
[17:55] <Quintasan> Well, you get some minor benefits such as Kubuntu email business cards and whatnot
[17:55] <ClassBot> There are 5 minutes remaining in the current session.
[17:55] <Quintasan> but most importantly you become a part of our really nice community
[17:55] <ovidiu-florin> Website magic & community management
[17:56] <Quintasan> and recive your own place in the Hall of Fame
[17:56] <ovidiu-florin> you will get to post stuff on our website, help maintain it and improve it. So a bit of web development
[17:57] <ovidiu-florin> Also, the best thing of them all: You get to promot Kubuntu as a Kubuntu contributor
[17:57] <ovidiu-florin> you get to be a part of the team
[17:57] <ovidiu-florin> and we care ( a lot ) about our team members
[17:57] <ovidiu-florin> you get to travet to Kubuntu meetings
[17:58] <ovidiu-florin> and have fun while doing it :D
[17:58] <Quintasan> That too I guess :D
[17:58] <Quintasan> There is also community management which involves...social media?
[17:58] <Quintasan> and more IRC I guess
[17:59] <ovidiu-florin> yes, of course
[17:59] <Quintasan> Well, I think that's all we could cover in and hour
[17:59] <Quintasan> Be sure to join us at #kubuntu-devel and say hello
[17:59] <ovidiu-florin> we're on Google+ https://plus.google.com/107577785796696065138
[17:59] <Quintasan> Thanks for having us
[18:00] <ovidiu-florin> Thank you
[18:00] <Quintasan> jose: Do we have anyone next?
[18:00] <jose> well, that's myself!
[18:00] <Quintasan> hah
[18:00] <Quintasan> jose: Go on then!
[18:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-classroom.html following the conclusion of the session.
[18:00]  * Quintasan leaves the stage
[18:01] <jose> thanks a bunch, Quintasan and ovidiu-florin for the session about Kubuntu, very interesting!
[18:01] <jose> and well, we're coming near the end of the Open Week!
[18:02] <jose> in case you don't know me, I'm José Antonio Rey, another random community member (who wants to be a unicorn too!)
[18:02] <jose> and part of the LoCo Council
[18:02] <jose> this time I'm going to explain what are LoCo Teams, what they do, and how can you become part of yours!
[18:03] <jose> if you have any questions, make sure to ask them at #ubuntu-classroom-chat, they should start with QUESTION:
[18:04] <jose> let's get rolling!
[18:05] <jose> I'm quite sure you may have wondered if there are any people around your country or city who use Ubuntu like you, or who contribute to Ubuntu
[18:06] <jose> well, we have Ubuntu LoCo Teams
[18:06] <jose> LoCo stands for Local Community, so, they are Ubuntu Local Community Teams
[18:07] <jose> for those speaking Spanish: no, we're not crazy. ok, we might be, but just a little bit
[18:09] <jose> people inside LoCo Teams get together to share experiences, help advocate Ubuntu and, in general, have fun
[18:10] <jose> we have LoCo Teams mostly all around the globe
[18:10] <jose> and you can find yours by going to loco.ubuntu.com
[18:11] <jose> loco.ubuntu.com is a great resource we have, and is often referred to as the LoCo Team Portal
[18:11] <jose> or LTP for short
[18:12] <jose> once you've found your LoCo Team, you will see they have a Launchpad team you can also join, and a mailing list to which you can subscribe!
[18:13] <jose> they should also have an IRC channel, in case you want to live-chat with someone else
[18:14] <jose> make sure to say 'Hi!' once you join, so everyone knows you're around
[18:14] <jose> in the LTP you will be able to find events for your LoCo Team, so if you want to attend *all* details should be listed there
[18:15] <jose> are there any questions so far?
[18:17] <ClassBot> genii asked: What if my area doesn't have a LoCo? Can I start one?
[18:17] <jose> sure thing!
[18:17] <jose> if you don't find a LoCo in your area, and only if you don't fine one it's good to start a new LoCo Team
[18:18]  * jose grabs a link
[18:18] <jose> https://wiki.ubuntu.com/LoCoTeamHowto should contain information about how to start a LoCo team in case there is none in your area
[18:18] <jose> any other questions?
[18:21] <jose> I'll guess we'll move on
[18:21] <jose> oh, question!
[18:21] <ClassBot> genii asked: What role does the #ubuntu-locoteams channel have ?
[18:22] <jose> the #ubuntu-locoteams is a general loco-related support channel, and also a place for contacting the LoCo Council
[18:22] <jose> I'll get to what the LoCo Council is in a bit :)
[18:23] <jose> so, LoCo teams are the ones responsible for advocating Ubuntu in their areas, as I mentioned
[18:23] <jose> for example, they host the awesome release parties!
[18:23] <jose> people just get together and celebrate, they sometimes have cake, pizza and soft drinks
[18:23] <jose> (beer may also be included)
[18:25] <jose> and also host Ubuntu hours
[18:26] <jose> that is, when people just get together for an hour and talk about Ubuntu or even their lives
[18:27] <ClassBot> genii asked: Do you have to be an Ubuntu member before joining a LoCo?
[18:27] <jose> not at all!
[18:27] <jose> anyone can join a LoCo Team!
[18:28] <jose> the only requirement for joining is liking Ubuntu, for sure
[18:28] <jose> if you have a unicorn, I'm sure he'll also be accepted in the team
[18:30] <jose> LoCo teams are also welcome to do any kind of events they like
[18:30] <jose> they can participate in conferences and do lots of things
[18:30] <jose> there's no limit on what a LoCo can do, as long as it follows the CoC
[18:32] <jose> and, as mentioned before, anyone can join, so it's no "programmers only" club, in case you were wonderint
[18:32] <jose> s/wonderint/wondering/
[18:33] <ClassBot> jincreator asked: Can you briefly explain about verified LoCo Team?
[18:33] <jose> good question!
[18:33] <jose> in the community, we have two types of LoCo Teams: LoCo Teams and Verified LoCo Teams
[18:35] <jose> Verified teams have gone through a process where the LoCo Council has checked that they have their stuff set up, and the team contact is contactable
[18:36] <jose> it's a very simple process, in fact
[18:39] <jose> so I think I've mentioned the LoCo Council a couple of times, you may be wondering what it is
[18:42] <jose> the LoCo Council is a group of people elected by the Community Council, which helps the LoCo Teams and empowers them
[18:43] <jose> we are the ones responsible to check and verify teams
[18:43] <jose> as well as helping you if you have a problem with your resources (whichever it may be)
[18:45] <jose> also, if there's a conflict in a LoCo Team, you can contact us and we'll be more than happy to help
[18:47] <jose> to leave some contact details about the LoCo Council
[18:47] <jose> you can reach us by sending us an email to loco-council@lists.ubuntu.com
[18:48] <jose> or if you go to #ubuntu-lococouncil on irc.freenode.net, just say '!lococouncil' without quotes
[18:48] <jose> oh, and we try to constantly post news at lococouncil.ubuntu.com, our blog
[18:50] <ClassBot> There are 10 minutes remaining in the current session.
[18:51] <jose> so, I don't know if you guys have any questions before we wrap up the session
[18:54] <jose> well, I think that will be all for now
[18:54] <jose> if you want to contact us make sure to come by #ubuntu-locoteams or send us an email at loco-council@lists.ubuntu.com, we don't bite :)
[18:55] <ClassBot> There are 5 minutes remaining in the current session.
[18:55] <jose> ooh, question!
[18:56] <ClassBot> jincreator asked: What happens to verified loco team if they didn't apply re-verification process after 2 years?
[18:56] <jose> good point, jincreator!
[18:56] <jose> Verified status lasts for two years, so if the team doesn't apply for re-verification, then they lose their verified status, as well as the privileges it may have
[18:57] <jose> so make sure your team applies in time!
[18:58] <jose> well, I think that's all I can say for this session, if you have any questions just go ahead and ask in #ubuntu-locoteams
[18:58] <jose> you're totally welcome to join
[18:58] <jose> finally, I would like to thank you all for attending this OpenWeek, it's been awesome
[18:59] <jose> we had a great variety of people from many many teams, and I really hope it has served you all in learning something new about the amazing community we have
[18:59] <jose> also thanks to everyone who helped!
[19:00] <jose> and, so we've come to the end. thanks again for attending, and I hope to see you around!
[19:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-classroom.html