[11:29] <bashelier> @schedule Paris
[11:29] <ubotu> Schedule for Europe/Paris: 06 Jun 22:00: Edubuntu | 07 Jun 22:00: Ubuntu Development Team | 12 Jun 17:00: Kernel Team | 13 Jun 14:00: Edubuntu | 14 Jun 18:00: Ubuntu Development Team | 16 Jun 19:00: Xubuntu Developers
[03:35] <DarkSun88> Hi all
[09:13] <juliux> @schedule
[09:13] <ubotu> Schedule for Etc/UTC: 06 Jun 20:00: Edubuntu | 07 Jun 20:00: Ubuntu Development Team | 12 Jun 15:00: Kernel Team | 13 Jun 12:00: Edubuntu | 14 Jun 16:00: Ubuntu Development Team | 16 Jun 17:00: Xubuntu Developers
[10:00] <LaserJock> time?
[10:01] <willvdl> LaserJock, 10pm
[10:01] <ogra> same here :)
[10:01] <LaserJock> 1pm here
[10:01] <LaserJock> silly people
[10:01] <ogra> heh
[10:01] <ogra> todays meeting would have been a EC meeting
[10:02] <ogra> whatever that means nowadays ...
[10:02] <LaserJock> ah, that reminds me
[10:02] <LaserJock> well, we do have a fairly big pile of applicants
[10:02] <ogra> well, nobody o the agenda
[10:02] <ogra> i just looked
[10:02] <LaserJock> I approved stgraber the other day
[10:02] <LaserJock> well, I'm not sure that people know they need to be added
[10:02] <ogra> i wonder if the procedure is to unclear
[10:03] <willvdl> I'll look into it
[10:03] <LaserJock> we can fix that on the team description
[10:03] <willvdl> if it isn't it probably is my fault :)
[10:03] <ogra> The Edubuntu council will review membership candidates at every first meeting in a month, please add yourself below and subscribe to [WWW]  https://launchpad.net/people/edubuntu-members. Note that the same membership rules as in Ubuntu apply.
[10:03] <ogra> from the agenda page ...
[10:03] <willvdl> we should have it on the wiki
[10:03] <LaserJock> but the EC *has* technically run out
[10:03] <ogra> with a bit adjustment it should fit for the team page
[10:04] <pips1> can we vote on including someone as a member in his/her absence?
[10:04] <ogra> LaserJock. ?
[10:04] <LaserJock> yes, people us LP for teams these days, wiki pages don't necessarily get done
[10:04] <LaserJock> ogra: the EC memberships where for 2 releases, which ended with Feisty's release
[10:04] <LaserJock> *were
[10:04] <ogra> oh, we need to refresh then
[10:04] <ogra> unless someone wants to step back
[10:05] <LaserJock> well, I somehow feel like we should have some sort of procedure for this
[10:05] <ogra> well, we should keep such discussions for meetings where the full EC is around
[10:05] <LaserJock> yes, you're right
[10:05] <ogra> i'd like to have highvoltage ad RichEd attending for such stuff
[10:06] <LaserJock> sure
[10:06] <ogra> anyway, lets get started ...
[10:06] <pips1> I vote for Gavin MCullagh as edubuntu member, he rocks! :-)
[10:06] <ogra> i'll try to keep tech as short as possible today, since i'm currently trying to get the liveCD fixed aside here
[10:06] <ogra> pips1. right, but he needs to attend the meeting at least
[10:07] <ogra> i'd happily approve him indeed
[10:07] <ogra> i'll mail him about it
[10:07] <pips1> good idea
[10:07] <ogra> ok, anyway, the tribe1 CD is due tomorrow ...
[10:08] <ogra> https://isotesting.stgraber.org/isotesting/iso/Edubuntu
[10:09] <ogra> the liveCD is still oversized and due to a bug in the build system it couldnt get fixed until now, i'm working on getting a properly sized iso done tonight though
[10:09] <ogra> the i386 CD should be fine for use and not be much different to gutsy
[10:09] <ogra> please test as you can ...
[10:10] <ogra> ltsp ...
[10:10] <LaserJock> are there any notes for what to test on the Desktop CDs?
[10:10] <ogra> one of our biggest bootspeed issues, X detection will be dropped in the next upload
[10:10] <LaserJock> or is there no link because they aren't built yet
[10:10] <ogra> LaserJock. live session and ubiquity for now
[10:10] <ogra> its only the first milestone
[10:10] <ogra> its fine if it roughly works
[10:11] <LaserJock> I can do most of i386 tonight I think
[10:11] <willvdl> ogra, what does it mean to drop X detection?
[10:11] <ogra> willvdl. 20seconds fsater boots
[10:11] <ogra> *faster
[10:11] <willvdl> I mean what does X detect do :)
[10:11] <LaserJock> willvdl: we were doing autodetection of X on the clients
[10:11] <willvdl> server checking for X on the clients?
[10:11] <LaserJock> for automatically setting up X on the clients
[10:12] <ogra> xorg 7.3 and the new xrandr can detect the X setup at runtime now, so no xorg.conf is needed anymore
[10:12] <LaserJock> the Xorg "magic"
[10:12] <willvdl> gotcha
[10:12] <LaserJock> so are we just not using autodetection?
[10:12] <ogra> before we had a script that ran dpkg-reconfigure xserver-xorg on boot which was very time consuming
[10:12] <willvdl> great, cause xorg.conf is a mystery to me :)
[10:12] <ogra> LaserJock. right
[10:13] <LaserJock> ugg, dpkg-reconfigure on every boot?
[10:13] <LaserJock> that's no fun
[10:13] <ogra> i will leave the code in but add an option for lts.conf to force its usage, by default we'll use xorg's magic
[10:13] <ogra> it makes the booting incredibly fast
[10:13] <ogra> and worked on all clients i tried it on
[10:14] <ogra> two issues are left with that though
[10:14] <ogra> funny mouse setups ...
[10:14] <ogra> (27 button cybermice with 4 scrollwheels and vibrator)
[10:15] <ogra> they might be problematic t set up in the beginning ...
[10:15] <ogra> nad keyboards ...
[10:15] <ogra> *and
[10:15] <willvdl> four that cousin that looks like your brother?
[10:16] <ogra> i'm not sure yet how to handle keyboard settings ... there are several options
[10:16] <ogra> anyway, that will be a major change in tsp and a big step forward technically
[10:16] <ogra> *ltsp
[10:16] <willvdl> a post config script perhaps?
[10:16] <ogra> yes, indeed
[10:17] <ogra> or simply running xmodmap after x startup
[10:18] <ogra> thats about all i have to say about tech today ...
[10:18] <ogra> i sent the priority list for specs to Keybuk, but he didnt assig the prios yet
[10:18] <LaserJock> I'm a little closer to core-dev
[10:19] <ogra> due to time costraints RichEd and i didnt have the opportunity to go through approving yet either
[10:19] <LaserJock> hopefully soonish I'll have a interview with the TB and they'll decide
[10:19] <ogra> yeah, to bad that didnt happen yesterday
[10:19] <LaserJock> I'm working on categorization for the add-on CD
[10:20] <LaserJock> ogra: I've got a tech question for you about that, what do we ship from XFCE4?
[10:20] <LaserJock> do we ship a complete xfce4 on the add-on CD?
[10:20] <ogra> its in the ship-addon seeds, let me look
[10:21] <LaserJock> hmm, from the seed it looks pretty complete
[10:21] <LaserJock> but it's a bit hazy from the .desktops
[10:21] <ogra> http://paste.ubuntu-nl.org/24479/
[10:22] <LaserJock> because there are only .desktops for like the plugins
[10:22] <ogra> a xfce-meta.desktop file ?
[10:22] <ogra> or edubuntu-xfce
[10:22] <LaserJock> anyway, by looking at the current CD contents I came up with the following categories
[10:23] <LaserJock> ogra: yeah, that's what I'm thinking we need
[10:23] <ogra> good, lets have it :)
[10:23] <LaserJock>  * Young Children
[10:23] <LaserJock>  * Graphics
[10:23] <LaserJock>  * Science
[10:23] <LaserJock>  * Extras
[10:23] <LaserJock>  * KDE Edutainment
[10:23] <LaserJock>  * XFCE4
[10:23] <ogra> i dont like XFCE4
[10:24] <LaserJock> as a category or period? :-)
[10:24] <ogra> how bout something like * Light Desktop (xfce)
[10:24] <LaserJock> ok sure
[10:24] <ogra> nobody has an idea what XFCE might mean
[10:24] <ogra> apart from us probably
[10:24] <willvdl> what does it mean? :)
[10:25] <LaserJock> so those categories are what would be in the g-a-i menu
[10:25] <LaserJock> any other suggestions?
[10:25] <willvdl> LaserJock, what about collaboration stuff? e.g. moodle, other cms's
[10:25] <ogra> * Games ?
[10:25] <LaserJock> well, we don't have those yet
[10:25] <LaserJock> ogra: well, I was thinking that the games would go in "Young Children"
[10:26] <ogra> ah
[10:26] <LaserJock> do we have games for older people on there?
[10:26] <ogra> right
[10:26] <willvdl> could we pslit the kde-edu stuff into the categories? probably not, it's one package right?
[10:26] <ogra> ot yet
[10:26] <ogra> but its surely possible
[10:26] <LaserJock> well, we can split them up
[10:26] <LaserJock> in the menu
[10:26] <LaserJock> but at this point I wonder if people are more thinking "I'm looking for the KDE edu stuff"
[10:26] <willvdl> cause kde-edu has maths, science, language...
[10:26] <LaserJock> sure
[10:27] <LaserJock> what I was planning
[10:27] <willvdl> LaserJock, except those who have o idea what it is
[10:27] <ogra> right
[10:27] <LaserJock> is if we get more apps for other categories we split it up
[10:27] <LaserJock> but I don't want a category with one item I guess
[10:27] <LaserJock> or would that be fine?
[10:27] <willvdl> sounds right
[10:27] <ogra> well
[10:27] <willvdl> makes sense.
[10:27] <ogra> yep
[10:28] <LaserJock> we have 53 .desktops right now
[10:28] <LaserJock> 17 of them are xfce
[10:28] <LaserJock> roughly 15 KDEEdu
[10:29] <LaserJock> well, the other thing is, what is the best way to get testing of this?
[10:29] <LaserJock> I could manually adjust the menus and desktops
[10:29] <LaserJock> and rebuild the .iso
[10:29] <ogra> add info how to test it to the testing procedures
[10:29] <LaserJock> but I'm not sure if that's helpful for people to have to download the whole .iso to test
[10:29] <ogra> oh, you mean during development
[10:29] <LaserJock> yes
[10:30] <ogra> well, you should rsync
[10:30] <ogra> and we should work on the real iso
[10:30] <ogra> it wont change much so the rsyncs will be very fast
[10:30] <LaserJock> well, I guess I just need to bug cjwatson and figure out how that app-install directory gets on there
[10:31] <LaserJock> if it's fairly easy then I can make adjustments and we can see the results in the dailies
[10:31] <ogra> right
[10:31] <LaserJock> alright, I think that's enough from me
[10:31] <ogra> at least if mvo cant help
[10:31] <LaserJock> I asked mvo and pitti already
[10:32] <ogra> i always thoght app-install-data was responsible
[10:32] <LaserJock> well, my question is how it actually ends up on the .iso
[10:32] <LaserJock> perhaps I'm not clearly stating my question
[10:33] <LaserJock> I don't think I have access to the build scripts that do that part
[10:33] <ogra> hmm
[10:34] <LaserJock> I looked through ubuntu-cdimage and couldn't find anything
[10:34] <ogra> right
[10:34] <LaserJock> I mean, the app-install directory is like what app-install-data provides
[10:34] <ogra> well, colin might be able to help
[10:35] <LaserJock> but I don't know where to tap into to get my modifications on the add-on CD
[10:35] <ogra> yep i understand
[10:35] <ogra> more tech questions ?
[10:35] <LaserJock> I'm good I think
[10:35] <willvdl> not here
[10:36] <ogra> then lets move on
[10:36] <ogra> docs ?
[10:36] <willvdl> well, I'd like to do website first if that's OK?
[10:36] <LaserJock> well, nixternal is scheduling a Doc Team meeting
[10:36] <ogra> indeed
[10:36] <LaserJock> I'm listed as required to attend for Edubuntu
[10:36] <LaserJock> that's all from me
[10:36] <willvdl> LaserJock, I'll do my bit to be there
[10:36] <ogra> cool
[10:37] <LaserJock> willvdl: that would be good
[10:37] <willvdl> I'm behind on the procedures. the kenya trip threw me a bit
[10:37] <mvo> ogra, LaserJock: I did some hacking with cjwatson on this, but I can't remember what bzr branch was responsible for this (colin did most of the work on the cdimage front)
[10:37] <willvdl> but matt east has done good work with the team page
[10:37] <ogra> mvo. i'll find out, thanks
[10:37] <willvdl> it's way better than my attempt tod escribe things :)
[10:37] <LaserJock> mvo: ok, thanks.
[10:38] <pips1> willvdl: link?
[10:38] <willvdl> erm, wiki.ubuntu.com/DocTeam or something
[10:38] <willvdl> I'm a wiki editor for help.u.com now
[10:39] <willvdl> so I can remove those annoying old and duplicated cookbooks
[10:39] <ogra> cool
[10:40] <LaserJock> DocumentationTeam probably
[10:42] <willvdl> it's good anyway
[10:42] <willvdl> shall we chat website?
[10:42] <ogra> shoot
[10:42] <willvdl> did anyone discuss it last week?
[10:42] <pips1> well,...
[10:42] <pips1> I kind of missed my cue last time
[10:43] <LaserJock> I don't remember last week
[10:43] <pips1> when I started my report, everybody had gone already ;-D
[10:43] <willvdl> urk
[10:43] <LaserJock> oh, wait, that would've been 5am, I wasn't here
[10:43] <willvdl> lazy boy
[10:43] <LaserJock> blah, I was up til 3am last night with Ubuntu stuff
[10:44] <willvdl> ok, I checked minutes form previous week
[10:44] <willvdl> items are:
[10:44] <willvdl> drupal 5.1
[10:44] <willvdl> theme template
[10:44] <nixternal> willvdl: I will let you know the date and time of the meeting...what is a "best" time for you?
[10:44] <willvdl> and our own customisation
[10:44] <pips1> right
[10:44] <willvdl> nixternal, my evenings. I'm UTC+2
[10:45] <willvdl> actually, the timezones normally work out OK for me. jsut not a weekend :)
[10:46] <willvdl> pips1, have you or highvoltage received anything from newz2000?
[10:46] <pips1> highvoltage volunteered to customise the template, apparently, he got the template from matt nuzum and started working on it. last week, he said he would put up the reworked template for comments... as soon as he is ready
[10:46] <pips1> haven't spoken to highvoltage since, though
[10:47] <willvdl> OK good news
[10:47] <LaserJock> he's probably off starting a new company
[10:47] <LaserJock> slacker
[10:47] <LaserJock> ;-)
[10:47] <pips1> as for me, I have been busy with my day job :-/ nothing to report really :-(
[10:47] <willvdl> pips1, likewise :(
[10:47] <pips1> heh
[10:47] <willvdl> as soon as we have that template, let's setup the proposed edubuntu-website team
[10:48] <willvdl> and brainstorm our content
[10:48] <willvdl> wiki vs web etc.
[10:48] <pips1> well, no need to wait for the template to brainstorm on content, really
[10:48] <willvdl> meaning, how to fit what into where. but yes, you're right :)
[10:48] <nixternal> just put a picture of me on there and you sell cds like hotcakes!
[10:49] <LaserJock> sell like hotcakes where?
[10:49] <willvdl> nixternal, are you the little girl on the edubuntu cover?
[10:49] <pips1> nixternal: hehe
[10:49] <willvdl> hawwtckes
[10:49] <nixternal> I hope not
[10:49] <LaserJock> willvdl: lol
[10:49] <pips1> willvdl: lol
[10:49] <nixternal> gahaha
[10:49] <ogra> heh
[10:49] <LaserJock> well, I think it's a good idea to brainstorm the web content on the wiki
[10:50] <pips1> ok
[10:50] <LaserJock> then when it's been tossed around enough, get it cleaned up and put in drupal
[10:50] <LaserJock> we need to focus people to edubuntu.org
[10:50] <LaserJock> as the primary starting point
[10:50] <willvdl> yeah. as much static info on there as possible rather than wiki
[10:51] <LaserJock> so we need to make sure that the stuff people really need is either on there or linked from there
[10:51] <LaserJock> it's not bad to have a short bit on something and link to a wiki page for more info
[10:51] <LaserJock> but things like this silly Desktop CD issue
[10:51] <willvdl> ok, let's check with highvoltage tomorrow. is he putting up a sandbox?
[10:51] <pips1> static = proof read, generalised (or at least tagged as 6.06 LTS and 'Latest greatest' release)
[10:51] <willvdl> LaserJock, exactly what I mean
[10:51] <LaserJock> we need to have a nice big notice that people shouldn't be installing via the Desktop CD
[10:52] <LaserJock> we also need to put some dynamic in the frontpage
[10:52] <LaserJock> people want to see new news and things
[10:52] <willvdl> static also means links to things that don't change, release notes, news items, team info etc.
[10:52] <willvdl> alot of our current wiki can go in there
[10:53] <pips1> right
[10:53] <LaserJock> well, you want to strike a balance
[10:53] <LaserJock> between having to maintain a hug pile of static docs
[10:53] <willvdl> OK, first things first: drupal 5.1?
[10:53] <LaserJock> well
[10:53] <LaserJock> we can start working on content on the wiki right now
[10:53] <pips1> yep
[10:54] <LaserJock> we should tag wiki docs we want to go on edubuntu.org
[10:54] <willvdl> not sure it will be that simple
[10:54] <pips1> not first things first but things-to-be-done-in-parallel :-)
[10:54] <willvdl> :)
[10:54] <willvdl> we should tag info or sections that can go on the web. the wiki pages are quite convoluted
[10:54] <pips1> (well, best-effort-in-parallel)
[10:54] <LaserJock> well, it's not like we update to drupal 5.1 and all of a sudden content pops out ;-)
[10:55] <willvdl> why not? why are we using t drupal then?
[10:55] <LaserJock> because, it's shiny
[10:55] <willvdl> drupalAI
[10:55] <willvdl> just kidding
[10:55] <pips1> lol
[10:55] <pips1> you guys are cracking me up
[10:56] <nixternal> cuz drupal is hawwt
[10:56] <LaserJock> willvdl: drupalAI that plugs into some Google search API?
[10:56] <willvdl> so we'll make a website page under edubuntu/devel or something
[10:56] <willvdl> awesome
[10:56] <pips1> anyway, I can do a clean install of drupal...
[10:56] <willvdl> pips1, you've got a sandbox right?
[10:56] <LaserJock> willvdl: yes, and we can just list candidates there
[10:56] <pips1> willvdl: yes, I have a sandbox
[10:57] <LaserJock> willvdl: those are good bite-size tasks for contributors
[10:57] <LaserJock> "we need these wiki pages cleaned up before going on edubuntu.org"
[10:57] <willvdl> is it live? i.e. as in on the web?
[10:57] <willvdl> LaserJock, that reminds me, nearly done with BST structure
[10:57] <pips1> and I have access to the current .org server, I just haven't had the time to familiarise myself with that box / have a look what is already setup on that box regarding apache/mysql, etc
[10:58] <pips1> willvdl: yes, my sandbox server can be accessed online, the beta site is running on it too
[10:58] <willvdl> excellent
[10:59] <willvdl> so we can devel it parallel
[10:59] <pips1> yep
[10:59] <willvdl> I know I'm jumping around but LaserJock, can you repeat what you said to me the other day about MOTU recipes?
[11:00] <LaserJock> oh, sure
[11:00] <LaserJock> well we've started this wiki project
[11:00] <LaserJock> MOTU Recipies
[11:00] <LaserJock> where people can write sort of HowTo like pages for specific packaging tasks
[11:00] <LaserJock> like making a debdiff
[11:00] <LaserJock> or doing a merge
[11:00] <LaserJock> it's a bit more indepth than just a FAQ
[11:01] <LaserJock> it's a bit more like topics in the Topic Based Help system
[11:01] <LaserJock> anyway
[11:01] <LaserJock> I was thinking this might be cool for Edubuntu
[11:01] <LaserJock> and in fact, if we got a good collection of Edubuntu Recipes
[11:01] <LaserJock> then an Edubuntu Cookbook becomes a natural outcome
[11:02] <pips1> fingers crossed
[11:02] <pips1> :-)
[11:02] <willvdl> it could even be like "my edubuntu recipe" or how I installed my lab
[11:02] <LaserJock> since it's on a wiki people can add/enhance as they come across things
[11:02] <LaserJock> willvdl: exactly
[11:02] <ogra> gavin started some nice docs recently
[11:02] <willvdl> I really think this is the best way to capture contributions
[11:02] <willvdl> ogra, the FAQ?
[11:02] <ogra> we need to make sure to get them over to us
[11:02] <LaserJock> in #ubuntu-motu when people come across something we're asking them if they'd write it up
[11:03] <ogra> the faq and some debgging docs as well iirc
[11:03] <ogra> i.e. how to set up bootchart on thin clients to measure bootspeed
[11:03] <pips1> \o/
[11:03] <willvdl> ah. the FAQ is now on help.ubuntu.com/community/EdubuntuFAQ. i won't be linked off main page cause of it's structure
[11:03] <willvdl> ogra, I missed that, but a perfect recipe
[11:04] <LaserJock> https://wiki.ubuntu.com/MOTU/Recipes/PackageUpdate is an example
[11:04] <LaserJock> and https://wiki.ubuntu.com/MOTU/Recipes/Debdiff
[11:04] <willvdl> this way we can stick to the procedure we decided at UDS: grab contributions and then collate into handbook in timely fashion before release
[11:05] <LaserJock> we might want to come up with a little list of desired recipes
[11:05] <LaserJock> just to get some things kicked off
[11:05] <willvdl> yeah, we can capture the current handbook
[11:06] <willvdl> a recipe could be *anything*, even what FLOSS means to education...
[11:06] <LaserJock> well, it will be anything the community is concerned enough to write about ;-)
[11:06] <willvdl> we might need to call it the cookbook again :)
[11:07] <ogra> yay
[11:07] <LaserJock> well, I can see having both, handbook being a reference doc
[11:07] <willvdl> just kidding
[11:07] <LaserJock> and cookbook being, well, a cookbook
[11:08] <LaserJock> but recipes work well for both
[11:08] <LaserJock> the basic problem is we need content
[11:08] <LaserJock> it's really not so important how we get it
[11:08] <pips1> yeah, think handbook = dusty tome, and cookbook = dogeared and greasy binder
[11:08] <willvdl> ++
[11:08] <willvdl> LaserJock, as Scotty so aptly poited out at UDS
[11:08] <LaserJock> we (edubuntu doc people) can turn content into the desired form
[11:08] <LaserJock> but we need content first
[11:09] <LaserJock> and I think it's best if that comes from the community
[11:09] <willvdl> our procedure then jsut needs to have a recipre freeze with enough time to collate handbook
[11:09] <LaserJock> yep, or maybe not even that
[11:10] <LaserJock> we can do a recipe snapshot
[11:10] <LaserJock> and build static docs out of that
[11:10] <willvdl> still need to dump into xml
[11:10] <LaserJock> especially if we end up doing some moin2docbook
[11:10] <willvdl> LaserJock, are you positive that will work well enough?
[11:10] <LaserJock> nope
[11:11] <LaserJock> but it's better than nothing
[11:11] <pips1> I like the idea that people are encourage to write down *their* setup, rather than asking to write only about the "ideal" setup that never gets written...?
[11:11] <willvdl> there is no "ideal" setup
[11:11] <LaserJock> in fact, to start with
[11:11] <pips1> *encouraged
[11:11] <LaserJock> the "Cookbook" could be a static doc on edubuntu.org that merely links to the wiki pages
[11:12] <pips1> hmm
[11:12] <willvdl> hmm, help.u.com?
[11:12] <LaserJock> and Handbook writers can just look over recipes and copy-n-paste
[11:12] <LaserJock> well
[11:12] <willvdl> LaserJock, cookbook may just as well link straight to wiki
[11:12] <pips1> when you say, "static doc", do you mean "merely a introductory sentence with navigational links"?
[11:12] <LaserJock> help.u.c doesn't have very good structure for handling Edubuntu
[11:13] <willvdl> LaserJock, we'll change that in the meeting :)
[11:13] <willvdl> noone can find kubuntu docs anymore either
[11:13] <LaserJock> willvdl: why not edubuntu.org?
[11:13] <LaserJock> I fail to see the point of having a website if we don't put anything on it ;-)
[11:13] <willvdl> because there is already help.ubuntu.com...
[11:14] <willvdl> fair enough :)
[11:14] <willvdl> moot point
[11:14] <LaserJock> well, if we can have it on help.ubuntu.com that's fine
[11:14] <willvdl> one thing at a time I guess
[11:14] <LaserJock> but I think we need to work on HTML and PDF versions of docs as well
[11:14] <willvdl> ++
[11:14] <LaserJock> our users are a tad different than the usual Ubuntu user I think in this regard
[11:15] <willvdl> to summarise:
[11:15] <LaserJock> teachers/admins are going to want to go to edubuntu.org and download some PDF docs
[11:15] <willvdl> it can be shipped in edubuntu-docs package too
[11:15] <LaserJock> yes, space permitting :-)
[11:16] <willvdl> 2 cds dude
[11:16] <willvdl> oh
[11:16] <willvdl> right
[11:16] <willvdl> summary: (i want to capture this on paper :)
[11:17] <willvdl> FAQ on help.u.com/community for capturing FAQ style thingies
[11:17] <willvdl> recipes on help.ubuntu.com/community for capturing Topics and Setups etc.
[11:18] <willvdl> LTSP docs also go on wiki presumably in different section as they get linked from SErver section off main page
[11:18] <willvdl> then just before doc freeze we collate recipes in cookbook
[11:19] <willvdl> and handbook folks can write handbook off it
[11:19] <willvdl> we release on edubuntu.org
[11:19] <willvdl> and package as much as possible
[11:19] <willvdl> .
[11:19] <willvdl> sound right?
[11:19] <LaserJock> pretty much
[11:19] <pips1> yep
[11:19] <willvdl> how long do we need to collate?
[11:19] <LaserJock> well, cookbook = recipe Table of Contents
[11:20] <LaserJock> so that shouldn't take long
[11:20] <LaserJock> handbook stuff takes much longer
[11:20] <willvdl> handbook is differnet yeah.
[11:20] <willvdl> since we can draw from many sources
[11:20] <LaserJock> string freeze is Sept. 13th
[11:20] <willvdl> and has different scope
[11:20] <willvdl> one week?
[11:21] <LaserJock> which essentially only valid for the handbook and TBH Topics
[11:21] <willvdl> we don't have TBH stuff though
[11:21] <LaserJock> well, some of the recipes could end up being TBH
[11:22] <willvdl> right. and LTSP definately should too
[11:22] <nixternal> LaserJock: are we going to convert to TBH?
[11:22] <LaserJock> I'd like to have a draft Cookbook at Beta Freeze
[11:22] <LaserJock> nixternal: I don't think really convert
[11:22] <LaserJock> just provide topics as appropriate
[11:22] <willvdl> nixternal, we would like to have something in  TBH
[11:22] <LaserJock> I don't want to force too much work
[11:23] <LaserJock> so if a recipe or section in Handbook seem like they'd make a good topic, then lets do it
[11:23] <nixternal> well if you decide on it, I can start the layout changes as necessary
[11:23] <willvdl> let's not worry about it for gutsy
[11:23] <nixternal> leave the handbook alone and create a topic based setup then?
[11:23] <willvdl> let's just get something decent out
[11:23] <LaserJock> ok, fundamental question
[11:24] <nixternal> well, most of the topic based stuff can be read from ubuntu docs right?
[11:24] <LaserJock> do we want to continue the Edubuntu Handbook for gutsy?
[11:24] <willvdl> the handbook is supposed to be a resource for educators
[11:24] <LaserJock> ok, so should we ship that in Gnome Help?
[11:24] <willvdl> the recipes are going to fill that role
[11:25] <willvdl> perhaps make handbook = recipes and the rest TBH
[11:25] <LaserJock> ok, I'm a little concerned about resources
[11:25] <willvdl> my brain hurts
[11:25] <LaserJock> I was thinking more handbook = reference cookbook and TBH = recipies
[11:26] <willvdl> ok. then we need to decide on topic categories
[11:26] <willvdl> which should be easy
[11:26] <LaserJock> blah, we need a little doc sprint
[11:26] <LaserJock> this is getting long and a bit OT
[11:27] <willvdl> yeah. mainly my fault
[11:27] <LaserJock> nah, I'm not very clear still on what we want to do and if we can pull it off
[11:27] <nixternal> maybe setup an irc meeting for edubuntu docs sometime soon?
[11:27] <willvdl> well, we chatted in UDS and the bottom line was "get the info into a wiki"
[11:27] <LaserJock> yes
[11:27] <nixternal> probably should be clear prior to having a main doc team meeting
[11:28] <willvdl> as priority
[11:28] <willvdl> yes
[11:28] <LaserJock> I think the idea of Edubuntu Recipes is a good way to get content on the wiki
[11:28] <LaserJock> we need to promote it and really push it
[11:28] <willvdl> ++
[11:28] <LaserJock> then as it gets closer to release the edubuntu-doc team can finalize what we want to ship
[11:29] <LaserJock> given the amount of content we have
[11:29] <LaserJock> if it's a flop there's no sense and making plans
[11:29] <willvdl> we have two scopes and they get confused a bit :)
[11:30] <LaserJock> willvdl: can you make (if it isn't already) and area on help.u.c/communit for the FAQ and Recipies
[11:30] <willvdl> FAQ is there
[11:30] <willvdl> I'll do it for recipes
[11:30] <LaserJock> when we've got that ready for people to start contributing we'll do a media blitz
[11:30] <willvdl> I want ot make the FAQ release specific as well
[11:31] <LaserJock> well, get it set so that people can start editing then email edubuntu-devel
[11:31] <willvdl> I'll capture tonights discussion into a wiki page on wiki.e.org and then we can mung that around
[11:31] <willvdl> and edubuntu-users
[11:31] <LaserJock> then I can blog and fridge it
[11:31] <LaserJock> ubuntu-education
[11:31] <willvdl> the whole WORLD!
[11:32] <willvdl> tatto it on your children's foreheads
[11:32] <LaserJock> and especially when people come into #edubuntu
[11:32] <LaserJock> and they figure something out, say "can you add that to ...?"
[11:32] <LaserJock> or "mind writing up a recipe for that on ...?"
[11:32] <willvdl> LaserJock, ++ for the recipe idea. so simple and will fix so many problems
[11:33] <willvdl> much easier than docs + use cases that never appear
[11:33] <willvdl> pips1, check out the outpost.com commercials. must be on youtube
[11:33] <LaserJock> I don't have kids, but the cat might not mind ;-)
[11:34] <pips1> hehe
[11:34] <willvdl> he
[11:34] <willvdl> shall we leave it here?
[11:34] <LaserJock> I think so, for me anyway
[11:34] <LaserJock> I'm tired
[11:34] <LaserJock> and it's only 2:30pm
[11:34] <willvdl> pips1, I've got some stuff to add to community blog
[11:35] <pips1> great
[11:35] <willvdl> about eLEarning Africa. jsut need to edit out the canonical stuff
[11:35] <pips1> ?
[11:35] <pips1> just go ahead, I'm not going to hold you back
[11:35] <LaserJock> btw, if anybody has interesting news items about Edubuntu let me know and I'll throw it on Fridge
[11:35] <willvdl> I wrote a canonical report which won't be of much interest to community.
[11:35] <pips1> ah
[11:36] <willvdl> pips1, just remind me in a few days to do it. it's midway on my priorities
[11:37] <willvdl> we'll attract more people. jeust need the tipping point
[11:37] <pips1> willvdl: don't ask me to remind you, just do it!
[11:37] <pips1> :-P
[11:37] <willvdl> I'll forget!
[11:37] <pips1> pfft
[11:37] <LaserJock> pips1: just write a cron job that emails and does an IRC poke
[11:38] <pips1> ok, I'll *encourage* you to contribute
[11:38] <pips1> LaserJock: hehe
[11:38] <willvdl> LaserJock, I'll flood ping you you bastard!
[11:38] <LaserJock> heh
[11:38] <pips1> tsk
[11:38] <willvdl> I demand the personal touch!
[11:38] <willvdl> dudes, as usual, very informative tonight. need to write this up. back to #e
[11:38] <LaserJock> ok, so a cron job that wake up highvoltage to go ping you
[11:39] <pips1> poor h.
[11:39] <ogra> http://cdimage.ubuntu.com/edubuntu/daily-live/20070606.5/ seems to be good for testing
[11:39] <LaserJock> ogra: awesome
[11:39] <willvdl> heh
[11:39] <ogra> finally they are properly sized, sigh
[11:40] <pips1> ogra: very timely reminder that we haven't been doing anything but talking, while you were silently ploughing away as always ;-)
[11:40] <LaserJock> ogra: is an rsync of these from Feisty any good?
[11:40] <pips1> ohhh, do you have an updated rsync script?
[11:40] <ogra> LaserJock. it might speed up a bit, yes
[11:41] <ogra> pips1. nope
[11:41] <ogra> i'm rsyncing manually ...
[11:41] <pips1> ic
[11:41] <LaserJock> that's what I do too
[11:41] <ogra> feel free to take the old one and fix the paths :)
[11:41] <LaserJock> since I usually only do like 1 at at time
[11:41] <LaserJock> *a
[11:42] <ogra> well, i do 6, but thats a simple for loop :)
[11:42] <LaserJock> I usually have to use ogra's rsync script to figure out the rsync commands
[11:42] <ogra> lol
[11:42] <pips1> hihi
[11:43] <pips1> ok, guys, great comedy tonight, I'm off... good night
[11:43] <ogra> yeah meeting eds here ...
[11:48] <willvdl> minutes are up
[12:09] <effraie> @schedule Paris
[12:09] <ubotu> Schedule for Europe/Paris: Current meeting: Edubuntu | 07 Jun 22:00: Ubuntu Development Team | 12 Jun 17:00: Kernel Team | 13 Jun 14:00: Edubuntu | 14 Jun 18:00: Ubuntu Development Team | 16 Jun 19:00: Xubuntu Developers