=== 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:45aswHi! Is there a documentation meeting today? (In a few minutes I think...)
=== mvo_ [~egon@suprimo-230.ping.de] has joined #ubuntu-meeting
03:55hornbeckyes you are in the right place asw
03:56hornbeckI am helping the wife for a few more minutes than I will be in here
03:57aswCool...
04:02aswIs there an agenda or a web-page for this meeting?
04:02aswI only saw the notice is ubuntu-users/devel...
=== plovs [~plovs@62.84.21.44] has joined #ubuntu-meeting
04:03hornbeckno there is no agenda
04:04hornbeckwe just wanted to get some people together who has some ideas on the docs and which direction we should go with them
04:04hornbeckbut we will give people a few more minutes to get in here
04:05plovshi
04:06aswok. will transcripts be posted?
04:07asw(I'm pretty bad at IRC so I'm happy if they are not...)
04:07plovstranscripts are good for people who couldn't make it
04:08hornbeckhttp://wiki.ubuntulinux.org/DocumentationAgenda
04:08hornbeckthere you go
04:08hornbeckI do believe that there will be transcripts
04:08hornbeckmako: you really here?
04:08aswtranscripts are good I just hate all the spelling/grammar mistakes that are saved for posterity... =^)
04:09hornbeckwell noone is perfect
04:09hornbeckthat is what spell check is for
04:09aswI don't know how to use spell-check with irc. (I use xchat)
04:09hornbeckI meant outside irc
04:09hornbeckI use xchat also
04:10hornbeckthere 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:11hornbeckwell I guess others will show up
04:12hornbecka couple more about to be here
04:14aswI have some particular things I'd like to work on but since I'm new I don't know what the etiquette is...
04:14hornbeckhold one sec
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
04:15plovswill docbook be used for documentation?
04:15hornbeckhold one sec
04:15hornbeckother main people are on their way
=== sivang [~pooh@80.179.66.136.forward.012.net.il] has joined #ubuntu-meeting
04:15hornbeckdon't want to get in discussions and have them lost
04:15aswplovs: are you Poslavsky on the wiki doc-team page?
=== plovs holding his breath
04:16plovsyes
=== enrico [~enrico@enrico.developer.debian] has joined #ubuntu-meeting
04:16hornbeckok, there is about the last one I was waiting for
04:18enricoHello, and good afternoon.  Sorry for the delay, I understood it was 16.00 UTC instead of CET
04:18sivangme also :)
=== ph_ [~ph@pD9E6B6F0.dip.t-dialin.net] has joined #ubuntu-meeting
04:19hornbeckThere will be a documentation meeting this friday at 1400UTC in
04:19hornbeck#ubuntu-meeting on the freenode server
04:19hornbeck:)
04:19sivangI'd like everybody to introduce himself a bit,
04:19enricoSince we're all here, we can start.  How about a round of introductions?
04:20sivangShall I start?
04:20sivang:)
04:20hornbeckI am John Hornbeck, I worked with the Gnome doc team for awhile and have started alot of work with Ubuntu so far
04:20sivanghornbeck?
04:20hornbeckI live in Oklahoma
04:20hornbeckis that good
04:21hornbecknext?
04:21sivangI'm Sivan Green, I'm from Israel. I've started the /UDP page on the wiki, with some thoughts about
04:21sivangthe directions of ubuntu's documentation.
04:22enricoI'm Enrico Zini, Italy.  I've been working on designing a community-based approach to produce documentation
04:22sivangI'm a long time Linux user, programmer and have had experience with documentation on some corporate company.
04:22KamionI'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:22sivangKamion : nice to see you here :)
04:22aswI'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:23plovsI am AlexanderPoslavsky, I'm from the Netherlands,I work as windows admin, but prefer linux :)
04:23hornbeckhehe, I am a windows admin also
04:23sivanganybody else?
04:24sivangmako ?
04:24hornbeckI guess everyone else is just watching
04:25hornbeckso six of us than
04:26enricoEnrico, Sivang, Hornbeck, Asw, Plovs, Kamion
04:26Kamion(don't consider me part of the doc team please, as I said I'm just lurking really)
04:26hornbeckok
04:26enricoDoc team: Enrico, Sivang, Hornbeck, Asw, Plovs
04:26enricoGoal: Total world domination
04:26plovsit's a start...
04:27enricoI guess we're here to discuss how to get to that
04:27hornbeckyes
04:27sivangyes.
04:27hornbeckwould you like us to discuss what we have done so far?
04:27aswyes please
04:27enricohornbeck: sure!
04:27hornbeckso everyone can be caught up to speed
04:27hornbeckok, I will start
04:28sivanggood idea, let's have an overview for what already exists.
04:28hornbeckI have mainly worked on the wiki trying to get alot of it up to speed
04:28hornbeckI 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:29hornbeckI try to stay active on the mailing list so i get more ideas of faqs and other information that needs docs
04:29hornbeckthats it for me
04:30enricoasw?
04:30aswI'm completely new.
04:30hornbecksivang?
04:31aswCould somebody mention JohnLevin, BenEdwards or KevinWixted (they are on the DocumentationTeam page)
04:31sivangyes,
04:31sivangI'd recommend everybody to take a look at the /DocumentationTeam page, see the people who are listed there to get an idea
04:32asw(Also robertbrimhall)
04:32sivangplease see also /DocumentationArea more wiki work by interested people
04:33sivanganybody correct me if I slipped away any other piece of index web, for what others have done by now.
04:34hornbecklooks right to me
04:34enricoAs 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:36hornbeckok, so we know who we are now
04:36hornbeckI have a few questions
04:37hornbeckenrico: Where would you like us to be as far as docs, for Hoary
04:37hornbeckthat is a large question I know
04:38enricoThat is a large question
04:38hornbeckok I will make it smaller
04:38sivangLet'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:39hornbecksivang: warty is about out the door
04:39aswI'm reading http://wiki.ubuntulinux.org/HoaryHedgehog_2fReleaseSchedule
04:39hornbeckwe can do keep up docs for it, but the goal as I see it right now is Hoary
04:40hornbeckenrico: a better start question would be, what areas are we looking at documenting
04:40enricosivang: yes.  It's reasonable to start some working together first, then make release-oriented plans
04:41aswSo 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:41enricoSo, ideally, there should be no documentation at all.  Programs should just work, and do what users want.
04:41hornbeckasw: we are still working on docs for warty
04:41Kamionyou guys don't have to worry about the seed freeze very much
04:41hornbeckenrico: yes
04:42enricoDocumentation comes in when programs are not that clear, or when the users don't know what they want
04:42enricoThis highlight two fields of working :)
04:42Kamionthe problem you'll have is that not all the documentation you'll need to write will be clear *until* feature freeze
04:43Kamionbut by shortly after feature freeze you'll probably want to have the guts of most of the docs and then start polishing
04:43hornbeckso alot of late night before a release
04:43enricoKamion: 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:43enricoAnd, in the traditional computer-science style, what we need to do is change the nature of the problem ;)
04:44hornbeckenrico: that comes back to, what all are we going to document
04:44hornbeckare we going to have our own docs for everything?
04:44sivangno.
04:44enricohornbeck: docs for everything?  No, please no
04:44enricoThat would be bad, for various things
04:44hornbeckor are we going to use docs from other places and feel in the spots
04:44enrico - disrespect for all the good work that already exists
04:44enrico - lots of work to do
04:44hornbeckenrico: I was just giving a example
04:45hornbecknot asking to do so
04:45enrico - it would disconnect us from the rest fo the community
04:45pittiDoc should handled similar to packages: keep ubuntu-specific changes, but base on upstream docs
04:45enricohornbeck: ah, ok, sorry :)
04:45sivangpitti : exactly
04:45pittiAFAICS you can even use the same tools (diff, etc.) for it
04:45hornbeckyeah
04:45enricoSo, 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:45sivangyes, and that would enable us to feed debian back, as our ROCK
04:46aswI 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:46enricoWorking based on what the issues are will also allow us to produce documentation which addresses what users are actually trying to do
04:47sivangIdeally we should probably follow this to start up a bit:
04:48sivang1) Identify the goal our users might want to accomplish.
04:48enricoI 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:48enricoOn these two identities, both are important, and one kills the other
04:48Kamionyou 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:48enricoThis is a nice Hegelian dialectic
04:49enricoResolving dialectics lead to Genius, and of course Total World Domination
04:49sivang2) Investigate current works to see relevancy and suitability.
04:49enrico3) Establish channels and formats for dissemination of the documentation
04:49sivang3) See how we might carry on them, to produce ubuntu compatible education.
04:49sivangoh :)
04:50enricosivang: sorry for overlapping
04:50sivangsorry for taking #3
04:50sivang:-)
04:50enricoasw: ubuntu for scientists... noted!
04:50aswI have some very basic questions about licensing too. (And yes I have strong flame-war generating opinions...)
04:51aswI have a silly IRC question. was the message "asw: ubuntuy for scientists... notes!" private? sorry for being an idiot.
04:51enricoKamion: review, yes, but starting from existing issues
04:51Kamionasw: no.
04:51hornbeckenrico: so let me make sure I am understanding
04:52hornbecksee what existing issues there are right now.  Start with docs that will address those issues
04:52enricoasw: no, I sent it into the channel: I just wanted to acknowledge your interest
04:52hornbeckcorrect?
=== hubs [~hubs@N507P012.adsl.highway.telekom.at] has joined #ubuntu-meeting
04:52aswenrico, kamion: thanks but why is it highlighted on my xchat screen.  
04:53hornbeckasw: cause it has your name on it
04:53enricohornbeck: 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:53hornbeckenrico: 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:54enricoDo we have a mailing list to post things for review and have discussions?
04:54hornbecknot yet
04:54aswis 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:54enricoI don't mind using existing mailing lists for production, but it may be useful to have one for coordination
04:54sivangenrico : why don't we publish on the wiki somewhere also?
04:54Kamionenrico: use ubuntu-devel@ and put [doc]  in the subject line, please
04:55hornbeckenrico: please say something to mdz about our own list
04:55enricoKamion: if we fit there, ok
04:55Kamionmdz already expressed an opinion on this
04:55Kamionwhich was "use ubuntu-devel@ and put [doc]  in the subject line, please" :-)
04:55aswactually I could see why coordinating with devel is a really good idea.
04:55aswmaybe it's not so bad if we are exposed to their traffic?
04:55enricoKamion: ok
04:56Kamionthe 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:56hornbeckKamion: I see the point in that
04:57aswenrico: can you put your idea on a wiki page or maybe on today's meeting page?
04:57enricoKamion: won't people bother if we'll start dumping on -devel our delirious world domination plans?
=== sivang feel ths same
04:57enricoasw: it'll take a while for me to do the wiki formatting, though
04:57hornbeckenrico: they said if we start over crowding than we can have our own
04:58Kamionenrico: well, you shouldn't be getting too delirious anyway :)
04:58enricoKamion: (this is just to get a "don't worry" from you, so that we can dodge compalints)
04:58enricoKamion: Damn!  No "don't worry"! :)
04:58hornbeckenrico: put it all in a mail, and I can put on the wiki today
04:58Kamionenrico: we'd like to know what you're doing; in general you should be keeping discussion fairly tightly on-topic
04:59sivangKamion : does this also applies to before release tight times? :)
04:59hornbeckKamion: you guys just want to watch over us huh?
04:59enricoAfter the meeting I'll work on publishing my plan (with hornbeck maybe) and on summarizing recent discussion with sivang
04:59Kamionhornbeck: well, new teams starting up often need some supervision in most organisations
=== pitti [~martin@195.227.105.180] has joined #ubuntu-meeting
05:00Kamionsivang: yes, we can cope with a bit more mail; just don't wibble :)
05:00hornbeckKamion: right, you guys like to watch
05:00Kamionhornbeck: 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:01enricoCasually, we have pictures of ubuntu people naked in the pool already :)
05:01hornbeckhaha
05:01sivanghahahaha
05:01enricoHowever, back to the plans, we have:
05:01hornbeckyes
05:01enrico 1) Some draft long-term plans
05:02enrico 2) Some titles for ubuntu-specific guides (coming from the UDP wiki page mostly, I image from sivang and hornbeck)
05:03hornbeckenrico: 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:03hornbeckenrico: they have docs for just about all issues I ever ran into for gentoo
05:04enricoThen, we'll have docs to make you run in even more issues!! ;)
=== sivang nods
05:04enricoWell, the idea is that you should never run into an issue with Ubuntu, and we focus on showing how to do creative things
05:05enricoI 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:05Kamion(enrico raises a good point; please don't document workarounds for problems that you should be telling us to fix instead)
05:05hornbeckthat would be nice
05:05sivangmaking 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:06hornbeckenrico, Kamion: good ideas but we are not there yet
05:06aswSo what about licensing (GFDL?) and style guidelines?  Somebody mentioned docbook?
05:06enricoasw: good question
05:06sivangYes, I have :)
05:06hornbeckdocbook is nice
05:07enricoKamion: are there policies about licenses for documentation?
05:07sivangGFDL would be great.
05:07enricoKamion: GFDL but without invariant sessions?
05:07enricos/session/section/
05:07aswI'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:07enricoKamion: GPL altogehter?
=== enrico wouldn't mind creating GPL documentation, which would be supercool
05:08enricoThat is, we should distribute the source form, including, for example, spreadsheets we used to generate the graphics and so on)
05:08aswFrankly 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:08aswI think Debian has made the wrong decision with respect to invariant sections.
05:08enricoI'd honestly ask upstairs (sabdfl or something like that) for that
05:08aswIt's one of the reasons I'm interested in ubuntu.
05:09Kamionwe 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:09Kamionit'll just create unnecessary barriers
=== sivang backs enrico with GPL altogehter
05:09aswkamion: this is practical...
05:09hornbeckI think GPL would be nice
05:09Kamion(I'm not authoritative on this, BTW, just an opinion)
05:09sivangor there's even the artistic license, if we really want to get nasty :)
05:10enricoWhatever the license (we can delegate decisions on that, Italian style ;) , let's talk about formats
05:10hornbeckshould someone hop to ubuntu-devel and ask
05:10Kamionthe artistic licence is ... not ideal. clarified artistic isn't too bad.
05:10enricoFrom one side, we are probably creating some books, so docbook qualifies
05:10sivangI think docbook is preferable, and we should use debian DTD.
05:10aswenrico: sabdfl?
05:10sivangKamion : agreed
05:10enricoFrom the other side, we are probably writing items into Plone
05:11Kamionasw: sabdfl is Mark Shuttleworth's IRC nick
05:11thomi think most debian developers would recommend avoiding the gfdl as it stands
=== hubs [~hubs@N507P012.adsl.highway.telekom.at] has joined #ubuntu-meeting
05:11enricoIt would be interesting making something to drag Plone items into Docbook, should we aggregate things from Plone into a book
05:11enricoAnd the other way round to post the aggregation into Plone
05:11enricoI'm not a Plone expert yet, but I imagine this is doable
05:11sivangyes, through a plugin or some hacks
05:11hornbeckI have not worked with plone yet
05:12enricoI also have (as you could imagine) some funky ideas about indexing, coming from my debtags experience, but I'll save these for later :)
05:13enricoI 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:14sivangusing debiandoc would give us the minimalistic looks debian guides have, which I guess would ease debian's use of our works
05:14enricoThey could be a "working method" we can share
05:14aswkamion: 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:14Kamionsivang: 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:14enricoOk, I'll post the three points a bit later, let's stay on docbook for a moment
05:14aswAt least for documents I write.
05:15sivangKamion : I'll have a look.
05:15Kamionasw: dunno about the 19th, that might be release-oriented, but feel free to suggest it
05:15aswenrico: one reason I'
05:15Kamionasw: I really recommend against even GFDL without invariant sections if you want to have a hope of contributing anything back to Debian.
05:15enricoAbout docbook, one good thing is that you can delegate the look to later
05:15Kamionasw: the GFDL has a number of problems besides invariant sections.
05:16enricoAltough I'd like to see OpenOffice.org integration with docbook getting a bit more mature
=== mako waves
05:16enrico(but that's because I'm a vim user, and I don't have psgml-mode in vim)
=== enrico waves at mako
05:16makowas sorting out an another urgent work problem
05:16enricowho came in just in time to see my vim frustration wrt docbook and tease me ;)
05:17aswenrico: 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:17sivangenrico : test emacs, it's wonderful in it
05:17enricosivang: I know
05:17aswIf the upstrea documentation uses tex-info use that. If it uses latex use that...
05:17hornbeckI loves me some nano
05:18hornbeckasw: I don't like the idea of using multiple formats
05:18hornbeckjust me though
05:18sivangasw : using doc book enables you to ouput different formats.
05:18Kamionhornbeck: contributing changes back upstream makes dealing with multiple formats inevitable
05:18enricoasw: 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:18Kamionhornbeck: same way the distribution development team have to deal with all sorts of stuff
05:19enricoif someone is confident in writing with something else, I'd like to respect that, or we're putting barriers to contrbution.
05:19hornbeckKamion: understood
05:19enricoSo, if someone wants to write something, but knows latex better than docbook, it's not bad to say "go on"
05:19hornbeckok
=== sivang would like to see we making sure debian could use our work, however stricting this may be.
05:20enricoIf (s)he's interested in learning docbook later, we can offer to convert it so that (s)he can see how it works
05:20sivangthere's convertors from latex to docbook and vice versa also :)
=== enrico loves OpenOffice.org -> DocBook
05:20makoi would like to see the output from something going latex -> docbook, or either way, before i trusted it
05:21enricoAlso because OOo already saves in something that's soo docbook-ish
05:21enricoBut this is a pet technical quirk of mine
05:21enricosivang: mako's a docbook freak
05:21enricosivang: mako writes DSSSSSL: don't trust him ;)
05:21makoactually, i've been writing almost entirely in restrcutred text recently
=== plovs is back
05:21sivangmako : my man, I didn't realize ... :))
05:21hornbeckI prefer docbook also
05:22makoi find RST much cleaner, but DB is the thing that looks most like a community standard
05:22enricoCool, we have some non-normative agreement here, then
05:22aswHonestly 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:23plovssorry, to drop in, would it be possible to write documentation in the wiki and then parse it to docbook?
05:23sivangplovs : see the backlog
05:24plovsme reading the backlog
05:24aswplovs: that's nice...
05:24aswplovs: I mean I think it's nice to draft in the wiki first.
05:25enricoasw: guidelines... tricky issue
05:25sivangenrico : we can stick to "standard" approches already evident on open source projects.
05:25enricoasw: I think guidelines are good when they help you in making choices that you don't know much about
05:25makoasw: 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:25aswenrico: my point is that we should agree on what we consider "good enough" levels of documentation and then levels that are "ideal".
05:25enricoBut they risk restricting creativity and participation in one takes them too strictly
05:25makoasw: even if it means that everyone has to learn a new format once :)
05:26enricomako: Version control is very good for bigger projects, yes
05:26aswwould it be possible to export the wiki directly into docbook in a "nice" way?
05:26enricoAnd I've recently discovered *meld*, which is SO COOL!
05:26plovsasw: i looked today there is no moinmoin2docbook converter
05:27enricoasw: it would be kind of limited, since in wikis you do lots of formatting "by hand" anyway
05:27enricoWhile in docbook you don't do formatting at all
05:27sivangwe could have the docbooks compiled to XHTML, and include this server side or something by plone
05:28plovsenrico: put with a good python-parser it is possible, moinmoin-raw is *very* simple
05:28enricoI suggest we leave this discussion to when we see what we're about to produce/producing
05:28sivangenrico : very well.
05:28aswpeople 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:28enricoThat 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:28enrico(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:29plovsmaybe we should first write documentation...
05:30enricoHowever, 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:30enricoBut we're digressing
05:30sivanglet's concentrate on close milestones
05:30aswpersonally 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:30hornbeckI think I am going to have to reread this whole thing
05:31sivangconept wise first, and see how we carry on the make something for HOary
05:31enricoI'd like to present the three philosophy mantras, and then starting posting summaries on the maling list
=== enrico rolls drums
=== sivang is anxiuos.
05:31enricoMantra #1: "Do things that are technically simple, and socially complex"
05:32enrico(or else, when even socially simple things happen, you'll be busy working at technically complex things)
05:32enrico(and we already have lots of good developers working at the technically complex anyway)
05:33enricoMantra #2: "Cool think!  Let's put it into the TODO-list for the next-to-the-upcoming release!"
05:33enrico(or else, the upcoming release we're working on right now will never happen)
05:34enricoMantra #3: "First, get to do it.  Then, document how to do it.  Then, automate it."
05:34enrico(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:35enricosivang: I'd translate "automate" with "send a wishlist bug to the developers"
05:35enricoAnd that's how we make feedback from the community to the developers
05:35sivangok
05:36enricoThen, we're of course free to take away the "documentation" hat and wear the "developers" hat
05:36hornbeckenrico: so part of our job also is to let the developers know when something is to complex
05:36sivanghornbeck : and is a very important one, also.
05:36enricohornbeck: yes. Absolutely.
05:37sivangso not to get all busy by docs that never need be written,
05:37hornbeckenrico: I guess I was blind to that part but now it makes alot of since
05:37enricohornbeck: I think that when documenting you're in an extremely critical watching point to see how things are
05:37sivangactually there a point here :) .
05:38hornbeckI must say that I am somewhat enlightened
05:38plovsso, what docs sgould be written is there a list somewhere of stuff that needs to be done/
=== enrico cheers at hornbeck's enlightenment
05:38sivangThe 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:38hornbeckplovs: I have just been watching the mailing list
05:38enricoplovs: One thing we can do is creating a 'documentation' metapackage on bugzilla
05:39sivangor make the devs improve it altogether.
05:39enricoplovs: then using that as a todo-list, and to post ideas
05:39sivangthis would be our first doc bug ! :)
=== sivang is however uncertain whe this bug would be close :)
05:39enricoThat could be used to collect requests, and reassign them to other documents we're writing or maintaining
05:40enricosivang: when we feel like, of course!
05:40plovsin the wiki is a page about kernel compiling etc, i could write that
05:40hornbeckplovs: http://wiki.ubuntulinux.org/KernelHowto
05:41hornbeckplovs its all your
05:41sivangenrico : 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:41plovsok, in the documentation should we concentrate on command-line use, apt-get or explain everything through synaptic
05:41enricoBugs that are never closed have a nice usefulness in collecting discussion
05:42enricoWe could collect enough discussion on a never closed topic that it becomes a book on his own
05:42sivangenrico : 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:42enrico(and then we publish the book and close the bug ;)
05:42sivangyes!
05:42makoheh
05:43hornbeckplovs I have been trying to do alittle of both
05:43hornbeckso a book deal is what we are really looking for out of this :)
05:43enricomako: how do we get such a virtual package for bugzilla?
05:43makoenrico: ask justdave
05:43enricohornbeck: not afaik
05:44makoenrico: it shouldn't be a problem
05:44sivangI'll talk to justave
05:44enricohornbeck: I was just talking abstract
05:44plovsuntil then we could just use a page in the wiki with a list of topics we want covered
05:44hornbeckenrico: it was a joke
05:44enricoAlthough 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:45enricoBut I'll keep that for discussion in the dissemination phase
05:45enricoor even, when material is there, anyone can make a book out of it
05:45plovsthe free-bsd is nice, if i would use it, i would buy such a boo
05:45enricohornbeck: ops! Sorry for keeping it so long on a joke :(
05:45hornbeck:)
05:46hornbeckSo goals for right now
05:46hornbeckI need to go to work soon and need to know where we are
05:46hornbeckcan we summerize?
05:47aswI could say a few things.
05:47enricoasw: go on
05:47makosomeone should write up a summary and post it to -devel
05:47aswI will:
05:47makoi will make sure it gets into traffic
05:47enricomako: you'll see our posts on -devel, you'll see them...
=== enrico laughs evilly
05:47aswtalk "upstairs" about doc licensing. (in particular with respect to GFDL...)
=== sivang sivang joings him..moouahhha
05:48aswI have offered to start a "ubuntu for scientists" section.
05:48hornbeckasw: start it up
05:48aswI have suggested a wiki->docbook gateway (based on people's pref for doc book.)
05:48enricoubuntu-devel used a a coordination mailing list, with [doc]  in the subject
05:48aswI'm sorry these are all possibly far away goals...
05:48aswthat's all.
05:48asw(for me)
05:49plovsdo we have some short-term goal, for say three months?
05:49makoin regards to licensing, we don't need to worry so much
05:49enricowe have 3 mantras that enlightened hornbeck
05:49hornbeckyes very much so
05:49enricoOne short term goal could be a short document to get people to install ubuntu and connect with the community
05:49makowe're not debian, and document licenses have an explicit exception in the philosophy document.. this team is probably empowered to deal with them on a case-by-case basis
05:50enricoThat's the shortest-term goal I can figure out
05:50enricoWith sivan we put down some more ideas on this
05:50aswmako: I plan to write a real "dead-trees" book it will be part of my phd thesis and it will include an invariant section regarding why I think freesoftware is important for scientists.  I would like to see ubuntu distribute my book even if debian wont.  But this is a flame war for another day.
05:51aswI also plan to write documentation debian will distribute.
=== sivang reverts back to suggesting the artistic license, however offtopic now :)
05:51hornbeck[OT]  is plone something I need to learn?
05:51enricohornbeck: not until you feel you really need to
05:52hornbeckok
05:52enricoI think discussion could continue with some proposals on the table
05:52plovswhat docbook layout do we use?
05:53enricoSomeone has suggestions about docbook layouts?
05:53plovswe would need some sort of docbook primer like the fedora-people use (or we can use theirs)
05:53hornbeckI would suggest we use the same layout that is used with gnome docs
05:53hornbeckdon't know what it is called
05:53sivangWe can end this now, and have some material sent -devel , than continue discussion their. let us raise up the [doc]  traffic! :)
05:53hornbecksivang: I agree
05:54plovssivang: would it possible to have a seperate doc-list?
05:54hornbeckplovs: not right now
05:54plovstoo bad...
05:54enricoIf there are no other very short-term things to discuss, my plan would be to start wikifying the documentation proposal and posting to the list an extract of the summaries of my and sivan e-mail brainstorming and the summary of this meeting
05:54hornbeckplovs: all in good time
05:54sivangwe would have to add some more traffic to -devel, until they can't stand us amymore and would have to set up one :)
05:55enricoThat's the main plan
05:55aswplovs: it's not so bad to be forced to read what the developers are up to but also if you just use [doc]  in the subject line it's easy to filter the documentation messages...
05:55hornbeckenrico: I will post a docbook format question to the list
05:55sivangasw : exactly.
05:56sivanganother thing that needs be done,
05:56sivangis the start orginizing all the scattered parts of documentation into one stop shop wiki page,
05:56sivangthat would link to everything else
05:56hornbecksivang: I am working on this
05:57hornbeckI have notes for different pages, and just need to get them together
05:57sivangI'd sugges to have the /UDP Page as strting home,
05:57hornbeckplanned on working that tonight
05:57hornbeckok
05:57hornbecksivang: do we want /UDP to branch off to other start pages
05:57sivangand move all development and sketched to /DocumentationTeam/Development
05:58hornbeckdo we want /Desktop /Command than go to the correct docs
05:58sivanghornbeck : it can, however this should be very inline with the goal you're trying to explain
=== enrico works at wikifying the proposal and posting notes, then
05:58plovsin moinmoin with category you can make easily searchable docs, like CategoryNotYetFinished etc
05:59sivangyes
05:59sivangthat could assist us
05:59enricoI declare the meeting has finished, thank you everyone for participating, it's been a great groove!
05:59plovsthen make one page in the wiki with a search-string and it will give you a list of pages
05:59enricoThe room will be free for us to stay around
05:59hornbeckok
05:59enricoSo don't worry about having to leave :)
05:59plovsenrico: see ya!
06:00aswgood talking with all of you!
06:00hornbecksivang: There are alot of random docs
06:00enricoI'll be online just here, following the discussion
06:00sivanghornbeck : yes I noticed :)
06:00hornbecksivang: so do we want to put them all on one page or have pages for sorting
06:01sivanghornbeck : as I see it, we need organize those goal wise high level and then diverge as neccesary in referenced pages.
06:01enricoWriting indexes is also a very good form of writing.  I wouldn't mind creating with composing existing text instead than creating with composing words
06:01sivangthe idea is to make the documenation goal oriented
06:01enricoBut don't talk to me about indexing (yet)
06:01enricoThe problem is, I have the technological solution for all indexing and cathegorization needs
06:02enricoI mean, the perfect solution
06:02hornbeckenrico: get to it
06:02hornbeck:)
06:02enricoSo when I start talking about it, I don't stop
06:02enricoapt-get install debtags-edit; debtags update; debtags-edit
06:03plovshornbeck: a wiki does not need to be hierarchical, just use [[PageList(regex)] ] , to make automatic indexes
06:03hornbeckok
06:03enricodebtags is faceted categorization applied to Debian packages.  It seems to be a good approach for sorting 15000+ different packages
06:04hornbeckwhat is this debtags enrico?
06:04enricoBut here, as you see, we're digressing
06:04hornbeckwell the wife needs me for alittle while
06:04hornbeckI will be around today
06:04makobefore people disband
06:04hornbeckthanks for the meeting everyone
06:04hornbeckok
06:04sivangfine joh :)
06:05makois someone going to write this up?
06:05sivangc'ya soon!
06:05makowho is writing up the summary and action items?
06:05hornbeckenrico?
06:05sivangme and enrico , I guess
06:05enricoYes, I'd say so
06:05makosivang: please, email -devel
06:05hornbeckok, so someone's on it
06:05hornbeckhave fun guys
06:05makoyeah, just want to make sure someone has that one :)
06:06sivangmako : we will , we will .....mouhaaa
06:06sivang:)))
=== sivang away "be back in 15 minutes"
=== x4m [~max@228.160-136-217.adsl.skynet.be] has joined #ubuntu-meeting
=== hubs [~hubs@N617P010.adsl.highway.telekom.at] has joined #ubuntu-meeting
=== hazmat [~hazmat@c-24-15-10-12.client.comcast.net] has joined #ubuntu-meeting

Generated by irclog2html.pl 2.1 by Jeff Waugh - find it at freshmeat.net!