/srv/irclogs.ubuntu.com/2007/01/17/#ubuntu-meeting.txt

=== 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
Seveastsmithe, liar :p12:58
=== 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
highvoltage@schedule12:35
UbugtuSchedule 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 Board12:35
highvoltageexcellen12:35
highvoltaget12:35
Hobbsee@schedule sydney12:37
UbugtuSchedule 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 Board12:37
=== 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
juliux@schedule02:24
UbugtuSchedule 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 Board02:24
=== 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
lotusleaf "looking through a demon's eye" "We're gonna spy on God Find out if he really is"02:49
=== 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
juliux@schedule08:00
UbugtuSchedule 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 Board08:00
=== 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
willvdl@schedule09:00
UbugtuSchedule 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 Board09:00
=== pips1 [n=philipp@55-158.1-85.cust.bluewin.ch] has joined #ubuntu-meeting
highvoltagehey pips109:01
highvoltagelong time no see09:01
pips1hey highvoltage09:01
willvdlhey pips1!09:01
pips1:-)09:01
=== pips1 looks around
willvdlright, who's present?09:02
willvdlShall we get cracking?09:02
pips1sure09:02
pips1RichEd is in Australia, right?09:02
willvdlRiched is in Australia at LCA09:02
willvdlsnap09:02
willvdland ogra can't make it tonight09:02
pips1ic09:03
juliuxhi09:03
pips1rodarvus ?09:03
pips1sbalneav ?09:03
sbalneavHello!09:03
willvdlhey09:03
pips1hi!!09:03
sbalneavPresent09:03
pips1cbx33 ?09:04
=== sbalneav holds hand up
willvdlrodarvus is around I think09:04
pips1willvdl: will you pace us through the agenda?09:05
willvdlWell, let's get started anyway09:05
willvdl=== TECHNICAL ===09:05
willvdlIf ogra were here, I'm sure he'd ask for testers...09:05
willvdlnot sure how much we can cover in tech09:06
cbx33hi09:06
sbalneavI'll be doing some testing of thin client sound this weekend.09:06
willvdlola09:06
cbx33nice one sbalneav09:06
willvdlgreat, ogra mentioned sound architecture last week09:06
=== cbx33 has an update on LTCM(SCP)
=== willvdl hands cbx33 the conch shell
cbx33oooh09:07
cbx33well.....09:07
cbx33is this thing on09:07
cbx33...09:07
cbx33I have started the LTCM spec09:07
cbx33it's now successfully broken up into front end and back end09:07
cbx33which is awesome09:07
willvdlaha. saw those discussions09:07
cbx33today I worked for a little while on the tiled vnc feature that everyone wanted09:07
cbx33and I actually got it working09:08
cbx33borrowed some code from somewhere else09:08
cbx33but it's all GPL so we're good09:08
willvdlsweet09:08
cbx33that's me done09:08
cbx33anyone who wants to test it for me09:08
cbx33shout09:08
willvdlwhat does the "split" mean as such?09:09
cbx33well09:09
cbx33it will allow a KDE developer to write a kde front end for LTCM09:09
cbx33since they can just import the backend module and all the hard stuff is done for them09:09
willvdlah. with clear api etc09:09
cbx33indeed09:09
cbx33and the backend is actually tiny09:10
=== j_ack [n=rudi@p508D8BAA.dip0.t-ipconnect.de] has joined #ubuntu-meeting
cbx33the gui takes up most code09:10
=== pips1 is trying to figure out the acronym... Linux Terminal Control Manager? Erm...
Riddellcbx33: what is LTCM?09:10
cbx33LTSP Thin Client Manager09:10
willvdlthin client manager09:10
willvdlsnap09:10
cbx33damn you win ;)09:11
cbx33however for now the vnc stuff will only be in the gnome version09:11
willvdllooking forward to seeing it in action09:11
cbx33as 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 split09:11
pips1so LTCM (LTSP Thin Client Manager) is now the official new name for SCP (Student Control Panel)?09:12
cbx33yes09:12
cbx33oh and I spotted a bug in SCP which should be fixed soon09:12
pips1right09:12
willvdlI can't imagine you've had much time for the MOTD thingy?09:13
cbx33unfortunately no09:13
cbx33not yet09:13
cbx33It's still a possibility09:13
cbx33infact it's SOOO simple to implement09:13
willvdlshall we move on?09:14
pips1Is anyone present expecting to be able to test Herd 2, 3, ... (besides sbalneav)?09:14
cbx33sure09:14
cbx33unfortunately I won't have time09:14
pips1let's move on..09:15
willvdllet's skip to Artwork if no-one minds?09:15
cbx33sure09:15
cbx33Lisa is sorry she can't attend this evening09:15
willvdl=== ARTWORK ===09:15
willvdl^^^ makes logs easier to edit09:15
cbx33she hasnt had a great deal of time lately....been very very busy with paid work09:15
cbx33but she is still working hard...and really really needs your feedback09:16
willvdlCanonical is going to employ an ubuntu artist09:16
cbx33for edubuntu too?09:16
willvdlneed to see how that works out09:16
cbx33ok09:17
willvdlcbx33, feedback on templates, pallettes etc?09:17
cbx33I think shes talking about the mock wallpaper she did a while back09:17
cbx33but09:17
cbx33I think they'll be some more before not too long to comment on09:17
cbx33also09:17
cbx33if anyeone knows of any budding artist09:17
cbx33please get them involved09:17
willvdllet's tap the Ubuntu Artwork channel09:18
willvdlmake a formal "call for contributions"?09:18
cbx33well we have done that in the past09:19
cbx33I'll get lisa to mail them tonight09:19
pips1Does the Artwork Team have its own introduction/welcome page somewhere?09:19
willvdlsweet. just good to voice ourselves I guess09:19
cbx33yes09:19
willvdlEdubuntuArtwork09:19
cbx33people just don't seem keen to help out Edubuntu much09:19
willvdlperhaps we need to make it easier for them09:20
willvdlsomehow...09:20
highvoltagewillvdl: i agree with you09:20
cbx33me too09:20
cbx33I just don;t know how09:20
willvdlI'm don't hang around the artwork channels much or browse the contributions but there are a lot of folk contributing to Ubuntu art09:21
cbx33yeh09:21
cbx33ok I'll draft up an email...09:21
willvdlif we have representation in those channels then well get stuff I'm sure09:21
cbx33ok if I run it by you willvdl ?09:21
willvdlsure09:21
=== pips1 glances at https://wiki.ubuntu.com/Artwork
=== LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-meeting
willvdlIs there anyway we can merge our Artowrk "space" with the ubuntu artwork "space"?09:22
cbx33hmmm09:22
cbx33possibly I suppose09:22
pips1hi LaserJock09:22
willvdlquote: feisty will be designed by cliff09:23
LaserJockhi everybody09:23
highvoltagehey LaserJock09:23
willvdlas with dapper. how did that affect edubuntu back then?09:23
LaserJockuggg09:23
highvoltagedapper was a tough one09:24
LaserJockwillvdl: armed revolt? :-)09:24
pips1"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
willvdlLaseJock, dodgy prawn?09:24
highvoltageogra and janew weren't very happy that they didn't have any say in the artwork09:24
cbx33does that include edubuntu do we know?09:24
willvdldid edubuntu do its own artwork in dapper?09:24
highvoltagewillvdl: hired artist09:24
willvdlfor backgrounds, splash and icons?09:25
highvoltagewillvdl: except for icons09:25
cbx33we had a wallpaper in main though didn't we09:25
pips1"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
willvdllegacy pages09:25
pips1hmm09:26
cbx33sounds old09:26
LaserJockis there a rationale behind not letting the community do the artwork?09:26
LaserJockit seems to go back and forth, kinda annoying09:26
pips1yeah09:26
willvdlhttp://art.ubuntu.com/main.php09:26
willvdlanyway, it is still very valuable to have contributions regardless of closed design09:27
cbx33well for a start we have more than just one wallpaper09:27
pips1oh, I didn't know they had revanped the art.u.c site09:27
highvoltageLaserJock: I don't think there's anythin wrong with Canonical hiring people to improve Ubuntu's artwork... but... \09:27
pips1*revamped09:27
cbx33highvoltage, I agree09:27
highvoltageLaserJock: if there are better community submisions, it should be considered too, imho09:27
cbx33maybe for get someone behind it to drive it in right direction09:28
LaserJockhighvoltage: but they won't consider them if they are already contracting people, it would be a waste of money09:28
willvdlhighvoltage, LaserJock : that is how I would expect things to be run09:28
cbx33so will that be for Edubuntu too.....?09:28
cbx33can we confirm this09:28
willvdljust like Canonical hires kernel developers09:29
highvoltagecbx33: by ubuntu I mean *buntu09:29
willvdlcbx33, I will check09:29
cbx33ah ok09:29
LaserJockwillvdl: it's a bit different, IMO09:29
willvdlLaserJock, only if handled badly09:29
LaserJockwhich it seems to have been historically09:29
LaserJockartwork that is09:29
cbx33basically how much should we push the artwork in Edubuntu09:29
cbx33and how much is going to be forced upon us09:30
LaserJockthe Canonical hired kernel guys work in the open with patches, ML etc.09:30
LaserJockgenerally we get to see the artwork when it's released09:30
willvdlMy opinion is to push contributions anyway09:30
willvdlwhat we build now can always be used later or even make it in if the process allows09:30
willvdlplus we keep the community active09:31
pips1willvdl: but it's not very encouraging for designers, if the aren't any clear known "rules"09:31
cbx33exactl09:31
cbx33y09:31
pips1clear procedures... so you know what to expect and what not to expect09:31
cbx33it's pretty upsetting infact09:31
willvdlagreed, but note that art.u.c gets contributions regardless09:31
cbx33when someone has worked really hard ....09:31
cbx33willvdl, it's a little different09:31
LaserJockespecially when the dev community all say the want a community artwork and are ignored09:32
LaserJock*they09:32
cbx33because edubuntu last relase had 2 contributors09:32
cbx33so it makes it a little more personal09:32
willvdlI hear you guys and agree09:32
willvdlI'm just saying we should not stop contributing09:32
cbx33no, but can you see how.....in a big community like ubuntu it just means a drop in contributions09:33
cbx33but that with a tiny team....2 people that can make or break the contributions full stop09:33
willvdlyeah.09:34
=== pips1 reads the introduction on http://art.ubuntu.com/main.php
willvdlOK, PoA:09:34
LaserJockespecially when the community isn't consulted at all09:34
pips1cbx33: good point09:34
willvdlwill check on procedures, policies etc internally09:34
cbx33also....09:35
willvdland, seperate issue, try and integrate more with artwork team for leverage?09:35
pips1ok, willvdl to report back at the next meeting :-)09:35
willvdljust not sure immediately how to achieve the latter09:35
=== Joe5656 [n=JoeCormi@mctnnbsa28w-142167096017.pppoe-dynamic.nb.aliant.net] has joined #ubuntu-meeting
willvdlThere's definately enough concern on the issue to raise it09:36
pips1how relevant is https://blueprints.launchpad.net/~ubuntu-art ?09:37
pips1... to edubuntu artwork, I mean09:37
highvoltagepips1: fairly09:38
highvoltagepips1: edubuntu inherits some of the ubuntu artwork stuff09:38
highvoltagepips1: like firefox themes, etx09:38
highvoltage*etc09:38
willvdlany *buntu artwork work should include/be relevant to edubuntu IMHO09:38
highvoltagepips1: and the edubuntu gtk theme is normally derived from whatever theme is in use on edubuntu09:38
highvoltageI mean, Ubuntu09:38
=== highvoltage really needs some sleep
cbx33nn highvoltage09:39
cbx33;)09:39
highvoltagecbx33: heh. I'll hold out a bit :)09:39
willvdlOkie, lets discuss further on ML and I'll try find out what I can09:40
cbx33ok09:40
pips1In 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...09:41
=== Lure [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
willvdlfrom EdubuntuArtwork?09:41
pips1yep09:41
pips1just a thought09:42
willvdlwhat interests me is that the artwork team consider EdubuntuArt as legacy page09:42
willvdlassuming the community is already integrated09:42
cbx33yeh...funny that09:42
willvdlWe should fix that09:42
cbx33i don't remember anyone talking to Lisa about it ;)09:42
willvdlit's a perception09:43
pips1well things are always moving fast in ubuntu land :-) and it's hard to keep up with what is going on everywhere09:43
willvdl:)09:43
willvdlshall we move to docs?09:44
cbx33ok09:44
willvdl=== Documentation ===09:44
willvdlI've been thinking about doc contributions somewhat09:45
willvdland have chatted to a number of folk09:45
cbx33ok09:45
=== ash211 [n=andrew@user-1121oil.dialup.mindspring.com] has joined #ubuntu-meeting
willvdlon wiki contributions vs SVN contributions09:45
willvdlmeaning wiki = open collaboration09:46
willvdland svn = open collaboration but large barrier09:46
willvdlhow do you folks feel?09:46
LaserJockdepends on the doc, IMO09:47
=== tommy [n=tommy@83.167.116.108] has joined #ubuntu-meeting
willvdltrue09:47
pips1wiki = medium barrier too, AFAIK09:47
LaserJockif you want it stable and need to be in various formats do docbook09:47
LaserJockwith svn09:47
willvdlyip, but the svn authors can pull their info form the wiki09:48
willvdlif the wiki is used as the "development" space09:48
pips1hold on, we are talking about a variety of tools and formats here...09:48
willvdltrue09:48
pips1docbook = format09:48
pips1svn = versioned repository09:49
pips1wiki = versioned repository with web frontend09:49
pips1no?09:49
willvdlyip09:50
willvdlalso docs in svn get packaged09:50
LaserJockwiki also = format09:50
pips1willvdl: how do you imagine your "perfect" documentation process?09:50
willvdlperfect? :)09:51
willvdlwell, I'm just again trying to leverage contributions09:51
Joe5656!Question  How do I leave this channel?  I'm not at the right channel here....  My apologies for interrupting you all!09:51
pips1LaserJock: ok, wiki stores the information in its own format, that's right09:51
willvdland was thinking back to a conversation I had with pips1 vefore the holidays09:51
willvdland others09:52
willvdlbeing that the wiki is the easiest and most open tool and repo we have for contributions09:52
willvdlWould 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 files09:53
pips1well, ideally we could have a super userfriendly "frontend" tool combined with the benefits of a standard format such as docbook...09:54
willvdlalthough my suggestion is contrary to using Launchpad, bug-reporting etc09:54
pips1how so?09:54
=== pips1 isn't sure he is following willvdl
LaserJockJoe5656: /leave09:55
Joe5656Thanks laser!09:55
LaserJockI'm not sure that easy contribution is always the way to go though ...09:55
willvdlperhaps LaserJock can help me here, but LP tracks the docs (in whatever format) and contributions are made in patches, bug-reports or specs09:55
LaserJocksometimes a little barrier isn't a bad thing09:55
LaserJockwell, we have an upstream product09:56
LaserJockpeople can file bugs against that09:56
LaserJockand we can write specs09:56
LaserJockpatches are sent to the ML09:56
willvdlperhaps we should take a step back here09:57
willvdland look at what docs we are needing09:57
willvdlWe need an install guide prob09:58
willvdlrelease-notes & about page09:59
willvdland LTSP info as it forms part of our release10:00
willvdlgiven the topics, and the authors, what would the best tools be?10:00
willvdlpips1 what are your thoughts?10:03
sbalneavSorry to interject, but is the svn repo for the handbook still on digitalredneck?10:04
willvdlnope. moved into docteam.u.c10:04
sbalneavDo I still have commit?10:05
pips1Off 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
willvdlsbalneav, best check with mdke or someone10:05
willvdlnot sure10:05
cbx33sorry guys I'm gonna have to duck out, splitting headache10:06
willvdlpips1 the "guides": meaning the ubuntu ones or our own?10:06
cbx33and tired10:06
pips1willvdl: we can probably reuse the "Ubuntu Guides", but I haven't really looked into that, so I don't really know.10:07
willvdlI'd like to open a discussion on the handbook aim again. I think things have move along alot since it was created10:08
LaserJockwell, it's also noteworthy that Ubuntu and Kubuntu are moving away from "guides"10:08
pips1The Desktop Guide and the Server Guide from Ubuntu are shipped with Edubuntu anyway, right?10:09
willvdlpips1, have you looked at the Topic Based Help spec?10:09
willvdlthinks so10:09
pips1LaserJock: tell us more?10:09
LaserJockright now, Edubuntu ships ubuntu-docs10:10
pips1yep10:10
LaserJockpips1: the doc team is going for a more topic based approach10:10
LaserJockso if we just basically created add-on topics to cover Edubuntu specifics10:10
=== pips1 reads https://blueprints.launchpad.net/ubuntu/+spec/topic-based-help
LaserJockwe can "blend in" with the rest of Ubuntu docs10:11
LaserJockand there would be no duplication10:11
willvdlLaserJock, this would be the domain of the Handbook right?10:11
tsmithe@schedule10:12
UbugtuSchedule 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 Board10:12
pips1In 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
LaserJockwillvdl: what I'm saying is that I'm not sure that a "Handbook" fits in with the way documentation in Ubuntu and upstream are heading10:12
LaserJockit's fine for a book, or an all-inclusive PDF or something10:13
LaserJockwhich I think there would be a demand for10:13
willvdlLaserJock, I chatted to Sean Wheller about that earlier10:13
willvdland looked at the original aim of the handbook again10:13
LaserJockbut I think you could do that with the TBH approach anyway10:13
willvdland I think you're right in a sense10:13
willvdlBut the handbook aim was as an install/customisation/basic usage guide?10:15
LaserJockit was meant by Mario to be a book10:15
sbalneavLTSP, 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
LaserJockthe one-stop shop for Edubuntu10:15
willvdlsbalneav, I thought you might say that10:15
willvdlLaserJock, it can still be but we need TBH to "mature" first10:16
willvdlIMHO10:16
sbalneavThe problem with LTSP is, it's really a "tech" thing, and not a user thing.10:16
LaserJocksbalneav: well, I'm not sure why having a "Configuring an LTSP Server" would be a had topic10:16
LaserJocks/had/bad/10:16
LaserJockok, so I think the decision needs to be made there10:17
willvdlit becomes an interesting topic to squeeze in since it depends on the specific network topology10:17
LaserJockwhat do you want to present in the user's help system10:17
LaserJockand what do you want to provide online10:17
sbalneavIt 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
LaserJocksbalneav: ideally yeah10:17
LaserJocksbalneav: but we have the Server Guide in there10:18
LaserJockwhich isn't all that non-tech10:18
sbalneavI'm good either way.10:18
willvdlLTSP would fit into the server guide logically right?10:18
sbalneavRight.10:18
LaserJockI think you guys should take a look at the feisty docs10:18
LaserJockjust to get a feel for what it's like10:19
willvdlbut, as I understand from ogra, installing it ontop of ubuntu versus out of edubuntu is slightly difference10:19
LaserJockand see if you think it could fit in well there10:19
willvdl*different10:19
LaserJockwillvdl: Ubuntu users wouldn't see it10:19
=== mr_pouit [n=mrpouit@LAubervilliers-151-12-73-187.w193-252.abo.wanadoo.fr] has joined #ubuntu-meeting
willvdlLaserJock, the doc? or ltsp?10:20
LaserJockltsp stuff10:20
willvdlbut thry could if they chose10:20
LaserJockthat's what I'm saying, LTSP would be inserted into the help system on Edubuntu machines10:20
LaserJockif they installed edubuntu-docs10:21
willvdlcool. so we definitely need LTSP doc & LTCM (SCP) doc10:21
LaserJockwell, you don't have a ton of time for all this10:22
willvdlplus install guide & customisation guide as a first priority?10:22
LaserJockString Freeze is March 8th10:23
willvdlI know10:23
willvdland I'm not around for much of Feb or March10:23
LaserJockwell, I still think you need to seperate out exactly what you want for shipped material vs. online material10:23
willvdltrying to10:24
willvdlpersonally I'd like as much as possible shipped.10:24
willvdlsbalneav, you're putting your stuff in the handbook right?10:25
pips1sbalneav: regarding your 'short snapper' comment earlier... I just discovered the useful tips on writing help docs here : https://wiki.ubuntu.com/UbuntuHelp/PageStructure10:26
willvdlpips1, something else we should maybe look at...10:27
willvdlsome of our docs are in the drupal CMS. maybe start moving them to the svn?10:28
willvdlI've also been reading your various planning pages for the web/wiki10:29
pips1did you make any sense from them?10:30
willvdlyeah. alot had to do with setting up drupal site. looots of info10:31
willvdlgood stuff10:31
willvdlI'd like to chat to you later or tomorrow about some content?10:31
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
pips1willvdl: I agree with LaserJock that there is a difference between shipped / "solid" documentation and online / flexible documentation...10:32
willvdlyes.10:32
willvdljust trying to decide what we should work on as priority for shipped docs10:32
pips1ok10:32
pips1and there needs to be a process for moving and refining online/in flux docs to shippable documentation10:33
willvdlyip. what I was asking earlier10:33
willvdldepends on the doc and author10:34
willvdlSpecifically the release-notes and About page can be handled like that10:34
pips1They way I see it, we will have community members' "input" in both drupal and the wiki...10:35
willvdlwell not the drupal... ?10:35
pips1drupal will have forums, and eventually community members will write stuff that is worthy and valid documentation... ?10:35
willvdlbut there is ubuntuforums.org?10:36
willvdlanyway, I am following you10:37
pips1(drupal also has a nice "book" content type, for "sequential"/ordered content).10:37
willvdlpips1, how do you envisage using something like that for community contribution?10:38
willvdlsine it is not really a versioning tool...10:38
pips1willvdl: RichEd and me discussed the "filtering" process at UDS MV... we haven't quite gone into implementational details (with Drupal) yet.10:38
willvdlah, you mean the community education site? or www.edubuntu.org?10:39
pips1(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
pips1willvdl: I'm talking about the community site10:40
willvdlno worries, it's the concept that's important10:40
willvdlpips1 something else I'd like to push with doc team is the Quality Assurance spec10:40
pips1link ?10:41
willvdlwhich has policies for Release sensitive help pages10:41
=== willvdl looks
pips1ohhh, that would be very interesting indeed10:42
willvdlhttps://blueprints.launchpad.net/ubuntu-website/+spec/help-wiki-quality-assurance10:42
willvdlso that we don't confuse edgy docs with dapper etc.10:42
willvdlI think it's very easy to do.10:43
pips1willvdl: explain how...10:43
willvdledgy pages go in a edgy sub-page10:43
willvdlor have an edgy name space for example10:43
willvdlEdubuntuEdgyXXXXX10:44
willvdlor EdubuntuXXXXX/Edgy/10:44
dsasOr says at the top of the page. "Applies to Edgy and Feisty"10:44
willvdldsas, yip. or even categories10:45
dsaseasier then for docs that apply to multiple releases to not have redundant copies.10:45
willvdlbut namesacing makes it easier for scripts and preserves namespace for future release docs10:45
willvdldsas, redirects10:45
=== pips1 notes that the spec is for improving the functionality of moin moin wiki, but the spec is new, so it probably won't be implemented shortly (?)
willvdlanyway it's a topic for debate in the doc-team10:46
willvdlnot edubuntu10:46
willvdlOK we need to wrap up. Let's flag the Online/Offline doc inclusion as an Unresolved Issue10:47
pips1I will just note that on the future edubuntu community space, we can simply use drupal's tagging feature10:47
willvdlcool. tags will work too10:48
willvdlpips1 are you around tomorrow morning?10:49
pips1hmm10:49
willvdlor friday?10:49
pips1friday is better, I got a bunch of work I need to do tomorrow10:50
pips1let's set a time10:50
willvdlcool. just want to confirm some stuff with you10:50
willvdllet's set time after meeting10:50
pips1ok10:51
willvdlAnyone want to bring anything else to the table?10:51
willvdlOh, cbx33 is going to write the Edubuntu chapter in the Ubuntu Book!!!10:51
willvdlHe wants a call for suggestions/ feedback etc.10:51
pips1heh10:51
willvdlLet's give him some support on this, it's good for us :)10:52
willvdlOkie going once?10:52
pips1are you talking about the printed book, or wha?10:53
willvdlyip10:53
pips1*what?10:53
pips1ah10:53
willvdlofficial ubuntu book10:53
willvdlgoing twice?10:53
pips1ah.. an updated version, I take it... what is the timeline for it?10:53
willvdlno idea unfortunately10:54
willvdlbest ask cbx33 :)10:54
pips1righty10:54
willvdlOkie, six minutes short of two hours and we've covered some serious debate :)10:55
willvdllet's take the edubuntu doc discussion to the ML and to the ubuntu-doc team10:55
pips1Good to hear about all that documentation thoughts..10:56
willvdlpips1 it is a big and confusing monster10:56
willvdlbut fun10:56
pips1:-)10:56
willvdlOK, thrice. thanks folks. I'll have minutes up as soon as possible10:57
pips1Thanks10:57
pips1cu all!10:58
willvdlciao10:59
=== willvdl [n=will@196.207.32.235] has left #ubuntu-meeting ["Leaving"]
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : 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 | 31 Jan 20:00 UTC: Edubuntu
=== mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting
=== wasabi_ [n=wasabi@ubuntu/member/wasabi] has joined #ubuntu-meeting
=== lmanul [n=manu@dan75-4-82-239-58-38.fbx.proxad.net] has joined #ubuntu-meeting
=== wasabi_ [n=wasabi@ubuntu/member/wasabi] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has left #ubuntu-meeting ["Exit,]
=== LaserJock [n=mantha@ubuntu/member/laserjock] has left #ubuntu-meeting []

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