=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has left #ubuntu-meeting [] === warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Technical Board meeting Tuesday 19 October 2004 | Agenda on wiki.ubuntulinux.org/TechnicalBoardAgenda === Topic (#ubuntu-meeting): set by mdz at Tue Oct 12 19:45:33 2004 === #ubuntu-meeting [freenode-info] why register and identify? your IRC nick is how people know you. http://freenode.net/faq.shtml#nicksetup === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting === pitti_ [~martin@195.227.105.180] has joined #ubuntu-meeting === pitti [~martin@195.227.105.180] has left #ubuntu-meeting [] === warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Technical Board meeting Tuesday 19 October 2004 | Agenda on wiki.ubuntulinux.org/TechnicalBoardAgenda === Topic (#ubuntu-meeting): set by mdz at Tue Oct 12 19:45:33 2004 === warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Technical Board meeting Tuesday 19 October 2004 | Agenda on wiki.ubuntulinux.org/TechnicalBoardAgenda === Topic (#ubuntu-meeting): set by mdz at Tue Oct 12 19:45:33 2004 === hornbeck [~hornbeck@adsl-68-92-227-78.dsl.okcyok.swbell.net] has joined #ubuntu-meeting [03:45] Hi! Is there a documentation meeting today? (In a few minutes I think...) === mvo_ [~egon@suprimo-230.ping.de] has joined #ubuntu-meeting [03:55] yes you are in the right place asw [03:56] I am helping the wife for a few more minutes than I will be in here [03:57] Cool... [04:02] Is there an agenda or a web-page for this meeting? [04:02] I only saw the notice is ubuntu-users/devel... === plovs [~plovs@62.84.21.44] has joined #ubuntu-meeting [04:03] no there is no agenda [04:04] we just wanted to get some people together who has some ideas on the docs and which direction we should go with them [04:04] but we will give people a few more minutes to get in here [04:05] hi [04:06] ok. will transcripts be posted? [04:07] (I'm pretty bad at IRC so I'm happy if they are not...) [04:07] transcripts are good for people who couldn't make it [04:08] http://wiki.ubuntulinux.org/DocumentationAgenda [04:08] there you go [04:08] I do believe that there will be transcripts [04:08] mako: you really here? [04:08] transcripts are good I just hate all the spelling/grammar mistakes that are saved for posterity... =^) [04:09] well noone is perfect [04:09] that is what spell check is for [04:09] I don't know how to use spell-check with irc. (I use xchat) [04:09] I meant outside irc [04:09] I use xchat also [04:10] there will be mistakes on irc because you are typing fast and trying to keep up with conversations === ..[topic/#ubuntu-meeting:hornbeck] : Documentation meeting Friday 15th October 2004 | Agenda on wiki.ubuntulinux.org/DocumetationAgenda [04:11] well I guess others will show up [04:12] a couple more about to be here [04:14] I have some particular things I'd like to work on but since I'm new I don't know what the etiquette is... [04:14] hold one sec === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting [04:15] will docbook be used for documentation? [04:15] hold one sec [04:15] other main people are on their way === sivang [~pooh@80.179.66.136.forward.012.net.il] has joined #ubuntu-meeting [04:15] don't want to get in discussions and have them lost [04:15] plovs: are you Poslavsky on the wiki doc-team page? === plovs holding his breath [04:16] yes === enrico [~enrico@enrico.developer.debian] has joined #ubuntu-meeting [04:16] ok, there is about the last one I was waiting for [04:18] Hello, and good afternoon. Sorry for the delay, I understood it was 16.00 UTC instead of CET [04:18] me also :) === ph_ [~ph@pD9E6B6F0.dip.t-dialin.net] has joined #ubuntu-meeting [04:19] There will be a documentation meeting this friday at 1400UTC in [04:19] #ubuntu-meeting on the freenode server [04:19] :) [04:19] I'd like everybody to introduce himself a bit, [04:19] Since we're all here, we can start. How about a round of introductions? [04:20] Shall I start? [04:20] :) [04:20] I am John Hornbeck, I worked with the Gnome doc team for awhile and have started alot of work with Ubuntu so far [04:20] hornbeck? [04:20] I live in Oklahoma [04:20] is that good [04:21] next? [04:21] I'm Sivan Green, I'm from Israel. I've started the /UDP page on the wiki, with some thoughts about [04:21] the directions of ubuntu's documentation. [04:22] I'm Enrico Zini, Italy. I've been working on designing a community-based approach to produce documentation [04:22] I'm a long time Linux user, programmer and have had experience with documentation on some corporate company. [04:22] I'm Colin Watson, Canonical staffer, Ubuntu installer team leader, really just lurking here while doing other stuff, since I've been doing the installation manual work for warty. [04:22] Kamion : nice to see you here :) [04:22] I'm AlexanderWait on the wiki -- http://non.fiction.org/~await -- I would like to see free software and ubuntu in particular more widely adopted in scientific applications. I am working on a new alife project for my phd. X3D/VRML, GNU Arch, Boinc (seti@home) are some of the technologies. I've used Linux commercially since 1993. [04:23] I am AlexanderPoslavsky, I'm from the Netherlands,I work as windows admin, but prefer linux :) [04:23] hehe, I am a windows admin also [04:23] anybody else? [04:24] mako ? [04:24] I guess everyone else is just watching [04:25] so six of us than [04:26] Enrico, Sivang, Hornbeck, Asw, Plovs, Kamion [04:26] (don't consider me part of the doc team please, as I said I'm just lurking really) [04:26] ok [04:26] Doc team: Enrico, Sivang, Hornbeck, Asw, Plovs [04:26] Goal: Total world domination [04:26] it's a start... [04:27] I guess we're here to discuss how to get to that [04:27] yes [04:27] yes. [04:27] would you like us to discuss what we have done so far? [04:27] yes please [04:27] hornbeck: sure! [04:27] so everyone can be caught up to speed [04:27] ok, I will start [04:28] good idea, let's have an overview for what already exists. [04:28] I have mainly worked on the wiki trying to get alot of it up to speed [04:28] I have also worked on the start page for Warty and also working on the gnome-user-guide to go into warty === plovs off to another meeting irl, i'll read th log and be back asap... [04:29] I try to stay active on the mailing list so i get more ideas of faqs and other information that needs docs [04:29] thats it for me [04:30] asw? [04:30] I'm completely new. [04:30] sivang? [04:31] Could somebody mention JohnLevin, BenEdwards or KevinWixted (they are on the DocumentationTeam page) [04:31] yes, [04:31] I'd recommend everybody to take a look at the /DocumentationTeam page, see the people who are listed there to get an idea [04:32] (Also robertbrimhall) [04:32] please see also /DocumentationArea more wiki work by interested people [04:33] anybody correct me if I slipped away any other piece of index web, for what others have done by now. [04:34] looks right to me [04:34] As of myself, I'm less of a documentation person and more I'm more interested in user-centered design and in facilitating community creativity [04:36] ok, so we know who we are now [04:36] I have a few questions [04:37] enrico: Where would you like us to be as far as docs, for Hoary [04:37] that is a large question I know [04:38] That is a large question [04:38] ok I will make it smaller [04:38] Let's try and see what we can see for warty, both offline and wiki wise. We might want to concentrate on a modest milestone, and after warty to head up for the big plans for Hoary. [04:39] sivang: warty is about out the door [04:39] I'm reading http://wiki.ubuntulinux.org/HoaryHedgehog_2fReleaseSchedule [04:39] we can do keep up docs for it, but the goal as I see it right now is Hoary [04:40] enrico: a better start question would be, what areas are we looking at documenting [04:40] sivang: yes. It's reasonable to start some working together first, then make release-oriented plans [04:41] So there is a "seedFreeze" Nov.29 and feature freeze feb.7 when do we stop writing documentation? I want to understand how much time we have. [04:41] So, ideally, there should be no documentation at all. Programs should just work, and do what users want. [04:41] asw: we are still working on docs for warty [04:41] you guys don't have to worry about the seed freeze very much [04:41] enrico: yes [04:42] Documentation comes in when programs are not that clear, or when the users don't know what they want [04:42] This highlight two fields of working :) [04:42] the problem you'll have is that not all the documentation you'll need to write will be clear *until* feature freeze [04:43] but by shortly after feature freeze you'll probably want to have the guts of most of the docs and then start polishing [04:43] so alot of late night before a release [04:43] Kamion: yes. Which brings us back to the debian categorizatin problem: how can I have a good category database without even knowing what software is in the distr? [04:43] And, in the traditional computer-science style, what we need to do is change the nature of the problem ;) [04:44] enrico: that comes back to, what all are we going to document [04:44] are we going to have our own docs for everything? [04:44] no. [04:44] hornbeck: docs for everything? No, please no [04:44] That would be bad, for various things [04:44] or are we going to use docs from other places and feel in the spots [04:44] - disrespect for all the good work that already exists [04:44] - lots of work to do [04:44] enrico: I was just giving a example [04:45] not asking to do so [04:45] - it would disconnect us from the rest fo the community [04:45] Doc should handled similar to packages: keep ubuntu-specific changes, but base on upstream docs [04:45] hornbeck: ah, ok, sorry :) [04:45] pitti : exactly [04:45] AFAICS you can even use the same tools (diff, etc.) for it [04:45] yeah [04:45] So, back to my original discourse, one line of working would be see what's unclear in Warty, then check if it's been either fixed in Hoary or if it needs documenting [04:45] yes, and that would enable us to feed debian back, as our ROCK [04:46] I am interested in documenting specific subsystems (eg hardware accelerated 3D), GNU Arch for developersm, maybe TeXmacs... in general I'm interested in working on "Ubuntu for Scientists" [04:46] Working based on what the issues are will also allow us to produce documentation which addresses what users are actually trying to do [04:47] Ideally we should probably follow this to start up a bit: [04:48] 1) Identify the goal our users might want to accomplish. [04:48] I see we're having two identities here: from one side we have frenzy in the hands and we want to *write*, and from the other we are into a designing phase for the work === sivang agrees === hornbeck agrees also [04:48] On these two identities, both are important, and one kills the other [04:48] you might find it easier to start from reviews of the existing upstream and Debian documentation and work out what needs to be added/contributed/improved [04:48] This is a nice Hegelian dialectic [04:49] Resolving dialectics lead to Genius, and of course Total World Domination [04:49] 2) Investigate current works to see relevancy and suitability. [04:49] 3) Establish channels and formats for dissemination of the documentation [04:49] 3) See how we might carry on them, to produce ubuntu compatible education. [04:49] oh :) [04:50] sivang: sorry for overlapping [04:50] sorry for taking #3 [04:50] :-) [04:50] asw: ubuntu for scientists... noted! [04:50] I have some very basic questions about licensing too. (And yes I have strong flame-war generating opinions...) [04:51] I have a silly IRC question. was the message "asw: ubuntuy for scientists... notes!" private? sorry for being an idiot. [04:51] Kamion: review, yes, but starting from existing issues [04:51] asw: no. [04:51] enrico: so let me make sure I am understanding [04:52] see what existing issues there are right now. Start with docs that will address those issues [04:52] asw: no, I sent it into the channel: I just wanted to acknowledge your interest [04:52] correct? === hubs [~hubs@N507P012.adsl.highway.telekom.at] has joined #ubuntu-meeting [04:52] enrico, kamion: thanks but why is it highlighted on my xchat screen. [04:53] asw: cause it has your name on it [04:53] hornbeck: or, given the issues, see what documentation is around and see if we need to produce something new, point to something existing, produce a short doc that points to something existing "for knowing more" [04:53] enrico: Ok I understand === enrico feel like he should present his plan to the group, for wider discussion === enrico feels like the text he's made won't fit into a single line in IRC [04:54] Do we have a mailing list to post things for review and have discussions? [04:54] not yet [04:54] is it possible for somebody like me to work on a section of docs like "ubuntu for scientists" while keeping up with/staying out of the way of whatever the rest of you are doing? [04:54] I don't mind using existing mailing lists for production, but it may be useful to have one for coordination [04:54] enrico : why don't we publish on the wiki somewhere also? [04:54] enrico: use ubuntu-devel@ and put [doc] in the subject line, please [04:55] enrico: please say something to mdz about our own list [04:55] Kamion: if we fit there, ok [04:55] mdz already expressed an opinion on this [04:55] which was "use ubuntu-devel@ and put [doc] in the subject line, please" :-) [04:55] actually I could see why coordinating with devel is a really good idea. [04:55] maybe it's not so bad if we are exposed to their traffic? [04:55] Kamion: ok [04:56] the problem with a separate list in the beginning is that it means the doc team is likely to get disconnected too much from development activity === enrico generally agrees with mako's idea that every time one creates a new mailing list, God kills a kitten [04:56] Kamion: I see the point in that [04:57] enrico: can you put your idea on a wiki page or maybe on today's meeting page? [04:57] Kamion: won't people bother if we'll start dumping on -devel our delirious world domination plans? === sivang feel ths same [04:57] asw: it'll take a while for me to do the wiki formatting, though [04:57] enrico: they said if we start over crowding than we can have our own [04:58] enrico: well, you shouldn't be getting too delirious anyway :) [04:58] Kamion: (this is just to get a "don't worry" from you, so that we can dodge compalints) [04:58] Kamion: Damn! No "don't worry"! :) [04:58] enrico: put it all in a mail, and I can put on the wiki today [04:58] enrico: we'd like to know what you're doing; in general you should be keeping discussion fairly tightly on-topic [04:59] Kamion : does this also applies to before release tight times? :) [04:59] Kamion: you guys just want to watch over us huh? [04:59] After the meeting I'll work on publishing my plan (with hornbeck maybe) and on summarizing recent discussion with sivang [04:59] hornbeck: well, new teams starting up often need some supervision in most organisations === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting [05:00] sivang: yes, we can cope with a bit more mail; just don't wibble :) [05:00] Kamion: right, you guys like to watch [05:00] hornbeck: we'll split it out if it becomes an issue === sivang suggest the "Ubuntu Documentation Team" reality TV show. === hornbeck would get naked in the pool all the time [05:01] Casually, we have pictures of ubuntu people naked in the pool already :) [05:01] haha [05:01] hahahaha [05:01] However, back to the plans, we have: [05:01] yes [05:01] 1) Some draft long-term plans [05:02] 2) Some titles for ubuntu-specific guides (coming from the UDP wiki page mostly, I image from sivang and hornbeck) [05:03] enrico: I think we should shoot for this http://www.gentoo.org/doc/en/index.xml === enrico has a look, feels we can do better [05:03] enrico: they have docs for just about all issues I ever ran into for gentoo [05:04] Then, we'll have docs to make you run in even more issues!! ;) === sivang nods [05:04] Well, the idea is that you should never run into an issue with Ubuntu, and we focus on showing how to do creative things [05:05] I wouldn't mind finally taking Linux out of the troubleshooting and customization and finally into the "how to remove the red eyes to your digital camera pictures" [05:05] (enrico raises a good point; please don't document workarounds for problems that you should be telling us to fix instead) [05:05] that would be nice [05:05] making the illusion we have squashed all other issues, so you wind up asking, what can I do with Ubuntu today? :) === pitti_ [~martin@195.227.105.180] has joined #ubuntu-meeting [05:06] enrico, Kamion: good ideas but we are not there yet [05:06] So what about licensing (GFDL?) and style guidelines? Somebody mentioned docbook? [05:06] asw: good question [05:06] Yes, I have :) [05:06] docbook is nice [05:07] Kamion: are there policies about licenses for documentation? [05:07] GFDL would be great. [05:07] Kamion: GFDL but without invariant sessions? [05:07] s/session/section/ [05:07] I've recently inherited the "REC.GAMES.COREWAR" faq and I will need to use something for that. It's plaintext/html at the moment... [05:07] Kamion: GPL altogehter? === enrico wouldn't mind creating GPL documentation, which would be supercool [05:08] That is, we should distribute the source form, including, for example, spreadsheets we used to generate the graphics and so on) [05:08] Frankly I have watched the folks at MIT debate over invariant sections and if ubuntu is about freedom then political speech aka invariant sections should be permitted. It's just complicated and maybe out of scope for this meeting... [05:08] I think Debian has made the wrong decision with respect to invariant sections. [05:08] I'd honestly ask upstairs (sabdfl or something like that) for that [05:08] It's one of the reasons I'm interested in ubuntu. [05:09] we don't have a hard objection to the GFDL, but since we would like to send improvements back to Debian I'd strongly recommend that you avoid the GFDL and invariant sections in documentation you write. === sivang backs enrico with GPL altogehter? [05:09] it'll just create unnecessary barriers === sivang backs enrico with GPL altogehter [05:09] kamion: this is practical... [05:09] I think GPL would be nice [05:09] (I'm not authoritative on this, BTW, just an opinion) [05:09] or there's even the artistic license, if we really want to get nasty :) [05:10] Whatever the license (we can delegate decisions on that, Italian style ;) , let's talk about formats [05:10] should someone hop to ubuntu-devel and ask [05:10] the artistic licence is ... not ideal. clarified artistic isn't too bad. [05:10] From one side, we are probably creating some books, so docbook qualifies [05:10] I think docbook is preferable, and we should use debian DTD. [05:10] enrico: sabdfl? [05:10] Kamion : agreed [05:10] From the other side, we are probably writing items into Plone [05:11] asw: sabdfl is Mark Shuttleworth's IRC nick [05:11] i think most debian developers would recommend avoiding the gfdl as it stands === hubs [~hubs@N507P012.adsl.highway.telekom.at] has joined #ubuntu-meeting [05:11] It would be interesting making something to drag Plone items into Docbook, should we aggregate things from Plone into a book [05:11] And the other way round to post the aggregation into Plone [05:11] I'm not a Plone expert yet, but I imagine this is doable [05:11] yes, through a plugin or some hacks [05:11] I have not worked with plone yet [05:12] I also have (as you could imagine) some funky ideas about indexing, coming from my debtags experience, but I'll save these for later :) [05:13] I feel like we should start flooding ubuntu-devel with the material we have and start discussing, however, I wanted to present three "philosophy" items that came up in a discussion with sivang [05:14] using debiandoc would give us the minimalistic looks debian guides have, which I guess would ease debian's use of our works [05:14] They could be a "working method" we can share [05:14] kamion: I emailed mark at hbd com but very generically. Irc would probably have been nice to chat about this... Is the developer meeting on the 19th a good place for that? It sounds like GFDL (without invariant sections for 99% of documents is the best way to go.) [05:14] sivang: you might like to look at the way the installation manual's done; the build system is still hacky but it's basically docbook [05:14] Ok, I'll post the three points a bit later, let's stay on docbook for a moment [05:14] At least for documents I write. [05:15] Kamion : I'll have a look. [05:15] asw: dunno about the 19th, that might be release-oriented, but feel free to suggest it [05:15] enrico: one reason I' [05:15] asw: I really recommend against even GFDL without invariant sections if you want to have a hope of contributing anything back to Debian. [05:15] About docbook, one good thing is that you can delegate the look to later [05:15] asw: the GFDL has a number of problems besides invariant sections. [05:16] Altough I'd like to see OpenOffice.org integration with docbook getting a bit more mature === mako waves [05:16] (but that's because I'm a vim user, and I don't have psgml-mode in vim) === enrico waves at mako [05:16] was sorting out an another urgent work problem [05:16] who came in just in time to see my vim frustration wrt docbook and tease me ;) [05:17] enrico: one reason I've used plain-text is that locking yourself into one format or another seems to always cause problems for me. (I find that much documentation doesn't get written because it would be too much of a pain to convert it into one format over another.) maybe we should not have a "fixed" standard style? [05:17] enrico : test emacs, it's wonderful in it [05:17] sivang: I know [05:17] If the upstrea documentation uses tex-info use that. If it uses latex use that... [05:17] I loves me some nano [05:18] asw: I don't like the idea of using multiple formats [05:18] just me though [05:18] asw : using doc book enables you to ouput different formats. [05:18] hornbeck: contributing changes back upstream makes dealing with multiple formats inevitable [05:18] asw: of course if you hack on somethign upstream you respect that; however, if we produce something new, docbook can be a good default choice. HOWEVER, [05:18] hornbeck: same way the distribution development team have to deal with all sorts of stuff [05:19] if someone is confident in writing with something else, I'd like to respect that, or we're putting barriers to contrbution. [05:19] Kamion: understood [05:19] So, if someone wants to write something, but knows latex better than docbook, it's not bad to say "go on" [05:19] ok === sivang would like to see we making sure debian could use our work, however stricting this may be. [05:20] If (s)he's interested in learning docbook later, we can offer to convert it so that (s)he can see how it works [05:20] there's convertors from latex to docbook and vice versa also :) === enrico loves OpenOffice.org -> DocBook [05:20] i would like to see the output from something going latex -> docbook, or either way, before i trusted it [05:21] Also because OOo already saves in something that's soo docbook-ish [05:21] But this is a pet technical quirk of mine [05:21] sivang: mako's a docbook freak [05:21] sivang: mako writes DSSSSSL: don't trust him ;) [05:21] actually, i've been writing almost entirely in restrcutred text recently === plovs is back [05:21] mako : my man, I didn't realize ... :)) [05:21] I prefer docbook also [05:22] i find RST much cleaner, but DB is the thing that looks most like a community standard [05:22] Cool, we have some non-normative agreement here, then [05:22] Honestly it seems more important to agree on what "final" formats we want (i.e. PDF, html) and let people use whatever they want. Maybe somebody already has some nice writing/style guidelines we could adopt so that the -final- products were consistent. [05:23] sorry, to drop in, would it be possible to write documentation in the wiki and then parse it to docbook? [05:23] plovs : see the backlog [05:24] me reading the backlog [05:24] plovs: that's nice... [05:24] plovs: I mean I think it's nice to draft in the wiki first. [05:25] asw: guidelines... tricky issue [05:25] enrico : we can stick to "standard" approches already evident on open source projects. [05:25] asw: I think guidelines are good when they help you in making choices that you don't know much about [05:25] asw: that's fine but being able to have things in version control and being able to collaborate with people without having to learn a new a format each time is worth something [05:25] enrico: my point is that we should agree on what we consider "good enough" levels of documentation and then levels that are "ideal". [05:25] But they risk restricting creativity and participation in one takes them too strictly [05:25] asw: even if it means that everyone has to learn a new format once :) [05:26] mako: Version control is very good for bigger projects, yes [05:26] would it be possible to export the wiki directly into docbook in a "nice" way? [05:26] And I've recently discovered *meld*, which is SO COOL! [05:26] asw: i looked today there is no moinmoin2docbook converter [05:27] asw: it would be kind of limited, since in wikis you do lots of formatting "by hand" anyway [05:27] While in docbook you don't do formatting at all [05:27] we could have the docbooks compiled to XHTML, and include this server side or something by plone [05:28] enrico: put with a good python-parser it is possible, moinmoin-raw is *very* simple [05:28] I suggest we leave this discussion to when we see what we're about to produce/producing [05:28] enrico : very well. [05:28] people working on GNU Arch found that the wiki helped a great deal with documentation so I think if there was a way to make the wiki more compatible with docbook that would be a very good thing [tm] [05:28] That is, if it's a book, we may want to print it. If it's a short thing, we post it in Plone, or in a mailing list or newsletter [05:28] (and so on) === enrico conceives a wiki in which people write docbook === sivang had envisioned the same :) === enrico thinks that would be quite a good idea, considering the metadata you can put in docbook [05:29] maybe we should first write documentation... [05:30] However, that would be a little bit less wiki (in the sense of fast, unless you hook psgml-mode into mozilla) === ph_ [~ph@pD9E6B6F0.dip.t-dialin.net] has left #ubuntu-meeting ["Verlassend"] [05:30] But we're digressing [05:30] let's concentrate on close milestones [05:30] personally I think that documentation is a major unsolved problem is Free Software projects. So I hope it's not too much of a digression to talk about wiki->docbook... [05:30] I think I am going to have to reread this whole thing [05:31] conept wise first, and see how we carry on the make something for HOary [05:31] I'd like to present the three philosophy mantras, and then starting posting summaries on the maling list === enrico rolls drums === sivang is anxiuos. [05:31] Mantra #1: "Do things that are technically simple, and socially complex" [05:32] (or else, when even socially simple things happen, you'll be busy working at technically complex things) [05:32] (and we already have lots of good developers working at the technically complex anyway) [05:33] Mantra #2: "Cool think! Let's put it into the TODO-list for the next-to-the-upcoming release!" [05:33] (or else, the upcoming release we're working on right now will never happen) [05:34] Mantra #3: "First, get to do it. Then, document how to do it. Then, automate it." [05:34] (changing the order produces bad result. Of course, one can reiterate the process multiple times) === sivang thinks that "automate it" is going to be an exciting part. === enrico rolls drums === enrico suddendly stops and meditates === enrico awakes from meditation [05:35] sivang: I'd translate "automate" with "send a wishlist bug to the developers" [05:35] And that's how we make feedback from the community to the developers [05:35] ok [05:36] Then, we're of course free to take away the "documentation" hat and wear the "developers" hat [05:36] enrico: so part of our job also is to let the developers know when something is to complex [05:36] hornbeck : and is a very important one, also. [05:36] hornbeck: yes. Absolutely. [05:37] so not to get all busy by docs that never need be written, [05:37] enrico: I guess I was blind to that part but now it makes alot of since [05:37] hornbeck: I think that when documenting you're in an extremely critical watching point to see how things are [05:37] actually there a point here :) . [05:38] I must say that I am somewhat enlightened [05:38] so, what docs sgould be written is there a list somewhere of stuff that needs to be done/ === enrico cheers at hornbeck's enlightenment [05:38] The point is , if someone want to be fiddeling with inner workings and low lever stuff, that's cool. We won't concentrate on it at first. [05:38] plovs: I have just been watching the mailing list [05:38] plovs: One thing we can do is creating a 'documentation' metapackage on bugzilla [05:39] or make the devs improve it altogether. [05:39] plovs: then using that as a todo-list, and to post ideas [05:39] this would be our first doc bug ! :) === sivang is however uncertain whe this bug would be close :) [05:39] That could be used to collect requests, and reassign them to other documents we're writing or maintaining [05:40] sivang: when we feel like, of course! [05:40] in the wiki is a page about kernel compiling etc, i could write that [05:40] plovs: http://wiki.ubuntulinux.org/KernelHowto [05:41] plovs its all your [05:41] enrico : haha, no I meant - this would serve as on ongoing list of things to do, and their status, so It might as well never close as work would always need doing :) [05:41] ok, in the documentation should we concentrate on command-line use, apt-get or explain everything through synaptic [05:41] Bugs that are never closed have a nice usefulness in collecting discussion [05:42] We could collect enough discussion on a never closed topic that it becomes a book on his own [05:42] enrico : haha, no I meant - this would serve as on ongoing list of things to do, and their status, so It might as well never close as work would always need doing :) [05:42] (and then we publish the book and close the bug ;) [05:42] yes! [05:42] heh [05:43] plovs I have been trying to do alittle of both [05:43] so a book deal is what we are really looking for out of this :) [05:43] mako: how do we get such a virtual package for bugzilla? [05:43] enrico: ask justdave [05:43] hornbeck: not afaik [05:44] enrico: it shouldn't be a problem [05:44] I'll talk to justave [05:44] hornbeck: I was just talking abstract [05:44] until then we could just use a page in the wiki with a list of topics we want covered [05:44] enrico: it was a joke [05:44] Although maybe publishing books from free content could be nice (that is, you get the book, and even the source online, and you can buy a nice color printed copy and generate some revenue) [05:45] But I'll keep that for discussion in the dissemination phase [05:45] or even, when material is there, anyone can make a book out of it [05:45] the free-bsd is nice, if i would use it, i would buy such a boo [05:45] hornbeck: ops! Sorry for keeping it so long on a joke :( [05:45] :) [05:46] So goals for right now [05:46] I need to go to work soon and need to know where we are [05:46] can we summerize? [05:47] I could say a few things. [05:47] asw: go on [05:47] someone should write up a summary and post it to -devel [05:47] I will: [05:47] i will make sure it gets into traffic [05:47] mako: you'll see our posts on -devel, you'll see them... === enrico laughs evilly [05:47] talk "upstairs" about doc licensing. (in particular with respect to GFDL...) === sivang sivang joings him..moouahhha [05:48] I have offered to start a "ubuntu for scientists" section. [05:48] asw: start it up [05:48] I have suggested a wiki->docbook gateway (based on people's pref for doc book.) [05:48] ubuntu-devel used a a coordination mailing list, with [doc] in the subject [05:48] I'm sorry these are all possibly far away goals... [05:48] that's all. [05:48] (for me) [05:49] do we have some short-term goal, for say three months? [05:49] in regards to licensing, we don't need to worry so much [05:49] we have 3 mantras that enlightened hornbeck [05:49]