=== Simira [~Simira@179.80-202-212.nextgentel.com] has joined #ubuntu-meeting === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-meeting === jiyuu0 [~jiyuu0@219.95.213.246] has joined #ubuntu-meeting === robitaille [~robitaill@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting === dato [~adeodato@84-120-77-228.onocable.ono.com] has joined #ubuntu-meeting === JaneW [~JaneW@dumbledore.hbd.com] has joined #ubuntu-meeting === dieman [~dieman@3.14159265358979323846264338327950288419716939937510582097.org] has joined #ubuntu-meeting === mvo [~egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting === pitti [~pitti@box79162.elkhouse.de] has joined #ubuntu-meeting === pitti [~pitti@box79162.elkhouse.de] has left #ubuntu-meeting [] === mbeattie [~mbeattie@ool-4355f1f7.dyn.optonline.net] has joined #ubuntu-meeting === ..[topic/#ubuntu-meeting:Seveas] : /topicth the command "date --utc" [11:35] ah narf === ..[topic/#ubuntu-meeting:Seveas] : Tue 31 May 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda|| Tue 6 June May 22:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || Find out UTC time with the command "date --utc" === ..[topic/#ubuntu-meeting:Kamion] : Tue 31 May 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda|| Tue 6 June 22:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || Find out UTC time with the command "date --utc" === JaneW [~JaneW@wbs-146-163-161.telkomadsl.co.za] has joined #ubuntu-meeting === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-meeting === pitti [~pitti@box79162.elkhouse.de] has joined #ubuntu-meeting === pitti [~pitti@box79162.elkhouse.de] has left #ubuntu-meeting [] === ozamosi [~ozamosi@80.252.171.200] has joined #ubuntu-meeting === Mithrandir [~tfheen@vawad.err.no] has joined #ubuntu-meeting === amu [~amu@amu.developer.debian] has joined #ubuntu-meeting === jbailey [~jbailey@CPE000ded9d787c-CM014260028338.cpe.net.cable.rogers.com] has joined #ubuntu-meeting === dato [~adeodato@84-120-77-228.onocable.ono.com] has joined #ubuntu-meeting === mdz [~mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-meeting === ozamosi [~ozamosi@cust-adsl-80-252-171-200-dynamic.areteadsl.se] has joined #ubuntu-meeting === ubuntulog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Tue 31 May 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda|| Tue 6 June 22:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || Find out UTC time with the command "date --utc" === Topic (#ubuntu-meeting): set by Kamion at Tue May 31 12:29:15 2005 === Unfrgiven [~ankur@202.76.176.94] has joined #ubuntu-meeting === ubuntulog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-meeting === Topic for #ubuntu-meeting: Tue 31 May 20:00 UTC: Tech Board -- https://www.ubuntulinux.org/wiki/TechnicalBoardAgenda|| Tue 6 June 22:00 UTC Community Council -- http://wiki.ubuntu.com/CommunityCouncilAgenda || http://wiki.ubuntu.com/Calendar || This is NOT #ubuntu, nor #ubuntu-devel || Find out UTC time with the command "date --utc" === Topic (#ubuntu-meeting): set by Kamion at Tue May 31 12:29:15 2005 [10:00] (mdz/#ubuntu-meeting) welcome, everyone [10:00] (ogra/#ubuntu-meeting) hey := [10:00] (ogra/#ubuntu-meeting) :) [10:00] (Nafallo/#ubuntu-meeting) sabdfl: evening [10:00] (ajmitch/#ubuntu-meeting) hi [10:00] (ivoks/#ubuntu-meeting) evening [10:00] (dholbach/#ubuntu-meeting) hey [10:00] (fabbione/#ubuntu-meeting) evening [10:00] (zul/#ubuntu-meeting) evening sabdfl [10:00] (mdz/#ubuntu-meeting) MaintainerCandidates is stale; there are people at the top who were already processed [10:01] (mdz/#ubuntu-meeting) is " Daniel 'Daniel N' Neuenschwander" present? [10:01] how about AnteKaramatic? [10:01] here [10:01] evening all === diamond is currently attempting to move self to active list on that page. damn slow net conn -/ [10:02] hey ivoks := [10:02] ;) [10:02] ogra: ;) [10:02] ivoks: so you have been working with the MOTU team? [10:02] mdz: for couple of weeks, yes [10:02] mostly on cxx transition [10:02] apologies for not showing up the last time btw, lost net access for the last week -/ [10:02] ogra,dholbach: what is your assessment? [10:03] he did QUITE a lot of work on the c++ transition [10:03] mdz, seen my last mail to -devel ? [10:03] :=) [10:03] ogra: I doubt it [10:03] thumbs up from me [10:03] in your opinion, is he ready to make unreviewed uploads to universe? [10:04] he is unstoppable and works nice with the team, i'm happy with ivoks on our side [10:04] ok... if I can say something... [10:04] <\sh> ivoks++ ..hes great [10:04] ivoks: of course [10:04] i;m not planing to do unreviewd uploads right away.. [10:04] i'm more of a team player [10:04] and will allways want second oppinion on somethign [10:05] i know he doesnt feel safe yet, but his changes were good and you could see the learning curve, he works tight with \sh and herve, so it would be ok for me [10:05] same thing with packages [10:05] ivoks: well, that is the privilege we are discussing: if you are granted upload privileges, it is left to your discretion === jani [~pet@Home03207.cluj.astral.ro] has joined #ubuntu-meeting [10:05] hey jani [10:05] hey dholbach :), all [10:05] ivoks: so I should rather say, "ready to choose whether an upload requires review" [10:05] mdz: right [10:05] does anyone else have anything to say regarding ivoks? [10:05] \sh, ?? [10:06] <\sh> yeah [10:06] doko? [10:06] no, apart from that he'd be a welcome addition to the team [10:06] herve is missing sadly... [10:06] i highly appreciate this sense of cautiousness [10:06] <\sh> what i saw from ivoks, it was good enough (for me)...and when something wasn't ok, he fixed it accordingly [10:06] ivoks: looks like you've been working with software for some time === camilotelles [~Camilo@200.128.80.254] has joined #ubuntu-meeting === seb128 [~seb128@ANancy-151-1-12-101.w83-194.abo.wanadoo.fr] has joined #ubuntu-meeting [10:07] mdz: I'm happy with ivoks as motu [10:07] nonetheless, software from Universe goes out to thousands of computers, so it requires a high level of responsibility [10:07] sabdfl: well, my job requiers me to to that, so one learns something on the way [10:07] sabdfl: i know, i'm ready for it [10:08] responsibility, that is [10:08] erk === sabdfl was reading the wrong wiki page [10:08] <\sh> ivoks grew in the last couple of weeks (imho) [10:08] sabdfl, ivoks is ver cautious about his work and always asks for a second opinion [10:08] you're not actually 16, are you [10:08] sabdfl: nope, 23 [10:08] SPETHIAL [10:08] 'k [10:08] i'll shut up then === KaiL_ [KaiL@p548F5DA7.dip.t-dialin.net] has joined #ubuntu-meeting [10:08] was trying to find a nice way to put it [10:08] :) [10:08] ivoks == AnteKaramatic [10:08] yes [10:09] elmo, very :) [10:09] Keybuk,sabdfl: thumbs up/down? [10:09] ivoks: given your clustering experience, have you come across the SSI project? [10:09] which clustering solution would you think best for ubuntu? [10:09] motu seem keen, so I'll give him an up [10:09] sabdfl: no, i played only with mosix [10:09] and he seems to have humility [10:10] +1 for ivoks from me === dieman mostly uses condor [10:10] .msg Keybuk Like you'd know it if you ever saw it... [10:10] +1 from me as well [10:10] sabdfl: well, this is load balancing cluster, wich works good with sarge, don't see why it wouldn't do same with ubuntu [10:10] ivoks: congratulations [10:10] HOORAYY [10:10] mosix is nice [10:10] +1 [10:10] :) [10:10] <\sh> yes [10:10] ivoks: grats [10:10] congrats ivoks [10:10] welcome, ivoks [10:10] ok, it's like draming :) [10:10] <\sh> ivoks: welcome :) and congrats :) [10:10] diamond: what is your name? [10:10] thanks all [10:10] WOW ivoks! ROCK! [10:10] mdz: Stephen Shirley# [10:10] yeah [10:11] http://www.ubuntulinux.org/wiki/StephenShirley [10:11] mdz: see apology above about not turning up last time (if you haven't seen it) btw === diamond nods [10:11] ivoks: good work, welcome :) [10:11] ajmitch: thanks [10:11] ivoks: congrats [10:11] diamond: no worries [10:11] surak: thanks [10:11] thank you all [10:11] last week's meeting was announced on short notice and few people were able to make it, it seems [10:11] ivoks: congrats :-) [10:12] feedback from the MOTU team on diamond's work thus far? [10:12] Stephen "Captain Pedantic Pants" Shirley did great work before the hoary release, i remember some non-trivial cases he fixed [10:12] Nafallo: :) tnx [10:12] but you've been busy in the last time, diamond, right? [10:12] yep.. he was quite active in hoary [10:12] dholbach: aye [10:12] and did a good work === KaiL_ [KaiL@p548F5DA7.dip.t-dialin.net] has left #ubuntu-meeting ["Glaubt] [10:12] far more active than some of us other MOTUs :) [10:13] dholbach: i do sys admin for the university computer club, it's been chewing up a lot of my time recently with irc setup, i'd like to merge some of that work into ubuntu (and upstream) if i can [10:13] diamond: your packages are quite diverse, any particular focus you'd like to bring to ubuntu? === JaneW [~JaneW@wbs-146-163-161.telkomadsl.co.za] has joined #ubuntu-meeting [10:14] sabdfl: ah, yeah, those packages are mainly fixed because they were on the list, and i could figure out the isse. my focus is stuff like flexibile authenticaion. the above irc stuff is mainly a pam patch to ircd-hybrid that was written by one of the guys in the comp soc, i'd made a debian package that we're using, i'd like to get it more widespread. that sort of thing [10:14] i'd like to see kerberos auth available for everything, [10:15] ssl enabled (or at least enabable) for all services, things like that [10:15] cool, thanks [10:15] sounds good to me [10:15] krb5++ [10:15] Keybuk: +/- ? [10:16] hi, sorry I am late - connection problems [10:16] i'm like ivoks in that i don't intend to upload anything without review for some time [10:16] ogra, dholbach? + or - from you? [10:16] i've been doing development for a while, but i'm fairly new to debian packaging [10:16] + [10:16] i'm absolutely happy with him [10:16] ok + from me [10:17] sorry got dragged away for a sec.) [10:17] <\sh> g'evening JaneW [10:17] jupi [10:18] + from me, on the basis that he'll seek review and guidance from MOTU where appropriate [10:18] diamond: congratulations [10:18] mdz: thank you -) [10:18] is there anyone else here who is seeking approval for upload/maintainership? === dholbach is sooo happy :) [10:18] yay === diamond does a happy dance that no-one ever needs to see. *cough* [10:18] heh === dholbach hugs diamond and ivoks === pitti likes to see the MOTUs grow :-) [10:19] congrats ivoks and diamond [10:19] <\sh> diamond: welcome on board :) and congrats :) === ogra higs the three [10:19] hugs even [10:19] is there a complete list of the MOTU team anywhere? [10:19] sabdfl: I was just wondering the same [10:19] http:///wiki.ubuntu.com/MOTU [10:19] <\sh> wiki/MOTU ? [10:19] oops, http://wiki.ubuntu.com/MOTU [10:19] dholbach: :) [10:20] ivoks, diamond please add yourself there ;) [10:20] is that 20 members now, then? [10:20] yep [10:20] yes, mdz :) [10:20] excellent [10:20] will do :) [10:21] thanks to ogra, dholbach and the rest of the team for successfully recruiting and nurturing new arrivals [10:21] seed change proposals? [10:21] diamond: congrats [10:21] yeah, bigtime re: ogra and dholbach [10:21] sabdfl, serpentine for main please :) [10:21] http://www.ubuntulinux.org/wiki/SupportedSeedProposals [10:21] mdz: i completely enjoy it ... the team itself works just fine [10:22] seb128: is seahorse a reasonable thing to have in main? [10:22] hmm, did it stop breaking things ? [10:22] if it's experimental, we should wait [10:22] i heard about doubled entrys and the like [10:23] mdz: I've not really used it, I can have a look but no opinion on it atm [10:23] that's a really out of date list === St0n3-C0l [~stone@St0n3-c0l.user] has joined #ubuntu-meeting [10:23] yes, we haven't looked at it in quite some time === danko123456 [~dbernar1@wnpgmb02dc1-186-160.dynamic.mts.net] has joined #ubuntu-meeting [10:23] due to the release === Vince [~vincent@abo-185-85-69.ang.modulonet.fr] has joined #ubuntu-meeting [10:23] it was last reviewed in mataro, wasn't it? [10:23] should we officially approve mono for main, or have we already done that? :) [10:24] there are some no-brainers on here [10:24] we should have a better system for package proposals then the wiki... MOTU is just disussing that [10:24] consensus on mono has always been that we should let germinate handle it [10:24] and seed the apps we want [10:24] Keybuk: I reviewed it, fine for me [10:24] yeah, that makes sense for me [10:24] so are there mono apps we should put in main? [10:24] is tseng around? [10:24] <\sh> ogra: we forgot to put this on the agenda ;) === pitti anticipates the cry for eagle [10:24] beagle, even [10:24] mdz, Kamion has the list since last week [10:25] there's nothing else on that list that immediately leaps to _my_ attention; so I guess we should ask for proposers to step forward to advocate their app? [10:25] patch-36 [10:25] add beagle, monodevelop, tomboy to supported (ogra) [10:25] so they're already done [10:25] and we just need to resync the archive === mgalvin [~mgalvin@host-66-202-95-170.spr.choiceone.net] has joined #ubuntu-meeting [10:25] yay for tomboy [10:25] sabdfl: you installed it yet? :p [10:25] latex-ucs seems like a no-brainer, given pitti's approval [10:25] I still think latex-ucs would be a nice addition, but maybe there are not so many latex users in Ubuntu... [10:25] sabdfl, wiki links in notes ? ;) [10:26] waiting for it in main :-) [10:26] sasl2-bin is a no-brainer, given that its source is already in main [10:26] mdz: there is not much potential for breakage, also security-wise === mez_ [~mez@82-36-228-130.cable.ubr01.perr.blueyonder.co.uk] has joined #ubuntu-meeting [10:26] pitti: i've got a fair number of latex users. [10:26] pitti: seconded. [10:26] I've never used latex-ucs, how is it different from latex? or is just the same with utf-8 .tex file support? [10:26] <\sh> mdz: much more important should be the applications using sasl2 ;) [10:26] mdz: so I can seed it? [10:26] mdz: rather than getting caught on the detail of the packages, maybe it's worth talking about the policy for supported? [10:27] for our initial releases it's been strictly what the full-time team felt comfortable supporting [10:27] sabdfl: I think that's sufficiently documented already, no? [10:27] http://www.ubuntulinux.org/wiki/SeedManagement [10:27] fdclock jumps out as a "why do we need yet another clock, let alone support it" to me [10:27] Keybuk: it can be thrown around? :-P [10:27] and vnc4server ... doesn't vino already cover that? [10:27] as the team grows, we should have the ability to put something in supported if we have sufficient commitment from the community that we think it will actually get supported [10:28] (though maybe that's more of a desktop worry than supported) [10:28] all proposals require review/approval from the core team regarding security and supportability [10:28] i don't think having someone just say "i'll do it" is sufficient [10:28] currently that's delegated to pitti, which has been working well so far [10:28] we need to have a strong feeling that it will happen [10:29] pitti: I already did [10:29] but i would be more open to persuasion if we had a list of names of people who are strongly active in the project who support any of those items [10:29] mdz: thanks [10:30] something can still be supported ad-hoc in universe, in the sense that updates can also be posted to universe packages post-release [10:30] sabdfl, the MOTU team still needs to grow for such things... trasitions eat our manpower.... [10:30] we should probably have a "so you think that package 'foo' should be in Ubuntu main?" how-to document [10:30] pitti: could you draft something like that? [10:31] the criteria for main should be that we can provide an absolute assurance of pitti-like security updates, without requiring the clone-pitti branch to have landed [10:31] pitti: include some guidelines about things that you look for in review, so that the proposer can consider those before even requesting review [10:31] mdz: yes, I can [10:31] pitti: great, thanks [10:31] well, my point is that we should have a plan to scale main beyond what pitti can handle [10:31] but not beyond the point where we are in any doubt of the quality we can deliver [10:32] sabdfl: right now the reviews didn't take so much of my time, it's the updates that do :-) [10:32] pitti: the updates are the most important bit [10:32] but that requires a working sec team for universe.... we still dont have it... [10:32] i don't see anything on the list that i would want to devote your time to for updates [10:32] sabdfl: right, that's why I don't really like software with a bad security history (which I'm evaluating for the decision) [10:32] but we should be willing to consider anything on the list if there is a team of people who will provide the update assurance for it [10:32] <\sh> ogra: and it will be more difficult when the server projects fires up for real life [10:33] ogra: well, we have the beginnings, but it needs to be developed much further [10:33] thom: do you know if NM's wpa support will use wpa-supplicant, or be native? [10:33] pitti: agreed - it shouldnt get in if it doesn't pass the review [10:33] ogra: there's a start on a security team for universe [10:33] at any rate, I've seen quite a number of requests for wpa-supplicant [10:33] the protocol seems to be gaining ground [10:33] but the start is there since quite some time, i dont see it evolving yet [10:33] pitti: please add wpa-supplicant to your queue for review; if you're happy with it, it should move into main [10:33] mdz: definitely, it's something that ideally should be done via network manager [10:34] mdz: added to my todo [10:34] is there any sense in an idea of having main-proposals accompanied by a spec, with appropriate people leading, seconding or expressing interest in it -- including plans for it being in main? [10:34] Keybuk: isn't that what's happening now? [10:34] Keybuk: great idea [10:35] JaneW: those proposals don't have specs [10:35] JaneW: this is very ad-hoc [10:35] sabdfl,Keybuk: that's going to be overkill in most cases [10:35] Kamion would need to check each one too, as one package could drag in half of universe through germinate [10:35] difficult to look at "foobarmatic" and contribute to the discussion unless you know what it is. who wants it, who will look at it, who will watch the upstream mailing list for security updates, etc [10:35] mdz: a spec can be just a single page saying why the program rocks [10:35] it doesn't have to be 2000 words on plans for it [10:36] Keybuk: ... and why it won't break much :-) [10:36] I like the idea, I just don't think we can require it for all cases [10:36] e.g., sasl2-bin [10:36] having a page like that gives us place to put a motivation, and document the process, such as whether or not it has been reviewed [10:36] mdz: happy for you to fasttrack things [10:36] mdz: we can always just rubberstamp obvious things [10:36] ok, agreed then [10:36] but where suggestions come in that aren't immediately YES to the TB [10:37] pitti: the proposed document should specify that proposals be accompanied by a written rationale [10:37] <\sh> mdz: the combination makes it...sasl2 is nice for postfix + cyrus imapd e.g. and postfix is in main and cyrus imapd is old (ubuntu version) [10:37] pitt is authoring the proposed specification for proposal specifications :-) === pitti phears recursivity [10:37] we definitely need a place to record rationale [10:38] there are things on SupportedSeedProposals that we can't put in main [10:38] but I don't want to just delete them [10:38] mdz: I think a small wiki page which has the rationale and the points I usually do for review would be fine [10:38] add a new section with "Can't be put in main" [10:38] ? [10:38] hi, sorry I'm late [10:38] Kamion: part timer [10:38] Keybuk: germinate> elmo does a post-hoc check on that when adding them to the archive, too [10:38] <\sh> mdz: so if i like to see an application in main, will it pull the "security deps" into main, too? [10:38] \sh: "security deps"? [10:39] .msg elmo slack-jawed hippy [10:39] Mithrandir: that's basically what I'm doing now === gustavor [~gustavo@32.104.18.243] has joined #ubuntu-meeting [10:39] <\sh> mdz: sasl2 is such a thing, postfix+imapd+sasl2 are belonging together for strong auth [10:39] elmo: you actually use scponly? [10:39] mdz: err, not really, no [10:39] that page is freakin ancient [10:40] elmo: please delete any of your stuff from there that is no longer interesting [10:40] I've saved my edits [10:40] I've seeded the obvious ones [10:40] if we spec-process it, we could replace that page with one on a moin wiki containing some magic to show all pages with SupportedSeedProposal in them ... and then split based on whether it's a draftspec, rejected, etc. [10:40] the rest of them will need rationales according to the process pitti is documenting [10:41] so let's move on with the agenda [10:41] jbailey: what's the rationale for this oo.o2 stuff? [10:41] we don't have the option of backing down on oo.o2 now; it's already part of desktop [10:41] mdz: Pulling the Java stuff in to main right now brings two compilers and 3 vms in. Now that toolchaintransition is mostly done, I can start cleaning it up. [10:41] the rationale is that it won't build with just main at the moment, and that means we don't get to try out and fix up new milestones [10:41] mdz: is there anything better than scponly? [10:41] we could do so priefly during breezy, surely? [10:42] mdz: But in the meantime, OOo2 needs it and the buildds cycle every 30 minutes not being able to pull in the build-deps. [10:42] doko's been asking to demote it temporarily to universe for a while now [10:42] The idea is to pull it out for now, get it all building and happy and move it back. [10:42] jbailey: any particular reason it pulls them in? [10:42] (in that why doesn't it just pull one?) [10:42] jbailey: err, no they don't [10:42] Keybuk: Because the packages we inherit from Debian are a bit inconsistant. [10:42] I told lamont to fail stuff that was cycling [10:42] elmo: you can use restricted ssh keys instead of scponly for a more flexible approach [10:42] elmo: Ah lovely. That's a change from when I looked before then. [10:43] it's ultimately going in main anyway? [10:43] Right. [10:43] so why not leave it there while it's fixed [10:43] diamond: err, not really - keys won't allow you to restrict an account to only scp-ing AFAIK [10:43] But without also bringing in jikes, sablevm, etc. [10:43] diamond: restricted ssh keys are more limited [10:43] it's not like breezy is otherwise unbroken right now === KabelKasper [~vloechte@i5387EC2F.versanet.de] has joined #ubuntu-meeting [10:43] diamond: and it'd also be tricky to prevent the user from scping in a new authorized_keys [10:43] Keybuk: the buildds can't violate layers [10:43] jbailey: if you want to disable the java stuff until it builds properly, that's fine [10:43] diamond: if you try to do that, you have to say "can scp only to this target" [10:43] but I'd rather it just got fixed [10:43] Keybuk: i.e. if main b-d's on stuff beneath main, it won't build, at all, ever [10:44] elmo: main can't b-d on stuff beneath it, that's how germinate works! :p [10:44] putting something in main implicitly drags in its b-ds [10:44] Keybuk: not entirely automatically [10:44] mdz: 'kay. It'll be a couple weeks before new OOo2's will build usefully. [10:44] Keybuk: germinate != katie [10:44] Keybuk: heh, in germinate's mind sure. but katie's an indepent kind of gal and has her own idea of what's in main === tseng|work [~ccc27a01@sls-eb20p9.dca2.superb.net] has joined #ubuntu-meeting [10:44] elmo, Kamion, mdz: ah, right. my bad [10:44] sorry was afk. [10:44] jbailey: can't we revert to the hoary state of affairs, to get it building? [10:45] would be nice if ssh did support it tho [10:45] tseng|work: never mind, it turned out that it had already been dealt with [10:45] ok, thanks. [10:45] mdz: I'll have to ping doko on that part of it, he's away and asked me to proxy the question. I thought OOo2 was in Universe for Hoary. [10:45] So didn't really care what all it pulled in. [10:45] jbailey: it was, but it was also building without the java stuff at one point, I thought [10:45] openoffice.org2 | 1.9.79.2-0ubuntu2 | hoary | source, i386, powerpc [10:46] I'll ask doko if that's possible. [10:46] it's in main for hoary [10:46] diamond: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282339 - but scp is dead, it'd have to be done in sftp [10:46] jbailey: what's involved in fixing the actual breakage? [10:46] Kamion: *nod* [10:46] mdz: Just going through and cleaning up deps/build-deps to use the prefered java apps. [10:46] elmo: oh, goodie. does it actually build, I wonder? [10:46] mdz: That was dep'ing on the C++ transition. [10:46] jbailey: why will that take weeks? [10:47] mdz: Mostly because I think you want EarlyUserspace first, so I'm aiming for that this week, and Java stuff next week. =) === KabelKasper [~vloechte@i5387EC2F.versanet.de] has left #ubuntu-meeting ["Kopete] [10:47] mdz: should do, we did do the full rebuild thing twice [10:47] jbailey: is there someone else capable of doing the work for oo.o2/java? [10:47] elmo: good point [10:47] i don't mind dropping oo.o2 from desktop for two weeks [10:47] mdz: wasabi is capable, but is busy since getting his new job. [10:48] sabdfl: what purpose does it serve? [10:48] mdz: Otherwise, it's just packaging and making sure that any errors that come up get fixed if something was depending on a particular vm quirk. [10:48] if it's an irritant in any way [10:48] the only problem it's causing currently is that oo.o2 won't build from source [10:49] jbailey: is oo.o2's breakage holding up the C++ transition or something? [10:49] isnt it the other way round? [10:49] c++ -> java -> ooo2? [10:49] it's pretty important that we get oo.o2 into a usable state early in the breezy cycle [10:49] we don't want to end up in the same situation we were in for Hoary [10:50] mdz: I don't think so. I think it was largely driven by not irritating the buildds. [10:50] if oo.o2 isn't blocking anything big, I'd prefer for it to stay put [10:50] the buildds can deal [10:50] jbailey: can you ping wasabi and see if he might be available to help us out on this? [10:51] jbailey: (on a bounty basis) [10:51] mdz: Will do. [10:51] mvo! [10:51] (err, -ECHAN) [10:51] ok, next agenda item was about ServerTeam [10:51] THPECIAL [10:51] I have already assigned it a priority, and also responded to infinity's direct inquiry on the subject [10:51] (elmo, not the server team) [10:51] sabdfl: You hate us, admit it ;)_ [10:52] it wasn't a tech board matter in the first place [10:52] i'm a desktop guy, what can i say [10:52] but anyway, it's dealt with [10:52] any other business before we adjourn? [10:52] expansion of this group? [10:52] mdz, seed serpentine to main please... ? [10:52] sabdfl: nominees? [10:52] mdz, thats AudioCDBurning..... [10:53] what about our breezy goals review? [10:53] send me nominations, i'll make nominations and we'll have a vote of the developers [10:53] to confirm [10:53] ogra: given that seb128 maintains it, seems like a no-brainer [10:53] pitti: I am just looking through them now === ogra watches pitti mutating to JaneW [10:54] hehehe === wasabi_ [~wasabi@207.55.180.100] has joined #ubuntu-meeting [10:54] one question: confirmation of TB members, would that be a vote of main-maintainers, or main-and-motu? [10:54] mdz, yep... just wanted to state i :) [10:54] it even [10:54] JaneW: *blink* :-) [10:54] some people are being better about giving regular updates than others [10:54] sabdfl: isn't it a vote of the existing TB (looking at the web page) ? [10:54] Keybuk: no [10:54] huh wha? [10:54] it's a vote of the developers [10:54] but when we decided that, we didn't have the MOTU [10:54] (Oxford) [10:55] confirming TB nominations is a weighty responsibility [10:55] confirmation of CC should clearly be all members [10:55] mdz: nominating them even more so :-) [10:55] mdz: wpa-supplicant is the plan, last i heard [10:56] i'd like to hear from the TB and the MOTU regarding the TB confirmation vote [10:56] pitti: was going to give you a gold star for your updates - but I may take it back now! [10:57] it seems logical to me that it should include MOTU [10:57] to me too [10:57] mdz++ [10:57] yes, i think so as well [10:57] though to date, I haven't really considered MOTU approvals in that light [10:58] pitti: it doesn't really help that your updates are 'can someone else do this?' [10:59] JaneW: that was intended to be a reminder for discussing the goals here === JaneW gives jbailey a gold star! === jbailey does a snoopy dance! [10:59] JaneW: do you have gold stars to give? [10:59] p/me applauds jbailey [10:59] pitti: is there a tech board issue to decide regarding the goals? [10:59] well done jbailey :) [10:59] Keybuk: only to those that please me [10:59] ok, let's take that to the CC [10:59] mdz: not really, it's more a request for reassign, but that can be done on the ML [10:59] is that a wrap? === JaneW tells everybody to look at jbailey's updates to his BreezyGoals [11:00] any other business before we adjourn? [11:00] mdz: security takes more time than expected, so I feel I should drop some assignments rather early than too late [11:00] mdz: if we had went through the goals page here I had mentioned it, but I'll ask on -devel [11:01] pitti: understood, please try to find candidates within the development team if you can [11:01] ask around if anyone is interested [11:01] <\sh> well, i don [11:01] looks like we're finished with tech board business [11:01] right on time, too [11:01] \sh are you volunteering again? ;) [11:01] meeting adjourned, thanks everyone [11:01] *claps* [11:01] thanks [11:01] <\sh> JaneW: no :) [11:01]