14:37 #startmeeting 14:37 Meeting started Thu Mar 24 14:37:35 2016 UTC. The chair is davidcalle. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:37 14:37 Available commands: action commands idea info link nick 14:37 o/ 14:38 hey :) 14:38 o/ 14:38 all right... shall we get started then - thanks a lot for filling out the agenda already 14:38 before we go into the agenda, can we quickly go through the original request if anybody has questions about it 14:39 sure 14:39 so that we are on the same page on what we should discuss today 14:39 knome: I thought the original request was well written and stated the issues well. 14:39 (i expect everybody has read the original mail, so fire away questions) 14:39 Yeap 14:40 The pad is already very clear 14:40 I stated one objection to the original request in a comment on the pad. 14:40 I'm a bit confused 14:40 the proposal seems to be mostly about getting somebody from the Canonical Community team to be assigned to lead the doc team, and then there's a number of specific issues relating to docs themselves which are on the agenda 14:41 hey guys, sorry for being late 14:41 * mhall119 reads the backlog real quick 14:41 GunnarHj, it's likely the inability to make decision has affected the community help wiki the most, but essentially we are again seeing discussion to moving to some other markup with the serverguide instead of seeing actual contributions 14:41 GunnarHj, so i wouldn't say it's only the community help wiki; of course, i'm not particularly involved with the desktop or server docs 14:42 Well, let's drop that discussion. It won't lead us forward anyway. 14:42 dholbach, that's the agenda dpm set up, and people built on 14:42 dholbach: I understood this meeting to be mainly about getting help. 14:43 ok... 14:43 it looks like we have different expectations and not everyone sees themselves represented by the agenda? 14:43 or am I misunderstanding things? 14:43 Not my case 14:43 dholbach, i totally agree that we should keep more on the meta level than talk about actual tasks to be worked on (though i understand that at that this point it would be essential to get the desktop guide for the LTS in at least some kind of good shape, and that might already require help from canonical) 14:43 dholbach: so I don't think the request was specifically for someone in our team (canonical community team) to step up to lead the docs team, just for somebody within canonical to do so 14:43 dholbach, talk about not being able to make decisions... :) 14:44 I merely filled out dpm's thing about 16.04, but it doesn't matter. 14:44 dholbach: The agenda is fine. Let's move on. 14:45 pleia2: are you around to join this meeting? 14:45 ok, let's use the agenda then - feel free to add more items if your item is not covered 14:45 mhall119, she's jetlagging and probably sleeping 14:45 ah, right, ok 14:45 who wants to talk about the first item? 14:45 i don't. 14:46 dholbach: first item being "Pending tasks for 16.04"? 14:46 can you ping me when we've covered that? 14:46 I said what I wanted to say in the etherpad itself. 14:47 Yes knome 14:47 I have one question about the first item: names next to tasks. Eg dsmythies1 is the first taks "assigned" to you and you are looking for help, or is it a topic you want to raise? 14:47 As regards the status of the desktop guide (which initially triggered this meeting) it's under control. Doug added the pending items to the agenda. 14:47 I was just saying who will do it. No help required. 14:48 Ok 14:48 The list might not be complete, I just wrote what I do (and one Gunnar thing). 14:49 dsmythies1, are there any blockers regarding the desktop guide, apart from it being still quite a bit of work? 14:49 can the community team ask for some assistance with the documentation from people who work with those specific areas? 14:50 dholbach: No blockers. 14:50 eg. so that dsmythies1 doesn't have to do all the work? 14:50 knome: we can, it would help a great deal to get very specific needs 14:50 knome: that's what I was going to ask: do you need us to raise awareness about eg. the server guide? 14:51 For my part of it, I lost months tryign to get a good 16.04 server (and desktop) going with which to work on. But no, not blockers now for desktop. Blocker for serverguide was inability to build PDF, but solved this morning. 14:51 here's how i think it should go: 14:51 like "Adding network printer of ipp docs have outdated instructions from 10.04" 14:51 canonical employee works on application/area X 14:51 rather than "printing docs need updating" 14:51 knome, that part is understood 14:51 canonical employee makes sure the documentation for application/area X is in order 14:51 knome: that's not generally how canonical employees work 14:51 It is there something to talk about concerning the first item then? 14:51 mhall119, can we make some generalisations and not focus on the minutiae? 14:51 mhall119, because i don't think that's helpful at all 14:51 knome, it's important to understand this 14:52 knome: I think focusing on details is what's needed now 14:52 okay... 14:52 we basically have little idea how the team is run 14:52 let's make an example 14:52 serge works on LXD for canonical 14:52 I am grateful for the explanation earlier 14:52 knome: there isn't one canonical person responsible for application/area X 14:52 --> serge works with the docs team to make sure the docs are up-to-date 14:52 mhall119, i understand and know. 14:53 another example: 14:53 dsmythies1, did you reach out to the desktop team and their communications channels about this already? 14:53 mhall119 makes a change in some package he doesn't usually work on 14:53 --> mhall119 works with the documentation team to make sure the change is documented 14:53 mhall119, does that make sense to you? 14:53 currently, changes are landed and the documentation team mostly works on the documentation changes without canonical involvement 14:54 dholbach: That would be more something that Gunnar would typically do. 14:54 knome: in that scenario, does the developer update the docs, or tell someone from the docs team what changed? 14:54 i'm not saying the canonical employees need to write the documentation, but some cooperation would be helpful; especially in the case that the documentation team can't handle all the tasks in time 14:54 dsmythies1, do you know if any coordination or any reaching out has already happened? if not, we should note down we still need to do that 14:54 mhall119, ^ see last comment for answer 14:54 I don't think that's the kind of involvement we need from Canonical. We just need someone to coordinate the effords. 14:55 guys 14:55 knome: Yes. We have very much a"you try and it and discover for yourselves" approach right now. 14:55 what we're discussing here is coordination 14:55 so please let's go through this one by one 14:55 dholbach: What do you mean by "coordination or any reaching out"? 14:56 * knome waits for dholbach to tell who can speak then 14:56 GunnarHj, my first impulse was to talk to the desktop team or mail their mailing list and see if there's anyone who could help with the screenshots 14:56 dholbach: I made a "call for help" request on the docs list, and we did the most necessary work already. 14:56 knome, I was under the impression we used the agenda now 14:56 GunnarHj, ok... so the screenshots for the desktop guide are done then? 14:56 dholbach: Doug will do the screenshots. It's under control! 14:56 dholbach, okay. 14:56 ok, great - sorry for the confusion then 14:56 dholbach: I will do the screenshots. I have doen them for many cycles now. 14:57 thanks a lot dsmythies1 14:57 hoeever... 14:57 thanks dsmythies1, do you have a script or workflow that you use which others can follow? 14:57 let me say something. 14:57 sure 14:57 the issue with the screenshots is that we have to do them so very very late in the cycle. 14:58 mhall119: I do not use a script. 14:58 the script has always been a waste of time, in my opinion. 14:58 GunnarHj, I was just thinking of the desktop team list because I know there's lots of subscribers, some only listening in, and maybe somebody to help with screenshots (or related work) could maybe recruited there the next time :) 14:59 I set up a minimum szed screen, for maximum left over resolution after re-sizing. 14:59 dholbach: Possibly. But we are talking about 5 screenshots or so.. 14:59 oh ok 14:59 in that case that's not necessary O:-) 14:59 I think that's a trivial problem right now 14:59 ok, cool 15:00 GunnarHj, what are the desktop master files? 15:01 dholbach: https://code.launchpad.net/~ubuntu-core-doc/ubuntu-docs/trunk 15:01 dholbach: I meant the master bzr branch in Launhpad 15:01 and what needs to be updated on those? 15:01 are there MPs or bug reports or something that lists what needs to be done? 15:02 mhall119: The screenshots, translations, and we are done. 15:02 cool - are the translations teams busy with the translations already? 15:02 mhall119: No, this is now the regular release procedure. No MP or bug report. 15:03 dholbach: Hope so. The tempate is in Rosetta. 15:03 GunnarHj: is there a list of screenshots that need to be updated? 15:03 maybe somebody could ping the team another mail? 15:03 mhall119: I have not decided yet which screen shots need to be re-done. 15:03 dholbach, there are problems related to translation teams "working", but dpm told it was off-topic for this meeting; i've added the item to the agenda again though. 15:04 mhall119, dholbach: Please!!! dsmythies and I have it under control. No extra action needed! 15:04 ok, let's move on to the next item then 15:04 What is the most important think to talk to? start there! 15:04 GunnarHj, sorry, we're finding our way around here and wanted to make sure the points on the agenda are well understood 15:05 About sorry 15:05 GunnarHj: we were asked to help the docs team, in order to do that we have to understand the state of things, which is why we're asking all these questions 15:05 dholbach: No problem. But I just want you to know that we did some work after the CC meeting when we said that no work had been done yet. 15:06 whoever is adding items to the agenda, please add it as the last item. 15:06 shall we talk about the server guide then? that seems to be next on the agenda? 15:06 doko bdmurray robru cyphermox: hi, looks like there's another meeting in progress here; #ubuntu-meeting-2? 15:07 sorry slangasek 15:08 serverguide is in trouble. it is falling behind reality. We only started doing anything with it after string freeze. 15:08 dsmythies1, can i suggest something that you likely agree with? 15:09 knome: Go ahead. 15:09 dsmythies1: at the risk of sounding like a broken record, is where a list of what specific things need updating on the server guide? 15:09 instead of talking about the work items we need to take, could we talk about how this situation doesn't repeat again with the next release, and what kind of cooperation from what teams would be needed 15:09 I agree with knome in that regard 15:10 mhall119: wait a minute... 15:10 since that was the intention of the original mail we have written and sent with lyz 15:10 knome: I am wrtting... 15:10 no hurry. 15:11 knome, AlbertoSalviaNov: if we understand better what needs doing, we can note it down and figure out where we can bring people together to solve this 15:11 dholbach, i'm sure actionable work items will bring up within the discussion 15:11 *will be brought up 15:12 We simply know that nobody is really in charge of the documentation, and that is all. 15:12 If I could go back to knome's earlier point: Myself, I think person X works on some serever aspect. Person X MUST supply documentation. The "toss it over the fence" approach does not work. I mean I just sued systemd for the first time two months ago. 15:12 We do not need further analysis. 15:12 AlbertoSalviaNov, I think we do 15:12 dsmythies1, instead of "MUST supply", i would say "must cooperate with the documentation team" 15:12 mhall119: : https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide 15:13 dsmythies1, ultimately, that might mean supplying the documentation though 15:13 knome: The difference between the serverguide and others is that we need Subject Matter Experts. Often the docs team has no lcue how to write the stuff. 15:13 right 15:13 no clue 15:14 dsmythies1, ack, though i see the same issue with the desktop docs 15:14 dsmythies1, or at least the part that changes are not made known, and no cooperation effort is offered 15:14 mhall119: We also have put out requests for help on the serverteam e-mail list and on Ubuntu forums, a few times now. 15:14 maybe it's easier to figure out the desktop doc stuff 15:15 dsmythies1: this is exactly what I was looking for, thanks! So the items in yellow and red are the ones that need help? 15:15 so the way I would normally approach a situation where team A and B need to work more closely together would be to put together a list of items, discuss early on which items might be subject to change, and track the list during the cycle 15:15 and I think we can help in bringing the docs team people together with folks who do that 15:15 dholbach, one of the problems related to that is that some changes land very late in the cycle and are unannounced before it's too late 15:15 Not working closer is not the cause but the consequence, of not having a coordinator. 15:16 mhall119: They are the higher prioities, yes. pmatulis's original e-mail list items by priroity. 15:16 and if at some stage we find there's not enough time, we could do something like: dev from team A provides some pointers, or the point is discussed on team A's mailing list and we try to rope others in 15:16 knome, the team managers should know around UOS or some weeks later which blocks they're going to land 15:16 dholbach, weight on the word should. 15:16 so that time should be good to discuss the plan 15:16 knome, mh? 15:16 dholbach, i'm sorry to have "an attitude", but that's the reality 15:16 dsmythies1: it looks like most are in need of review, is that something you need the developers to review, or something the docs team reviews? 15:17 knome, look - I can't change the reality of a fast moving project 15:17 dholbach, also please note that a plan isn't enough for the docs team to start working 15:17 dholbach, say, take the gnome software inclusion 15:17 I think we need to start with a plan to bring people together 15:17 knome, please 15:17 dholbach, we still don't know if it's in its final stage, but it's past the documentation freee 15:17 dholbach, please what? 15:17 I know 15:17 but we can only plan for what we do know 15:17 dholbach, i'm just pointing out the details. 15:17 * dsmythies1 tries to keep up... 15:17 and I think that a plan and some more discussion would help a lot already 15:18 knome: does the docs team currently have regular meetings with the engineering teams? 15:18 mhall119, none at all. 15:18 knome, I've been part of this project for 11 years now - don't you think I know that some stuff lands very late? I'm unhappy about this too and I'm sorry for anyone who has to do the work catching up. 15:18 but I'm really trying to help here 15:19 and I think that an early plan, discussed with the right people and some regular catchup will be an improvement 15:19 knome: does the docs team have regularly scheduled meetings of their own, where we can invite the engineering teams? 15:19 mhall119, not regularly scheduled, and when they happen, often not many people are able to attend 15:19 ok, that's one of the first things that I think needs to happen 15:19 So, again, that's not the problem 15:19 dholbach, i don't disagree. 15:20 mhall119: There were regular docs team meetings, but not currently. We miss a leader/coordinator. 15:20 knome, good :) 15:20 mhall119: For the serverguide, we need developers to review. I can give a couple of examples, which will also relate to knome's points. 15:21 dsmythies1: ok, with your detailed list we can take that to the engineering teams and ask them to assign somebody to review each one, I can't imagine a single page review would take very long 15:21 Example 1: Samba: A major component has been dropped, well after the start of 16.04. Cost me about a month trying to make my server work. Need developer to update that chapter. 15:22 mhall119, it would help if there was a clear understanding on what should be on the agenda, and then stick to it too. 15:22 GunnarHj: how frequent were those meetings in the past 15:22 ? 15:22 weekly, bi-weekly, monthly? 15:22 mhall119, understanding and agreement, that is. 15:22 mhall119: monthly 15:22 knome: for this meeting, or for regular docs team meetings? 15:22 mhall119, both :) 15:23 Example 2: from 14.04: The change for wen server file to default was changed from /var/www/ to /var/www/html so bery late in the cycle that we had already reviewed that chapter. Then it was broken. 15:23 I personally think meetings are not needed: you just bring topics inmediately as needed, as you write documentation inmediately when a change takes place. 15:23 AlbertoSalviaNov, i disagree. 15:23 for the regular meetings, I think doing something like the CC does and pre-schedule checkins with the various engineering teams so you can talk to them about what they're landing and what docs will need to change because of it 15:23 Maybe we could try something like this next cycle: review the ToC early on in the cycle, figure out which will likely need updating, have regular catchups (be it by mail, IRC or whatever) with the relevant managers of the engineering teams to track progress and define an escalation process. This could also be brought up on the desktop or server lists to get others involved and more help? 15:24 mhall119: That's a good idea. 15:24 dholbach, would it be the documenation teams responsibility and task to check if updates are going to land? 15:24 knome, it should be in the calendar of the relevant team manager and somebody who understands which blocks have already landed in the docs 15:25 ack. 15:25 knome: it would be the responsibility of both docs team and engineering teams to coordinate code landings with doc updates 15:25 and if it's just an email every other week - it can be lightweight 15:25 it wouldn't necessary have to be a full-blown hangout which takes 2 hours or something 15:26 dholbach, mhall119: But we are not talking about rather obvious things that should be done. The problem is that we don't have persons to assume the leadership roles needed. 15:27 that too. 15:27 not->now 15:27 GunnarHj, can you maybe name a few responsibilities that would fit into these roles? 15:27 It is simpler than having roles 15:27 GunnarHj: understood, but finding out what that leader will needs to do will help us find him or her 15:27 dholbach: We just mentioned coordination with engineering. 15:28 * dholbach nods 15:28 mhall119: Ack. 15:28 GunnarHj: something that we've been learning with the CC and LC is that leaders are more likely to come around if the responsibilities of leadership are clearly defined 15:28 and as the original mail implies, coordination of the documentation team in general 15:29 the mail even lists three actionable items; let me paste them here 15:29 thanks 15:29 – Work as a mediator with the members to resolve disagreements, be 15:29 able to reach a consensus and get along with the work 15:29 – Work with other Canonical employees, encouraging them to take part 15:29 more in writing documentation, especially with the components they are 15:29 working with themself 15:29 – Work with the Canonical IS team to resolve technical difficulties 15:29 I think this regular meeting could do with some help from some (one or more) of us in the community team to chase down people internally 15:29 the community help wiki is experiencing 15:29 popey++ 15:30 in the short term, the leader will also need to scedule the regular docs team meetings at a time and frequency that will get the most attendance 15:31 yes 15:31 and probably will need to run the meetings, at least to start 15:31 alternatively, just schedule often enough that everybody in the team gets to participate once in a while 15:32 because obviously there isn't a time that works for everybody, ever 15:32 a common problem 15:32 regularity still works out better than ad-hoc, but the leader can decide how best to balance those needs 15:32 Typically helped by using meeting bot and sending out a nice update mail to the team, so people who couldn't be there can contribute via email. 15:33 +1 15:33 Meetings take people out of work, where you could just email people when needed, and they can read and answer when it better suits them. 15:33 AlbertoSalviaNov, I find this quite productive now 15:33 AlbertoSalviaNov, i still disagree. 15:33 meetings also let you get through more things faster, this last hour of discussion would have taken a week over email 15:33 AlbertoSalviaNov, if you'd rather leave, I think that's fine 15:34 it's also an important opportunity to bring people together from separate teams 15:34 of course they shouldn't be longer or more often than necessary 15:35 i agree that meetings *can* be distracting and useless in some cases, but i wouldn't call all meetings useless and try to avoid them like a plague 15:35 Meetings serve the purpose to remind people about things which need to be done. 15:35 and as dholbach said, it's agreat opportunity to meet people you wouldn't meet otherwise. 15:36 like that AlbertoSalviaNov guy. 15:36 +100 15:36 What do you feel are the most urgent items for 16.04, which feel like they need to be rescued? 15:36 dholbach, let me throw the ball back to you: 15:37 what does canonical feel is the most important area in their official desktop/server documentation? 15:37 or is it not important to them 15:37 knome, I'm probably not the best person to answer this 15:37 but it's a question we could ask the desktop and server folks 15:37 dholbach, ack. this is one of the questions the coordinator for the doc team could help answer 15:37 and keep in mind, and coordinate work based on that 15:37 let's note it down 15:38 nobody in the doc team has that insight. 15:38 dholbach: Let's not talking more about the 16.04 desktop guide. We will be shipping a decent (I hope) set of docs. 15:39 dholbach: No rescue plan needed, in other words. 15:39 GunnarHj, ok... and for the server guide is there anything urgent we, right now, could help out with by raising awareness or doing anything else? 15:40 GunnarHj: so nothing is in critical need of work from Canonical for 16.04 docs? 15:40 basically, is there bleeding that we need to stop before we work on fixing the soure of the problem? 15:40 For serverguide, yes: The entire thing needs to be reviewed for accuracy. 15:40 GunnarHj, would you say that the desktop documentation for 16.04 has got the "minimal" effort to kept up-to-date instead of actually being able to improve it this cycle? 15:40 mhall119: Not for desktop. Can't speak for server. 15:41 desktop got about 1.50th of the attention it could have used. 15:41 knome: Yes. 15:41 1/50th 15:41 it sounds like server needs to have somebody review that list of pages 15:41 GunnarHj, okay 15:41 I think there is nothing else I can contribute to this conversation, that I think we need a coordinator and everything else will come on its own. 15:41 there is also talk of chnaging to some new markdown laguage. 15:42 So bye bye 15:43 dsmythies1: that's something that can be worked out once a leader is identified and regular meetings start again 15:43 I don't think we're prepared to make any decisions on that today 15:43 dsmythies1, who's discussing this right now? 15:44 e-mail thread on serverteam and docteam lists. 15:44 did you get the feeling that the people who are discussing this would also put some work into this? :) 15:45 +1' 15:45 yes, there were, I think, 2 or 3 that said they would help with a markdown type change. 15:46 but that sounds more like a 16.10 discussion, right? 15:46 dsmythies1, is there a list of chapters which need to be reviewed with more priority than others? 15:47 That is my thought yes, but we also had the same talk at 14.04 and then is fizzled. BY the way we only publish LTS serverguides 15:47 dholbach: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide#Contribution_table has the list along with priorities for the server guide 15:47 dholbach: Yes, The link I gave earlier. I will find and repeat 15:47 ... oh never mind 15:47 thanks I must have missed it 15:48 mhall119: BY the way for desktop: https://docs.google.com/spreadsheets/d/19RdaR3G_8TQ49f-Nb0XJAwhnlweMWJqsTr4kciSV5S0/edit#gid=584037095 15:49 dsmythies1: is there a priority list for those? 15:49 No. we did a bit of priority by e-mail. 15:50 dsmythies1: can you find the link to that thread in the archive and add it to our etherpad? 15:50 I'll try... 15:50 thanks 15:51 thanks dsmythies1 15:52 I want you to have a look at the workflow at The Ubuntu Manual: https://docs.google.com/spreadsheets/d/10Nl3Yue69IM2EflSdyeHgADET49RZRmgfDVoxHutQIk/edit#gid=2094840941 15:52 dholbach: for the immediate future, how about you and I contact the desktop and server teams with these list of review needs for 16.04 15:52 It does work there, but the UM is more structured than ubuntu docs 15:52 As regards the desktop, there were a mix of list messages and private mails. Not easy to provide a link to the latter. 15:53 mhall119, yes, let's chat about this later on 15:54 hannie, do you want to explain a bit how the structure differs? 15:54 Ok. UM is divided in chapters and sections. Every contributor takes care of a certain chapter or section. 15:55 And the contributors are the ones who wrote them initially? 15:55 Ubuntu docs is more like a set of loose pages with less structure in it 15:55 No, each version we have different contributors 15:56 and where did you recruit them? 15:56 Like with the docs, we also struggle to get enough people to help, so we decided to publish only LTS versions 15:56 Recruting is done her:e: http://ubuntu-manual.org/ 15:57 i don't think ubuntu can only ship LTS docs 15:57 documentation needs to go with all releases 15:57 GunnarHj: Good point. 15:57 knome, I agree 15:57 that looks nice - good work putting this all together 15:58 But I waas talking about the workflow 15:58 okay. 15:58 GunnarHj: can one of you but together a list of priorities? Or at least a "top X" pages we can have the desktop team focus on? 15:59 Desktop: The problem, the way I see it, is that I don't know if the page needs work or not until I try it. So far, evertying I have looked at has uncovered issues. 16:01 dsmythies1, that is why I was thinking of assigning parts of the docs to team members who can read and change "their" part of the documents 16:01 mhall119: Hmm.. DocumentationStringFreeze was a week ago. Selecting top priority pages is quite some work. IMO we need to let 16.04 go as regards the desktop. 16:01 dsmythies1: do you know which pages are going to be most commonly referred to by users? 16:01 mhall119: No. 16:02 mhall119, maybe the canonical IS can set something up for that 16:02 mhall119, though they promised to do the same for the community help wiki ages ago, not seeing anything for that yet either :) 16:02 (not blaming anybody, just pointing out) 16:02 knome: you mean getting page view stats? 16:02 yes 16:03 ack, we can look into that 16:03 isn't that the same as most referenced? 16:03 GunnarHj: right, we hit string freeze so we stopped. I went to serverguide, and to build issues. 16:03 knome: probably 16:03 mhall119, as you do that, here's the ticket from december 2013 for the community help wiki: https://rt.ubuntu.com/Ticket/Display.html?id=23534 16:04 knome: thanks, are there other outstanding RTs for the docs team that we need to follow up on? 16:04 yes, but page veiw stats doesn't tell us help usage within a computer, which might be quite different. 16:04 dsmythies1, true, though might give some insight. 16:04 dsmythies1: true, but I don't think there's any way we can get that info 16:05 agreed 16:05 mhall119, not any i'm following ATM 16:06 alright, we've gotten quite a bit of information from you guys, which is going to take some time to absorb, and dholbach and I both have action items, can we go ahead and schedule a follow-up meeting with you for next week, or in 2 weeks, to pick it up again? 16:07 fine 16:07 yes, fine. 16:07 same day and time, if that works well enough for everybody? 16:07 O.K. for me. 16:07 fine with me too 16:07 can't promise anything, i would set a doodle poll again 16:08 See you all next time 16:08 dholbach: are you good for next week? 16:08 yes, I think that should work 16:08 thanks a lot for your input everyone 16:08 and thanks for the patience 16:09 great, thanks everybody for your time and all of the insights 16:09 #info Notes and actions: http://pad.ubuntu.com/doc-team 16:09 Thanks 16:09 Thanks all 16:09 Thanks! 16:09 #endmeeting