[16:02] <jaakko_kui> hi
[16:03] <mandel> jaakko_kui, o/ ready to start getting things rolling?
[16:03] <jaakko_kui> yes
[16:03] <jaakko_kui> but  a simple todo list needed ?
[16:03] <mandel> jaakko_kui, lets wait for the other two, this channels seems to be a better place, else the conversation is hard to have
[16:03] <fmunozs> hello
[16:04] <mandel> jaakko_kui, I think so, we might agree on this things here, then we can add a branch with and MP with the TODO :)
[16:04] <mandel> fmunozs, hola!
[16:04] <jaakko_kui> hola
[16:04] <mandel> gatox, fmunozs, jaakko_kui so we all know each other more or less (at least what we mentioned in the email)
[16:04] <jaakko_kui> yep
[16:05] <mandel> I think the best way to start is to consider how to reuse the code that we already have
[16:05] <jaakko_kui> agreed
[16:05] <robru> is this the twitter thing?
[16:05] <mandel> I like the idea of jaakko_kui and me doing the cpp code and fmunozs and gatox the qml
[16:05] <mandel> robru, yes
[16:05] <jaakko_kui> is cpp allowed ?
[16:06] <jaakko_kui> js?
[16:06] <robru> mandel, ok, great. I just wanted to point out to everybody that 90% of the work of authentication to twitter and caching downloaded messages has already been done
[16:06] <mandel> jaakko_kui, yes, zoltan recommends to use as much qml js as possible
[16:06] <gatox> jaakko_kui, we need cpp for the keyring stuff and other apis
[16:06] <robru> so all you really need to do is a frontend
[16:06] <jaakko_kui> wow great
[16:06] <mandel> robru, where?
[16:06] <robru> mandel, lp:friends
[16:06] <fmunozs> mandel, I think dennyabrain is part of the team too btw
[16:06] <dennyabrain> ya i am
[16:07] <robru> lp:friends was born from the ashes of gwibber. it started off as a python3 port and then slowly became a complete rewrite. it supports facebook, twitter, flickr, foursquare, and identica so far.
[16:07] <jaakko_kui> welcome :)
[16:07] <mandel> robru, well that is just great, but does it use the twitter rest apis?
[16:07] <dennyabrain> thank you :)
[16:07] <mandel> robru, what lang does it use?
[16:07] <robru> mandel, yes it does use REST APIs, just not the realtime one
[16:07] <mandel> robru, as in, no python on the phone, sorry
[16:07] <mandel> robru, ok, so no support for streams, right?
[16:07] <robru> mandel, it's written in python, but it's not a long-running process. it uses dbus activation to only start when needed.
[16:07] <mandel> dennyabrain, uh, did I forget about you, sorry!
[16:08] <robru> mandel, there is support for streams.
[16:08] <mandel> robru, that is the problem, I was told by the phone team no to use python although python2 and 3 are there...
[16:08] <robru> mandel, lol, we are already using this on the phone.
[16:08] <dennyabrain> no problem, mandel :)
[16:08] <mandel> not that I have anything against python
[16:08] <robru> mandel, lp:friends is already being used by the share app for photo uploads.
[16:08] <mandel> racedo, agh, messy canonical...
[16:09] <robru> mandel, we have qml bindings in lp:qml-friends
[16:09] <mandel> dennyabrain, so, I guess that you have to introduce yourself to the others :)
[16:09] <fmunozs> that's what I supposed, the sharing framework should have relations with the twitter and Facebook app somehow
[16:09] <dennyabrain> umm well i dont know what to say exactly :P
[16:10] <mandel> robru, so at the end, they decided to push for cpp but then used python.. bloody hell
[16:10] <robru> mandel, this project was actually started by barry warsaw some time ago, then I was hired to complete it.
[16:11] <mandel> robru, very well, then I see is waaaaaaya to many people to do just a frontend... but ok
[16:11] <robru> mandel, we are using vala to handle some of the performance-critical stuff and to keep memory usage under control. it's fairly optimised at this point
[16:11] <mandel> dennyabrain, small background is enough
[16:11] <mandel> robru, very well, so we only have to deal with streams witch we may want if we port this to a desktop and deal with the dbus bindings..
[16:12] <dennyabrain> Ok I am an engineer by training and currently working as an interaction designer. I have experience developing interactive applications especially with a focus on sound using c++, processing and arduino
[16:12] <mandel> fmunozs, jaakko_kui, gatox, dennyabrain does what I said make sense?
[16:12] <mandel> dennyabrain, awesome, were are you based, I'd like to have piple to work together if they are in the sime time zone :)
[16:13] <fmunozs> not sure what do you mean with streams, but yea, I see that most of the backend code is already developed by robru
[16:13] <robru> mandel, yeah, so if you want to play around with friends you can get some packages from ppa:super-friends/ppa.
[16:13] <dennyabrain> I am in India right now
[16:13] <robru> fmunozs, mandel, so yeah, our twitter support is not 100%, in particular we are missing photo uploads, so if somebody wanted to work on that, that would be super.
[16:14] <dennyabrain> not sure if anyone else in the team is from around :)
[16:14] <mandel> robru, that ppa, does it support armf (I suppose that the vala bits need to be compiled in the right arc)
[16:14] <robru> mandel, yes, we should have arm builds on there.
[16:14] <fmunozs> robru,  it's good to know that it supports identica too as some have already asked for it
[16:14] <mandel> dennyabrain, so jaakko_kui and I are in europe and gatox and fmunozs in america (latin)
[16:14] <dennyabrain> ok.
[16:14] <mandel> fmunozs, I'd say, lets assume we only deal with twitter atm
[16:14] <mandel> :)
[16:15] <robru> fmunozs, yes, the identica support is beautiful. it subclasses twitter and changes the URLs. very elegant ;-)
[16:15] <mandel> fmunozs, one step at a time
[16:15] <dennyabrain> time is gonna be a problem then :)
[16:15] <fmunozs> mandel, sure
[16:15] <mandel> dennyabrain, not really, I work at crazy times :)
[16:15] <dennyabrain> well yeah same here, so i guess nothing unworkable then :P
[16:15] <mandel> jaakko_kui, how do you see the idea of reusing lp:friends, it does make perfect sense
[16:16] <jaakko_kui> could be ok, not really know about it
[16:16] <jaakko_kui> i should study it
[16:17] <robru> mandel, jaakko_kui fmunozs : if you reuse lp:friends, all you have to do is develop a frontend that displays tweets, all the message downloading and caching is already handled in a nice way.
[16:17] <mandel> jaakko_kui, so there goes an item for the list => Look at lp:friends and decide what is the best course of action :)
[16:17] <mandel> robru, yep, we still need cpp for the dbus calls
[16:17] <gatox> mandel, jaakko_kui dennyabrain fmunozs sorry........ in a meeting..... i'll read everything after the meeting
[16:17] <jaakko_kui> ok
[16:17] <fmunozs> robru, does it handle private messages?
[16:17] <robru> fmunozs, yeah
[16:17] <mandel> robru, AFAIK there are no QML bindings for it, fmunozs is that correct?
[16:17] <robru> mandel, we already provide qml bindings at lp:qml-friends. so you don't even need to make dbus calls directly
[16:18] <mandel> so we are 5 people for just the front end..
[16:18] <robru> ;-)
[16:18] <mandel> when we could be doing two core apps instead of a single one...
[16:18] <robru> well, lp:friends also supports facebook. why don't a couple of you do the facebook app?
[16:18] <mandel> robru, we might want to use lp:friends, test it all the way and add streams to it
[16:19] <robru> mandel, yes please, patches welcome. there is a concept of streams in place already, feel free to expand it to your needs.
[16:19] <mandel> robru, makes sense
[16:19] <mandel> fmunozs, gatox, can you guys work together regarding the initial ui
[16:20] <mandel> fmunozs, dennyabrain can you take a look at lp:friends, check if the ppa generates the .deb for armf and if we can use it
[16:20] <fmunozs> robru, there is a different team for Facebook, I suppose they will have to contact you or redo most of your work by themselves
[16:20] <mandel> I'll ping around to the phablet team regarding the use of lp:friends, but as robru mentioned, it makes no sense not to use it
[16:22] <robru> if you guys have questions about the qml bindings, I recommend speaking to ken.vandine@canonical.com, he wrote them. I know more just about the python backend.
[16:22] <mandel> fmunozs, exactly, I'll speak with dpm about this
[16:23] <mandel> fmunozs, jaakko_kui, gatox ok, I think we have enough to start with, lets try to see if lp:friends is the right tool and the guys in the phablet have nothing against it (I have no reason to doubt robru I'm just surprised this was not communicated)
[16:23] <jaakko_kui> ok
[16:23] <robru> yeah, internal communications has been a bit weak, sorry guys ;-)
[16:24] <fmunozs> we need to  check what is missing from it (i.e photo uploading as mentioned by robru)
[16:24] <mandel> jaakko_kui, since you have no experience with bzr do you want to create a bzr branch with the todo and do a merge proposal
[16:24] <mandel> jaakko_kui, seems like a good way to gt you started :)
[16:24] <jaakko_kui> ok
[16:24] <mandel> fmunozs, yes, I think jaakko_kui and dennyabrain can deal with that, I will deal with politics..
[16:24] <jaakko_kui> i try :)
[16:24] <robru> fmunozs, we already support photo uploading for facebook and flickr, just not twitter yet
[16:25] <mandel> fmunozs, gatox you guys start doing designs and try to merge ideas from the diff work we have so far
[16:25] <fmunozs> ok!
[16:26] <mandel> fmunozs, jaakko_kui, dennyabrain, gatox confirmed by the phablet team, they  use friends, so we stick with it
[16:26] <dennyabrain> ok
[16:26] <mandel> do lets do as planned, 2 for the ui, 2 to investigate the lib
[16:26] <mandel> dennyabrain, jaakko_kui, gatox, fmunozs for you info I have nothing because I'm off to holidays in the mountains so no internet connection :-/
[16:27] <mandel> once I'm back I'll help dennyabrain and jaakko_kui, sounds reasonable?
[16:27] <fmunozs> sounds good
[16:27] <dennyabrain> ya
[16:27] <jaakko_kui> ok :)
[16:28] <mandel> dennyabrain, fmunozs, jaakko_kui, gatox awesome! can you guys send me your blogs etc.. I want do do some announcements and add details about you (mail me to manuel@canonical.com)
[16:29] <mandel> will update the wiki to point you as the official developers of the app etc..
[16:29] <jaakko_kui> ok
[16:29] <dennyabrain> ok. will do
[16:29] <mandel> superb
[16:30] <mandel> I'll send an update to the mailing list about this and will set a new meeting for tuesday, sounds good?
[16:30] <mandel> I'll try to be there but I can't promise a thing
[16:30] <dennyabrain> sure.
[16:30] <jaakko_kui> ok
[16:30] <mandel> jaakko_kui, once you have done the mp please add me as a reviewer in case there is something to help you with, but I'm sure you will be fine
[16:31] <jaakko_kui> ok :)
[16:32] <mandel> jaakko_kui, dennyabrain, fmunozs, gatox catch you all later then o/
[16:32] <dennyabrain> bye
[16:32] <fmunozs> thanks, i'll send you my details later today!
[16:32] <fmunozs> bye
[16:32] <jaakko_kui> bye
[17:01]  * pleia2 waves
[17:01] <jbicha> o/
[17:02] <dholbach> heya
[17:02] <beuno> o/
[17:02] <jbicha> I hope I'm not the only one here from Docs
[17:02] <pleia2> I think hannie is from manual and phillw from wiki
[17:03] <hannie> pleia2, correct, hi to all
[17:03] <jbicha> ok that helps :)
[17:03] <czajkowski> aloha
[17:03] <dsmythies> I am here for serverguide (but never been to any meeting or even IRC before)
[17:04] <czajkowski> thanks for coming folks
[17:04] <pleia2> #startmeeting
[17:04] <meetingology> Meeting started Thu Feb 28 17:04:08 2013 UTC.  The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:04] <pleia2> #chair czajkowski dholbach cprofitt
[17:04] <meetingology> Current chairs: cprofitt czajkowski dholbach pleia2
[17:05] <pleia2> #chair YokoZar Gwaihir
[17:05] <meetingology> Current chairs: Gwaihir YokoZar cprofitt czajkowski dholbach pleia2
[17:05] <pleia2> there we go
[17:05] <czajkowski> smart ;)
[17:05] <pleia2> #topic Docs team catch-up
[17:05] <Gwaihir> o/
[17:05] <pleia2> #chair beuno
[17:05] <meetingology> Current chairs: Gwaihir YokoZar beuno cprofitt czajkowski dholbach pleia2
[17:05] <czajkowski> lol
[17:06] <pleia2> so at these catch-ups with teams we pretty much just check in to see how things are going, if there are blockers or anything we can help with
[17:06] <pleia2> jbicha: can you tell us a bit about how core "official docs we ship" are doing?
[17:07] <jbicha> like many areas of Ubuntu, we are undermanned
[17:07] <jbicha> I think for the Ubuntu Desktop docs though, we are critically undermanned
[17:08] <jbicha> I am intending to resign from being the defacto Docs lead this week, both because I have too many responsibilities now and to make it a little more obvious that we need help
[17:09] <jbicha> I'll be available for the next month or so to help with transition if anyone else wants to jump in
[17:09] <pleia2> seeing that there are folks working on the wiki and other projects springing up like ubuntu-manual, do you think it may partially be an onboarding issue?
[17:09] <dholbach> jbicha, are there others in the team who have taken on leadership roles or started to take care of some of the organisation?
[17:09] <jbicha> I believe other parts are doing a little better (Server docs & the Manual)
[17:09] <beuno> jbicha, interesting, do you have a feeling as to why?
[17:10] <pleia2> (I have seen concerns that "docs are too hard to get involved with")
[17:10] <jbicha> dholbach: for ubuntu-docs itself, not really, just look at the commit log: https://code.launchpad.net/~ubuntu-core-doc/ubuntu-docs/quantal
[17:11] <phillw> o/
[17:11] <jbicha> mdke is still sort of around and he's nearly an expert at this but he's been less active than he used to be
[17:12] <YokoZar> I have heard in multiple places now that the easier you make doc contributing the more likely you are to get results (eg more like wikipedia and less like...well the rest of Ubuntu)
[17:12] <dholbach> is there some kind of TODO list for the docs project?
[17:13] <jbicha> ubuntu-docs (and similarly for the server guide or xubuntu, kubuntu, etc.) does require a fair bit of knowledge: the format (docbook or mallard) is similarish to html but different, bzr and LP have a rough learning curve (even though they are easier than some things), good English skills, and you have to know your topic or devote time to learn it
[17:14] <pleia2> jbicha: is there a "how to contribute" page that defines the skills needed and gives links to resources?
[17:14] <phillw> yeah, I'm not looking forward to bzr and LP :/ Once I've mastered it, I may be help out a bit for obvious typos etc.
[17:14] <jbicha> dholbach: not really, there's some LP bugs and the regular "figure out what's different in Ubuntu this cycle and make updates"
[17:15] <dholbach> pleia2, there's https://wiki.ubuntu.com/Jams/Docs I know of
[17:15] <jbicha> pleia2: it's a bit out-dated but there's some things at https://wiki.ubuntu.com/DocumentationTeam/
[17:15] <dholbach> which might be nice for this weekend
[17:15] <pleia2> yeah, https://wiki.ubuntu.com/DocumentationTeam/Organization#Requirements_for_Ubuntu_Documentation_Committers doesn't even mention mallard
[17:15] <jbicha> for mallard, #docs on irc.gnome.org can help a lot, we've effectively needed to fork the GNOME Desktop Guide for the Ubuntu one any way
[17:16] <pleia2> jbicha: if I drafted some easier instructions, would you be willing to review them so we can get this updated?
[17:16] <jbicha> http://projectmallard.org/
[17:16] <jbicha> pleia2: yes I should be able to review that
[17:16] <hannie> At the manual we use bzr and LP. There are extensive instructions on the manual side and newcomers can ask help via mailing list
[17:16] <hannie> *site
[17:18] <pleia2> (I've been interested in improving this for a while, worked with j1mc a few UDSs ago but unfortunately didn't make a huge amount of progress and he's mostly moved on)
[17:18] <jbicha> the other problem is that when you have people that learn bzr and lp too well, they may jump into contributing elsewhere (like I did)
[17:18] <pleia2> hannie: yeah, I think that helps a lot (and I'll take a look at those again :))
[17:19] <hannie> It really works
[17:19] <jbicha> j1mc might come back if we need him, I think he just thought it's more useful to contribute upstream
[17:19] <pleia2> jbicha: yeah, that's the impression I got
[17:19] <jbicha> he also went against the grain and switched from XFCE *to* GNOME when GNOME Shell came out
[17:19] <pleia2> hehe
[17:19]  * pleia2 just added the Unity keybindings to her Xfce
[17:20] <YokoZar> I am beginning to think most people don't quite get the difference between docs and the manual
[17:21] <YokoZar> or even help.ubuntu.com
[17:21] <pleia2> the docs are help.ubuntu.com :)
[17:21] <jbicha> also if anyone's interested in docs, check out http://openhelpconference.com/ I went last year and it was great, even though it was in Ohio, we had several from Canada and a few from Europe and even further come
[17:21] <pleia2> /community is the wiki
[17:21] <Gwaihir> I think there is some confusion between wiki, the help we ship in the distro, and the manual project
[17:21] <YokoZar> It seems intuitive to only expect one writing source
[17:21] <jbicha> it's run by shaunm, the guy who created Mallard for GNOME
[17:22] <jbicha> bkerensa was working on adding yet another help source using the Mozilla Support framework but that may have been abandoned by now
[17:23] <pleia2> jbicha: what does a release cycle for docs look like?
[17:23] <jbicha> historically we don't necessarily do much until Feature Freeze or UI Freeze, and then it's a mad dash to get things done before Docs Freeze
[17:24]  * pleia2 nods
[17:24] <pleia2> so I'm thinking the rest of the cycle is good time to start getting people up to speed with how to use tools, fixing small errors and things we know changed
[17:25] <dholbach> the current discussion on u-devel@ might benefit the docs team then? :)
[17:25] <beuno> jbicha, had any time to reflect how rolling releases is going to affect this?  :)
[17:25]  * beuno high-fives dholbach 
[17:25] <dholbach> beuno, o/ \o
[17:26] <jbicha> beuno: well at least we don't have to worry about the version number being out of date...
[17:26] <dholbach> what do you think might be a good way to recruit new doc team members?
[17:26] <jbicha> it would also allow someone to contribute at any time and get their work in to Ubuntu fairly quickly
[17:26] <jbicha> but I'm not sure the translators will be very thrilled about that..
[17:27] <pleia2> yeah, I'm thinking docs may still need to stay on some sort of freeze schedule for translators
[17:27] <pleia2> even if it turns into yearly
[17:28] <jbicha> I'm figuring that we'll have some sort of train like the mozilla train and docs freeze may be on the early side to give docs translators time
[17:28] <hannie> Translators usually finish the GUI first, before they start with docs
[17:28] <YokoZar> I'm more worried that without a regular release process we'll simply lose track of what is and isn't irrelevant
[17:29] <YokoZar> So, say new feature X lands in Ubuntu some day; I don't think it's part of anyone's process to go "hmm X replaced Y, we better mark the docs for Y as needing update" or whatever
[17:29] <YokoZar> and indeed the feature landing in Raring may be the first opportunity the docs team has to actually document it!
[17:29] <YokoZar> *raring = rolling current unstable
[17:29] <pleia2> does anyone else attending this meeting have comments about the current status of the doc team? (or Ubuntu docs in general?)
[17:31] <YokoZar> As an upstream Wine guy, I will say that when we moved our FAQ from source control to a wiki it became less than 5 years out of date
[17:32] <YokoZar> wikis have dead pages and obsolete pages and all that entails, of course, but the FAQ itself was reasonably updated
[17:33] <pleia2> the community-maintained docs are pretty extensitive (though there is still a lot that's unmaintained, the wiki team has a tagging system to identify out of date pages)
[17:33] <hannie> Can anyone give me a link to docs-wiki?
[17:33] <pleia2> hannie: help.ubuntu.com/community
[17:33] <hannie> thanks
[17:34] <phillw> o/
[17:34] <phillw> back a while back, there was discussion of having the ability to convert from wiki format to docbook / mallard.... did anything come of this?
[17:35] <phillw> I know there is a convert routine from Vbulletin (forum) to wiki that is up and running.
[17:36] <hannie> you mean https://launchpad.net/~ubforums2ubwiki
[17:37] <phillw> hannie: I assume so, I know of it from the forum guys doing a convert of a tutorial for lubuntu into wiki format (I think we were one of the guinea pigs).
[17:38] <YokoZar> I seem to remember some people saying the migration tools for wiki -> mallard weren't the best
[17:38] <phillw> YokoZar: okies, thanks. Just a line of thought I had :)
[17:39] <YokoZar> phillw: Yeah I think it would be quite nice if that was the workflow and only one person had to bother with mass script conversion, but it doesn't seem to be the case.
[17:39] <phillw> yeah, I have yet to endure learning  bzr / LP / commits etc. But it is on my list of things to do.
[17:39] <YokoZar> It's certainly easier for a less technical person to edit a wiki page and review it periodically than to decipher a new format, bzr, and our merge process
[17:40] <pleia2> for the xubuntu docs rewrite last year we did a mostly manual moin to docbook conversion, it got the docs written (woo, goal!) but docbook conversion fell to one guy and I'm glad it wasn't me :)
[17:41] <hannie> phillw, you can always ask help on ubuntu-manual@lists.launchpad.net
[17:41] <pleia2> phillw: it's less scary once you just dive in, and there are lots of people in the community who can help :)
[17:41] <phillw> hannie: I've got to learn the quality system 1st, but I'm sure most of that will transfer over.
[17:42] <phillw> pleia2: nicholas skaggs has wriiten up some tutorials for me to follow :)
[17:42] <pleia2> yay
[17:42] <phillw> I'm sure they would be of use to help updating the 'intoduction to docs' team as well.
[17:43] <hannie> Has anyone thought of using LaTeX?
[17:43] <YokoZar> pleia2: that seems like something that might be partially automateable
[17:44] <pleia2> YokoZar: yeah, it was "mostly manual" so there was a script that caught a lot of things but then manual fixing of a lot
[17:45] <cprofitt> very good conversation about the docs team
[17:46] <cprofitt> Gwaihir: sorry for scrolling back, but I agree that many do not understand the difference between the manual and the wiki
[17:48] <hannie> What do you mean by "difference"? there is no relation between manual and wiki
[17:49] <cprofitt> hannie: exactly that
[17:50] <cprofitt> the team has people who work on one or the other, or both
[17:50] <cprofitt> but many people looking to join do not realize that both the wiki and the manual are part of the docs team
[17:50] <cprofitt> they are familiar with one or the other of the resources
[17:50] <cprofitt> other people think they have to do both to be on the docs team
[17:51] <pleia2> I don't think the manual is strictly part of the ubuntu doc team
[17:52] <pleia2> the doc team governs official docs that are shipped (and posted to help.ubuntu.com) and the community maintained help wiki at help.ubuntu.com/community
[17:52] <hannie> Ok, I see what you mean. Can you use the Ubuntu weekly to do some explaning on manual and wiki, and contributors needed?
[17:52] <hannie> *explaining
[17:52] <pleia2> hannie: if you give me a blog post link, we'll include it :)
[17:53] <pleia2> (or if you need me to blog about it, I could use some reviewers)
[17:53] <dholbach> is there anything you feel the CC could help you with?
[17:53] <hannie> pleia2, I mean someone from the docs team should write an article on this for the Ubuntu weekly
[17:53] <pleia2> hannie: oh, I see
[17:54] <pleia2> I'll see about writing something up
[17:54] <cprofitt> this wiki page does a nice job, but many do not find it
[17:54] <cprofitt> https://wiki.ubuntu.com/DocumentationTeam/Organization
[17:55] <pleia2> yeah, perhaps just pointing that out would be enough
[17:56] <pleia2> hannie: can I bug you to do a review once I have a draft to make sure it answers your questions?
[17:56] <hannie> pleia2, sure
[17:56] <pleia2> great
[17:56] <pleia2> #action pleia2 to draft improvements to doc team getting involved and have jbicha review
[17:56] <meetingology> ACTION: pleia2 to draft improvements to doc team getting involved and have jbicha review
[17:57] <pleia2> #action pleia2 to draft blog post explaining parts of the ubuntu doc team
[17:57] <meetingology> ACTION: pleia2 to draft blog post explaining parts of the ubuntu doc team
[17:57] <pleia2> no more actions for pleia2
[17:57] <pleia2> anyone else have any comments before we wrap this up?
[17:57] <pleia2> I'm very glad we had this conversation, thanks everyone :)
[17:58] <jbicha> pleia2: thank you
[17:58] <dholbach> yes, thanks a lot everyone! and thanks for your hard work on this!
[17:58] <phillw> nice to touch base with the others, thanks for arranging it pleia2
[17:58] <hannie> do we get a link to the meeting logs shortly?
[17:59] <phillw> hannie: as soon as the meeting ends :)
[17:59] <hannie> right
[17:59] <pleia2> #endmeeting
[17:59] <meetingology> Meeting ended Thu Feb 28 17:59:34 2013 UTC.
[17:59] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-28-17.04.moin.txt
[17:59] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-28-17.04.html
[17:59] <pleia2> ^^ there you go :)
[17:59] <YokoZar> Thank you guys :)
[17:59] <hannie> pleia2, my email is hannie at ubuntu-nl.org
[18:00] <pleia2> hannie: yep, I've got it :) thanks
[18:00] <hannie> see you
[22:00] <Fra_ButBut_> Hello