[13:02] <sergiusens> Good morning, evening or night depending on where you are
[13:03] <sergiusens> I'm part of the Touch team and thought it would be a good idea to share on how to contribute back to the team
[13:03] <sergiusens> s/team/project/ :-)
[13:03] <sergiusens> The project is sort of diveded on two sides
[13:04] <sergiusens> one is what we based out of Android, which could be considered our HAL
[13:04] <sergiusens> and Ubuntu proper
[13:05] <sergiusens> If anyone has questions please go ahead and ask btw
[13:06] <sergiusens> ok, so we have multiple team working on each side
[13:08] <sergiusens> the Phone Foundations (which I am a part of), works on this android hal and on the general plumbing on the Ubuntu side.
[13:08] <sergiusens> The there's a shell team, a team working on mir, an sdk team and an apps team
[13:08] <sergiusens> working on the higher layers would be just like working on a general Ubuntu system
[13:10] <sergiusens> So I'm going to move on and give an overview on how you would work on the android side
[13:11] <sergiusens> !QUESTION
[13:12] <ClassBot> jsjgruber-l99-p asked: HAL?
[13:12] <sergiusens> HAL as in hardware abstraction layer, we ideally use android just to get to the hardware
[13:13] <ClassBot> SonikkuAmerica asked: Just to be clear, the Ubuntu Touch Android HAL is the ARM core from CyanogenMod 10.1 if I remember correctly?
[13:14] <sergiusens> the android hal is based out of cm-10.1 and all our modifications live here: http://phablet.ubuntu.com/gitweb
[13:14] <sergiusens> under the phablet-10.1 branch
[13:16] <sergiusens> so in general, if you would want to get these sources and build out for one of these systems one would...
[13:17] <sergiusens> repo init -u git://phablet.ubuntu.com/CyanogenMod/android.git -b phablet-10.1
[13:18] <sergiusens> in some directory, then repo sync and wait for a bit
[13:18] <sergiusens> the sync is much faster that pulling plain android since we removed most of the big pieces which are not related to this HAL
[13:20] <sergiusens> once that's done, we need to add two branches that live in bazaar which are the lp:platform-api and lp:phablet-extras/libhybris
[13:21] <sergiusens> whenever you see phablet-extras, it means it's not supposed to live there and in the process or needs to be upstreamed
[13:22] <sergiusens> in a very simple way to say it, hybris would be the gateway to talk to android from ubuntu
[13:22] <sergiusens> after we have all that in, we grab the specifics to a hardware platform
[13:23] <sergiusens> first we would need to source the _android_ build environment -> source build/envsetup.sh
[13:23] <sergiusens> so we can have breakfast
[13:24] <sergiusens> breakfast brings in the hardware specifics... so doing breakfast maguro would bring in the device specific branch and it's dependencies
[13:25] <sergiusens> the dependencies are tracked by cm.dependencies, in the case of maguro http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_device_samsung_maguro.git;a=blob_plain;f=cm.dependencies;hb=refs/heads/phablet-10.1
[13:26] <sergiusens> we support, as in builds, 4 devices, maguro, manta, grouper and mako
[13:26] <sergiusens> but any contribution to another device is welcome
[13:27] <sergiusens> so let me sidetrack a bit...
[13:27] <sergiusens> in some of these dependencies you will see a ref to a kernel repo... these, in the case of these four devices are in the process of being in ubuntu
[13:28] <sergiusens> if you are on saucy you can apt-cache search mako and grouper (and manta iirc) and get them already
[13:28] <sergiusens> and that's done by the kernel team now
[13:29] <sergiusens> after having breakfast, there's one more step, and it's getting the binary blobs... all the device repos have a script that does this for you provided that your device is hooked up
[13:30] <sergiusens> in the case of the nexus devices, they are available to you at https://developers.google.com/android/nexus/drivers
[13:31] <sergiusens> if you are just getting started with a new device, breakfast will get you started and pull in the repos from cyanogenmod directly
[13:32] <sergiusens> these sources after their adaptation are more than welcome to live on phablet.ubuntu.com
[13:33] <sergiusens> if they are, we will setup something so they build weekly/nightly and be ready for use with phablet-flash (for those who don't want to manually do it which is also possible)
[13:34] <sergiusens> it's sort of important to keep the builds in sync on the android and ubuntu side with regards to the platform-api and hybris, since they live on both sides, android_hal and ubuntu
[13:34] <sergiusens> on the ubuntu side, everything is much simpler... or at least there is more expertise from the rest of the team on how to build this part :-)
[13:35] <sergiusens> it's just livebuild, and you can give it a shot if you want
[13:35] <sergiusens> it all lives here lp:touch-preview-images/ubuntu-build-phablet
[13:36] <sergiusens> a tar file comes out of building with that
[13:37] <sergiusens> which is wrapped into a zip file and an edify script that allows to deploy from recovery
[13:37] <sergiusens> there are two reasons to provide this only as an update.zip and not as an .img as we do for the others (which we do both)
[13:38] <sergiusens> one if that not all devices have fastboot and the other is some devices can't fit this in through fastboot due to image size constraints when flashing
[13:39] <sergiusens> if everything were great, we would've probably just gone with a userdata.img from the start that would contain the ubuntu bits
[13:40] <sergiusens> if you are in anyway interested in tinkering on this side, I recommend joining #ubuntu-touch
[13:40] <sergiusens> so if there aren't any question regarding this topic, I'm going to do a 180
[13:41] <sergiusens> and move on to a different topic
[13:41] <sergiusens> still Touch related though :-)
[13:42] <sergiusens> ok, another side of things is testing
[13:43] <sergiusens> there's a manual side and an automated side
[13:44] <sergiusens> the manual side is the easiest to explain so I'll touch base on that... there's a simple suite of tests that we run that lives in http://iso.qa.ubuntu.com
[13:44] <sergiusens> you can look for them under the Product (Ubuntu Touch) labels
[13:44] <sergiusens> i.e., for manta: http://iso.qa.ubuntu.com/qatracker/milestones/270/builds/44685/testcases
[13:45] <sergiusens> anyone can run a cycle against the current build that lives on cdimage
[13:46] <sergiusens> regarding the apps and shell, every MR gets (or should get) to run autopilot tests among others before a merge is accepted on jenkins
[13:47] <sergiusens> it doesn't capture all the issues or prevent some broken packages, but it does catch most
[13:47] <sergiusens> the unit tests and all other tests for those packages are also run
[13:48] <sergiusens> if you are looking into automated testing with autopilot, I recommend branching one of the projects and to look into the tests/autopilot subdirectory
[13:48] <sergiusens> and that's all I'm going to say with regards to that due to time
[13:49] <sergiusens> last but not least comes image testing
[13:49] <sergiusens> we used to have a suite that ran and accepted an image that has got a bit behind it's usefulness, so this cycle we are going to be working and refocusing on it
[13:50] <sergiusens> in the end, we want to have a sort of rolling release during development where no regressions occur... it's a big goal, hard to reach, but that's where the focus is
[13:50] <ClassBot> There are 10 minutes remaining in the current session.
[13:51] <sergiusens> so cdimage would build the build and land it in /pending, uexposed to users
[13:51] <sergiusens> our jenkins instance will catch it and run suites against it and determine it's stability on the 4 platforms... if a test fails, we fix and reiterate
[13:52] <sergiusens> if it passes it gets moved to current for all others to grab
[13:52] <sergiusens> Given the session is about to end, I'll ask, are there any questions?
[13:55] <sergiusens> ok, that's a wrap
[13:55] <sergiusens> have a nice day!
[13:55] <ClassBot> There are 5 minutes remaining in the current session.
[14:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/05/21/%23ubuntu-classroom.html following the conclusion of the session.
[14:02] <phillw> good morning / afternnon or evening!
[14:02] <phillw> I'm the team leader for testing in lubuntu.
[14:03] <phillw> Firstly, what is lubuntu? Lubuntu is a low resource member of the ubuntu family based on lxde
[14:04] <phillw> it continues to go from strength to strength thanks to the hard work of all the team and feed back from users, who rapidly become involved in testing :)
[14:04] <phillw> The is a set of slides showing what lubuntu looks like at http://lubuntu.net/
[14:05] <phillw> for anyone curious as to what it looks like.
[14:06] <phillw> it has been decided that the major development work for this cycle will be set the foundation for our first LTS release in 14.04
[14:07] <phillw> the recent vUDS meeting can be viewed at http://youtu.be/qfy_GxKHL0M at your leisure.
[14:08] <phillw> So, how can people help out?
[14:08] <phillw> A great place to start looking is at https://wiki.ubuntu.com/Lubuntu/GettingInvolved
[14:09] <phillw> we always need people in all the teams, being new to the areas that interest you is not a bar to joining and getting used to how things are done.
[14:10] <phillw> As nicholas is going to be running a session on QA / Testing a little later I'll briefly touch on testing, as any one can help test :)
[14:11] <phillw> if you want some back ground on testing the images (ISO's) then head over to https://wiki.ubuntu.com/Lubuntu/Testing for background information on what the various terms that are used mean
[14:12] <phillw> another important area that needs contributers is documentation. It is hoped to have 'off-line' documentation available for 14.04 (with hopefully a draft version on 13.10)
[14:13] <phillw> we are also re-vamping the wiki area and looking into making a lubuntu manual.
[14:14] <phillw> head over to https://wiki.ubuntu.com/Lubuntu/DocumentationTeam if you are interested in helping out and make your-selves known!
[14:15] <phillw> as you can see from https://wiki.ubuntu.com/Lubuntu/GettingInvolved most of the teams have their own mailing lists so that they can discuss things. These are really handy as we are split across all sorts of time-zones :)
[14:16] <ClassBot> SonikkuAmerica asked: When you say "setting the foundation," does that mean that 14.04 LTS will only be a maintenance release built on 13.10?
[14:17] <phillw> SonikkuAmerica: no, it means that 13.10 may be a little rough round the edges. There are various development issues that are being worked on, not all of them may make the cut off for 13.10
[14:17] <ClassBot> TheLordOfTime asked: What do you mean by "offline documentation"?
[14:18] <phillw> off-line documentation means that the installation media itself will have help files on it, which will be installed and able to be viewed without internet access
[14:19] <phillw> no more getting told to look up on the internet how to find out solutions as to why your internet isn't working :)
[14:21] <phillw> the lubuntu manual will be a downloadable file that you can then view off-line or print for reference.
[14:22] <phillw> the off-line area will be using Mallard, the documentation on using mallard is currently being updated, so we're not sure how complete it will be for 13.10
[14:24] <phillw> are there any questions people have? I've just briefly covered where we are, where we are heading and how to assist.
[14:25] <phillw> rtfm = read the 'friendly' manual :)
[14:27] <phillw> the pre-alphas of lubuntu are now available via the iso-tracker http://iso.qa.ubuntu.com/qatracker/milestones/243/builds
[14:29] <phillw> Not wishing to steal any of Nicholas's presentation, the QA team have held already some classroom sessions https://wiki.ubuntu.com/Testing/Activities/Classroom and are planning some more to update things that have changed.
[14:30] <ClassBot> SonikkuAmerica asked: I VBox'ed 13.04 and saw a couple of new session options (LX Games and Lubuntu Nexus 7 Session). Can you tell us a little about those without cutting into another topic?
[14:31] <phillw> SonikkuAmerica: I don't have any information to hand on those. It is probably best to ask on the general mailing list. I'm sure someone will give you (and me) details :)
[14:32] <phillw> for games, we are most likely dropping the 'ace of penguins' suite and having just one, fairly decent, game.
[14:35] <phillw> having had a quick google, adding nexus 7 is something that the developers would have to implement, I am unaware of any discussions on the subject so far but did find this.... http://imagebin.org/258276
[14:36] <phillw> we did have a netbook option previously, but as to what is planned for 13.10 / 14.04 I do not know.
[14:37] <phillw> any other questions?
[14:40] <phillw> if there are no further questions, that about wraps things up. Thanks for attending and for the questions!
[14:50] <ClassBot> There are 10 minutes remaining in the current session.
[14:55] <ClassBot> There are 5 minutes remaining in the current session.
[15:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/05/21/%23ubuntu-classroom.html following the conclusion of the session.
[15:01] <coolbhavi> Hello all
[15:01] <coolbhavi> :-)
[15:02] <coolbhavi> and welcome to my session on loco teams in ubuntu
[15:02] <coolbhavi> I am Bhavani shankar a ubuntu developer and I will be representing the LoCo council in ubuntu today
[15:03] <coolbhavi> taking all your questions related to Loco teams and their working in ubuntu
[15:05] <coolbhavi> So basically this is intended to be a q n a session where you can ask any questions related to how is the loco team infrastructure made up and how loco teams work in ubuntu
[15:05] <coolbhavi> so any questions are welcome :)
[15:07] <coolbhavi> so assuming there are no questions as of now let me move on
[15:07] <coolbhavi> so who are we the LoCo council in ubuntu and what we do?
[15:08] <coolbhavi> In ubuntu we are a team of 6 members who take care of the governance of loco teams in ubuntu
[15:09] <coolbhavi> and provide the loco teams with whatever support is required in terms of infrastructure
[15:10] <coolbhavi> so in short we take care to see that the loco teams are running smoothly at any given point of time
[15:12] <coolbhavi> https://wiki.ubuntu.com/LoCoCouncil page describes our duties related to local communities (LoCo's) in ubuntu
[15:12] <coolbhavi> (as I said earlier, any questions are welcome at any point of time)
[15:14] <coolbhavi> So moving on, how to setup a loco team in ubuntu?
[15:17] <coolbhavi> setting up a loco team is fairly simple: First decide which region you want to create a team for and then search the loco directory (loco.ubuntu.com) for any loco presence in your area and if not you could go ahead and create one
[15:18] <coolbhavi> https://wiki.ubuntu.com/LoCoTeamHowto page comes in handy while doing so
[15:19] <coolbhavi> Ok, Now I have a existing loco team in the area and I want to contribute, so how to join?
[15:21] <coolbhavi> Simple again just browse the loco directory at loco.ubuntu.com and select a region of your choice and join a loco team in your area and start contributing :-)
[15:21] <ClassBot> kotux asked: In the Los Angeles region, there is a Pasadena LoCo. Would it be ok to start a LoCo in Los Angeles too?  (The cities are not too far apart.)
[15:23] <coolbhavi> kotux, A good question, if the cities are not far apart you can be better off I think contributing to the existing loco than creating one yourself
[15:23] <coolbhavi> in  your area
[15:24] <coolbhavi> alright, lets move on
[15:24] <coolbhavi> ok so I have joined or created a loco team, whats next?
[15:25] <coolbhavi> You can contribute in a variety of ways in your loco team
[15:27] <coolbhavi> like spreading the word about ubuntu(not to be confused with marketing) or running installfests or bug jams and global jams and so on
[15:27] <coolbhavi> Any questions till now?
[15:29] <ClassBot> fkol_k4 asked: What is the benefit of contributing via a LocCo team instead of doing this on one's own initiative? In what ways does Ubuntu backs LoCo teams?
[15:30] <coolbhavi> fkol_k4, I am coming to that in the next part :-)
[15:31] <coolbhavi> so I have joined a loco team.. What are the benefits my team gets
[15:31] <coolbhavi> ?
[15:32] <coolbhavi> there is a procedure called the loco teams approval procedure which is done by the Loco council every 2 years
[15:32] <coolbhavi> welcome to SergioMeneses btw :-)
[15:34] <coolbhavi> so once we verify and approve the loco team operations, the team will be given a approved/verified team status in ubuntu
[15:35] <coolbhavi> so how to get your team operations verified and whats the benefit?
[15:36] <ClassBot> fkol_k4 asked: in the 2013 UDS it was announced by Jono Bacon that LoCo approval will be deprecated.
[15:36] <coolbhavi> fkol_k4, thats something we are contemplating on as yet
[15:37] <coolbhavi> and going forward we will only verify the operations I guess as we are thinking to extend the support to teams in larger cities too..
[15:38] <coolbhavi> so its work in progress :-)
[15:38] <coolbhavi> so moving ahead..
[15:39] <coolbhavi> what is the loco team approval procedure and what are its benefits?
[15:41] <coolbhavi> once a loco team deems to be active for some part of time they can apply for approval and general guidelines are given in this wiki page: https://wiki.ubuntu.com/LoCoCouncil/TeamApprovalGuidelines
[15:44] <coolbhavi> once the team gets approved the team would be given conference packs pressed cd's via shipit primarily for distribution in the loco and in conferences
[15:44] <coolbhavi> SergioMeneses, any other goodies you can specify here :-)
[15:45] <ClassBot> SonikkuAmericaX asked: Due to the announcement that pressed discs of the latest versions will no longer be available, will LTS releases still be pressed and sent to LoCo teams upon request?
[15:46] <coolbhavi> SonikkuAmericaX, yes
[15:48] <SergioMeneses> There are teams that are not approved, but that does not mean they can not receive conference packs or resources
[15:48] <SergioMeneses> as you can see in this wikipage https://wiki.ubuntu.com/UbuntuAtConferences
[15:48]  * SergioMeneses gives the word to coolbhavi 
[15:49] <coolbhavi> only thing is you ll receive a scaled down version :-)
[15:50] <ClassBot> There are 10 minutes remaining in the current session.
[15:51] <coolbhavi> Last but not the least: to make your loco team experience easier in ubuntu jono has put all the things together and come up with a kit called ubuntu advocacy kit (uak)
[15:53] <coolbhavi> you can see the project page here: https://launchpad.net/uak
[15:54] <coolbhavi> and download the latest package from here and install: https://launchpad.net/~uak-admins/+archive/uak
[15:55] <coolbhavi> its a offine reference which runs from your pc and anyone is welcome to contribute :-)
[15:55] <ClassBot> NikTh asked: How many Loco contacts can exist in a Loco team ? One , two , or more ?
[15:55] <ClassBot> There are 5 minutes remaining in the current session.
[15:56] <coolbhavi> NikTh, any number can be more than one unless any conflicts doesnt arise within the team
[15:56] <coolbhavi> :-)
[15:56] <SergioMeneses> NikTh, there is a figure called: Councils - a group of administrators
[15:57] <coolbhavi> the floor is open for any questions as we wind up :-)
[15:58] <SergioMeneses> NikTh, if you LoCo team is big maybe you will need more contacts
[15:58] <coolbhavi> for any queries you can write to us at loco-council at lists.ubuntu.com
[15:58] <SergioMeneses> sure! any question please let us know :D
[15:59] <coolbhavi> thanks SergioMeneses
[15:59] <coolbhavi> :-)
[15:59] <SergioMeneses> ok guys, it was a pleasure to be part of this amazing event! :D enjoy it :)
[16:00] <coolbhavi> and thanks all of you for attending our session :-)
[16:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/05/21/%23ubuntu-classroom.html following the conclusion of the session.
[16:01] <balloons> Hello and welcome to the ubuntu quality team session. My name is Nicholas Skaggs and I'm the QA Community Coordinator. Thanks for attending (or reading this log later!)!
[16:02] <balloons> This session is intended to introduce you to what the quality team does, some of the sites and tools utilized by the team, as well as how you can join and participate.
[16:02] <balloons> You may ask questions at any point.. Just be sure to utilize the #ubuntu-classroom-chat channel. Prefix your question with QUESTION: to ensure I see it.
[16:02] <balloons> Everyone ready?
[16:03] <balloons> So first I'm going to give a brief overview of what QA is and how the team works, then I'll dive into the activities we do during the cycle. Along the way, we'll talk about the tools we use as well. Finally, we'll talk about how you can get involved and then do a Q & A.
[16:03] <balloons> So to start off, let’s take a look at the wiki page for the team
[16:03] <balloons> http://wiki.ubuntu.com/QATeam
[16:04] <balloons> On the page you can see some of the teams goals and purpose
[16:04] <balloons> Simply put, we help ensure everyone's work in ubuntu is presented in the best possible way
[16:05] <balloons> From designing good process, to testing, to making sure things 'just work', we want the culmination of work that results in the ubuntu image to be the best it can be
[16:05] <balloons> So where do we hang out?
[16:05] <balloons> Many different places actually :-)
[16:05] <balloons> right here on IRC, #ubuntu-quality
[16:05] <balloons> on our mailing list:     https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[16:05] <balloons> in the forums;     http://ubuntuforums.org/forumdisplay.php?f=427
[16:05] <balloons> on askubuntu;     http://askubuntu.com/questions/tagged/quality
[16:06] <balloons> and even on social sites like facebook; https://www.facebook.com/groups/UbuntuQA/
[16:06] <balloons> twitter; https://twitter.com/ubuntutesting
[16:06] <balloons> and google+; https://plus.google.com/b/108452779163647535106/108452779163647535106/
[16:06] <balloons> So, what do we do exactly?
[16:06] <balloons> During the course of the cycle, we as a team participate by providing test results for the packages as they are undergoing development. If we find a bug, we'll also report and file it.
[16:07] <balloons> In addition, we develop testcases, best practices and even tools to help us test more effectively
[16:07] <balloons> Our testing is done via several avenues. I'll describe each briefly.
[16:07] <balloons> The frst is cadence testing, https://wiki.ubuntu.com/Testing/Cadence.
[16:08] <balloons> Cadence testing is simply the term we use to describe that we test at regular intervals.
[16:08] <balloons> In practice, this amounts to us testing every 2 weeks during the cycle -- we test images, packages and and hardware.
[16:08] <balloons> The second is smoke testing, or dogfooding as some would call it, the development version of ubuntu.
[16:09] <balloons> This means simply installing or upgrading to the development release and using it as a regular machine. By attempting to work and perform tasks under the development version you may encounter a bug.
[16:10] <balloons> Your usage of the development version represents a broad and unique testcase
[16:10] <balloons> The third is a call for testing. This is a call to test a specific piece of software, with an accompanying set of tests and instructions for testing.
[16:10] <balloons> This call could happen at anytime throughout the cycle, and is utilized by developers to help ensure the software they are landing in the development version is ready for general consumption.
[16:11] <balloons> So, how do we coordinate all of these different avenues for testing? The answer is the QATracker
[16:11] <balloons> https://wiki.ubuntu.com/Testing/QATracker
[16:12] <balloons> The tracker is where we submit the test results and get information needed to complete the test, such as the testcase and installation instructions.
[16:12] <balloons> There are actually several qatracker instances each geared towards testing different things
[16:13] <balloons> http://iso.qa.ubuntu.com is used to report results for image testing
[16:13] <balloons> http://packages.qa.ubuntu.com is used to report results for package testing
[16:13] <balloons> http://laptop.qa.ubuntu.com is used for laptop/hardware testing
[16:13] <balloons> The tracker helps us work together as a team to perform these testing activities. The wiki page has more details about how it works and provides links to walkthroughs to help you get started submitting results.
[16:14] <balloons> So we've talked about test results and some of the testing our team does. But there is another way to participate in the team
[16:15] <balloons> Namely, helping create the testcases we use
[16:15] <balloons> You can contribute both manual and automated testcases to ubuntu.
[16:15] <balloons> Manual testcases are intended to be run by us, humans :-), while the automated testcases can be run by a machine.
[16:16] <balloons> As a team, we maintain two projects the Ubuntu Manual Tests (https://launchpad.net/ubuntu-manual-tests/) and the Ubuntu Autopilot Tests (https://launchpad.net/ubuntu-autopilot-tests/) projects.
[16:17] <balloons> The Ubuntu Manual Tests project holds all of our manual test results. Everything you see on the various qatrackers like iso.qa.ubuntu.com is held in the source code repository.
[16:17] <balloons> The testcases are written in plain english, with a simple html syntax. You can see the format for our testcases here https://wiki.ubuntu.com/Testing/TestCaseFormat.
[16:18] <balloons> Anyone can contribute a manual testcase to the project and we welcome contributions :-)
[16:19] <balloons> Both of the projects utilize a 'TODO' bug tag for work and testcases that need to be done
[16:20] <balloons> I'll describe more about how to get involved in any of these activities in just a moment
[16:20] <balloons> Now if your interested in automated testing, check out the ubuntu autopilot tests project
[16:21] <balloons> The Ubuntu Autopilot Tests project holds the autopilot testcases for ubuntu. Autopilot (https://launchpad.net/autopilot) is a tool that allows us to write functional gui testcases
[16:22] <balloons> he goals of the project are twofold; Automate iso testing installation via ubiquity and write a set of automated tests for every default desktop application in ubuntu.
[16:22] <balloons>  Both of these goals are intended to augment manual testing and provide a nice set of regression tests that can be run everyday against the newly built image.
[16:23] <balloons> So we spoke about the qatracker, where our manual test results are reported. So where does the automated test results lie?
[16:24] <balloons> the answer is the QA dashboard (http://reports.qa.ubuntu.com/)
[16:24] <balloons> https://jenkins.qa.ubuntu.com/ is the raw jenkins output that is utilized to generate the nice graphs and views on the QA dashboard
[16:24] <balloons> On the smoke testing page you can see the automated testing results for our daily images. Images are not published for manual testing until they meet a baseline criteria for installation via automated testing -- this helps us focus our testing efforts :-)
[16:25] <balloons> So, that was a quick runthrough of many different things. In a nutshell we spoke about contributing test results and contributing testcases
[16:26] <balloons> If your interested in contributing, there is some great documentation on our wiki, and even video walkthroughs on youtube.
[16:26] <balloons> Check out https://wiki.ubuntu.com/Testing/Activities and https://www.youtube.com/qualitybecomesyou for more information.
[16:27] <balloons> Specifically for contributing test results, there are walkthroughs at the bottom of the QATracker page https://wiki.ubuntu.com/Testing/QATracker
[16:27] <balloons> For contributing testcases check out: https://wiki.ubuntu.com/QATeam/ContributingTestcases
[16:27] <balloons> In addition, we also host hackathons where we hack on our testcases
[16:28] <balloons> We are currently scheduling hackfests for the saucy cycle https://wiki.ubuntu.com/QATeam/Hackfest
[16:28] <balloons> hackfests are a great way to get started contributing -- people are around to help you and review your contributions
[16:29] <balloons> So, let's field some questions now
[16:29] <balloons> Skini151 asks, QUESTION: How new package format will influence the QA in future?
[16:31] <balloons> I assume you are referring to the click packages. click packages should't change anything for us in the future. They may require more testing if the packages are intended to be run across more devices distros, etc.
[16:31] <balloons> However, we as a team are ultimately testing the package and in general aren't concerned with how it's delivered
[16:32] <balloons> That said, we might be a part of doing testing specifically to ensure the click packages work properly :-)
[16:33] <balloons> Feel free to ask any other questions you might have, I'll continue
[16:35] <balloons> So we've talked a little about the team and given you an introduction to what we do
[16:35] <balloons> Hopefully we've whet your appetite a little, and you are curious to learn more
[16:35] <balloons> Getting involved in quality is a great way to start contributing to ubuntu
[16:36] <balloons> We interact with many different teams and people.
[16:36] <balloons> The work is diverse, and the skillsets required are too. There's room for you on the team!
[16:37] <balloons> Are a technical person? Do you like to code?
[16:37] <balloons> or perhaps your just wanting to learn a little python?
[16:38] <balloons> You could consider writing some automated testcases using autopilot and contributing them to the ubuntu-autopilot-tests project
[16:38] <balloons> you could also work on some of the tools we use, such as testdrive; https://launchpad.net/testdrive
[16:39] <balloons> Perhaps you enjoy writing, or are skilled with explaining things step by step
[16:39] <balloons> we need your skills in our ubuntu-manual-tests project!
[16:40] <balloons> Maybe you just like breaking things, or running bleeding edge software -- contributing test results is right up your alley!
[16:41] <balloons> Even if your not running ubuntu, but a flavor instead, we still need and welcome contributions in all of the above areas. We share many things like testcases and tools across the ubuntu family
[16:42] <balloons> Vasudevan_ asks QUESTION:  When  is the autopilot session planned ? I am running into issues with the existing scripts on autopilot 1.3
[16:43] <balloons> Good question. We should have a hackathon very soon; however, please don't struggle and wait alone. We're happy to help and chat about testing anytime in #ubuntu-quality and for autopilot specifically #ubuntu-autopilot if autopilot isn't playing nice
[16:43] <balloons> watch the mailing list for the announcement
[16:43] <balloons> of the day/time for the hackfest
[16:44] <balloons> Skini151 asks, QUESTION: Where QA Team pay more attention at testing process? (sorry for my bad english).
[16:45] <balloons> Skini151 explains that he is asking how we determine what to test as a quality team
[16:46] <balloons> Very good question! In the past we've centered our efforts around a couple things. The first was new development we knew was landing in the release. For example, a new version of unity.
[16:46] <balloons> The second is tried to look at things like errors.ubuntu.com and launchpad bugs, as well as feedback from our group on what's broken and what needs attention and then schedule some testing around it
[16:47] <balloons> This cycle we actually have a blueprint for making this even clearer on the dashboard
[16:47] <balloons> https://blueprints.launchpad.net/ubuntu/+spec/qa-s-dashboard
[16:48] <balloons> There's alot in there, but specific to what I'm talking about is called KPI, or Key performance indicators. We'll be talking about this more during the cycle
[16:48] <balloons> Essentially the dashboard will attempt to give a concise view of the state of quality in ubuntu at any given time.
[16:48] <balloons> Any other questions?
[16:49] <balloons> I hope I've enticed you to join us in our quality endeavors :-). Let me share with you the next steps for joining the team and being more involved
[16:49] <balloons> The steps for joining the team are quite simple. It's an open membership. You simply need a ubuntu SSO account
[16:49] <balloons> https://login.launchpad.net/+new_account, if you don't have one
[16:49] <balloons> That will allow you to contribute results to the tracker. In addition you should join our launchpad team and mailing list.. And then leave us a message and say hello! We're happy to help you get started and guide you through an area you'd like to help in
[16:49] <balloons> LP team: https://launchpad.net/~ubuntu-testing
[16:49] <balloons> mailing list:  https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[16:50] <balloons> The mailing list will keep you informed about testing events we are having, new initiatives, and allow you to ask questions and get help
[16:50] <balloons> Finally, our #ubuntu-quality channel has folks from around the world hanging out at many different hours of the day.. Do stop by and say hello or ask questions anytime
[16:51] <ClassBot> There are 10 minutes remaining in the current session.
[16:53] <balloons> ok, if there's no more questions, this will be the official end of the session :-)
[16:54] <balloons> I'd like to thank everyone for coming out or reading the log later :-)
[16:54] <balloons> Also, I'd like to remind you that we as a quality team will be hosting more classroom sessions on specific topics next month for new comers to ubuntu quality
[16:55] <balloons> Things like how to test images, how to file bugs, using vm's, etc, etc
[16:55] <balloons> Watch the classroom announcement space as well as our social media and mailing lists for the specific dates and events
[16:55] <balloons> Thanks everyone!
[16:55] <ClassBot> There are 5 minutes remaining in the current session.
[17:01] <pleia2> Hi everyone, welcome to the Ubuntu Open Week session about the Ubuntu Women Project!
[17:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/05/21/%23ubuntu-classroom.html following the conclusion of the session.
[17:01] <pleia2> My name is Elizabeth Krumbach Joseph. I currently work for HP and am tasked with working on the OpenStack Infrastructure team
[17:01] <pleia2> Here in the Ubuntu world, among other things, I'm a member of the Ubuntu Community Council and one the quartet of leaders for the Ubuntu Women project along with Cheri Francis, Flavia Weisghizzi and Silvia Bindelli
[17:02] <pleia2> The Ubuntu Women project was started in 2005 and formalized in 2006 (around when I got involved) by folks who were interested in helping to get more women using and contributing to Ubuntu
[17:02] <pleia2> Continuing efforts have been spurred on by continued gender imbalance in open source, so loosely we work to:
[17:02] <pleia2>  - reach out to women in our community or interested in joining and offer help to get involved
[17:03] <pleia2>  - give suggestions to current community members about how they can encourage higher female participation (or, at the very least, not actively drive them away)
[17:03] <pleia2>  - work on programs to raise the profile of potential role models already within our community (having role models has proven to be a very important part of increasing involvement)
[17:03] <pleia2>  - provide a safe environment where people can feel free to discuss problems or concerns they have about the community related to gender issues
[17:04] <pleia2> We're happy to say that when we were last tracking it, we were showing 5% of Ubuntu Members as women, which is higher than the general open source world where statistics range from 1-4%
[17:04] <pleia2> but obviously 5% isn't great either :) we want a lot more women joining Ubuntu and technology in general, so our efforts continue
[17:05] <pleia2> oh, and if anyone has any questions, please speak up at any time, in #ubuntu-classroom-chat you can do a question like:
[17:05] <pleia2> QUESTION: Do you like penguins?
[17:06] <pleia2> and I'll be able to pull it over here via classbot to answer it
[17:06] <ClassBot> dee asked: Are there country specific Ubuntu Women projects? Background: I do not see that much projects in Germany even if I'm part of the German LoCo. (But maybe I do not look hard enough.) So how do you reach women in non English speaking countries?
[17:06] <pleia2> great question, dee!
[17:06] <pleia2> currently there are only a couple
[17:07] <pleia2> there is a very active team in Italy that Flavia and Silvia participated in for Italian speakers
[17:07] <pleia2> http://wiki.ubuntu-it.org/GruppoPromozione/UbuntuWomen
[17:07] <pleia2> there is also an effort in Hungrary: http://women.ubuntu.hu/
[17:08] <pleia2> unfortunately nothing in germany right now, but these are all led by women in our community who stepped up to run something, it's not something we centrally organize
[17:08] <pleia2> so if someone in another country wants to start something for their region + language - please do! and let us know :)
[17:10] <pleia2> now, before I get into talking about some of our current projects, I have 2 things this session is not about, but may be useful resources for those interested
[17:10] <pleia2> 1. I won't be justifying the existence of the Ubuntu Women Project or explaining basic feminism topics
[17:10] <pleia2> This is open source! Members of the project feel it is valuable and wish to spend their time on it, if you aren't interested in the project please join us! and if not, work on something else :)
[17:11] <pleia2> If you are interested in the language of feminism, particularly as it relates to open source communities, to understand why we do what we do, I recommend starting with: http://geekfeminism.wikia.com/wiki/Feminism_101
[17:11] <pleia2> err, aren't/are
[17:11] <pleia2> 2. I won't be rehashing the challenges that many women face in open source, tech or geek communities in general, or incidents that have occurred, it's not constructive for this space and these are already well-documented in many places, including:
[17:12] <pleia2> http://geekfeminism.wikia.com/wiki/Category:Issues
[17:12] <pleia2> http://geekfeminism.wikia.com/wiki/Timeline_of_incidents
[17:12] <pleia2> Now, recent projects and plans for the future!
[17:12] <pleia2> At the Ubuntu Developer Summit in Copenhagen for the Raring cycle we put together a blueprint outlining some of our goals:
[17:12] <pleia2> https://blueprints.launchpad.net/ubuntu-women.org/+spec/community-r-ubuntu-women-project-goals
[17:13] <pleia2> Some of what we got accomplished on that list was work by Emma Marshall to start doing follow-up interviews of women who are working in Ubuntu and to seek out new ones
[17:13] <pleia2> She was able to complete 3 of these, you can see her posts over on http://blog.ubuntu-women.org/
[17:13] <pleia2> and I have another email in my inbox from her about another :)
[17:14] <pleia2> related to dee's question, Flavia and Silvia also took time to share some of the history and tips from the Italian chapter of Ubuntu Women, details here: http://blog.ubuntu-women.org/2013/02/irc-presentation-of-ubuntuwomen-it-summary/
[17:14] <pleia2> so this may be helpful to other regional chapters looking to get started
[17:15] <pleia2> (of course we always encourage folks to join their LoCo team first!)
[17:15] <pleia2> We also began brainstorming for some kind of competition that the team would run, since participation in these in the past has been high and has done a great job of raising interest in the project, which will happen this cycle
[17:15] <pleia2> So this cycle we met at a virtual Ubuntu Developer Summit to discuss more plans
[17:16] <pleia2> Blueprint here: https://blueprints.launchpad.net/ubuntu-women.org/+spec/community-1305-ubuntu-women
[17:16] <pleia2> And since it was virtual, we have a video from the google hangout: http://www.youtube.com/watch?v=7Uw9ipsmXkM
[17:17] <pleia2> We'll be continuing work on the competition. Penelope Stowe and Cheri have come up with an idea to do a sort of online scavenger hunt for trivia questions related to women in tech and/or Ubuntu
[17:17] <pleia2> The plans is also to also continue to write articles for an Ubuntu Women column in Full Circle Magazine (see: http://wiki.ubuntu-women.org/FullCircleMagazine), we've been unable to do that lately due to lack of time/availability
[17:18] <pleia2> If anyone is interested in helping you can see that wiki page get some idea of what we've written in the past, who we've interviewed and if you're interested in writing something there is also some information about the basics of what we're looking for and some style guidelines
[17:18] <pleia2> I proof read all articles passed along to the magazine, so don't be shy about providing ideas or even articles :)
[17:19] <pleia2> We're also going to continue Career Days sessions that Cheri launched: http://wiki.ubuntu-women.org/CareerDays
[17:19] <pleia2> These are IRC-based sessions intended to expose women to careers related to technology, Ubuntu and open source
[17:20] <pleia2> And while we welcome anyone to give these sessions, when women give them it's also a great opportunity to show off the work of these successful female role models to inspire others
[17:20] <pleia2> please let us know if you're interested in this project :)
[17:20] <pleia2> Finally, we're also going to be putting together some questions for a general poll of our community to find out what people want and expect out of the project
[17:21] <pleia2> I'm really excited about this one as I find that our project needs a bit of a "tune up" every couple of years to readjust to our changing project and audience
[17:21] <pleia2> having feedback is really important so we can make sure we're spending our time in the right place and redirect efforts as needed
[17:21] <pleia2> related to this, we're seeking to connect more with other women in tech groups, reaching out online about possible collaborations and ways we can help each other
[17:22] <pleia2> perhaps sending the survey their way, then publishing the anonymous results so everyone in our communities can take advantage of the data
[17:23] <pleia2> we'll also be seeing how our own mission and theirs sync to find other ways to collaborate
[17:23] <pleia2> Personally I'll be attending Ada Camp in San Francisco in a few weeks and hope to reach out to some folks there http://sf.adacamp.org/
[17:24] <pleia2> if 30 minute time slots existed for open week, I would have taken one of those :) that's all I've got!
[17:24] <pleia2> questions?
[17:24] <pleia2> (ask in #ubuntu-classroom-chat)
[17:30] <ClassBot> dee asked: I know there is nothing in Germany but maybe you know an German female Ubuntu member that wants to talk on German Ubucon in October. There is still time to find someone about your project there. :)
[17:31] <pleia2> off the top of my head I can't think of one, but I'll ask around, mind if I send your request to the ubuntu-women mailing list?
[17:31] <pleia2> thanks dee!
[17:50] <ClassBot> There are 10 minutes remaining in the current session.
[17:55] <ClassBot> There are 5 minutes remaining in the current session.
[18:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2013/05/21/%23ubuntu-classroom.html
[18:01] <pleia2> thanks everyone!