[00:58] Hi all [00:58] Sorry I missed the meeting [17:35] I'll probably be sleeping when the meeting happens, but I'll check the channel out after I wake up. [20:51] Hey, rickfosb [20:55] hello world ! [20:55] hey, c7p [20:56] how are you godbyk ? [20:57] Hello godbyk, c7p [20:57] not too bad. and you, c7p? [20:57] godbyk: fine :) [20:57] hey rickfosb [21:00] godbyk, liked the pdf site. I just glanced at it; is it free use? [21:00] ηευ ChrisWoollard [21:01] hey* [21:01] Hello [21:01] rickfosb: Yeah, it's free for nonprofit use. [21:01] I like it! [21:01] yeah great tool [21:01] Hello ChrisWoollard [21:01] Evening rick [21:02] Hey, ChrisWoollard. [21:02] Evening Godbyk [21:03] who is here for the meeting, raise your hands ! [21:03] o/ [21:03] Guys, only 5 signed up on the poll. (I didn't vote) HERE [21:03] \o/ [21:03] I'm here. [21:04] ChrisWoollard, I'll need to look that one up :-) [21:04] two hands up :) [21:04] Hannie sent an apology, if I recall the email strings [21:05] Is everyone who said they were available in the poll here? [21:05] Ah yes, I see it now! [21:06] agenda: http://pad.ubuntu-uk.org/tXtRXeYMKv [21:07] \two of you are [21:07] c7p and ChrisWoollard [21:07] meetingbot ? [21:07] #startmeeting [21:07] Meeting started at 16:07. The chair is godbyk. [21:07] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:07] Bryan, Mario, and Ben signed up [21:07] [TOPIC] Should the Natty release continue? [21:07] New Topic: Should the Natty release continue? [21:08] Any thoughts? [21:09] Natty release has many problems [21:09] My 2 cents: I would rather not stop work. But perhaps we can try some new tools to help move along... like your pdf edit... Maybe some additional advertisement via Planet Ubuntu [21:09] I think that maybe not. Otherwise we are always playing catchup. It would be great to get the manual out at around release. [21:10] first, the natty manual will be out around when the oneiric will be released [21:10] who will be interested on an outdated manual ? [21:10] I'm ok with Halting Natty; assuming we work on the process to get our manual out at 'release'... Is that even possible? [21:10] rickfosb: Well, we managed it with our first manual (lucid). [21:11] you probably had a better editor in chief (grin) [21:11] rickfosb: And back then we were still inventing our tool chain and starting from scratch. [21:11] rickfosb: (I guess I was also unemployed then and had more time to spend on it, too. :-)) [21:11] rickfosb: no we hadn't even an editor [21:11] It could be possible. Natty and Oneric don't look vastly different so therefore it might be possible to tweak it enough [21:12] So, IF we take what we have --> move directly to Oneric... what do we save? [21:12] If skipping Natty and going straight to Oneiric would allow us to get back on track and release the Oneiric manual at the same time as the software, that'd be awesome. [21:13] godbyk: yeah [21:13] I think we'd save some of the intermediary steps (various editing milestones, writing freezes, etc.). [21:13] also we need some new authors, cause ours have gone. New authors would be interested on releasing a manual that will be read [21:14] So, how about doing on ly 1 release a year... same release each time X.10 [21:14] or XX.04 which ever [21:15] I think it depends what changes [21:15] good point [21:15] ChrisWoollard: I agree. I think it'd be nice to have manuals for the LTS releases, at a minimum. [21:15] Unity required quite a big change [21:15] i don't think the 2 releases is the problem, the problem is that we don't keep authors motivated :/ (maybe) [21:16] If we had people working on writing and editing, I think we could manage the six-month releases. But we'll need to continually recruit new members to replace the ones that have left. [21:16] It would also be nice to have the manual for the one prior to LTS also. [21:16] yea, they (we) all start out strong and then life happens [21:16] ...Or find a way for anyone to easily do that drive-by editing/writing. [21:16] godbyk: +1 [21:17] on this subject Kevin i think we can deploy google docs [21:17] it's online, it's easy [21:17] I really like the pdf site as a way to get people to help out. Especially if one of our ubuntu members (hint) could post to the planet every so often [21:17] At some point we should probably survey our team members and get an idea of what does prevent them from helping. Is our tool chain too cumbersome? Do they just not have time? Are all the tasks too boring? [21:17] or any relevant service* [21:18] Well, I like the tool chain; but I do find that I'm 'fixing' latex after a revision from some of the authors... like they don't run make... [21:19] That has always been an issue [21:19] so it may be an issue for some =-- tool chain that is [21:19] I have been doing the same [21:20] i think we need one who will be in charge of this getting new people, motivating them, getting feedback from them etc [21:20] so, if we used google docs; or a pdf annotation tool, and did continuous outreach.... that might help us make the major revisions on time... [21:20] Would it be better if there were a two-stage editing process then? Something more accessible (wiki, Google docs, Etherpad) that the authors and editors could work with. Then another stage for the LaTeX geeks to handle the nit-picky LaTeX markup and layout? [21:21] Maybe reach some of the folks who are making the code changes to annotate [21:21] godbyk +1 [21:21] +! [21:21] +1 [21:22] c7p is really excited about it ;) [21:22] i can handle the Latex markup [21:22] +1 I think [21:22] xD [21:23] What would happen if once the google doc had been latexed and the author wanted to make changes? [21:23] The trick with two stage is keeping the updates linear... I've had that problem when getting text in the same chapter from multiple sources... [21:23] exactly ChrisWoollard [21:23] ChrisWoollard: I think after it was LaTeX'd, the changes should be noted on the PDF and the LaTeX editors would make them. (We'd also need to track the changes in the original doc for future versions, too, I guess.) [21:24] btw i want to share something with you [21:24] back to our current toolchain to help with version control... [21:24] It seemed like there was also a problem figure out what we needed to update and write about this time, too. Maybe there should be some initial meetings where we do some research and establish a clear and detailed outline of what's new, what's different, etc. so we know exactly what needs to be written. [21:25] Then the assignments to the authors could be more specific. [21:26] godbyk: agree, since I'm not running a beta... i've no real clue.. guess I'll have to learn how to run two versions [21:26] True [21:26] c7p was going to share? what? [21:26] http://www.ubuntu.com/testing usually has release notes about what has changed [21:26] LINK received: http://www.ubuntu.com/testing usually has release notes about what has changed [21:27] I'll book mark that now (while I'm thinking about it) [21:27] rickfosb: i'm talking with the guys from the greek community that are involved to a community magazine. We have exactly the same problems as projects. EXACTLY ! [21:27] people are leaving, the process of writing is too technical, project misses its goals etc [21:28] c7p: that makes me feel a little better. :-) have they found any solutions? [21:28] no we are searching :P [21:28] what i've concluded is that we have to keep the writing process as easy as possible [21:29] how about this; what is our goal here? If we are just a printed version of help, then we're duplicating effort. If the goal is to provide user friendly information, then maybe we've added too much content [21:30] also we have to motivate contributors constantly, everyone has little free time, but with no motivation, rewards people lose their passion [21:30] trim it down and point to online help when it gets 'too technical' [21:30] (I hear ya! c7p; I could use a week off too! ) [21:31] As far as was aware we are aimed at non techies. So there shouldn't be anything to technical [21:31] The original aim of the project was to produce a printed and bound book for new Ubuntu users. [21:31] rickfosb: the documentation for the too techy stuff exists but the process is still complex [21:32] We assume that the readers have some basic computer knowledge (how to use a mouse and keyboard, etc.). [21:32] ChrisWoollard, has the document gotten to 'fat'? [21:32] *too [21:32] The printed book aspect is important for new users because it's something they can scribble notes in as they learn, something they can set on their desk alongside them as they work through a procedure. [21:33] I like the book aspect; otherwise, why bother just do help.ubuntu... [21:33] I don't think the size has changed much. 154 pages is quite slim really [21:33] We actually have fewer pages now, but I think the bulk of that change is because I shrank the screenshots. [21:34] ChrisWoollard, if we keep the same structure then (chapters) and target LTS releases, and significant interim releases, is that doable (given a constant flow of help) [21:34] i think we have to rethink the whole content of the manual, but it's not subject now. we have to look on it of course later [21:35] on a coming meeting [21:35] ok [21:35] Right now we have a couple topics that are somewhat conflated: [21:35] (1) Do we cancel the Natty release in favor of starting work on the Oneiric release (so it can be published on time)? [21:36] (2) What can we do to improve our workflow and project's chance of success. [21:36] I'm inclined to vote yea on item 1 [21:37] I'm loathe to take a vote with so few voters, but at this point, I think we're the only active project members. :-/ [21:37] #2 (I like providing content for the 'world' to comment on and let us do the latex) [21:37] (1) +1 [21:38] godbyk +1 I know [21:38] I'm also inclined to vote +1 to canceling the Natty release and moving straight to Oneiric. [21:38] me too [21:39] I guess we can make it official... [21:39] even if we don't have enough authors i have the time and energy to pull this release [21:39] [VOTE] Cancel the Natty release and move on to the Oneiric cycle. [21:39] Please vote on: Cancel the Natty release and move on to the Oneiric cycle.. [21:39] Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot [21:39] E.g. /msg MootBot +1 #ubuntu-manual [21:39] +1 [21:39] +1 received from ChrisWoollard. 1 for, 0 against. 0 have abstained. Count is now 1 [21:39] +1 [21:39] +1 [21:39] +1 received from c7p. 2 for, 0 against. 0 have abstained. Count is now 2 [21:39] +1 received from rickfosb. 3 for, 0 against. 0 have abstained. Count is now 3 [21:39] +1 [21:39] +1 received from godbyk. 4 for, 0 against. 0 have abstained. Count is now 4 [21:40] I think that's all of us, right? [21:40] yes [21:40] [AGREED] Cancel the Natty release and move on to the Oneiric cycle. [21:40] AGREED received: Cancel the Natty release and move on to the Oneiric cycle. [21:40] (I'm not sure if that closed the voting or not. I hope so.) [21:41] what is the release Date for Oneiric [21:41] +1 [21:41] yep [21:41] October 13. [21:41] 13th October [21:41] https://wiki.ubuntu.com/OneiricReleaseSchedule [21:42] We've already passed the UI freeze date, so things should be fairly settled. [21:42] So we go through the release notes and try to get the natty text updated? [21:42] If you're not already, you might wish to subscribe to the ubuntu-docs mailing list. They send UI freeze exception requests to that list so you can track the things that are still in flux. [21:42] Godbyk: Can you transfer the natty branch to a new oneric one? [21:43] i'm from 11.10 now, i can track all the changes that need to be done [21:43] ChrisWoollard: Yeah, I can set up the bzr branch. [21:43] good [21:44] What was remaining on the to do list for the Natty release? [21:44] We'll need to transfer those items over. [21:44] Not sure, but I did think that some editting was required [21:44] i will make a complete todo list maybe tomorrow, by tracking the changes [21:44] And we should get a few people to read through the various parts of the manual and ensure that they're up to date with Onieric. [21:45] (That, in my mind, involves reading a section and clicking on whatever it says to click on.. ensuring that the text is the same and that the process still works as written.) [21:45] godbyk: +1, the tool that you shared with us would totally help us [21:46] c7p: Once I get the oneiric branch created, I'll upload a new 11.10 PDF and we can start passing the link around. [21:46] Reading the worksheet; the last three chapters showed lots of potential changes; but I never saw revisions to indicate that they'd actually done them. [21:46] c7p +1 [21:46] i mean godbyk +1 [21:48] ChrisWoollard do you post your blog to planet ubuntu? I've seen your name.. might help once we get the link to the pdf to get the word out? [21:48] I do sometimes. It is my choice if it goes there [21:49] just tell me what you want and i can arrange it [21:50] ChrisWoollard thanks! I think once we get the branch built, and the first pdf built, we might want to blog about what we're up to... get a bigger audience? [21:50] rickfosb is shamelessly using ChrisWoollard [21:50] np [21:51] i think we must have the 11.10 pdf in a good status before sharing it with the planet [21:51] I would agree to that... talk about a firestorm.. :-)) [21:51] heh.. no doubt! [21:52] maybe we can share every chapter when it's almost finished [21:52] the vote may not be closed; I have a private message that I already voted [21:52] smile [21:54] c7p; just take the pdf by chapter? [21:54] :D, nevermind, the decision has been taken. the bot wants to sabotage us [21:54] We've been writing and editing the chapters in parallel, not in serial. [21:55] So we haven't all been focusing on, say, chapter 2 until it was finished and then moving on to chapter 3. [21:55] yeah, i'm talking for the sharing the pdfs for proofread and comments before the mani release of the whole book [21:55] I think 1 - 3 are in decent shape; we'd need to review the release notes. not sure about the screen shots [21:55] Most are done, I thought; [21:56] i think so [21:57] godbyk, when do you think you could have time to create the new branch? [21:57] rickfosb: I can probably get it done later today. [21:58] cool [21:58] After the meeting, I'll work up an email to ubuntu-manual and let them know what we're up to, along with the raw meeting log, etc. [21:58] 'kay [21:58] are we done ? [21:59] have we finished* [21:59] Once you get the pdf location arranged,,, is that something that any of us could upload, or would that be you after a bzr revision? [22:00] rickfosb: Well, I figured I'd change the version number in the PDF to reflect 11.10 instead of 11.04 before uploading it. [22:00] yes sir. [22:00] Otherwise, anyone can upload a PDF to the site (it's free) and share the link. [22:01] i'm happy that some things have been set in order [22:01] Its not to hard to do global search and replace on the chapters to fix the other version numbers... and names... [22:01] rickfosb: this have to be done on all tex files [22:02] if the branch will be up tomorrow, we have to do a lot of work :P [22:02] yes.. I've been using vi or gvim and stepping through the chapters when I found a global that needed work [22:02] nice [22:02] I'll send you guys an email as soon as I get the branch created. I'll also upload a PDF to that site and give you the link to it. [22:02] ok, what else tonight? [22:03] godbyk Great! [22:03] great all [22:03] Something else I think we should do soonish it to create a simple, informal survey and email it to the list. [22:04] survey for what ? [22:04] I'd like to get feedback from the team members to see how we can get them involved again, why they're not actively participating at the moment, how we can make things easier, etc. [22:04] godbyk; I'll put that in my email to the team! [22:04] if you want? [22:05] rickfosb: sure! [22:05] so rickfosb will handle the survey ? [22:05] (its text... so not a 'formal' survey) [22:05] I can rattle of a bunch of random questions I have for the team if you like. [22:05] did you have something else in mind? [22:05] perfect! [22:06] I was thinking of just asking some rather open-ended questions and get some free-form answers. [22:06] Nothing scientific or anything formal. [22:06] I just want a better idea of where the sticking points are. [22:06] neat [22:06] you want to think about it and email me? I'll do the email tomorrow [22:07] rickfosb: that sounds like a plan. [22:07] cool, I'll use your email as my "go" to email the team [22:07] btw if that helps you, you can use forms from g docs [22:07] 'kay. [22:08] thank you all [22:08] c7p: that's not a bad idea. then all the responses can go in a spreadsheet that we can share. [22:08] forms? [22:08] godbyk: yeah you dont have to organize them :) [22:09] check goole docs, go create > forms [22:09] wow! I never used a form... that alright [22:09] thanks! [22:09] create new* [22:09] g2g see you soon [22:09] thanks for coming, c7p! [22:10] i hope to come up with the list of what needs to be done for 11.10 tomorrow or the day after tomorrow [22:10] see you and thanks c7p [22:11] godbyk, ChrisWoollard, any thing else tonight? [22:11] not that i can think of [22:11] rickfosb: not that I can think of [22:11] despite this, I am enjoying working with you guys [22:12] i'm looking forward to the pdf annotations; [22:12] Guess I should do this before I forget... [22:12] #endmeeting. [22:12] #endmeeting [22:12] Vote is in progress. Finishing now. [22:12] Final result is 4 for, 0 against. 0 abstained. Total: 4 [22:12] Meeting finished at 17:12. [22:12] :) [22:12] have a good evening, then. [22:13] :) [22:13] Mootbot gets irked if you forget to end the meeting. :)