/srv/irclogs.ubuntu.com/2006/06/16/#ubuntu-meeting.txt

=== nixternal [n=nixterna@71.194.189.213] has joined #ubuntu-meeting
=== nixternal`v2 [n=nixterna@71.194.189.213] has joined #ubuntu-meeting
=== j_ack [n=nico@p508DC1EE.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== JaneW [n=JaneW@dsl-146-167-152.telkomadsl.co.za] has joined #ubuntu-meeting
=== rikai [n=kitty@pool-72-65-96-19.ptldme.east.verizon.net] has joined #ubuntu-meeting
=== Flik [n=Flik@d205-250-159-119.bchsia.telus.net] has joined #ubuntu-meeting
=== rikai [n=kitty@pool-72-65-100-66.ptldme.east.verizon.net] has joined #ubuntu-meeting
=== nixternal [n=nixterna@71.194.189.213] has joined #ubuntu-meeting
=== susana_ [n=susana@92.Red-83-52-54.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== teckfatt [n=teckfatt@AC8D48E8.ipt.aol.com] has joined #ubuntu-meeting
=== Spec [n=dragonco@ubuntu/member/spec] has joined #ubuntu-meeting
=== Spec[x] [n=dragonco@charon.devis.com] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== dou213 [n=xxx@p54B04254.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== paco_reyes [n=paco@201.121.81.154] has joined #ubuntu-meeting
=== ogra_ [n=ogra@p5089DB24.dip.t-dialin.net] has joined #ubuntu-meeting
=== ajmitch__ [n=ajmitch@203.89.166.123] has joined #ubuntu-meeting
=== ajmitch__ [n=ajmitch@203.89.166.123] has joined #ubuntu-meeting
=== ajmitch__ [n=ajmitch@203.89.166.123] has joined #ubuntu-meeting
=== Flik [n=Flik@d154-5-33-125.bchsia.telus.net] has joined #ubuntu-meeting
=== BlueT__ [n=BlueT@61-59-209-195.adsl.static.seed.net.tw] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== gruvby [i=gruvby@eyeoftruth.be] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== magical_trevsky [n=magical@80-45-41-53.static.dsl.as9105.com] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== nixternal [n=nixterna@71.194.189.213] has joined #ubuntu-meeting
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has left #ubuntu-meeting ["Bye!]
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== lloydinho [n=andreas@rosinante.egmont-kol.dk] has joined #ubuntu-meeting
=== imbrandon_ [n=brandon@ubuntu/member/imbrandon] has joined #ubuntu-meeting
=== mvo [n=egon@p54A67118.dip.t-dialin.net] has joined #ubuntu-meeting
=== jenda [n=jenda@unaffiliated/jenda] has joined #ubuntu-meeting
=== rodarvus [n=rodarvus@200.146.65.147.adsl.gvt.net.br] has joined #ubuntu-meeting
=== Lure_ [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== doko_ [n=doko@dslb-088-073-096-168.pools.arcor-ip.net] has joined #ubuntu-meeting
=== ubijtsa2 [n=ubijtsa@nat-pool-lhr.redhat.com] has joined #ubuntu-meeting
=== ubijtsa2 [n=ubijtsa@nat-pool-lhr.redhat.com] has left #ubuntu-meeting ["Leaving"]
=== rodarvus [n=rodarvus@200.146.65.147.adsl.gvt.net.br] has left #ubuntu-meeting ["Leaving"]
=== luka74 [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== KOnsumer [n=KOnsumer@drsd-d9b85624.pool.mediaWays.net] has joined #ubuntu-meeting
=== Fracture [n=Fracture@dsl-202-173-191-84.qld.westnet.com.au] has joined #ubuntu-meeting
=== lucas [n=lucas@ubuntu/member/lucas] has joined #ubuntu-meeting
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== Hirion [n=hirion@draugr.de] has joined #ubuntu-meeting
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
kbrookssee you later01:59
=== bhuvan_ [n=bhuvan@vpn5.maa.collab.net] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:bhuvan_] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 16 Jun 17:00 UTC: Docteam meeting | 20 Jun 20:00 UTC: Technical Board | 21 Jun 13:30 UTC: Xubuntu | 21 Jun 20:00 UTC: Edubuntu | 26 Jun 21:00 UTC: Kubuntu | 28 Jun 12:00 UTC: Edubuntu | 28 Jun 13:30 UTC: Xubuntu
=== ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Jun 20:00 UTC: Technical Board | 21 Jun 13:30 UTC: Xubuntu | 21 Jun 20:00 UTC: Edubuntu | 26 Jun 21:00 UTC: Kubuntu | 28 Jun 12:00 UTC: Edubuntu | 28 Jun 13:30 UTC: Xubuntu
=== Plug [n=crb@203-167-190-117.dsl.clear.net.nz] has joined #ubuntu-meeting
=== Lure_ [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== bhuvan [n=bhuvan@ubuntu/member/bhuvan] has left #ubuntu-meeting []
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has joined #ubuntu-meeting
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has left #ubuntu-meeting []
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has joined #ubuntu-meeting
lukkettowhen the next meeting to become "member"?03:09
=== luka74 [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
azeemlukketto: AFAIK the next community council meeting should be soon, but no time has been set yet03:10
azeembut I haven't followed closely03:10
lukkettoazeem: thank you! I'll be tuned ;)03:14
=== j_ack [n=nico@p508D8C93.dip0.t-ipconnect.de] has joined #ubuntu-meeting
jendaI've been following closely, but it hasn't helped much :)03:23
=== DBO [n=DBO@cpe-71-65-4-255.twmi.res.rr.com] has joined #ubuntu-meeting
=== LjL [n=ljl@62-101-126-215.ip.fastwebnet.it] has joined #ubuntu-meeting
Seveasazeem, probably in 2 weeks03:31
Seveasnext week is the paris conference03:31
azeemwas there a CC meeting this week?03:32
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== rodarvus [n=rodarvus@201.21.134.56] has joined #ubuntu-meeting
=== lapo [n=bat@host166-243-static.46-85-b.business.telecomitalia.it] has joined #ubuntu-meeting
=== lapo [n=bat@host166-243-static.46-85-b.business.telecomitalia.it] has left #ubuntu-meeting ["Ex-Chat"]
=== j_ack [n=nico@p508D8C93.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== magical_trevsky [n=magical@80-45-41-53.static.dsl.as9105.com] has joined #ubuntu-meeting
=== rodarvus [n=rodarvus@201.21.134.56] has left #ubuntu-meeting ["Leaving"]
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== rodarvus [n=rodarvus@201.21.134.56] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== bhuvan [n=bhuvan@ubuntu/member/bhuvan] has joined #ubuntu-meeting
=== DonSc [n=don@82-41-205-39.cable.ubr11.edin.blueyonder.co.uk] has joined #ubuntu-meeting
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has joined #ubuntu-meeting
=== klepas [n=klepas@203-213-31-142.static.tpgi.com.au] has joined #ubuntu-meeting
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has joined #ubuntu-meeting
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has left #ubuntu-meeting []
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== luka74 [n=lure@ubuntu/member/lure] has joined #ubuntu-meeting
=== jjesse [n=jjesse@64.186.55.234] has joined #ubuntu-meeting
jjesse@schedule detroit06:53
UbugtuSchedule for America/Detroit: 20 Jun 16:00: Technical Board | 21 Jun 09:30: Xubuntu | 21 Jun 16:00: Edubuntu | 26 Jun 17:00: Kubuntu | 28 Jun 08:00: Edubuntu | 28 Jun 09:30: Xubuntu06:53
=== LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-meeting
klepasjjesse: that's nice :)06:57
klepas@schedule Sydney06:57
UbugtuSchedule for Australia/Sydney: 21 Jun 06:00: Technical Board | 21 Jun 23:30: Xubuntu | 22 Jun 06:00: Edubuntu | 27 Jun 07:00: Kubuntu | 28 Jun 22:00: Edubuntu | 28 Jun 23:30: Xubuntu06:57
=== archis [n=archis@unaffiliated/archis] has joined #ubuntu-meeting
bhuvanding, time to start ?07:00
LaserJockwow, punctual07:00
bhuvanlet's try to be punctual :)07:00
ograwhats going on? there is nothing scheduled07:00
jjessedoc team meeting07:01
bhuvanogra: we have scheduled doc team meeting, but it was not updated in the topic ...07:01
jjessethe schedule got messed up, the channel and fridge had it for yesterday, when today is the real time07:01
ograah07:01
ograi remember :)07:01
LaserJockI thought it was yesterday too07:01
highvoltageheh. they've probably said 'ubuntu' 10 times on the news tonight :)07:01
ograhighvoltage, not here :/07:02
highvoltage(sorry, meant for other channel)07:02
bhuvanLaserJock: no07:02
nixternalwoo07:02
nixternalalmost missed it07:02
bhuvanlet's start. first: Has everyone merged any changes made to the branch back to trunk for their documents?07:02
jjessecan we wait to make sure mdke is here?07:02
=== Exdaix [n=Exdaix@c-69-242-74-210.hsd1.pa.comcast.net] has joined #ubuntu-meeting
bhuvanok, np07:02
LaserJockbhuvan: I'm guessing no07:03
jjesselooks like he isn't goign to make it07:03
bhuvanLaserJock: ok07:03
jjessebhuvan: yes i have merged some changes back into branches for the releasenotes for bug #4852507:03
UbugtuMalone bug 48525 in kubuntu-docs "Problems with Dapper Release Notes for Kubuntu" [Medium,Confirmed]  http://launchpad.net/bugs/4852507:03
LaserJockbah, why can mdke never make the meetings? we need to schedule him better ;-)07:03
jjessehowever i'm not done making all of the changes07:03
bhuvanok07:04
LaserJockpackaging guide merge is ready to commit, I was just waiting for mdke to merge the common stuff07:04
bhuvanok07:04
jjessebhuvan: the changes have been both made in trunk/kubuntu and also branches/dapper/kubuntu07:04
bhuvanok, so henceforth we should make changes only in trunk?07:04
jjessebhuvan: correct07:05
bhuvancool07:05
LaserJockyeah, unless we have some weird thing that should go in -updates07:05
jjesseespecially as we build edgy documents and then at the end of things we wil merge trunk to branches/edgy07:05
bhuvanyeah ok07:06
jjesse+1 LaserJock07:06
bhuvanjjesse: i guess we have long way to go to creat branches/edgy?07:06
LaserJockdoc string freeze07:06
jjessewhen doc freeze comes we create branches/edgy07:06
jjesse4 months07:06
bhuvanoh ok07:07
jjesseactually less then that :)07:07
LaserJockwe'll see next week :-)07:07
bhuvanwhen is edgy scheduled to release (if i'm ignorant) ?07:07
nixternaloctober07:07
bhuvanok07:07
LaserJockbhuvan: the release schedule will be done next week at the dev summit07:07
nixternalfalls in line with the every 6 months07:07
jjessegets us bac on schedule for the 6 months after the delay07:08
jjessewhats' the next point in the agenda?07:08
LaserJocknew docs07:08
bhuvannext: New documents for EdgyEft07:08
nixternalNEW DOCUMENTS FOR EDGY EFT07:08
nixternalhehe07:08
bhuvan1) Ubuntu Reference Manual07:08
bhuvanany opinion about adding this manual for ubuntu?07:09
LaserJockwhat does it do?07:09
jjessewhat exactly will this manual be?  how will it defer from the DesktopGuide?07:09
LaserJockwe need a spec or something?07:09
jjessei would assume?07:09
LaserJockwhose baby is it?07:10
bhuvanLaserJock: spec is not ready. but the intention is to make sure user is able to resolve most of his issues using this manual. it covers basics07:10
bhuvanLaserJock: it's (will be) mine!07:10
jjessehow does that differ from the Desktop Guide?07:10
bhuvanjjesse: here we may cover how to install (basics), how to upgrade, how to configure custom apt repo, some server apps. finer specifics may be covered in specialised manuals like desktop guide, server guide, etc.07:11
jjessebhuvan: seems like a lot of overlap07:12
LaserJocktroubleshooting?07:12
bhuvanjjesse: may be how to add a cron job07:12
bhuvanjjesse: overlap with existing ones?07:12
bhuvanLaserJock: you want to add that section?07:12
jjessebhuvan: yes overlap with what the desktop guide can and should show07:13
bhuvanjjesse: i want this manual to the superset and all other documents may be derived from it. it should be the one stop document for almost all user requirements. for finer details, the users can refere specialized documents/manuals07:15
bhuvanit's just a thought. unsure how relevant/useful it will be07:15
jjessethen we need to make a Kubuntu one as well07:15
bhuvanjjesse: definitely :)07:16
nixternalthats where i can help out if needed since i use Kubuntu and know my ways around KDE...i tend to loose it, or get lost in gnome ;)07:16
LaserJockhmm, I think something more like an index of what we have07:16
LaserJock?07:16
jjesseLaserJock: i wonder if that would be better on what mdke is suggesting about reording yelp07:16
bhuvani guess almost all distribution (redhat, gentoo, debian) have such kind of document. so i guess we should have one07:17
LaserJockjjesse: that's what I was thiinking07:17
nixternalit could be universal, as pretty much what you do with Ubuntu you can do with Kubuntu and so forth, you would have to get specific when it comes down to KDE/GTK specific apps07:17
jjessebhuvan: i think we need a more/better defined spec of it before i can figure out why i would use it as a user07:18
jjessemaybe some further discussion on the mailing lists?07:18
jjessewith links to other docs of similar sort07:18
LaserJockyeah07:18
LaserJockI agree07:18
bhuvanjjesse: point. it adds value only when we have defined spec. i guess, i can prepare the spec so we can discuss either in mailing list/irc07:19
LaserJockI think a nice indexing type page (one for all derivatives) that makes it easy for a user to find what they want in the existing docs07:19
LaserJockwould be nice :-)07:19
jjessewhich i think mdke is aruging for07:19
LaserJockkinda, yeah07:20
bhuvanLaserJock: you are more refering to site map kind of document. i guess, reference manual may not be for that07:20
LaserJockkind of like a site map, but a little more to it07:20
bhuvanyeah07:21
LaserJockbhuvan: I'd suggest making a spec with an outline and links to other like docs as jjesse has said. I'm just not clear on what you are proposing07:21
bhuvanLaserJock: ok07:21
LaserJockand how it integrates with our docs, etc.07:21
=== linuxmonkey [n=linuxmon@unaffiliated/LinuxMonkey] has joined #ubuntu-meeting
bhuvanok07:21
LaserJockI think I like the idea, I just need to see more and we should tweak it up nice :-)07:21
bhuvanyeah ok and it should be presented well :)07:22
jjesse+1 laserjock07:22
=== linuxmonkey [n=linuxmon@unaffiliated/LinuxMonkey] has left #ubuntu-meeting ["Konversation]
bhuvanok, good plan. shall we move to next topic ?07:22
LaserJocksure07:23
bhuvanKubuntu Docs ([JonathanJesse] )07:23
bhuvanjjesse: do you like to propose new documents for kubuntu?07:24
nixternaljjesse: this is along the lines of what kmon and Riddell referred to?07:24
LaserJockjjesse: ok so what's new, the switching from windows?07:25
jjessesorry phonecall07:26
nixternalmy opinion, as well as many other Kubuntu'ers, is that the documentation is Ubuntu sided, and it seems as if Kubuntu is a back burner project..i think users would like to see a little more kubuntu specific documentation07:26
nixternalhaha jjesse me too..my sister wouldn't stop talking07:26
jjessenixternal what are you refering to riddell talkign about?07:27
LaserJocknixternal: I've been hearing that kind of thing from the dev side as well07:27
nixternalabout the Kubuntu documentation that was brought up during the Kubuntu Meeting a week or so ago07:27
jjessenixternal:  ah yes07:27
jjessewell currently the spec KubuntuDocs/Edgy refer to the current docs plus a SwitchingFromWindows07:27
jjesseplus there is no guide for any of adept programs which i'm writing07:27
nixternali know kmon had proposed a kubuntu doc/wiki team at their meeting...and that is why i was here to help07:28
jjesseah07:28
LaserJockbah, why do that?07:28
jjessenixternal: kmon and I spoke that we would not seperate the kubuntu users from ubuntu-doc07:28
nixternalim guessing they feel left out ;)07:28
jjessewe use the same tools, the same repository, the same site, help.ubuntu.com/doc.ubuntu.com etc07:29
nixternali agree jjesse..as i think that goes against the Ubuntu meaning for one...w/o Ubuntu there would be no Kubuntu07:29
bhuvannixternal: can you elaborate ?07:29
jjessebhuvan: it goes back to a lot of the documentation/work is very ubuntu specific07:29
LaserJockyeah, because people work on what they use07:29
jjessefor example in the Official Ubuntu Book, there is only one chapter dedicated to Kubuntu (which I wrote) but the rest of the book is dedicated to ubuntu07:29
bhuvanjjesse: wont it be solved if we have enough kubuntu documenters07:30
nixternalif you look at wiki documentation/howto's and what not, they all seem to lean towards Ubuntu...of course most of these articles will also work with Kubuntu07:30
nixternali would love to get involved with some Kubuntu documentation..that is why i was trying to join the DocTeam07:30
LaserJockand there is no reason you can't07:30
jjessebhuvan: yes it would help, however most of the calls for help that have been placed there has been no response07:30
jjessenixternal and we would love to have you help out with thedocs07:31
nixternalim not a coder..and i just want to help out..plus i have done documentation previously07:31
nixternalthx jjesse07:31
bhuvanjjesse: as LaserJock say they work on what they use.07:31
jjesseif you want to help out with the dekstop guide, release notes, about kubuntu etc that is great07:31
bhuvannixternal: great07:31
jjesseor if you want to write your document that needs help that would be perfect07:31
jjessenixternal: just add it to the spec :)07:31
nixternalspec link that you are referring to07:32
nixternalor link spec rather ;)07:32
jjessehttp://wiki.kubuntu.org/KubuntuDocs/Edgy07:32
bhuvanimo, if we remove gnome/kde everything is just one. so, the help system is available for all those applications in ubuntu/kubuntu form. so, why do we have hard feeling (if we have one)?07:32
nixternalarg..lol...looking at it already07:32
nixternali can come up with something im sure07:32
jjessenixternal: that is awesome07:33
nixternali can work with kmon and Riddell to see what they may like to see07:33
jjessenixternal: can you CC me on emails to them :)07:33
nixternalsure can07:33
bhuvannixternal: and may be to ubuntu-doc mailing list? 07:33
jjesseyeah07:33
nixternalno problem07:33
jjesseinstead of cc me just cc ubuntu-doc :)07:34
nixternalgot it07:34
LaserJockjjesse: ok, so is this switching to windows doc Kubuntu specific? could we turn it into a generic doc?07:34
jjesseLaserJock: well i think it might become like the DesktopGuide07:34
nixternalswitching to windows?  is that backwards?07:34
jjesseone for Ubuntu and one for Kubuntu07:34
nixternaldon't we want switching from windows ;)07:34
jjessejust because there are a lot of things that are different07:34
jjesseand it should be switching from windows07:35
nixternalhehe07:35
LaserJocklol, sorry07:35
nixternali think that would have been a bad marketing decision ;D07:35
LaserJockhehe07:35
jjesseanyways the wiki page SwitchingFrom Windows is quite big and there is a lot ubuntu specific stuff on it07:36
jjessei think someone, and maybe nixternal would like to create it :)  should take a large portion of it and kubuntuize it07:37
nixternali can take a look and come up with some Kubuntu ideas for it if you would like07:37
bhuvanimo, it should be more generic (applicable to both ubuntu/kubuntu) than being specific to kubuntu :)07:37
LaserJockyeah, I just wondered if it was DE specifc enough to need 2 docs07:37
bhuvan2 docs =  2 identical docs07:37
jjessehttps://wiki.kubuntu.org/SwitchingFromWindows07:38
bhuvanimo, in long run it may be difficult to maintain and keep them up-to-date and sync with each other07:38
jjesseagreed bhuvan, i think that is the problem we ran into w/ the desktop guide07:38
nixternalmaybe a default page "SwitchingFromWindows" with other pages linked to Ubuntu > Kubuntu  and so forth07:38
nixternalor like bhuvan said, make it generic07:38
jjesseif we create the document, we can get it linked off of help.ubuntu.com and also get included in the DesktopCD07:39
=== j_ack [n=nico@p508D8C93.dip0.t-ipconnect.de] has joined #ubuntu-meeting
LaserJockwhat I'd like to see is something where you write it as generically as possible and then have little notes or something where it is DE specifc07:39
nixternalalthough, it could be generic...alot of it actually...with some differences when it comes to graphical software installations via synaptics or ept07:39
bhuvanjjesse, imo we should have one document as we currently have (server guide, packaging guide). we can feel free to ship two copies seperately, may be one in ubuntu-docs and one in kubuntu-docs07:39
jjesseok, i'll start a thread on the mailing list where we can discuss in further detail07:40
LaserJockbhuvan: yes, ideally, the point is if we can get the info to the user we need doing it generically07:40
bhuvanjjesse: ok07:40
LaserJocksome things do depend on the DE07:40
bhuvanyeah07:41
bhuvanok, now, shall we move to next topic ?07:41
LaserJockI have one doc07:41
bhuvanyeah?07:41
LaserJockI didn't put it on the agenda07:41
jjessethe packaging guide?07:41
LaserJockand I don't know that I'll be doing it in edgy07:41
LaserJockhttps://wiki.ubuntu.com/UbuntuScriptingDoc07:41
bhuvango ahead07:42
LaserJockjjesse: now, that one isn't new anymore ;-)07:42
jjessegrin07:42
LaserJockmy idea was to have a simple intro to Python/Bash scripting and with cookbook style code snippets (contributed by the community) for every day user things07:42
nixternali like that07:43
LaserJockit is very brain dump at this point, but here is my rationale07:43
jjesseLaserJock: that sounds pretty cool07:43
LaserJock1) Ubuntu has been called a Python-centric distro07:43
LaserJockbut we really don't have any docs that show it (we do ship Dive into Python)07:44
=== bhuvan is loving python these days
=== nixternal is learning it ;)
LaserJock2) Even fairly new users need to do automated tasks07:44
nixternali can print 5+6 to the screen ;)07:44
LaserJockrename .mpg/.ogg based on id tags07:44
LaserJock3) It give a change for kids (and adults of course :-) ) to get into programming in an easy way07:45
jjesseLaserJock +1 for me07:45
jjessei'd go ahead and create it07:45
LaserJockso it's more of an Python/Bash evangelizing doc than a Course in Computer Science ;-)07:46
nixternal+1 here big time07:46
nixternalgreat spec imho07:46
bhuvanLaserJock, but how well it is useful while tons of documents are already available for python07:46
Specindeed07:46
LaserJockbhuvan: because it is Python on Ubuntu, and it isn't a Python Reference/Tutuorial07:46
nixternali could really use something like that considering im just now getting into the programming part of computers after stopping many many years ago...07:46
bhuvanLaserJock: can you show an example?07:47
LaserJockbhuvan: the one I gave was renaming .mp3s based on id tags07:48
LaserJockit takes about 10 lines in python07:48
bhuvanok, so are we going to include the script and demonstrate the user using a document?07:48
LaserJockyeah07:48
LaserJockthe idea would be similar to Python Cookbook07:48
LaserJockbut more user focused07:48
bhuvanLaserJock, great idea. but do you think other distro docteam prepare these kind of documents?07:49
LaserJockso get little scripts from people (we can have a "call for scripts" on the forums, ML, etc.) and then explain Python by explaining what the script does07:49
LaserJockbhuvan: I don't really know07:49
LaserJockbhuvan: I doubt it07:49
bhuvanLaserJock: good we didnt choose perl and we may end up shipping the dependent module along with the document ! 07:50
LaserJockjust getting people interested in Python by showing, "heah, you don't have to write a 10,000 line GUI app to use this"07:51
LaserJockmy main point is, Python is great, and we ship lots of Python stuff, let's show users how to use it a bit, get them interested07:51
bhuvanLaserJock: definitely we have point to prove. may be, we can list of couple of frequent programming needs in day to day user/developer need and document it in a form to reach them effectively07:52
bhuvanLaserJock, i'm not fully inclined including as part of document. But it is worth discussing with others through mailing list. so please ...07:53
jjessewhat is the next topic?07:53
nixternalseems as if the next topic is mdke specific concerning his "Turn the help system upsidedown and make it more useful" proposal07:53
LaserJockyeah, this is sweet07:53
bhuvannixternal, yeah thanks07:53
bhuvani have two questions from that document. 1) what does he refer as help system (d.u.c or h.u.c or w.u.c) 2) what does he refer as upstream document07:54
LaserJock1) yelp or khelpcenter? 2) gnome/kde07:55
jjessei think he referes to help.ubuntu.com07:55
bhuvan1) +1 jjesse07:55
nixternalmaybe we should hold this to the end just in case he makes it home and comes in here...or hold it off until we can speak with him07:55
DonSc"a possible way to go might be to bin the upstream categorisation that currently forms the front page of the help system"07:55
LaserJockwhat he's talking about it taking gnome/kde doc and melding them with our docs07:56
jjessei wish he wa here :)07:56
LaserJockand then we have a listing (like he has) of areas a user would want to go to07:56
DonScI read it as reforming the Yelp front page (FWIW)07:57
LaserJockyes07:57
bhuvanDonSc: me too come to that conclusion after reading point 1 in advantages section07:57
LaserJockI think the idea is to move away from doc specific documentation07:57
LaserJocklike you click on Packaging Guide or Desktop Guide07:57
jjesseexplain doc specific documentation?07:58
bhuvaninfact i never use 2nd half 07:58
DonSc"Project Mallard"!!!!1111!!one1!!!(tm)07:58
LaserJockso the documentation is centered around those areas07:58
LaserJockso I don't write the Packaging Guide so much as add to the "Contributing to Ubuntu" section07:59
jjesseintersting07:59
bhuvanif we include those new sections, where does the existing ones go?07:59
LaserJock"Using your desktop" would have stuff from DG but also Gnome/KDE docs, Offical book, etc08:00
LaserJockbhuvan: away!08:00
jjesseand how do we maintain it in svn?08:00
LaserJockhehe, that's a good question :-)08:00
bhuvanLaserJock: :) i'm unsure if he mean it :) :)08:00
LaserJockyes08:00
nixternalwrong button?08:01
bhuvanmay be08:01
LaserJockbhuvan: he wan't the yelp home page to look like what he had08:01
nixternalhehe08:01
bhuvanLaserJock: yeah, but where do we place existing ones and how do we draw line between new and existing ones?08:01
LaserJockthere won't be existing ones08:02
LaserJockthat's the point08:02
DonSclot of work08:02
LaserJockyelp will *only* have those items08:02
bhuvanLaserJock, each of those topics are excellent and need to be placed but where and at the cost of what?08:02
LaserJockthose items are the help system08:03
DonScReally, really, look into Mallard08:03
LaserJockthe cost is a heck of a lot of work08:03
LaserJockDonSc: I think that might be in the plan08:03
LaserJocknot sure though08:03
bhuvanLaserJock, not just that at the cost of existing ones08:03
DonScBasically along the same lines08:03
LaserJockbhuvan: no, they are a part of the new system08:03
bhuvanLaserJock: you mean they will be part of new system, but they wont be placed in front page?08:04
LaserJockbah, no08:04
LaserJockit won't say 08:04
LaserJock"Desktop Guide"08:05
LaserJockthe desktop guide content will be in the relevent areas08:05
bhuvanoh ok08:05
LaserJockalong with the upstream content08:05
LaserJockOffical book sections, etc.08:05
LaserJocksee the italicized stuff next to the items08:06
bhuvanso, it will be like segregating existing ones and forming these documents. once we develop all these documents, we may remove existing ones?08:06
LaserJockwell, I don't know that there an plan, but I would think the existing doc contents get swallowed up into the new help system08:07
LaserJock*is a plan08:07
LaserJockbasically, the problem is that the current yelp (and I think KDE has a similar problem) is a mess08:08
LaserJockusers don't know where to go08:08
bhuvanok08:08
DonScLaserJock: we're working on a new TOC for 2.1608:08
LaserJockthey never get to things they should, a lot of that is because we don't integrate into the upstream docs08:08
DonScAs a stopgap until Mallard arives08:08
LaserJockDonSc: ah, interesting08:08
=== bhuvan have added UbuntuScriptingDoc to agenda
LaserJockbhuvan: hehe, thanks08:09
LaserJockfor instance, Dive into Python08:09
DonScNeed to look into new categories though08:09
=== jjesse [n=jjesse@64.186.55.234] has joined #ubuntu-meeting
nixternalwb jjesse08:09
jjessesorry needed to restart08:09
nixternalhehe08:09
jjessevmware locked on me08:09
bhuvanLaserJock: what's your opinion about this proposal?08:10
bhuvanand jjesse: your opinion?08:10
LaserJockmdke's?08:10
jjessedon't have one right now, but i like the way things are setup right now :)08:11
bhuvanif we go ahead with this plan, how do we cater kubuntu needs? are we going to span that many kubuntu copies?08:11
nixternalmy opinion even though im not officially a member > i don't know about turning it upside down, however making it more useful is good, but making the entire system EASIER for a beginner is the biggest approvement I think needed08:11
nixternalimprovement08:12
jjesseagreed with bhuvan08:12
bhuvannixternal: to give your opinion, you need not be a member. so feel free. you are doing good08:12
nixternalwhew..thx ;)08:12
LaserJockmy opinion is this, I think the idea is great and we need to head in that direction, but it will take a lot of hard work and *really* good communication with upstreams, etc.08:12
LaserJockso if we can do it, wonderful08:13
nixternali see where bhuvan is coming from...  you would need 4 introductions for instance > Ubuntu / Kubuntu / Edubuntu / Xubuntu and more when new distro's come available08:13
jjessesupported instances08:13
LaserJocknixternal: each of those ships there own -docs anyway08:13
nixternaltrue08:13
bhuvanLaserJock: not yet i guess08:14
LaserJocknot yet what?08:14
bhuvani guess, each of those distro dont ship theire own -docs right now08:14
jjessejust kubuntu-docs and ubuntu-docs08:15
jjesseso far08:15
bhuvanjjesse: yes08:15
bhuvanso as mdke stated in line 2, we should do something adventurous this release. in that line it's an excellent move08:15
LaserJockbhuvan: yes they do08:16
LaserJockjjesse: no08:16
bhuvanLaserJock: is it? where do you see?08:16
LaserJockedubuntu and xubuntu shipped their own for Dapper, Edubuntu I'm sure of08:16
LaserJockyeah, they are both there08:17
LaserJockall the derivatives ship -docs08:17
bhuvanLaserJock: yeah i see relevant launchpad projects08:18
LaserJockanyway08:18
bhuvanhttps://launchpad.net/distros/ubuntu/dapper/+source/xubuntu-docs08:18
bhuvanfine08:18
LaserJockI believe users are not using the help systems effectively08:18
bhuvanso, atleast we conclude we can move forward in this direction. am i right?08:18
LaserJockheck, I'm not even using them effectavly08:18
jjessebhuvan: as long as we take into account the different distros08:19
LaserJockbhuvan: well, there are a lot of other issues, translations, how to actually merge upstream, etc.08:19
bhuvanjjesse: it has to be discussed08:19
bhuvanLaserJock: it's the path right. so, we must take care08:19
LaserJockI do think it is the right path08:20
bhuvansee the last point. 'Some hard work required' :)08:20
LaserJockthe user shouldn't have to figure out what is Ubuntu and what is Upstream08:20
LaserJockthey should just think "What do I want help about" and that's it08:20
nixternal+1 ^^08:20
jjessei would be intersted in further discussion08:21
bhuvananyhow, we still have two questions unanswered: 1) action plan and what will be the status of existing ones and how it will be organised in svn 2) for other distros08:21
LaserJockexisting docs are turned into the new ones08:21
LaserJockwe might have to ditch svn I don't know08:21
bhuvanLaserJock: ok08:21
bhuvanditch svn?08:22
=== bhuvan is from collabnet -- official svn sponsor :)
LaserJockwell, it could be that possibly it would be done via bzr08:22
LaserJockusing LP08:22
LaserJockwho know's08:23
LaserJockwe are discussing ditching source packages too so.... ;-)08:23
LaserJockit Edgy!!!08:23
LaserJockit's08:23
bhuvansource package is ubuntu-docs and i assume we will place all these new documents in that.08:23
LaserJockbhuvan: hehe, my point is that some people are talking about doing away with source packages in Ubuntu and using bzr/LP08:24
LaserJockanyway08:24
bhuvanok08:24
=== bhuvan is in half sleep. it's already 11:55 midnight
LaserJockmy point is, at this point we need to decide if it is worth pursuing actually figuring out an implementation plan08:25
bhuvanLaserJock: i meant action plan. how do we plan to generate these docs ? what are the topics they constitute ? when we will release the first snapshot and things alike08:26
bhuvanLaserJock: and importantly who is going to take the lead responsibility08:27
LaserJockwell, I think most of that is in mdke's spec08:27
bhuvanLaserJock: nope. it's just the outline and it define what to do, but it doesnt explain howto do08:27
LaserJockwell, then we need to figure that out ;-)08:27
bhuvanyeah, shall we move to next topic?08:28
LaserJockI think mdke just wanted some feedback from the team as to if he was on crack or not ;-)08:28
nixternallol08:28
bhuvanLaserJock, yeah i read it so08:28
LaserJocknext item08:28
bhuvanw.u.c to h.u.c/community migration activity08:28
LaserJockdo we know if the wiki has moved yet?08:29
bhuvannope. they have set redirecting though08:29
LaserJockyeah, I think people are busy getting ready for Paris08:29
bhuvanok08:29
bhuvanwill there be any change in wiki clean-up activity before we do this migration?08:30
LaserJockwe really need to get that done though08:30
LaserJockwell, it should be ready to go08:30
LaserJocklots of people went though and cleaned out docs they didn't want moved and added ones they did08:30
LaserJocksince it was supposed to happen like a week or two ago08:31
nixternalwe have been working on cleaning up w.u.c08:31
bhuvanyeah, we seem to keep discussing about wikiteam and special privileges for them to control certain freezed pages ...08:31
LaserJocknext item?08:32
bhuvanare we through with this?08:32
LaserJockI think so, the move hasn't happened yet08:33
bhuvanmy doubt is, if we move are we planning to implement new policies for wiki or live with existing one?08:33
nixternalany timeline on the move?08:33
LaserJocknixternal: it was supposed to happen a while ago08:33
jjesseare we still on the agenda or are there things we can move to #ubuntu-doc?08:33
LaserJockwe are on the agenda, do we need to make room for somebody else jjesse 08:33
nixternali thought so..i remember when i started working with the wiki team, corey said they were getting ready to move to h.u.c08:34
jjessenope i just don't want to get off track too far08:34
bhuvanjjesse: i guess we are not getting off track08:34
LaserJockbhuvan: yes, I expect there will be some new policies, not much of a change though08:35
bhuvani assumed when we migrate w.u.c to h.u.c/community, there might be a change in wiki policy, thus not all of the users can edit all pages08:35
bhuvanLaserJock: ok08:35
LaserJockbhuvan: only the wiki team can delete/rename and a few pages might be locked maliciousness doesn't happen 08:35
nixternalso...community docs..is the entire wiki going to be transferred, or just redirects?08:36
bhuvanmay be none of us here are unaware of that. we can discuss it in in #ubuntu-doc or mailing list so each of us may be aware of what'd happen after the move08:36
bhuvanok, next item?08:36
LaserJocknixternal: everything with CategoryDocumentation08:36
nixternalok08:37
bhuvanit's mine: Define a standard for svn (ubuntu-doc repository) commit log messages08:37
nixternalneed to work on cleaning up more of those then08:37
LaserJocknixternal: and redirects will be left on wiki.u.c08:37
LaserJockbhuvan: yes?08:38
bhuvancurrently, we committers dont follow standard when we commit the patch08:39
bhuvanit'd be great and useful if all committers follow and adhere to the standard when we record log messages08:39
LaserJockis it a problem?08:39
bhuvanin general, every open source project follow standard when it comes to commit08:39
LaserJockwell, but is it a problem for us? do you have an example?08:40
=== mdke [n=matt@ubuntu/member/mdke] has joined #ubuntu-meeting
bhuvanLaserJock: definitely yes. for a given document right now we dont know what was committed. the quality of log depend on committer08:40
LaserJockdoes the log matter much?08:40
bhuvanyes LaserJock08:41
bhuvanwhen someone wish to scan through the changes made to a document over a period of time, it makes sense08:41
LaserJockk, I guess08:41
mdkebhuvan: are you talking about the svn commit log? 08:41
bhuvanit does not require major effort to follow these simple standards, like: http://pastebin.com/71324008:41
bhuvanmdke: yes08:41
bhuvanmdke: last topic!08:41
mdkegotcha08:41
mdkeI think the quality of the logs has been quite high, myself08:42
bhuvanmdke: yeah true. everyone of us should follow08:42
mdkethey don't?08:42
bhuvanops, wrong url. it should be: http://pastebin.com/71325408:42
LaserJockI'm just not seeing a problem, not that I'm against what your saying08:43
bhuvani prefer every committer to follow this standard. so the quality of log doesnt differ among committers08:43
mdkeI think that is a bit too detailed, it might be overkill08:44
bhuvanLaserJock: ok. imo, it's good to practise these standards when we work in any open source project08:44
mdkelots of times people make big changes, and detailing everything that closely would take some time08:44
bhuvanmdke: ok, i guess it is required in long run. we can scan through the log messages and spell the history of document08:45
LaserJockI don't know, I just try to explain what I did, if people really care they can check out the diff or -commits08:45
bhuvanmdke: it can be comma seperated. for example if we add installation section for numerous sections, just include the section name seperated by comma08:45
bhuvanLaserJock: to understand what has been changed, it's wise to have detailed log message than expecting the user to go through diff or -commits08:46
LaserJockwho's the user?08:46
LaserJockI mean does anybody really care?08:47
bhuvandocument maintainers08:47
bhuvanif someone joins our team in future and if he wish to see the history of document, log messages play vital role08:47
LaserJockI'm not trying to bash the idea, it just seems a little overkill for us08:47
jjesseagreed08:47
bhuvanjjesse: agreed with whom :) :)08:48
jjesseLaserJock08:48
bhuvanyeah ok08:48
LaserJockI'm pretty bad a commit/change logs but I can try to get better08:48
mdkeyes, I think it's a bit overkill. However we can make an effort to give a good explanation of what is done in commits08:49
bhuvanok. let me assume it's -1 :)08:49
mdkeI'm not -1, I just think your paste was a little too much effort08:50
bhuvanmdke: ok08:50
LaserJockbhuvan: what I would like to see is a good example in the style guide (if it doesn't have one already)08:50
mdkegood idea08:51
bhuvanLaserJock: so you dont want it as mandatory. but we can let the committer take a call?08:51
LaserJock"best practices"08:51
bhuvanok, sounds good08:51
LaserJockand pehaps have a couple "essential elements of a good commit log"08:51
bhuvanyeah ok08:52
LaserJocklike if you commit a patch from somebody else make sure to mention who they are ;-)08:52
bhuvanyeah, we already do that08:52
bhuvanfine, i guess that's it for the day. we have discussed almost 2hrs!08:53
bhuvani guess, it's one of the productive meeting we had :)08:53
LaserJockyes08:53
mdkenice08:53
LaserJockit's because Matthew and Corey didn't show ;-)08:53
bhuvanthanks to everybody, LaserJock, jjesse & nixternal08:53
=== mdke nods
bhuvanha ha ha08:54
bhuvanand Madpilot :)08:54
LaserJockDoc Team meeting ends here ----------08:54
=== bhuvan [n=bhuvan@ubuntu/member/bhuvan] has left #ubuntu-meeting []
=== jjesse [n=jjesse@64.186.55.234] has left #ubuntu-meeting []
=== LaserJock [n=mantha@ubuntu/member/laserjock] has left #ubuntu-meeting []
=== DonSc [n=don@82-41-205-39.cable.ubr11.edin.blueyonder.co.uk] has left #ubuntu-meeting ["Ex-Chat"]
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== mdke [n=matt@ubuntu/member/mdke] has left #ubuntu-meeting ["goodbye!"]
=== jarufe [n=jarufe@200.104.140.155] has joined #ubuntu-meeting
=== ogra__ [n=ogra@p5089E3ED.dip.t-dialin.net] has joined #ubuntu-meeting
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-meeting
=== ogra_ [n=ogra@p5089E3ED.dip.t-dialin.net] has joined #ubuntu-meeting
=== Spec[x] [n=dragonco@charon.devis.com] has joined #ubuntu-meeting
=== sebas [n=sebas@belphegor.deadlysins.nl] has joined #ubuntu-meeting
=== Ubugtu [n=bugbot@ubuntu/bot/ubugtu] has joined #ubuntu-meeting
=== j_ack [n=nico@p508D8C93.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== sirkelley [n=sirkelle@ip68-12-236-180.ok.ok.cox.net] has joined #ubuntu-meeting
=== kjcole [n=kjcole@ubuntu/member/kjcole] has joined #ubuntu-meeting
=== Hirion [n=hirion@draugr.de] has left #ubuntu-meeting []
=== lukketto [n=lukketto@host40-190.pool877.interbusiness.it] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== Rinchen [n=Rinchen@unaffiliated/rescue] has joined #ubuntu-meeting

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