=== finalbeta [n=finalbet@d5152A68A.access.telenet.be] has joined #ubuntu-meeting === ToonArmy [n=chris@144.173.52.120] has joined #ubuntu-meeting === Yawner [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-meeting === dflake [n=dflake@64.0.192.73] has joined #ubuntu-meeting === ToonArmy [n=chris@Lafrowda-12.ex.ac.uk] has joined #ubuntu-meeting [12:58] tsmithe, liar :p === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === lupine_85 [n=lupine@nick.lupine.me.uk] has left #ubuntu-meeting ["Why] === lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #ubuntu-meeting === doko [n=doko@dslb-088-073-082-079.pools.arcor-ip.net] has joined #ubuntu-meeting === j_ack [n=rudi@p508D8149.dip0.t-ipconnect.de] has joined #ubuntu-meeting === mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting === freeflying [i=flyingfr@205.196.222.12] has joined #ubuntu-meeting === tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-meeting === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting === fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting === j_ack [n=rudi@p508D8149.dip0.t-ipconnect.de] has joined #ubuntu-meeting === Jester45 [n=Jester45@d8-241.rt-bras.wnvl.centurytel.net] has joined #ubuntu-meeting === Jester45 [n=Jester45@d8-241.rt-bras.wnvl.centurytel.net] has left #ubuntu-meeting [] === freeflying [i=flyingfr@gobstopper.dreamhost.com] has joined #ubuntu-meeting === raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting === mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting === ash211 [n=andrew@user-1121oil.dialup.mindspring.com] has joined #ubuntu-meeting === j_ack [n=rudi@p508D8149.dip0.t-ipconnect.de] has joined #ubuntu-meeting === mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting === Starting logfile irclogs/ubuntu-meeting.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 17 Jan 20:00 UTC: Edubuntu | 18 Jan 08:00 UTC: Ubuntu Development Team | 20 Jan 15:00 UTC: Xubuntu | 24 Jan 12:00 UTC: Edubuntu | 25 Jan 16:00 UTC: Ubuntu Development Team | 30 Jan 20:00 UTC: Technical Board === Topic (#ubuntu-meeting): set by Ubugtu at Tue Jan 16 23:30:05 2007 === datten_ [n=datten@xdsl-81-173-191-252.netcologne.de] has joined #ubuntu-meeting === robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting === alvonsius [n=alvonsiu@222.124.24.91] has joined #ubuntu-meeting === alvonsius [n=alvonsiu@222.124.24.91] has left #ubuntu-meeting ["Konversation] === raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting === Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting === imtheface [n=abns@ubuntu/member/imtheface] has joined #ubuntu-meeting === Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting === alvonsius [n=alvonsiu@222.124.24.91] has joined #ubuntu-meeting === mvo [n=egon@p54A6721C.dip.t-dialin.net] has joined #ubuntu-meeting === phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting === dennda [n=dennda@p54AFF91C.dip.t-dialin.net] has joined #ubuntu-meeting === phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting === sfllaw [i=sfllaw@debian/developer/coleSLAW] has joined #ubuntu-meeting === dholbach [n=daniel@i59F708F2.versanet.de] has joined #ubuntu-meeting === MatthewV [n=MatthewV@202.183.115.190] has joined #ubuntu-meeting === finalbeta [n=finalbet@d5152A68A.access.telenet.be] has joined #ubuntu-meeting === mvo_ [n=egon@p54A6674C.dip.t-dialin.net] has joined #ubuntu-meeting === juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting === dennda [n=dennda@p54AFF91C.dip.t-dialin.net] has joined #ubuntu-meeting === fanch [n=fanch@84.4.46.125] has joined #ubuntu-meeting === fanch [n=fanch@84.4.46.125] has joined #ubuntu-meeting === Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting === datten [n=datten@xdsl-81-173-191-252.netcologne.de] has left #ubuntu-meeting [] === Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting === dennda_ [n=dennda@p54AFF91C.dip.t-dialin.net] has joined #ubuntu-meeting === fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting === Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting [12:35] @schedule [12:35] Schedule for Etc/UTC: 17 Jan 20:00: Edubuntu | 18 Jan 08:00: Ubuntu Development Team | 20 Jan 15:00: Xubuntu | 24 Jan 12:00: Edubuntu | 25 Jan 16:00: Ubuntu Development Team | 30 Jan 20:00: Technical Board [12:35] excellen [12:35] t [12:37] @schedule sydney [12:37] Schedule for Australia/Sydney: 18 Jan 07:00: Edubuntu | 18 Jan 19:00: Ubuntu Development Team | 21 Jan 02:00: Xubuntu | 24 Jan 23:00: Edubuntu | 26 Jan 03:00: Ubuntu Development Team | 31 Jan 07:00: Technical Board === Hobbsee wonders how they're going to have a ubuntu development meeting when there are a whole lot of devs at linux conf au, having dinner with au people at about that time... === licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting === freeflying [i=flyingfr@gobstopper.dreamhost.com] has joined #ubuntu-meeting === juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting === fernando__ [n=fernando@189.0.132.137] has joined #ubuntu-meeting === freeflying_ [i=flyingfr@gobstopper.dreamhost.com] has joined #ubuntu-meeting === fanch [n=fanch@84.4.46.125] has joined #ubuntu-meeting === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === rodarvus [n=rodarvus@ubuntu/member/rodarvus] has joined #ubuntu-meeting [02:24] @schedule [02:24] Schedule for Etc/UTC: 17 Jan 20:00: Edubuntu | 18 Jan 08:00: Ubuntu Development Team | 20 Jan 15:00: Xubuntu | 24 Jan 12:00: Edubuntu | 25 Jan 16:00: Ubuntu Development Team | 30 Jan 20:00: Technical Board === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting === dsas [n=dean@cpc3-stok6-0-0-cust253.bagu.cable.ntl.com] has joined #ubuntu-meeting === lotusleaf [n=lotuslea@kernel-panic/member/carne.asada.burrito] has joined #ubuntu-meeting [02:49] "looking through a demon's eye" "We're gonna spy on God Find out if he really is" === lotusleaf [n=lotuslea@kernel-panic/member/carne.asada.burrito] has left #ubuntu-meeting ["trombone"] === phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === pipedream [n=pipedrea@www.aims.ac.za] has joined #ubuntu-meeting === ogra_ [n=ogra@p548AF27A.dip.t-dialin.net] has joined #ubuntu-meeting === dennda [n=dennda@p57A80973.dip0.t-ipconnect.de] has joined #ubuntu-meeting === j_ack [n=rudi@p508DB9AF.dip0.t-ipconnect.de] has joined #ubuntu-meeting === Huahua [n=hua_@122.0.231.80] has joined #ubuntu-meeting === lmanul [n=manu@dan75-4-82-239-58-38.fbx.proxad.net] has joined #ubuntu-meeting === dsas [n=dean@cpc3-stok6-0-0-cust253.bagu.cable.ntl.com] has joined #ubuntu-meeting === Hawkwind [n=SoS@ulteo/community-leader/Hawkwind] has left #Ubuntu-Meeting ["It's] === cbx33 [n=pete@ubuntu/member/cbx33] has joined #ubuntu-meeting === Ppjet6 [n=ppjet6@81.56.130.254] has joined #ubuntu-meeting === tomsku [n=tomsku@dsl-tregw3-fe4ddf00-223.dhcp.inet.fi] has joined #ubuntu-meeting === phanatic_ [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting === Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting === ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 17 Jan 20:00 UTC: Edubuntu | 18 Jan 21:00 UTC: Ubuntu Development Team | 20 Jan 15:00 UTC: Xubuntu | 24 Jan 12:00 UTC: Edubuntu | 25 Jan 16:00 UTC: Ubuntu Development Team | 30 Jan 20:00 UTC: Technical Board === Owdgit [n=ron@88-110-14-154.dynamic.dsl.as9105.com] has joined #ubuntu-meeting === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === mr_pouit [n=mr_pouit@LAubervilliers-151-12-73-187.w193-252.abo.wanadoo.fr] has joined #ubuntu-meeting === Adri2000 [n=adri2000@ubuntu/member/adri2000] has joined #ubuntu-meeting === Czubek [n=Damian@azt234.neoplus.adsl.tpnet.pl] has joined #ubuntu-meeting === nixternal_ [n=nixterna@ubuntu/member/nixternal] has joined #ubuntu-meeting === cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting === freefal [n=freefal@129.170.165.81] has joined #ubuntu-meeting [08:00] @schedule [08:00] Schedule for Etc/UTC: 17 Jan 20:00: Edubuntu | 18 Jan 21:00: Ubuntu Development Team | 20 Jan 15:00: Xubuntu | 24 Jan 12:00: Edubuntu | 25 Jan 16:00: Ubuntu Development Team | 30 Jan 20:00: Technical Board === slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting === slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting === mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting === sbalneav [n=sbalneav@mail.legalaid.mb.ca] has joined #ubuntu-meeting === dholbach_ [n=daniel@i59F76A91.versanet.de] has joined #ubuntu-meeting === ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: Edubuntu | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 Jan 21:00 UTC: Ubuntu Development Team | 20 Jan 15:00 UTC: Xubuntu | 24 Jan 12:00 UTC: Edubuntu | 25 Jan 16:00 UTC: Ubuntu Development Team | 30 Jan 20:00 UTC: Technical Board === willvdl [n=will@196.207.32.235] has joined #ubuntu-meeting [09:00] @schedule [09:00] Schedule for Etc/UTC: Current meeting: Edubuntu | 18 Jan 21:00: Ubuntu Development Team | 20 Jan 15:00: Xubuntu | 24 Jan 12:00: Edubuntu | 25 Jan 16:00: Ubuntu Development Team | 30 Jan 20:00: Technical Board === pips1 [n=philipp@55-158.1-85.cust.bluewin.ch] has joined #ubuntu-meeting [09:01] hey pips1 [09:01] long time no see [09:01] hey highvoltage [09:01] hey pips1! [09:01] :-) === pips1 looks around [09:02] right, who's present? [09:02] Shall we get cracking? [09:02] sure [09:02] RichEd is in Australia, right? [09:02] Riched is in Australia at LCA [09:02] snap [09:02] and ogra can't make it tonight [09:03] ic [09:03] hi [09:03] rodarvus ? [09:03] sbalneav ? [09:03] Hello! [09:03] hey [09:03] hi!! [09:03] Present [09:04] cbx33 ? === sbalneav holds hand up [09:04] rodarvus is around I think [09:05] willvdl: will you pace us through the agenda? [09:05] Well, let's get started anyway [09:05] === TECHNICAL === [09:05] If ogra were here, I'm sure he'd ask for testers... [09:06] not sure how much we can cover in tech [09:06] hi [09:06] I'll be doing some testing of thin client sound this weekend. [09:06] ola [09:06] nice one sbalneav [09:06] great, ogra mentioned sound architecture last week === cbx33 has an update on LTCM(SCP) === willvdl hands cbx33 the conch shell [09:07] oooh [09:07] well..... [09:07] is this thing on [09:07] ... [09:07] I have started the LTCM spec [09:07] it's now successfully broken up into front end and back end [09:07] which is awesome [09:07] aha. saw those discussions [09:07] today I worked for a little while on the tiled vnc feature that everyone wanted [09:08] and I actually got it working [09:08] borrowed some code from somewhere else [09:08] but it's all GPL so we're good [09:08] sweet [09:08] that's me done [09:08] anyone who wants to test it for me [09:08] shout [09:09] what does the "split" mean as such? [09:09] well [09:09] it will allow a KDE developer to write a kde front end for LTCM [09:09] since they can just import the backend module and all the hard stuff is done for them [09:09] ah. with clear api etc [09:09] indeed [09:10] and the backend is actually tiny === j_ack [n=rudi@p508D8BAA.dip0.t-ipconnect.de] has joined #ubuntu-meeting [09:10] the gui takes up most code === pips1 is trying to figure out the acronym... Linux Terminal Control Manager? Erm... [09:10] cbx33: what is LTCM? [09:10] LTSP Thin Client Manager [09:10] thin client manager [09:10] snap [09:11] damn you win ;) [09:11] however for now the vnc stuff will only be in the gnome version [09:11] looking forward to seeing it in action [09:11] as a) no one has stepped up to write a kde version yet and b) the code I hacked up was from a gnome app and I'm not sure how well it can be split [09:12] so LTCM (LTSP Thin Client Manager) is now the official new name for SCP (Student Control Panel)? [09:12] yes [09:12] oh and I spotted a bug in SCP which should be fixed soon [09:12] right [09:13] I can't imagine you've had much time for the MOTD thingy? [09:13] unfortunately no [09:13] not yet [09:13] It's still a possibility [09:13] infact it's SOOO simple to implement [09:14] shall we move on? [09:14] Is anyone present expecting to be able to test Herd 2, 3, ... (besides sbalneav)? [09:14] sure [09:14] unfortunately I won't have time [09:15] let's move on.. [09:15] let's skip to Artwork if no-one minds? [09:15] sure [09:15] Lisa is sorry she can't attend this evening [09:15] === ARTWORK === [09:15] ^^^ makes logs easier to edit [09:15] she hasnt had a great deal of time lately....been very very busy with paid work [09:16] but she is still working hard...and really really needs your feedback [09:16] Canonical is going to employ an ubuntu artist [09:16] for edubuntu too? [09:16] need to see how that works out [09:17] ok [09:17] cbx33, feedback on templates, pallettes etc? [09:17] I think shes talking about the mock wallpaper she did a while back [09:17] but [09:17] I think they'll be some more before not too long to comment on [09:17] also [09:17] if anyeone knows of any budding artist [09:17] please get them involved [09:18] let's tap the Ubuntu Artwork channel [09:18] make a formal "call for contributions"? [09:19] well we have done that in the past [09:19] I'll get lisa to mail them tonight [09:19] Does the Artwork Team have its own introduction/welcome page somewhere? [09:19] sweet. just good to voice ourselves I guess [09:19] yes [09:19] EdubuntuArtwork [09:19] people just don't seem keen to help out Edubuntu much [09:20] perhaps we need to make it easier for them [09:20] somehow... [09:20] willvdl: i agree with you [09:20] me too [09:20] I just don;t know how [09:21] I'm don't hang around the artwork channels much or browse the contributions but there are a lot of folk contributing to Ubuntu art [09:21] yeh [09:21] ok I'll draft up an email... [09:21] if we have representation in those channels then well get stuff I'm sure [09:21] ok if I run it by you willvdl ? [09:21] sure === pips1 glances at https://wiki.ubuntu.com/Artwork === LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-meeting [09:22] Is there anyway we can merge our Artowrk "space" with the ubuntu artwork "space"? [09:22] hmmm [09:22] possibly I suppose [09:22] hi LaserJock [09:23] quote: feisty will be designed by cliff [09:23] hi everybody [09:23] hey LaserJock [09:23] as with dapper. how did that affect edubuntu back then? [09:23] uggg [09:24] dapper was a tough one [09:24] willvdl: armed revolt? :-) [09:24] "Feisty artwork will be design by Cliff -- the fellow who designed the Dapper look. Do not expect to be able to contribute until sabdfl releases the official work. It is closed design involving Cliff and sabdfl only." [09:24] LaseJock, dodgy prawn? [09:24] ogra and janew weren't very happy that they didn't have any say in the artwork [09:24] does that include edubuntu do we know? [09:24] did edubuntu do its own artwork in dapper? [09:24] willvdl: hired artist [09:25] for backgrounds, splash and icons? [09:25] willvdl: except for icons [09:25] we had a wallpaper in main though didn't we [09:25] "Currently we are attempting to collect all art related people under the ubuntu-art team on Launchpad. This has been quite successful thus far, and therefore one should consider the ubuntu-art team as a good starting point for work. For links to legacy pages, please see the following links: EdubuntuArtwork ..." [09:25] legacy pages [09:26] hmm [09:26] sounds old [09:26] is there a rationale behind not letting the community do the artwork? [09:26] it seems to go back and forth, kinda annoying [09:26] yeah [09:26] http://art.ubuntu.com/main.php [09:27] anyway, it is still very valuable to have contributions regardless of closed design [09:27] well for a start we have more than just one wallpaper [09:27] oh, I didn't know they had revanped the art.u.c site [09:27] LaserJock: I don't think there's anythin wrong with Canonical hiring people to improve Ubuntu's artwork... but... \ [09:27] *revamped [09:27] highvoltage, I agree [09:27] LaserJock: if there are better community submisions, it should be considered too, imho [09:28] maybe for get someone behind it to drive it in right direction [09:28] highvoltage: but they won't consider them if they are already contracting people, it would be a waste of money [09:28] highvoltage, LaserJock : that is how I would expect things to be run [09:28] so will that be for Edubuntu too.....? [09:28] can we confirm this [09:29] just like Canonical hires kernel developers [09:29] cbx33: by ubuntu I mean *buntu [09:29] cbx33, I will check [09:29] ah ok [09:29] willvdl: it's a bit different, IMO [09:29] LaserJock, only if handled badly [09:29] which it seems to have been historically [09:29] artwork that is [09:29] basically how much should we push the artwork in Edubuntu [09:30] and how much is going to be forced upon us [09:30] the Canonical hired kernel guys work in the open with patches, ML etc. [09:30] generally we get to see the artwork when it's released [09:30] My opinion is to push contributions anyway [09:30] what we build now can always be used later or even make it in if the process allows [09:31] plus we keep the community active [09:31] willvdl: but it's not very encouraging for designers, if the aren't any clear known "rules" [09:31] exactl [09:31] y [09:31] clear procedures... so you know what to expect and what not to expect [09:31] it's pretty upsetting infact [09:31] agreed, but note that art.u.c gets contributions regardless [09:31] when someone has worked really hard .... [09:31] willvdl, it's a little different [09:32] especially when the dev community all say the want a community artwork and are ignored [09:32] *they [09:32] because edubuntu last relase had 2 contributors [09:32] so it makes it a little more personal [09:32] I hear you guys and agree [09:32] I'm just saying we should not stop contributing [09:33] no, but can you see how.....in a big community like ubuntu it just means a drop in contributions [09:33] but that with a tiny team....2 people that can make or break the contributions full stop [09:34] yeah. === pips1 reads the introduction on http://art.ubuntu.com/main.php [09:34] OK, PoA: [09:34] especially when the community isn't consulted at all [09:34] cbx33: good point [09:34] will check on procedures, policies etc internally [09:35] also.... [09:35] and, seperate issue, try and integrate more with artwork team for leverage? [09:35] ok, willvdl to report back at the next meeting :-) [09:35] just not sure immediately how to achieve the latter === Joe5656 [n=JoeCormi@mctnnbsa28w-142167096017.pppoe-dynamic.nb.aliant.net] has joined #ubuntu-meeting [09:36] There's definately enough concern on the issue to raise it [09:37] how relevant is https://blueprints.launchpad.net/~ubuntu-art ? [09:37] ... to edubuntu artwork, I mean [09:38] pips1: fairly [09:38] pips1: edubuntu inherits some of the ubuntu artwork stuff [09:38] pips1: like firefox themes, etx [09:38] *etc [09:38] any *buntu artwork work should include/be relevant to edubuntu IMHO [09:38] pips1: and the edubuntu gtk theme is normally derived from whatever theme is in use on edubuntu [09:38] I mean, Ubuntu === highvoltage really needs some sleep [09:39] nn highvoltage [09:39] ;) [09:39] cbx33: heh. I'll hold out a bit :) [09:40] Okie, lets discuss further on ML and I'll try find out what I can [09:40] ok [09:41] In that case, it might be a good idea to link to that launchpad specifications page from the artwork wiki page, so the community artists (i.e. AliasVegas) know what is done for ubuntu... === Lure [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting [09:41] from EdubuntuArtwork? [09:41] yep [09:42] just a thought [09:42] what interests me is that the artwork team consider EdubuntuArt as legacy page [09:42] assuming the community is already integrated [09:42] yeh...funny that [09:42] We should fix that [09:42] i don't remember anyone talking to Lisa about it ;) [09:43] it's a perception [09:43] well things are always moving fast in ubuntu land :-) and it's hard to keep up with what is going on everywhere [09:43] :) [09:44] shall we move to docs? [09:44] ok [09:44] === Documentation === [09:45] I've been thinking about doc contributions somewhat [09:45] and have chatted to a number of folk [09:45] ok === ash211 [n=andrew@user-1121oil.dialup.mindspring.com] has joined #ubuntu-meeting [09:45] on wiki contributions vs SVN contributions [09:46] meaning wiki = open collaboration [09:46] and svn = open collaboration but large barrier [09:46] how do you folks feel? [09:47] depends on the doc, IMO === tommy [n=tommy@83.167.116.108] has joined #ubuntu-meeting [09:47] true [09:47] wiki = medium barrier too, AFAIK [09:47] if you want it stable and need to be in various formats do docbook [09:47] with svn [09:48] yip, but the svn authors can pull their info form the wiki [09:48] if the wiki is used as the "development" space [09:48] hold on, we are talking about a variety of tools and formats here... [09:48] true [09:48] docbook = format [09:49] svn = versioned repository [09:49] wiki = versioned repository with web frontend [09:49] no? [09:50] yip [09:50] also docs in svn get packaged [09:50] wiki also = format [09:50] willvdl: how do you imagine your "perfect" documentation process? [09:51] perfect? :) [09:51] well, I'm just again trying to leverage contributions [09:51] !Question How do I leave this channel? I'm not at the right channel here.... My apologies for interrupting you all! [09:51] LaserJock: ok, wiki stores the information in its own format, that's right [09:51] and was thinking back to a conversation I had with pips1 vefore the holidays [09:52] and others [09:52] being that the wiki is the easiest and most open tool and repo we have for contributions [09:53] Would something like this work?: Docs get planned and "authored" to a degree on the wiki. At logical times the SVN authors pull this info into the docbook files [09:54] well, ideally we could have a super userfriendly "frontend" tool combined with the benefits of a standard format such as docbook... [09:54] although my suggestion is contrary to using Launchpad, bug-reporting etc [09:54] how so? === pips1 isn't sure he is following willvdl [09:55] Joe5656: /leave [09:55] Thanks laser! [09:55] I'm not sure that easy contribution is always the way to go though ... [09:55] perhaps LaserJock can help me here, but LP tracks the docs (in whatever format) and contributions are made in patches, bug-reports or specs [09:55] sometimes a little barrier isn't a bad thing [09:56] well, we have an upstream product [09:56] people can file bugs against that [09:56] and we can write specs [09:56] patches are sent to the ML [09:57] perhaps we should take a step back here [09:57] and look at what docs we are needing [09:58] We need an install guide prob [09:59] release-notes & about page [10:00] and LTSP info as it forms part of our release [10:00] given the topics, and the authors, what would the best tools be? [10:03] pips1 what are your thoughts? [10:04] Sorry to interject, but is the svn repo for the handbook still on digitalredneck? [10:04] nope. moved into docteam.u.c [10:05] Do I still have commit? [10:05] Off the top of my head: About (Intro/Overview, Release Notes, Sources of further help, ...), Installation and Configuration Guide (Desktop Guide, Server Guide, plus specifically LTSP), Customisation ("Cookbook"), plus How to contribute to Edubuntu Project. [10:05] sbalneav, best check with mdke or someone [10:05] not sure [10:06] sorry guys I'm gonna have to duck out, splitting headache [10:06] pips1 the "guides": meaning the ubuntu ones or our own? [10:06] and tired [10:07] willvdl: we can probably reuse the "Ubuntu Guides", but I haven't really looked into that, so I don't really know. [10:08] I'd like to open a discussion on the handbook aim again. I think things have move along alot since it was created [10:08] well, it's also noteworthy that Ubuntu and Kubuntu are moving away from "guides" [10:09] The Desktop Guide and the Server Guide from Ubuntu are shipped with Edubuntu anyway, right? [10:09] pips1, have you looked at the Topic Based Help spec? [10:09] thinks so [10:09] LaserJock: tell us more? [10:10] right now, Edubuntu ships ubuntu-docs [10:10] yep [10:10] pips1: the doc team is going for a more topic based approach [10:10] so if we just basically created add-on topics to cover Edubuntu specifics === pips1 reads https://blueprints.launchpad.net/ubuntu/+spec/topic-based-help [10:11] we can "blend in" with the rest of Ubuntu docs [10:11] and there would be no duplication [10:11] LaserJock, this would be the domain of the Handbook right? [10:12] @schedule [10:12] Schedule for Etc/UTC: Current meeting: Edubuntu | 18 Jan 21:00: Ubuntu Development Team | 20 Jan 15:00: Xubuntu | 24 Jan 12:00: Edubuntu | 25 Jan 16:00: Ubuntu Development Team | 30 Jan 20:00: Technical Board [10:12] In the spec it says "The Ubuntu/Kubuntu documentation teams do not have the resources to implement a topic-based help system from scratch. So for now we should restrict our efforts to reorganizing the Desktop Guide and Server Guide, to make the documentation easier to navigate." [10:12] willvdl: what I'm saying is that I'm not sure that a "Handbook" fits in with the way documentation in Ubuntu and upstream are heading [10:13] it's fine for a book, or an all-inclusive PDF or something [10:13] which I think there would be a demand for [10:13] LaserJock, I chatted to Sean Wheller about that earlier [10:13] and looked at the original aim of the handbook again [10:13] but I think you could do that with the TBH approach anyway [10:13] and I think you're right in a sense [10:15] But the handbook aim was as an install/customisation/basic usage guide? [10:15] it was meant by Mario to be a book [10:15] LTSP, though, isn't something that fits well into TBH. There's a lot of pre-tech stuff, and the whole "integration into my windows network" thing's a pain. [10:15] the one-stop shop for Edubuntu [10:15] sbalneav, I thought you might say that [10:16] LaserJock, it can still be but we need TBH to "mature" first [10:16] IMHO [10:16] The problem with LTSP is, it's really a "tech" thing, and not a user thing. [10:16] sbalneav: well, I'm not sure why having a "Configuring an LTSP Server" would be a had topic [10:16] s/had/bad/ [10:17] ok, so I think the decision needs to be made there [10:17] it becomes an interesting topic to squeeze in since it depends on the specific network topology [10:17] what do you want to present in the user's help system [10:17] and what do you want to provide online [10:17] It would be a big topic. Usually TBH is supposed to be "short snapper" type help, isn't it? Or am I smoking crack again? [10:17] sbalneav: ideally yeah [10:18] sbalneav: but we have the Server Guide in there [10:18] which isn't all that non-tech [10:18] I'm good either way. [10:18] LTSP would fit into the server guide logically right? [10:18] Right. [10:18] I think you guys should take a look at the feisty docs [10:19] just to get a feel for what it's like [10:19] but, as I understand from ogra, installing it ontop of ubuntu versus out of edubuntu is slightly difference [10:19] and see if you think it could fit in well there [10:19] *different [10:19] willvdl: Ubuntu users wouldn't see it === mr_pouit [n=mrpouit@LAubervilliers-151-12-73-187.w193-252.abo.wanadoo.fr] has joined #ubuntu-meeting [10:20] LaserJock, the doc? or ltsp? [10:20] ltsp stuff [10:20] but thry could if they chose [10:20] that's what I'm saying, LTSP would be inserted into the help system on Edubuntu machines [10:21] if they installed edubuntu-docs [10:21] cool. so we definitely need LTSP doc & LTCM (SCP) doc [10:22] well, you don't have a ton of time for all this [10:22] plus install guide & customisation guide as a first priority? [10:23] String Freeze is March 8th [10:23] I know [10:23] and I'm not around for much of Feb or March [10:23] well, I still think you need to seperate out exactly what you want for shipped material vs. online material [10:24] trying to [10:24] personally I'd like as much as possible shipped. [10:25] sbalneav, you're putting your stuff in the handbook right? [10:26] sbalneav: regarding your 'short snapper' comment earlier... I just discovered the useful tips on writing help docs here : https://wiki.ubuntu.com/UbuntuHelp/PageStructure [10:27] pips1, something else we should maybe look at... [10:28] some of our docs are in the drupal CMS. maybe start moving them to the svn? [10:29] I've also been reading your various planning pages for the web/wiki [10:30] did you make any sense from them? [10:31] yeah. alot had to do with setting up drupal site. looots of info [10:31] good stuff [10:31] I'd like to chat to you later or tomorrow about some content? === licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting [10:32] willvdl: I agree with LaserJock that there is a difference between shipped / "solid" documentation and online / flexible documentation... [10:32] yes. [10:32] just trying to decide what we should work on as priority for shipped docs [10:32] ok [10:33] and there needs to be a process for moving and refining online/in flux docs to shippable documentation [10:33] yip. what I was asking earlier [10:34] depends on the doc and author [10:34] Specifically the release-notes and About page can be handled like that [10:35] They way I see it, we will have community members' "input" in both drupal and the wiki... [10:35] well not the drupal... ? [10:35] drupal will have forums, and eventually community members will write stuff that is worthy and valid documentation... ? [10:36] but there is ubuntuforums.org? [10:37] anyway, I am following you [10:37] (drupal also has a nice "book" content type, for "sequential"/ordered content). [10:38] pips1, how do you envisage using something like that for community contribution? [10:38] sine it is not really a versioning tool... [10:38] willvdl: RichEd and me discussed the "filtering" process at UDS MV... we haven't quite gone into implementational details (with Drupal) yet. [10:39] ah, you mean the community education site? or www.edubuntu.org? [10:40] (willvdl: note I'm not sure if / I don't actually think we want to use the "drupal book" content type at all). I guess I shouldn't have mentioned it. [10:40] willvdl: I'm talking about the community site [10:40] no worries, it's the concept that's important [10:40] pips1 something else I'd like to push with doc team is the Quality Assurance spec [10:41] link ? [10:41] which has policies for Release sensitive help pages === willvdl looks [10:42] ohhh, that would be very interesting indeed [10:42] https://blueprints.launchpad.net/ubuntu-website/+spec/help-wiki-quality-assurance [10:42]