=== cbx33 [n=pete@84-45-238-195.no-dns-yet.enta.net] has joined #edubuntu === jinty [n=jinty@94.Red-83-58-173.dynamicIP.rima-tde.net] has joined #edubuntu === HedgeMage [i=HedgeMag@freenode/staff/HedgeMage] has joined #edubuntu === P3L|C4N0 [n=gcamposm@200.121.237.218] has joined #edubuntu === raekism [n=raekism@c-68-38-189-125.hsd1.pa.comcast.net] has joined #edubuntu === ogra_ibook [n=ogra@ubuntu/member/ogra] has joined #edubuntu === bash [n=bash@pc-55-105-104-200.cm.vtr.net] has joined #edubuntu === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #edubuntu === P3L|C4N0 [n=gcamposm@200.121.237.218] has joined #edubuntu === raekism [n=raekism@c-68-38-189-125.hsd1.pa.comcast.net] has joined #edubuntu [05:59] in #suse === bash [n=bash@pc-55-105-104-200.cm.vtr.net] has joined #edubuntu === ogra_ibook [n=ogra@ubuntu/member/ogra] has joined #edubuntu === raekism [n=raekism@c-68-38-189-125.hsd1.pa.comcast.net] has joined #edubuntu === yvesC [n=yves@lns-bzn-50f-81-56-207-189.adsl.proxad.net] has joined #edubuntu === fxc065 [i=flck0565@70.134.78.181] has left #edubuntu [] [09:34] hmm the font is really small on the proto site === highvoltage [n=Jono@196.36.161.235] has joined #edubuntu === froud [n=froud@dsl-145-49-133.telkomadsl.co.za] has joined #edubuntu [10:22] hi [10:23] I have a strange question [10:24] I was told that some time ago a handful of people working on edubuntu has made a copy of the tuxlab cookbook [10:24] question is, did anything come of that and if so where can I find the new product? [10:26] highvoltage: ping [10:27] froud: pong [10:27] waz up dude [10:27] I am on a lost content hunt [10:28] froud: pieces of the edubuntu cookbook does exist [10:28] ah ha [10:28] point me [10:28] just a moment... [10:30] froud: pygi is managing the new new version [10:30] https://wiki.edubuntu.org/HowToCookEdubuntu/Worksheet [10:30] we have the getting started guide ~90% complete: http://proto.edubuntu.org/gettingstarted === froud goes see [10:33] where is the src kept [10:34] highvoltage: see most on hold, was wondering if I could perhaps get src to diff with tuxlab [10:35] highvoltage: also I must figure out how to deliver a tuxlab and incorporate edubuntu [10:35] highvoltage: seems openlabs is not answering email, so dunno about them [10:36] froud: they exist in some wiki pages... just a sec.. [10:37] froud: https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook [10:37] https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Background?highlight=%28Cookbook%29 [10:38] https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Chapter_1_-_Introduction?highlight=%28Cookbook%29 [10:38] https://wiki.edubuntu.org/EdubuntuDocumentation/EdubuntuCookbook/Chapter_2_-_Walkthrough?highlight=%28Cookbook%29 [10:38] wiki search might be your best bet. [10:38] on the question on the e-mail you sent me, [10:39] we got that PDF from Hilton, the original file died with an older laptop :( [10:39] eihna! [10:41] chatting with jerome [10:41] he has stuff in ubuntu-docs svn [10:42] question is which is more updated [10:42] as for doing docs in wiki [10:42] wiki is like a content motel, stuff checks in but never checks out :-( [10:44] yeah. hotel california. [10:44] lucasvo: got your e-mail [10:45] jerome reckons svn is more updated than wiki [10:45] lucasvo: the idea is to go with a child-friendly look for now, and mature it gradually as the distribution matures [10:45] seems he was trying to port the docbook xml to wiki [10:45] i couldn't say for sure, but i trust jerome, if he says it's more updated, i would be inclined to believe him. === Sergi0 [n=serge@ip227-28-166-62.adsl.versatel.nl] has joined #edubuntu [10:46] :-) lol [10:46] jah [10:53] highvoltage: hm, but why not be mature from the beginning? [10:54] an unmature design isn't very helpful to make the distribution more mature [10:54] lucasvo: well, the first release is aimed at primary school classroom only [10:55] lucasvo: and the release later this year would be primary and high school, after that whole school, and then university as well [10:55] as I said, the teacher make the decision, and they expect it to be mature [10:55] lucasvo: yes, so it's about managing expectations [10:56] I would put the navigation box to the right [10:56] what's the status of schooforge? === juliux [n=juliux@ubuntu/member/juliux] has joined #edubuntu [10:58] highvoltage: did k12 ever make use of tuxlab cookbook? [10:58] lucasvo: yep, we'll look at that [10:58] froud: schoolforge, you mean? [10:58] froud: i don't think they did [10:58] yah my bad [10:59] hmm, pity [10:59] froud: wrt K12, the tuxlab cookbook was very specific to this project [10:59] schoolforge doesn't seem to be active, very much, at least not the last year or so. [10:59] so no slaves there :-) [11:00] last update was 2003 [11:01] so how active are k12 team? [11:01] k12ltsp team is quite active. [11:02] their main work is to get the release available each time a new FC is released. [11:02] it's a lot of work, but they keep up. [11:02] and they've done lots of small enhancements to FC that we have taken in tuxlabs for ubuntu [11:03] I am pondering .. how to get focus on tuxlabs but remain flexible to the needs of projects such as edubintu and k12 [11:03] 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] highvoltage: ok [11:04] froud: that is a bit of a toughie, since we'll have some software changes that will stay specific to ubuntu :/ [11:04] I like the modular tuxlab approach [11:04] 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] * [11:05] Software Module [11:05] * [11:05] Technical Module [11:05] * [11:05] Content Module [11:05] * [11:05] Training Module [11:05] * [11:05] Management Module [11:05] highvoltage: how would you want do it? [11:05] * [11:05] Support Module [11:05] * [11:05] Volunteer Module [11:05] * [11:05] 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] Sustainability Module [11:05] oops [11:05] sorry bout that :-) [11:06] highvoltage: ok, yes [11:06] highvoltage: but then we are doing the work twice [11:06] highvoltage: the main problem is the difference that will happen in the Content Module [11:06] lucasvo: we'll probably do it more than twice. possibly every six months, at most. [11:07] and making a design like this for only 6 months [11:07] 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] highvoltage: oh and of course the software module [11:07] froud: i hope we get them mostly good quality before release [11:07] I don't know, if the work is worth only beeing used for 6 month [11:07] .me looks around for release date :-) [11:07] highvoltage: but, yeah, we can try [11:08] 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] highvoltage: quality aside, do you agree that the main issue is in the Software and Content Modules [11:09] highvoltage: I would keep the colored footer from the old design [11:10] froud: i'm not sure i understand what you mean? [11:10] lucasvo: that was mainly discussed at the edubuntu summit in london === cbx33 [n=pete@84-45-238-195.no-dns-yet.enta.net] has joined #edubuntu [11:11] lucasvo: you might find some meeting notes if you search for summit in the wiki [11:11] 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] froud: yes, i would tend to agree there [11:12] highvoltage: that said we have replaced a problem with a smaller one [11:12] highvoltage: question is can we live with it [11:13] highvoltage: would edubuntu agree to using the other modules if they were branded as edubuntu [11:13] highvoltage: I am considering repurposing at first level just using brand changes [11:14] highvoltage: this way I can setup the Software and Content Modules with conditional processing to profile outputs for edubuntu and tuxlab respectively [11:15] froud: edubuntu's cookbook goals are slightly different to the tuxlab one [11:15] this assumes there will be some common content in these modules that is used by both projects [11:15] froud: the cookbook goals for edubuntu has also changed quite a bit a few times [11:15] highvoltage: has it stabilized? [11:15] froud: atm, the biggest goal for the edubuntu cookbook is just to get all the essential documentation complete [11:16] 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] froud: i distanced myself a bit from the cookbook initially, and considered myself more of an upstream maintainer [11:17] So how do you see the difference between edubuntu cookbook and tuxlab cookbook [11:17] froud: but got involved again in tha last few weeks, since we're having trouble getting to a finished cookbook state [11:17] 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] froud: but if you're talking in terms of making diffs between the two, they're very, very, very different [11:18] it's practically a cookbook from scratch. [11:18] as far as i understand it. [11:18] highvoltage: don't you think it will make more sense to gather around a common structure [11:19] yes, i do. [11:19] assuming I get OK to work on this for tuxlab [11:19] then edubuntu can capitalize on the work [11:20] at present we have two documentation projects that are going nowhere slowly [11:20] I think we can get one that is going somewhere slowly :-) [11:21] but it will take consolidation and cooperation with edubuntu team [11:21] hehe! [11:22] well put. === pygi [n=pygi@83-131-246-128.adsl.net.t-com.hr] has joined #edubuntu [11:22] spacey: alive? :) [11:22] hi [11:22] yes [11:22] pygi: froud has lots of questions about the cookbook :) [11:22] pygi: i think you should speak to him [11:22] spacey: like the worksheet? :) === pygi pokes froud :) [11:23] highvoltage: I think the current edubuntu.com design looks more mature than the design of proto.edubuntu.org [11:23] hey pygi [11:23] lucasvo: then we definately have to smooth out proto much more [11:23] froud: hello [11:23] how may I help you? :) [11:23] pygi: how would you define the status of the edubuntu cookbook [11:24] Status: Being written :) [11:24] froud, pygi: what do you think? which design is more mature: www.edubuntu.org or proto.edubuntu.org? === froud can't go there now [11:24] pygi: I may get OK to work on Tuxlabs [11:24] at least the font on proto is really small here [11:24] lucasvo: please make that red a little ligther? :) [11:25] pygi: in which case I would like to bring together opportunities for both tuxlabs and edubuntu [11:25] pygi: I don't have access to proto.edubuntu.org [11:25] highvoltage does? [11:25] yes [11:25] pygi: the current tuxlab project plan http://wiki.tsf.org.za/shuttleworthfoundationwiki/TuXlab/HowTo [11:25] froud: that is great, but for dapper we have just 1 chapter left untaken, about artwork if I am not mistaken [11:26] pygi: it's a modular approach [11:26] pygi: where are the sources [11:26] pygi: but which red do you meaan? [11:26] all red, and all orange...too bright [11:27] froud: what sources do you need? [11:27] pygi: what src do you have [11:27] ahh, so I am not the only one, thinking the design is too "funky" :) [11:27] pygi: for edubuntu cookbook [11:28] 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] I know of stuff in ubuntu-doc svn and in wiki, do you have something else? [11:28] hm, no, not really [11:28] other is being written :) [11:28] pygi: according to this it's ONHOLD https://wiki.edubuntu.org/HowToCookEdubuntu/Worksheet [11:29] only sction is the install http://proto.edubuntu.org/gettingstarted [11:29] froud: well, it's outdated :) [11:29] pygi: OK so what is the status? [11:29] well, "Being written" is the status :) [11:29] where can I view development [11:30] for now nowhere..until we upload all [11:30] is there a way that I can partake in the development (collaborate) [11:30] hmmm [11:30] yes, ofcourse [11:30] but currently only on this chapter "Look & Feel (Maintain artwork package,Fit your needs) " [11:30] because we have authors for all others [11:30] highvoltage: I'll try to come to next edubuntu meeting [11:31] https://wiki.edubuntu.org/HowToCookEdubuntu/looknfeel [11:31] that chapter goes to upper URL [11:31] pygi: so at present the doc effort is not following the open source development model? [11:31] froud: no, that is wrong thinking :) === froud is now confused [11:31] froud: you have a link to the open source development model? [11:32] Everything will be visible as soon as we update the pages, and write more [11:32] I don't want to update pages for 2 words :) [11:34] froud: do you understand? :) [11:34] 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] pygi: help me out here [11:35] pygi: speaking to highvoltage wee agree that the only problem areas [11:36] between what is tuxlab and edubuntu relate to Software and Content [11:36] other than this stuff like hardware, manaement and support are common between the projects [11:37] this enables both projects to repurpose the common content [11:37] pygi: do you think it might be a good idea to schedule another cookbook meeting? [11:37] froud: agreed [11:37] highvoltage: what for this time? [11:37] now all we need is a way to accomodate the differences between projects [11:37] pygi: then we could have everyone there, then it's easier to make decisions [11:37] highvoltage: let's first write all, then meeting, ok? [11:37] pygi: just for collaboration, it doesn't have to change anything [11:37] froud: agreed [11:38] pygi: sure, sounds good [11:38] pygi: here is the thing, I need to update for tuxlab [11:38] pygi: but would be nice to help edubuntu [11:38] pygi: so I am tasked with merging the best form all and providing a since source that all can use [11:39] pygi: so for tuxlab there will be tuxlab info [11:39] 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] and brand [11:39] same for edubuntu [11:39] froud: agreed, but... [11:39] froud: we should really both be able to get something from the cookbook, but at the moment cookbook is very fragile... [11:39] highvoltage: yes, that is part of what I must now do.... consolidate [11:39] and we can't allow to change things so much :-/ [11:40] froud: do you know how long it took us to get things of the ground? [11:40] pygi: there are two ways forward === pygi listens [11:41] pygi: 1. Tuxlabs moves forward independant of edubuntu [11:41] pygi: 2. Tuxlabs and Edubuntu move forward toegtehr [11:41] the later takes compromise on both sides [11:41] both projects have interests [11:41] froud: agreed [11:42] my task is to protect the interests of both [11:42] 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] while enabling lower maintenace cost, higher quality [11:42] froud: agreed [11:43] pygi: if this derails your targets, then we need to look toward after your targets [11:43] in the interim, tuxlabs will proceed and will just take into consideraton that it must embrace edubuntu [11:44] 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] I know [11:44] we battled a really heavy battle to get it off ground :-/ [11:44] pygi: i like keeping things simple. [11:44] highvoltage: meaning in real words? :) [11:44] pygi: froud = http://learnlinux.tsf.org.za/authors/web-os-team.html [11:44] jane_: here? :) [11:45] pygi, froud: in real words, it means that whatever we do, it shouldn't add more overheads to the project [11:45] http://learnlinux.tsf.org.za/courses/web-tuxlabs.html [11:45] actually it removes overheads [11:45] imho, someone can right it in MS-word for all that I care. as long as we get the docs written [11:45] :-) === pygi opens MSword :) [11:46] grrr [11:46] :) [11:46] highvoltage: the requirements I have are [11:46] 1. Update Tuxlab [11:46] 2. merge info from openlabs and edubuntu to tauxlab [11:47] 3. Enable tuxlab as upsteam to such projects [11:47] 4. Provide method for such project to benefit [11:47] 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] 5. Make it free and open [11:47] by when do you have to update tuxlab? [11:48] pygi: laying down the planning [11:48] pygi: but it is hard to accomodate edubuntu without transparency to development versions [11:48] froud: agreed [11:49] froud: There will be more often updates [11:49] if that can help you :) === froud nods and smiles [11:49] there, a compromise :) [11:50] now, you write a artwork section of edubuntu cookbook :) [11:50] If that is what it takes [11:50] nah, I was just joking...you don't have to write anything if you don't want, no worries :) [11:50] highvoltage: You need to update that article of urs to accommodate cookbook [11:50] ok now one more thing === pygi listens again [11:51] tuxlab requirements are to be in docbook xml [11:51] pygi: ok [11:51] highvoltage: it's just we don't need "Why" and such things [11:51] downloading will go somewhere else as well [11:51] the documents will later be converted into POT files and Tuxlab will be submited to Launchpad and rosetta [11:52] froud: hm, well, for now we are and will be doing on Wiki [11:52] once it's written, it'll change to other formats probably [11:52] pygi: if tuxlab goes launchpad so will edubuntu [11:52] once easier to distribute [11:52] one* [11:53] wiki is nice but not IMHO good for doing documentation properly [11:53] it simply s not portable enough [11:54] the other option is DITA [11:54] froud: agreed, but wiki is fine for now, don't you agree? [11:54] but the knowledge of DITA in the FOSS world is not strong enough [11:55] pygi: well, tuxlab is in docbook and is also in ubuntu-doc svn [11:55] froud: well, the cookbook will most probably be in docbook as well once it is written [11:55] the files on wiki are a port by jerome to wiki [11:56] I have three srcs of * coookbook [11:56] 1 in ubuntu-doc svn [11:56] this one is jeromes stuff for eduubuntu [11:57] 2. at svn in upfront system [11:57] this was original from Jean Jordaan [11:57] and 3 in the learnlinux svn [11:58] a copy of the upfront version [11:58] the stuff on wiki, according to jerome, is not as updated as the stuff in ubuntu-doc svn [11:59] pygi: this is why I want to compare your stuff, to see which is most update [11:59] I must bring it altogether in a single place [11:59] froud: I am aware of that, and you'll get ur docbook, but I don't think it'll happen this second :) [12:00] hm, what about this? [12:00] don't need dobook now, just the current format will do :-) [12:02] 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] pygi: that asumes too much [12:03] froud: nah, not really [12:03] pygi: if we are both developing in a hole [12:03] pygi: them we may be to far appart [12:03] froud: perhaps it does, but i think it will help get the edubuntu-docs out asap [12:03] froud: i think we can get the two parts together again later, don't you? [12:03] highvoltage: if we can see what edubuntu docs are [12:04] at present I have no way of knowing [12:04] froud: we agreed that we'll update it more often :) [12:04] so where can I see what is current [12:04] for now, nowhere [12:04] :-( [12:04] but there is not much written except highvoltage's, which needs modification [12:04] froud: for now, it might be safest to assume that there are no edubuntu docs === froud feels like he is going in sqquare circles === JaneW [n=JaneW@dsl-146-135-68.telkomadsl.co.za] has joined #edubuntu [12:05] welcome JaneW [12:05] highvoltage: ok I am going to recomend as follows [12:05] we cannot repurpose content from edubuntu [12:05] yet [12:05] therefore [12:06] either tuxlab waits [12:06] or tuxlabs just does its own thing based on edubuntu [12:06] I would suggest waiting [12:06] then I'll help you integrate [12:06] and we'll have tuxlabs ready the date the dapper is out [12:07] 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] froud: agreed, but there will be things written [12:08] pygi: the sooner we can see what is written, the sooner we can help [12:08] in my opinion, i would let both do its own thing for now, then merge again later [12:08] highvoltage: I think that is what jason will say [12:08] JaneW: are you alive? :) [12:09] 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] i think everyone agrees that we can, will, and must collaborate. [12:09] i also don't think that it has to happen right now. [12:09] sorry- [12:09] i mean- [12:09] no, that's right. multitaksing here [12:10] froud: hm, can we just integrate edubuntu right into it once the entire cookbook is written? [12:10] highvoltage: yes, but costing the tuxlab stuff ... repurposing edubuntu now will reduce investment [12:11] pygi: wont be so easy if we don't have the same conventions and structuring [12:11] pygi: in design of tuxlabs the information architecture will be such that it is modular [12:11] hm, all of this should have been discussed earlier, much earlier [12:12] pygi: tuxlab discussion has been done, but now I am looking for intel from edubuntu [12:12] info that can help us plan the architecture so that edubuntu can be easily incorporated [12:13] well, you can see the chapters/parts structure, but that probably isn't helpful enough [12:13] pygi: this has been discussed before [12:13] 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] highvoltage: yes, I know [12:13] pygi: with the very first edubuntu cookbook structure, we were going to copy exactly from tuxlab cookbook [12:14] froud: keep in mind though, that tuxlab cookbook structure has changed too [12:14] highvoltage: but this is not the very first structure, so... [12:14] highvoltage: tuxlab remains with the same outline [12:14] the new stuff from tsf is different [12:15] and will impact on the tuxlab cookbook v2 === pygi thinks we are rounding all the time around the same things === froud sees square circles === pygi confirms froud's seeings :) [12:16] oki doki [12:16] pygi: highvoltage: thanks for the information [12:16] froud: so, what are we to decide? [12:17] pygi: without current visability into edubuntu cookbook [12:17] I must assume that what is in edubuntu wiki and ubuntu-doc svn is the most current [12:18] I will therefore, based on the new tuxlab modular structure [12:18] http://wiki.tsf.org.za/shuttleworthfoundationwiki/TuXlab/HowTo [12:19] will be back in a sec [12:19] proceed with merging new tuxlab data + old tuxlab cookbook + edubuntu wiki stuff into tuxxxlab v2 === pygi_ [n=pygi@83.131.234.83] has joined #edubuntu === pygi_ is now known as pygi [12:20] pygi: did you get that last message [12:20] froud: your choice after all...yes, I did.. [12:21] froud: keep in mind though, that things like the tuxlab software installation will be quite different to the edubuntu one [12:21] froud: for instance, we'll have a two button server install [12:21] highvoltage: yes, I will profile the differences as I capture them from the differnt sources [12:22] IOW, If I find reference to this 2-button install [12:22] I will profile this difference as edubuntu [12:23] 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] froud: you won't find a reference to this install yet, it's currently undocumented :) [12:23] froud: ok [12:24] highvoltage: are we to document it in cookbook? [12:24] highvoltage: perhaps we need to pass progress information from tuxlab to edubuntu === froud ponders the problem of where to do the work [12:27] highvoltage: we have src in learnlinux repos [12:27] and ubuntu-doc [12:27] and wiki [12:28] open a new repos at edison or use an existing repos [12:28] ? [12:28] ironic thing is that tuxlab does not have its own svn [12:28] :-) [12:28] froud: perhaps better served on ubuntu server? you know how we feel about edison ;) [12:29] edison rocks [12:29] and it's much easier to give commit accounts :-) [12:29] hehe. i thought you hated it :) [12:29] no [12:29] svn is solid [12:29] it's everything else that bothers === sankarshan [n=sankarsh@202.149.56.110] has joined #edubuntu [12:30] is it ok to discuss edubuntu/tuxlab cookbook stuff on edubuntu-devel [12:31] there is no edubuntu-devel [12:31] I mean the mailing list? [12:31] yup, it probably is [12:32] OK, so if we use svn @edison and edubuntu-devel mailing list for mail [12:32] and this irc for chat ;-) [12:32] ok, but I'll be out for 3 days, so don't count me in :) [12:33] that way, edubuntu team can be inline to tuxlab devel [12:33] pygi: np [12:33] highvoltage: is this ok [12:33] anyway, you still have the option to wait until May, 10 :) [12:34] pygi: I must keep the interests of tuxlab in mind [12:34] froud: i don't think there's any problem with discussing tuxlab stuff on edubuntu-devel [12:34] yes, yes [12:34]