[06:07] hi [10:00] Hey@all === dholbach_ is now known as dholbach === dreaded66 is now known as fyrfaktry [14:59] * skaet waves [15:00] jibel, brendand, pitti, bjf - do we have quorum for a meeting today? [15:00] Hi all [15:00] hggdh, ping [15:01] Hi [15:01] ~ô~ [15:02] coolio looks like a good start anyhow. [15:02] #startmeeting [15:02] Meeting started at 10:02. The chair is skaet. [15:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:02] SRU/LTS bi-weekly synch meeting. [15:02] . [15:02] Reminder, please follow the convention of using ".." on a separate line when you've finished typing. Also, If someone wants to comment on the last point, please "o/", so we know to wait. [15:02] [TOPIC] Release overview - skaet [15:02] . [15:02] New Topic: Release overview - skaet [15:02] 10.04.3 [15:02] -- targetting July 21st for release. [15:02] -- new kernel was been pushed to updates late last week. Thanks to all involved in getting this last set of bug fixes in during the freeze. [15:02] -- candidate images have been posted on the iso tracker. Help testing is welcome. Please contact jibel, cjwatson or skaet if showstoppers found during testing. [15:02] . [15:02] We've been running into some space issues on cdimage, and some of the old releases have now been moved off to old-images (thanks cjwatson!). There is supposed to be some more disk space added as well so hopefully we won't get so crunched again for a bit. [15:03] . [15:03] This meeting will be moving on the calendar to Tuesdays going forward. [15:03] questions? [15:03] .. [15:03] [TOPIC] Kernel SRU status - sconklin or bjf [15:03] New Topic: Kernel SRU status - sconklin or bjf [15:04] hum [15:04] I can partially fill in if needed [15:04] sconklin is working on it [15:04] this is kernel new prep week. We are tracking a number of regressions that have turned up after release of kernels last week. [15:04] .. [15:04] o/ [15:04] sconklin, any new regressions on the lucid kernel we need to worry about for the release? [15:05] go cjwatson [15:05] * skaet cjwatson followed protocol, ;) o/ after him [15:05] what's the status of the various peripheral lucid kernel items on http://people.canonical.com/~ubuntu-archive/pending-sru.html ? Do we need to worry about any of them not being in -updates for 10.04.3 this week? [15:05] possibly. I just became aware of it before the meeting and haven't even looked at it yet. Stand by for the link [15:05] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811508 [15:05] Ubuntu bug 811508 in linux (Ubuntu) "Upon updating kernel, lost ethernet networking." [Undecided,New] [15:06] (right now, if no action is taken, the default will be that none of those reach 10.04.3, and I want to check that that won't make anyone's world collapse) [15:07] * skaet looking up the bug [15:07] cjwatson: I don't know whether it will or not. Honestly, we don;t pay much attention to the backports due to lack of time [15:07] there's also linux-firmware [15:07] yeah, don't know about that either [15:07] ok, I'm going to assume nobody is bothered then [15:07] afaik, we have to way to test the firmware package anyway [15:07] if that's not true, let me know ASAP and get the bugs validated :-) [15:08] (at least regression-tested ...) [15:08] yep, I don't know what gets tested by QA, will ask [15:09] I do know that we have new backports kernels in the pipeline, and that should not affect the point release at all [15:10] currently QA only tests security regressions, LTP, and boot on arches (bare-metal, KVM, EC2) [15:10] hggdh: thanks [15:10] .. [15:10] sconklin, yeah that bug sounds like one to keep an eye on, esp. since it also has +3 people on it already. [15:11] we have at least two severe regressions in Natty that only appeared after release [15:11] let us know if root cause is figured out if its something we have to respin for, or if we can release note it. [15:12] o/ [15:12] re: Natty, ack. [15:12] brendand, go [15:12] ok, what's the deadline for respin notification? [15:12] sconklin - can i get bug #'s for those. want to check if it's anything we should/could have caught with our testing [15:12] ? [15:12] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810400 [15:12] Ubuntu bug 810400 in linux (Ubuntu) "Disks not recognized after upgrading to 2.6.38-10 " [Undecided,New] [15:13] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/809878 [15:13] Ubuntu bug 809878 in linux (Ubuntu) "Wireless network & graphics card stop working after upgrade to 2.6.38-10" [Undecided,New] [15:13] There may be more. I'm gathering now [15:13] sconklin, soonest at this point. I think we'll need to know by end of day today, if at all possible. [15:13] ack [15:14] any other questions? [15:14] [TOPIC] HW certification - brendand [15:14] New Topic: HW certification - brendand [15:14] == Hardware Certification SRU Report == [15:14] • Tested Natty kernel 2.6.38-10.46 which was released recently. Results: http://people.canonical.com/~hwcert/sru-testing/current/natty-proposed.html [15:14] • Tested Maverick kernel 2.6.35-30.54 released before Rally: http://people.canonical.com/~hwcert/sru-testing/wk25_2011/maverick-proposed.html [15:14] • Tested Lucid kernel for 10.04.3 (2.6.32-33.70): http://people.canonical.com/~hwcert/sru-testing/current/lucid-proposed.html [15:14] • Currently testing Maverick kernel 2.6.35-30.56: http://people.canonical.com/~hwcert/sru-testing/current/maverick-proposed.html [15:14] ... [15:15] brendand, what's the summary from your perspective for lucid? [15:15] skaet - it looks fine from our point of view. [15:15] \o [15:16] o/ [15:16] hggdh go [15:16] brendand: how about bug 806586 -- will it be done this week (just curiosity)? [15:16] Launchpad bug 806586 in linux-lts-backport-natty (Ubuntu) "linux-lts-backport-natty: 2.6.38-10.46~lucid1 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/806586 [15:17] i'm not sure if we should be testing that one [15:18] a normal update would only yield 2.6.32-33, right? [15:18] correct [15:18] you have to explicitly select it [15:19] no, we don't have the capacity to test backports as well [15:19] just the main kernel [15:19] can you please mark the task invalid so that we can release it? [15:19] .. [15:19] sure [15:19] cjwatson, go [15:19] there seems to be at least one failure on every model. I'm not sure I have an account for hwcert data to inspect the details, but is there a common factor there? [15:19] (sorry if this is a well-known thing) [15:19] * skaet wonders this too [15:20] cjwatson - fine question. there is a test flaw that's getting fixed. === beni is now known as Guest90100 [15:21] any other questions? [15:21] ok, thanks [15:21] [TOPIC] QA status - hggdh [15:21] New Topic: QA status - hggdh [15:22] well, I have just been doing the kernel QA, so no news (apart from what sconklin and brendand and I already discussed) [15:22] .. [15:22] oops [15:22] we are on track, as far as I can see [15:22] .. [15:23] [TOPIC] 10.04.3 testing status - jibel [15:23] New Topic: 10.04.3 testing status - jibel [15:23] * Smoke Tested Ubuntu alternate|desktop|server|dvd amd64|i386: OK [15:23] * English|Non-english: OK [15:23] * OEM: KO. Finally found the bug mentioned during last release meeting (bug 650703) [15:23] Launchpad bug 650703 in Genesi EfikaMX Support Project "oem-config-prepare works, but oem-config fails to start after reboot" [Critical,In progress] https://launchpad.net/bugs/650703 [15:24] Fix uploaded to -proposed and verified but waiting for a real image to definitely mark it verified [15:24] Verification of installer changes in -proposed ok. [15:24] .. [15:25] Thanks jibel. [15:25] Any concerns other than the ones mentioned so far for 10.04.3? [15:25] o/ [15:28] hggdh, go [15:28] this is not as much 10.04.3 (although also applies): it would be nice if HC could test backported kernels, it would vastly increase the number of different hardware we test on [15:28] .. [15:28] o/ [15:29] hggdh, will ask about it, and cost/tradeoff implications then. [15:29] go brendand. [15:30] the main reason for certification testing is to ensure our certificates still apply [15:31] catching bugs etc is a good thing but doesn't extend to us testing kernels that we are not 'assuring' under the remit of the certification [15:32] but are those systems not supposed to be certified to run natty and maverick kernels which is mostly what lts-backport kernels are? [15:33] bjf - sure, but we are testing that kernel when it goes out as a natty kernel then [15:33] so i guess what testing does apply between the two gets done [15:34] the difference is that they have been built with lts toolchain and are running with a lucid userspace [15:34] One particular thing that does not get tested is if there is a problem with the more recent kernels on the older userspace X [15:35] true, true. in the end it comes down to resources and priorities. [15:35] in an ideal world etc... [15:35] yep, I understand that. [15:36] cool [15:36] so what are your resources and priorities? how long does it take to test a lucid kernel on the certification HW? [15:37] bjf - a couple of days [15:38] you are currently testing lucid, maverick and natty, correct? [15:38] o/ [15:38] that's right [15:38] brendand, lets talk about this more a bit offline, and see if there's a chance we can use the slots when oneiric images are broken to increase the testing of the backports? [15:38] are you at max capacity with that? [15:38] skaet, we are not going to test backports. Right now we don't certify them [15:39] I understand that our certification testing is useful for Ubuntu, to check how things are going in terms of hardware issues [15:40] but in the end, we are here to certify hardware, and we have to use our resources to do it better and better everytime [15:40] writing new tests, improving our processes, etc [15:40] but we can't test stuff we just don't certify, just because it could be useful [15:41] ara, suggest we take this offline then [15:41] skaet, sure thing [15:42] [TOPIC] General SRU status - pitti [15:42] New Topic: General SRU status - pitti [15:42] * skaet not seeing pitti [15:42] or martins for that matter. [15:43] " good night everyone!" << about 10mins back [15:43] from -desktop [15:44] thanks vish [15:44] [TOPIC] OEM priorities - vanhoof [15:44] New Topic: OEM priorities - vanhoof [15:45] skaet: here [15:45] :) [15:45] skaet: we're pretty well sorted presently, we have a number of fixes we're looking forward to that have already been reviewed and ack'd for the next natty sru cycle [15:46] nothing hot presently for 10.10, or 10.04 [15:46] .. [15:46] thanks vanhoof [15:46] any questions? [15:46] [TOPIC] New business, last chance for general questions? - all [15:46] New Topic: New business, last chance for general questions? - all [15:47] jibel pretty much got it all for 10.04.3 [15:48] thanks then everyone. [15:48] respin in progress for that ubiquity fix; if it doesn't validate, though, we'll just drop back to the validated ubiquity currently in -updates [15:48] in any event, there will be a respin to use only -updates [15:48] anything not in -updates at that point won't be in 10.04.3 [15:49] so if there's anything in http://people.canonical.com/~ubuntu-archive/pending-sru.html you care about, speak now or forever hold your peace [15:49] .. [15:49] :) [15:49] Thanks cjwatson [15:49] * skaet looks around for questions.... [15:49] ok, time to end it then [15:49] #endmeeting [15:49] Meeting finished at 10:49. [15:49] thank you skaet [15:50] Thanks skaet , good evening ! [15:50] bonne soiree, jibel [15:50] thanks vanhoof, jibel, hggdh, brendand, ara, bjf, sconklin, cjwatson, ara [15:50] thanks skaet === brendand_ is now known as brendand_n310 [17:02] hi! [17:02] o/ [17:03] hello [17:03] * sbeattie waves [17:03] #startmeeting [17:03] Meeting started at 12:03. The chair is jdstrand. [17:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:03] The meeting agenda can be found at: [17:03] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [17:03] LINK received: https://wiki.ubuntu.com/SecurityTeam/Meeting [17:04] [TOPIC] Review of any previous action items [17:04] New Topic: Review of any previous action items [17:04] [ACTION] jjohansen to give jdstrand updated apparmor for testing [17:04] ACTION received: jjohansen to give jdstrand updated apparmor for testing [17:04] jdstrand: ugh, sorry debugging the weekend revisions, I'll dump it on you in a little bit [17:05] jjohansen: cool, thanks. I still have a bit to work on before I'll need them. hopefully tomorrow or so is when I can dive in on them [17:06] [TOPIC] Weekly stand-up report [17:06] New Topic: Weekly stand-up report [17:06] I'll go first [17:06] last week I completed security-o-community work items [17:07] I started on dbus/apparmor work items and will continue to work on that this week [17:07] this week I am in the happy place [17:07] I am preparing a ufw upload for non-network-manager work items/bug fixes [17:07] and (of course), I have another manager training class [17:08] that is it from me. kees is out today, so, mdeslaur, you're up [17:08] I need to test the logrotate update I have [17:08] and will be going down the list [17:08] that's about it! [17:08] sbeattie: you're next [17:09] I'm on community this week [17:09] I have two embargoed issues that are due to come out this week. [17:10] I'm also taking a day of holiday on wednesday [17:10] I need to catch up on a backlog of apparmor issues. [17:10] Oh, I'm also recovering a bit from upgrading my laptop over the weekend to oneiric. [17:10] I think that's it for me. [17:10] micahg: you're up. [17:11] so, chromium is due for their 6 week major version update [17:11] I'm working on webkit this week [17:11] that's it for me [17:12] cool [17:13] [TOPIC] Highlighted packages [17:13] New Topic: Highlighted packages [17:13] one of my work items was to identify and report on community supported packages that would be a good place for people to contribute [17:14] so, each week I'll be reporting on this [17:14] as such... [17:14] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security on Freenode. The highlighted packages for this week are: [17:14] http://people.canonical.com/~ubuntu-security/cve/pkg/textpattern.html [17:14] LINK received: http://people.canonical.com/~ubuntu-security/cve/pkg/textpattern.html [17:14] http://people.canonical.com/~ubuntu-security/cve/pkg/ayttm.html [17:14] LINK received: http://people.canonical.com/~ubuntu-security/cve/pkg/ayttm.html [17:14] http://people.canonical.com/~ubuntu-security/cve/pkg/dhcpcd5.html [17:14] LINK received: http://people.canonical.com/~ubuntu-security/cve/pkg/dhcpcd5.html [17:14] http://people.canonical.com/~ubuntu-security/cve/pkg/freebsd-sendpr.html [17:14] LINK received: http://people.canonical.com/~ubuntu-security/cve/pkg/freebsd-sendpr.html [17:14] http://people.canonical.com/~ubuntu-security/cve/pkg/xmlsec1.html [17:14] LINK received: http://people.canonical.com/~ubuntu-security/cve/pkg/xmlsec1.html [17:14] [TOPIC] Miscellaneous and Questions [17:14] New Topic: Miscellaneous and Questions [17:15] Does anyone have any other questions or items to discuss? [17:15] jdstrand: do you want to give the link in the wiki where the weekly set lives? [17:15] sure [17:16] jdstrand: and thanks for working on that, it's a nice idea. [17:16] the https://wiki.ubuntu.com/SecurityTeam/HighlightedPackages is updated weekly [17:16] o/ [17:16] our GettingInvolved page includes this page [17:16] and dholbach will be incorporating that into his pages/community work [17:16] micahg: go ahead [17:17] there was a question over the weekend about sun java updates in hardy, it's in multiverse, I was wondering if the team is willing to sponsor updates with a server leaning for hardy still even in multiverse [17:18] .. [17:18] micahg: we (the security team) will not be providing updates. sun java is in partner now, and iamfuzz is the person who is in charge of updating this, so would be the best person to ask [17:19] that said, we would be happy to sponsor updated packages [17:20] jdstrand: k, thanks [17:20] any other questions? [17:24] ok, thanks everyone! [17:24] #endmeeting [17:24] Meeting finished at 12:24. [17:24] jdstrand: thanks! [17:24] sure thing! :) [17:24] thanks jdstrand === TheDaniel0108 is now known as Daniel0108 [19:01] Made it, even though they closed the venue. Did the meeting already start? [19:01] nope [19:02] … and actually, I did remind a DMB member about the meeting, does this give extra points? ;) [19:02] Heh. No, but it increases the chances that we *can* have the meeting. [19:02] oh hello [19:02] He is over here at debconf, we started talking a few hours ago, and he said "Oh, there is a meeting tonight?" :) [19:03] Laney, bdrung: ping [19:03] cody, actually [19:03] o/ [19:04] I like the aspect of putting faces to names in such conferences. :) [19:04] so, that's persia, maco, bdrung, geser and I. Looks like we have quorum ;) [19:04] stgraber: I would hope cody tries to come on soonish [19:05] Rhonda: look at my launchpad account, there is a small picture [19:06] i havent sent out the results of the last meeting. i think everyone's voted on that last application now, so: are we sticking with the tabulation procedures persia wrote up on the mailing list in evaluating that one? [19:06] cody will be online any moment. :) [19:06] He is sitting infront of me right now. [19:06] maco, The last meeting consisted of Laney and I being depressed that nobody else showed up. [19:07] Oh, the last actual meeting. Nevermind :) [19:07] the last one that wasnt on a "yay its a holiday i dont have to go to work and get to sleep in!" day ;) [19:09] cody-somerville: say hi :) [19:09] cody-somerville: hello goodbye hello [19:09] Hello :) [19:11] Have we started yet? [19:11] cody-somerville, Not effectively. [19:11] Could we start? Who is chair? [19:12] * cody-somerville only has like 40 minutes of battery. [19:12] I can chair [19:12] #startmeeting [19:12] Meeting started at 14:12. The chair is cody-somerville. [19:12] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [19:13] [topic] Rollcall [19:13] New Topic: Rollcall [19:13] o/ === beni is now known as Guest27522 [19:14] bdrung, Laney, geser, stgraber: ping [19:14] o/ [19:14] * stgraber waves [19:14] o/ [19:14] \o [19:15] Laney looks away so we [19:15] 'll begin. [19:15] [topic] Administrative Matters - Temporary resolution: Endorse Emmet's voting summary in the interim pending TB feedback [19:15] New Topic: Administrative Matters - Temporary resolution: Endorse Emmet's voting summary in the interim pending TB feedback [19:15] * persia auto-recuses [19:15] Emmet's summary matches my recollection of the agreement reached by members of the board during our first term. [19:16] can you post the link to his mail? [19:16] [LINK] https://lists.ubuntu.com/mailman/private/developer-membership-board/2011-July/000529.html [19:16] LINK received: https://lists.ubuntu.com/mailman/private/developer-membership-board/2011-July/000529.html [19:17] Since there was some confusion about our voting procedure and the original agreement was never officially documented, Emmet is moving to have the current board endorse the voting summary as written in his e-mail pending any feedback from the TB regarding their current review of the operation of the board. [19:18] https://lists.ubuntu.com/archives/technical-board/2011-July/000956.html is a bit easier to get to for most folk [19:19] I'd like to call the vote. If the board votes in the positive, we'll move forward with meeting. If the board votes against, I'll call the meeting to a close until we can agree on our voting procedure. [19:20] sounds good [19:20] yes [19:20] And I'm *not* moving that the current board approve that: if people want something else, that's fine. I just don't want there to be confusion about the current system. [19:20] one question [19:21] if all 7 members are present and 4 vote +1 and 3 vote -1 that would result in a +1 and a deferral [19:21] According to the procedure set previously, yes. [19:22] [vote] Agree that our current voting procedure is as described by Emmet via e-mail (ref: https://lists.ubuntu.com/archives/technical-board/2011-July/000956.html) [19:22] if only the four members are present that voted +1, that would result in +4 and the application approved without question the missing members, right? [19:22] Please vote on: Agree that our current voting procedure is as described by Emmet via e-mail (ref: https://lists.ubuntu.com/archives/technical-board/2011-July/000956.html). [19:22] Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot [19:22] E.g. /msg MootBot +1 #ubuntu-meeting [19:22] geser, Unless they already voted by e-mail [19:22] +1 [19:22] +1 received from cody-somerville. 1 for, 0 against. 0 have abstained. Count is now 1 [19:22] +1 [19:22] +1 received from bdrung. 2 for, 0 against. 0 have abstained. Count is now 2 [19:22] geser: Yes, although it is expected that any non-attendees would object by mail prior to the interview if they had objections and didn't expect to attend. [19:23] +1 [19:23] +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3 [19:23] If DMB members aren't reviewing applications prior to the interviews, we're probably doing it wrong. [19:23] * maco is re-reading [19:24] ( [19:24] (What does E mean btw in the numbering of the applicants?) [19:24] oh, e-mail [19:24] yes [19:24] +1 [19:24] +1 received from maco. 4 for, 0 against. 0 have abstained. Count is now 4 [19:26] +1 even if I would prefer to have a voting system which doesn't depend on how many members are at a meeting (the case I mentioned above is constructed and unlikely to happen) [19:26] +1 received from geser. 5 for, 0 against. 0 have abstained. Count is now 5 [19:27] #endvote [19:27] [endvote] [19:27] Final result is 5 for, 0 against. 0 abstained. Total: 5 [19:27] geser: How does this system depend on how many people show up? [19:27] It certainly wasn't intended to do so, and if it does, then it needs to be changed. [19:27] [AGREED] Current DMB voting procedure is as described at https://lists.ubuntu.com/archives/technical-board/2011-July/000956.html [19:27] AGREED received: Current DMB voting procedure is as described at https://lists.ubuntu.com/archives/technical-board/2011-July/000956.html [19:29] [TOPIC] Ubuntu Contributing Developer Applications - Juan Negron [19:29] New Topic: Ubuntu Contributing Developer Applications - Juan Negron [19:29] [link] https://wiki.ubuntu.com/JuanNegron/UbuntuContributingDeveloper [19:29] LINK received: https://wiki.ubuntu.com/JuanNegron/UbuntuContributingDeveloper [19:30] negronjl, Are you here? [19:30] Hrm? I'm still concerned about the statement that the voting procedure depends on meeting attendance. [19:30] Can we resolve that first? [19:31] Can we take it to the ml? I'm running out of battery. [19:31] Didn't we already process Juan Negron and Marc Cluet at the last meeting? [19:32] I'm happy to move it to the ML. That way I've more time to word it properly (and also notice any errors in my thinking). [19:32] Marc went to the mailing list [19:32] I'm here cody-somerville [19:33] OK. I'll just say that if results of the system do depend on meeting attendance, I'm against that system. === ejat- is now known as ejat [19:33] negronjl, Can you introduce yourself and your contributions to Ubuntu? [19:34] persia: it might only happen in border-cases, but those are that one cause the problems about how to interpret the voting [19:34] geser: i agree that non attending dmb member are a problem in the current voting system. [19:34] Hi all. My name is Juan Negron. I currently work for Canonical with the Systems Integrations Group. I am currently contributing to Ensemble (lp:ensemble), Principia (lp:principia), Orchestra (lp:orchestra) and Orchestra Modules (lp:orchestra-modules). [19:36] negronjl, So Launchpad says your first sponsored upload to Ubuntu was on June 8th 2011, is that correct? [19:36] negronjl: when did you began packaging? [19:37] cody-somerville: Sounds about right. It should be facter-plugins or orchestra ( and modules ) [19:37] bdrung: I started packaging a few years back but nothing that has been uploaded....that I started when I started in Canonical in Dec. [19:38] negronjl, And you created your application for UCD on June 13th, 2011 - right? [19:38] ...bdrun: Dec. 2010 [19:39] negronjl, When did you join Canonical btw? I don't think we've had a pleasure of meeting before. [19:39] cody-somerville: not sure of the dates...I've been working on packages for the above mentioned projects for a while so, they could have been ready before but uploaded then....the dates sound about right though [19:39] cody-somerville: I started on Dec. 2010 [19:39] cody-somerville: Worked for zaid_h and now kirkland [19:39] negronjl, Could you describe what you believe to be the relationship between the orchestra project and the Ubuntu project? [19:40] negronjl, What sort of contributions did you make to Ubuntu before starting work on ensemble? [19:40] persia: Orchestra is the mechanism to deploy Ubuntu server onto bare metal...Using cobbler, pxe booting, etc. [19:41] cody-somerville: Orchestra and Orchestra-modules. In the 1.x branch, I did facter-plugins ( facter-customfacts-plugins ) and all of the puppet recipes as well as some of the integration work with lynxman [19:41] negronjl, and before that? [19:42] negronjl, So, do you believe Orchestra and Ubuntu to be one project, or separate-but-parallel projects? [19:43] Dec. ( when I was hired ). I was working with lynxman in the development of the toolchain that will later be integrated in Orchestra ( the original name was sitoolchain ). The toolchain was based on puppet and mcollective with a log of "glue" code to "orchestrate" deployment in EC2, UEC and OpenStack [19:44] persia: I see Orchestra as a deployment and orchestration mechanism to deploy Ubuntu Server. Orchestra is the tool that gets Ubuntu Server deployed in bare metal quickly and effortlessly so the admins can go about their business. [19:44] as a side note. Orchestra will work with Ensemble ( that work is being done right now ) [19:45] I understand that. Do you believe them to be part of the same project, or do you see Orchestra as a project to deploy the output of the Ubuntu project? [19:45] persia: separate projects with a very parallel development and deployment cycle ( after all, Orchestra is mainly managed by the server/platform team ) [19:46] negronjl: is Orchestra Canonical funded and do you expect to continue packaging it the next couple months? [19:47] geser: Orchestra as a project I believe it is but, I have to be clear about this.... .It is an open source project. The main focus is to get it out right now and the people most interested in it's development at the moment happen to work for Canonical however, I ( and others ) are going to diff. conferences and promoting Orchestra ( and Ensemble ) to gain community support and development. [19:48] negronjl, So, if Orchestra is separate from Ubuntu, would it be correct to say that your contributions to Ubuntu consist of delivery of orchestra software to Ubuntu (orchestra, orchestra-modules), and patch contributions for facter-plugins and dotdee? [19:48] geser: As an example, I did a presentation at Structure/2011 where a Ben Saller ( Ensemble ) and myself did a talk about Orchestra and Ensemble [19:49] persia: ... and principia but, more or less, you can distill my package and bug contributions down to that level...yes. [19:49] Any other questions? [19:49] * persia has one, but needs another minute [19:49] geser: I am also scheduled to talk at CouchDB where we will be (again) talking about Orchestra and Ensemble as orchestrations for Ubuntu Server [19:50] as another side note: With or without Canonical, I intend to continue my contributions to Ensemble, Principia, Orchestra, orchestra-modules and facter-plugins just the same [19:51] negronjl, How do you feel about your experience of social integration with the Ubuntu Development community? [19:51] What do you think would be the next step for you? PPU for orchestra-related packages? [19:52] persia: re: social integration ... I'm getting there .. there's a lot of ground to cover and could be quite overwhelming if taken all at once.... [19:52] * cody-somerville has 19 minutes of battery left. [19:52] i am ready to vote [19:52] persia: re: next step...PPU for the packages belonging to the projects I work with ... that would be nice [19:53] * persia is done with questions [19:53] I'm ready to vote too [19:53] [vote] Ubuntu Contributing Developer Applications - Juan Negron [19:53] Please vote on: Ubuntu Contributing Developer Applications - Juan Negron. [19:53]