=== doko_ is now known as doko === fenris is now known as Guest68936 === fenris is now known as Guest62485 === Tonio_aw is now known as Tonio_ === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === fenris is now known as Guest72765 === Guest72765 is now known as ejat === mmrazik is now known as mmrazik|lunch === Quintasan_ is now known as Quintasan === mmrazik|lunch is now known as mmrazik === fenris is now known as Guest89250 === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === mmrazik is now known as mmrazik|otp === mmrazik|otp is now known as mmrazik === Guest75682 is now known as dpb___ === fenris is now known as Guest45110 [17:01] aloha [17:02] hello :) [17:02] beuno, pleia2, around as well? [17:02] only for a few minutes [17:03] o/ [17:03] Today we're meeting with the Tech Board. :) [17:03] so are any of the folks on https://launchpad.net/~techboard/+members her [17:03] *here [17:04] cjwatson, kees, mdz, soren, stgraber: anyone of you around? [17:04] ah right, it's today, well, I was just about to step out to get some lunch :) [17:04] oh, blast - I'm on leave today, can be around I guess but I was hoping somebody else would be [17:05] have just poked pitti elsewhere also [17:05] stgraber: cjwatson we'll make it quick so [17:05] cjwatson, I think mdz mailed us and said he could probably make it [17:05] #startmeeting [17:05] Meeting started Thu Nov 15 17:05:26 2012 UTC. The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:05] 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:05] #topic Catch up with the TB === meetingology changed the topic of #ubuntu-meeting to: Catch up with the TB [17:05] How has the last cycle worked out for the TB? [17:06] pretty good I think, didn't have a lot of things to discuss/review/do really [17:06] We've generally had a pretty quiet cycle, yes - there've been a few things we've been asked to resolve, but fairly low on controversy [17:07] Wow... I read most of the reports from the TB and thought that you actually had a lot on your plate. [17:07] I don't know whether I view this as a success or not [17:07] team reports++ [17:07] will the TBs workload increase with the helping of ARB now? [17:08] My perception has been that most of the things that come to us already have broad agreement, and sometimes we tweak a bit to try to ensure that precedents are set sanely and that sort of thing [17:08] Do you have a lot of internal discussion? Or are you mostly just consulted by other teams or parties? [17:08] the TB only reviews the the ARB processes when they need changes, so that's not taking a lot of time as the requested policy changes usually make sense and aren't controversial [17:08] e.g. the nvidia/fglrx SRUs question, which involved quite a lot of detail but it wasn't a fundamental disagreement [17:09] At the moment, the TB essentially only does anything when issues are brought to us [17:09] mostly just consulted by other teams/parties. The only internal discussion we have are about timezones/dst it seems :) [17:09] Did any of your ever the feeling the TB could have a more active role or is it not of much interest right now? [17:10] Sorry, not active, rather proactive. I didn't mean to say you're all lazy. :) [17:10] We've talked about this several times and kicked around a number of ways in which we might be more proactive, but it never seems to come to much [17:10] The brainstorm review seems to have (unfortunately?) rather fallen by the wayside [17:10] nods I think ye mentioned this at the last meeting up as well [17:11] cjwatson: is this something the TB would like to get back involved in,or do you see it as a role the TB can't take part in any more? [17:11] I feel the CC and the TB are pretty much in the same boat here. One thing we tried to do was inviting teams to our meetings to ensure that things are working seamlessly for everyone. [17:11] But of course several TB members are active on their own accounts anyway [17:11] And that has sparked some good discussions in the past. [17:11] czajkowski: I tend to feel that we may have outgrown the point where a single small board can be sufficiently on top of things everywhere to take an interventionist approach [17:12] dholbach: yes our catch ups are very useful [17:12] cjwatson, I think I agree - we also trust that people simply bring it up with the CC if they feel it's necessary [17:12] +1 [17:13] I'd certainly encourage folks to come to us when they're doing things that are likely to set precedent elsewhere and want a broader perspective - I think that's a valuable role the TB plays [17:13] But realistically we're likely to remain mainly reactive at least for a while, I think [17:13] Is there anything you feel should improve generally in the world of Ubuntu development? Anything you feel should change? [17:13] (Speaking only for myself though) [17:14] I don't think I can answer that from a TB perspective rather than from my personal perspective [17:14] Maybe stgraber can have a go :) [17:15] Or maybe something the TB might need help with? [17:16] If not, that's perfectly fine - I just thought it polite and interesting to ask. :-) [17:16] I can't really think of anything for either questions ;) [17:17] Not really - I suspect newer folks may be afraid to ask us things when they should [17:17] But I don't know if that's immediately fixable :) [17:17] thanks cjwatson [17:17] and stgraber [17:18] Again we're in the same boat with the CC, I think only personal encouragement works there. :) [17:18] Yeah [17:18] thanks a lot for your hard work [17:18] I'm very pleased to hear that things work out nicely for you. [17:18] cjwatson, enjoy the rest of your day off :) [17:18] I'm being summoned though so I'm afraid I'll have to go :) [17:18] Sorry, bad leave timing [17:18] no, it's all good :) [17:18] thanks for making time [17:18] Thank you [17:18] #topic Any other business === meetingology changed the topic of #ubuntu-meeting to: Any other business [17:19] https://wiki.ubuntu.com/CommunityCouncilAgenda seems very empty. [17:19] so maybe we just give a quick update on the CoC v2 [17:19] nods [17:19] we did two rounds of feedback for https://code.launchpad.net/~sabdfl/ubuntu-codeofconduct/v2-draft and it looks like everyone is sufficiently happy with it [17:20] so we're in the process of getting it into LP and on the website and will announce it once it's there [17:20] thanks a lot to everyone who helped put the update together! [17:20] yes it's nice to see the work finally coming together [17:20] we have the annoucement almost done [17:20] and the bug on website update filed [17:20] dholbach: what is left to get it into LP ? [17:20] I filed a merge proposal and it's WIP [17:21] https://code.launchpad.net/~dholbach/launchpad/coc-2.0/+merge/133702 [17:21] Rick Harding had a look at it already [17:21] so we're slowly getting there [17:21] cool [17:21] apart from that I'm happy to say that the community related sessions from UDS were great and that everyone seems to be busy working on the work items we agreed on there [17:22] it's nice to see how smoothly things are running [17:22] hey cprofitt [17:22] does anyone else have anything we should discuss here in the CC meeting now? [17:22] hey dholbach and everyone... sorry for being late [17:22] cprofitt, don't worry - looks like we wangled it :) [17:22] nothing from my side... [17:23] nothing from my side as well [17:23] in that case, it looks like we just need to put together the minutes and update the wiki, but we can do that outside the meeting [17:23] thanks a lot everyone for turning up! [17:23] lovely [17:23] #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 [17:23] Meeting ended Thu Nov 15 17:23:47 2012 UTC. [17:23] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-15-17.05.moin.txt [17:23] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-15-17.05.html [17:23] thanks dholbach [17:23] thank YOU [17:24] thanks dholbach === Tonio_ is now known as Tonio_aw [18:02] mfisch, mhall119: ready? [18:02] yep [18:04] we'll wait some more time for Mike [18:05] cielak: yup [18:05] oh, cool ;) [18:05] #startmeeting [18:05] Meeting started Thu Nov 15 18:05:14 2012 UTC. The chair is cielak. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [18:05] 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 [18:05] sigh [18:05] nevermind [18:05] what? [18:05] ? [18:05] okay, so here is the agenda: https://wiki.ubuntu.com/Accomplishments/Agenda [18:06] #link https://wiki.ubuntu.com/Accomplishments/Agenda [18:06] first thing I'd like to consult concerns what we clarified on UDS [18:06] I think the chair has to do that [18:06] ok [18:06] that the accomplishemnts should not be level-based [18:07] #topic Discussing whether general direction of project applies to the whole sysytem or just community accomplishments. [18:07] I think that was the direction we came back to yes [18:07] ^ cielak try pasting that [18:07] #topic Discussing whether general direction of project applies to the whole sysytem or just community accomplishments. === meetingology changed the topic of #ubuntu-meeting to: Discussing whether general direction of project applies to the whole sysytem or just community accomplishments. [18:07] oh, cool [18:07] so, just to fill me in, what is the general direction that was talked about? [18:08] okay, so my idea is that we may do the platform support level-based accomplishments, but disable this feature for community accoms [18:08] this way third-party collections could make use of 'dificulty' fields in .accomplishment files [18:08] but we would leave them unused for ubuntu-community-accomplishments [18:09] how would that field be used in the view/gallery? [18:09] sorry i'm late for the meeting, bad traffic [18:10] I think that the details page might display a number of stars (1-5) for accomplishments etc, but that's more a design question [18:10] what I mean is that it might make sense to implement support for such thing in the daemon, but since it's not cool for community accoms, this field would be not used for them [18:11] and in case of community accoms a 'N/A' would be displayed instead of stars [18:11] does that make sense? [18:11] hey s-fox :) [18:11] and this would be enforced just be the approval process accomplishments go through? [18:12] I am not sure how this applies to approval process [18:12] I want to avoid special logic for the community apps [18:12] accomps I mean [18:12] I mean, there wouldn't be something in the code that tries to stop it from being used for community accomplishments, right? [18:13] true [18:13] ok [18:13] the accoms themselves would just leave it out [18:14] I'm not sure if there is any special logic, just as field 'tips' is optional, so would 'difficulty' (or whatever) be [18:14] right [18:14] makes sense [18:14] I'm +1 on that [18:14] I have no objection to this [18:14] cool, thanks :) [18:14] I have also recently looked in how we can make daemon a DBus service, and I have two concerns about this solution [18:15] #topic Feedback on starting the daemon as a dbus .service, causing it to be running regardless of user will. === meetingology changed the topic of #ubuntu-meeting to: Feedback on starting the daemon as a dbus .service, causing it to be running regardless of user will. [18:15] what are the concerns? [18:15] the point is that once we install a .service, the daemon will always be started when user logs in [18:15] Why? [18:15] currently we give him a choice, and automatic startup is disablable [18:15] no, I think it can be only on-demand [18:15] yes it can be on-demand [18:16] when the first dbus call is made, dbus will launch it [18:16] and honestly that is standard operating procedure for almost everything [18:16] lenses and scopes for example [18:16] hm, that's odd, from my tests it was always starting regardless of whether it was requested or not [18:16] so the "automatically at startup" would just call the dbus service during session startup, otherwise it waits until the user loads the viewer [18:17] cielak: do you have the Unity trophy lens? [18:17] I do [18:17] that's probably starting it [18:17] thats whats launching it then [18:17] aaah! this makes a lot of sense [18:17] I'm not even sure we need an automatically at startup field anymore [18:17] so I'll be back to playing around with it, then ;) [18:17] it only makes sense as an option if the user doesn't have the lens [18:18] if you have the lens, it'll need to be running from startup [18:18] do we get notifications if the service is running but the app is closed? [18:19] another thing I have notices with DBus (yet this problem was present even before I tried setting up a service) is the way the daemon is closed when user session ends [18:19] I have discussed that with mfisch few weeks ago [18:19] what was the issue? [18:19] what I ended up with, is that for some reason the daemon is killed when user logs out [18:20] the session is over at that point [18:20] it does not receive a SIGTERM, it's simply killed [18:20] does it need to do any cleanup before it exits? [18:20] yeah, it does [18:20] for what? [18:20] removing the pidfile is a must [18:20] it doesn't get any signal? [18:20] what is the pidfile used for? [18:21] yeah thats a good question, I bet we dont need it anymore [18:21] otherwise, if the pidfile is left, there is no way to distinguish if the daemon is running or not [18:21] sure there is [18:21] you query it on dbus [18:21] if we only start it via dbus, then dbus handles that [18:21] what if it got stuck? [18:21] and "autostart" is handled by a simple dbus message too, not by manually launching it [18:21] dbus won't launch a new process if one is running [18:22] ah, so again it's dbus who cares about that stuff [18:22] I think that the service getting stuck is another issue [18:22] yeah, once we let dbus launch us, we should let dbus handle everything [18:23] yeah, so basically what jono did with cron and pidfiles, dbus does automagically [18:23] having us manually start or kill a process that dbus started will lead to bad news [18:23] yes [18:23] and dbus does it better ;) [18:23] odd that despite studying dbus for a week I have not discovered it's core goodies :) [18:23] you could study it for a year and still find surprises ;) [18:23] I've been debugging a dbus signal issue all week [18:24] okay, so the conclusion is that I need to learn DBus more before I start playing with it at all, hehe ;) [18:24] playing makes you learn faster [18:24] breaking makes you learn faster still [18:24] I think it's simpler than that [18:24] remove all the cronjob/pid file code [18:24] change autostart from a launch to sending a dbus message [18:24] that will force dbus to start it [18:24] then you're done I think [18:25] mfisch: actually, no way to remove it, as twistd relies on the file not existing [18:25] do we still need twistd? [18:25] ooh, porting the code out of twistd now would be a really great deal [18:25] I guess we do [18:25] what else does twistd give us? [18:26] what is twisted used for? [18:26] all that @deferred stuff is twisd magic [18:26] I don't know enough about the daemon internals to know [18:26] and it's meant to ensure our code is not multi-threading etc. [18:27] don't get me wrong, I'd LOVE to get rid of twistd [18:27] make jono re-write it in go [18:27] this needs more investigation [18:27] :) [18:28] I vote that we investigate more and revisit this [18:28] mfisch: +1 [18:28] +1 [18:28] okay, so let's move to next topic on my list [18:28] #topic Sync up with the team on the idea of expanding the .accomplishment format to support keywords/tags. === meetingology changed the topic of #ubuntu-meeting to: Sync up with the team on the idea of expanding the .accomplishment format to support keywords/tags. [18:29] have you played with my latest MP for the viewer? I know mfisch did [18:29] cielak: I need to respond to you, will try to do that tonight [18:29] mfisch: cool ;) [18:29] I haven't, no [18:30] mhall119: basically it implements much quickler filtering + a search feature [18:30] and I'd like to go one step further with te search feature [18:30] cielak: still using iconview? [18:30] currently it looks just in the accomplsihment title, and because of that searching for 'CC' will not find community-council accoms [18:30] mhall119: still! [18:31] mhall119: the magic is to use GtkTreeModelFilter and never clear the main model [18:31] my idea is that we may want to add an optional 'keywords' field in .accomplishment files [18:32] which would list synonyms, common typos etc. for the accomplishment [18:32] so that the search feature could check the title and the keywords [18:33] +1 for keywords [18:33] that's gonna be easy to implement, yet I think all changes to .accomplishments format are worth discussing :) [18:33] +1 too for keywords [18:33] awesome, thanks for your feedback ;) [18:33] lets file bugs to go back and add keywords to existing accomps too [18:34] exactly, I guess this is a cool assignment for a new contributor [18:34] tag the bugs with "bitesize" [18:34] quite easy, and helps to get familiar with accoms structure [18:35] having bitesize bugs makes it easy to point new contributors to a list of things they can do [18:35] and since we are speaking about new contributors... [18:35] #topic Looking for opportunities for new contributors and discussing how we should deal with suggesting work to them. === meetingology changed the topic of #ubuntu-meeting to: Looking for opportunities for new contributors and discussing how we should deal with suggesting work to them. [18:35] so i was thinking some about this [18:35] there is at least 3 people who are willing to contribute [18:35] and the current process of doing a MP and what-not may be causing people to not contribute [18:36] some of them are not interested in comtributing accoms, and I think they are very welcome to do some hacking in the viewer etc. === yofel_ is now known as yofel [18:36] ah I was thinking of accomps writers [18:36] mfisch: so you have ideas on how we can improve accomps writers experience? [18:37] no great ideas, but I wonder if the LP merge process is stopping people [18:37] so in my experience, this is what I'd recommend: [18:37] perhaps the script writing is also a problem [18:37] mfisch, the merge thing was akward to learn, but not that difficult once you get your head around it [18:37] that is my experience anyway :) [18:37] 1) Give a list of specific targets (like adding keywords to existing accoms) [18:38] 2) Give detailed step-by-step instructions for how to do it [18:38] on the other hand, there was noone who contacted us in terms of not being able to send their contribution [18:38] 3) Give detailed step-by-step instructions for how to submit it (bzr commit, bzr push, create an MP, etc) [18:38] 4) Blog about it (get jono to promote your blog post) [18:39] 5) Mosty importantly, publicaly thank the people who do contribute, seeing others get praise motivates people to get involved too [18:39] I'd like a blog post to include some specific ideas for ones people can write [18:39] I know we have a todo list somewhere [18:40] mhall119: agreed, except for the blog part this is what I usually do [18:40] I guess that's what mhall119 said in 1) [18:40] mfisch: I have some more bitesize bugs to fill in [18:40] http://mhall119.com/2012/02/contributing-to-unity-for-non-developers-keywords/ is an example you can look at, I got a lot of new contributors adding keywords to .desktop files with that [18:40] where is ours todo list so that I can add this ideas there? [18:41] mhall119: ooh, cool guide, we surely need something like that [18:41] cielak: write one ;) [18:41] lets take a todo for that [18:41] I surely will [18:41] I can help write it, just worried about over-committing to stuff right now [18:42] nexus7 is still crazy [18:42] mfisch: fix the primary-mouse-button-getting-stuck bug :P [18:43] If I recall correctly, the accoms-writing guide had detailed instructions on how to use bzr to submit changes [18:43] they may need refreshing, though [18:43] any more ideas on what simple activities we may assign to newcommers? [18:44] also, smartboyhw wanted to contribute new accoms, but we're running out of reasonable ideas [18:44] nope, just make sure you always give an over-abundance of information. People don't get discouraged by being told what they already know, but they will get discouraged if they're not told something they do need to know [18:44] yeah, totally :) [18:45] there's got to me hundreds of ideas for desktop [18:45] install ubuntu on ARM is one I'm a fan of [18:45] +1 for desktop, just get people to go through the apps on their Launcher and think of accomplishments they can write for each [18:45] https://wiki.ubuntu.com/Accomplishments/AccomplishmentIdeas/LocalAccomplishments [18:45] this may be worth refreshing too [18:46] One benefit of the "write something for an app on your launcher" is that they will be targetting an app they commonly use [18:46] cielak: lets take an action to update that wiki page with ideas [18:47] someone might have no interest in deja dup or gwibber, but if they have Tomboy notes stuck to their launcher, they would probably know what kind of accomplishments to write for that [18:47] agreed [18:47] "Tomboy didn't erase my notes for 3 months" [18:48] also, we talked at UDS about getting new icon images for people to use, that would be a good way for artists to get involved [18:48] mfisch: oh come on now [18:48] we should make them something possible [18:48] lol [18:48] I guess Martin took the artwork work item [18:48] * mhall119 happens to love Tomboy and hasn't lost anything in years [18:48] cielak: yeah, but there are more artists than just him [18:49] sure :) [18:49] I thought it might be appropriate to contact him and suggest he lead the artwork update [18:49] is there a website other than the wiki for the Accomplishments project? [18:49] it may be easier for him to reach for other artists and cooperate [18:50] nope [18:50] except for trophies.ubuntu.com [18:50] if he has time, he took several work items this UDS [18:50] anyway, contacting him would be fair [18:51] yeah, maybe he could write a blog calling for more artist contributors [18:51] indeed [18:51] you know i could ask the arty types on the ubuntu forums for help if you want. [18:51] s-fox: that's a good idea too [18:52] we might want a list of "wanted" images [18:52] i mean they are great for producing icons for developers [18:52] I'm thinking we could use a Ribbon, a medal, a certificate, etc [18:53] maybe a couple variations on the current trophy image [18:53] I know what i'd like to see, have the ask ubuntu icons match what they are on the website [18:53] +1 [18:53] +1! [18:53] all of that should go into a call for artist contributors, so they have a list of things they know we want [18:54] for the askubuntu ones, someone would need to check on copyright license for them [18:54] mfisch: ^^ [18:54] ok [18:54] thanks [18:54] we can ask jorge [18:55] ok, I can do that [18:55] even if we can't use those exact icons it would be good to have something like a ribbon? [18:55] yeah [18:55] also, let's ask for these in SVG, so we can easily re-color them, or add to them, etc [18:55] +1 [18:55] svg is a must [18:55] we might want to change icon size one day [18:55] + it is different in the lens [18:56] i thought svg was just for vectors? wouldn't we want something like a psd or whatever gimp uses? [18:56] we can render svg though [18:56] ahh :) [18:57] svg would be just as good, just edit it in Inkscape [18:57] indeed ;) [18:57] with 3 minutes left I should ask if anyone has something else to discuss? [18:57] s-fox, any progress on forum accomplishments? [18:58] not touched it cielak , it looks like the ubuntu forums might actually be getting the upgrade soon so the html might change [18:58] ooh [18:58] ideally the accoms would be html-independent [18:58] I am not sure how much this is doable, though [18:58] trying to get an idea as to when it will happen. no point spending time on making it work when the structure of the page might change [18:58] true [18:59] especially if it looks like it might come in before the new year [18:59] speaking of that, cielak I'm going to wait on pep8 until your search stuff is done [18:59] i am looking forward to doing more with regex though! :D [18:59] then again, the search stuff is waiting for your review ;) so whenever you'll have some spare time [19:00] s-fox: wasn't there a forums API we were going to get? [19:00] mhall119: haha! [19:01] mhall119: let me find you the link to the ticket [19:01] mhall119, we were met with silence. twice i believe [19:01] ah, ok [19:01] nvm then [19:01] mhall119: https://rt.ubuntu.com/Ticket/Display.html?id=19790 [19:01] jono even poked them for a response [19:02] we can't wait endlessly, so we'll use a workaround [19:02] ok [19:02] okay, anyone has something more to discuss? [19:03] maybe channel promotion ? [19:03] what do you mean? [19:03] mind you , i suppose that would come with getting more people involved with the project anyway [19:04] likely ;) [19:04] okay, so thanks everyone for coming and your feedback, have a nice day! [19:04] #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 [19:04] Meeting ended Thu Nov 15 19:04:57 2012 UTC. [19:04] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-15-18.05.moin.txt [19:04] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-11-15-18.05.html [19:05] thanks cielak [19:06] thanks cielak === Zilvador_ is now known as Zilvador === tiagohillebrandt is now known as tiagoscd === tiagoscd is now known as Guest13392 [21:58] Zilvador: are you here [21:59] cjohnston, Yes I am [21:59] ping Zilvador :) [22:00] pong s-fox :) [22:00] hi, we just wanted to check you were around since you are only candidate [22:00] lol [22:01] I see [22:01] Zilvador: will be another minute or two [22:01] No problem [22:01] waiting on the last person to get home [22:02] we're all on 3g apparently. haha [22:02] So high-tech :) [22:04] o/ PabloRubianes [22:04] hi s-fox [22:04] PabloRubianes, you at home now? [22:04] yes [22:04] PabloRubianes: are you able to chair? [22:07] #startmeeting [22:07] Meeting started Thu Nov 15 22:07:59 2012 UTC. The chair is s-fox. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [22:07] 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 [22:08] Mwhahaa [22:08] #voters s-fox cjohnston PabloRubianes micahg [22:08] Current voters: PabloRubianes cjohnston micahg s-fox [22:08]