[00:23] you could always just make a list of pages you want to include, and wget them from the wiki right before release [00:23] do a little URL re-writing so links to other offline pages point to them, while links to pages that weren't downloaded still point to the online wiki === joerg is now known as Guest90471 [00:43] i like wiki handbooks [00:43] where is this wiki? [00:44] a button to "update" wiki could be put there? [00:44] and using wget just as above? === Guest90471 is now known as joerg [02:18] Evening all [02:20] mhall119|work: Yeah, I suppose. I'd like something that's: [02:20] 1) Simple [02:20] 2) Doesn't require running a web server on the box to view [02:44] if we wget the files, they can just be viewed in a browser [02:45] btw, I'm going to try and get my LoCo to do a documentation jam around edu-games for the upcoming global jam [03:10] Another problem with the wiki idea is: translations. [12:47] Bah we need to disable the "your X isn't configured properly, do you want to reconfigure it" dialog for fat clients... I wonder how that's called [14:54] Morning all === joerg is now known as Guest351 [15:05] Dear Scott Balneaves, [15:05] We are pleased to inform you that you are now part of the GNOME [15:05] Foundation Membership. [15:05] \o/ [15:05] bbiab [15:14] sbalneav: Congrats !!! === Guest351 is now known as joerg [16:37] sbalneav: awesome!!! well done [16:37] sbalneav, stgraber, alkisg, nixternal_: [16:38] https://wiki.ubuntu.com/Edubuntu/Documentation/Developers [16:38] first draft based on Kubuntu policy as discussed. so far it's mostly s/kubuntu/edubuntu/g and s/kubuntu-dev/edubuntu-council/g [16:41] (just made a change so might be good idea to refresh) [16:51] * stgraber is looking [16:51] highvoltage: looks fine to me, except maybe that line needs a little explaining? "Able to upload Edubuntu packages" ==> where? [16:51] alkisg: to main and universe, but yes I'll add that [16:52] or I'll just say "ubuntu archives" instead [16:52] to Ubuntu archive [16:53] other than that small detail, looks good [16:53] Maybe sometime in the future we'll make another wiki page with the details on how to do that, and link to it? [16:54] alkisg: you mean the technical details on how to do that? [16:54] that's identical to a regular ubuntu archive upload [16:55] and there's good documentation for that on the wiki already I believe [16:55] alkisg: afaik dput will automatically know where to upload it to, so we could link to some of the MOTU docs if you're refering to the technical parts [16:55] OK, thanks, I'll search the wiki [16:56] https://launchpad.net/~edubuntu-dev/+members [16:58] are we going to start over with that group? or keep laserjock? [17:00] I guess it's also enough just having Edubuntu Council as an administrator? [17:10] I believe the team owner and admins are fine [17:11] we may have to empty it though [17:11] stgraber: I'm not an admin, could you do that please? [17:11] highvoltage: ? weird, the EC is the owner, you should have the right to [17:11] and the EC is also an admin [17:12] stgraber: oh right, of course [17:12] ok I'll empty it because strictly speaking, it should be empty [17:12] (and we can just re-apply when everything is in place) === nixternal_ is now known as nixternal [17:15] highvoltage: looks good... [17:18] highvoltage: yep [17:20] I'm also going to add developer-membership-board as a co-administrator as per https://wiki.ubuntu.com/UbuntuDevelopers/TeamDelegation [17:21] ok invited, anyway :) [17:22] (and also ubuntu-core-dev) [17:30] stgraber, nixternal, sbalneav, alkisg: I'll send our request to the TB, is that ok? anything else I should add? [17:31] TB/Developer Board [17:31] highvoltage: that will work [17:32] * alkisg agrees even though he doesn't completely understand all of it - but being able to upload to edubuntu packages will be a good thing :) [17:33] alkisg: well, basically (and sorry if you allready know/understand this part) the old destinctions of motu's and core-devs are going to be replaced/supplemented (it's all still in progress) so that there is a more fine-grained control over who can upload packages where [17:34] alkisg: so what we're applying for here is that everyone who are trusted edubuntu developers would be able to upload any Edubuntu package whether it's in universe or main [17:34] alkisg: where previously you'd have to become a core-dev in order to be able to upload to main [17:35] Ah, got it. I've heard of some of these things, but I didn't get the big picture - thanks for clearing it up! [17:35] you're welcome [17:39] Hmm fat client users can't authenticate as themselves, because no passwd entry is generated for them [17:40] So they can't even unlock gnome-screensaver [17:41] * alkisg looks at the LTSP user handling code... [17:44] Of course we could disable the screen locking, but in general, I think the user should be able to authenticate as himself... [17:52] highvoltage: Do I have to do something? I just got unsubbed from edubuntu-dev [17:55] sbalneav: read the scrollback of the last 40 lines or so, we're applying to make the edubuntu-dev a delegate of ubuntu-dev so we need to empty it first [18:13] sbalneav: we got rid of you because you were too good looking and made us look ugly :) [18:14] alkisg: oh no! look what you did! [18:14] Heh, bad timing :) [18:14] (probably just a co-incidence :p) [18:15] alkisg, stgraber, nixternal, Lns: this is what I'm sending: http://paste.ubuntu.com/374126/ [18:15] sending in 5 mins or so if no one objects :) [18:16] Looks fine [18:16] looks good to me =) [18:18] looks good to me [18:24] sent [18:42] What exactly is allowed after feature freeze? E.g. would a fat client patch for disabling "lock screen" be allowed? [18:46] alkisg: bug fixes are allowed, so that should be fine [18:46] alkisg: it's clearly not a feature, at least [18:47] Got it [18:47] Thanks! [18:48] Is it possible to take source from someone's PPA (which was packaged for Intrepid+) and build it for Hardy? I really need Audacity to run on my thin clients by Friday...this guy's PPA (https://launchpad.net/~diwic/+archive/ppa/+packages) has one with the pulseaudio fix, but he hasn't built it for hardy [18:49] Lns: doesn't stgraber have audacity on his ppa? [18:50] Ah no, Intrepid... [18:50] :( [18:50] I don't want my kids to miss out on their first podcasting class :( [18:50] Lns: I can try to copy it to my ppa, I don't know if it will compile [18:50] But if it does, you should be good to go [18:50] alkisg: that would be *so* awesome, I would owe you big!! [18:51] Which one do you want me to try? stgraber's or the other guy's? [18:51] Well I trust stgraber more than most...so ;) [18:51] k [18:51] thank you alkisg !! [18:51] Lns: if you can get all the build-depends satisfied with the right versions on hardy (or in a chroot or pbuidler) then it's quite easy [18:52] highvoltage: yeah - it was depending on some fairly core sound libraries I didn't really want to touch [18:52] Lns: https://launchpad.net/~alkisg/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=hardy [18:52] woah!! it's done? [18:52] Nope, it's in queue for compiling [18:52] oh. ;) [18:53] If it compiles, you're ok, if not, it'll need some love... [18:53] well thank you!! I'll refresh every so often today.. [18:54] I compiled the original audacity source on my server yesterday,j all it needed was wxwidgets.. but the sound preferences only gave me options for OSS..I figured i had to modify the makefile, and at that point I had to leave, so... [18:54] apt-get source gets you the source, apt-get build-dep gets you the dependencies, and debuild -b -tc -uc builds it ;) [18:56] oh yeah? No modifying anything? No dependancy hell? [18:56] Well if the dependencies are not satisfiable, you'll have to change the sources... [18:57] But in a normal case, with those commands you're able to build a .deb package locally. [18:59] * Lns needs a good lesson on the more intricate features of apt [18:59] Lns: failed to build, sorry... [19:00] :( [19:00] Thanks anyway! [19:00] make[3]: *** [src/hostapi/alsa/pa_linux_alsa.lo] Error 1 [19:01] src/hostapi/alsa/pa_linux_alsa.c:1366: error: 'SND_PCM_TSTAMP_ENABLE' undeclared (first use in this function) [19:01] hmm [19:04] http://cdimage.ubuntu.com/edubuntu/releases/10.04/alpha-2/ - latest ISO or no? Wasn't there a much newer version than from jan 14th? [19:04] stgraber: any comments on the audacity conversation above? [19:04] oh nm, found the latest build [19:06] Also, we should look at "bambam" (posted to the list last night about it) and possibly including it in lucid+1 [19:07] pretty simple but neat keyboard mashing program for toddlers [19:10] http://code.google.com/p/bambam/ [19:58] stgraber: I want to add 2 gconf files (defaults and mandatory settings) for the fat client plugin, e.g. something like this: http://alkisg.pastebin.com/d2cbaea2f [19:58] Should they be packaged as part of e.g. ltsp-client-core, or should they be generated on the fly by the fat client script (which will then be much bigger?) [19:58] /me would prefer the former... [20:06] They'll end up in /opt/ltsp/i386/usr/share/gconf/defaults & mandatory, and I expect them to grow over time... [20:34] Afternoon all [20:54] alkisg: you can use gconftool-2 to set these instead of writting the xml directly [20:54] stgraber: yes, but wouldn't it be more elegant to provide files instead? [20:54] alkisg: in your case, it'll be 4 gconftool-2 calls instead of writting the whole gconf [20:55] no, because if something else changes gconf, you'd override it. If you use gconftool-2, then it'll merge that with the existing schema [20:55] which is usually a lot better [20:55] By providing files, you can also have priorities (the number) [20:56] By gconftool-2 you just directly modify the database, you don't leave the admin any choice... [20:56] That's why most packages have gconf files instead of code, afaik.. [20:56] I don't mind in either case - I just thought that was the way to go [20:57] hmm, right, I guess we'll have to carry these as part of the ubuntu packaging for now, lacking a better place to put it upstream [20:58] Should I mail them directly to you when I'm done? [21:01] yep [21:01] Thanks! :) [21:01] though the tricky part will be to install them only when running a fat client [21:01] Why? [21:01] or does that also work for regular thin client ? [21:02] Thin clients don't have gconf, so it shouldn't matter if the files are there [21:02] Thin clients with localapps also don't have gconf [21:02] Thin clients with many many localapps which have gconf by an admin's mistake, should also have those gconf files [21:02] So I think we're ok in shipping them in any case... [21:02] ok [23:58] hey