Started logging meeting in #debian-edu, times are UTC.<br />
[19:00:33] &lt;h01ger&gt; \o/<br />
[19:00:35] * danielsan = Daniel Hess<br />
[19:00:42] * h01ger = Holger Levsen<br />
[19:00:43] &lt;vagrantc&gt; well, why not identify yourself with /me == Name<br />
[19:00:52] * vagrantc = Vagrant Cascadian<br />
[19:00:59] * pere = Petter Reinholdtsen<br />
[19:01:39] &lt;h01ger&gt; #topic agenda at http://wiki.debian.org/DebianEdu/Meeting - please add your topics now and tell vagrantc :)<br />
[19:02:06] * danielsan thinks we could skip #1 :)<br />
[19:02:23] &lt;vagrantc&gt; anyone mind me just taking moderatorship?<br />
[19:02:39] &lt;danielsan&gt; vagrantc: no, please go ahead and thanks<br />
[19:03:00] &lt;h01ger&gt; vagrantc, no, please go aheads & thanks!<br />
[19:03:01] * klausade = Klaus Ade Johnstad<br />
[19:03:21] * itais =José L. Redrejo<br />
[19:03:26] &lt;vagrantc&gt; #topic 2.1 Next (Lenny based) release : Name and version number <br />
<a name='0'></a>
[19:03:51] * pere believe we should stick to planets in the solar system if we are going to pick a name.<br />
<a name='1'></a>
[19:03:55] &lt;h01ger&gt; http://doodle.com/participation.html?pollId=ycn7rw4rtiasbmy6 says that everybody who participated in the poll was favoring "5.0r0"<br />
[19:04:15] &lt;h01ger&gt; but then vagrantc hat the great idea of "5.05r0~edu.r0"<br />
[19:04:17] &lt;h01ger&gt; (or such)<br />
[19:04:27] &lt;itais&gt; shit<br />
[19:04:29] &lt;vagrantc&gt; or +eduN<br />
[19:04:35] &lt;itais&gt; you must be kidding<br />
<a name='2'></a>
[19:04:45] &lt;h01ger&gt; http://doodle.com/participation.html?pollId=cvt5bi5qz5x2iu7a says that everybody who participated in the poll was favoring not to use codenames, except white.<br />
[19:04:51] &lt;danielsan&gt; 5.0+edu1 no?<br />
[19:05:17] &lt;vagrantc&gt; my proposal was to simply tack on +eduN to whatever version debian uses.<br />
[19:05:19] &lt;itais&gt; well, that's easier to read, but I can not imagine how to say "5.05r0~edu.r0" to the users<br />
[19:05:42] &lt;danielsan&gt; five dot zero plus edu one?<br />
[19:05:47] &lt;h01ger&gt; 5.0r0+edu1 was vagrantcs proposal<br />
[19:05:48] &lt;itais&gt; what's wrong with Debian Edu 5.0r0?<br />
[19:06:03] * h01ger had bad memory<br />
[19:06:14] &lt;h01ger&gt; itais, we also have point upgrades<br />
[19:06:18] &lt;vagrantc&gt; itais: it doesn't give room for debian-edu to make a sub-release outside of debian's cycle.<br />
[19:06:39] &lt;itais&gt; why? you always can say 5.0r1, 5.0r2, etc.<br />
[19:06:42] &lt;danielsan&gt; and does not show that we are almost debian<br />
[19:06:43] &lt;h01ger&gt; 5.0r2+edu4 is not that hard, IMHO<br />
[19:06:53] &lt;h01ger&gt; itais, no, those are debian numbers<br />
[19:07:27] &lt;itais&gt; h01ger, it's not hard for me, but think of telling to a school teachers, hey, I'm going to install here 5.05r0~edu.r0<br />
[19:07:48] &lt;h01ger&gt; itais, not 5.05r0~edu.r0 - 5.0r0+edu0<br />
[19:08:02] &lt;pere&gt; ~ is not a well known characters outside hardcore unix communities.<br />
[19:08:28] &lt;pere&gt; ran into a windows user the other day that was convinced the /~pere/ part in my URL was a typo.<br />
[19:08:30] * h01ger nods, but vagrantc didnt suggest ~ in the thread where people agreed<br />
[19:08:39] &lt;h01ger&gt; 5.0r0+edu0<br />
[19:08:44] &lt;danielsan&gt; one question is, whould it be 5.0r0+edu1 and then 5.0r1+edu1 or 5.0r1+edu2?<br />
[19:08:56] &lt;h01ger&gt; debian will release 5.0r1<br />
[19:08:57] &lt;itais&gt; :) good question<br />
[19:08:58] &lt;h01ger&gt; so<br />
[19:09:08] &lt;vagrantc&gt; i think it's really more of a + anyways, as it's actually additional stuff above and beyond plain debian at this point<br />
[19:10:47] &lt;pere&gt; will the rest of the debian community react negatively if we use a string too close to the official one?<br />
[19:11:07] * h01ger doubts it as we are debian for more than 99.9%<br />
[19:11:15] &lt;danielsan&gt; if we prefix something, why should one?<br />
[19:11:18] &lt;h01ger&gt; and its just a version number<br />
[19:11:19] &lt;vagrantc&gt; #link http://doodle.com/participation.html?pollId=cvt5bi5qz5x2iu7a<br />
<a name='3'></a>
[19:11:29] &lt;vagrantc&gt; #link http://doodle.com/participation.html?pollId=ycn7rw4rtiasbmy6<br />
<a name='4'></a>
[19:11:55] &lt;vagrantc&gt; h01ger: what was poll 1 of 3 ?<br />
[19:12:02] &lt;h01ger&gt; itais, the name to tell other people is "Debian Edu lenny" anyway, not "Debian Edu 5.0r0+edu1"<br />
[19:12:06] &lt;danielsan&gt; or suffix :)<br />
[19:12:31] &lt;h01ger&gt; vagrantc, pollId=ycn... was poll1<br />
[19:12:47] &lt;itais&gt; so, at the end, I will tell Debia Edu lenny, and Debian Edu lenny r1, and so on, so who cares about the name we use internally?<br />
[19:12:51] &lt;vagrantc&gt; h01ger: ah yes, 3 of 3 ?<br />
<a name='5'></a>
[19:13:09] &lt;h01ger&gt; http://doodle.com/participation.html?pollId=bcb76h6f2cep9hud is poll three and there everybody except two people said we should release when its ready. <br />
[19:13:21] &lt;h01ger&gt; itais, yes, i'd say so<br />
[19:14:35] &lt;h01ger&gt; so lets go for 5.0r0+edu0 ?<br />
[19:14:51] &lt;h01ger&gt; (and communicate "Debian Edu lenny")<br />
[19:15:59] * danielsan likes the suffix thing<br />
[19:16:24] * itais has no problem with that<br />
[19:16:56] &lt;vagrantc&gt; any outstanding concerns?<br />
[19:17:48] &lt;h01ger&gt; we have 2 more polls to discuss :)<br />
[19:17:53] &lt;h01ger&gt; and 43min left<br />
[19:18:00] &lt;h01ger&gt; (and other topics)<br />
[19:18:01] &lt;vagrantc&gt; alright, dare i say:<br />
[19:18:18] &lt;vagrantc&gt; #agreed use 5.0r0+edu0 for initial release<br />
<a name='6'></a>
[19:18:31] &lt;h01ger&gt; :)<br />
[19:18:52] &lt;pere&gt; get the spec for the next version too.<br />
[19:18:58] &lt;pere&gt; is it edu1 or r1?<br />
[19:19:12] &lt;h01ger&gt; r1 is what debian uses<br />
[19:19:14] &lt;h01ger&gt; so its edu1<br />
[19:19:27] &lt;h01ger&gt; vagrantc, please add this to #agreed<br />
[19:19:40] &lt;danielsan&gt; ro ...r1+edu1?<br />
[19:19:45] &lt;danielsan&gt; s/ro/so/<br />
[19:19:55] &lt;vagrantc&gt; pere: you just want clarity, or actually have concerns about it?<br />
[19:20:00] &lt;h01ger&gt; danielsan, we increase rX whenever debian does a pointrelease..<br />
[19:20:03] &lt;pere&gt; vagrantc: I want clarity.<br />
[19:20:44] &lt;h01ger&gt; pere, solved?<br />
[19:20:49] &lt;danielsan&gt; h01ger: right :)<br />
[19:21:02] &lt;pere&gt; h01ger: assuming it make it into the summary, sure.<br />
[19:21:15] &lt;vagrantc&gt; i think the eduN should only be incremented when debian-edu makes a new release.<br />
[19:21:16] * danielsan will take care<br />
[19:21:39] &lt;h01ger&gt; so, codename? agreed to drop it?<br />
[19:21:42] &lt;danielsan&gt; vagrantc: if we don't release noone would know that we incerement it :)<br />
[19:22:00] &lt;vagrantc&gt; danielsan: indeed.<br />
[19:22:29] &lt;danielsan&gt; we already have the codename of the debian version we base on<br />
[19:23:01] * vagrantc sees multiple codenames as confusing.<br />
[19:23:44] &lt;pere&gt; vagrantc: confusing for whom?  edu users know which code name they are using (like terra), but not which name it was based on.<br />
[19:24:10] * pere do not care much about code name, but believe we should stick to the planet theme if we keep it.<br />
[19:24:10] &lt;danielsan&gt; pere: at least in the sources.list there is still lenny<br />
[19:24:25] &lt;h01ger&gt; pere, you voted against the codename. everybody except white did. and no-one came up with good reasons for it..<br />
[19:25:22] &lt;vagrantc&gt; h01ger: are we looking at the same poll? http://doodle.com/participation.html?pollId=cvt5bi5qz5x2iu7a<br />
[19:25:40] &lt;h01ger&gt; yup<br />
[19:26:02] &lt;pere&gt; h01ger: as I remember it, I voted against luna.<br />
[19:26:28] &lt;vagrantc&gt; there's luna, no codename, mars and pluto as choices<br />
[19:26:40] &lt;h01ger&gt; <nitpick>pere, but you voted for pluto, which is not a planet :-D</nitpick> - the votes are in the url vagrantc just repeated<br />
[19:27:23] &lt;pere&gt; are we going to discuss my votes, or something else?<br />
[19:27:43] &lt;pere&gt; I suggested having all the unused planet names as options, but did not spend time on pressing the issue.<br />
[19:28:44] &lt;danielsan&gt; well we could talk about the code name for a while, but as (almost) anybody seems ok with no codename why don't we go for it?<br />
[19:29:08] &lt;danielsan&gt; wasn't it sarge who also has not had a codename?<br />
[19:29:28] &lt;h01ger&gt; 12 voted. 11 in favor of "no codename". why are we discussing this at all?<br />
[19:29:47] &lt;h01ger&gt; also noone came up with a good reason _for_ a codename, except nostaligy<br />
[19:30:03] &lt;h01ger&gt; while two people said the codename is causing confusing, and thus hurts<br />
[19:30:25] &lt;h01ger&gt; we had 3 releases so far. 1 without codename (sarge), 2 with (woody+etch)<br />
[19:30:56] &lt;pere&gt; sarge could be seen as a anomality.<br />
[19:31:20] &lt;danielsan&gt; how about another one? :)<br />
[19:32:26] &lt;vagrantc&gt; it seem slike there is an overwhelming vote in favor of no codename, but i hear some outstanding ... cornerns about simply moving forward ?<br />
[19:32:27] &lt;itais&gt; I'm with h01ger: we should respect the result of the votation, 11 against 1 is quite clear, and we should pass to the next item<br />
[19:33:54] &lt;vagrantc&gt; pere: you've been the voice in support of codenames, do you have outstanding concerns with "no codename" ?<br />
[19:34:25] &lt;pere&gt; vagrantc: not really.  Suspect it might help with marketing, but do not have any strong opinion on the topic.<br />
[19:34:39] &lt;vagrantc&gt; lets move on then.<br />
[19:34:52] &lt;h01ger&gt; .oO( "lenny" helps with marketing. "lenny mars" confuses )<br />
[19:35:00] &lt;h01ger&gt; the third poll... "release when"... <br />
[19:35:05] &lt;vagrantc&gt; #agreed we will simply use lenny as a codename<br />
<a name='7'></a>
[19:35:13] &lt;h01ger&gt; "...its ready!"<br />
[19:35:40] * h01ger would like to define what "ready" means. unfortunatly i didnt manage to put all the issue on http://wiki.debian.org/DebianEdu/Status/Lenny into bugs<br />
[19:35:43] &lt;h01ger&gt; yet<br />
[19:35:49] &lt;h01ger&gt; but what are our blockers?<br />
[19:35:57] &lt;vagrantc&gt; seems the result of the vote is to release when ready ...<br />
[19:36:03] &lt;danielsan&gt; tasksel<br />
[19:36:08] &lt;vagrantc&gt; #link http://doodle.com/participation.html?pollId=bcb76h6f2cep9hud<br />
<a name='8'></a>
[19:36:09] &lt;pere&gt; there are several blockers.<br />
[19:36:11] &lt;h01ger&gt; do we need a fixed lwat? (ie for editing dhcp entries with it)<br />
[19:36:29] &lt;pere&gt; h01ger: yes, probably.<br />
[19:36:42] * h01ger suggests to split the issues in http://wiki.debian.org/DebianEdu/Status/Lenny into "normal issues" and "blocking issues" now <br />
[19:36:55] &lt;pere&gt; should we change topic?<br />
[19:37:25] &lt;vagrantc&gt; #topic 2.2 Next (Lenny based) release : Current state of our Lenny <br />
<a name='9'></a>
[19:37:45] &lt;vagrantc&gt; how is lenny looking for debian-edu ?<br />
[19:38:00] &lt;pere&gt; the package installation is broken because I tried to add desktop and language specific packages.<br />
[19:38:19] &lt;pere&gt; when it was working, ltsp clients did not boot via pxe, at least when I used qemu.<br />
[19:38:29] &lt;h01ger&gt; mostly ready (bug wise), but we lack features.<br />
[19:38:44] * h01ger would add like to stop adding features so we can concentrate on the bugs<br />
[19:39:09] &lt;danielsan&gt; some important ones<br />
[19:39:10] &lt;pere&gt; the partition sizes generated by the installer are too small, which is worked around by extending partitions during installation, but this lead to fsck on first boot because of a misfeature in online ext3 resizing.<br />
[19:39:38] &lt;pere&gt; a fix is to make sure the minimum partition sizes are large enough to avoid resizing during normal installs.<br />
[19:39:40] * h01ger adds what pere just said to the status page<br />
[19:40:03] &lt;pere&gt; the edu-expert profile question is messed up in text mode.<br />
[19:40:16] &lt;h01ger&gt; pere, for all languages?<br />
[19:40:22] &lt;pere&gt; h01ger: not sure.<br />
[19:40:23] &lt;itais&gt; and the ldapify is not done yet<br />
[19:40:37] * h01ger suggests to either drop the sugar profile from expert mode or upload jonas' sugar backports to our repo<br />
[19:40:42] &lt;pere&gt; yes, dhcp uses ldap for its info, but we do not have any tools to maintain it.<br />
[19:41:10] &lt;pere&gt; h01ger: I agree to the dropping sugar.  we can make a sugar CD instead if we got time.<br />
[19:41:15] &lt;itais&gt; and not for pdns, nor fill the ldap tree with the right configs<br />
[19:41:30] &lt;pere&gt; itais: yeah, DNS config is not (yet) in LDAP.<br />
[19:41:50] &lt;pere&gt; italc or the controlaula stuff should probably be configured to work out of the box.<br />
[19:41:54] * h01ger asks everyone to update the status page with known issues (or the state of them). i would also suggest to really define the blockers for our lenny release based on bug numbers in the next irc meeting (which we should have sooner again) - i would also promise to file bugs for each issue on the status page<br />
[19:42:19] &lt;pere&gt; we should get the OCS Inventory stuff configured out of the box.<br />
[19:42:22] * h01ger adds "dropping sugar" to the page<br />
[19:42:52] &lt;itais&gt; for the client it's pretty easy, for the server I don't see it possible unless a good amount of work is done via cfengine (for OCS inventory)<br />
[19:43:16] &lt;pere&gt; we should fix PXE install setup to work also for DVD installs (the d-i PXE images are missing in the archive, currently downloaded on the fly).<br />
[19:43:28] &lt;pere&gt; itais: yes, the server part is the problem.<br />
[19:43:42] &lt;vagrantc&gt; seems like the topic has naturally moved on to the next point:<br />
[19:43:44] &lt;itais&gt; another possibility is making some inventory.skolelinux.org server and not installing the inventory in the school, only configurating the client to send the data there, as popcon<br />
[19:43:59] &lt;vagrantc&gt; #topic 2.3 Next (Lenny based) release : bugs+features that need fixing before we can release <br />
<a name='10'></a>
[19:44:19] &lt;h01ger&gt; #info please update http://wiki.debian.org/DebianEdu/Status/Lenny<br />
<a name='11'></a>
[19:44:25] &lt;pere&gt; itais: I would be very mad if my hosts submitted that amount of info out of the site.<br />
[19:44:49] &lt;pere&gt; it would be nice if we could get the roaming laptop stuff working.<br />
[19:44:49] &lt;h01ger&gt; itais, why not setting up tjener as an ocs inventory server?<br />
[19:45:04] &lt;pere&gt; h01ger: because it is hard to do automatically at install time.<br />
[19:45:12] &lt;h01ger&gt; ah, that bug<br />
[19:45:12] &lt;itais&gt; h01ger: because the deb package can not be preseeded and it's not easy to configure<br />
[19:45:23] * h01ger looks that bug up<br />
[19:45:26] &lt;pere&gt; when installing the main-server on a laptop, network-manager is installed, messing up the network configuration.<br />
[19:45:38] &lt;itais&gt; pere: about the roaming stuff,it's not hard, maybe we might do the same with all the pcs, not only laptops<br />
[19:45:43] &lt;pere&gt; this is actually because the debian laptop task is installed by default.<br />
[19:46:05] &lt;pere&gt; itais: yes, I believe it should be the default for all installs, if it work.<br />
[19:46:27] &lt;itais&gt; pere: why does network-manager mess the configuration?<br />
[19:46:49] &lt;itais&gt; it should not do it, in fact it does not do it in the laptops I've set up<br />
[19:47:03] &lt;pere&gt; itais: because it block network setup from happening at boot.  it only happen after the user log in, and no user can log in because the network isn't configured.<br />
[19:47:07] &lt;vagrantc&gt; as a time check, we have 14 minutes left, and 2-3 remaining agenda items...<br />
[19:47:23] &lt;itais&gt; pere: it should not be that way<br />
[19:47:32] &lt;pere&gt; I guess my point is that there is a lot of stuff left to fix in the lenny version.<br />
[19:47:32] &lt;vagrantc&gt; (usbstick images, other business, next meeting)<br />
[19:47:41] &lt;itais&gt; network-manager gets an ip as soon as a dhcp server is available when using a cable connection<br />
[19:47:42] &lt;pere&gt; who did a lenny install recently?  on real hardware?<br />
[19:47:48] &lt;itais&gt; what you say happens when using wireless<br />
[19:47:55] &lt;itais&gt; pere: me, today<br />
[19:48:08] &lt;pere&gt; itais: with kde?<br />
[19:48:18] &lt;itais&gt; not :'(<br />
[19:48:24] &lt;h01ger&gt; pere, if ocs-inventory needs mysql running (which is not the case in d-i..), one can use a firstboot script to configure it. (a script that runs upn the first boot)<br />
[19:48:31] &lt;pere&gt; btw, I suspect kdm isn't able to handle expired passwords properly.  this is annoying.<br />
[19:48:45] * h01ger can confirm the kdm issue<br />
[19:49:04] &lt;pere&gt; h01ger: sure, or start mysql from d-i to configure it, or something.  someone just need to do the work.<br />
[19:49:06] * vagrantc suspects ldm doesn't handle all cases of password expiry either<br />
[19:49:13] &lt;h01ger&gt; definitly for 3.5.5, not fully sure about 3.5.9<br />
[19:49:23] &lt;klausade&gt; pere: did ltspserver install yesterday, also no kde.<br />
[19:49:24] &lt;h01ger&gt; pere, right :)<br />
[19:49:43] &lt;pere&gt; there is also the iceweasel SSL cert issue.  it refuses to connect to our web site.<br />
[19:49:47] &lt;danielsan&gt; pere: don't forget start-stop-deamon does not work during install<br />
[19:49:58] &lt;pere&gt; danielsan: I did not say it was easy. :)<br />
[19:50:46] &lt;h01ger&gt; pere, i dont think the iceweasel ssl issue is (or should be) release critical. we can say: "you have to use konqueror for the internal server"<br />
[19:51:04] &lt;pere&gt; also, I suspect we should extend the IP range of the backbone network from 10.0.2.0/23 to something/22 or perhaps even /16.<br />
[19:51:11] &lt;vagrantc&gt; so, we have a list of issues reported in irc, can someone go through the logs and make sure they're appropriately added to the lenny status page, and/or file bug reports?<br />
[19:51:42] &lt;h01ger&gt; best those people who said them. because they probably know these issues best<br />
[19:51:59] &lt;pere&gt; I also believe we should rewrite the squid configuration to avoid the hardcoded IP address and instead use all subnets listed in LDAP.<br />
[19:52:10] &lt;h01ger&gt; and please file bug instead. using the wiki page doesnt work well, or at least i learned from the etch release that using  bugzilla works _much_ better<br />
[19:52:12] &lt;danielsan&gt; maybe we could do a package that creates a ca on tjener, that can be used with tinyca. but still there is the problem that how to get the ca onto the workstations<br />
[19:52:14] * pere doubt he will find time to do it, and thus prefer others to look into it.<br />
[19:52:22] &lt;itais&gt; there's still a lot of remaining work, so volunteers?<br />
[19:52:28] &lt;pere&gt; I got one our off today, but reporting all these bugs will take a while.<br />
[19:53:11] &lt;klausade&gt; h01ger: it's rather easy to include sites to exlude from ssl checks, it's just a small hack to the global firefox/profile. it defeats all security ...<br />
[19:53:12] &lt;pere&gt; please do test installs, fix stuff, and more test installs.  also, test on real hardware, to discover hardware issues.  I'm told that X.org vesa driver do not work in lenny.  it is probably fatal for us.<br />
[19:53:18] * h01ger thinks we should stop adding features (like rewrite squid conf) and rather get a bug free release out the door. squeeze will come/freeze in 18 months (approx), so we should not shorten our squeeze development cycle too much<br />
[19:53:51] &lt;pere&gt; h01ger: well, some of us are not happy with all the hardcoded IP addresses.<br />
[19:54:03] &lt;h01ger&gt; klausade, see.. if this was an issue tracked as a bug it would be very easy to add the info there :)  (of course its also easy to add to the status page, but...)<br />
[19:54:34] &lt;vagrantc&gt; with 7 minutes left, shal we postpone the discussion on usbticks and other business, and move towards hashing out the next meeting time?<br />
[19:54:38] &lt;h01ger&gt; pere, its in 3 files or so. not that many. i believe, more people would profit from an earlier release than from that feature :)<br />
[19:54:39] &lt;pere&gt; hardcoded IP addresses only belong in the DHCP and DNS config, I believe.<br />
[19:54:44] &lt;h01ger&gt; vagrantc, yes. please move on<br />
[19:54:56] * h01ger thinks its important to define a next meeting<br />
[19:54:58] &lt;vagrantc&gt; #topic Next meeting?<br />
<a name='12'></a>
[19:55:13] &lt;pere&gt; I might be able to make every three weeks.<br />
[19:55:15] &lt;h01ger&gt; #info no agreement on release blockers found.<br />
<a name='13'></a>
[19:55:33] &lt;danielsan&gt; wednesdays seem to work best<br />
[19:55:46] &lt;danielsan&gt; #link http://wiki.debian.org/DebianEdu/Meeting/VoteForDate<br />
<a name='14'></a>
[19:55:50] &lt;pere&gt; #info several potential release blockers mentioned.<br />
<a name='15'></a>
[19:55:52] * h01ger would rather prefer every two weeks but prefers peres participation more :)<br />
[19:56:08] * pere have not had time to do test installs since the devcamp. :(<br />
[19:56:16] &lt;itais&gt; pere: I've removed all the hardcoded ip from my squid conf, but I remember you told me you needed them due to some license issues<br />
[19:56:23] &lt;vagrantc&gt; wednesdays work good for me<br />
[19:56:24] &lt;itais&gt; it's that right?<br />
[19:56:36] * h01ger sighs<br />
[19:56:45] &lt;vagrantc&gt; andreas made a request for a different time<br />
[19:56:51] &lt;pere&gt; thursday are busy for me.<br />
[19:56:59] &lt;danielsan&gt; hour later, yes<br />
[19:57:12] &lt;itais&gt; wednesdeays are ok for me, and an hour later is not a problem <br />
[19:57:20] &lt;danielsan&gt; that would make the meeting end at 22:00 localtime for most people<br />
[19:57:41] &lt;h01ger&gt; or 8am for white, iirc. which maybe could even work :)<br />
[19:57:42] &lt;danielsan&gt; at least until march :)<br />
[19:58:23] &lt;pere&gt; 22:00 is a bit late for me.<br />
[19:58:32] * pere is getting up rather early these days.<br />
[19:58:49] &lt;pere&gt; itais: did you find time to look at the tasksel issue, btw?<br />
[19:58:50] &lt;itais&gt; ah, I thought you did not even go to bed ;)<br />
[19:58:50] &lt;vagrantc&gt; 3 weeks from now would be november 26th<br />
[19:59:04] &lt;h01ger&gt; i wont be able to make that date<br />
[19:59:07] &lt;itais&gt; pere: not, I even forgot it buried in a pile of work<br />
[19:59:15] &lt;h01ger&gt; i will be traveling to extremadura that date :)<br />
[19:59:22] &lt;h01ger&gt; (+time)<br />
[19:59:40] &lt;pere&gt; itais: if you get it working, you could install the gnome version by adding desktop=gnome on the Cd boot propmt.<br />
[19:59:46] &lt;vagrantc&gt; 2 weeks from now, november 19th<br />
[19:59:53] &lt;vagrantc&gt; and 4 weeks from now, december 3rd<br />
[20:00:07] &lt;itais&gt; pere: then I should find some time slot to work on it :)<br />
[20:00:33] &lt;itais&gt; as the lenny release is closer I think we should do it in 2 weeks<br />
[20:00:41] * vagrantc concurs with itais <br />
[20:00:44] * pere will try to show up.<br />
[20:00:45] &lt;itais&gt; to avoid people begin to relax<br />
[20:00:53] * h01ger too<br />
[20:01:00] &lt;pere&gt; should we plan another devcamp?  we got the funds for it. :)<br />
[20:01:10] &lt;vagrantc&gt; november 19th, 19:00 UTC ?<br />
[20:01:23] * itais agrees<br />
[20:01:29] &lt;danielsan&gt; ok for me<br />
[20:02:17] * pere will do its best.<br />
[20:02:19] &lt;danielsan&gt; and as andreas did not show up yet, one hour seems not to be enough :)<br />
[20:03:08] &lt;vagrantc&gt; ok, i'll call it:<br />
[20:03:24] &lt;vagrantc&gt; #agreed next meeting, november 19th, 19:00 UTC<br />
<a name='16'></a>
[20:03:32] &lt;vagrantc&gt; thanks everyone!<br />
[20:03:33] &lt;danielsan&gt; \o/<br />
[20:03:36] &lt;vagrantc&gt; #endmeeting<br />
<hr>Meeting ended.<br /><hr><p>Information on meetbot is available at <a href='http://meetbot.debian.net'>meetbot.debian.net</a></p>