[08:39] <highvoltage> @schedule
[08:39] <Ubugtu> Schedule for Etc/UTC: 21 Feb 12:00: Edubuntu | 21 Feb 16:00: Kernel Team | 22 Feb 16:00: Ubuntu Development Team | 24 Feb 21:00: Ubuntu US LoCo Team Mentor | 25 Feb 17:00: LoCo Team | 26 Feb 23:00: Community Council
[11:01] <juliux> @schedule berlin
[11:01] <Ubugtu> Schedule for Europe/Berlin: 21 Feb 13:00: Edubuntu | 21 Feb 17:00: Kernel Team | 22 Feb 17:00: Ubuntu Development Team | 24 Feb 22:00: Ubuntu US LoCo Team Mentor | 25 Feb 18:00: LoCo Team | 27 Feb 00:00: Community Council
[12:57] <willvdl> @schedule
[12:57] <Ubugtu> Schedule for Etc/UTC: Current meeting: Edubuntu | 21 Feb 16:00: Kernel Team | 22 Feb 16:00: Ubuntu Development Team | 24 Feb 21:00: Ubuntu US LoCo Team Mentor | 25 Feb 17:00: LoCo Team | 26 Feb 23:00: Community Council
[12:58] <cbx33> Hi all I'm here for 10 mins
[12:58] <cbx33> so if you wanna ask me anything....ask now
[12:58] <willvdl> okie
[12:58] <willvdl> what's the land speed of the african swallow?
[12:58] <cbx33> um...
[12:59] <cbx33> noooooooooooooooooo
[12:59] <willvdl> he
[12:59] <cbx33> https://wiki.ubuntu.com/EdubuntuArtwork/Palette
[12:59] <cbx33> could you put that up at artwork section
[12:59] <willvdl> will do
[12:59] <willvdl> TCM update?
[12:59] <cbx33> and for tech...I have done a lot of bug fixing for TCM
[12:59] <cbx33> vnc is much more stable
[12:59] <cbx33> working a lot more on it today
[01:00] <juliux> cbx33, is in feisty now a tcm version that usable?
[01:00] <willvdl> cool
[01:00] <cbx33> juliux: useable yes
[01:00] <juliux> cbx33, great
[01:00] <cbx33> still has bugs
[01:00] <cbx33> a nasty one at the mo, that I'll need ogras help fixing
[01:00] <juliux> i tested on version on the weekend but there was still your two example users
[01:00] <cbx33> juliux, that has been fixed
[01:01] <juliux> cbx33, great
[01:01] <cbx33> the scp-client program is started under Xsession
[01:01] <cbx33> but it can't communicate with the gnome-screensaver instance
[01:01] <cbx33> so it can't blank screens etc
[01:01] <highvoltage> hi cbx33, willvdl and juliux
[01:01] <highvoltage> juliux: pong, btw ;)
[01:01] <juliux> hey highvoltage
[01:01] <highvoltage> and jsgotangco too :)
[01:01] <willvdl> hey
[01:01] <cbx33> this is very annoying bug
[01:02] <cbx33> but I hope we can solve it soon
[01:03] <willvdl> sweet
[01:03] <cbx33> i think that's it
[01:03] <cbx33> chapter is going through final stages of checking
[01:03] <willvdl> can't wait for that one
[01:04] <cbx33> oh and anyone wanting to look at any of my side projects....Iopened up my own repo, which will probably hold devel debs of tcm too
[01:04] <willvdl> malone registered?
[01:04] <cbx33> deb http://progbox.co.uk/repo edgy-cbx33 extras
[01:04] <cbx33> can you register a repo with malone?
[01:04] <willvdl> oh. sorry thought you ment LP
[01:04] <cbx33> hehe
[01:04] <cbx33> tcm now has a product
[01:04] <cbx33> on LP
[01:04] <willvdl> well, if you use bugzilla etc. then yes
[01:04] <cbx33> so please test and bug report
[01:05] <juliux> i will test it
[01:05] <cbx33> thanks juliux the vnc won;t work as yet
[01:05] <cbx33> and that version isn't in the repos yet
[01:05] <cbx33> need ogra to debdiff it
[01:05] <cbx33> but i can give you a manual set of packages if you're interested
[01:05] <juliux> cbx33, did you have .deb?
[01:05] <cbx33> i will do tonight
[01:06] <willvdl> sounds like my laptop
[01:06] <highvoltage> I wanted to ask your feedback on something
[01:06] <juliux> cbx33, i am off from 23-28 but bevor and after that i can test
[01:07] <highvoltage> I want to put together an edubuntu metapackage for Kubuntu, that will transform Kubuntu into an Edubuntu-KDE machine. does anyone think that's worth while?
[01:07] <cbx33> yes
[01:07] <willvdl> yeah. sounds interesting. what would it do exactly?
[01:08] <juliux> highvoltage, why not with xubuntu?
[01:08] <Riddell> highvoltage: sure, but I've no idea how well all the LTSP stuff works in KDE so testing that would be needed first (it should all work in theory, but I've not heard of anyone who's tried it)
[01:08] <highvoltage> juliux: we do that with tuxlabs, and edubuntu is going to get an official, supported Xfce on edubuntu's 2nd disc
[01:08] <highvoltage> (at least, I think it will be supported)
[01:09] <juliux> Riddell, i think skolelinux is using kde with ltsp
[01:09] <cbx33> I'm off.... juliux would appreciate that testing...and on the groups and filtering....right click in the user name area
[01:09] <willvdl> Riddell, I know of a few small groups that do it, but can't think off hand of anyone large and reputable
[01:10] <Riddell> juliux: yeah, the basics will work fine, it's all X
[01:10] <Riddell> but I'm curious to know how well kdm, sound, mounting devices etc works
[01:10] <willvdl> cbx33, ciao
[01:11] <highvoltage> Riddell: the LTSP parts works fine with LTSP, the only part that I think I might have trouble with might be the Edubuntu KDM theme, since I haven't made a KDM theme yet
[01:11] <highvoltage> Riddell: but I'm sure there's lots of people on #kubuntu that could help me, and it can't be much more complicated than a GDM theme :)
[01:12] <Riddell> highvoltage: anyway, I would think it worthwhile if you're willing to maintain it, it just needs a branch of the seeds, edubuntu-meta and kubuntu-default-settings for artwork
[01:12] <Riddell> highvoltage: #kubuntu-devel will happily help
[01:12] <highvoltage> Riddell: great. at first I'll just put it in my own server for people to play with, if the response is good, and there's one or two people willing to give a hand, we can probably get it into universe quite quickly
[01:14] <Mithrandir> note that featurefreeze for universe is tomorrow.
[01:14] <Riddell> but, and this is the most important point, it may not be called kedubuntu, that would be a grave offence
[01:15] <highvoltage> Riddell: noted ;)
[01:16] <Mithrandir> edukubuntu would be better?
[01:16] <highvoltage> Mithrandir: ok, it might have to go into feisty+1 then, which would give a better amount of testing, which is good
[01:16] <Riddell> yes, edubuntu-kde is good
[01:21] <willvdl> moving on. Docs?
[01:21] <willvdl> I've been working round the clock on my NEPAD stuff and am not likely to get the chance that I hoped for to work on hbook
[01:22] <willvdl> before the 28th
[01:22] <willvdl> but I finished wiki.edubuntu.org/Edubuntu , it just needs a "miscellaneuous" section
[01:24] <willvdl> anyone else?
[01:24] <willvdl> otherwise I need to go. got horrid fever
[01:24] <juliux> willvdl,  i have something technical;9
[01:24] <willvdl> shoot
[01:24] <juliux> i have tested edubuntu on a sparc
[01:24] <cliebow_> bbl
[01:24] <juliux> and it is working well with i386 clients
[01:24] <highvoltage> willvdl: I LOVE the new wiki page!
[01:25] <willvdl> juliux, which sparc?
[01:25] <juliux> willvdl, an old ultra 60
[01:25] <juliux> it is a 64bit sparc
[01:27] <willvdl> juliux, great
[01:27] <willvdl> On that note, I'm struggling. I gotto go. I'll be in on Monday again.
[01:27] <juliux> i will write a wiki page about that
[01:29] <willvdl> ciao folks. my apologies
[01:31] <highvoltage> cbx33 and willvdl have left, and RichEd, ogra and pips1 isn't available
[01:31] <highvoltage> shall we call this meeting to and end and conclude it as the shorted edubuntu meeting ever?
[01:31] <juliux> highvoltage, +1
[01:32] <jsgotangco> no!
[01:32] <highvoltage> jsgotangco: you have the floor. enjoy!
[01:32] <jsgotangco> lol
[01:33] <jsgotangco> let's talk about edubuntu in ps3
[01:33] <jsgotangco> lol
[01:33] <jsgotangco> please ignore jsgotangco
[01:33] <highvoltage> /ignore jsgotangco
[01:33] <jsgotangco> bwahaha
[01:33] <highvoltage> :)
[01:33] <highvoltage> * MEETING ADJOURNED
[02:27] <jsgotangco> cbx33: it was a fairly short meeting
[02:27] <cbx33> i guessed as much
[02:34] <givre> @schedule
[02:34] <Ubugtu> Schedule for Etc/UTC: Current meeting: Edubuntu | 21 Feb 16:00: Kernel Team | 22 Feb 16:00: Ubuntu Development Team | 24 Feb 21:00: Ubuntu US LoCo Team Mentor | 25 Feb 17:00: LoCo Team | 26 Feb 23:00: Community Council
[04:43] <zul> @schedule montreal
[04:43] <Ubugtu> Schedule for America/Montreal: 21 Feb 11:00: Kernel Team | 22 Feb 11:00: Ubuntu Development Team | 24 Feb 16:00: Ubuntu US LoCo Team Mentor | 25 Feb 12:00: LoCo Team | 26 Feb 18:00: Community Council | 27 Feb 15:00: Technical Board
[04:45] <fernando> @schedule brazil
[04:45] <fernando> @schedule Sao_Paulo
[04:45] <Ubugtu> Schedule for America/Sao_Paulo: 21 Feb 13:00: Kernel Team | 22 Feb 13:00: Ubuntu Development Team | 24 Feb 18:00: Ubuntu US LoCo Team Mentor | 25 Feb 14:00: LoCo Team | 26 Feb 20:00: Community Council | 27 Feb 17:00: Technical Board
[04:50] <cbx33> @schedule london
[04:50] <Ubugtu> Schedule for Europe/London: Current meeting: Kernel Team | 22 Feb 16:00: Ubuntu Development Team | 24 Feb 21:00: Ubuntu US LoCo Team Mentor | 25 Feb 17:00: LoCo Team | 26 Feb 23:00: Community Council | 27 Feb 20:00: Technical Board
[04:52] <_kyle> morning ben.
[04:52] <BenC> good morning
[04:53] <pochu> @now cet
[04:53] <Ubugtu> Current time in CET: February 21 2007, 16:53:19 - Current meeting: Kernel Team
[04:53] <pochu> BenC: the clock is fine :)
[04:53] <BenC> @now UTC
[04:53] <Ubugtu> Current time in Etc/UTC: February 21 2007, 15:53:37 - Current meeting: Kernel Team
[04:53] <zul> heylo
[04:53] <BenC> 16:00 is the meeting time
[04:53] <pochu> hi zul :)
[04:53] <BenC> so I guess it's just preemptive
[04:54] <zul> heh its hurry up and wait
[05:00] <BenC> Just waiting on rtg
[05:01] <pochu> BenC: is there an agenda?
[05:01] <BenC> https://wiki.ubuntu.com/KernelTeam/Meeting
[05:01] <BenC> Agenda is there
[05:01] <pochu> ty :)
[05:02] <BenC> Ok, time to start
[05:02] <BenC> First, I want to thank anyone from the community who is joining us
[05:03] <BenC> This is the first of our team meetings, and hopefully it will turn into a means of us organizing with the community better, and bring in new people to help out
[05:03] <BenC> In case anyone missed it, the agenda is at https://wiki.ubuntu.com/KernelTeam/Meeting
[05:04] <BenC> I was hoping mjg59 would be here for the first item, so we'll skip to the second in case he shows up later on
[05:04] <BenC> pkl_: You added the second item: Status of Unionfs. Discuss whether to include Unionfs 2.0 in Feisty kernel.
[05:04] <pkl_> Yeah...
[05:05] <pkl_> A bug has been raised against the current version of Unionfs (just getting it).
[05:06] <BenC> pkl_: Does the bug affect just feisty, or does this affect edgy and prior as well?
[05:06] <pkl_> #85145...
[05:06] <BenC> bug 85145
[05:06] <Ubugtu> Malone bug 85145 in linux-source-2.6.20 "run-init crashes when root is unionfs on nfs" [Undecided,In progress]  https://launchpad.net/bugs/85145
[05:06] <zul> oh this is the initramfs thingy?
[05:07] <pkl_> It was raised against initamfs, but it isn't anything to do with it.
[05:07] <BenC> So dapper is ok, it's just feisty
[05:07] <pkl_> It is a pure Unionfs on NFS branch bug.  Recent changes (post 2.6.18) means NFS oopses on a NULL pointer.
[05:08] <BenC> I wonder if this has anything to do with some of the fs changes I had to do during .19/.20
[05:08] <zul> couldnt you just backport the fix rather than updating to 2.0?
[05:08] <BenC> so is the bug NFS or unionfs? Is updating to unionfs just working around the real bug?
[05:08] <pkl_> This has been fixed, but, only in Unionfs 2.0.  A new call lookup_one_len_nd has been added.
[05:09] <pkl_> Very difficult question to answer BenC:  Both the Unionfs and NFS people has engaged in a lot of finger pointing...
[05:10] <BenC> Ah, upstream politics
[05:10] <pkl_> But the major issue appears to be recent NFSv4 changes.
[05:10] <BenC> pkl_: Unionfs is used quite a bit in our livecd's, and I would prefer this late in the game not to bump major versions on it
[05:10] <BenC> pkl_: Is the fix easily isolated?
[05:11] <pkl_> I'll see if I can back port the essential fix (which is to add and use lookup_one_len_nd() which passes the necessary pointer)  to 1.2 Unionfs.
[05:12] <pkl_> This essentially should be all that's required.
[05:12] <BenC> pkl_: Ok, sounds like a good plan
[05:12] <BenC> Looks like mjg59 wont be able to make it, so we'll cover d80211 sans his expertise
[05:13] <BenC> _kyle: You have some newer crack than I have in the repo...how's that coming?
[05:13] <_kyle> good, i'm going to push it into a branch for you to look at in about 5 seconds.
[05:14] <BenC> flash-kyle
[05:14] <BenC> _kyle: Do you have any hw to test the drivers using it?
[05:14] <_kyle> er, unless i accidently nuked that tree... err...
[05:14] <_kyle> BenC: bcm43xx
[05:14] <Nafallo> _kyle: <3 backup
[05:14] <BenC> I was going to do a 2.6.20-9 upload today, but if you think you can get d80211 working, I can hold off
[05:14] <_kyle> i have an atheros card too, but it's minipci, and gutting my thinkpad is always a pain.
[05:15] <_kyle> BenC: when do you intend to upload next after this?
[05:15] <BenC> hopefully over the weekend
[05:15] <BenC> uploads have been getting too far apart, I need to make them more frequent
[05:16] <_kyle> ok. i have some hppa crack to push for jeff so we can have a buildable.
[05:16] <BenC> _kyle: FYI, the bcm43xx-dscpape driver lacks a MODULE_DEV_TABLE, so if you want to use it, just manually load it (after unloading the bcm43xx driver)
[05:17] <_kyle> yeah, i saw those commits.
[05:17] <BenC> Ok, let's move on to what I know is everyone's favorite subject...bugs
[05:17] <zul> yippe skippe
[05:18] <BenC> I didn't have time to write up a "how to triage" bugs, but there's plenty of them on the ubuntu wiki for general bug work, and the kernel isn't much different
[05:19] <BenC> Basically what we need to aim for is to not let the untriaged bug list get so big
[05:19] <zul> what is the list at now?
[05:19] <BenC> it's safe to assume we wont be able to fix all the bugs, because we either don't have hardware where the bug is occurring, or it's the type of bug that happened once, and will never happen again
[05:19] <BenC> zul: ~250 when I checked last night (2.6.20)
[05:20] <pkl_> that's all bugs, right?
[05:20] <BenC> But what I want to make sure is that we at least respond to all incoming bugs
[05:20] <BenC> pkl_: All open bugs on 2.6.20 kernel
[05:21] <BenC> For those that aren't aware, I've been working with launchpad folks to try and get some features in that will make bug triaging a lot easier
[05:21] <pkl_> A response along the lines of "go away we're not going to fix this" is better than no response?
[05:22] <BenC> pkl_: A little better wording, but pretty much :)
[05:23] <BenC> The main thing for a new bug right now is getting all the normal information (dmesg, screen photo of it's a solid lock with traceback, lspci, etc)
[05:23] <zul> please no automated bug scripts as well
[05:23] <BenC> 9 times out of 10, the bugs just don't have enough info
[05:24] <BenC> Yeah, make sure you ask for information pertinent to the bug
[05:24] <BenC> we don't need dmidecode when someone's ext3 partition gets corrupt
[05:25] <BenC> The second step after getting the info is to classify the severity, there's a wiki with severity ratings (someone will paste it in a few minutes I'm sure)
[05:25] <BenC> Once all the info is collected, set the status (confirmed, most times)
[05:25] <BenC> During this process, once you take on triaging a bug, assign it to yourself
[05:26] <BenC> Once you start working on it, set it to In Progress, etc...Once it's in git, set it to fix committed, and once we upload it, set it to fix released
[05:27] <BenC> Any bug that is marked Confirmed and Importance > Medium should be fixed asap
[05:27] <Mithrandir> and if it's important to get fixed before release, please assign either the next milestone to it or 7.04 if it's not possible to get done before the next milestone.
[05:27] <BenC> either by yourself, or bringing it up to the rest of the team
[05:27] <BenC> Correct
[05:27] <Mithrandir> (7.10 for feisty+1, etc, naturally)
[05:28] <zul> how long per day should we spend on bug hunting (kernel team vs community)?
[05:28] <BenC> zul: Community is welcome to work on it as long as they want :)
[05:29] <BenC> I would expect core kernel team to spend some time on it every day, probably set aside 1-2 hours for just triaging, and more as needed for actual debug
[05:30] <fdoving> looks like the bcm43xx item is done already, but for whom it may concern bug 85404 is reported by Michael Buesch concerning the state of bcm43xx in the recent feisty kernel.
[05:30] <Ubugtu> Malone bug 85404 in linux-source-2.6.20 "bcm43xx completely broken in feisty" [Undecided,Confirmed]  https://launchpad.net/bugs/85404
[05:31] <BenC> fdoving: Yes, we're aware of it, and it is fixed in git
[05:31] <BenC> pkl_, _kyle, rtg: Any questions?
[05:31] <fdoving> good, thanks :)
[05:31] <_kyle> nyet.
[05:31] <rtg> Nope.
[05:31] <pkl_> no
[05:31] <BenC> Ok, let's get down to the nitty gritty of the 2.6.20 bug list :)
[05:32] <BenC> 263 bugs, 122 unconfirmed, 233 unassigned
[05:33] <BenC> How many does everyone have assigned to themselves?
[05:34] <zul> no idea :)
[05:34] <rtg> I've been working on the various suspend problems, but have not assigned any to myself yet.
[05:34] <BenC> Only 30 bugs assigned :)
[05:35] <pkl_> I've working through a number, but have not assigned any to myself.
[05:35] <BenC> Assigning it to yourself doesn't mean you are committing to fix it
[05:35] <BenC> So let's work on getting that 122 and 233 down to near nothing by the end of next week
[05:36] <pkl_> OK.  What does assigning it signify?
[05:36] <BenC> the 122 is where community can help the most (confirming bugs by getting all relevant info to reproduce and/or debug it)
[05:36] <zul> sure..
[05:37] <BenC> pkl_: Means you are giving the submitter someone to talk to about the bug
[05:37] <pkl_> Ah good.  Terminology strikes again.  In many previous roles. assigning it basically takes an 'exclusive lock' on the bug.
[05:37] <BenC> you get the info you need to debug it, and keep them up-to-date on the status via the bug status. milestone and comments
[05:39] <BenC> I would say if the bug gets to the point where you know it's confirmed, and you cannot fix it, then assign it to the ubuntu-kernel-team in general
[05:40] <BenC> we'll consider those bugs for discussion at meetings, or when time permits during normal hours
[05:41] <BenC> Community can do that as well, if the bug has all relevant info, we can pull from the ubuntu-kernel-team assigned list to assign to ourselves
[05:41] <BenC> I'm going to action item me to detail all this on the KernelTeam wiki
[05:42] <BenC> Any questions, comments?
[05:42] <zul> nope
[05:43] <pkl_> No, I'm happy.
[05:43] <BenC> Ok, we have about 18 minutes left if anyone has anything to bring up
[05:43] <BenC> This is also a good time for community to ask the kernel-team any questions
[05:43] <zul> i just want to confirm the kernel for feisty+1
[05:43] <cbx33> can I ask a question?
[05:44] <BenC> zul: We'll make that decision in Seville
[05:44] <zul> .22?
[05:44] <BenC> zul: It could be .23, depends on time frame
[05:44] <BenC> cbx33: Sure
[05:44] <cbx33> I'm still running edgy, but i cannot suspend it gnome-network-manager is running with ndiswrapper
[05:44] <cbx33> is this common?
[05:45] <cbx33> it just locks with gnome-screensaver instead
[05:45] <BenC> cbx33: This is a better question for #ubuntu-kernel, but yes, ndiswrapper is notoriously sucky...it is running win32 code afterall
[05:45] <cbx33> ok
[05:45] <cbx33> that's fine
[05:45] <cbx33> another question
[05:46] <cbx33> I work in a school and am a contributor to Edubuntu
[05:46] <abogani> BenC: Only one question (yes or no type): Do you think that my work on my spec (https://blueprints.launchpad.net/ubuntu/+spec/realtime) will be useful in the future? Thank you
[05:46] <cbx33> I want to get some interactive whiteboards working in edubuntu, how hard is it to write a device driver?
[05:47] <BenC> abogani: Absolutely...I have to say that the stock Ubuntu kernel cannot take on the RT patchset until it is merged with Linus' tree though. However a separate kernel like what is done for xen is entirely possible.
[05:47] <cbx33> abogani, don't the ubuntu-studio guys have a low latency kernel?
[05:48] <BenC> cbx33: It all depends on if the specs are available for the device. There's the Linux Device Drivers manual available freely on the internet
[05:48] <cbx33> ok
[05:48] <pochu> I have a little question (don't know if it's stupid): will we support wpa out-of-the-box? :-)
[05:48] <cbx33> thanks BenC
[05:48] <crimsun> there is a -lowlatency* set (universe & multiverse), yes
[05:48] <Mithrandir> the archive team is not going to accept random kernels nilly-willy and as a start, they have to be done as patch sets against linux-source-$version
[05:48] <BenC> cbx33: See the KernelTeam/FAQ wiki about patches like -rt :)
[05:48] <crimsun> pochu: (already do via NM for some chipsets.)
[05:48] <BenC> it details what Mith said aswell
[05:48] <zul> Mithrandir: that will happen for feisty+1 with xen fyi
[05:49] <Mithrandir> zul: good to hear.
[05:49] <BenC> xen, the butt of all jokes
[05:49] <zul> thanks..
[05:50] <crimsun> 'unconfirmed' audio bugs against linux-source-2.6.20 are now triaged.
[05:51] <BenC> crimsun: BTW, you rock...thanks for keeping up with audio bugs and patches
[05:51] <BenC> Any more random questions?
[05:52] <BenC> pkl_, _kyle, rtg: Anything to add?
[05:52] <_kyle> nope.
[05:52] <pkl_> no.
[05:52] <rtg> Lots 'o bugs to look at.
[05:53] <dholbach> Was that the first Kernel Team meeting?
[05:53] <pochu> dholbach: yes
[05:53] <BenC> dholbach: The first public one
[05:53] <dholbach> Congratulations! I hope you'll attract a lot of community people to it!
[05:53] <BenC> we've been doing secret-hand-shake meetings for a few weeks already :)
[05:53] <BenC> dholbach: Thanks
[05:53] <dholbach> Coooool :)
[05:54] <BenC> Ok, thanks to everyone for coming, especially to the community members
[05:54] <zul> no probs
[05:54] <BenC> adios all
[05:54] <abogani> BenC: thanks again
[05:55] <cbx33> it was great to see BenC
[05:55] <cbx33> really good idea ;)
[05:55] <cbx33> and I like the community bit at the end
[07:01] <estephban> ?
[09:23] <pochu> @schedule cet
[09:23] <Ubugtu> Schedule for CET: 22 Feb 17:00: Ubuntu Development Team | 24 Feb 22:00: Ubuntu US LoCo Team Mentor | 25 Feb 18:00: LoCo Team | 27 Feb 00:00: Community Council | 27 Feb 21:00: Technical Board | 28 Feb 21:00: Edubuntu