=== chin is now known as Guest36963 === sjokkis_ is now known as sjokkis === jasono_ is now known as jasono [04:21] when is next lecture going to start and what will be the topic? [04:27] changed_nick, https://wiki.ubuntu.com/UbuntuDeveloperWeek [04:28] changed_nick, go to that url ,you will got all the details regarding the classs.... [04:49] chandan_kumar: thank you :) [04:53] changed_nick, yours welcome. === qwebirc73447 is now known as geco2 === head_v is now known as head_victim === angeldaker is now known as daker [13:11] what is the time for developer week today? [13:12] raki_: http://is.gd/8rtIi [13:14] thank you!! [13:18] are there any logs forthe previous days [13:18] Maybe https://wiki.ubuntu.com/Classroom has link. [13:19] There should be logs. [13:19] raki_: https://wiki.ubuntu.com/Classroom#Logs/Transcripts [13:24] wiki.ubuntu.com/UbuntuDeveloperWeek has links to logs (just yesterday's are in progress but will be up in about 5 minutes as long as the wiki cooperates with me) [13:34] all the logs from Developer Week so far are now up at https://wiki.ubuntu.com/UbuntuDeveloperWeek/ [15:06] please guide me how to use this channel?someone told me this is best place to learn about linux... [15:20] Fvic: https://wiki.ubuntu.com/Classroom [15:54] which session today ? [15:55] HELLO MY FRIENDS! WELCOME TO DAY 4 of UBUNTU DEVELOPER WEEK! [15:56] if you need any information at all (which sessions, etc.) head to: https://wiki.ubuntu.com/UbuntuDeveloperWeek [15:56] also... if you haven't joined #ubuntu-classroom-chat yet, you might want to do that now [15:56] because that's where we chat and ask questions [15:56] if you have questions, please ask - we want our sessions to be as interactive as possible [15:57] if you do ask, please make sure you prefix your question with QUESTION: [15:57] ie: QUESTION: Which language should become default language of Ubuntu? [15:58] The first session of the day is lead by an awesome guy, a friend and colleague of mine, who probably has an opinionated answer to the last question [15:58] it's David Planella, Mr. dpm [15:58] who is going to talk about hooking up your application with Launchpad Translations [15:59] dpm, you still have a few minutes until you get started :) [15:59] have a great day 4 every one - enjoy the sessions! [16:00] Thanks dholbach, I've got the right answer to that question, but we'll leave it for another full session :) [16:00] of course you do :) [16:00] enjoy! [16:00] ;) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Integrating your package with Launchpad Translations - Instructors: dpm [16:01] Let's wait a couple of minutes for everyone to join in, and then we can get started [16:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/03/%23ubuntu-classroom.html following the conclusion of the session. [16:03] Ok, let's get started... [16:03] Hi all [16:04] Welcome to this Ubuntu Developer Week talk on integrating your package with Launchpad Translations [16:05] I'm David Planella, from the Community team at Canonical, and my job as the Ubuntu Translations Coordinator is to make sure, with the help of our awesome translations community, that Ubuntu rocks equally hard in every language. [16:05] Today I'd like to get a bit more technical and explain how you can make sure your package is well integrated with the Launchpad Translations web app, [16:06] so that Ubuntu translators can happily do their work and provide a well localized OS to our users. [16:06] Just to give you a brief summary, here's how it will go: [16:06] We'll first start with a couple of background subjects, then we'll go more into the details related to packaging and finally we'll wrap it up with a Q+A session [16:07] If you have questions during the session though, feel free to interrupt and ask me on #ubuntu-classroom-chat [16:07] So, without further ado... [16:07] Let's roll [16:07] Integrating Your Package with Launchpad Translations [16:07] ==================================================== [16:07] So, as mentioned in the intro, the idea of this talk is to give you an overview of what is needed in your package to play well with Launchpad and for their translations to be exposed to translators there. [16:08] Note that this only essentially applies to packages in the main and restricted repositories (and additionally for the -security, -proposed and -updates pockets). [16:09] Only their translations will be imported into Launchpad and delivered in language packs (more on this in a few minutes). [16:09] Packages in universe, multiverse, etc. will not be translatable in Launchpad, and translations will be shipped with the packages and have no direct interaction with Launchpad or the language pack infrastructure. [16:09] i.e. they will be shipped as they come from upstream [16:10] First of all, I'll start with a bit of background for those of you not yet too all familiar with translations [16:10] Launchpad Translations [16:10] ---------------------- [16:10] As you might know, in Ubuntu we use our very own translations tool: Launchpad Translations [16:11] Launchpad Translations allows distributed translation of our Operating System, by a large number of volunteer contributors, who work hard to ensure Ubuntu is well localized for everyone to use it in their own language. [16:11] You can see the Ubuntu translations here: https://translations.launchpad.net/ubuntu [16:11] (you can choose a distro series there, e.g. Natty to see the stats) [16:12] There you'll see a list of translatable applications and documentation, ordered by priority [16:12] Ubuntu is currently translated in more than 200 languages, with different levels of coverage, and can easily support more. [16:12] You can see the languages supported of in the last stable version of Ubuntu here: [16:12] http://people.ubuntu.com/~dpm/ubuntu-10.10-translation-stats.html [16:12] Many of those translations are done by upstream translation communities, and they also get imported into Launchpad during package uploads [16:13] The Ubuntu Translations Community [16:13] --------------------------------- [16:13] I won't dwell too much on this subject, as I think as a packager you might be more focused on the technical side of things. [16:13] Nevertheless, I'd like to add a few words about the Ubuntu Translations community, since I think, be it for the subject of this talk, or be it because we are all part of the bigger Ubuntu family, it is important for those working directly or indirectly with translations to know more about it. [16:14] Ubuntu Translators are a vast number of volunteers who organise themselves in translation teams, appointed to be responsible for the translation of a given language. [16:14] And they just rock. [16:14] You can see the full list of Ubuntu translation teams here: [16:15] https://translations.launchpad.net/+groups/ubuntu-translators [16:15] With your translation uploads you'll be enabling them to deliver Ubuntu in hundreds of languages, to many, many people [16:15] So time to feel proud now :) [16:15] Language Packs [16:15] -------------- [16:16] btw, I guess there were no questions so far, if there is anything that was not clear, feel free to ask [16:17] In Ubuntu we ship all translations in dedicated .deb packages called language packs [16:17] Packages in main and restricted don't contain translations in the form of .mo files themselves [16:18] (if you are not familiar with them, .mo files are a type of binary files where translations are loaded from at runtime. The source for translations are textual .po files that get compiled into the final .mo files) [16:18] They are stripped during the build on the Launchpad buildds and put into the language-pack-* packages instead. [16:19] There is a set of language packs per language [16:20] They are divided roughly between generic translations and those which are used in a GNOME-based desktop and those used in a KDE-based desktop [16:20] We essentially make use of language packs to deliver translations independently from applications and thus we're able to ship regular translation updates throughout a distro series lifecycle. [16:21] Translations Import Workflow [16:21] ---------------------------- [16:22] On a 1000 feet view, what happens when you do a package upload is that their translations get stripped by a tool called pkgbinarymangler, and they are put in a translations tarball containing a translations template (more on this later on) and the translations themselves. [16:22] This tarball is then fed to Soyuz, which ends up handing it to the translations imports queue. There, they will be eventually processed, approved and imported into Launchpad, at which point they will be exposed in the translations web interface ready for translators to do their job. [16:24] If you are interested in seeing what the imports queue looks like, you can see the translation uploads currently pending review here: [16:24] https://translations.launchpad.net/ubuntu/natty/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW&start=75&batch=75 [16:24] That's the global imports queue, but you can see it per package as well [16:25] https://translations.launchpad.net/ubuntu/natty/+source/gtkhtml3.14/+imports [16:25] There's an example ^ [16:26] So now we come to the nitty gritty details... :) [16:27] let's try to answer some of the questions first... [16:27] monish001 asked: Are we taking here about the time of package installation - "stripped during the build on the Launchpad buildds and put into the language-pack-* packages instead." [16:28] No, the translations are stripped during the package build. By the time the package is installed, translations are no longer in the package [16:28] They will be in the language packs instead [16:28] chadadavis asked: when translations from different packages are merged into a language pack, how do you check that expressions like "File not found" are translated consistently between applications? [16:29] That's something that as a packager you cannot ensure, so you'll be relying on translators to work consistently [16:29] Launchpad also helps on that, giving global suggestions for translations which have the same original message in other projects [16:30] What I'm trying to say is that this is something translators are used to deal with [16:30] and translation consistency is part of their work [16:30] ok, let's move on then [16:30] Package Modifications for a better Ubuntu integration [16:30] ----------------------------------------------------- [16:31] In order for translations to be imported to Launchpad and in order to direct translators to the translations page to start contributing straight away, [16:31] we make two main changes to the application at the packaging level: [16:31] * Creation of a POT file on build - We require the .deb package to produce a .pot translation template during the build, which will be imported into Launchpad and be used to expose translations for translators to do their work. [16:31] * Addition of the Launchpad integration library - We add some functionality to display some additional entries to the Help menu, to direct contributors to Launchpad to report bugs, submit translations and get help. [16:32] For those not familiar with the concept of a POT template: [16:32] It's a textual file with the .pot extension [16:33] and it's what Launchpad use as the source for exposing translations [16:33] all translations in all languages will be based on that template, which contains the translatable messages in English [16:34] It's generally built by gettext-based tools [16:34] which extract translatable messages from the code in an application [16:34] and put them in the textual .pot file [16:34] Generating POT templates [16:34] ~~~~~~~~~~~~~~~~~~~~~~~~ [16:34] For pkgstriptranslations (in the pkgbinarymangler package) to do the job right and translations to be imported into Launchpad, [16:35] you should make sure that your package in main or restricted generates a POT translation template during the build. [16:35] It does not necessarily need to be shipped in the source or in the binary package. [16:35] Generating it during the build is good enough. [16:35] -> Note that if your package does not generate a POT template on build, its translations will remain as Blocked in the Launchpad Translations import queue and will not be imported [16:35] So it's important to get this right [16:36] The most common approaches are running either of the following in the debian/rules file: [16:36] * For packages using CDBS and automake: [16:36] * You just need to include /usr/share/cdbs/1/rules/langpack.mk in debian/rules [16:36] * If the package is a GNOME one, and you are using the gnome.mk CDBS class already, you should be good to go, since it already includes langpack.mk [16:36] * If for some reason the POT template cannot be generated during the build, see the next points below. [16:37] * Other packages, using intltool usually require: [16:37] * A call to intltool-update -p in debian/rules, or [16:37] * a call to an already existing Makefile target to build the POT (this does exist quite often in fact). [16:37] * For packages which don't use intltool: [16:38] * Need to get fixed individually: [16:38] * Usually by adding a call to xgettext and po/POTFILES.in, or [16:38] * Finding an already existing Makefile target. e.g. Use $(MAKE) -C po update-po instead of (cd po; make update-po; cd ..). Example in the debian/rules file from upower: [16:38] common-post-build-arch:: [16:38] make -C po upower.pot [16:38] * Packages which use python-distutils-extra: [16:39] * Template creation should happen automagically :) [16:39] oh, btw: [16:40] Gettext is the underlying and most widely used technology to enable translations of Open Source projects. [16:40] Intltool is a higher level tool that adds functionality to gettext by allowing the extraction of translatable strings from a variety of file formats. [16:40] Questions so far? [16:41] Is it clear that Ubuntu packages need to generate a .pot file during the build? [16:41] ok, next then [16:41] The Launchpad Integration Library [16:41] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [16:42] Ubuntu applications use the Launchpad integration library to provide shortcuts to Launchpad to obtain help, report bugs and submit translations. [16:42] You can see it in action in every application's help menu, and it lives here: [16:42] https://launchpad.net/launchpad-integration [16:42] Note that this only works for Ubuntu packages available in the repositories. The Launchpad integration library does not work with PPAs or other projects hosted in Launchpad. [16:42] It has bindings for several languages. An example in Python: [16:43] import LaunchpadIntegration [16:43] LaunchpadIntegration.set_sourcepackagename('my_app') [16:43] LaunchpadIntegration.add_items(self.builder.get_object('menu_help'), 0, False, True) [16:43] Unless the packaged application itself makes use of it already, you should add it as a patch. [16:43] If you want to see a couple of examples, these bugs will help you learning how you can add support for the Launchpad Integration Library to your package: [16:44] https://bugs.launchpad.net/bugs/436742 [16:44] https://bugs.launchpad.net/bugs/508395 [16:44] Verifying Packages [16:44] ------------------ [16:44] Finally, here is a small recipe and some guidelines to help you test and optimize your packages, so that translation-related files get automatically imported seamlessly into Launchpad. [16:44] Generally, you will only need to do this once when setting up your package the first time, altough it can also be useful to debug import problems, for example [16:49] Testing the package locally [16:49] ~~~~~~~~~~~~~~~~~~~~~~~~~~~ [16:49] To test if your package conforms to the requirements of the import script in the Launchpad imports queue, you can do the following: [16:50] oops short disconnection :) [16:50] anyway, let's continue... [16:50] * Template name and domain: the filename of the template (.pot file) should be the same as what the expected translation domain is. [16:51] * Translation filenames: the actual translations (.po files) must have a filename of the format $LANGUAGECODE.po or $LOCALECODE.po (e.g. de.po, pt_BR.po, zh_TW.po) [16:51] There are 10 minutes remaining in the current session. [16:51] * Template and translations location: all translation-related files (the .pot template and its corresponding .po templates) must end up in the same (sub-)directory if possible. [16:51] * Obsolete translations: if there are .po files present in the package but no associated .pot template, please remove them, since they cannot be used without a .pot template. [16:51] * Valid POT template: please check if the .pot file has any meaningful content. Empty .pot files should best be removed and the package build rules be fixed. [16:52] * Templates generated by patches: if your package contains patches and those patches result into extra templates, like patches.pot, please merge those changes into the main template [16:52] Anyway, that was it for the session content, [16:52] I hope you found it useful [16:53] If you've got any questions related to the session or to translations in general, now feel free to ask! :-) [16:53] Q+A [16:53] --- [16:53] chadadavis asked: does the Launchpad integration provide any services for PPA packages? Since it's not officially supported/working on those? [16:54] As far as I know, it works only if there is a package available in the Ubuntu repositories, but I haven't tried it with PPAs [16:55] Any more questions? [16:56] There are 5 minutes remaining in the current session. === mdeslaur_ is now known as mdeslaur [16:58] ok then, if there are no more questions we'll wrap up early [16:58] Thank you very much for your attention, I hope you enjoyed it and I hope to see you soon! [16:59] I'll now leave you in the able hands of Kaleo, who'll tell you all about Getting Started with Unity 2D!! [16:59] Enjoy! [17:00] it seems Kaleo is not here yet, and I see there is a question, so I'll try to answer that one in the meantime [17:00] monish001 asked: What if i want the enduser to choose the language? === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Getting Started with Unity 2D - Instructors: Kaleo [17:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/03/03/%23ubuntu-classroom.html following the conclusion of the session. [17:02] Kaleo has been caught up in something else important. I'll keep you posted. Hold tight. [17:05] thanks a lot Kaleo [17:05] with just 5 minutes delay, I give you Florian "Kaleo" Boucault, one of the masterminds behind Unity 2D [17:05] enjoy the session :) [17:06] Thanks people for joining in [17:06] I will give a brief overview of Unity 2D [17:06] And let you guys shoot questions my way [17:07] Unity 2D is essentially an implementation of the Unity user interface using Qt and QML [17:07] it reuses the same backend technologies used in Unity proper [17:07] libbamf, libdee, libunity, places, etc. [17:08] and intends to provide a UI that matches Unity proper as much as possible [17:08] The rationale behind Unity 2D is that we want to run on platforms that do not provide accelerated OpenGL [17:08] QUESTION: < jack002> what are those: libbamf, libdee, libunity, places, [17:09] BAMF provides application matching services: it tells you what applications are running on the desktop and informations about them [17:09] libdee is a way to publish lists of data over D-Bus [17:10] places are the providers of data for the dash (the dash is the thing that comes up when you click on the Ubuntu button in the top left corner) [17:11] For those who want to try out Unity 2D, you can find it in a PPA for Natty [17:11] We also provide a stable version for Maverick in the same PPA but it does not contain the latest features [17:12] < monish001> QUESTION: how to find it in a PPA for Natty? [17:12] https://launchpad.net/~unity-2d-team/+archive/unity-2d-daily === dholbach_ is now known as dholbach [17:13] Unity 2D is the default interface for ARM based Ubuntu isos [17:15] For developers [17:15] and people interested contributing to it [17:15] we have a home on the ubuntu wiki [17:15] https://wiki.ubuntu.com/Unity2D [17:16] In terms of architecture [17:16] Unity 2D is divided into: [17:16] - window management (using metacity) [17:16] - a top panel [17:16] - an application launcher on the left [17:16] - the dash search interface [17:16] - a workspace switcher [17:16] they are all separate applications/processes [17:17] the code (hosted on launchpad with Bazaar) reflects that separation of components [17:18] each having its directory: [17:18] - panel [17:18] - launcher [17:18] - places (= dash) [17:18] - spread (= workspace switcher) [17:18] metacity being mostly upstream with around 3 small patches [17:19] 18:17 < chadadavis> The current natty seems to already have it in the default repositories. [17:19] That's correct [17:19] We pushed a recent version into Natty last week [17:19] but I really recommend the PPA [17:19] which contains critical bug fixes [17:20] 18:19 < abhinav> QUESTION: what languages can we use for development ? and can development be done on Maverick or Natty is absolutely necessary ? [17:20] Unity 2D is written in C++, QML and incidentally Javascript [17:20] C++ is used to create APIs that the user interface written in QML uses [17:21] QML is a declarative language to describe user interfaces; it is part of Qt [17:21] Development is now only done on Natty [17:21] We stopped developing on Maverick 2 weeks ago [17:22] Only backporting essential bug fixes [17:22] 18:20 < rsajdok> QUESTION: Can you describe how to run unity-2d-launcher with gdb and any function? [17:22] If you have Unity 2D installed from the PPA [17:22] and if Unity 2D is running [17:22] you can attach gdb to the unity-2d-launcher process [17:23] ps aux | grep unity-2d-launcher will give you the PID of it [17:23] sudo gdb -pid PID_OF_LAUNCHER [17:23] will give you the gdb prompt [17:23] rsajdok: does it answer your question? [17:26] < jack002> QUESTION: Is there any plan to implement "windows tiling" like in Windows? I constantly need two programs opened like Firefox and Terminal. Switching between them is annoying, resizing windows is time consuming... [17:26] There is no plan for windows tiling as far as I know [17:26] Sorry :( [17:27] < monish001> QUESTION: Could we expect projects from unity 2D for GSoC 2011? [17:27] We have not thought about it at all [17:27] It sounds like a great idea [17:27] I would love any help we can get :) === ClassBot_ is now known as ClassBot === jussi01_ is now known as jussi [17:30] For people who want to chat about Unity 2D in general [17:31] we hang out on #ayatana on freenode [17:31] with the Unity proper people [17:31] agateau, oSoMoN and uriboni are the people to talk with [17:31] by uriboni I meant nerochiaro! [17:35] Ok, well [17:35] I feel we are running out of questions [17:35] Thank you all for the good questions and your time [17:36] I will stay here longer in case any question comes up [17:36] 18:35 < raki__> i would want to help too how can i start? [17:36] Start by installing it and trying it out [17:40] If you like it [17:40] I suggest you find something you would like to improve [17:40] And start from there [17:40] The wiki page is a great starting point [17:40] https://wiki.ubuntu.com/Unity2D === leila is now known as Guest82995 [17:40] < monish001> QUESTION: do we have something called unity 3d also> [17:40] Unity 3D is a nickname for Unity proper, Unity you get by default in Ubuntu Natty [17:41] < Mkaysi> QUESTION: Is Unity2D going to be shopped with Natty, if someone uses computer, which can't run Unity 3D? [17:41] No, it will not be installed by default [17:41] It will not be on the CD [17:41] but it is installable via the packages very easily === Kmos is now known as Guest60040 [17:41] < rsajdok> QUESTION: It started but I can not set backtrace on function launcherapplication::launch() [17:41] for that you will need to run from the source code [17:41] by that I mean [17:41] get the source code as indicated on the wiki page [17:41] compile it [17:42] and then start the launcher from there using gdb: [17:42] bzr branch lp:unity-2d [17:42] cd unity-2d [17:42] cmake . && make [17:42] gdb ./launcher/app/unity-2d-launcher [17:42] should do it === yofel_ is now known as yofel [17:52] QUESTION: [17:52] < raki__> suppose if i want to develop something for unity then will i have to learn qml or c++ is enough? [17:52] < raki__> and what are you using javascript for? [17:53] if you are going to touch the user interface at all you will need to understand QML [17:53] Javascript is used inside QML [17:53] but no worries, QML is really as easy as it gets [17:53] the learning curve is not so high if you did UIs before [17:56] monish001> QUESTION: could you provide any good tutorial for QML to get started? [17:57] the QML documentation is quite good [17:57] and there is an official tutorial [17:57] http://doc.qt.nokia.com/4.7-snapshot/qml-tutorial.html === msnsachin12 is now known as msnsachin === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Q+A with Ubuntu Engineering Director - Instructors: rickspencer3 [18:01] hello all === Guest60040 is now known as KKmos [18:02] I guess there's no intro or such, just dive in? [18:02] so, I'm Rick Spencer [18:02] I'm currently the director of engineering for Ubuntnu Engineering [18:03] which basically means that I help the teams that create Ubuntu, Ubuntu Server, Ubuntu Arm editions, Ubuntu virtual images, etc... [18:04] I'm happy to take questions on any and all topics [18:04] please note that I don't typically have a lot of fine grained technical context on some things, so I may have to refer you to others for certain things [18:04] I guess I'll just hang out and see if I get any questions? [18:06] mhall119 asked: What do you do as Engineering director? [18:06] well, the Engineering Managers, and the our release manager and our technical architect all report to me [18:07] so, there is a lot of my job that is typical people management [18:07] making sure people have what they need to do their jobs [18:07] signing off on holiday requests and expense reports, that kind of stuff [18:08] also, the Engineering Managers (as well as Kate and Allison - release manager and technical architect) and I are all a management team [18:08] so I have some leadership roles on that team [18:08] for instance, I try to herd this particular herd of cats through planning UDS [18:08] another part of the role is around product management [18:09] this involves a lot of working with folks in the Ubuntu community, upstreams, Canonical, etc... to understand what they need or want to do with Ubuntu [18:09] and I try to get everyone aligned to make those things happen [18:12] Director of Engineering sounds like a role with a lot of Authority ... but it's not really that kind of job [18:12] I do try to use the position to influence the project though in ways that I think are important [18:15] for instance, in Natty I wanted to see more work to enable community contributions to land easily, so I worked with the community team and engineering managers to make sure that Canonical engineers could do that [18:15] hmm ClassBot stopped working for me :/ [18:15] I'll go copy and paste method [18:15] QUESTION: What challenges do you see in recruiting and keeping good people? [18:15] well, for Ubuntu Engineering, their are a couple of challenges [18:15] first, people do best when they are comforatable working in a transparent community minded manner [18:15] jsjgruber asked: What challenges do you see in recruiting and keeping good people? [18:15] hmmm, freenode seems to be acting a bit wonky, please try to bear with me here === daker is now known as angeldaker === tubadaz_ is now known as tubadaz [18:16] so, finding engineers and managers who *like* to work on a community project can be difficult at times [18:17] like, we may find someone who knows a technical space really well, but is not comforatable working in the open [18:17] another aspect is that Canonical folks who get paid to work on Ubuntu work at home [18:17] but then that is punctuated with travel [18:17] personally, I love the lifestyle, but it's not for everyone === JayFo is now known as JFo [18:18] also, for my part, I am very picky [18:18] I really look for people who are "awesome" in multiple ways, so it can take longer to fill some roles [18:19] finally, we work really hard, but have high standards in terms of being easy to work with [18:19] so that's recruiting [18:19] in terms of retaining, this has not been so challenging, we don't get too much turn over [18:19] but when people do leave, they seem to become more like alumni than "ex-Canonical" folks [18:19] so it seems that in general people depart on good terms [18:20] mhall119 asked: Do you have any specific goals for the Natty Cycle, and if so who are those going so far? [18:20] hey, classbot is working again! [18:20] anyway [18:20] YES! [18:20] hold on [18:20] so, there are goals that are project wide, then my personal goals [18:20] for the project wide goals, there was a lot of focus on the client [18:20] we had 5 primary areas for Canonical folks to focus on on the client [18:21] 1. Unity (natch) [18:21] 2. 2d experience [18:21] 3. software center [18:21] 4. contributors (as previously mentioned) [18:21] 5. testing [18:21] this last bit is new to us [18:21] for my perosnal goals, I wanted to see: [18:21] 1. more nurturing of new contributors [18:21] 2. more and better communication across the project [18:22] 3. more systematic release process with better quality [18:22] I think that #1 has gone pretty well thanks to the community team and the redoubled efforts of Canonical engineers AND Ubuntu engineers [18:22] for instance, the sponsorship queue hit a low of only 14 items earlier this week [18:23] #3 has gone well thanks to the efforts fo skaet and many others [18:23] #2, I'm not to sure we made much progress there, it's a hard problem [18:23] chadadavis asked: Is there are hard line between Canonical employees and others, or does Canonical sponsor / support some developers part time as well? [18:23] well ... === AndrewMC is now known as Guest30896 [18:24] to be a Canonical employee working in Ubuntu essential means that you get paid by Canonical to work in the Ubuntu community full time [18:25] so, the community of Ubuntu developers is a super set of the developers that Canonical pays [18:25] however, Canonical does, from time to time, outsource some development work on Ubuntu, but typically for projects for which Canonical is the usptream [18:25] for example, to finish off parts of Unity [18:25] normally, but not always, that will go through a company like Codethink, or Collabora [18:26] fisch246 asked: i realize this is really early... but has there been any talk on 11.10 yet? any ideas being passed around? care to share any? === Guest30896 is now known as AndrewMC [18:26] it is early, but not really really early [18:27] allison (wendar) the Technical Architect on our team ... is going to work on getting all the great ideas from users and developers organized 11.10 UDS, and I think she's going to start that soon [18:27] so at the product level, what will ubuntu *be*, nothing really specific comes to mind [18:27] however, in terms of the project, I would like to see more nurturing of new contributors, but also [18:28] revisit if existing core contributors are being sufficiently and properly supported [18:28] also, the whole project wide communication part, I'd like us to take another whack at that [18:29] one area that does occur to me for the project is how users actually get Ubuntu [18:29] I'm wondering if having basically a set of CD ISOs should be the only way to get Ubuntu, or if there should be others [18:29] like should we have a tool for creating a USB stick [18:30] or maybe you we could use a net-install kind of thing [18:30] mhall119 asked: Last I heard, Canonical doesn't run a private UEC cloud for their own websites (or community-run sites like loco-directory), why is that and is there any plans to change? [18:31] Canonical has an IS team that sets up all that infra structure and such [18:31] I very much trust that they make good decisions about how best to support Ubuntu, so I never really looked into this [18:31] so, I can't really answer your question [18:31] if you PM me, I can work to connect you with someone who could though [18:32] gaberlunzie asked: when is Libre.fm going to get some love to make it into Banshee or other? [18:32] sorry, I have no idea [18:32] I would follow up with jasonwarned, he hangs out in #ubuntu-desktop [18:32] darkdevil666 asked: Any thought of implementing gnome shell 3 in later versions? [18:32] sure [18:32] I look at it in 2 ways [18:33] first, Ubuntu should always offer the choices of the best in FOSS software [18:33] so, when we are able, it should be trivial to install a gnome-shell session on Ubuntu [18:33] secondly, if in the long run, gnome-shell turns out to be simply the best choice for users, we shouldn't hesitate to embrace it [18:34]