[03:21] hi chilicuil [03:22] chilicuil: did you go any further with the forum issue yet? [03:24] elfy: hey elfi, not yet, I've comment it to the team though, we're still evaluating alternatives, thanks for the follow up =) [03:25] you're welcome - not often I'm actually up when I see you join channel(s) === Neo31` is now known as Neo31 === \b is now known as benonsoftware === kickinz1 is now known as kickinz1|afk === kickinz1|afk is now known as kickinz1 === kickinz1 is now known as kickinz1|afk [16:00] o/ [16:00] hi [16:01] \o [16:01] o/ [16:02] o/ [16:02] o/ [16:02] steve and I are in a call still [16:02] ah [16:02] should end soon i hope [16:02] I'm in that call too :) [16:02] oh, sorry [16:02] indeed [16:03] * barry can start the meeting [16:03] #startmeeting [16:03] Meeting started Thu Feb 19 16:03:12 2015 UTC. The chair is barry. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:03] Available commands: action commands idea info link nick [16:03] thanks barry [16:03] give me a few moments folks... [16:04] o/ [16:04] #topic lightning round === meetingology changed the topic of #ubuntu-meeting to: lightning round [16:05] echo $(shuf -e barry doko stgraber jodh bdmurray slangasek caribou infinity mvo sil2100 robru cyphermox) [16:05] sil2100 caribou robru doko slangasek stgraber mvo barry jodh bdmurray infinity cyphermox [16:05] sil2100: you're up! [16:05] * cyphermox is starting to think shuf knows about him, and sorts 'cy' towards the end. [16:05] Oh! [16:05] I didn't expect that [16:06] - Landing team work, silo coordination, preparing landing e-mails [16:06] - Trying to debug/triage some of the strange CI Train problems sighted on Friday [16:06] sil2100: I can start if you want [16:06] - Promotion of the RC image for the ww07-2015 milestone [16:06] - Documenting the ww07-2015 milestone on the reports page [16:06] - Attending RTM status meetings [16:06] - Tending the ww09-2015 milestone, coordinating landings and fixes [16:06] - Experimenting with custom tarball creation for ubuntu-rtm mako * Poking around and learning about apparmor cache re-creation [16:06] - Archive diff automated scripts * Implemented proper deep version differencing between archives * Made the binary -> source conversion more efficient [16:06] - Improve error handling for commitlog generation [16:06] - A short patch-pilot duty [16:06] (done) [16:06] Bugfix: [16:06] hm, it pasted strangely [16:06] - Upload of Firmware assisted dump support for ppc64el to Vivid (LP: #1415562) [16:06] Launchpad bug 1415562 in linux (Ubuntu) "[Ubuntu 15.04] Support firmware assisted dump on ppc64le" [Medium,Fix committed] https://launchpad.net/bugs/1415562 [16:06] - CUPS : SRU for bug #1352809 (-h override) [16:06] bug 1352809 in cups (Ubuntu Utopic) "/usr/bin/lp on Trusty using -h option doesn't work as expected" [Medium,Fix committed] https://launchpad.net/bugs/1352809 [16:06] - rsyslog memory leak (LP: #1423586) [16:07] Launchpad bug 1423586 in rsyslog (Ubuntu Trusty) "Please backport memory leak fixes present up to 7.4.6" [Medium,Confirmed] https://launchpad.net/bugs/1423586 [16:07] - libvirtd lost floating IP [16:07] Prepare CTS sprint [16:07] Work on deja-dup FTBS (test needs fixing) [16:07] (done) [16:07] * Train: [16:07] - ported test suite from nose to nose2 at barry's recommendation [16:07] - fixed a couple of unhandled exceptions in rare corner cases discovered in last weeks' build.py rewrite [16:07] - started a branch for pushing merged branches to LP at build time instead of publish time (but didn't land this yet) [16:07] - started generating full silo content diffs at build time [16:07] - in response to disk space crisis, added a cleanup step that deletes extra copies of built packages after they're no longer needed (eg, versions from distro are downloaded for diffing, and then those get left around taking up space; deleting them halves the silo disk usage after diffs are generated) [16:07] - discovered a case where two silos containing the same package were published at the same time; the usual check that prevents this failed due to a race condition, experimented with a branch to resolve this but it's incomplete. [16:07] - removed the mandatory 5 minute pause at the start of the watch phase; this has no effect on builds but speeds up WATCH_ONLY runs on already-built silos from 5 minutes to 20 seconds. [16:07] - merged watch_ppa.py into build.py because it no longer made sense for those modules to be separate (watch_ppa.py contained a lot of boilerplate that duplicated what was already handled better by the new build.py; merging them resulted in the watch_ppa.py logic taking up half as many lines of code with no feature regressions) [16:07] - streamlined a couple untested packagemanager.py functions and wrote tests for them [16:07] - modified build.py to start recording the revno of the branch it merges, and modified publisher.py to check these revnos and prevent publication if a branch contains a new, unbuilt revno. [16:07] - attempted running the test suite under py3 and started fixing the easiest of bugs, however there's a large class of unicode bugs I've yet to understand. [16:07] robru: \o/ [16:08] robru: feel free to ping me about those [16:09] i think doko is not here today [16:09] slangasek: are you ready or should we come back to you? [16:09] barry: yeah I need to read about unicode, I do not understand it very well atall [16:10] robru: i have some excellent links and resources i'll pass along [16:10] barry: thanks [16:10] let's come back to slangasek [16:10] 51 minutes until the meeting [16:10] stgraber: are you here today? [16:10] robru: very impressive list :) [16:10] mvo: thanks ;-) [16:10] let's come back to stgraber, tho i'm not sure he's here today [16:11] mvo: you're up if you want, or we can come back [16:11] click: [16:11] - merge review feedback from barry, thanks! [16:11] - New click 0.4.37, mostly SDK fixes [16:11] growisosfs: [16:11] - merge fix for blue-ray burning bts #713016 (LP: #113679) + SRU [16:11] unattended-upgrades: [16:11] - Review/merge fix for #1422345 and upload new version (thanks Brian!) [16:11] snappy: [16:11] Launchpad bug 113679 in xorg-server (Ubuntu Dapper) "xorg freezes when running openoffice" [High,Fix released] https://launchpad.net/bugs/113679 [16:11] - prepare new alpha3 with snappy-go as part of the release [16:11] - lots of features/fixes/improvements for snappy-go [16:11] (include fixes to make the code go vet/go-lint clean) [16:11] - spec/implemented snappy config (with examples) [16:11] (done) [16:11] eh, thats not the right bugnumber [16:12] barry: right, hi, here now :) [16:12] but I have nothing written ;-D [16:12] bug #11133679 [16:12] Error: Launchpad bug 11133679 could not be found [16:12] slangasek: no worries, we'll come back to you [16:12] short week due to usa holiday. [16:12] si: LP: #1421434. LP: #1387719. lots of testing for 3.0 release. built 3.0 package for citrain; testing and debugging build failures. started to look at the server code; filed one mp with more to come. (server needs some changes to support si 3.0) [16:12] Launchpad bug 1421434 in Ubuntu system image "Ensure reactor listens for signals on the correct object path" [High,Fix committed] https://launchpad.net/bugs/1421434 [16:12] Launchpad bug 1387719 in Ubuntu system image "Update useragent to contain the current channel name, device name and build id" [High,Fix committed] https://launchpad.net/bugs/1387719 [16:12] other: click reviews for mvo. lots of discussion upstream and elsewhere about python zip file distributions (single-file executables). investigated several tools. began working with pex. [16:12] debuntu: debian bug 778708 (pex ITP) [16:12] Debian bug 778708 in wnpp "ITP: python-pex -- library for generating Python executable zip files" [Wishlist,Open] http://bugs.debian.org/778708 [16:12] --done-- [16:12] https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1113679 [16:12] Launchpad bug 1113679 in dvd+rw-tools (Ubuntu Utopic) "Close session failed when burning 25gb blu-ray disc" [Undecided,In progress] [16:13] barry: \o/ for the reviews [16:13] mvo: np! ping me if you need more [16:13] jodh: are you around today? [16:13] barry: there are still some open but no real rush [16:13] * snappy: [16:13] - Reworked bug 1412737 after discovering the original code didn't work [16:13] bug 1412737 in snappy-ubuntu "snappy on grub systems should detect a broken boot and fall back to the other root partition on power cycling." [Critical,Confirmed] https://launchpad.net/bugs/1412737 [16:13] in a chroot: [16:13] https://code.launchpad.net/~jamesodhunt/snappy/bug-1412737/+merge/249976 [16:13] - Wrote a "Snappy Image Tests" doc that documents the tests to run for [16:13] a promotion candiate: [16:13] https://docs.google.com/a/canonical.com/document/d/1R_Tw0N0QbEpjFeYf9XnVV8Gp8ldT2Ig0PO6MfR-kuSM/edit [16:13] - Investigated an issue raised on #snappy (bug 1423529) that uncovered a couple of [16:13] bug 1423529 in snappy-ubuntu "writable partitions not fsck'd." [High,In progress] https://launchpad.net/bugs/1423529 [16:13] initramfs bugs. Tested fix and awaiting comments: [16:13] https://code.launchpad.net/~jamesodhunt/ubuntu/vivid/initramfs-tools-ubuntu-core/bug-1423529 [16:13] - Code reviews and MP prep. [16:13] - Promotion candidate testing. [16:14] * misc: [16:14] - perf review admin. [16:14] ⚽ [16:14] mvo: cool. i'll take a look while my long friggin' tests are running :) [16:14] barry: hehe [16:14] investigation into errors oops regarding event greenlets [16:14] submitted RT to have staging version of gunicorn updated [16:14] tested backport of gunicorn to precise in canonistack (good) [16:14] tested gunicorn update on staging / production version of daisy and errors FEs (good) [16:14] review of Error Tracker OOPS reports, setup exception handling for LP not returning JSON [16:14] pinged webops regarding kicking retracers [16:14] foundations bug triage [16:14] submitted git pull request to upstream unattended-upgrades fixing LP: #1422345 [16:14] Launchpad bug 1422345 in unattended-upgrades (Ubuntu) "stop being nice does not work" [High,In progress] https://launchpad.net/bugs/1422345 [16:14] uploaded unattended-upgrades fix for LP: #1422345 to T and U [16:14] uploaded update-manager fix for LP: #1421044 [16:14] Launchpad bug 1421044 in update-manager (Ubuntu) "Too easy to accidentally restart computer when 'restart to complete update' box pop up" [High,Fix released] https://launchpad.net/bugs/1421044 [16:14] uploaded a fix for ubuntu-release-upgrade KDE frontend bug (LP: #1423279) [16:14] Launchpad bug 1423279 in One Hundred Papercuts "[vivid] [proposed] syntax error while upgrading" [High,Confirmed] https://launchpad.net/bugs/1423279 [16:14] SRU verification of whoopsie Utopic fix for LP: #1217407 [16:14] bdmurray: \o/ for the unattended-upgrades fix! [16:14] Launchpad bug 1217407 in whoopsie (Ubuntu Utopic) "whoopsie spams the log with "online" messages" [Low,Fix committed] https://launchpad.net/bugs/1217407 [16:14] SRU verification of apport Utopic fix for LP: #1084979 [16:14] Launchpad bug 1084979 in apport (Ubuntu Utopic) "Submitting error report asks confounding questions" [Medium,Fix committed] https://launchpad.net/bugs/1084979 [16:14] recreated and reported apport bug LP: #1423382 [16:14] Launchpad bug 1423382 in apport (Ubuntu) "unable to use apport to report a bug from point release Live CDs" [Undecided,New] https://launchpad.net/bugs/1423382 [16:14] pinged cyphermox regarding merge proposal for bug LP: #1325801 [16:14] Launchpad bug 1325801 in Ubuntu CD Images "failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:" [Undecided,In progress] https://launchpad.net/bugs/1325801 [16:14] performance review [16:14] short week due to Monday Holiday [16:15] ✔ done [16:15] Last week: [16:15] - Was at Linaro Connect all week, good sessions, good conversations [16:15] - Got a new ARMv8 board to play with, when I find some "spare" time [16:15] This week: [16:15] - Point release, point release, point release, point release! [16:15] - Some kernel SRU wrangling [16:15] - General SRU and AA reviews and maintenance [16:15] (done) [16:15] * partman-auto upload as per last week [16:15] * continued investigation on ppc64el bootloader installation issue. [16:15] * Patch pilot on Monday: grub-installer, live-build, resiprocate [16:15] * Fixed minor bug in network-manager-openconnect. [16:15] * Reviewed/looked into bug 1422924. [16:15] * Reviewed MP for usb-creator bug 1325801 [16:15] bug 1422924 in network-manager (Ubuntu) "Revert latest nm" [Undecided,New] https://launchpad.net/bugs/1422924 [16:15] bug 1325801 in Ubuntu CD Images "failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:" [Undecided,In progress] https://launchpad.net/bugs/1325801 [16:16] * Discussed debian-installer arm64 changes with dannf. [16:16] * Looked into bug 1422864 in ubiquity with infinity. [16:16] * SRU for installation-guide, efibootmgr. [16:16] bug 1422864 in ubiquity (Ubuntu Trusty) "14.04.2: UEFI: linux 3.13.0-45 downloaded during install" [Undecided,Fix released] https://launchpad.net/bugs/1422864 [16:16] * ubiquity: bug 1418105. [16:16] bug 1418105 in ubiquity (Ubuntu) "Trusty: testing .2 the oem session on i386 leaves the oem wifi password in place" [High,In progress] https://launchpad.net/bugs/1418105 [16:16] * Reviewing mate-menu, mate-tweak for sponsoring. [16:16] (done) [16:16] slangasek: ready? [16:17] going once [16:17] * short week due to holiday on Monday [16:17] * very focused on snappy [16:17] * image promotion in progress for this week [16:17] * armhf device tarball generation has needed straightening out [16:17] * reviewing branch for grub failover handling [16:17] * looking at initramfs handling of partitions being mounted without fsck; looking to figure out how to do less in the initramfs [16:17] * need to get nfs-utils systemdified today so we can make the switch to systemd by default [16:17] * performance reviews! If you haven't done your self-eval yet, do it yesterday! If you haven't sent me your selections for 360 review, do that today! [16:17] infinity: speaking of last-minute switching to systemd, are you sending the announcement about Feature Freeze? [16:17] oh, and (done) [16:18] thanks [16:18] slangasek: I'm delaying feature freeze until I get all the features in that I want! [16:18] nice plan [16:18] slangasek: (Yeah, I should send the email later tonight, after point release stuff is done) [16:18] infinity: yay! i can sneak a few in too then [16:18] infinity: MOAR FEACHURES! [16:18] #topic AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [16:18] hah [16:18] infinity: ok, no hurry! ;) [16:18] ;) [16:19] slangasek: what about the standing FFe? [16:19] does anybody have anything else fun or interesting to discuss? [16:19] slangasek: did you have a moment to comment? [16:19] sil2100: I'll follow up on that discussion [16:19] Ok, thanks :) [16:20] AOB> do the performance review stuff ;) [16:20] slangasek: at least the site isn't as horribly painful this time around :) [16:20] okay, let's me this short! [16:20] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [16:20] Meeting ended Thu Feb 19 16:20:54 2015 UTC. [16:20] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-02-19-16.03.moin.txt [16:21] thanks! [16:21] thanks barry [16:21] thanks [16:21] cyphermox, infinity : yeah - and i put out a MP for smoser's code to deal w/ the d-i/arm64 changes. i'll go ahead and push that unless there's an objection [16:21] oh crikey, missed infinity [16:21] dannf: try #ubuntu-devel [16:22] dannf: like I mentioned it looked fine but it would be good to have other eyeballs on it, some who've seen more of the arm64 stuff. [16:22] cyphermox: yeah, i'll ping infinity [16:23] alright === med_` is now known as medberry === medberry is now known as medberry2 [16:59] Hello GunnarHj [16:59] hannie: Hi! [17:00] GunnarHj, hannie, Hi. [17:00] hey dsmythies I was just looking for dou or smy in the list :) [17:00] Hi dsmythies [17:02] hi :) [17:02] #startmeeting [17:02] Meeting started Thu Feb 19 17:02:40 2015 UTC. The chair is elfy. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:02] Available commands: action commands idea info link nick [17:03] hi elfy [17:03] #chair dholbach_ [17:03] Current chairs: dholbach_ elfy [17:03] hiya [17:04] #topic CC Catchup with the Doc Team === meetingology changed the topic of #ubuntu-meeting to: CC Catchup with the Doc Team [17:04] hello - how are you doing? [17:04] nice to see you all :) === dholbach_ is now known as dholbach [17:04] how are things in the doc team? [17:05] Low activity, unfortunately. [17:05] O.K. I posted a pathetic litttle update on the agenda (albeit with less than 24 hours until now) [17:05] I was just reading the agenda update [17:05] Evening :) [17:06] GunnarHj, yes low activity. [17:07] seems rather a common comment for sure :) [17:07] there has been a spurt on xubuntu the last few days, and serverguide. [17:07] yea - I know about xubuntu :) [17:07] how do you organise most of your work? is it bug reports? or anything else? [17:08] I mainly work of infastructure and behind the scenes stuff. I just do it. [17:08] As for the desktop guide: Mostly bug reports indeed. [17:08] GunnarHj is usually aware of what I am up to. [17:08] Today is the string freeze? [17:08] The good news is that not much is happening with the Unity desktop right now. [17:08] feature freeze [17:09] so you have a list of bugs people could start working on, if they wanted? [17:09] Today is an arbitrary string freeze for point releases of the serverguide. both 12.04 and 14.04 [17:09] ah ok [17:09] dholbach: The bug list isn't very short either... But basically yes. [17:10] s/short/long/ [17:10] bugs: yes, and Ian is picking away at some on the serverguide front. [17:10] so that's some good news already - it looks like you're organised, even if you could do with more hands on deck [17:11] cloud docs got added recently didn't it - iirc [17:11] In the end we are over dependant on myself and GunnarHj [17:11] you mentioned that you would need server experts - did you get some help from the server team? or are you in touch with them? [17:12] mmm - depending on people can be unfortunate - especially for those depended on [17:12] Subject matter experts: Yes, Peter Matulis sends help requests to the server team list every cycle. [17:12] Re desktop: I'd say we are on top of it right now. But I'm worrying about what's going to happen when the desktop changes significantly. This applies to both the official desktop guide and the Ubuntu manual. [17:13] Do we have a feeling for how steep the learning curve is for new contributors to the docs team? [17:14] Cloud: Yes, after almost a year they have been added. We are happy with the two license apprroach, where the main license didn't chnage but canonical has NC on their stuff. [17:14] yea, I read that [17:14] #chair YokoZar [17:14] #chair YokoZar [17:14] Current chairs: YokoZar dholbach_ elfy [17:14] leasnring curve: Yes, it is steep. I think some give up after becoming overwhlemed [17:14] ha :) [17:15] do you think it could help to have something like a training session to learn "how to fix your first docs bug" or something like that? or did you try that already? [17:15] However, we have completley overhauled all the wiki pages , so at least they help rather than hinder now. [17:15] Re learning curve: I'm not sure I agree with dsmythies on that. It's not rocket science. Anybody who really wants to contribute can do so. [17:15] What are contributor finding overwhelming with the Docs team? [17:16] The extrodinary amount of time it takes to get anything done. [17:16] GunnarHj: well I know that I for one end up scratching my head a lot when I'm editing wiki's :) [17:16] dsmythies: But it's a one time effort. [17:17] training: we did a big thing almost a year ago. Nobody came to it. I wouldn't do it again. [17:17] dsmythies, how long does it usually take to write a wiki manual? [17:17] Beats me, I don't work on the wiki. [17:17] elfy: Ok.. Contributing to the official docs is slightly more complicated..ö [17:17] :) [17:18] Is the official docs and the wiki the same of different? Just so I am clear on the two. [17:18] or different [17:18] ... other than I was heavily involved in the docs team pages overhaul [17:18] anyone thought of running a session at UOS? [17:19] what is UOS [17:19] Could it help to try to separate the task of writing the content from bringing it into the right form/format? [17:19] dsmythies, Ubuntu Online Summit [17:19] dsmythies: the online summit [17:19] elfy: for docs? [17:20] sak: They are to separate beasts. Any Ubuntu user can add stuff to the wiki, while only the dedicated team can commit to the official docs. [17:20] s/to/two/ [17:20] why not - run a community track [17:20] wxl: ^^ [17:20] Thank you gunnarhj [17:21] dholbach: you mean a wyswig editor? :-) [17:21] elfy: We should always have a community track! [17:21] I do not understand "community track" [17:22] dsmythies: track would be a session the doc team ran in UOS - talk about what you do, try and drum up some new blood [17:22] wxl, I just thought a bit longer about the steep learning curve now and wondered if it would help to break up a task like "document how to do X" would be easier or had a better chance of getting done, if the task of writing up the content, ie detailing the instructions, etc. was separated from bringing it in the right form (Mallard or Docbook or moin format or whatever) [17:23] that way the learning curve was probably a bit less steep, because writing up the content AND bringing it into the right form AND using a merge proposal might be a bit hard for some [17:23] dholbach: well, then you need a parser or something to make it reasonable, or a wyswig editor [17:24] dholbach: Something worth considering, maybe. Simply encourage people to contribute content in some raw format... [17:24] wxl, ok, I was thinking more of a more experienced member of the team who could help with massaging content into the right format :) [17:24] Any plans for markdown, rst or textile support? [17:24] dholbach: i've done it before with training people but it's a PAIN [17:24] Perhaps and editor that converts the content into the right form? [17:24] octoquad: well, moin supports rst, but you add the rst IN the moin, which is stupid because people that don't know rst can't properly maintain it [17:24] We did some summit sessions over a few cycles, particulary when pleia2 was more involved. [17:25] wxl, I see, I suppose better UI editing tools might help to structure the text for someone who doesn't know the raw markup [17:25] dsmythies: ok - did it help at that time? [17:25] We tried to let contributors write in raw format, but it was too much work for others to get it right, so we decided to stop it. [17:25] plans for rst or whatever changes: thsi always comes up. It would be a ton of work and what people want to change to changes every quarter. I want not part of it. [17:26] hannie: Ok.. [17:26] I mean at The Ubuntu Manual [17:26] octoquad: true, true, personally i LOOOOOOATHE moin, but that's another storry [17:26] i *REALLY* think we need to support markdown. it's largely becoming the de facto standard for lightweight markup [17:26] maybe it could be tried in a smaller scale [17:26] perhaps, wiki content should be structured per cycle and cloned on a new cycle, with some type of inherentice of previous cycle text? [17:27] just to see if somebody would be willing to help with formatting [17:27] content stays relevant per cycle [17:27] rst makes sense because it's the canonical python markup, but that doesn't mean anything. i mean, jeez, moin moin is in py and they don't support it :/ [17:27] and better UI tools to manage markdown. [17:27] s/markdown/markup [17:28] i have strong feelings about markup languages. i MAY be interested in helping develop a ui tool [17:28] converting to a new system and build system is a very big investment [17:28] or at least the parser if soneone is more handy with front end [17:28] wxl, what is rst? [17:28] wxl, I'm keen as well [17:28] sak: reStucturedText [17:28] sak, restructured text [17:28] elfy: Summit: Such things always create a stir, but then fades back to normal. [17:28] I see, and its benefits? [17:28] sak: another lightweight markup language like moin moin, markdown, textile, etc. etc. etc. [17:28] sak: oh god, don't get started on the markup wars :) [17:29] The low activity problem tends to end up in endless discussions on markup languages. ;) The principal issue is the low interest in contributing, I'm afraid. [17:29] lol, we are having one now [17:29] sak: the one obvious benefit is that it's a python tool, so python supports it well [17:29] GunnarHj, perhaps that's where the problem arises from? [17:29] I agree with GunnarHj [17:29] octoquad: I doubt it. [17:29] GunnarHj, if things were a lot easier you might get a bit more contributions [17:29] GunnarHj: we have a very enthusiastic new head of docs/wiki in lubuntu. he may be willing to help, but having clear details about what needs to be done would be helpful [17:30] wxl, nice, something I am becoming familiar with [17:30] I just wonder if running a session would help - even if it only results in a couple of new contributors [17:30] a session will always help [17:30] at worst you'll have some sort of presentation you can show to noobs [17:30] especially if it's going to be recorded, people can watch it later on again [17:30] and they are [17:31] that for sure dholbach [17:31] Please note: I am not very IRC savy, and am having trouble keeping up. [17:31] at least given current technology [17:31] dsmythies: that's ok :) [17:31] I think there was a pretty good session for about a year ago which might be resued. [17:31] cool [17:31] if no one in docs has experience with it, i'd be happy to help [17:32] wxl: Thanks, noted. ;) [17:32] training session I have always found helpful. Takes out the guess work [17:32] would it help to help review the current "get involved" docs again to see how understandable they are for a newcomer? or is there anything else the CC could help with? [17:32] dholbach: not a bad idea. i could find some fresh eyes to show them to [17:32] I'd happily run through those get involved docs [17:33] same here [17:33] and probably others in ubuntu-community-team@lists.ubuntu.com :) [17:33] hehehe [17:33] yep [17:33] Sounds great. Looking forward to your feedback. [17:33] :-) [17:33] GunnarHj dsmythies - anything else we could help you with? [17:34] The lubuntu QA getting stared wiki was well written. I can help overview the getting started docs page [17:34] YokoZar, pleia2, mhall119, elfy, czajkowski: any more questions from you? [17:34] Think it's ok for today. Thanks all! [17:34] not from me dholbach [17:34] thanks a lot for your tireless work - I really appreciate it [17:34] Yes, O.K. [17:35] thanks everyone :) [17:35] actually [17:35] I take the meeting is over? [17:35] GunnarHj dsmythies could one of you link me to the instructions on dealing with the manual formatting? [17:35] maybe we should start a discussion on the community team list too, just to see if we can come up with some more ideas to improve the situation [17:35] GunnarHj dsmythies - if one of you wants to point me at the 'start helping' page I'll start looking [17:35] (or bring it up on the community team list) [17:36] just a sec [17:36] ((which might be better)) [17:36] We'll get back on the list. [17:36] sounds good thanks [17:36] thanks a lot [17:36] https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation [17:37] Oh, or on list , per Gunnr [17:37] elfy, are we meeting up with anyone else today? [17:37] https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuDesktopGuide [17:38] dholbach: QA team [17:38] ah cool [17:38] horray for QA team [17:38]