/srv/irclogs.ubuntu.com/2005/05/17/#ubuntu-doc.txt

=== Burgundavia [~corey@S01060010dcc226d1.du.shawcable.net] has joined #ubuntu-doc
=== jsgotangco [~jsg@202.57.71.235] has joined #ubuntu-doc
jsgotangcogood morning02:45
Burgundaviasalut02:46
jsgotangcoBurgundavia, what is happening?02:46
Burgundavianot much02:47
jsgotangcoeven svn isn't active02:47
jsgotangco:(02:47
Burgundaviano02:47
BurgundaviaI need to email elmo my new key02:47
Burgundaviaand then I will get active02:48
jsgotangcook02:48
=== jiyuu0 [~jiyuu0@219.95.34.148] has joined #ubuntu-doc
=== thegreedyturtle [~thegreedy@user-0c93oto.cable.mindspring.com] has joined #ubuntu-doc
jsgotangcothegreedyturtle, hi there04:17
=== jiyuu0 [~jiyuu0@219.95.34.148] has joined #ubuntu-doc
thegreedyturtlehey jsgo, sorry i was idle05:36
thegreedyturtlestill kinda am ;)05:36
jsgotangcono worries05:37
=== blahrus [~blahrus@12-223-50-121.client.insightbb.com] has joined #ubuntu-doc
=== jdub [~jdub@home.waugh.id.au] has joined #ubuntu-doc
Burgundaviahey05:42
Burgundaviaok05:42
Burgundaviaquick summary05:42
Burgundaviawe want a web way to editing our docs in svn, using docbook05:42
Burgundaviafroud has investigated apache lenya05:42
Burgundaviaseems like it meets our needs05:42
Burgundaviawe need a dev to look at it and give and upcheck/downcheck05:43
jduba 'web way'?05:43
Burgundaviaediting online, ala a wiki, but into the svn repos05:43
jdubusing docbook syntax?05:44
Burgundaviayes05:44
jdubso writing docbook syntax into an html form that gets shunted into svn..05:45
Burgundaviayes, I believe so05:45
jdubthat seems remarkably breakable and complicated for simple document editing procedures05:45
BurgundaviaI have not played with lenya myself05:45
Burgundaviawe are looking to involve a great many people in doc editing05:45
Burgundaviaprovide a single source05:45
Burgundaviaand keep our existing infrastructure05:45
jdubthat sounds like using an svn or baz repository directly to me - i don't understand the web page requirement05:46
Burgundaviathe web requirement is to lower the exisiting barrier to editing05:46
Burgundaviathink of this as rosetta vs a gnome-translator05:46
jdubit doesn't lower the barrier usefully05:47
jdubthe writer still has to author docbook05:47
jsgotangcocan i make a comment05:47
jduband they're stuck in an htmlarea instead of a text editor05:47
Burgundaviajsgotangco, jump in05:47
jsgotangcoi still don't see the point of the portal since the manual author still has to dump his thoughts in an html text area05:48
jdub(i see lenya has some element of wysiwyg editing, but has an awful chunk of infrastructure underneath it)05:48
Burgundaviaok05:48
jsgotangco(the awful chunk of intfrastructure can be the xslt stuff)05:49
Burgundaviathe team almost ripped itself apart in January discussing major changes05:49
Burgundaviawe decided that the path of least resistance was to develop a web portal to our existing docbook/svn stuff05:49
jdubthat sounds like a heck of a lot of wasted time to me05:50
Burgundaviacan you suggest a better solution (I am asking seriously)05:51
jdubsorry, but a good editor, sensible revision control (svn or preferably baz) and useful preview tools (yelp) are all you need to start writing and contributing good documentation05:51
Burgundaviawhat about single source?05:52
BurgundaviaI want to remove all docs from the wiki (hopefully)05:52
jdubso, you have to get used to the idea that it will never happen :)05:53
jsgotangcoi still like our current setup05:53
jsgotangco(its quite simple really)05:53
=== Burgundavia is very very frustrated now
jdubofficial documentation in revision control and in the distro (packages) is hugely beneficial05:53
=== Burgundavia really really really should have been at UDU
jdubbecause you have a clear place to contribute (both docs, translations, etc)05:54
jduband a clear delivery path (packages in the distro)05:54
jdubyou could also autogenerate them for a website05:54
Burgundaviawhat about on the web?05:54
jdubif you want to deliver them to a website, that's really simple05:55
jdubthere will always be stuff going on in the wiki05:55
Burgundaviaok05:55
BurgundaviaI am talking single source05:55
Burgundaviathe wiki is currently filled with crap, from our perspective05:56
jdubin fact, having the wiki makes finding people for the documentation team so much easier05:56
Burgundaviamost of what we are discussing has been hashed out many times on the doc team lists05:56
jdubwe can pluck great contributors from the wiki into the doc team, and get them working on the distro docs05:56
BurgundaviaI am trying to move forward what we discussed there05:56
jdubok, so my suggestion for moving forward:05:57
jdub* docbook in revision control05:57
Burgundaviabut you are failing to address the major issue that still exists05:57
jdub* attempt to automate package building for testing purposes05:57
jdub* do some gonzo web delivery for testing purposes, maybe spruce it up and make it sexy later on05:57
Burgundaviawhat about getting it back from the web?05:58
jdub* hack more talk less! :)05:58
jsgotangcojdub, ROCK05:58
BurgundaviaI am trying to get something together here05:58
Burgundaviajsgotangco, to be honest, you are not helping05:58
BurgundaviaI am very very mad now05:58
jdubwell, further down the track we could look into doing documentation commentary like php.net, but in the distro instead of on the web05:58
jsgotangcoBurgundavia, i don't seewhy we have to complicate this to be honest05:58
jdubbut there's no point making things complicated to start with05:58
jsgotangcomy problem at the moment is that no one is pulling docs from svn except some people05:59
BurgundaviaI am going to walk away, and when I come back, I am going to post a message to the devel list about what the doc team has dicussed, what we have found, and where we need to move05:59
jsgotangcoour svn is still empty05:59
jdubjsgotangco: empty?05:59
jdubi thought all the distro doc bits were in it05:59
jsgotangcoempty as in old docs05:59
jsgotangcoi meant it still has old docs06:00
jsgotangcoits not really moving that much06:00
jdubyeah06:00
jsgotangcojust look at the commit list06:00
jdubseems there's more discussion about infrastructure issues than actual doc hacking :)06:00
jsgotangcoi know06:00
jsgotangcothats why i believe froud is getting frustrated at this06:00
jsgotangcothis is not a complicated issue06:01
jsgotangcojdub, http://lists.ubuntu.com/archives/ubuntu-doc/2005-May/002220.html06:03
Burgundaviaok06:04
Burgundaviasorry, needed to blow off steam06:04
BurgundaviaSean and I have spent the past 2 months talking about this issue06:04
Burgundaviaand this is what we came up with06:04
Burgundaviaso, yes there has already been a lot of talk06:04
Burgundaviathis is about how to move it forward06:04
jdubi don't see the necessity for a "web portal" to move forward06:05
jdubwe already have the tools06:05
Burgundaviabasically, I said, we need a web way to edit stuff06:05
jdubbut you don't06:05
Burgundaviasean said, lets not lose the exisiting infrastructure06:05
jsgotangcojdub, would it be possible to consider this for the future instead for this release cycle06:05
jdubyou have a much better tool on your hard disk06:06
Burgundaviajsgotangco, no06:06
jduba web browser is a hideous place to write docbook06:06
Burgundaviaat least let us try and then fail06:06
jdubyou actually have all the tools you need already06:06
Burgundaviabefore you condemn us to fail beforehand06:06
BurgundaviaI find that very annoying06:06
jdubi'm not saying it will fail06:06
jsgotangcoi can only imagine our portal becoming like the wiki sorry but that's how i feel about this06:06
jdubi'm saying you have everything you need to write and publish documentation06:07
Burgundaviajsgotangco, we can control access to a web portal much easier06:07
Burgundaviajdub, I am saying we don't06:07
jdubyou don't need a web portal to write docs06:07
Burgundaviajdub, you don't need rosettta to translate either, by the same logic06:07
jdubthat's absolutely true06:07
Burgundaviabut it makes it easier06:08
Burgundaviathis is about making it easier06:08
BurgundaviaUbuntu is about making it easier06:08
jdubdude06:08
jdubemotional argument is not useful argument06:08
BurgundaviaI am just very frustrating06:08
Burgundaviabecause we have a workable solution06:09
Burgundaviafroud has tested it06:09
Burgundaviawe just need a dev to implement it06:09
jdubno, dude06:09
jdubthis is silliness06:09
jdubyou already have all the tools you need06:09
jdubevery other project out there has written documentation without a 'web portal'06:09
Burgundaviamost docs suck06:09
Burgundaviaand they don't involve the community06:09
jdubin exactly the same way that every other project out there has translations done in emacs06:09
jdubthat is incorrect06:09
Burgundaviasuffice it to say that we need a better way. We really do. The web is a very easy tool to getting people involved06:10
Burgundavialets harness that06:10
jdubi'm sorry, but this is emotional claptrap06:10
jduba) you don't need a better way, you need to actually write docs06:11
Burgundaviajdub, that is rude06:11
jdubb) you don't need more people involved, you need a small team doing great work - *then* you can scale up06:11
jdubthis is infrastructural fantasy stuff06:11
jdubthe point about rosetta is fine, but translation has actually scaled to the point where rosetta can be useful06:14
jdubdocumentation, within ubuntu, has not06:14
jduba better first step would be to have web based commentary on documentation, like php06:15
jdubthen integrating that with yelp, the documentation reader in gnome06:15
Burgundaviacommentary on docs?06:15
jdubthat will allow people to contribute to the documentation in a useful way, and have documentors operating as editors of those contributions06:16
jdubfurther down the track, using something similar to monodoc for user contributions far beyond commentary would be great06:16
jdubbut it's very, very important to start small and scale up06:16
Burgundaviathen fundamentally is the difference between that and what I am proposing?06:16
jdubi'm talking about the future06:16
jdubnice things to have06:16
BurgundaviaI think the people will appear "when you build it"06:16
jdubthey're entirely unnecessary for writing documentation right now, however06:17
jdubwe have the best tools to hand already06:17
jdubrevision control (svn or even better, baz)06:17
Burgundaviawe currently use svn, talk to us later about changing06:17
Burgundaviawe are also not going to change from docbook06:18
jdubemacs or vi with docbook/xml editing helpers, or even conglomerate if it's stable enough06:18
Burgundaviathus, we need an easy way to involve people06:18
Burgundaviaconglomerate is not06:18
jdubok, the easy way to involve people is this:06:18
BurgundaviaI use bluefish myself06:18
jdubdo absolutely fantastic work and inspire people to get on board06:18
Burgundavialook, docs are glamourous06:19
Burgundaviaevery single barrier, no matter how small, that is in the way migth be the showstopper06:19
Burgundaviaobserve gnome docs06:19
jdubi understand06:19
jdubah, gnome documentation has different problems06:19
jdubrelated to scaling and branching06:19
Burgundaviaon the web eliminates a huge barrier of getting another program and learning how to use that, etc.06:19
jdubno, it doesn't significantly help06:20
jdubunless the user doesn't have to write docbook06:20
BurgundaviaI don't want documentors to have to deal with version control06:20
Burgundaviataht should just happen06:20
jdubwhich can be done with desktop tools too :)06:20
Burgundaviawhich ones?06:20
BurgundaviaeSVN?06:20
jdubno06:20
jdubdude06:20
jdubscale up06:20
jdubforget this infrastructure fancy06:21
Burgundaviajdub, I am saying we will scale when we have the structure in place06:21
jdubthe important thing is to do great work - that's what gets people interested to help out06:21
jdubyou don't need to scale now06:21
jdubyou need to start06:21
Burgundaviaplease just implement the lenya thing, and then we can talk06:22
Burgundaviawe can make that an official request, if you want06:22
jdub"then we can talk"?06:22
jdubdude06:22
jdubseriously06:22
jsgotangcoBurgundavia, that didnt sound right06:22
=== Burgundavia thought this would be easy
jdubit's not easy because it's not right or compeling06:23
jdubcompelling06:23
jdubthe doc team doesn't need more infrastructure to write docs06:23
jdubit needs more docs :-)06:23
jdubthat's what will get people interested06:24
Burgundaviajsgotangco, have you read through the backlog of this channel and doc-list?06:24
jdubone of the past gnome doc team leaders learnt docbook specifically to contribute06:24
jdubi know guys who've learnt C to contribute to gnome06:24
BurgundaviaI am trying to find the email exchange mark, sean and I had06:24
Burgundaviajust a sec06:24
jsgotangcoBurgundavia, irclog no, but doc-list yes, for me its all pointless as no one is pulling docs from svn06:25
jsgotangcosvn is all that matters to me at the moment06:25
jdubthe real lesson here is not to get bogged down in irrelevant details06:25
jdubstart small, kick arse, scale when necessary, not before06:26
jdubi understand the attraction, but i've seen way too many projects kill themselves doing things that are unrelated to their real goals06:27
jdubi have to get some lunch :-)06:27
jsgotangcome too06:28
jsgotangcojdub, thanks for the time06:28
Burgundaviajdub, take a read through this thread --> http://lists.ubuntu.com/archives/ubuntu-doc/2005-April/001755.html06:28
jdubso i just had a long walk to get lunch06:58
jduband thought about a bunch of the problems06:58
jsgotangcosounds good i just arrived from lunch as well07:00
jdubi think the first part is really basic07:00
jdubthis talk about a web portal assumes that the major role of the doc team is 'writing docs'07:00
jdubwhere really, it isn't07:01
jdubat least not this early on07:01
jdubthere's an enormous amount we can do simply by using what we have, and integrating it in a more useful way07:01
jdubthere's very little that needs to be done from scratch07:01
jdub*very* little07:01
Burgundaviathat is the point of lenya07:04
Burgundaviait is already a fairly mature app07:04
jduboh, dude, come on07:05
Burgundaviain fact, they just added some measure of WYSIWYG editing07:05
jsgotangcook i want to base on my experience im no docbook expert at all, sean took the time to mentor me and most of what I know came from him but it didnt stop me from doing stuff in what we currently have in a learning standpoint it is very interesting but can be intimidating to the new user07:05
jsgotangcoid rather have contributors who know some level of docbook or at least willing to bitethe bullet instead of giving them toned-down tools07:06
jsgotangcotoo much abstraction muddles things07:06
Burgundaviajdub, jsgotangco, sorry, my ex is calling, I must run07:07
jdubBurgundavia: "the point of lenya" is not to realise that we hardly need to write new docs at all07:07
Burgundaviajdub, say again?07:07
jdubi've relayed a thought about hardly needing to write docs at all, and you've somehow related it to a document writing tool07:08
jdubit ends up sounding silly after a while07:08
BurgundaviaI am still not understanding what you are saying07:08
jsgotangcohmm you mean using technology for the sake of technology instead of your end goal?07:08
Burgundaviaweb based writing is not technology for the sake of technology07:09
jdubBurgundavia: you inserted your current argument into an unrelated point07:09
Burgundaviaok07:09
jdubhere's me saying we don't need to write new docs07:09
jduband here's you saying "this is what a doc writing tool is for!"07:10
jdubit doesn't gel07:10
jduband it sounds silly07:10
Burgundaviaok07:10
Burgundaviawhat I got from you is that current tools are suffecient not "we don't need to write new docs"07:11
jduboddly, i'm saying both07:11
Burgundaviawhat do you mean about writing new docs?07:12
jdubbut the latter is a new thought07:12
Burgundaviaare you saying we just need to collate what is out there?07:12
Burgundaviathat is total crack07:12
jdubit is not total crack07:12
jdubwe have a wealth of documentation already07:12
jsgotangcoit makes sense reusing what we currently have07:12
jduband it is inadequately presented to users07:12
Burgundaviagood docs are visual07:12
jsgotangcowe just have to weed out the crack ones07:12
Burgundaviavisual requires screenshots/etc.07:12
Burgundaviawhich are by there very nature Ubuntu specific07:13
jdubbut you're assuming that requires fresh new documentation07:13
Burgundaviaat the very least, it requires major refactoring of exisiting docs07:13
jduband ignoring the massive benefits we can give to users from existing works07:14
jdubno dude07:14
jdubeven before refactoring07:14
jdubthere is a lot we can do07:14
jdubfor instance07:14
Burgundaviasorry, really have to go this time07:14
jdubearly in the warty cycle07:14
Burgundaviamy ex is here07:14
Burgundaviacountinue what you have to say07:14
BurgundaviaI can read in the scrollback07:14
Burgundaviaand respond later07:14
jdubi suggested (and thom implemented) integration of the debian doc metadata and OMF07:14
jdubsuddenly, we almost doubled the documentation available in yelp07:15
jdubthat's a huge win07:15
jdubwith very little work07:15
jsgotangcojdub, most argue that no one reads documentation in yelp07:15
jdubjust pulling together stuff we already have07:15
jdubjsgotangco: well hey, lots of people argue that no one reads documentation :-)07:15
jsgotangcook same goes then so we have so much stuff in the wiki07:16
jsgotangcosome are gold, some are crack07:16
jsgotangcoi still believe we can weed out the crack in that07:16
jdub(i don't think either argument has much merit)07:16
jsgotangcoand integrate in current svn07:16
jdubyeah, there's a bunch of stuff we can do there07:17
jdubbut there's way more we can do without even touching a line of docbook07:17
=== thegreedyturtle [~thegreedy@user-0c93oto.cable.mindspring.com] has joined #ubuntu-doc
jsgotangcowe all agreed in UDU that our wiki needs a facelift thats why we had a bof for that07:17
jdubyeah, switching away from zwiki will make life simpler07:18
jdubthat was an unfortunate mistake07:18
jsgotangcoi still believe that since docbook gets frozen our wiki is the natural exgtension of the documentation therefore needs tighter controls07:18
jdubthe wiki needs tighter controls?07:18
jsgotangcowell at least have someone review what people have been posting on it07:19
thegreedyturtle'hoy07:19
jdubyes07:19
jdubit needs farming07:19
thegreedyturtlei kinda disagree with that, i think that the wiki needs to be very free, and then the docteam takes the best of it and moves it into the official docs07:20
jsgotangcowe shouldn't remove its collaborative nature07:20
jdubthegreedyturtle: (you're not disagreeing)07:20
thegreedyturtleim disagreeing with the statement that the wiki needs tighter controls07:20
jdubthegreedyturtle: jsgotangco just clarified that07:20
thegreedyturtlemm, im not so sure about even review myself though07:21
thegreedyturtleit would be good for keeping the wiki organized though07:21
jdubevery good wiki needs farmers07:21
jsgotangcoyou end up with ambigious docs07:22
thegreedyturtleclarify farmers?07:22
jsgotangcofarmers weed stuff07:22
jdubpeople who roam the wiki, tidying stuff up, culling the crap, etc.07:22
thegreedyturtlegot it07:22
jsgotangcoso far mdke is doing good work on that07:22
thegreedyturtleis mdke post on the list at all? i don't have the names matched to the irc handles yet07:24
jsgotangcoim sure contributors are interested in learning some docbook07:24
jsgotangcothegreedyturtle, mdke is matthew east07:24
thegreedyturtleok07:24
jsgotangcojdub is jeff waugh07:24
thegreedyturtlethanks07:25
thegreedyturtlebeing fairly new myself, i think the biggest hurdle for new people isn't actually the docbook formats, but accessing the repositories07:26
jsgotangcohmmm you mean by committing or just accessing07:27
jsgotangcoits not that difficult07:27
thegreedyturtlea bit of both, and i know it's not difficult, but consider what happens when someone checks out the document source code07:27
thegreedyturtlethey suddenly get this huge dump of code, and it's easy to get overwhelmed07:28
thegreedyturtleand then: what to do next?07:28
jsgotangcowell you check out svn because you expect that stuff right07:28
thegreedyturtlewell, you check out the svn because you expect it, and I check out the svn because I expect it, but someone who just wants to submit a quick document about how they made something work would not want that stuff07:29
thegreedyturtlethey just want to write a paper and feel good about it - which is why wikis are so popular... which brings us back to the root07:29
jsgotangcowe can't put all that stuff in svn much less include every contribution07:30
thegreedyturtlevery true - so the question here is how can we allow a user who doesn't want to deal with docbook and svn to contribute to something other than a wiki?07:31
thegreedyturtlethe simple way is to use farmers07:32
jdubthegreedyturtle: further down the track - annotated documentation, either on the web or in yelp07:32
jdubbut it's *further down the track*07:33
jdubno point worrying about it now07:33
thegreedyturtlerighto07:33
jsgotangcook we're going back to where we started, this is not a complicated thing some people have submitted docs in OOo or other format and we've publishedit as docbook07:34
thegreedyturtleso that's your earlier point about just getting something 'on paper' ?07:34
thegreedyturtleyou are saying that someone submitted as OOo and someone else did the conversion for them, right?07:35
jsgotangcoright07:35
jsgotangco(although OOo to Docbook isn't the cleanest thing available at the moment)07:36
thegreedyturtlefrom your experience, do you think that's scaleable?07:36
thegreedyturtleanother question, one of you mentioned that the svn documents are all old?07:36
thegreedyturtlewhat are they old compared to?07:37
thegreedyturtleanother repo, the wiki, ... ?07:37
thegreedyturtle(im kinda picking your brain now.. :)07:37
jsgotangcoif you mean scaleable in a sense that we can do it for everyone everyday, no its not the most effective way but we don't do that everyday07:39
jsgotangco(i don't think traffic of that kind won't go up either)07:39
jsgotangcowhen I said old, i meant hoary old docs since we're in breezy, there are some stuff that may not be applicable now07:40
thegreedyturtleok07:40
jsgotangco(if you look at the commit list nothing much has moved either)07:40
jsgotangco(which is understandable because we're still to early to do effective docs for breezy)07:41
jdubthegreedyturtle: luckily, we don't need to be concerned about scalability this early on :-)07:41
jsgotangcoright07:41
thegreedyturtleyou guys both running breezy right now?07:41
jsgotangcomy other machine runs breezy07:41
thegreedyturtleis it worth running yet?07:42
jsgotangcoi wouldn't use it as main of course07:42
thegreedyturtleok07:43
jsgotangcobut some people i met in UDU run breezy in their laptops07:43
thegreedyturtlemmm UDU, that was prolly lotsa fun neh?07:43
jsgotangcoit was fun but it was work at the same time07:44
jsgotangco(we watched hitchiker's guide though)07:44
thegreedyturtlebrb07:44
thegreedyturtlefun, work, what's the difference?07:48
thegreedyturtlewhat do you usually use to edit docbook, just an xml editor?07:49
jsgotangcoheck even emacs will do07:50
thegreedyturtleyeah but I'm lazy...07:51
jsgotangcowell being lazy won't start things really07:53
thegreedyturtleit's not a lazy as in start things, more lazy as in i want the convenience of a simple editor, but i guess it doesn't matter07:54
jsgotangcoi like learning new stuff i guess it really depends on the person07:55
thegreedyturtlei like learning stuff too, but right now im up to my nostril hairs07:55
thegreedyturtlei have a subversion book to read, a docbook to read, and im still finishing essential sys admin, let alone my programming courses at college. I also want to at least get a small 'code portfolio' under my belt, and toss in a girlfriend... you get the idea :)07:57
thegreedyturtleand I still needs a job...07:57
thegreedyturtlehence, the easier it is to contribute, the more I'll be able to07:58
=== jiyuu0 [~jiyuu0@219.95.34.148] has joined #ubuntu-doc
thegreedyturtleanyhoo, im off to work on the above list, i appreciate your ear 08:00
Burgundaviajsgotangco, check your mail09:18
jsgotangcook reading now09:22
=== Liz [~Liz@fixed-203-87-27-63.nsw.chariot.net.au] has joined #ubuntu-doc
jsgotangcook at least we'll know if we're go or no09:25
Burgundaviabasically I am tired of talking this issue09:25
Burgundaviaand jdub really really pissed me off09:25
Burgundaviawe have hashed out nearly every detail, we just need the implementation now09:26
jsgotangcoill try out lenya myself later it looks mighty interesting09:27
Burgundavialenya looks really really cool09:27
KinnisonMorning09:28
Burgundaviasalut Kinnison 09:28
BurgundaviaI was arguing with more people today09:28
Kinnisonheh09:28
Burgundaviathis time it was jdub09:28
BurgundaviaI aim high09:28
=== Kinnison grins
Burgundaviatomorrow it will be mark09:32
Burgundaviaoh wait, already done that09:32
Burgundaviabugzilla bug 851609:32
Burgundaviain other news, corey is looking forward to helping out more with malone09:33
jsgotangcospatial?09:33
Burgundaviayep09:33
jsgotangcothat was a nasty thread09:33
BurgundaviaUbuntu spatial breaks usablity09:33
KinnisonYeah, I don't like it, but my father does09:33
Burgundaviathe closing window way?09:33
Kinnisonyep09:33
Burgundaviaseems to split the community09:33
Kinnisonaye09:34
Burgundaviaala the menu bar thing09:34
Kinnisonhaving a config option in breezy is a *must* IMO09:34
Burgundaviawindow vs global09:34
=== Kinnison reads his IRC backlog
=== cc [~cc@byte.fedora] has joined #ubuntu-doc
Burgundaviajsgotangco, check your mail10:26
jsgotangcowait10:26
jsgotangcoit might work but it'll take some time10:29
BurgundaviaI just sent that to the list to highlight the importance of getting our portal up10:29
jsgotangcobrb11:29
=== enrico [~enrico@enrico.developer.debian] has joined #ubuntu-doc
=== solomarv [~rouslan@terkin.hamlin.clarkson.edu] has joined #ubuntu-doc
=== solomarv [~rouslan@terkin.hamlin.clarkson.edu] has left #ubuntu-doc []
=== jdub boggles at cory
jdubcorey01:43
=== Kinnison tickles jdub
=== jiyuu0 [~jiyuu0@219.95.34.58] has joined #ubuntu-doc
=== jiyuu0 [~jiyuu0@219.95.34.58] has joined #ubuntu-doc
=== jjesse [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== maskie [~maskie@196-30-109-217.uudial.uunet.co.za] has joined #ubuntu-doc
=== HappyFool [~HappyFool@tedo-ip-nas-1-p274.telkom-ipnet.co.za] has joined #ubuntu-doc
HappyFooli've written a page on the ubuntu wiki, and one of the comments I've made is that it *might* be unsafe to edit /etc/modules -- is this overly conservative? What could realistically go wrong? (page is http://www.ubuntulinux.org/wiki/IntelFiveThreeSixEPModemHowto)08:52
HappyFooloh, and hello ;)08:52
=== mpt [~mpt@203-167-186-125.dsl.clear.net.nz] has joined #ubuntu-doc
=== Burgundavia [~corey@S0106000ea623639e.gv.shawcable.net] has joined #ubuntu-doc
thegreedyturtlemeeting at #ubuntu-meeting09:09
Burgundaviaindeed09:10
=== sivang [~sivang@box79162.elkhouse.de] has joined #ubuntu-doc
=== jjesse [~jjesse@mail.ftpb.com] has left #ubuntu-doc []
mvirkkilAny news about the CD shipments?10:08
Burgundaviawe are not the correct people to ask10:10
Burgundaviaand they will contact you when they ship, to confirm the addy10:10
mvirkkilBurgundavia: Just wondering. Didn't want to ask in ubuntu-devel either. Oh, well. Patience is a virtue :-)10:11
Burgundaviaindeed10:12
=== HappyFool [~HappyFool@tedo-ip-nas-1-p274.telkom-ipnet.co.za] has left #ubuntu-doc ["Leaving"]

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!