=== daker_ is now known as daker [19:51] hello all [19:52] Hey, c7p. [19:52] Evening [19:55] hi everyone! [19:58] Hello [20:00] #startmeeting [20:00] Meeting started at 14:00. The chair is godbyk. [20:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [20:00] Yay, I remembered how that worked! :) [20:01] nice, i guess here is the agenda http://pad.ubuntu-uk.org/jM8mKDIKEB [20:01] [TOPIC] Find a new project leader [20:01] New Topic: Find a new project leader [20:01] * daker is here [20:02] Hey, ChrisWoollard.. still around? [20:02] Yes [20:02] Ah, there you are. [20:02] just poped downstairs for some food [20:02] Was popey involved? [20:02] (Sorry, couldn't resist.) [20:03] Back on topic now. [20:03] :) [20:03] So Ben's resigned as the project lead on account of being busy with other things and having a life and all. [20:04] That left us somewhat rudderless and we need to sort out the future of this project. [20:04] It has been noticed. [20:04] If we think the project should continue, we'll need to work on finding a new project lead (or at least a release manager for each edition). [20:05] (As well as finding folks to do all the other work that's involved in publishing a manual, of course.) [20:05] I guess the first question we need to answer is: Do we think the project should continue or should we let it die? [20:05] Do we have a Jobe spec? [20:06] ChrisWoollard: There's a short one here: http://typewith.me/dV3ZKFh1fp [20:06] But nothing too specific. [20:06] we want the project to continue, that's why we are here, right ? [20:06] o/ [20:07] I want it to continue [20:07] really? i'm here to see it die! muhahaha! [20:07] yap, ok is there anyone here who wants to lead ? [20:07] lol [20:08] not me :) [20:08] Are there any volunteers? [20:08] There are a couple ways we can go about this: [20:09] 1. Find a project lead who helps steer the overall project (across multiple releases), and [20:09] 2. Find an editor in chief for each release cycle who manages that particular edition of the manual. [20:09] These two roles could be filled by the same person or filled by multiple people. [20:09] i am reading the mailing list since some months but i am unable to vote on who could take the lead. [20:10] sipherdee: there is nobody as candidate until now so don't worry [20:10] godbyk: your are the defacto nexus of this project and as such the most natural candidate to now lead officially. yeah, i know, i'm mean ;) [20:11] thorwil: Oh, you're evil! [20:11] i agree [20:11] Unfortunately, I'm afraid I don't have the time to take on that responsibility right now. [20:12] The same for me. My time for this project is somewhat eratic. [20:12] I think we should determine the structure of the role(s) we need to fill (either a single project leader or a project leader and an editor-in-chief). [20:12] maybe we need other model of team management until we find a project leader [20:12] Then we can look for volunteers on the mailing list and elsewhere in the community. [20:13] So, potentially look outside of the project? [20:14] here we go http://typewith.me/GY2L5yJCUF [20:14] godbyk, can you right what we need and I can post it to the planet [20:14] + others [20:14] I can jot some notes in there, yeah. [20:15] ChrisWoollard: for the editors i think it's ok but for the project leader i'm not so sure [20:16] c7p: You don't think we should go outside of the project? [20:16] ChrisWoollard: for new members of course [20:18] and maybe for leader but independents if he/she has worked on other project [20:18] what about joining/building a bridge to the documentation team, to stay within my evil ways? [20:19] thorwil: I don't think anyone's against the notion, but we'd need some specific proposals/ideas on how to do that. [20:19] That isn't such a bad idea. [20:19] thorwil: Otherwise, we just end up talking a lot and nothing happens. [20:20] yes [20:20] Where as at the moment we haven't really talked or done anything [20:20] :) [20:20] The documentation team is being hit pretty hard this cycle, too, as they're not able to just repackage GNOME's upstream documentation. [20:20] Everyone has to write new documentation for Unity. [20:20] godbyk: i'm great at *not* talking a lot, but bad at diplomacy :) [20:20] Hello everyone. AM I late for the meeting? [20:21] jasono: A bit, but it's still going on, and you haven't missed much yet. [20:21] jasono: a little [20:21] Oh. :/ [20:21] not much [20:22] c7p: Did you have any specific ideas in mind for alternative team management models? [20:23] i have some ideas [20:23] c7p: Do tell! [20:23] :p [20:23] please share [20:23] what a leader does ? he set roles [20:24] we should set roles by ourselves since there is none [20:24] the problem that we have regards writing content [20:25] as far as i remmber ben was checking the text, he was highlighting changes and aditions that should be done [20:25] one member or maybe more should be in charge of this, tracking changes of future releases [20:26] then ben was writing at his blog and at omgubuntu about what our team does and what it needs [20:26] In my mind, the editor-in-chief is basically someone who wrangles all the chapter authors and editors and harasses them until they've turned in their work. [20:27] The EiC makes sure we hit our deadlines and basically drives the release. [20:27] The project leader, in contrast, is really there just for more big-picture things.. longer-term thinking. I think this role isn't nearly so important (at least as embodied by a single individual) as the EiC. [20:28] The responsibilities of the project leader could be split up and assigned to multiple individuals easily enough. [20:28] But I think that we really need an editor-in-chief for each edition. Someone who takes responsibility for that edition. [20:28] Communication could be done by whoever really [20:29] godbyk: +1 (leader could be split up and assigned to multiple individuals easily enough.) [20:29] Marketing, recruiting, cheerleading, etc., can and should be done by multiple people. [20:29] make the EiC an honor you have to apply for and who knows ...? [20:29] It might help if they can post to the planet. But that could be proxied through other people too. [20:29] My primary concern, then, is finding a good EiC. [20:30] The EiC role could be held be a different person each release cycle, or by one person for multiple release cycles (if they're good at it and willing to stay on). [20:31] Personally, both roles share me. Oh the Responsibly [20:31] s/share/scare [20:31] The EiC needs to be dedicated and willing to stick around at least for the duration of that release cycle. [20:32] could EiC role be taken by two people ? [20:32] The EiC role could be shared by a couple people as long as they work closely together. I don't think it ought to be distributed across more people than that, though, because then the responsibility level drops too much and people are willing to shrug it off too easily. [20:33] i agree on that two are enough [20:33] You could delegate responsibiliy to various chapters also. [20:33] ChrisWoollard: Each chapter would have its own author(s) and an editor, perhaps. [20:34] that would work [20:34] But I really want to have one (or two at most) people who have responsibility for the entire manual. [20:34] Agreed [20:34] To ensure it gets published on time, that it's of the highest quality, etc. [20:35] So... Should we move on and work on these roles later? [20:35] It's the EiC's job to manage the chapter authors/editors. [20:36] Sure. [20:36] what's next ? [20:36] [TOPIC] Quickshot [20:36] New Topic: Quickshot [20:36] Any Quickshot developers around? [20:36] or anybody that knows anything about it? [20:37] I saw jenkins in here earlier, but then he went offline. [20:38] I haven't seen flan in quite a while. [20:38] Personally i think quickshot is a big problem [20:38] Okay, so we need to find out the status of Quickshot: Is is ready for us to use on the Maverick edition? [20:38] Nobody seems to know anything about it [20:38] And we need to get some instructions written up on how to install and use it. [20:39] I know that flan and jenkins have both been really busy the past few months. [20:39] So we may need to scare up some more developers to help out. [20:39] As far as i know the screenshots are all that we really need for the maverick manual [20:40] Okay, I'll contact flan and jenkins to get a status report and see if they can write up some instructions for us. [20:40] I'll also see if they need more developers to help them out. [20:41] [ACTION] godbyk will contact Quickshot developers to get a status report, to get instructions for installation/use, and to see if they need more developers [20:41] ACTION received: godbyk will contact Quickshot developers to get a status report, to get instructions for installation/use, and to see if they need more developers [20:41] [TOPIC] Natty edition [20:41] New Topic: Natty edition [20:41] What do we want to do? [20:42] 1. [20:42] A full Manaul [20:42] For the Natty edition, we need to decide whther to publish a full manual or just release some sort of Unity supplemental. [20:42] 2. A New featues / changes guide [20:42] 3. Nothing (Wait to the next LTS). [20:42] 4. ? [20:42] unity is a headache fot the editions to come :/ [20:43] I tried the Alpha 1 and hated it. It never worked and drove me round the bend. [20:43] Can you give me an idea of some things that would be in the new features / changes guide? [20:43] Does anybody have views on what to do? [20:44] Ideally, I think our manual should cover the default installation/settings of Ubuntu. [20:44] I would say for Natty for example. Unity [20:44] So an Installation Chapter [20:44] So if Unity is the default desktop environment (or whatever), then we should cover that in the manual. [20:44] no unity isn't the default [20:45] It isn't theh default? [20:45] http://www.ubuntu.com/testing/natty/alpha2 [20:45] LINK received: http://www.ubuntu.com/testing/natty/alpha2 [20:45] (I'm behind the times on Natty.) [20:45] Looks like [20:45] LibreOffice [20:46] From ChrisWoollard's link: "Ubuntu Desktop will run Unity by default..." [20:46] I do wonder if that is set in stone. [20:47] if the hardware supports 3d or 2d it is default, if the hardware doesn't support video accelartion gnome 2.3 is default [20:47] I wonder if i depends on how far the development of it gets [20:47] if it is stable enough [20:47] Given that the GNOME desktop (panels) are the fallback when the hardware doesn't support Unity, will we need to cover both Unity and GNOME (panels)? [20:47] I would say yes. [20:47] Well, that'll increase the size of the manual a bit. :) [20:48] Isn't there also a 2d unity in developement? [20:48] if 3D is supported you will be able to run Unity, if not you will be able to run Unity-2D [20:48] My opinion is that I should be able to hand a copy of our manual and an installation CD to someone and they should be able to install and start using Ubuntu. [20:49] So if Unity and GNOME environments are both included on the CD, we should cover them in the manual. [20:49] +1 [20:49] that's right [20:49] We may be able to downplay the GNOME environment a bit if we don't think most people will see it, but it should at least get a mention and pointers to more info about it. [20:50] i'd say a mention and pointers to more info about it should be all it gets [20:50] I really depends on how likely the fallback will be [20:51] I know that Ubuntu in a VM never seems to have 3d. Or at least whenever I have tried it [20:51] We have plenty of GNOME material already written. So we could repackage that as a supplemental that we can point to, perhaps. [20:52] ChrisWoollard, to run Unity in VM you need VirtualBox4 [20:52] Oh Okay, I haven't tried VB4 yet. [20:52] I gave up on VB at version3 because it have performance issues whenever i used it. [20:53] Do we have a consensus on how to handle the Natty edition? [20:53] two chapters, one for gnome and one for unity ? [20:53] Maybe we could have a vote on what to do? [20:54] ChrisWoollard: We could. What are the options? [20:54] 1.) Full 2.) New Feaures / Changes + Installation 3.) Nothing [20:54] 4? [20:55] I think (1) could be split into two options: (a) include both GNOME and Unity in one manual, or (b) include only unity and point to a supplemental fascicle for GNOME. [20:56] So our options would be: 1(a), 1(b), 2, or 3. [20:56] Do we want to vote on those? If so, I guess just shout out which option you prefer. [20:56] concentrate on defaults/the common case, everything outside of that risks causing confusion and is too mabitious regarding workload [20:57] mabitious, cute [20:57] thorwil: So that's kind of a vote for 1(b) where the fascicle may not exist? :) [20:57] 1(a) if we have enough editors till then [20:58] I am worried about the number of people we having working on it. [20:59] ChrisWoollard: I am, too. But I think we have to have some of these decisions made before we can recruit for volunteers. Otherwise when people show up, we won't have anything ready for them to do. [20:59] I would like 1a i think [21:00] everyone has the right to vote, comon :P [21:00] Looking at the Maverick edition, I think chapter 2 ("Around the Desktop") is the one most affected by the Unity change. And that chapter is only 15 pages long. (And not all of those pages will have to be modified.) [21:01] Given that, I'll cast my lot in with 1(a) as well. [21:01] (If it were more material than that, the I'd be tempted to go with 1(b) to avoid confusing people with two different desktop environments.) [21:02] Ok [21:02] (I think if we go with 1(a), we'll want to move the GNOME stuff to an appendix or someplace out of the way.) [21:02] I agree. Appendix for Gnome would work. [21:02] Last call for votes? [21:03] Going...... [21:03] ...........Going....... [21:03] :D [21:04] .......................................... Sold...... To the Alien in the cheap seats!.... [21:04] [ACTION] The Natty manual will cover both Unity and GNOME environments [21:04] ACTION received: The Natty manual will cover both Unity and GNOME environments [21:04] [TOPIC] Maverick edition [21:04] New Topic: Maverick edition [21:04] It needs screenshots [21:05] ChrisWoollard: Is that really all that needs to be done? [21:05] I think most of it was written and editted. [21:05] Okay. I guess I had assumed we still had a bunch of editing to do, or something. [21:05] Obviously, it could do with checking. [21:06] Always. :) [21:06] I know all the big changes were done. [21:06] So I guess we'll need to wait to hear back from the Quickshot folks then? [21:06] Yes. [21:06] So the action is to kick the Quickshoters [21:07] Cool. I'll use that as leverage. "You guys are holding up the Maverick edition!" [21:07] nice nice [21:07] [TOPIC] Recruiting [21:07] New Topic: Recruiting [21:08] regarding this, first we need to define the roles to be taken and the tasks that should be done [21:08] We need to complete those role specs [21:09] Can we also maybe copy Maverick to a new branch to start working on Natty> [21:09] ? [21:09] ChrisWoollard: We'll create a new natty branch. [21:09] I'll try to do that later today. [21:09] (After I remember how it all works again. :-)) [21:09] We can't really get people to work on stuff until that is gone [21:09] dos/gone/done [21:10] nice, regarding natty changes have in mind this pad http://typewith.me/1rgiBqwp8U [21:10] fill it with whatever is missing [21:11] [ACTION] godbyk to create a natty branch [21:11] ACTION received: godbyk to create a natty branch [21:12] Once that is done I can try to get new people to help. [21:12] I think that we should try to find an EiC for the natty edition ASAP. [21:13] Then they can jump in and start driving that release. [21:13] How / Where? [21:13] Well, we should finish the job description first, probably. [21:13] Then we can post it to our mailing list and see if anyone there wants to step up for that role. [21:14] We should ...... never mind [21:14] you got there first [21:14] If not, then we can cast a wider net: hit up the planet and OMG!, etc. [21:15] While you guys are still around, can you help out with the EiC job description? [21:15] [TOPIC] Natty editor-in-chief [21:15] New Topic: Natty editor-in-chief [21:15] The job description is being worked on at http://typewith.me/GY2L5yJCUF [21:17] (I hate writing job descriptions.) [21:20] you guys are good in writing descriptions :p [21:21] Anything else left to cover? [21:23] i think it's all that should be written [21:23] ChrisWoollard: Nothing else on the agenda. [21:23] I think we'll try to clean up this editor in chief job description and then post it to the list. [21:23] guys something more [21:23] ChrisWoollard: Do you want to handle the recruitment of the EiC? [21:23] Should we formally close, but continue to sort out the jov specs [21:23] ChrisWoollard: Works for me. [21:23] c7p: What else do you have? [21:24] [TOPIC] Any other business [21:24] New Topic: Any other business [21:24] i think we should work a bit on site these months [21:24] i mean to add new content [21:24] "on site" [21:24] or update the existing [21:24] website* [21:24] c7p: Oh! [21:24] I know there is a beta for the website [21:24] c7p: There is a new test site out there: http://test.ubuntu-manual.org/ [21:25] nice [21:25] humphreybc and daker were working on it before humphreybc left. [21:25] I'm not sure what it's status is. [21:25] What do you want me to do for the EiC? [21:25] c7p: But, I agree, we do need to work on the website at some point in the not-so-distant future. [21:26] ChrisWoollard: When we finish the description, do you want to send it to the list? [21:26] yes we need to have a least a nice and comprehensive "get involved" and "about us" section [21:27] godbyk: Ok, np [21:28] c7p: I agree. [21:28] c7p: Remind us when we schedule the next meeting to add that to the agenda. [21:28] ok [21:28] Should be have another meeting in a couple of weeks? [21:29] ChrisWoollard: Probably a good idea. [21:29] So we can see how our recruiting efforts went and to get a handle on the natty edition before we run out of time there. [21:29] Is Saturday 20:00UTC a good time? [21:29] any views? [21:29] It works well for me. [21:30] we may set a poll [21:30] c7p: can you schedule the next meeting? [21:30] with the poll? [21:30] of course [21:30] thanks [21:30] no problem [21:31] Any other business, anyone? [21:31] Can you check the Minutes? [21:31] http://pad.ubuntu-uk.org/jM8mKDIKEB [21:31] LINK received: http://pad.ubuntu-uk.org/jM8mKDIKEB [21:31] We'll continue to work on the editor-in-chief job description at http://typewith.me/GY2L5yJCUF if anyone cares to join us. [21:32] ChrisWoollard: Looks good to me. [21:32] I'll post the minutes to the Wiki. [21:32] 'kay. [21:32] #endmeeting [21:32] Meeting finished at 15:32. [21:32] nice [21:32] ChrisWoollard: Can you post the minutes to the mailing list, too? (Along with a link to the transcript.) [21:34] where do i find the transcript? [21:34] I will post to the list. [21:36] ChrisWoollard: http://irclogs.ubuntu.com/2011/02/12/%23ubuntu-manual.html [21:37] almost forgot it, me and Patrick are working on rewriting the getting started as editor/author https://docs.google.com/document/d/1B0zSycRKFmWy39ipsS-1VYw43UYdrvY1MSpY9s5Emkk/edit?authkey=CKWU8dYM&hl=en# if you guys have some time check it and let me know your opinion and if you find any typo etc [21:38] c7p: Sure thing. [21:38] Lemme finish this job description first. [21:38] i can give anyone editor privileges if they want [21:39] I'll have a look also [21:39] It looks good so far. [21:43] should i add on leader and Eic description pad the description of an editor -we have written it during a previous meeting- ? [21:44] c7p: Sure, you can drop that in someplace. It might be helpful. [21:44] ok [21:44] (I feel like I'm starting to just dump everything on the poor EIC!) [21:45] Oh, that's not bad. [21:46] haha [21:46] well he may not be the only who is responsible for all these [21:48] list of UMP pads http://typewith.me/OzNMJ6gyKk , you don't have to bookmark all these. Just bookmark the list [21:49] Oooo, We now have a Chapter Editor as well. [21:50] what's the difference between author and editor ? [21:51] c7p: The author writes the text and the editor proofreads it (basically). [21:52] My brain's going in circles now. What am I missing in the EIC description? [21:52] poor EiC [21:52] If nothing obvious is missing, I'll turn it over to ChrisWoollard to tighten up the text a bit. [21:52] :p [21:52] c7p: I know! [21:53] I'm trying not to dump everything into one role, but there really is a lot for the EIC to do. [21:53] Many of those duties are shared among other roles, too, of course. [21:54] you should write this cause it's very deterrent to become an EiC when you see this list ! [21:56] godbyk. I will have a look at the text in a while. [21:58] ChrisWoollard: np [22:02] Now I have to look through the minutes to see what I crazy stuff I agreed to do. :-) [22:07] Okay, I've emailed the Quickshot guys. I'll let you know what I hear back. [22:07] Next up: Branch for natty. [22:07] EiC is release manager ? [22:08] c7p: Yes. [22:09] ok thx [22:10] all: have a nice weekend :), bye