#title #ubuntu-manual Meeting Meeting started by godbyk at 19:05:13 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-manual/2012/ubuntu-manual.2012-05-19-19.05.log.html . == Meeting summary == *Roll call *Author updates and status reports *Troubleshooting chapter *VirtualBox as a tool for authors and editors *UDS meeting report ''LINK:'' https://lists.ubuntu.com/archives/ubuntu-uk/2012-May/thread.html#34095 (godbyk, 19:50:31) ''LINK:'' http://popey.com/blog/2012/05/09/why-not-contribute-to-ubuntu-manual/ (godbyk, 19:51:01) ''LINK:'' http://www.scribtex.com/ Has anyone tried it? It has all the features we need. (herat, 20:12:44) *Collaboration with the docs team ''LINK:'' https://help.ubuntu.com/12.04/index.html (stillnotcool, 20:26:24) *Screenshot editors *Call for editors *Any other business Meeting ended at 20:46:46 UTC. == Votes == == Action items == * (none) == People present (lines said) == * godbyk (137) * c7p (85) * stillnotcool (65) * tomswartz07 (40) * kereltis (19) * ChrisWoollard (14) * TonyP (13) * herat (8) * sayantandas (7) * thorwil (5) * Guest67191 (4) * meetingology (3) == Full Log == 19:05:13 #startmeeting 19:05:13 Meeting started Sat May 19 19:05:13 2012 UTC. The chair is godbyk. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:05:13 19:05:13 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 19:05:28 #topic Roll call 19:05:34 Thanks for coming everyone. 19:05:51 If you're here for the meeting, please say 'hello' for our roll call. 19:05:58 Hello 19:06:01 hello 19:06:02 hello 19:06:03 hello 19:06:04 hello 19:06:28 hello 19:06:46 Thanks! If anyone comes in late, meetingology should catch them. 19:06:53 #topic Author updates and status reports 19:07:11 The deadline for the first draft is May 31. 19:07:28 here you can see the status every single section http://bit.ly/I0SAXe 19:07:32 All of the new content should be written and the screenshots should be in place by then. 19:07:46 To the authors: Have you encountered any problems or do you have any questions so far? 19:07:57 "Learning More" should be all set 19:08:09 Does anyone think they won't be able to make the May 31 deadline? 19:08:12 Obviously, this is not a mission-critical chapter :) 19:08:17 But I do enjoy maintaining it 19:08:18 None in my sections so far. Just need to do some finishing touches and screencaps 19:08:35 None in my section. 19:09:02 That's quite comforting to hear! :-) 19:09:18 herat screens are pushed on the branch ? 19:09:20 Though, I suppose it's more likely that the authors I need to worry about are the ones who aren't at the meeting. ;-) 19:09:31 y maybe :D 19:09:35 ha! true 19:09:41 c7p: Yes. 19:09:55 c7p: Were there some issues with the Troubleshooting chapter? 19:09:55 cool so is finished almost finished ? 19:10:11 yap will talk about it next 19:10:54 c7p: Yes. It is finished. :) 19:10:59 cool 19:11:19 well 19:11:38 from the desktop chapter i got almost no feedback from John 19:11:46 Hannie must doing well 19:12:10 what concerns me most is the first part of that chapter that is very important and doesn't have an author 19:12:19 hello 19:12:25 everyone 19:12:26 hey sayantandas 19:12:35 finally managed to login to irc! 19:12:45 :D glad to hear that 19:12:51 c7p: which chapter is missing an author? 19:12:58 yap 19:13:19 i 've sent a message to the list but nobody seemed interested 19:13:38 or maybe John did but i got scarce feedback from him 19:14:08 we'll need one or two to get assigned to it 19:14:34 i don't think many have to change there but that section has to be the most well-written 19:14:50 cause it's very critical in my opinion 19:14:57 can we just flip an editor to review it? 19:15:05 c7p: I agree that that section is most critical to understanding how to use Unity/Ubuntu. 19:15:38 tomswartz07: maybe, that could help, 19:15:57 is anyone interested in helping with that section ? 19:16:07 i figure, if there arent too many changes, it should be no issue for an 'editor' style review 19:16:30 I will review it, if that would help 19:16:45 cool, thx TonyP 19:16:53 Just point me at it 19:17:01 we need an author too to write the HUD section 19:17:26 if any chapter requires input, i may be able to help.. 19:17:39 and maybe the chapter has to be reorganized for a better understanding, i'm not sure about that though 19:17:49 good to know 19:17:57 i have the sound menu for review; i have seen changes are quite little 19:18:24 cool 19:19:00 then the Additional software section 19:19:13 i have not feedback from its author 19:19:26 herat could you manage it ? 19:19:42 Hello, che. 19:20:07 *additional software section is in the Software management chapter 19:20:08 He guys, sorry I'm late, rushed off my feet here :) 19:20:13 c7p: Yes, I could do that. 19:20:13 hello Guest67191 19:20:35 herat: nice, thx 19:20:46 <--kereltis 19:21:31 hm, anything else to be said in this topic ? 19:22:10 c7p: Did we find authors for all the sections that need them? 19:22:44 Anthony will do the office suite and totem sections 19:23:00 and then troubleshooting chapter need author 19:23:03 or authors 19:23:26 tomswartz07 and Kev Quirk are interested from what i remeber 19:23:41 if nobody appears for that chatper 19:23:51 c7p: Okay. Let's try to get that sorted out over the next couple days. If need be, we can put out another call for authors for those sections. 19:23:52 sure, id be willing to work on it. 19:24:12 godbyk: yea 19:24:31 i am ok to work for HUD + my existing sections 19:24:49 #topic Troubleshooting chapter 19:24:55 c7p: Did we cover the troubleshooting chapter already? 19:25:01 tomswartz07: could you manage the a part of this section or make an outline for it ? 19:25:11 nope i don't think so 19:25:22 surely. what do you need done? 19:25:34 sayantandas: ok good :), we'll talk through mail about it 19:26:05 1st i think the chapter needs to be re-written in order to meet today needs 19:26:14 not much have changed there since 10.04 19:26:24 at least that's my impression 19:26:48 so section have to be removed, others need update and others need to be added 19:27:07 what do you think ? 19:27:51 sounds good. Ill work up a detailed outline for the new chapter 19:28:09 ah good 19:28:15 would GoogleDocs work for everyone, or should I use another service? 19:28:37 tomswartz07: Google Docs should work fine. 19:28:40 Kev is also interested so if you need a second hand he should be able to help 19:28:42 Hey, ChrisWoollard. 19:28:49 hello Chris !: ) 19:28:57 Sorry I am late. Was putting kids to bed 19:29:04 ChrisWoollard: Excuses, excuses! 19:29:13 Hi Chris 19:29:16 At least i remembered this time 19:29:28 aren't you watching Chelsea ? :P 19:29:30 Hi Guest67191 19:29:47 No. Couldn't care less about football 19:29:58 fair enough 19:30:04 zing! 19:30:07 brb guys, trying to sort out this name thing 19:30:43 ok, sorted 19:30:43 c7p: Did we get all the authors/chapters discussion sorted? (That is, shall we move on to the next topic?) 19:30:46 ok so tom will make an outline of the new chapter 19:30:53 yes 19:31:05 ill sort it and share with the mailing list 19:31:05 if tom hasn't to say anything else let's proceed 19:31:16 :) nice 19:31:32 #topic VirtualBox as a tool for authors and editors 19:31:43 tomswartz07: Did you want to lead this part of the discussion? 19:31:49 certainly. 19:32:28 ive found that, while working on the manual sections, VirtualBox makes it easier to manage your systems 19:32:56 i feel it would be best to give an example. 19:33:26 In the Instant Messaging section, there is a section on the 'First Run' dialog, and how you may set up your accounts. 19:33:48 unfortunately, its difficult to pull up the first run, well.. after your first run. 19:34:38 If you use Virtualbox, you can run a fresh, clean install of Ubuntu, avoiding issues from your own personal customizations 19:35:14 hm, that would be highly beneficial especially if we use it for the 12.10, 19:35:29 I feel that this would be most helpful for the sections that deal with the desktop and UI elements, as having screenshots with various backgrounds, fonts, etc may confuse 19:36:00 the main feature about Virtualbox is that you can take a "Snapshot" that saves the exact machine state. 19:36:19 I agree, I use vbox all the time for testing distros and it's very easy to setup and use 19:36:25 so, if you need to redo a 'first-run' menu many times, you just reload that snapshot 19:37:27 kereltis: right! its very easy to set up- it installs a basic Ubuntu (or any OS) as a file on your drive, and you run it as a program 19:37:43 yep 19:38:25 tomswartz07: If people are interested in using VirtualBox with the Ubuntu Manual project, it might be useful to have some step-by-step instructions on how to set it up for that use. We could put the instructions on the mailing list and in the style guide. 19:38:40 Certainly. 19:38:41 good idea 19:38:54 good idea 19:39:22 after some releases this guide will be a manual to make a manual :P 19:39:34 very meta 19:39:47 c7p: That's the goal. I'm trying to dump all of our how-to's and instructions in there. 19:40:23 i guess the idea is, if we all die in a plane crash, everyone will know how to redo the manual 19:40:34 btw Kevin, https://wiki.ubuntu.com/ubuntu-manual works ? 19:40:38 We will need to have a list of standard login id, machine name, etc 19:40:48 c7p: Yes, though it's likely woefully out of date. 19:41:03 yes i see it 19:41:36 does virtualbox support some kind of automation? 19:41:45 thorwil: what do you mean? 19:42:03 tomswartz07: automating "user" actions 19:42:33 no, unfortunately. 19:42:57 Virtualbox is made to allow you to run different operating systems at once on the same machine 19:43:12 similar to Parallels for Mac, i guess. 19:43:15 being able to write a script that walks through all required states and does screenshots would have been to awesome 19:43:28 thorwil: Agreed. That would've been awesome. 19:43:43 If VirtualBox could've been giving a list of keystrokes and mouse clicks to perform. 19:44:37 has anyone checked it http://shutter-project.org/ ? 19:44:38 Now, VB can take a screenshot of the system that will work for our manual, provided you set the VB resolution to the proper settings. 19:44:56 that sounds interesting tom 19:45:29 c7p: tried that but did not work perfectly for me. 19:45:52 c7p: right? 19:46:33 Because the entire OS from virtualbox runs in a program window, you can resize the 'display' to the appropriate setting and snap the screenshots 19:47:01 c7p: Shutter looks nice and appears to have a plugin system. I wonder if the functionality of Quickshot could be incorporated into a Shutter plugin. 19:48:24 i ll take a look on it in summer when i'll have more free time 19:48:43 #topic UDS meeting report 19:48:46 *i'll look at it 19:49:02 Hannie and I attended the Ubuntu Manual UDS session via IRC. 19:49:12 I'm not sure who else was listening in at the time on IRC. 19:49:30 I missed it 19:49:38 me too :( 19:49:41 missed uds completely 19:49:44 We discussed a bit about the history of the project and a bit about where we wanted to go with it. 19:49:55 was hoping it would appear on youtube 19:50:14 popey posted an email to his LUG and a blog entry asking his readers why they weren't contributing to the manual. You can read their responses: 19:50:31 https://lists.ubuntu.com/archives/ubuntu-uk/2012-May/thread.html#34095 19:51:01 http://popey.com/blog/2012/05/09/why-not-contribute-to-ubuntu-manual/ 19:51:22 Just a sec and I'll find the link to the IRC channel logs. 19:52:27 Well, I responded to popey's email 19:52:43 we ask Jono to include a trophy in his ubuntu trophy project, might help with awarness 19:52:48 Here are the pad notes from the session: http://summit.ubuntu.com/uds-q/meeting/20570/desktop-q-ubuntu-manual/ 19:53:35 Kevin i think Latex terrifies everyone who checks out getting involved pages ! 19:53:55 c7p: +1 19:54:02 +2 19:54:05 c7p that's a good point 19:54:09 IRC logs: http://irclogs.ubuntu.com/2012/05/09/%23ubuntu-uds-grand-ballroom-h.html 19:54:12 +3 so :P 19:54:37 I have been contributing to the manual since the first edition, and I have never once installed or run Latex 19:54:38 The IRC logs consist primarily of me responding to questions and discussion from the people at the UDS session. 19:54:45 (So it'll read as being quite one-sided.) 19:55:08 what's the alternative? docbook isn't necessarily more accessible. the manual written in LO Writer isn't gonna happen 19:55:12 Is it LaTeX itself that's intimidating or the installation process? 19:55:27 we can still use Latex 19:55:41 but the authors should have the option either to use it or not 19:56:19 We have in the past allowed authors to submit their work in others formats. 19:56:30 Then we have editors manage the LaTeX markup. 19:56:41 godbyk: Yes, and I think that went a long way toward encouraging more participation 19:56:45 I'm okay with that as long as the editors as willing to do it. 19:57:33 From the discussions I've had, it seems that people have been more put off by the installation process of upstream TeX Live than in using LaTeX itself. 19:57:40 Do you guys agree or disagree? 19:57:47 half and half. 19:58:01 agree 19:58:09 No probs for me even though I have not used LaTeX, but the install was hairy 19:58:09 Unfortunately, I think that the Debian folks are still rejiggering their texlive packages. (They're completely overhauling the way they're organized.) 19:58:11 godbyk: Agree. The installation process involves using the command line 19:58:24 i think that many are put off by the massive install base that TeX takes, and the other half assume that you need to be a code monkey to do anything 19:58:25 I can imagine people just want a ubuntu package. 19:58:29 I'd still prefer to use Libreoffice though 19:58:33 there is a gui version of latex, and also libreoffice extension.. can we not use either of them? 19:59:08 sayantandas: Well, there are LaTeX editors (basically IDEs for LaTeX) and you're welcome to use those. 19:59:19 godbyk: can't we generate a file with the proper options that will be used from installer ? 19:59:21 sayantandas: I don't think that the LibreOffice extensions will work with our manual, however. 19:59:30 c7p: I'm not sure. I'll look into it, though. 19:59:35 I'm wondering if authors need to install or use LaTeX at all. If not, then we might be able to remove all the LaTeX stuff from the "getting involved" instructions 20:00:26 Ideally, I'd love for our authors and editors to be able to do all of the work via a web editor (similar to a wiki but a bit more structured). But we need to do some design work and a lot of coding before that can happen. 20:00:36 this might eliminate a critical barrier to entry, allowing folks new to the project (or thinking about getting involved with it) a simple way to do so: Contrat the group, find an editor who needs a writer for a section, and get cracking. 20:01:09 *contact 20:01:14 stillnotcool: That's something we can do now. Authors can submit their writings to an editor as long as the editor is willing to convert it to LaTeX for them. 20:02:07 Right. And it's worked well in recent editions. 20:02:24 can we use docbook to generate latex code ? 20:02:45 c7p: Yes. Though there will always have to be some fine-tuning of the output. 20:03:16 c7p: I think that the docbook markup is at least as scary as the LaTeX markup, though. 20:03:27 i agree 20:03:56 ok 20:04:26 godbyk: I agree. What I'm thinking about might indicate a larger shift in the way we conceptualize the role of author and editor, the division of labor between the two 20:04:43 stillnotcool: +1 20:05:10 I completely agree that we should simplify the workflow for authors and editors. 20:05:22 The instructions we feature on our home page seem to imply that writers -- in order to write and contribute -- need complex installations of software not already on their machiens, and not even available in the official repositories 20:05:22 And it'd be nice if they didn't have to know anything about LaTeX. 20:05:54 I think that having a web-based editing system would fix those issues for us, and that we should work on creating one. 20:06:17 (Though it obviously won't happen in time for 12.04, it'd be nice if it could be in place for 12.10 or at least 13.04.) 20:06:18 But do they still need to use bzr? 20:06:41 TonyP: Ideally, authors would be in charge of writing. Anything else is icing, gravy. 20:06:41 That's just as scary 20:06:52 Here's what Hannie and I do for Chapter 8: 20:07:09 Hannie pulls the most recent copy of the chapter from bzr when it's time to work 20:07:27 He shares that on Google Docs, where we both collaborate (I do the writing, he edits as I go). 20:07:47 WHen I sign off on it, he gives it a final edit, asks any remaining questions, then tightens the markeup and pushes the revision 20:08:03 This is a special case, I suppose, because we don't have screenshots 20:08:33 He and I both agreed to use GDocs because we're comfortable with it, and it mae collaborating easier. 20:08:44 Cool. 20:08:46 Writer/editor pairs could choose another tool if one works better. 20:08:50 Thats a very great idea 20:09:08 But this has worked well for us, and allowed me to do what I enjoy most: writing. 20:09:08 Another route that some authors/editors have taken is to just drop .ods files into an Ubuntu One shared folder. 20:09:20 godbyk: I like that, too. 20:09:21 sounds good 20:09:43 Maybe it is just a case of making sure people know that they can write anyway that suits them 20:09:44 or Dropbox, if you prefer cross platform for us Arch users :) 20:10:06 What I have envisioned is that we'd have a website that works similar to a wiki. Though instead of using wiki markup, we'd have a WYSIWYG editor. 20:10:15 Authors would write content. 20:10:28 We might advertise author jobs as writing jobs, and editor jobs as technical positions -- the work not only of editing prose, but marking up copy and taking screenshots (doing more technical work) 20:10:29 Once authors have written content, the editors are notified and can come along and tweak things. 20:10:41 Once the editors have finished with it, the translators are notified and can translate that section. 20:10:56 All of that would happen on the website. There'd be no LaTeX or bzr visible. 20:11:05 godbyk: Right. 20:11:26 In addition, when something that's been translated is edited/modified, the translated can see what's actually changed. 20:11:48 So if, say, a comma were added, the translated could see that only a comma has been added and that they don't need to retranslate the entire paragraph. 20:12:00 I think that would go a long way toward helping our translators. 20:12:11 They could start work a lot earlier in the process and keep up more easily. 20:12:12 godbyk: Well put 20:12:44 Once everything has been written an edited, we'd generate the LaTeX code, make any tweaks there that we wanted to make and have our PDFs ready to go. 20:12:44 http://www.scribtex.com/ Has anyone tried it? It has all the features we need. 20:12:52 At the same time, we'd generate ePUB and other formats. 20:13:24 herat: Yes! But costly. 20:13:40 stillnotcool: Oh. Did not see that. 20:13:44 herat: I haven't tried it yet. Though we'd need to be able to use our own document class ("template"). 20:13:59 And it looks like it's $10/month. 20:14:50 Anyway, that's some of what I have envisioned for our website and process in the future. To make that happen, we'd need to design the site in more detail and find some web developers to create it for us. 20:15:03 yap 20:15:23 we also need to talk about the project to the outside world 20:15:26 herat: I won't presume to argue for what's best with regard to our implementation/use of LaTeX. godbyk is the expert there, and knowsmore about what we need/want than I do. I'll just say that from a writer's perspective the current instructions are a little intimidating, and I think it behooves us in the near future to reconsider our writer/editor workflow to better accommodate newer contributors. 20:15:34 This website would also allow for drive-by editing. Anyone can come along and fix bugs. 20:15:38 godbyk: I like it. 20:15:52 If they're anonymous edits, they'd need to be approved by a registered editor first. 20:16:09 I think what we need is a person to basically hit up all of the Linux news outlets and cheerlead our project. if we could get more users, we could get much more varied skills and more breathing room to work 20:16:16 maybe worth testing at least 20:16:37 ChrisWoollard: What's worth testing? 20:16:45 scribtex 20:16:50 ChrisWoollard: Ah, gotcha. 20:17:01 I'll poke around it a bit and see how it looks. 20:17:23 click trial. it takes you to a demo site 20:17:27 I like how the basic/free version is limited to "one bollaborator." I'm unsure what that actually looks like! 20:17:39 *collaborator 20:18:08 Another topic that was raised during the UDS session: 20:18:14 #topic Collaboration with the docs team 20:18:36 The question of why we're not collaborating with the docs team is raised periodically. 20:19:00 Aside from some initial strife between Ben and the docs team when the project first started, 20:19:17 I think the real reason for lack of collaboration is that no one from either team has really taken up the issue. 20:19:31 godbyk: Right, a schism I never really understood, to be honest. 20:19:38 Are they still using another system. I forgot which one 20:19:42 godbyk: i agree 20:19:54 My question is: In what ways would teams benefit from collaboration? How can we collaborate? 20:20:06 ChrisWoollard: I think they're using docbook/mallard markup. 20:20:30 Ahhh. Mallard. That's what I was thinking of 20:20:37 I think the docs team likely has a better sense of what's most useful to the uninitiated. 20:21:15 Questions: How could the docs team help the manual project? How could we help the docs team? 20:21:16 The docs team must document _everything_ in Ubuntu, but it's likely they have some kind of data regarding which documentation is accessed most frequently by new users. 20:21:46 Understanding these patterns might help us target our manual and ensure that our chapters cover relevant material 20:22:37 i don't know how we can help each other, maybe we can have a poll of content were anyone of both project can have direct access to the work of the other 20:22:43 And because we are trying to remain sensitive to the needs of new/inexperienced users, we might offer them this perspective on relevant sections of the official documentation, which could benefit from what we've already done 20:23:43 I'll ask a stupid question while I'm at it (admitting my own ignorance): What does the docs team do? 20:23:56 From what I gather, they maintain the official Ubuntu help files. 20:24:11 my understanding is that the team maintains the documentation at help.ubuntu.com 20:24:11 i think that's what they do 20:24:28 Okay. 20:24:51 It would be nice to hear from them occasionally 20:24:56 So they are the help team 20:24:57 My sense is that we're all working with the same mission, though our foci are different 20:25:15 we are writing material specifically targetted at new users 20:25:37 True but I see the two projects as aiming at different people, they cover everything in great detail which can turn into geek speech, good stuff but can be intimidating if your new to computers. We on the other hand target the people that are brand new and just want the basics to get them started in basic language they can easily follow. 20:25:39 what we do seems to me a subset of the overal project of documenting Ubuntu 20:25:51 kereltis: Yes. 20:26:01 So, try this: 20:26:23 visit the home page for 12.04 documentation 20:26:24 https://help.ubuntu.com/12.04/index.html 20:26:32 or https://wiki.ubuntu.com/DocumentationTeam 20:26:48 On that page, you'll see a few different types of documentaiton 20:26:51 A desktop guide 20:26:54 A server guide 20:26:57 and an installation guide 20:27:13 our manual could be the first link: 1. "Getting Started Guide" 20:27:46 One difference between their desktop guide and our manual is that we can't easily redirect the user to read, say, the Empathy help pages for more information. We try to include the most common and useful information directly in our manual. 20:28:06 godbyk: Right, and we rightly shouldn't. 20:28:12 In other words, our manual needs to be fairly self-contained instead of merely pointing to other documentation. 20:28:20 yap 20:28:37 Our manual assists new folks with the task of navigating a stock installation. 20:28:48 I'm just poking around their desktop guide, so this may not be representative. 20:29:01 It appears that their style is very oriented on the how-to. 20:29:14 Example: �To let other users use your computer, you can either log out, or leave yourself logged in and just switch users. If you switch users, all of your applications will continue running, and everything will be where you left it when you log back in.� 20:29:17 When they're ready to graduate from "Getting Started," they head to the "Desktop Guide," which could actually be renamed to something like "Complete Documentation" or "Advance Documentation" 20:29:35 Most of their paragraphs begin with, �To do x, ...� 20:29:51 Whereas we should be providing a bit more background/discussion instead of just a sequence of steps to follow. 20:30:29 godbyk: +1 20:30:32 +1 20:31:03 Having said that, I do think it'd be useful if we explored the topics that they're covering in the desktop and installation guides to see if there's anything that we're missing. 20:31:14 (Or conversely, anything that they're missing that we think they should add.) 20:31:25 godbyk: Agreed. 20:31:33 Agreed 20:31:38 me too 20:31:40 Would anyone here be interested in taking up that task? 20:31:57 That is, doing a comparison between their desktop and installation guides and our manual? 20:32:30 godbyk: Would it be something each author could do for his or her individual chapter? Perhaps editors could peruse the documentation for their subjects and suggest to authors changes or additions. 20:32:55 stillnotcool: Possibly, though the info might be scattered around quite a bit. 20:33:04 Tell you what, I'll take on that task. 20:33:22 I'll have a look at their guides and see what they cover and what we cover, figure out the overlap and things that each group has missed. 20:33:49 guys i got to go 20:33:51 godbyk: That's generous. Thanks for doing it. 20:34:01 Okay, see you later, c7p. 20:34:13 cya c7p 20:34:15 i think this was one of the best meetings ! 20:34:18 see you all 20:34:30 bye c7p 20:34:32 thanks for being here 20:34:37 same, we got a lot discussed 20:35:10 Okay, I think we have just a couple more topics and then we'll be finished. 20:35:19 #topic Screenshot editors 20:35:31 We've discussed this previously a bit. 20:36:06 I think that it'd work best if the authors took the initial screenshots (so they can show us what they want), and then we should have one or two screenshot editors who come along afterward and take all the "official" screenshots. 20:36:31 I think having a couple people taking all the screenshots will help ensure consistency. 20:36:39 agreed, it would cut down on problems 20:36:46 What do you guys think? 20:37:31 Good idea 20:37:35 godbyk: Sounds easy enough. Writers could just use the built-in screenshot software to give editors the gist. 20:37:53 Would anyone here like to volunteer to be a screenshot editor? 20:38:09 If not, I'll send an email to the list and ask for volunteers. 20:38:44 Okay, I'll email the list. 20:38:51 We'll need someone who knows LateX I presume 20:39:13 kereltis: Nope. Just someone who's detail-oriented and can take screenshot with the proper resolution and whatnot. 20:40:10 #topic Call for editors 20:40:26 Hannie sent an email to the list earlier this week to get volunteers to be editors. 20:40:31 I don't think she got much of a response. 20:40:53 Just me and someone else 20:40:55 We could ask omgubuntu and iHeartubuntu to give us a mention and ask for editors 20:40:56 She's going to email the editors we have and some of the editors we've had in the past to see if they're still interested in helping. 20:41:04 Having said that, I think that we'll still need more editors. 20:41:44 I'll write up a call for editors that we can send out to website. 20:41:52 What website would you suggest I send it to? 20:42:03 omgubuntu 20:42:25 kereltis: +1 20:42:39 think that's our best bet 20:42:44 Okay. 20:42:57 I'll have someone post it to Planet Ubuntu as well. 20:43:05 Something in the Ubuntu weekly news? 20:43:14 we might make the call more specific ... assess our needs as say "we need editors with knowledge of x, y, and z" 20:43:24 TonyP: +1 20:43:42 TonyP: Good idea. I'll ask pleia2 about that. 20:43:46 yep, maybe http://benjaminkerensa.com/ as well 20:44:10 'kay. 20:44:38 #topic Any other business 20:44:45 I think we've touched on everything that was on the agenda. 20:45:08 Nice work godbyk. Thanks for chairing and leading. 20:45:09 Just a reminder that the upcoming deadline of 31 May is when authors need to have finished their writing and draft screenshots. 20:45:27 Does anyone have any other business they'd like to discuss? 20:45:29 Or any questions? 20:46:20 All set :) 20:46:40 All right. Since there is no other business, we're adjourned. 20:46:44 Thanks for coming, everyone! 20:46:46 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)