=== Varka_ is now known as Varka [01:49] @schedule denver [01:49] Schedule for America/Denver: 18 Dec 08:00: Server Team meeting | 20 Dec 07:00: Desktop Team Development | 21 Dec 05:00: MOTU meeting === asac_ is now known as asac === czessi_ is now known as Czessi === \sh_away is now known as \sh [07:57] moin === cjwatson_ is now known as cjwatson === \sh is now known as \sh_away === bigon_ is now known as bigon === dholbach_ is now known as dholbach === Hobbsee_ is now known as Hobbsee === \sh_away is now known as \sh === ubotu changed the topic of #ubuntu-meeting to: Current meeting: Server Team meeting Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting === ubotu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Dec 14:00 UTC: Desktop Team Development | 21 Dec 12:00 UTC: MOTU meeting [16:00] #startmeeting [16:00] Meeting started at 16:00. The chair is soren. [16:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:00] Welcome to the Ubuntu Server community meeting. [16:00] First: Introduction round: [16:00] I'm Soren. I work for Canonical on the server team. [16:01] Mathiaz in hiking around in Laos. dendrobates is busy. [16:01] Tough crowd... [16:01] :P [16:01] hey soren [16:01] Am I the only one here? [16:02] no, I am here [16:02] do we also have to introduce? :) [16:02] That was the plan. [16:02] I'm Mario, I'm an upstream developer for various projects [16:02] most notable of them probably being Libburnia project [16:02] hello [16:03] I'm Adam Sommer so far working moslty on the Server Guide documentation [16:03] * nijaba thinks that sommer does a great job at it [16:03] nijaba, jdstrand: We're just introducing ourselves... [16:03] ah [16:03] nijaba: thx man [16:04] oh yes, I also wrote the Edubuntu Handbook :P [16:04] we were just doing some intros [16:04] So I'm Nick Barcet, Ubuntu Server product manager [16:04] I am Jamie Strandboge and am an Ubuntu Security Engineer. I help with Ubuntu Server wherever I can [16:04] Ok, I think that's everyone? [16:04] yup, seems so [16:05] Agenda is at https://wiki.ubuntu.com/ServerTeam/Meeting [16:05] [TOPIC] Review ACTION points from previous meeting. [16:05] New Topic: Review ACTION points from previous meeting. [16:05] Meeting log: [16:05] https://wiki.ubuntu.com/MeetingLogs/Server/20071211 [16:05] hey [16:05] ACTION: nijaba will revise the minimum requirements to include tasksel tasks [16:06] Hi, zul. [16:06] done [16:06] * soren hugs nijaba [16:06] That's it, it seems :) [16:06] * nijaba blushes [16:06] [TOPIC] Review each section of the ServerTeam/Roadmap. [16:06] New Topic: Review each section of the ServerTeam/Roadmap. [16:06] https://wiki.ubuntu.com/ServerTeam/Roadmap [16:06] For your clicky-clicky pleasure.. [16:07] Triage openldap bugs [16:07] I've not looked this one bit, I'm afraid. Anyone? [16:08] No? I blame the holidays. [16:08] Triage samba bugs [16:08] Same.. :( [16:08] mathiaz is our master bug triager :) [16:08] it does seem like things have slowed down... is that normal for this time of year [16:08] * nijaba think that thaïland should be forbidden to ubuntu devs [16:09] ..and Laos. [16:09] :) [16:09] sommer: kees and I triaged a couple CVEs ;) [16:09] * soren ^5s jdstrand [16:09] And I triagged a few JeOS issues [16:09] * soren hugs nijaba again [16:09] (that was actual meant for soren -- little to quick on the tab) [16:10] s/to/too/ [16:10] Ok, let's just leave those two items there, shall we? [16:10] Packager corner [16:10] Merge packages from Debian [16:10] * jdstrand wonders how long he can blame his keyboard for his typing skills... [16:10] I think we managed to get to the bottom of these. [16:10] jdstrand: :) [16:11] Improve apache package [16:11] Not assigned to anyone.. [16:11] as soren knows, he reviewed and uploaded the libnss-ldap and libpam-ldap merges of mine [16:11] jdstrand: Sure did. :) [16:11] Has anyone looked at "Default ssl configuration for apache"? [16:12] * nijaba thinks it is his turn to hug someone... soren and jdstrand maybe ? [16:12] :) [16:12] * jdstrand always welcomes a hug, and hugs nijaba back :) [16:12] It seems not. Any takers? [16:12] (The "Default ssl configuration for apache" thing. Not the hugs) [16:13] soren: there was a gutsy goal for bug #135624 [16:13] Launchpad bug 135624 in php5 "libapache2-mod-php5 should provide LAMP test page" [Low,Triaged] https://launchpad.net/bugs/135624 [16:13] jdstrand: Did that involve ssl? [16:13] so apache is going to inlcude ssl or will it be a seperate apache-ssl package? [16:14] separate package, being pulled automatically is the way to go me things =) [16:14] sommer: apache-ssl is a completely different thing. [16:14] the main problem is that the script to generate the certificates is missing it seems [16:14] * pygi hides [16:14] soren: heh. uh, no... [16:14] nijaba: It's there. It's in ssl-cert. [16:14] * jdstrand stops 'oh-ohing' and puts his hand down [16:14] nijaba: because we used to have the script before, today you have to do it manually [16:14] with openssl thingy [16:14] pygi: It's in ssl-cert? [16:14] no idea, I didnt check === \sh is now known as \sh_away [16:14] but by default, it's not there :p [16:15] $ dpkg -L ssl-cert | grep make-ssl-cert [16:15] /usr/sbin/make-ssl-cert [16:15] soren: it used to be in path, so it was easy [16:15] /usr/sbin is in $PATH [16:15] doesn't ssl-cert generate the snake-oil cert and key? [16:15] sommer: Yes. [16:15] gotcha, is the plan to use that for apache? [16:16] sommer: I'd sure assume so. [16:16] I am talking about apache2-ssl-certificate which used to be there and is still referenced in a few docs [16:16] That's the right thing to do if you're not using proper certificates. [16:16] nijaba: Ok. We should fix the docs then. [16:16] nijaba: ..and make it all easier. I do remember it being quite a bit more tricky than necessary. [16:16] soren: fine with me [16:17] sommer: Will you look into this? [16:17] soren: sure [16:17] sommer: You can try to document it, and I can do any code changes if you find something that should be obviously better. [16:17] I would recommend adding a "apache2-ssl-certificate" page to the wiki that points to the new up to date procedure [16:17] I don't think the apache2-ssl-certificate is mentioned in the "official" docs, but I seem to remember it's in the wiki [16:18] [ACTION]: sommer will look into documenting how to set up apache with ssl [16:18] ACTION received: : sommer will look into documenting how to set up apache with ssl [16:18] Ok, next item.. [16:19] "Notify need to restart apache2 when installing a new module" [16:19] I belive I contested this last time. [16:19] google 'apache2-ssl-certificate site:help.ubuntu.com' [16:19] Which modules require a restart and don't do it? [16:19] Yes, that's the answer I got last time, too. [16:19] nijaba: cool not too many [16:20] sommer: still think that we should have a wiki explaining the change and the correct procedure [16:20] Does anyone object to removing that item from the Roadmap? I've not seen any evidence that this issue exists? [16:20] nijaba: yep, I'll create a page and link it to the main apache article [16:21] soren: no problem with me... I'd think there'd be more bugs related to the issue. [16:21] sommer: If you see any, could you send me the link at some point? [16:21] sure [16:21] Thanks. [16:21] * jdstrand tentatively raises his hand, and asks soren if we can talk about bug #135624 [16:21] Ok, moving right along.. [16:21] Launchpad bug 135624 in php5 "libapache2-mod-php5 should provide LAMP test page" [Low,Triaged] https://launchpad.net/bugs/135624 [16:22] Um... Well, yes, I guess it's sort of related. [16:22] it is related in that its LAMP [16:22] it was something that was supposed to get into gutsy, but didn't [16:22] jdstrand: Right. What has Debian said about it? [16:22] Nothing, it seems. :( [16:22] nothing-- a debdiff has been languishing in the BTS [16:23] since it doesn't look like we will get it for free, maybe it should be added to the Roadmap [16:23] the debdiff is easy-- there is one in the LP bug too [16:23] jdstrand: We've got both apache and php maintainers on staff. You should poke someone. :) [16:24] * jdstrand goes off poking... [16:24] soren: should it be added to the Roadmap? [16:24] jdstrand: We could do that. [16:24] (not the poking-- the task) [16:25] :) Sure. [16:25] I'll do that when we're done here. [16:25] I think it'd be a good idea so it won't be forgotten [16:25] soren: thanks! :) [16:25] Ok. Next item: "Improve mysql package upgrade" [16:25] Who added this? [16:25] mathiaz I think [16:25] Does anyone what the issue is? [16:26] wasn't there something during UDS about that? [16:26] Insert "know" where appropriate. [16:26] sommer: If there were, I forgot. [16:27] schedule @berlin [16:27] ya, I seem to remember some discussion about it... my not have been at UDS though [16:27] maybe there was a bug? [16:27] Ok.. If noone knows what it's about, let's skip it for now. [16:28] I can't spot it. [16:28] soren: please do skip^ [16:28] Next item: "Improve php modules packages" [16:28] The issue being that newly installed php modules should cause a restart of apache. [16:29] ivoks was supposed to be working on ditching libapache2-mod-php5, so it becomes a php problem rather than an apache problem. [16:30] ...and it that case, I don't think it'll be much of a point of discussion. The problem so far has been that php should unconditionally restart apache as it wasn't sure that apache was even using php. [16:30] shouldn't unconditionally... [16:31] Man, typing *is* hard. [16:31] Hmm... The ditching libapache2-mod-php5 should be on the roadmap, too. [16:31] I agreed that it should be suggested, not forces [16:31] or "instead" rather. [16:32] nijaba: What should? [16:32] reloading of apache [16:32] nijaba: Right. When we ditch mod-php5, it seizes to be an issue. [16:33] Anything else about this? [16:33] Ok, next item: "Integration of Dovecot SASL and Postfix" [16:33] I've been discussing this with ivoks a bit, but I'm not sure how far along he's come. [16:34] soren: didn't I saw diffs he proposed? [16:34] nijaba: Yes, but they were rejected. [16:34] nijaba: By me. [16:35] :) [16:35] I'll make a note of poking ivoks about it when he shows up again. [16:35] soren: right... so since he his not around today, let's skip [16:36] The next few items, I'm not sure about. [16:36] "Update Ubuntu ServerTeam wiki pages" [16:36] Mathiaz is the assignee. I don't know the status, I'm afraid. [16:36] (Holidays are annoying) [16:36] "Write a How-To for Drupal on Ubuntu" [16:36] JimTarvid around? [16:37] Guess not. [16:37] soren: I haven't seen him since the 2nd or 3rd meeting [16:37] Ah. [16:37] Next: "Track pages on help.ubuntu.com that need to be updated" [16:37] sommer: status? [16:38] haven't concentrated on that one too much lately [16:38] sommer: Fair enough. [16:38] there's a list of Samba pages that need cleaned up [16:38] there's a lot of duplication, and I wasn't sure the best route to take [16:39] Something you need/want to discuss here? [16:39] I'd hate to remove a page and get into some kind of flame war about it [16:39] probably not a big deal, but some of the pages are rather long === _bigon is now known as bigon [16:40] I say to aim for quality rather than quantity. A lot of crap is still crap. [16:40] totally agree, I'll try to focus some on that this week [16:40] +1 [16:40] sommer: If you're completely rewriting, just move the old page to somewhere else (Blah/Old). [16:41] sommer: Great! [16:41] soren: good idea will do. [16:41] Next: "Update Server-Related Ubotu Factoids" [16:41] Did these get poked into ubotu yet? [16:41] ..some at least did. [16:42] I think nealmcb was testing them the other day [16:42] Ok. Does anyone have any input about this in nealmcb's absence? [16:43] Guess not. [16:43] "Review ServerGuide for Hardy" [16:43] sommer is doing a great job at it [16:43] Wonderful! [16:43] sommer: Do you want to talk about it? [16:44] sommer: It's fine if not. [16:44] sure, I was wondering if anyone could test the Backups section [16:44] I take it [16:44] I sent a message to the server ml, but haven't had much of a response so far [16:44] * sommer no longer has a tape drive [16:45] * soren neither :( [16:45] Will ask elmo to take a look as well [16:45] nijaba: cool, I added an archive rotation section that I think covers your previous suggestions [16:45] nijaba: I sent him an email as well, because I wasn't sure if he was on the server ml [16:45] not sure he is either [16:46] really no rush at this point [16:46] I'm also working on an eBox section, but wasn't sure of the status of it for Hardy? [16:47] I think soren said that he will check with updstream in jan. [16:47] sommer: I'm not really the one doing the work on it this time around. It's been "outsourced" to the eBox developers (upstream, I mean). [16:47] I'll be keeping an eye on it, though. [16:47] that's cool, I started a wiki page on help.u.c [16:48] sommer: eBox has a lot of documentation of its own, though. [16:48] sommer: Good stuff, afair. [16:48] ya, I'm working through it trying to document what's done so fare in Gutsy [16:48] Both developer, user, and installation guides. [16:48] soren: anything on developing specific plugin? [16:48] cool thankt [16:48] cool thanks [16:48] nijaba: :) [16:49] sommer: I honestly wouldn't bother. [16:49] sommer: The eBox stuff in gutsy is not worth mentioning. Quite the contrary, actually. [16:49] heh... also for my own learning... thinking about deploying it at work [16:49] with hardy that is [16:50] sommer: If you do, don't bother with the Ubuntu packages :) [16:50] sommer: Ah, ok. [16:50] soren: you mean, for gutsy? [16:50] nijaba: Yes. [16:50] Ok, moving on... [16:50] "Create Server GUI Wiki Page" [16:51] still on my todo list [16:51] Ok. [16:51] but if anyone else wants to start thats cool... heh [16:51] :) [16:51] Next: "Integrate AppArmor into Ubuntu" [16:51] That's done, surely? [16:51] It's installed by default even in gutsy.. Why is it on the roadmap? [16:52] odd... I guess it meant additional profiles [16:52] I also added an AppArmor section to the Server Guide. [16:52] Possibly. I'll ask mathiaz to update it. [16:52] sommer: Cool! [16:52] "Simplify storage management (RAID1 - LVM-on-RAID) during installation" [16:52] ivoks is not here, so we'll skip. [16:52] soren: I believe it is, at least in part, getting more profiles [16:52] jdstrand: Ok, cool. [16:52] (that was for apparmor) [16:53] [TOPIC] ruby-on-rails (What is the status of this?) [16:53] New Topic: ruby-on-rails (What is the status of this?) [16:53] Anyone? [16:53] ... [16:53] I think dendrobates was going to check up on it... from the last meeting [16:53] * nijaba grumbles about christmas [16:54] Yeah, and he's not here, so we lose :) [16:54] Moving right along.. [16:54] [TOPIC] JeOS tutorial (shall we redirect users from wiki to linuxtoday.com ?) [16:54] New Topic: JeOS tutorial (shall we redirect users from wiki to linuxtoday.com ?) [16:54] nijaba: Go! [16:54] The editor from linuxtoday.com do not want to publish our JeOS tutorial if it is published on our wiki. [16:54] A possible compromise would be to mofify our wiki so that it points to the rest of the article on linuxtoday.com for the 90days it will be published there. [16:54] We feel awkward about this and would love to have your opinion. [16:54] On one hand it would increase the visibility of JeOS a bit [16:54] On the other hand it would prevent us from editing (improve) it for a while. [16:55] What do you think? [16:55] so the article is redirected for 90 days then replaced after their article is taken down? [16:55] yes, that's the idea [16:55] doesn't seem too big a deal to me [16:56] any other comments? [16:56] * sommer votes to do it... seems like it will help in marketing and stuff [16:56] I would think we would want to be able to edit it, as this would put us into March, and hardy releases in april. we want testers and the docs need to be up to date [16:56] we could of course have updates point somewhere else, but it is a concern [16:56] generally [16:57] jdstrand: what about putting it in bzr for the time? === juliux_ is now known as juliux [16:57] * jdstrand thinks he didn't phrase any of that particularly well, but hopes his point got across anyway [16:57] nijaba: That's an option. [16:57] nijaba: I have no problem with that, but prospective users/testers will need to be able to easily find it [16:58] how is Jeos going to be documented long term? [16:58] improving that tuto? [16:59] is the documentation going to always be in the wiki or is something planned for the docbook docs? [16:59] nijaba: can the wiki page that points to the tutorial have an errata section (or something)? [16:59] nijaba: at least a pointer to it? [16:59] sommer: sure, I don't think that would be a problem [16:59] sommer: I don't think we talked about it, really. [16:59] jdstrand: That sounds sensible. [16:59] gotcha, I'm not even sure where it would fit, but just wondering [17:00] nijaba: I'd also like to point out that I am all for getting the information out there-- just want to make sure our testing doesn't suffer [17:00] so I'll propose the editor that we have a redirection + an errata section there. [17:00] (and testers ;) [17:01] jdstrand: That was one of my concerns as well. Replacing the wiki page with a link to linuxtoday and errata and then put the one for hardy in bzr for 90 days? [17:01] Is that what we're doing? [17:01] soren: is the future of JeOS, ubuntu-vm-builder, or will we still maintain a separate iso? [17:01] soren: yes [17:01] Still a separate ISO, I would think [17:02] [AGREED] Replace the Jeos tutorial wiki page with a link to linuxtoday and errata and then put the one for hardy in bzr for 90 days? [17:02] AGREED received: Replace the Jeos tutorial wiki page with a link to linuxtoday and errata and then put the one for hardy in bzr for 90 days? [17:02] soren: I think that sounds reasonable [17:02] jdstrand: It has to be reasonable. I told MootBot we agreed on it. [17:02] sommer: could you create the place holder in bzr? I'll update the wiki in due time [17:02] soren: haha-- you just typed faster than I [17:03] * jdstrand is trying to type more carefully after all [17:03] nijaba: sure [17:03] Ok, Last item: [17:03] [TOPIC] Agree on next meeting date and time. [17:03] New Topic: Agree on next meeting date and time. [17:03] thanks... my bzr skills are still not perfect and I don't even know if I have the right to do the add. [17:03] I intend to at least pretend to not be working next week. [17:04] nijaba: Everyone can create branches for every project on Launchpad. [17:04] I'll be there until Wednesday.... then off to kenya for 12 days (until the 6th) [17:04] ^^ I think that may be a better approach [17:04] I also think January 1st is going to be difficult. [17:05] nijaba: a seperate bzr branch for the article I mean [17:05] sommer: right [17:05] this I know how to do [17:05] So next meeting on January 8th? That's quite a while, but then again, not much is going to happen in between. [17:06] soren: I don't think that we have much choice... [17:06] soren: sounds good to me [17:06] Cool. [17:06] soren: me too [17:06] [AGREED] Next meeting January 8th, same time same channel. [17:06] AGREED received: Next meeting January 8th, same time same channel. [17:06] Any other business? [17:06] Going once... [17:07] twice.... [17:07] thrice! Meeting adjourned [17:07] #endmeeting [17:07] Meeting finished at 17:07. [17:07] cool thanks all [17:07] Have a good one, everyone... Adam: party on... [17:07] heh... party! [17:07] thanks soren! === markey is now known as Mamarok === \sh_away is now known as \sh === \sh is now known as \sh_away [20:01] hi all [20:01] hi [20:01] * slangasek waves [20:01] mjg59,Keybuk: ping [20:01] I think Keybuk is without network until tomorrow [20:02] hi [20:02] hey evand, slangasek [20:02] lamont: ping? [20:03] Hi [20:03] sabdfl: ack [20:03] * keescook waves too [20:04] * somerville32 waves as well. [20:04] #startmeeting [20:04] Meeting started at 20:04. The chair is mdz. [20:04] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [20:05] [TOPIC] ubuntu-core-dev application by Steve Langasek [20:05] New Topic: ubuntu-core-dev application by Steve Langasek [20:06] =============================================== [20:06] [LINK] https://lists.ubuntu.com/archives/motu-council/2007-December/000615.html [20:06] LINK received: https://lists.ubuntu.com/archives/motu-council/2007-December/000615.html [20:06] +1! [20:06] * mdz glares at sabdfl [20:06] (oops, sorry, will try to lean on my mouse in a different channel) [20:07] slangasek: I thought you were providing a convenient visual separator for the meeting log [20:07] slangasek: it was a good topic separator. ;) [20:07] i thought it was a reflection of the looooong pause [20:07] till i stated the obvious ;-) [20:07] [link] https://wiki.ubuntu.com/SteveLangasek [20:07] LINK received: https://wiki.ubuntu.com/SteveLangasek [20:08] * sabdfl will curb enthusiasm in favour of a modulated approach before others, too, state the obvious [20:08] sabdfl: given that mjg59 and I both know slangasek reasonably well from Debian, perhaps you should lead the discussion :-) [20:09] slangasek: what are your thoughts on keybuk's proposal to merge main and universe? [20:10] sabdfl: I share the concerns Martin Pitt raised about the difficulty in keeping control of build-dependencies if there's no longer a separation at the apt level preventing wrong packages pulled in on the buildds [20:11] agreed, and there are also social consequences if we make build/install dependencies mean more than just exactly what they say [20:11] and I think the concerns you just raised is also valid, though it wasn't one that had occurred to me [20:11] s/concerns/concern/ [20:12] could you comment further on the difference between -core-dev and -motu? [20:12] I want to find a way to make it work, but I'm a bit discouraged at all the holes we'd need to patch [20:13] there's definitely a nice element to having the people who care about a set of packages, say who gets to upload them [20:14] hmm, I think the separation between -core-dev and -motu is a valuable one for a number of reasons. Historically, Debian has only had one level of contributor, full DDs, which gave upload rights to everything; this had the effect of setting a very high bar for any contributions. In comparison, MOTU is a useful way not of /excluding/ people from contributing to main, but of /including/ them as contributors to universe [20:15] interestingly, Debian has recently invented another level of contributor [20:15] what's that? [20:15] Debian Maintainer [20:16] [link] http://www.debian.org/vote/2007/vote_003 [20:16] LINK received: http://www.debian.org/vote/2007/vote_003 [20:16] so certainly, any plan that reorganizes the main/universe split should keep in mind the importance of privilege separation in allowing contributors to bootstrap their way into the community [20:17] slangasek: based on your experience in the process, do you have any thoughts about how we might improve either the process or the team structure itself? [20:17] neat [20:17] mdz: by "process" you mean the process of becoming MOTU/core-dev? [20:17] slangasek: specifically, yes, and the general process of getting involved in the project [20:18] working at Canonical, you've had a leg up on most folks who go through it because you have daily contact with a lot of other folks involved in the project, but I'm always interested in feedback about what it's like and how we can make things easier for those interested in contributing [20:19] right; getting involved came easily for me, not just because it's part of my job but also because IRC is a natural medium for me [20:20] so dropping into #ubuntu-motu and finding my way around was not hard at all [20:20] I don't know how it would be for someone trying to approach the project on an email-and-forums-only basis [20:20] I wonder if the pervasiveness of IRC in Ubuntu is limiting for those who are not used to it [20:21] I'm not sure how solvable that problem is - email is always more formal and higher latency than IRC [20:21] are there many big decisions that are taken exclusively through irc? [20:21] not that I've seen [20:21] there's no introductory document which says "lots happens on IRC, it's important to be there" [20:21] just "hey, there's an IRC server, check it out" [20:22] sabdfl: it's not so much that as that the day-to-day heartbeat happens there [20:22] how people know you're alive and can talk to you [20:22] the uds framework is still really good for folks working to a longer timescale [20:23] +1 from me, again :-) [20:23] but someone who turned up at UDS and then didn't follow IRC or -changes or such after that would be lost [20:23] mjg59: any questions for slangasek? [20:23] and for the record i'm really glad to see the debian maintainer proposal, looks like it will ease pressure on N-M and DAM [20:23] mdz, I find that I have to stress to people who comes to me looking to get involved with Ubuntu the importance of being on IRC is to getting involved [20:23] mdz: as far as process, another thing that was confusing to me initially was the "apply to MOTU" vs. "apply to core-dev directly" question, which seems to have been sorted out now since I first applied; that's good :) [20:23] slangasek: given your extensive Debian background, now that you've had a look from the other side, what do you think about our relationship with Debian? the good, the bad, the weird? [20:24] somerville32: maybe it's something we should add to UbuntuDevelopment [20:24] somerville32: a quick, practical guide to getting in touch with other Ubuntu developers [20:24] there's a Communication paragraph, but it's more or less a list of resources [20:25] slangasek: Do you feel the balance of MOTU (in terms of not putting people off by putting too many barriers in their way, but still wanting to keep the quality of universe high) is about right at the moment? [20:25]