=== godbyk changed the topic of #ubuntu-manual to: Ubuntu Manual Project discussion | Oneiric edition released! | Style Guide: http://files.ubuntu-manual.org/style-guide.pdf | Website: http://ubuntu-manual.org | Launchpad: https://launchpad.net/ubuntu-manual | IRC logs: http://irclogs.ubuntu.com [20:02] Hey, the troika is here! where is the rest? Hi godbyk and c7p [20:02] lol [20:02] Hello, hannie. [20:02] hello [20:03] We'll have to wait for the others to join, in the meantime I do some further reading [20:04] agenda if anyone wants to read: http://pad.ubuntu-uk.org/UMP-March2012Meeting [20:06] hi all [20:06] hello, tomswartz07 [20:07] we are waiting for more people to join us [20:07] great. sorry im late! [20:07] hello [20:08] Shall we get started then? [20:09] I think we should, although there were many more names on the doodle list [20:09] Okay. [20:09] Even though mootbot is absent/dead, we'll keep up appearances. [20:09] #startmeeting [20:09] we're going to be logged, correct? may as well just email it to those who missed [20:09] The meeting agenda is available at . [20:09] will this be logged anyway? [20:10] The meeting should still be logged, yes. [20:10] If not, I'm logging it. [20:10] ok [20:10] good [20:10] great. ok. lets get into it then :) [20:10] [TOPIC] Recent Oneiric release [20:10] who starts this ? [20:10] First off, as you've probably noticed, we just released Getting Started with Ubuntu 11.10 this week. [20:11] Congratulations and many thanks to everyone who helped out with that manual! [20:11] Yes, we should be proud of the result. [20:11] congrats :) people [20:12] its very nice! congrats [20:12] Having said that, it took us quite a while to get the Oneiric manual released. Which leads us to our next agenda item: [20:12] [TOPIC] Problems we faced during Oneiric [20:12] c7p: Would you like to take this topic? [20:12] ok i wrote this item so i start :) [20:13] well this topic is opened in order to share our experience and what held the release of the back [20:14] i think that the major holdup was the screenshot collection. [20:14] is that fair to say? [20:14] yeah that's right [20:14] I think reviewing also took too long [20:14] screenshots and the proofreading for me took the most time [20:14] +1 hannie [20:15] what i should mention is that in contrast with the previous releases authors didn't step off [20:16] yes, i thought the chapter authors did a very good job of getting things done in a timely manner. [20:16] One of the solutions could be: 2 persons should keep track of "their chapter" (author(s) and editor(s)) [20:17] yeah that sounds great [20:17] and report to the editor-in-chief [20:17] on a regular basis [20:17] yes [20:17] including the screenshots in that chapter [20:18] hannie: now, correct me if Im incorrect; wasnt the screenshot issue caused by the varying methods that people were taking screenshots? [20:18] we have to set a new editor-in-chief since Rick "resigned" [20:19] tomswartz07, yes, but if people had checked "their" chapter it would not have been so much work for others [20:19] hannie: I see. [20:20] c7p: how will we get a new editor-in-chief? [20:20] godbyk: was there any other issue with screens apart from the different resolutions ? [20:20] hannie: :D i don't know [20:21] c7p: I think the primary problem with the screenshots was that some were taken at the wrong resolution. Another issue is that some screenshots hadn't been taken at all. [20:21] how many screenshots were missing completely? [20:21] tomswartz07: Not too many. I think there were perhaps 2–3 screenshots that were missing completely. [20:22] hannie: regarding EiC we have to add the opening on the website if there isn't any member of the project that wants to take the role [20:22] A missing screenshot is one where someone has written \screenshot{...} in the .tex file, but hasn't captured the screenshot and uploaded it to the repository. [20:22] I am in favour of giving good instructions about screenhots on our website [20:23] Make author/editor responsible for the screenshots, but give them good instructions [20:23] hannie: i agree. perhaps if we are particular in spelling out the duties of each role it will make things easier. [20:23] godbyk, is it possible to update the screenshot instructions on the website? [20:24] hannie: I'll look into that. I can add it to the style guide, as well. [20:24] godbyk, that would be great. [20:24] tomswartz07: +1 [20:25] are there any authors here ? [20:25] i am [20:26] what are the problems you faced ? [20:27] as an author always [20:27] as an author? not too much, actually. [20:27] ah ok [20:27] updating the information and sifting through what has changed since the last version was the most difficult. [20:28] i am asking in order to write down what are the problems in the writing process [20:28] in my section, in particular, there wasn't that much that had changed. perhaps the other sections (where more development took place) had a different experience [20:28] c7p, do we have to send an email to all the authors and ask, or via the mailing list? [20:28] yes maybe [20:29] i haven't sent mails to authors [20:29] Do you want me do do this? [20:29] i think they are all subscribed to the list [20:29] Hey, ajmontag. You can read the minutes of what we've discussed (and the agenda) here: [20:29] hi ajmontag [20:29] hey ajmontag [20:30] hannie: that would be great, since i have many things on my mind lately [20:30] Hello, i'm a bit preoccupied atm, but i'll try to read along! [20:30] i have a mild suggestion for the next version of the manual [20:30] c7p, I will contact them about this via the list [20:30] ok thx [20:31] The other action that should be taken is: find an editor-in-chief. Shall I put that on the list as well? [20:32] tomswartz07, what's the suggestion? [20:33] going along the lines of what we have just discussed, perhaps it would be best to focus (initally) on getting screenshots and compile a list of the differences between the current edition and precise [20:34] I agree with tomswartz07. I think that establishing the list of differences will make it a lot easier for authors to get started. [20:34] I don't know if one person can find all the differences, though. [20:34] naturally, the ubuntu changelogs are easy to get, but if we could use those to guide our edits it will make things so much easier [20:34] We may need a group of people to do this. Or perhaps we should have the authors themselves do it. [20:35] tomswartz07, godbyk I do not quite get this: [20:35] you mean use screenshots to point out the differences between oneiric and precise? [20:36] hannie: no. this is purely for the authors and editors sake. [20:36] hannie: No, not with screenshots. We just need to figure out what changes we need to make for the new version. [20:36] it seems to me that when we dig in for the next edition, we are starting from scratch each time. [20:36] you mean make a plan/framework of the differences? [20:37] hannie: exactly [20:37] hannie: yes. [20:37] ah, ok [20:37] so far, i know that OMG!Ubuntu! and Cannonical themselves provide very good update info. [20:37] First of all, I think we will have to find out if the current authors are willing to continue with "their" chapter [20:38] And then they can find out what the differences are [20:38] i think most of the authors are willing to maintain their chapter [20:38] how about the chapter editors? [20:39] hannie: agreed. a small addendum, however; if a master list is compiled, then (potentially) a small number of authors can work on a few chapters [20:39] tomswartz07: true. as long as there aren't *too* many changes. [20:39] just food for thought, however. [20:39] The switch to Unity was a huge change for us. [20:39] godbyk: i agree. [20:39] we have no chapter editors as far as i remember ! [20:39] either a group of people gather a list of all the differences, or [20:40] or there are 2 [20:40] the authors/editors do this for their chapter [20:40] that's why the proofreading process didn't went so well [20:40] c7p, yes we have [20:40] how many ? [20:41] After the first of May I will be able to do editing if you'd like. [20:41] https://docs.google.com/spreadsheet/ccc?key=0Ar0Z6vOO38EydFl2cTJRNzJPZU56WEI3VzdKNzJtR0E&hl=en_US#gid=3 [20:41] hannie: isnt that just what we do now? authors make changes and then those are listed via the commit logs? [20:41] actually how many sections are they assigned to [20:41] this is the list of the people that wanted to contribute as editors [20:42] I think every chapter should have a reviewer/editor assigned to it [20:42] this doesn't mean that they all worked as editors [20:42] sure, the problem is that almost no one wants to work as editor [20:42] well, im very willing to commit to more sections if need be [20:42] *works [20:42] good to know [20:43] I am also available for more than one chapter [20:43] * benonsoftware is free is he is needed [20:43] so, we already have three ;) [20:43] make that four [20:44] the crucial part as it seemed with the 11.10 is the proofreading period :D, so if you and other contributors solve this [20:44] fair enough. [20:44] 12.04 will go smooth [20:44] I will ask for editors via the list too [20:44] if we don't face any other new problems of course [20:45] there is no need to do it know [20:45] how many are willing to start in now? perhaps if we use the pre-release interface freezes, we could get that much of a jump before the actual release [20:45] why not? the earlier the better [20:45] As far as sorting out the changes between 11.10 and 12.04, are we leaving that up to the authors? [20:45] contributors have to know that there is work for them to do atm [20:46] we can call for authors now [20:46] godbyk, that is what I would prefer, yes [20:46] c7p: +1 [20:46] but the experience from 11.10 shows that the editors lose their interest if they don't have job to do [20:47] c7p, I can do that in the same email in which I address the current authors [20:47] ok i don't have problem with this [20:47] hannie: Good idea. That way we can see which authors can't help us this cycle so we can find new authors to fill in those spots. [20:47] c7p, as an editor I experienced a very good cooperation with "my" authors [20:48] good to know :) [20:48] here's a very hopeful thought: if we could get the 12.04 edition released in a timely fashion, do you think we could contact Cannonical to get it featured on their site? [20:48] I could talk to Ben Humphrey and Joey Sneddon to see if we could get it featured on OMG!Ubuntu! [20:49] tomswartz07: i'm not sure about this :/ [20:49] tomswartz07, I put an item on the agenda: Promoting the manual. Is that what you mean? [20:49] hannie: surely [20:49] i mean about the canonical [20:49] c7p: what are your reservations? [20:50] i think they want to see something very neat to put it on their website [20:51] you know with great design etc, but that's just thoughts, we don't have anything to lose if we send them a mail [20:51] Well, oneiric is quite neat, don't you think? [20:52] i mean in respect of design [20:52] hannie: i agree. its better than saying 'oh, just go to this website for help'. a co-opted manual may help those just starting. [20:52] at any rate, heres an idea: [20:53] ok, it is still too early to promote Precise. But we should do it when the time is there [20:53] +1 [20:53] we have other issues to look now [20:53] if we could get a signal boost from various open source sites, we could get volunteers to help improve the design for 12.04 [20:53] i agree [20:54] tomswartz07: I do have a lot of thoughts on the website end of things, but we'll have to save those for another meeting, I'm afraid. [20:54] godbyk: fair enough. [20:54] tomswartz07: first we need to track down the things we want from them to do, and be specific [20:55] Shall we move on down the agenda? [20:55] c7p: im willing to help with this, if you wish. moving on. [20:55] yeah [20:55] [TOPIC] Division of tasks: 1 or more persons responsible for: screenshots, final editing, planning/scheduling, roadmap, publishing etc. [20:55] I think we've covered some of this already. [20:56] It looks like we want the authors to be responsible for their own screenshots and for determining what needs to be updated within their chapter, correct? [20:56] yes [20:56] I think so. [20:56] yes [20:57] I think that the editing should be up to each chapter editor (though we may need to provide some more clear guidelines on what this entails). [20:57] final editing = task editor-in-chief (will be quite a job!) [20:57] That leaves the editor-in-chief to worry about the bigger-picture stuff like the overall schedule and roadmap for the release cycle and to sign off on the final edition to be published. [20:57] maybe that's a bit deterring for a new EiC that isn't member of the project already :/ [20:57] although it depends on the author/editor teams. If they do their best there won't be much to do for the editor-in-chief [20:58] The scheduling of work within a chapter can be handled by the chapter editor and the chapter authors. [20:58] Yes, first we have many little islands. Later we make it one big country :) [20:59] I think what's happened in the past few releases is that hannie, c7p, and I fix little bugs and make minor edits throughout the manual. [20:59] Then when we're tired of doing that, we release the PDF. [20:59] :) [20:59] not to downplay the role of the EiC, but it seems that the main role is to just give the whole manual a read-through and give it a proofread? [20:59] right. Therefore I insist on giving authors/editors more responsibility [21:00] tomswartz07: I'd say that the primary role of the EiC it to keep everyone on task and on schedule. [21:00] godbyk: i see. [21:00] The EiC doesn't do a lot of copy-editing, per se. [21:00] (Or at least, the EiC shouldn't be responsible for editing the entire manual himself/herself.) [21:01] godbyk: you mean an author/editor coordinator in other words ? [21:01] godbyk, what was the reason Rick stopped? Was it too much work for him? [21:01] c7p: Yes. As well as the driver of the project during that cycle. [21:01] hannie: I think his day job started taking up more of his time. [21:01] So who ensures consistant voice and style among chapters? EiC? [21:01] perhaps we could give the EiC a task to help promote the manual? [21:01] ajmontag: Ostensibly, yes. In the past, I don't think that's really happened, though. [21:02] i agree with Kevin [21:03] We have to describe the job for the EiC before we try to find one [21:03] hannie: +1 [21:03] yap [21:04] it seems that in our rush to get the manual done, many of the jobs have become muddled. [21:04] tomswartz07: I agree. [21:04] +1 [21:04] I think that we should more clearly define the responsibilities and duties of each role (author, editor, EiC). [21:04] godbyk: +5 [21:04] That way everyone knows what he/she needs to do. [21:05] godbyk: that's a whole new meeting [21:05] c7p: Agreed. [21:05] but we need more people on the meeting too [21:05] I suggest we describe these roles via the list [21:05] especially those who are affected [21:05] Perhaps it's something we can do on the mailing list. I can write up a draft and post it to the list for feedback if you like. [21:06] hannie: that's a solution too [21:06] godbyk: Google Doc? shared edits? [21:06] tomswartz07: It might be better to have more of a discussion format to start with. [21:06] i see. good idea. [21:06] godbyk, good idea: make a draft and put it on the list for feedback [21:06] tomswartz07: ..Since we'll want to collect opinions of what people think their roles currently entail. [21:06] hannie: Okay, I'll do that. [21:07] btw a collaboration platform would be very helpful [21:07] c7p: Can you be more specific as to what you mean? [21:07] yes [21:08] Well I've gotta run, will catch up with the agenda later on. Bye. [21:08] see ya ajmontag [21:08] ajmontag: Okay. Thanks for coming, ajmontag. [21:08] bye ajmontag [21:08] we in greek ubuntu community have use atrium http://openatrium.com/ [21:08] this helps us to communicate set tasks [21:09] update the status of the task, [21:09] c7p: Is that the one based on Drupal? [21:09] divide team members in task droups etc [21:09] benonsoftware: im not sure but i can ask our admin [21:09] I will add atrium to my favourites and study it later [21:10] As I think we are using that also for one project I'm in [21:10] Yeah, we are using that also [21:10] that's a tool that helps us to see what are the tasks that need to be done [21:10] Yeah [21:10] i usually find myself forgetting what i wanted to do [21:11] c7p, I suggest we put this on the next meeting's agenda [21:11] i agree [21:11] Okay. [21:11] [TOPIC] Format of the new version [21:12] godbyk, I did not have time to study booktype, although I started with converting Prologue [21:12] You did the same I noticed [21:12] hannie: Yeah, I converted the entire Prologue using Booktype. [21:12] So did I :) [21:12] Booktype appears to be geared primarily toward generated ePUB-format e-books. [21:13] I suppose it is too late now to discuss booktype. [21:13] So their editor is limited to the types of things you can do with ePUB. [21:13] i think we can use booktype in this series instead of the ubuntuone method [21:13] I don't think Booktype will work for us as it stands now, but it may be something we can modify or use as an example for creating a new system that works for our needs. [21:14] So, we stick to LaTeX for the moment? [21:14] if we see that everything goes well with booktype and that suits 100% to the project we can publish the manual this way, if not we just convert the chapters to latex as we did for 11.10 [21:14] I am going to work on writing a script that can convert our manual to ePUB format when I get some time. We'll see how it goes. [21:15] I think we should stick to LaTeX for now. [21:15] what are the pros of going to booktype? [21:15] This needs further discussion in the next meeting [21:15] im assuming that this is in replacement of LaTeX? [21:15] tomswartz07: The pros of using Booktype are that it has a web-based editor. [21:15] i tend to latex too kevin [21:15] tomswartz07: Everyone edits their text via the website. [21:16] tomswartz07: It's has a sort-of WYSIWYG editor, but it's limited in functionality to what the ePUB format can do. [21:16] For instance, ePUB doesn't have margin notes. [21:16] authors can comment on chapters, and communicate with each other [21:16] godbyk: I see. Im unfamiliar with it. [21:16] godbyk, what I missed is the possibility of marginnotes [21:16] ePUB doesn't have footnotes, either, so you have to use end notes with links between the main text and the end note (and vice versa). [21:16] i think we have to share it with the list [21:16] yes, it does have footnotes [21:16] but nommarginnotes [21:16] is there a way to take LaTeX to ePub? [21:17] hannie: They're not real footnotes, though. They're end notes. [21:17] ah, ok. [21:17] tomswartz07: Well, I'm going to write a script that should convert our manual to ePUB. It's really hard to do for the general case of all possible LaTeX documents, but since our manual only uses a small subset of commands, I don't think it'll be too difficult. [21:18] very nice. [21:18] godbyk, you are our hero [21:18] superkevin [21:18] hannie: Only if I get a working script. :-) [21:19] i havent tested it, but does anyone know if there are formatting issues with the PDF on a basic eReader? (OG Kindle, for example) [21:19] godbyk, will you inform the list about booktype? [21:19] I know some LaTeX PDFs dont play nice. [21:19] hannie: Sure. [21:19] ty [21:20] tomswartz07, I think our manual.pdf looks fine [21:20] If authors do not know the latex code others will help them [21:21] tomswartz07: It could probably be formatted a little better as it's currently on a full sheet of paper. If we generated a PDF on smaller page sizes, it might look better on the ebook readers. (I haven't tested this, though.) [21:21] It's certainly something we can explore if anyone has an ebook reader and wants to test out some different PDFs for us. [21:21] I have a Nook, but it's rooted... Not much help here. [21:21] tomswartz07: Will it read PDFs? [21:22] the standard PDF looks as perfect as it does on a computer. [21:22] godbyk, we're 20 minutes overtime :) [21:22] hannie: Duly noted! [21:22] We can discuss formats some more in the future. Feel free to started a thread on the mailing list about ebooks if you like. [21:22] [TOPIC] Strict deadline [21:23] * godbyk doesn't want to keep hannie and c7p up past their bedtime. It's already super-late for them. [21:23] sorry folks! :X [21:23] i don't have problem with time guys [21:23] really [21:23] Maybe this will be the task of the EiC, so leave it for the moment [21:23] hannie: I think we have to sort out what changes need to be made before we can establish a deadline, too. [21:24] ok [21:24] [TOPIC] Any other business? [21:24] I am quite happy with the results of our first Precise meeting, [21:24] Is there anything else urgent that we need to discuss during this meeting? [21:25] recap the tasks that we have to ? [21:25] although I think it a pity so many people put their names on the list but did not come [21:25] Sure. [21:25] None here. I look forward to starting in on the 12.04 edition. [21:25] [ACTION] To help alleviate these problems in the future, we will provide clear instructions on how to take the screenshots and insert them in the manual. The chapter author and editor are responsible for the screenshots that appear in their chapter. These instructions should appear in the style guide. [21:25] [ACTION] Explicitly spell out the duties of the chapter author and editor so they know what their responsibilities are. [21:25] nope. I want to thank you all for being here [21:25] [ACTION] Hannie will email the authors to assess what problems they encountered during the previous release cycle. [21:25] [ACTION] Authors will be responsible for determining what needs to be updated from 11.10 to 12.04. [21:25] [ACTION] Provide clearer lists of responsibilities and guidance for each of these roles. [21:25] [ACTION] godbyk will create a draft list of responsibilities for each of the roles and post it to the mailing list for feedback. [21:26] [ACTION] godbyk will inform the list about Booktype. [21:26] ok good [21:26] I think we should also hold regular meetings again. [21:26] You should book #ubuntu-meeting for the next meeting [21:26] Right, there is work to be done [21:26] yeah i agree [21:26] That seemed to help keep people involved in the project. [21:26] godbyk: +1 [21:26] even every week [21:27] c7p, will you plan the next meeting? [21:27] sure [21:27] oh, so nice to work with you guys! [21:27] me 2 [21:27] c7p: thanks! [21:27] See you next time. [21:27] cheers [21:27] Okay, then. Meeting adjourned! [21:27] #endmeeting [21:27] cheers all! [21:27] cheers [21:27] Feel free to hang around and chat some more, if you li.e [21:27] like, rather. [21:28] i'll stay [21:28] im staying :) [21:28] I'll collect these minutes notes and post the minutes to the mailing list. [21:28] yes, time to relax. I have been working for Ubuntu all day [21:28] * benonsoftware is also staying :P [21:28] did anyone contact any news sources RE: the 11.10 edition? [21:28] tomswartz07: Nope, though one news source contacted me. [21:28] its release, I should say [21:28] Let me find the link. [21:29] tomswartz07: http://news.efytimes.com/e1/80966/Here-Comes-Ubuntu-Manual [21:30] very nice! [21:30] Looks like we've had one person buy the print edition of 11.10. [21:30] Just wondering has any work been done on the website? [21:30] I'll have to see how many downloads we've had. [21:30] (After what happend last time and test.) [21:30] benonsoftware: No, but I'd really like to get a new website up and running. [21:30] Okies [21:31] I'd like the website to be manageable by multiple people (project leaders, editor-in-chief). [21:31] How is it manage atm? [21:31] At the moment, I log into the server and edit the site by hand while it's live. Not the best solution, I can assure you! [21:32] what if we use a wysiwyg website editor? Weebly comes to mind. It allows multiple editors [21:32] its free and allows for custom domains [21:32] godbyk: Yeah, I've done that before :P [21:33] tomswartz07: tbh I've used weebly a few times and its not really good for sites that ubuntu-manual.org [21:33] Some of the things I'd like to be able to do with the website is allow people to modify the text of the site (e.g., add/remove/edit job listings, news items, edit static text), publish manuals (upload the PDF, set the language and format). [21:33] And that's just for the public-facing site. [21:34] It'd also be nice if we could move all of our writing, editing, translating, and publishing stuff to a web interface to make it easier for everyone to do their work. [21:34] then they wouldn't have to download LaTeX and learn its syntax. [21:34] Hmm, okies [21:34] or worry about retranslating an entire paragraph just because someone fixed a typo. [21:34] i know we tried with having online edits, and those who knew LaTeX would copy/pasta [21:35] I have plenty of big ideas, but no time to implement them myself. :/ [21:35] Well for the public frontent WordPress in my mind would be a good system (or Drupal) [21:35] tomswartz07: We did. I'm not sure how well that worked. I recall going through and fixing a bunch of LaTeX markup as a result of that. [21:35] tomswartz07: Some editors would miss a lot of the markup that they should've inserted. [21:36] i see. [21:36] benonsoftware: WordPress would be okay for part of the site. I don't know how well it'd handle our download page, though. http://ubuntu-manual.org/downloads [21:36] We also need to make sure the site is multilingual. [21:36] What do you mean? (About download) [21:37] The big download button on the front page should go to the latest version of the manual for whatever language is being shown at the moment. [21:37] Same with the 'buy this book' starburst. [21:37] I think that if we move to an online frontend for editing, it would be much easier for authors, but we would lose so much in the featureset in terms of formatting and editing [21:37] Right now those are broken a little bit because the site just wasn't designed with that in mind at the very beginning. [21:37] benonsoftware: The dropdown lists and options that allow you to select which PDF you want to download. [21:38] Okies [21:38] tomswartz07: Well, we'd need to modify the online editor to allow for the insertion of margin notes, screenshots, and the other elements that exist in our manual. [21:39] If the online editor stored the text in an XML format, for instance, then we could more easily convert it to HTML, ePUB, LaTeX, and other formats. [21:39] (There would still need to be some tweaking after the automatic conversion, I suspect, but it'd handle the bulk of the work.) [21:41] There was a second version of the Ubuntu Manual website that was created. It lives at . [21:41] I think it was designed to solve a couple of these issues (and got a face-lift). [21:42] But I'm not sure how to modify anything on the site (e.g., add new downloads). [21:42] I don't know if it's best to start from scratch or to build from one of the existing sites. [21:43] (I suspect it's best if we establish clear goals and use cases for our website and design new site from the ground up with these things in mind.) [21:43] +1 [21:43] what if we have an open call for new ideas? [21:44] tomswartz07: I think it's better that we establish an initial set of ideas first and then we can put it out there to get more opinions and have people look it over. [21:44] At my work, we have a method of code review (using gerrit) that allows many of us to make code changes to get approved before go-live [21:44] Otherwise I think it'd generate too many ideas and we'd never get anywhere. [21:46] perhaps I should rephrase; have an open call for those who can do website design, then take those people and have a brainstorming meeting [21:46] sounds good [21:47] Id be willing to head that group. I've done about half a dozen websites from (mostly) scratch. [21:48] that's very encouraging :) [21:48] but, godbyk; youre right. I think we need to get our heads together and get a plan before moving on anything [21:49] looking back at how muddled things got, i think planning is something that should be imperative [21:54] tomswartz07: I agree. [21:54] I think that we need to have a clear picture of what we want before we bring in the web developers. [21:54] yess [21:54] I think we should be flexible enough to change things a bit of the web devs thing it's a good idea, [21:55] but if we bring in a bunch of web devs and just say, 'Hey, we want a new website,' it's unlikely that we'll get what we really want. [21:55] yap [21:55] i agree [21:55] and we need to gain the respect of the community [21:56] or at least seem as an active project [21:56] c7p: That would definitely help. [21:56] And for that to happen, I think we need to get a lot better organized. [21:56] if we advertise more, it may help [21:56] We've been fairly slap-dash so far. [21:56] haha i agree [21:57] Ill tell you what. Ill talk to the guys at OMG: Ben originally started the project, so he's sure to be willing to advertise it [21:57] tomswartz07: They've done a great job in the past of advertising for us: posting about new releases of the manual and about our call for 'job' applicants. [21:58] I think that once we figure out exactly what we want/need, then we can go to them and have them help us get the word out. [21:58] But we can't skip that first step. :) [21:58] i concur. [21:58] +100 [21:59] they didnt talk about the oneiric release, though. did they? [21:59] we didn't contact them so i don't think they did [21:59] tomswartz07: Nope, but then I haven't emailed them about it directly, either. [21:59] at any rate, it might help to advertise it. we did work pretty hard on it. [21:59] tomswartz07: If you'd like to tip them off about it, you're welcome to. [22:00] sounds like a plan. Ill do that right now! [22:00] <('-'<) [22:01] Does anyone know who runs the meetingology bot? [22:02] Since mootbot appears to be defunct/dead, it'd be handy to have meetingology hand out in our channel to help with meetings. [22:03] godbyk: Alan Bell does [22:03] See #meetingology [22:03] benonsoftware: Thanks. I'll contact them. [22:03] No worries [22:04] benonsoftware: I've messaged Alan about it. [22:04] Okies [22:06] Should I ask OMG to put in about volunteers? [22:06] tomswartz07: Let's wait to hear back from hannie to see what authors are still available, etc. [22:06] if so, who to contact? [22:06] then we'll know what volunteers we'll need. [22:08] sounds good. :) [22:10] ok- im off! this laundry isnt going to do itself :P [22:11] great meeting everyone! talk to you all soon [22:11] See you later, tomswartz07. Thanks for coming! [22:11] cya tomswartz07 [22:12] thanks for coming [22:14] Hey.. meetingology has joined us. That'll come in handy for our next meeting. [22:14] xD [22:18] :P