[05:59] <raekism> in #suse
[09:34] <spacey> hmm the font is really small on the proto site
[10:22] <froud> hi
[10:23] <froud> I have a strange question
[10:24] <froud> I was told that some time ago a handful of people working on edubuntu has made a copy of the tuxlab cookbook
[10:24] <froud> question is, did anything come of that and if so where can I find the new product?
[10:26] <froud> highvoltage: ping
[10:27] <highvoltage> froud: pong
[10:27] <froud> waz up dude
[10:27] <froud> I am on a lost content hunt
[10:28] <highvoltage> froud: pieces of the edubuntu cookbook does exist
[10:28] <froud> ah ha
[10:28] <froud> point me
[10:28] <highvoltage> just a moment...
[10:30] <highvoltage> froud: pygi is managing the new new version
[10:30] <highvoltage> https://wiki.edubuntu.org/HowToCookEdubuntu/Worksheet
[10:30] <highvoltage> we have the getting started guide ~90% complete: http://proto.edubuntu.org/gettingstarted
[10:33] <froud> where is the src kept
[10:34] <froud> highvoltage: see most on hold, was wondering if I could perhaps get src to diff with tuxlab
[10:35] <froud> highvoltage: also I must figure out how to deliver a tuxlab and incorporate edubuntu
[10:35] <froud> highvoltage: seems openlabs is not answering email, so dunno about them
[10:36] <highvoltage> froud: they exist in some wiki pages... just a sec..
[10:37] <highvoltage> froud: https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook
[10:37] <highvoltage> https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Background?highlight=%28Cookbook%29
[10:38] <highvoltage> https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Chapter_1_-_Introduction?highlight=%28Cookbook%29
[10:38] <highvoltage> https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Chapter_2_-_Walkthrough?highlight=%28Cookbook%29
[10:38] <highvoltage> wiki search might be your best bet.
[10:38] <highvoltage> on the question on the e-mail you sent me,
[10:39] <highvoltage> we got that PDF from Hilton, the original file died with an older laptop :(
[10:39] <froud> eihna!
[10:41] <froud> chatting with jerome
[10:41] <froud> he has stuff in ubuntu-docs svn
[10:42] <froud> question is which is more updated
[10:42] <froud> as for doing docs in wiki
[10:42] <froud> wiki is like a content motel, stuff checks in but never checks out :-(
[10:44] <highvoltage> yeah. hotel california.
[10:44] <highvoltage> lucasvo: got your e-mail
[10:45] <froud> jerome reckons svn is more updated than wiki
[10:45] <highvoltage> lucasvo: the idea is to go with a child-friendly look for now, and mature it gradually as the distribution matures
[10:45] <froud> seems he was trying to port the docbook xml to wiki
[10:45] <highvoltage> i couldn't say for sure, but i trust jerome, if he says it's more updated, i would be inclined to believe him.
[10:46] <froud> :-) lol
[10:46] <froud> jah
[10:53] <lucasvo> highvoltage: hm, but why not be mature from the beginning?
[10:54] <lucasvo> an unmature design isn't very helpful to make the distribution more mature
[10:54] <highvoltage> lucasvo: well, the first release is aimed at primary school classroom only
[10:55] <highvoltage> lucasvo: and the release later this year would be primary and high school, after that whole school, and then university as well
[10:55] <lucasvo> as I said, the teacher make the decision, and they expect it to be mature
[10:55] <highvoltage> lucasvo: yes, so it's about managing expectations
[10:56] <lucasvo> I would put the navigation box to the right
[10:56] <froud> what's the status of schooforge?
[10:58] <froud> highvoltage: did k12 ever make use of tuxlab cookbook?
[10:58] <highvoltage> lucasvo: yep, we'll look at that
[10:58] <highvoltage> froud: schoolforge, you mean?
[10:58] <highvoltage> froud: i don't think they did
[10:58] <froud> yah my bad
[10:59] <froud> hmm, pity
[10:59] <highvoltage> froud: wrt K12, the tuxlab cookbook was very specific to this project
[10:59] <highvoltage> schoolforge doesn't seem to be active, very much, at least not the last year or so.
[10:59] <froud> so no slaves there :-)
[11:00] <froud> last update was 2003
[11:01] <froud> so how active are k12 team?
[11:01] <highvoltage> k12ltsp team is quite active.
[11:02] <highvoltage> their main work is to get the release available each time a new FC is released.
[11:02] <highvoltage> it's a lot of work, but they keep up.
[11:02] <highvoltage> and they've done lots of small enhancements to FC that we have taken in tuxlabs for ubuntu
[11:03] <froud> I am pondering .. how to get focus on tuxlabs but remain flexible to the needs of projects such as edubintu and k12
[11:03] <highvoltage> lucasvo: if you feel strongly about the maturity feel, i suggest you mention it at the next edubuntu meeting. it was a team decision last time, and it's not something i can (or would want to) reverse just like that.
[11:04] <lucasvo> highvoltage: ok
[11:04] <highvoltage> froud: that is a bit of a toughie, since we'll have some software changes that will stay specific to ubuntu :/
[11:04] <froud> I like the modular tuxlab approach
[11:04] <highvoltage> lucasvo: although, i do agree with you, to a large extent. perhaps we should just try to fast-forward the process a bit?
[11:04] <froud>     *
[11:05] <froud>       Software Module
[11:05] <froud>     *
[11:05] <froud>       Technical Module
[11:05] <froud>     *
[11:05] <froud>       Content Module
[11:05] <froud>     *
[11:05] <froud>       Training Module
[11:05] <froud>     *
[11:05] <froud>       Management Module
[11:05] <lucasvo> highvoltage: how would you want do it?
[11:05] <froud>     *
[11:05] <froud>       Support Module
[11:05] <froud>     *
[11:05] <froud>       Volunteer Module
[11:05] <froud>     *
[11:05] <highvoltage> lucasvo: what we could do is, as soon as the new site is up, start working on a more mature theme, that still captures the 'fun spirit' of the old design, and then have apply the new theme a few months later
[11:05] <froud>       Sustainability Module
[11:05] <froud> oops
[11:05] <froud> sorry bout that :-)
[11:06] <lucasvo> highvoltage: ok, yes
[11:06] <lucasvo> highvoltage: but then we are doing the work twice
[11:06] <froud> highvoltage:  the main problem is the difference that will happen in the Content Module
[11:06] <highvoltage> lucasvo: we'll probably do it more than twice. possibly every six months, at most.
[11:07] <lucasvo> and making a design like this for only 6 months 
[11:07] <highvoltage> froud: to be perfectly honest, quite a bunch of the tuxlab modules aren't close to the quality i would like to have them
[11:07] <froud> highvoltage: oh and of course the software module
[11:07] <highvoltage> froud: i hope we get them mostly good quality before release
[11:07] <lucasvo> I don't know, if the work is worth only beeing used for 6 month
[11:07] <froud> .me looks around for release date :-)
[11:07] <lucasvo> highvoltage: but, yeah, we can try
[11:08] <lucasvo> highvoltage: anyway do you know if there are any articles or irclogs about what should be changed in edubuntu to make it suitable for highschools as well?
[11:08] <froud> highvoltage: quality aside, do you agree that the main issue is in the Software and Content Modules
[11:09] <lucasvo> highvoltage: I would keep the colored footer from the old design
[11:10] <highvoltage> froud: i'm not sure i understand what you mean?
[11:10] <highvoltage> lucasvo: that was mainly discussed at the edubuntu summit in london
[11:11] <highvoltage> lucasvo: you might find some meeting notes if you search for summit in the wiki
[11:11] <froud> highvoltage: seems to me that, with the exception of Softwate and Content Modules, the other Tuxlab modules should also be applicable to Edubuntu
[11:11] <highvoltage> froud: yes, i would tend to agree there
[11:12] <froud> highvoltage: that said we have replaced a problem with a smaller one
[11:12] <froud> highvoltage: question is can we live with it
[11:13] <froud> highvoltage: would edubuntu agree to using the other modules if they were branded as edubuntu
[11:13] <froud> highvoltage: I am considering repurposing at first level just using brand changes
[11:14] <froud> highvoltage: this way I can setup the Software and Content Modules with conditional processing  to profile outputs for edubuntu and tuxlab respectively
[11:15] <highvoltage> froud: edubuntu's cookbook goals are slightly different to the tuxlab one
[11:15] <froud> this assumes there will be some common content in these modules that is used by both projects
[11:15] <highvoltage> froud: the cookbook goals for edubuntu has also changed quite a bit a few times
[11:15] <froud> highvoltage: has it stabilized?
[11:15] <highvoltage> froud: atm, the biggest goal for the edubuntu cookbook is just to get all the essential documentation complete
[11:16] <highvoltage> froud: it's almost at a stage where it's stabilasing. pygi is putting quite a bunch of work into structurising that nicely.
[11:16] <highvoltage> froud: i distanced myself a bit from the cookbook initially, and considered myself more of an upstream maintainer
[11:17] <froud> So how do you see the difference between edubuntu cookbook and tuxlab cookbook
[11:17] <highvoltage> froud: but got involved again in tha last few weeks, since we're having trouble getting to a finished cookbook state
[11:17] <highvoltage> froud: if you look at the 'edubuntu cookbook' pages on the wiki, they're quite different. they newer one might be slightly more similar.
[11:18] <highvoltage> froud: but if you're talking in terms of making diffs between the two, they're very, very, very different
[11:18] <highvoltage> it's practically a cookbook from scratch.
[11:18] <highvoltage> as far as i understand it.
[11:18] <froud> highvoltage: don't you think it will make more sense to gather around a common structure
[11:19] <highvoltage> yes, i do.
[11:19] <froud> assuming I get OK to work on this for tuxlab
[11:19] <froud> then edubuntu can capitalize on the work
[11:20] <froud> at present we have two documentation projects that are going nowhere slowly
[11:20] <froud> I think we can get one that is going somewhere slowly :-)
[11:21] <froud> but it will take consolidation and cooperation with edubuntu team
[11:21] <highvoltage> hehe!
[11:22] <highvoltage> well put.
[11:22] <pygi> spacey: alive? :)
[11:22] <spacey> hi
[11:22] <spacey> yes
[11:22] <highvoltage> pygi: froud has lots of questions about the cookbook :)
[11:22] <highvoltage> pygi: i think you should speak to him
[11:22] <pygi> spacey: like the worksheet? :)
[11:23] <lucasvo> highvoltage: I think the current edubuntu.com design looks more mature than the design of proto.edubuntu.org
[11:23] <froud> hey pygi 
[11:23] <highvoltage> lucasvo: then we definately have to smooth out proto much more
[11:23] <pygi> froud: hello
[11:23] <pygi> how may I help you? :)
[11:23] <froud> pygi: how would you define the status of the edubuntu cookbook
[11:24] <pygi> Status: Being written :)
[11:24] <lucasvo> froud, pygi: what do you think? which design is more mature: www.edubuntu.org or proto.edubuntu.org?
[11:24] <froud> pygi: I may get OK to work on Tuxlabs
[11:24] <spacey> at least the font on proto is really small here
[11:24] <pygi> lucasvo: please make that red a little ligther? :)
[11:25] <froud> pygi: in which case I would like to bring together opportunities for both tuxlabs and edubuntu
[11:25] <lucasvo> pygi: I don't have access to proto.edubuntu.org
[11:25] <pygi> highvoltage does? 
[11:25] <lucasvo> yes
[11:25] <froud> pygi: the current tuxlab project plan http://wiki.tsf.org.za/shuttleworthfoundationwiki/TuXlab/HowTo
[11:25] <pygi> froud: that is great, but for dapper we have just 1 chapter left untaken, about artwork if I am not mistaken
[11:26] <froud> pygi: it's a modular approach
[11:26] <froud> pygi: where are the sources
[11:26] <lucasvo> pygi: but which red do you meaan?
[11:26] <pygi> all red, and all orange...too bright
[11:27] <pygi> froud: what sources do you need?
[11:27] <froud> pygi: what src do you have
[11:27] <lucasvo> ahh, so I am not the only one, thinking the design is too "funky" :)
[11:27] <froud> pygi: for edubuntu cookbook
[11:28] <pygi> froud: well, we are mostly writing original content, but we can look at tuxlabs howto (where is it now? :) )if we really need it
[11:28] <froud> I know of stuff in ubuntu-doc svn and in wiki, do you have something else?
[11:28] <pygi> hm, no, not really
[11:28] <pygi> other is being written :)
[11:28] <froud> pygi: according to this it's ONHOLD https://wiki.edubuntu.org/HowToCookEdubuntu/Worksheet
[11:29] <froud> only sction is the install http://proto.edubuntu.org/gettingstarted
[11:29] <pygi> froud: well, it's outdated :)
[11:29] <froud> pygi: OK so what is the status?
[11:29] <pygi> well, "Being written" is the status :)
[11:29] <froud> where can I view development
[11:30] <pygi> for now nowhere..until we upload all
[11:30] <froud> is there a way that I can partake in the development (collaborate)
[11:30] <froud> hmmm
[11:30] <pygi> yes, ofcourse
[11:30] <pygi> but currently only on this chapter "Look & Feel (Maintain artwork package,Fit your needs) "
[11:30] <pygi> because we have authors for all others
[11:30] <lucasvo> highvoltage: I'll try to come to next edubuntu meeting
[11:31] <pygi> https://wiki.edubuntu.org/HowToCookEdubuntu/looknfeel
[11:31] <pygi> that chapter goes to upper URL
[11:31] <froud> pygi: so at present the doc effort is not following the open source development model?
[11:31] <pygi> froud: no, that is wrong thinking :)
[11:31] <highvoltage> froud: you have a link to the open source development model?
[11:32] <pygi> Everything will be visible as soon as we update the pages, and write more
[11:32] <pygi> I don't want to update pages for 2 words :)
[11:34] <pygi> froud: do you understand? :)
[11:34] <froud> pygi: yes ...    so until somebody does something, like uploading, nobody else has abilit to do anything because they cannot get the lastest revision
[11:35] <froud> pygi: help me out here
[11:35] <froud> pygi: speaking to highvoltage wee agree that the only problem areas
[11:36] <froud> between what is tuxlab and edubuntu relate to Software and Content
[11:36] <froud> other than this stuff like hardware, manaement and support are common between the projects
[11:37] <froud> this enables both projects to repurpose the common content
[11:37] <highvoltage> pygi: do you think it might be a good idea to schedule another cookbook meeting?
[11:37] <pygi> froud: agreed
[11:37] <pygi> highvoltage: what for this time? 
[11:37] <froud> now all we need is a way to accomodate the differences between projects
[11:37] <highvoltage> pygi: then we could have everyone there, then it's easier to make decisions
[11:37] <pygi> highvoltage: let's first write all, then meeting, ok?
[11:37] <highvoltage> pygi: just for collaboration, it doesn't have to change anything
[11:37] <pygi> froud: agreed
[11:38] <highvoltage> pygi: sure, sounds good
[11:38] <froud> pygi: here is the thing, I need to update for tuxlab
[11:38] <froud> pygi: but would be nice to help edubuntu
[11:38] <froud> pygi: so I am tasked with merging the best form all and providing a since source that all can use
[11:39] <froud> pygi: so for tuxlab there will be tuxlab info
[11:39] <highvoltage> froud: you also have to keep in mind that, lots of things have changed for the edubuntu cookbook project, and we wouldn't want to change things drastically so that it starts from scratch again
[11:39] <froud> and brand
[11:39] <froud> same for edubuntu
[11:39] <pygi> froud: agreed, but...
[11:39] <pygi> froud: we should really both be able to get something from the cookbook, but at the moment cookbook is very fragile...
[11:39] <froud> highvoltage: yes, that is part of what I must now do.... consolidate
[11:39] <pygi> and we can't allow to change things so much :-/
[11:40] <pygi> froud: do you know how long it took us to get things of the ground? 
[11:40] <froud> pygi: there are two ways forward
[11:41] <froud> pygi: 1. Tuxlabs moves forward independant of edubuntu
[11:41] <froud> pygi: 2. Tuxlabs and Edubuntu move forward toegtehr
[11:41] <froud> the later takes compromise on both sides
[11:41] <froud> both projects have interests
[11:41] <pygi> froud: agreed
[11:42] <froud> my task is to protect the interests of both 
[11:42] <pygi> highvoltage, spacey: I am not really sure we can do anything at this point...even minor "turn somewhere" from the current plan could be a dissaster...thoughts?
[11:42] <froud> while enabling lower maintenace cost, higher quality
[11:42] <pygi> froud: agreed
[11:43] <froud> pygi: if this derails your targets, then we need to look toward after your targets
[11:43] <froud> in the interim, tuxlabs will proceed and will just take into consideraton that it must embrace edubuntu
[11:44] <pygi> no, not the targets actually, but you have to understand that the cookbook was supposed to be written ages ago, and it wasn't
[11:44] <froud> I know
[11:44] <pygi> we battled a really heavy battle to get it off ground :-/
[11:44] <highvoltage> pygi: i like keeping things simple.
[11:44] <pygi> highvoltage: meaning in real words? :)
[11:44] <froud> pygi: froud = http://learnlinux.tsf.org.za/authors/web-os-team.html
[11:44] <pygi> jane_: here? :)
[11:45] <highvoltage> pygi, froud: in real words, it means that whatever we do, it shouldn't add more overheads to the project
[11:45] <froud> http://learnlinux.tsf.org.za/courses/web-tuxlabs.html
[11:45] <froud> actually it removes overheads
[11:45] <highvoltage> imho, someone can right it in MS-word for all that I care. as long as we get the docs written
[11:45] <froud> :-)
[11:46] <highvoltage> grrr
[11:46] <highvoltage> :)
[11:46] <froud> highvoltage: the requirements I have are
[11:46] <froud> 1. Update Tuxlab
[11:46] <froud> 2. merge info from openlabs and edubuntu to tauxlab
[11:47] <froud> 3. Enable tuxlab as upsteam to such projects
[11:47] <froud> 4. Provide method for such project to benefit
[11:47] <pygi> froud: all I can say for now that initial version of the How to cook Edubuntu? (like a call for QA, gramatical errors checking, etc) will be like May, 10.
[11:47] <froud> 5. Make it free and open
[11:47] <pygi> by when do you have to update tuxlab?
[11:48] <froud> pygi: laying down the planning
[11:48] <froud> pygi: but it is hard to accomodate edubuntu without transparency to development versions
[11:48] <pygi> froud: agreed
[11:49] <pygi> froud: There will be more often updates
[11:49] <pygi> if that can help you :)
[11:49] <pygi> there, a compromise :)
[11:50] <pygi> now, you write a artwork section of edubuntu cookbook :)
[11:50] <froud> If that is what it takes
[11:50] <pygi> nah, I was just joking...you don't have to write anything if you don't want, no worries :)
[11:50] <pygi> highvoltage: You need to update that article of urs to accommodate cookbook
[11:50] <froud> ok now one more thing
[11:51] <froud> tuxlab requirements are to be in docbook xml 
[11:51] <highvoltage> pygi: ok
[11:51] <pygi> highvoltage: it's just we don't need "Why" and such things
[11:51] <pygi> downloading will go somewhere else as well
[11:51] <froud> the documents will later be converted into POT files and Tuxlab will be submited to Launchpad and rosetta
[11:52] <pygi> froud: hm, well, for now we are and will be doing on Wiki
[11:52] <pygi> once it's written, it'll change to other formats probably
[11:52] <froud> pygi: if tuxlab goes launchpad so will edubuntu
[11:52] <pygi> once easier to distribute
[11:52] <pygi> one*
[11:53] <froud> wiki is nice but not IMHO good for doing documentation properly
[11:53] <froud> it simply s not portable enough
[11:54] <froud> the other option is DITA
[11:54] <pygi> froud: agreed, but wiki is fine for now, don't you agree? 
[11:54] <froud> but the knowledge of DITA in the FOSS world is not strong enough
[11:55] <froud> pygi: well, tuxlab is in docbook and is also in ubuntu-doc svn
[11:55] <pygi> froud: well, the cookbook will most probably be in docbook as well once it is written
[11:55] <froud> the files on wiki are a port by jerome to wiki
[11:56] <froud> I have three srcs of * coookbook
[11:56] <froud> 1 in ubuntu-doc svn
[11:56] <froud> this one is jeromes stuff for eduubuntu
[11:57] <froud> 2. at svn in upfront system
[11:57] <froud> this was original from Jean Jordaan
[11:57] <froud> and 3 in the learnlinux svn
[11:58] <froud> a copy of the upfront version
[11:58] <froud> the stuff on wiki, according to jerome, is not as updated as the stuff in ubuntu-doc svn
[11:59] <froud> pygi: this is why I want to compare your stuff, to see which is most update
[11:59] <froud> I must bring it altogether in a single place
[11:59] <pygi> froud: I am aware of that, and you'll get ur docbook, but I don't think it'll happen this second :)
[12:00] <pygi> hm, what about this?
[12:00] <froud> don't need dobook now, just the current format will do :-)
[12:02] <pygi> considering the cookbook should be written by the May, 10 then I'll help you integrate it into Tuxlabs, and we'll merge All "error fixes" in it by the time they exist (like May, 20)
[12:02] <froud> pygi: that asumes too much
[12:03] <pygi> froud: nah, not really
[12:03] <froud> pygi: if we are both developing in a hole
[12:03] <froud> pygi: them we may be to far appart
[12:03] <highvoltage> froud: perhaps it does, but i think it will help get the edubuntu-docs out asap
[12:03] <highvoltage> froud: i think we can get the two parts together again later, don't you?
[12:03] <froud> highvoltage: if we can see what edubuntu docs are
[12:04] <froud> at present I have no way of knowing
[12:04] <pygi> froud: we agreed that we'll update it more often :)
[12:04] <froud> so where can I see what is current
[12:04] <pygi> for now, nowhere
[12:04] <froud> :-(
[12:04] <pygi> but there is not much written except highvoltage's, which needs modification
[12:04] <highvoltage> froud: for now, it might be safest to assume that there are no edubuntu docs
[12:05] <pygi> welcome JaneW
[12:05] <froud> highvoltage: ok I am going to recomend as follows
[12:05] <froud> we cannot repurpose content from edubuntu
[12:05] <froud> yet
[12:05] <froud> therefore
[12:06] <froud> either tuxlab waits
[12:06] <froud> or tuxlabs just does its own thing based on edubuntu
[12:06] <pygi> I would suggest waiting
[12:06] <pygi> then I'll help you integrate
[12:06] <pygi> and we'll have tuxlabs ready the date the dapper is out
[12:07] <froud> however, if we wait and edubutu has nothing to show a month down th eline, we will have wasted valuable time for tuxlab
[12:07] <pygi> froud: agreed, but there will be things written
[12:08] <froud> pygi: the sooner we can see what is written, the sooner we can help
[12:08] <highvoltage> in my opinion, i would let both do its own thing for now, then merge again later
[12:08] <froud> highvoltage: I think that is what jason will say
[12:08] <pygi> JaneW: are you alive? :)
[12:09] <highvoltage> both have seperate goals at the moment, but it will have lots of overlap, but it's wasteful to compromise anyone of the two right now, even for the sake of collaboration.
[12:09] <highvoltage> i think everyone agrees that we can, will, and must collaborate.
[12:09] <highvoltage> i also don't think that it has to happen right now.
[12:09] <highvoltage> sorry-
[12:09] <highvoltage> i mean-
[12:09] <highvoltage> no, that's right. multitaksing here
[12:10] <pygi> froud: hm, can we just integrate edubuntu right into it once the entire cookbook is written?
[12:10] <froud> highvoltage: yes, but costing the tuxlab stuff ... repurposing edubuntu now will reduce investment
[12:11] <froud> pygi: wont be so easy if we don't have the same conventions and structuring
[12:11] <froud> pygi: in design of tuxlabs the information architecture will be such that it is modular
[12:11] <pygi> hm, all of this should have been discussed earlier, much earlier
[12:12] <froud> pygi: tuxlab discussion has been done, but now I am looking for intel from edubuntu
[12:12] <froud> info that can help us plan the architecture so that edubuntu can be easily incorporated
[12:13] <pygi> well, you can see the chapters/parts structure, but that probably isn't helpful enough
[12:13] <highvoltage> pygi: this has been discussed before
[12:13] <froud> not being able to see the cuurent structure, I am unable to make recomendation on how each may proceed in the ionterm in such a way that will enable relatively simple merging at a future date
[12:13] <pygi> highvoltage: yes, I know
[12:13] <highvoltage> pygi: with the very first edubuntu cookbook structure, we were going to copy exactly from tuxlab cookbook
[12:14] <highvoltage> froud: keep in mind though, that tuxlab cookbook structure has changed too
[12:14] <pygi> highvoltage: but this is not the very first structure, so...
[12:14] <froud> highvoltage: tuxlab remains with the same outline
[12:14] <froud> the new stuff from tsf is different
[12:15] <froud> and will impact on the tuxlab cookbook v2
[12:16] <froud> oki doki
[12:16] <froud> pygi: highvoltage: thanks for the information
[12:16] <pygi> froud: so, what are we to decide?
[12:17] <froud> pygi: without current visability into edubuntu cookbook
[12:17] <froud> I must assume that what is in edubuntu wiki and ubuntu-doc svn is the most current
[12:18] <froud> I will therefore, based on the new tuxlab modular structure
[12:18] <froud> http://wiki.tsf.org.za/shuttleworthfoundationwiki/TuXlab/HowTo
[12:19] <pygi> will be back in a sec
[12:19] <froud> proceed with merging new tuxlab data + old tuxlab cookbook + edubuntu wiki stuff into tuxxxlab v2
[12:20] <froud> pygi: did you get that last message
[12:20] <pygi> froud: your choice after all...yes, I did..
[12:21] <highvoltage> froud: keep in mind though, that things like the tuxlab software installation will be quite different to the edubuntu one
[12:21] <highvoltage> froud: for instance, we'll have a two button server install
[12:21] <froud> highvoltage: yes, I will profile the differences as I capture them from the differnt sources
[12:22] <froud> IOW, If I find reference to this 2-button install
[12:22] <froud> I will profile this difference as edubuntu
[12:23] <froud> in this way the difference between tuxlab and edubuntu will be available inline and we can decide what to do with them once edubuntu releases
[12:23] <highvoltage> froud: you won't find a reference to this install yet, it's currently undocumented :)
[12:23] <highvoltage> froud: ok
[12:24] <pygi> highvoltage: are we to document it in cookbook?
[12:24] <froud> highvoltage: perhaps we need to pass progress information from tuxlab to edubuntu
[12:27] <froud> highvoltage: we have src in learnlinux repos
[12:27] <froud> and ubuntu-doc
[12:27] <froud> and wiki
[12:28] <froud> open a new repos at edison or use an existing repos
[12:28] <froud> ?
[12:28] <froud> ironic thing is that tuxlab does not have its own svn
[12:28] <froud> :-)
[12:28] <highvoltage> froud: perhaps better served on ubuntu server? you know how we feel about edison ;)
[12:29] <froud> edison rocks
[12:29] <froud> and it's much easier to give commit accounts :-)
[12:29] <highvoltage> hehe. i thought you hated it :)
[12:29] <froud> no
[12:29] <froud> svn is solid
[12:29] <froud> it's everything else that bothers
[12:30] <froud> is it ok to discuss edubuntu/tuxlab cookbook stuff on edubuntu-devel
[12:31] <pygi> there is no edubuntu-devel
[12:31] <froud> I mean the mailing list?
[12:31] <pygi> yup, it probably is
[12:32] <froud> OK, so if we use svn @edison and edubuntu-devel mailing list for mail 
[12:32] <froud> and this irc for chat ;-)
[12:32] <pygi> ok, but I'll be out for 3 days, so don't count me in :)
[12:33] <froud> that way, edubuntu team can be inline to tuxlab devel
[12:33] <froud> pygi: np
[12:33] <froud> highvoltage: is this ok
[12:33] <pygi> anyway, you still have the option to wait until May, 10 :)
[12:34] <froud> pygi: I must keep the interests of tuxlab in mind
[12:34] <highvoltage> froud: i don't think there's any problem with discussing tuxlab stuff on edubuntu-devel
[12:34] <pygi> yes, yes
[12:34] <highvoltage> froud: just keep in mind that most of the tuxlab team isn't on edubuntu-devel
[12:34] <pygi> anyway, I am running
[12:34] <pygi> talk to you later
[12:34] <froud> pygi: cheers
[12:34] <froud> thanks
[12:34] <highvoltage> cheers pygi 
[12:35] <pygi> mario dot danic at gmail dot com if you need me
[12:35] <froud> highvoltage: so btw where are the tuxlab team
[12:37] <froud> http://www.tuxlab.org.za/
[12:38] <highvoltage> froud: there: http://www.tuxlab.org.za/about_us/team.htm
[12:38] <highvoltage> froud: although that's outdated
[12:38] <highvoltage> froud: jason isn't really tuxlab team anymore
[12:38] <highvoltage> froud: and will is being phased out
[12:39] <froud> but no mailing list
[12:39] <froud> guess they will have to subscribe to the edubuntu-devel list :-)
[12:40] <highvoltage> yeah, let's make them do that
[12:40] <froud> OK, I am off to  do more research
[12:40] <froud> later
[12:40] <froud> expect mail on mailing list
[12:50] <enyc> ;-)
[02:29] <jsgotangco> hey!!!
[02:30] <jsgotangco> froud, salut did you find what you were looking for?
[03:29] <froud> jsgotangco: hi
[03:29] <jsgotangco> hey
[03:30] <froud> jsgotangco: I managed to speak with pygi and highvoltage about the edubuntu coookbokk
[03:30] <jsgotangco> ahh cool
[03:30] <froud> seemss there is somethng being worked on, but we can't view it at present
[03:30] <jsgotangco> yes well we're going to have beta in a week
[03:31] <froud> yah, but where is it, in wiki?
[03:31] <jsgotangco> i dunno
[03:31] <jsgotangco> im not in the loop of current work
[03:32] <froud> so how do you now there is a beta in a week :-)
[03:32] <jsgotangco> april 20 is supposed to be the first beta release of dapper
[03:32] <jsgotangco> unless ogra_ibook will not do a beta i guess its ok
[03:33] <froud> pygi feels May 10
[03:33] <highvoltage> jsgotangco: the april 20 doc is the docs which are in the edubuntu-docs package
[03:33] <froud> hey mgalvin 
[03:34] <highvoltage> jsgotangco: which currently, is an *exact* copy of the tuxlabs software and technical module
[03:34] <mgalvin> froud: hey! :)
[03:34] <highvoltage> jsgotangco: so the doc we'll have for the 20'th, is basically the getting started guide
[03:34] <jsgotangco> froud, we're very much liberal with regards to edubuntu anyway with docs
[03:35] <froud> jsgotangco: no problem, just so liberal that a person cannot get straight answers on anything :-)
[03:35] <jsgotangco> lol
[03:35] <jsgotangco> anyway, i'm just waiting for ogra_ibook 's email so i could complete my stuff (about edubuntu, and the ff homepage)
[03:36] <froud> jsgotangco: it's my understanding that there is some devel on another book which is in addition to what is currently in ubntu-doc and wiki
[03:36] <jsgotangco> its the only one i could commit for this cycle
[03:36] <jsgotangco> froud, i think that's the one from elkner and company using lore,  haven't seen it
[03:36] <froud> neither has anyone else :-)
[03:37] <jsgotangco> lol
[03:37] <jsgotangco> froud, but jonathan's guide is pretty solid
[03:38] <froud> johnathan's guide?
[03:39] <froud> jsgotangco: stuff in wiki and ubuntu-doc svn are the same, right?
[03:40] <jsgotangco> froud, pretty much
[03:40] <froud> I will post some information to edubuntu-devel mailing list once I have cleared up what is what and where
[03:40] <froud> probably gonna make a new repository for it
[03:40] <highvoltage> froud: you're getting all the straight answers, you just don't want to accept them!!
[03:41] <froud> lol
[03:41] <jsgotangco> froud, we really don't know where the heck are those things they did (or so they say) in lore
[03:41] <highvoltage> froud: http://jonathancarter.co.za/files/jonathan.pdf
[03:42] <froud> highvoltage: a new one? do you have src
[03:42] <highvoltage> froud: just html
[03:42] <froud> that will do
[03:42] <highvoltage> froud: - i think. could you be more specific?
[03:43] <froud> hmm a spelling lesson
[03:43] <froud> lol
[03:45] <froud> jsgotangco: does this conversation answer your first question?
[03:46] <highvoltage> lucasvo: check out proto, i've applied some of your suggestions, still working on some of the points you mentioned
[03:46] <jsgotangco> lol i read that as conversion
[03:46] <jsgotangco> Jonathan?
[03:47] <lucasvo> highvoltage: I like it
[03:47] <froud> jsgotangco: how's that tarball com'n
[03:47] <jsgotangco> froud, i haven't even started
[03:47] <jsgotangco> gimme an hour to take dinner first
[03:47] <froud> :-) what you been doing all this time
[03:47] <froud> an hour
[03:47] <froud> !!!!
[03:47] <ubotu> NO SPEAKE ENLISH! Try searching at http://ubuntu.cc.com.au/, froud
[03:47] <froud> what's this a holidau camp :-)
[03:48] <froud> hmmm a bot
[03:49] <jsgotangco> froud, meh, wife just arrived
[03:49] <jsgotangco> froud, i'll get back to you promise
[03:49] <froud> no pressure dude
[03:49] <froud> you rock
[03:49] <jsgotangco> wait
[03:49] <jsgotangco> 1 q
[03:49] <jsgotangco> froud, can orderedlists be nested with additional ordered lists
[03:49] <jsgotangco> ?
[03:49] <froud> yes
[03:49] <jsgotangco> cool
[03:49] <lucasvo> highvoltage: I would make less boxes
[03:49] <jsgotangco> thanks
[03:49] <jsgotangco> brb
[03:50] <froud> np
[03:50] <highvoltage> jsgotangco: yes?
[03:51] <highvoltage> lucasvo: yes. all the junk from the left moved to the right, so there is too many boxes now... will scale down.
[03:52] <lucasvo> I love chocolota
[03:52] <enyc> ;-)
[03:52] <froud> caffiene and Radio Paradise (amarok honks sox)
[03:53] <lucasvo> (maybe that's in the genes from the swiss folk)
[03:53] <lucasvo> highvoltage: what do you think, would removing the background from the boxes be ok? 
[03:54] <lucasvo> or would there anybody be against it?
[03:56] <froud> jsgotangco: don't worry abt the tarball I did a co
[04:02] <jsgotangco> froud, what revision?
[04:02] <froud> HEAD
[04:02] <froud> Checked out revision 2901.
[04:03] <jsgotangco> eerr that's current
[04:03] <froud> not much there
[04:04] <jsgotangco> yeah because i deleted it before
[04:04] <froud> oooh so what happened to all the work you had done? It's just existing in svn?
[04:04] <froud> or in wiki
[04:05] <jsgotangco> i don't really remember i was pretty much pissed back then i moved some to wiki then i became jobless
[04:06] <froud> np
[04:08] <highvoltage> lucasvo: jane and ogra both like the orange background in the boxes
[04:08] <froud> jsgotangco: no problem that's why its in svn :-)
[04:10] <jsgotangco> AHA
[04:10] <jsgotangco> i have an HTML output
[04:10] <jsgotangco> hehe
[04:10] <jsgotangco> seems pretty old
[04:10] <jsgotangco> August 12, 2005
[04:11] <froud> how relevant is it now?
[04:12] <jsgotangco> it went until half of chapter 5 of tuxlabs
[04:12] <jsgotangco> and the glossary
[04:12] <froud> so up to half of chapter 5 was change for edubuntu
[04:13] <jsgotangco> The Edubuntu Cookbook
[04:13] <jsgotangco> From Zero to Linux Hero!
[04:13] <jsgotangco> The Ubuntu Documentation Project

[04:13] <jsgotangco> Revision History
[04:13] <jsgotangco> Revision 0.1	August 04, 2005	JSG
[04:13] <jsgotangco> 1st Draft committed to svn
[04:13] <jsgotangco> Revision 0.2	August 05, 2005	JSG
[04:13] <jsgotangco> Added chapters for Edubuntu cookbook
[04:15] <jsgotangco> can you try checking out r1644
[04:16] <jsgotangco> ah wait a bit
[04:17] <jsgotangco> what's your email again?
[04:18] <jsgotangco> i'll forward you the latest i have which is an HTML output
[04:18] <froud> c msg for email
[04:19] <jsgotangco> the latest i have is August 24, 2005
[04:20] <froud> sec lemme see what is in 1644
[04:21] <froud> yah looks like 164 is it. This is your log
[04:21] <froud> more chapter edits to edubuntu cookbook
[04:21] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/advanced.xml
[04:21] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/background.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/downloadinternet.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/edubuntu-cookbook.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/gettingmost.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/introduction.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/lablayout.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/osseducsoft.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/problemsolver.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/serverconfig.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/softcomponents.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/thinclient.xml
[04:22] <froud> M /trunk/edubuntu/EdubuntuCookbook/C/walkthrough.xml
[04:22] <froud> ring any bells
[04:22] <jsgotangco> arggghh what went into my mind and decided to stop writing them
[04:22] <jsgotangco> yeah i made them into modules
[04:22] <jsgotangco> i thought it would be easier for me to write them
[04:23] <jsgotangco> what date was this?
[04:23] <froud> 24-08-2005
[04:23] <froud> 03:54
[04:23] <froud> and 31 seconds
[04:24] <jsgotangco> this was the time and xorg was breaking so badly and even we didnt even have a good LTSP candidate working
[04:24] <froud> yes and I just got fed up
[04:24] <froud> you see, hack the source, trust svn :-)
[04:25] <jsgotangco> hmm 4 days before my birtday even
[04:27] <froud> jsgotangco: you a wack of work on this dude, the diff between 1644 and first time edubuntu was added in big
[04:28] <jsgotangco> i didn't commit them until i felt it was working right
[04:28] <jsgotangco> but then real life went into play
[04:31] <jsgotangco> i would say the wiki has better edits
[04:34] <jsgotangco> they sure look good now that i get to read them again
[04:47] <jsgotangco> im going to sleep early
[04:47] <jsgotangco> froud, hope it helps
[05:00] <prizren> hi
[05:14] <froud> so kewl http://drowtales.com/
[05:35] <froud> can any tell me how this outline shapes with what is to be release May 10
[05:38] <froud> oops sorry forgot the url :-)
[05:38] <froud> https://wiki.edubuntu.org/HowToCookEdubuntu/Chapters
[06:55] <froud> Anybody have something to add to https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/WhyEdubuntu
[06:55] <froud> seems the page is no longer found 
[06:58] <highvoltage> ogra: hi there. had a good weekend?
[06:58] <ogra> highvoltage, so so ... 
[06:59] <froud> would people agree that https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Chapter_1_-_Introduction is now superceded by https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Introduction
[07:00] <froud> the same may be true of
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 1 - Introduction
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 2 - Walkthrough
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 3 - Background
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 4 - Lab Layout
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 5 - Thin-Client Computing
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 6 - Software Components
[07:00] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Chapter 7 - Networking
[07:00] <highvoltage> froud: i would think so
[07:00] <froud> OK
[07:02] <froud> highvoltage: I take it that it is safe for me to assume that this lot is what actually represents the current cookbook?
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Educational
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Expanding
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/GettingStarted
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/GettingStarted/CoyoteRouter
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/HardwareRequirements
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Introduction
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Networking
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Preface
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/ServerConfiguration
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Software
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/ThinClient
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Walkthrough
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Worksheet
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Background
[07:02] <froud> # EdubuntuDocumentation/EdubuntuCookbook/Backups
[07:03] <highvoltage> froud: i can't see how it's unsafe, so i'm tempted to say yes.
[07:04] <froud> Well I just happended to find the pages that have Chapter X and thought I had better ask
[07:04] <froud> perhaps the idea was to redo the last pages in the first ones I listed?
[07:06] <froud> of course putting https://wiki.edubuntu.org/HowToCookEdubuntu/Chapters into the dubmix makes me wonder how many jigsaw puzzels we have on the table
[07:07] <froud> highvoltage: any idea where this went https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/WhyEdubuntu
[07:34] <highvoltage> ls
[07:34] <highvoltage> pggg... wrong keyboard
[07:34] <Burgwork> salut highvoltage 
[07:34] <highvoltage> hi Burgwork!
[07:35] <highvoltage> Burgwork: how are things?
[07:35] <Burgwork> pretty good
[07:35] <highvoltage> ogra: did you do some moving this weekend?
[07:36] <highvoltage> things are good for me too. i'm behind with everything and getting more so but i'm getting a lot done very quickly and it feels good.
[07:36] <Burgwork> yes, pretty behind myself
[08:17] <highvoltage> ogra: did you do some moving this weekend?
[08:18] <Reznor> highvoltage:  check pvt if ur not busy
[08:21] <ogra> highvoltage, thats still some months in the future ...
[08:21] <highvoltage> ogra: ok.
[08:21] <highvoltage> ogra: are you very busy now? Bluekuja and I want to talk to you about edubuntu testing.
[08:22] <ogra> first i have to do some renovation .
[08:22] <ogra> i prepared the house so far 
[08:22] <highvoltage> ogra: otherwise, ping us at any time when you have some free moments
[08:22] <highvoltage> ok, nice. how is that going?
[08:22] <ogra> slow, but fine 
[08:23] <ogra> i have to care for the whole household, the animals and my job alongside (most of that does my Gf usually) that slows me down a bit
[08:23] <highvoltage> understandable.
[08:24] <ogra> and since we cant terminate the contract effectively before aug. 1st, i have plenty of time
[08:24] <highvoltage> living together with my father is good, he takes care of all the 'house' stuff.
[08:24] <ogra> yeah
[08:24] <spacey> god i'm happy i don't live with my parents :)
[08:24] <ogra> the first release of edubuntu would never have happened without her support :)
[08:24] <highvoltage> with my father it's a 50/50 thing at least. for me it's not like living with a parent.
[08:25] <highvoltage> ogra: wow hey.
[08:25] <highvoltage> ogra: we should name something after her, or put in an easter egg referring to her :)
[08:25] <ogra> heh, yeah
[08:26] <ogra> i'll think about it :)
[08:26] <highvoltage> ogra: and about the testing?
[08:26] <ogra> lets do that tomorrow ...
[08:27] <highvoltage> ok, that's good for me.
[08:27] <highvoltage> Bluekuja: read last few lines ^^^
[08:28] <highvoltage> ogra: the edubuntu website is making some progress, although i would've liked it to go faster: http://proto.edubuntu.org
[08:28] <highvoltage> the drupal css is daunting :(
[08:29] <highvoltage> but i'm simplifying it so once that is done the rest of the theming and maintenance should be a breeze
[08:29] <ogra> it was your chioce ;)
[08:29] <highvoltage> yes, i know :)
[08:29] <Burgwork> highvoltage, a minor point, but we are "linux for young human beings", not gnu/linux
[08:29] <highvoltage> Burgwork: ok
[08:30] <Burgwork> I have heard that moin and zope are no calk walks either
[08:32] <Burgwork> there are a few ood colour things I noticed
[08:32] <Burgwork> search button is blue
[08:33] <highvoltage> yeah, that's where most of the css problems get me
[08:33] <highvoltage> i like the blue button :)
[08:33] <highvoltage> it's rebellious
[08:33] <Burgwork> it looks out of place
[08:33] <highvoltage> my colour problems are more with the text and the links.
[08:33] <Burgwork> yes, I was going to comment ont hat next
[08:34] <highvoltage> the theme we basically use is spreadfirefox, and the css is extremely integrated.
[08:34] <highvoltage> so you'd have two lines describing many things, so when you change a colour of one heading, you have to untangle that from all the other headings
[08:35] <highvoltage> so it's like a very tangled wire you have to sort out.
[08:36] <highvoltage> we started with spreadfirefox because it resembles some of the other ubuntu sites closely, but in hindsight it might have been better starting from one of the simple drupal themes, and building up from there.
[08:36] <highvoltage> herman also noted that the fonts are too small, the text will be bigger shortly
[08:36] <highvoltage> Burgwork: but i suppose we can turn the blue button into yellowy/orangy :(
[08:37] <Burgwork> yes
[08:37] <Burgwork> consistency is a good thing
[08:37] <Burgwork> if you have blue there, you need to have blue elsewhere
[08:37] <highvoltage> that one boy is wearing a blue t-shirt
[08:38] <highvoltage> and there's blue in the khangmand and kalzium screenshots :)
[08:38] <Burgwork> umm, that is not enough
[08:38] <highvoltage> oooh, and the kubuntu logo!
[08:39] <Burgwork> lol
[08:41] <spacey> bah, where does that failed to initialize HAL come from
[08:43] <highvoltage> spacey: i believe it's from a 60's movie called 2001: A Space Odysey
[08:45] <spacey> :p
[08:45] <spacey> also the failing part?
[08:46] <Burgwork> "I am sorry spacey, I can't do that"
[08:46] <highvoltage> HAL failed in a very bad way. it even killed people.
[08:46] <spacey> but now HAL is failing on my breezy terminal server :p
[08:46] <Bluekuja> back
[08:47] <spacey> actually you don't notice a thing
[08:47] <spacey> but the popup is annoying
[08:47] <Bluekuja> tomorrow when jon?
[08:47] <highvoltage> spacey: is this on an ltsp network?
[08:47] <highvoltage> ogra, Bluekuja: is 19:30 gmt+2 fine?
[08:48] <spacey> didn't log in with ltsp yet, i'm logged in with NX now
[08:48] <spacey> will try normal ltsp later this week
[08:48] <Bluekuja> nope for me no
[08:48] <Bluekuja> im a away
[08:48] <Bluekuja> i return home at 21:00
[08:48] <highvoltage> Bluekuja: when are you back? we can do it later, since we're staying up until 11:00.
[08:48] <Bluekuja> yeah 22:00
[08:48] <Bluekuja> is ok for me
[08:48] <highvoltage> ok
[08:49] <Bluekuja> 22 to 23
[08:49] <Bluekuja> 1 hour
[08:49] <Bluekuja> and then meeting
[08:49] <Bluekuja> perfect for me
[08:50] <Bluekuja> i start doing a work
[08:50] <Bluekuja> im here if you need something jon
[08:50] <Bluekuja> ;)
[08:50] <highvoltage> Bluekuja: ok, thanks!
[08:51] <Bluekuja> you're alwais welcome jon ;)
[08:52] <spacey> Apr 17 20:49:02 localhost gconfd (herman-14552): Adres "xml:readwrite:/home/herman/.gconf" getraceerd naar een schrijfbare configuratiebron op positie 0
[08:52] <spacey> *g*
[08:52] <spacey> syslog is full of it
[08:53] <spacey> why o why
[08:54] <spacey> not for a monday evening at least
[09:11] <enyc> error/me meeps at spac
[09:11] <enyc> ;-)
[09:16] <mgalvin> ogra: ping?
[09:41] <froud> anyone seen this page anywhere https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/CommonTasks
[09:47] <froud> another one seems to be missing https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/ClassroomUse
[09:47] <spacey> thats the old cookbook wiki part
[09:48] <spacey> currently were working in the HowToCookEdubuntu
[09:48] <froud> which is the new?
[09:48] <highvoltage> goodnight, #edubuntu
[09:48] <spacey> Guess it will replace the other pages later
[09:48] <spacey> bit confusing like this
[09:48] <spacey> anyway
[09:48] <spacey> i'm off to bed
[09:48] <spacey> goodnight
[09:48] <froud> spacey: this https://wiki.edubuntu.org/HowToCookEdubuntu/Chapters