/srv/irclogs.ubuntu.com/2011/05/19/#ubuntu-meeting.txt

=== krtek is now known as Captainkrtek
=== yofel_ is now known as yofel
=== doko_ is now known as doko
=== Quintasan_ is now known as Quintasan
NCommanderMorning all, who's around?15:57
NCommander#startmeeting16:00
MootBotMeeting started at 10:00. The chair is NCommander.16:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:00
ogra_moop16:00
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2011/2011051916:01
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2011/2011051916:01
* NCommander pokes ogra_'s moop16:01
ogra_ouch !16:01
ogra_dont you touch my moop !16:01
NCommander[topic] Standing Items16:02
MootBotNew Topic:  Standing Items16:02
NCommander[link] http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html16:02
MootBotLINK received:  http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html16:02
NCommander[link] http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-oneiric-alpha-1.html16:02
MootBotLINK received:  http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-oneiric-alpha-1.html16:02
NCommanderNone of my specs are showing up ...16:02
* ogra_ isnt done yet with spec writing 16:02
NCommanderOh right, it has to be approved, doesn't it16:03
NCommanderbah16:03
ogra_NCommander, lets go over them to see if everything is set right (accepted etcd)16:03
ogra_after meeting16:03
* davidm is happy bp are getting done16:03
ogra_but its good to see the tracker work16:03
ogra_doesnt look like as much hassle for me as last round16:04
* NCommander likes our '2.0' blueprints for A1 :-)16:04
NCommanderRight16:04
NCommanderso moving on16:04
NCommanderif my web browser didn't force quit ...16:05
NCommander[topic] Unity 2D Status16:05
MootBotNew Topic:  Unity 2D Status16:05
ogra_use an ac100, its more stable :P16:05
ogra_i think we can drop that16:05
ogra_desktop team takes over now16:05
ogra_i talked to didrocks in budapest16:06
davidmI think it's DX team and desktop team16:06
NCommandercool16:06
* NCommander brings dead to this standing item16:06
ogra_well, i think upstream is still the same16:06
ogra_not DX afaik16:06
NCommander[topic] Kernel Status (cooloney, rsalveti)16:06
MootBotNew Topic:  Kernel Status (cooloney, rsalveti)16:06
ogra_heh16:06
ogra_NCommander, ppisati16:06
rsalveti:-)16:06
ogra_and we should probably include the linaro platform guys that work on kernel bits in that16:07
ogra_do you have any ?16:07
rsalvetisend an SRU for bug 77067916:07
ubottuLaunchpad bug 770679 in u-boot-linaro (Ubuntu) "Missing proper support for Beagle XM rev B and C" [Undecided,New] https://launchpad.net/bugs/77067916:07
NCommanderrsalveti: won't that require an item respin of natty, no?16:07
rsalvetistill waiting for comments16:07
rsalvetiNCommander: in theory yes16:07
rsalvetibut we can just publish a new kernel file somewhere and update the wiki16:08
rsalvetilike we did with maverick16:08
ogra_well, we can alsways provice replacement uInitrd and uImage16:08
rsalvetiyeah, that's what we did with maverick16:08
ogra_right16:08
rsalvetibut no other update16:08
rsalvetiti-omap4 kernel is kind of the same16:08
rsalvetiwill be sending another SRU for the drm driver next week16:09
ogra_do you have anyone in your team that should be included in the topic ping ?16:09
rsalvetinow that I got that sorted out with linaro kernel16:09
rsalvetiogra_: that depends on what exactly we want to discuss16:09
ogra_same for any other of the standing topics :)16:09
rsalvetisure, we can solve this offline16:09
ogra_yeah16:10
rsalvetithat's all for me16:10
ogra_ppisati, everything fine in your world ?16:10
rsalvetiNCommander: put an action for you to include ppisati at this topic :-)16:11
NCommanderrsalveti: I already edited the wiki16:11
ogra_well, seems he isnt around ... neither is cooloney16:11
ogra_so move :)16:11
NCommander[topic] ARM Porting/FTBFS status (NCommander, janimo)16:12
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, janimo)16:12
ogra_its horrid16:12
NCommanderfpc was bootstrapped on armel but beside that not much to add as the buildds drain16:12
ogra_yeah, will still need a while to lighten up16:12
* NCommander isn't going to touch it until the build queue is close to empty16:12
ogra_i occasionally go over them and give back what looks like being worth it16:13
ppisatiogra_: let me read...16:13
* ogra_ wonders where jani is 16:14
ogra_still jetlagged from the 100km train ride probably :)16:14
GrueMasterheh16:14
NCommanderogra_: :-P16:14
NCommandercan I move on?16:14
ogra_yeah16:15
NCommander[topic] ARM Image Status (ogra, NCommander)16:15
MootBotNew Topic:  ARM Image Status (ogra, NCommander)16:15
ogra_well ...16:15
ogra_waiting for live-build to be implemented for x8616:15
ppisatiah k :)16:15
ogra_i guess then we have a very small window to make it work for A116:15
ogra_the risk is high that we wont make A1 though16:16
GrueMasterAlways is.16:16
NCommanderYeah16:16
ogra_in other news i worked the week on preparing everything for the ac100 image16:16
NCommanderright now all CD image work is depwait A1, though cjwatson said if we implement stuff in livecd-rootfs, then he'll migrate it to livehelper16:16
ogra_the bits from https://launchpad.net/~ac100/+archive/ppa will land in oneiric next week16:16
ogra_so that we can start rolling images16:17
ogra_look, its a jani :)16:17
* NCommander throws a pokeball at wild janimo 16:17
janimosorry, forgot what time it was16:17
NCommander:-P16:17
ogra_well, thats all about images atm ... toboin ?16:17
ogra_anything to say about nook ?16:18
ogra_GrueMaster, ^^16:18
GrueMasterNot yet.  Main focus has been on usbboot for panda.16:18
ogra_yeah, thought so16:18
ogra_though you had lots of converation going on about nook images in the channel :)16:18
GrueMasterAlthough one user has gotten some work towards making it boot natty.16:18
ogra_*conversation16:18
NCommandercan I move on?16:19
ogra_go16:19
NCommander[topic] QA Status (GrueMaster)16:19
MootBotNew Topic:  QA Status (GrueMaster)16:19
GrueMasterHey, that's me!16:20
ogra_wohoo !16:20
GrueMasterMy focus this week has been gitting panda to boot via usb blob from a host system.16:20
ogra_for automated image testing ;)16:20
janimoGrueMaster, this means no SD card needed at all?16:21
ogra_yeah16:21
GrueMasterThis will help a lot for the new buildd deployment, and also help to build an image automation framework.16:21
janimosweet16:21
GrueMasterNo SD card was harmed in the making of thisproduction.16:21
ogra_lol16:21
janimosome SD cards deserve to be harmed though16:21
ogra_hehe16:21
GrueMasterCurrently I am hung on getting the usb & network ports initialized.  I have a working kernel & initrd.16:22
GrueMasterReviewing x-loader & u-boot code tosee what they do to enable them.16:22
ogra_i'll get you the initrd bits until monday16:22
NCommanderGrueMaster: seems like a lot of it is hte board just isn't happy coming up OTG. could be an issue of whats being iniialized vs what isn't?16:23
GrueMasterI'm using the headless image as a test base.   I have the rootfs on a USB drive andam pushing down the kernel with a modified initrd.16:23
GrueMasterYes.16:23
GrueMasterNot sure if it is the otg port getting in the way,but it shouldn't as they are completely separate circuits.16:24
ogra_NCommander, well, its the decision of putting half the board init code into x-loader and u-boot16:24
NCommanderwell yes16:24
ogra_if it would live in the kernel as it should, there wouldnt be any probs16:24
GrueMasterbtw:  u-boot doesn't appear to support usb.16:24
ogra_GrueMaster, rsalveti is working on it16:24
GrueMasteryes, I know.16:25
rsalvetiGrueMaster: u-boot supports usb now ;-)16:25
ogra_and martyn told me yesterday that the PXE support patch landed upstream16:25
rsalvetiand TFTP16:25
GrueMasterHopefully we can work together today and get a solution.16:25
rsalvetion my branch16:25
GrueMasterNice.16:25
rsalvetibut I still prefer to jump into the kernel directly16:25
ogra_\o/16:25
ogra_++16:25
ogra_but at least we have something even if that doesnt work16:26
rsalvetianyway, just working with GrueMaster to see what we can get16:26
rsalvetiyup :-)16:26
GrueMasterThe aboot->kernel method is much cleaner, but what ever it takes to get forward progress is semi-acceptable.16:26
ogra_the good thing is that we could even use it in the images and boot *way* faster16:26
rsalvetilet's spend some more time trying to get this to work16:26
ogra_we should inspect that16:27
GrueMasteronce I get this working (critical priority), I'll focus on blueprint refinement and nook color.16:27
rsalvetiyeah, can add that at my u-boot tftp bp16:27
rsalvetiI'll be changing it to "alternatives to boot ubuntu images"16:27
rsalvetisomething like that16:27
rsalvetiomap4boot16:27
ogra_cool !16:27
rsalvetiu-boot with TFTP and PXE16:27
rsalvetiand u-boot with fastboot16:27
rsalvetithat should cover most of the cases, if not all16:28
GrueMasterThat's all from me.  Questions?16:28
ogra_not here16:28
NCommander[topic] Specification Status16:29
MootBotNew Topic:  Specification Status16:29
NCommanderprobably a good idea to go over this16:29
NCommanderI have two spcs drafted, one reviewed, one I mostly completed then handed off, and one that still needs a writeup16:30
* ogra_ has nothing to report yet ... mine will be ready by monday16:30
ogra_janimo, GrueMaster ?16:31
janimoI have work items more or less written up on my specs16:31
janimobut no other work. Drafting means filling up the wiki template?16:31
ogra_(and anyone else having specs on the team tracker :) )16:31
ogra_janimo, yeah16:31
GrueMasterI think NCommander has been plastering me with work items.  I have been toofocused to check.16:31
janimoteam tracker == burndown charts?16:31
ogra_you dont need all topics from the tamplate, only what makes sense in your context16:31
ogra_yeah team tracker == burndown16:32
NCommander[topic] ABO16:34
MootBotNew Topic:  ABO16:34
* NCommander has nothing16:34
GrueMasterABO???16:34
ogra_ABO ?16:34
ogra_OBA ?16:34
NCommander[topic] AOB16:34
MootBotNew Topic:  AOB16:34
ogra_BOA ?16:34
GrueMasterBOA?16:34
* NCommander beats ogra_ 16:34
ogra_BAOBAB16:34
GrueMasterBAO?16:34
ogra_BLAH :)16:34
* ogra_ doesnt have anything for this topic16:34
NCommanderI'm guessing we don't16:34
NCommanderclosiging the meeting in 316:35
NCommander216:35
NCommander116:35
NCommander#endmeeting16:35
MootBotMeeting finished at 10:35.16:35
=== ayan is now known as ayan-afk
pitticjwatson, mdz, kees, Keybuk: TB meeting now?18:59
Keybukpresent18:59
kees\o19:02
sabdflo/ ?19:02
sabdfl;-)19:02
keesI have a hard-stop in 30 minutes, though19:02
Keybukwho is chair today?19:04
keesagenda says mdz19:04
pittisent SMS to mdz and cjwatson19:04
sabdflhttps://wiki.ubuntu.com/TechnicalBoardAgenda19:05
sabdflshould we just dive in?19:05
sabdfldo we have anything like a quorum?19:05
pittifour people should be enough?19:05
keesyeah, we have 419:05
sabdflok, i'll take the chair, i'm somewhat overdue19:06
sabdflMootBot: #startmeeting19:06
sabdflsigh19:06
sabdflhelp19:07
pittiwithout the mootbot: I think19:07
persiaDon't highlight MootBot when starting19:07
sabdfl#startmeeting19:07
MootBotMeeting started at 13:07. The chair is sabdfl.19:07
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:07
cjwatsonhi, I'm here now19:07
sabdfl[TOPIC] Status of Lubuntu19:07
MootBotNew Topic:  Status of Lubuntu19:07
sabdflwe had a session or two at UDS on this19:08
cjwatsonI think Lubuntu was adequately resolved at UDS, yes19:08
cjwatsonit is blocked on more disk on antimony + cdimage.ubuntu.com internal mirrors, but that is in train19:08
sabdflcjwatson: elmo says np to bigger disks on cdimage19:08
cjwatsonright19:08
cjwatsonblocked as in that-hasn't-happened-yet, not as in we-need-to-convince-people19:08
sabdflokdokey19:08
sabdflso, the status is it will be official as soon as we have the new space, and that's approved, just not actioned19:09
keessounds good to me19:09
cjwatsonhttps://rt.admin.canonical.com/Ticket/Display.html?id=45727, for Canonical folks19:09
sabdfli'll document that in the meeting report, i don't think we need to announce anything till we actually have a release19:09
Keybukcool19:09
cjwatsonagreed - it'll be easy to turn on once we have headroom19:09
sabdfli'm sure the Lubuntu folks will take the opportunity to raise their banner19:09
sabdflok, wrapped19:10
pittishoudl we follow up to Julien on the list?  or was that already resolved at UDS?19:10
sabdfl[TOPIC] ffmpeg vs libav19:10
MootBotNew Topic:  ffmpeg vs libav19:10
sabdflpitti: i think it's resolved, but feel free to send him this snippet of IRC?19:10
pittisabdfl: sure19:10
cjwatsonpitti: yeah, Julien knows19:11
keesso, it's not just Ubuntu -- Debian did the ffmpeg -> libav thing too, but that masks a bit that it's the same maintainer19:11
sabdflhmm.. why are we not listed at https://wiki.ubuntu.com/Teams ?19:11
sabdfli was looking for the team report page19:12
cjwatsongood question19:12
sabdflok, will find that later19:13
cjwatsonhttps://wiki.ubuntu.com/TechnicalBoard/TeamReports19:13
sabdflkees, so we are de-facto diverged from debian, for lack of consensus on this within ubuntu?19:13
pittiwould be intersting to hear siretart's side of the storey19:13
pittistory19:13
cjwatsonlibav is currently waiting in NEW IIRC19:13
cjwatsonnot due to any particular archive admin animus that I'm aware of, but just post-oneiric-opening/UDS backlog19:13
cjwatsonoh, wait, I stand corrected19:14
cjwatsonlibav is in oneiric19:14
cjwatsonso we are not at present diverged from Debian, except by an Ubuntu delta to the libav package19:14
cjwatsonwhich is small: http://patches.ubuntu.com/liba/libav/libav_4:0.7~b1-1ubuntu1.patch19:14
keeslibav is even in _natty_19:14
keesand their versioning is charging ahead.19:15
sabdflis there any certainty that libav will be a more cohesive community?19:15
cjwatsonyou're right, I must have been thinking of binary NEW19:15
sabdflfor example, will they take a more dev-friendly approach to sonames?19:15
cjwatsonpersonally I'm extremely reluctant to take any view at all on this without hearing both sides - has anyone been in touch with Reinhard about this?19:15
cjwatsonlibav has what looks like actual versions rather than datestamps19:16
keessabdfl: that's my question too. I don't feel like I have all the information I need to form an opinion19:16
cjwatsonoh, blah, so did our ffmpeg packages19:16
keescjwatson: I haven't heard from siretart19:16
* micahg is a little sore about breaking BC in the libavcodec52 to libavcodec53 transition, but idk what that's worth19:17
cjwatsonit's clear to me that there's a social split in the community, but I don't think we should be attempting to judge that19:17
sabdflis there an active thread on -tb? is this something that needs a private conversation, if it's about social dynamics that are already stressed upstream?19:17
pittino active thread AFAICS19:17
cjwatsonwe should be taking a decision on technical merit, which probably to some extent needs to include the views of the developers willing to work on this in Debian/Ubuntu (although not necessarily be dominated by that)19:17
cjwatsonmuch of the impetus for the mail sent to us seems to be social19:18
pittirealistically, if we'd decide for ffmpeg instead of libav, we'd need someone else to maintain it, though19:18
cjwatson(though there is some technical content)19:18
keesyeah, if the Debian and Ubuntu maintainer chose libav, that does carry a fair bit of weight19:19
cjwatsonmicahg: BC?19:19
keesbinary compat19:19
micahgcjwatson: backwards compatability19:19
keesoh19:19
keesheh. I thought you meant ABI19:19
cjwatsonin a sense stronger than what usually happens when you change soname?19:19
cjwatsonwas it an API break as well?19:19
micahgcjwatson: yes19:19
keesowch19:20
cjwatsonok, well - that does happen sometimes, I'm not sure that should be determining without details19:20
cjwatsonif we never allowed API breaks there wouldn't be much in the platform :-)19:20
keesright19:20
keesbut to do it so "soon" after a fork makes things almost more painful.19:20
cjwatsonI'm feeling very low on facts here19:21
micahgsome of it was cleaning up namespaces19:21
cjwatsoncan somebody take an action to catch up with siretart and get his side?19:21
keesI'll take that19:21
cjwatsonsorry, I'm back-seat-chairing, I should stop that19:22
sabdflit's very helpful when it's helpful :-)19:23
sabdfl[ACTION] kees, invite siretart to comment on TB list, or in private, as appropriate19:23
MootBotACTION received:  kees, invite siretart to comment on TB list, or in private, as appropriate19:23
cjwatsonI was about to say that we should have somebody with relevant expertise go off and produce an impartial report, but one might reasonably argue that that's the TB's job :-P19:23
sabdfl[TOPIC] Follow up on https://bugs.launchpad.net/bugs/451390 (mdz)19:24
MootBotNew Topic:  Follow up on https://bugs.launchpad.net/bugs/451390 (mdz)19:24
ubottuUbuntu bug 451390 in ubuntu-community "limited upload rights no longer give series nomination accept/decline rights" [Undecided,New]19:24
pittihm, fixed a week ago19:25
cjwatsonthat bug is apparently closed in LP, but I have not got round to finding somebody with the right set of privileges to real-world-test it19:25
pittiI can take that19:25
keescjwatson: we could maybe try bjf?19:25
pittiwe have plenty of non-core-devs in the desktop team19:25
keeshe was most recently added to ubuntu-drivers for the nominations purpose19:25
micahgI tested it, I can now approve stuff in main that I can upload even though I"m MOTU19:25
keesmicahg: ah! even better, thanks!19:25
pittiah, good19:26
sabdflso, that's fix confirmed?19:26
pittiso we can also close the community task then19:26
keeswe probably need another action to purge ubuntu-drivers of people that were added there as a work-around for this bug19:26
sabdflpitti: can you take care of that?19:26
pittisabdfl: no, because I already did it :)19:27
sabdfl:-)19:27
sabdflit's that time machine of yours, pitti19:27
sabdfldo we all have admin on ubuntu-drivers?19:27
sabdfldo we know who was added just for that purpose?19:27
pittisabdfl: yes, TB owns it19:27
pittijasoncwarner is the latest member, I think that was done at UDS19:28
pittiso that he could shuffle around the summit schedule19:28
sabdfli doubt that's for this case, though19:28
pittiright19:28
pittiit was for blueprint handling19:28
pittiI only overheard it, though19:28
sabdflwe could of course just purge -drivers and add those who notice :-)19:29
sabdflwere all such additions documented in TB meetings, or ad-hoc?19:29
pittihttps://launchpad.net/~ubuntu-drivers/+members doesn't look unreasonable, though19:29
pittipretty much the tech leads, and folks who should be able to approve/change blueprints19:30
sabdfljosh hoover?19:30
keesit's been ad-hoc, afaik. I have removed bjf, as he was one I added and documented in the nominations bug report19:30
pittisabdfl: U1 team uses ubuntu blueprints for their work19:30
sabdflok, let's consider that done19:30
sabdfl[TOPIC] Action review19:30
MootBotNew Topic:  Action review19:30
keesI have to go now; I'll check backscroll when I'm back.19:31
sabdflcheers kees19:31
sabdflAction: rickspencer3 will bring up the state of unity on the -desktop list for public review and discussion19:31
sabdfldone19:31
sabdflI asked for a review between TB and DX and Desktop on Natty/Unity at UDS, but failed to get to it myself.19:32
sabdflI saw good dialogue between DX and Platform-Desktop about how to improve processed for Oneiric19:32
sabdflbut figured TB would have useful commentary and critique19:32
sabdfldid anyone here get to that session?19:33
pittinot me unfortunately19:34
pittioh, except if that was the session where everyone brought up their pet bugs19:34
pitti(and praises)19:34
pittiI was in that one19:34
sabdflno, i think that was the Unity design review19:34
pittiright19:34
sabdflfrom a governance point of view, i thought the debate / discussion about unity-by-default was healthy19:35
pittion -devel@? I agree19:35
sabdflhowever, i think it flagged a lack of clarity on responsibilities and delegation19:35
cjwatsonI think I was in that session - http://summit.ubuntu.com/uds-o/meeting/community-o-natty-retrospective/19:35
sabdflfrom my perspective, TB is on the hook for technical decisions, the health of the developer community, quality, across the whole archive19:36
pittiah, now I remember, thanks cjwatson for the link19:36
cjwatsonthere was a lot of discussion about when people felt it appropriate to involve the TB in things, and some fairly obvious disconnect19:36
sabdfli think the TB could rightly have provided guidance and critique on freezes, testing, dependencies, delivery19:36
cjwatsonalso discussion about the role of the TB versus the release team19:36
sabdfli think teh release and desktop teams, however, need to feel they have a mandate too19:37
cjwatsonI think I view the release team as sort of the "ordinary" authority on these matters, and the TB is an appeals/escalation body as well as sort of wider policy setting19:37
sabdflright19:37
ScottKI was in the session and expressed views similar to cjwatson19:37
pittithat mainly clarified the status quo of reactive "where the buck stops" dispute resolution (TB) vs. "day-to-day exception processing and archive consistency" (release)19:37
sabdfli felt we undermined the desktop team a little by leaving the scope of the conversation so wide19:38
cjwatsonin my view the unity-by-default debate should probably have involved the release team more than it did, but at the time, bouncing things around between groups would have been unnecessary bureaucracy19:38
cjwatsongiven the short timescales involvd19:38
sabdfli hoped the natty retro would give the TB an opportunity to set tighter guidelines on things which define the quality of the release, while also strengthening the desktop teams ability to make in/out calls19:38
pittiTBH the discussion about unity or not wasn't really a good release team matter anyway, as this is was a major project-wide decision19:38
sabdflright - we'll likely only ever see micro-versions of that debate in future19:39
cjwatsonwe talked about the way the TB is quite reactive, and I mentioned that a while back we started trying to deal with something proactively every now and again, but it kind of fizzled out19:39
sabdfland those are unlikely to get kicked up19:39
cjwatsonsomebody suggested having a secretary to the TB whose job it is to keep track of the kinds of things we ought to be discussing, which I think is a great idea19:39
cjwatsonwas that ScottK?19:39
ScottKThat was me.19:39
sabdfli think it would help if we had non-Canonical representation in the desktop team19:40
sabdflhowever, such folk will certainly feel pressure, possibly unfairly, from all quarters19:40
cjwatsonI'm slightly cautious of fighting the last war (if you'll excuse the martial metaphor)19:40
cjwatsonthe next debate of this king may not be anything to do with the desktop19:40
cjwatson*kind19:40
sabdflright, but the underlying principle should hold19:41
pitti*cough* systemd *cough*19:41
persiaEncouraging teams to consist of members from several viewpoints is likely useful regardless of the conflict.19:41
sabdflwell, that one may well be for the TB, as it's hardly desktop OR Server OR kubuntu OR ...19:41
pitti(as a totally random example of what might come up as a similar discussion)19:41
sabdflbut is there any difference of opinion about the TB as guardian of quality, of talent and code, delegating decisions like in/out app selections to teams like -desktop?19:43
ScottKAlso for technical dispute resolution.19:43
sabdflthat too19:44
cjwatsonsabdfl: I don't think anyone is of the opinion that the TB should be micromanaging day-to-day (or even month-to-month) decisions19:44
sabdflKeybuk: as a non-Canonical voice, what say you?19:44
persiaFor consistency with the ReleaseManifests, I'd prefer if the TB delegated those decisions to the Product Managers, but in practice, it's nearly the same thing.19:44
cjwatsonwhich is good because I don't think we could if we wanted to :-)19:44
Keybuksabdfl: I think as long as things are discussed in Ubuntu forums, it's ok19:45
Keybuke.g. UDS is a great place to have those kinds of technical discussions19:45
Keybuklikewise the Ubuntu mailing lists19:45
* pitti has some difficulty with answering that question about the unity example, as the desktop team (and me) was quite biased19:45
sabdflagreed19:46
* ScottK died a little inside when Keybuk said "Ubuntu forums" as a place for technical discussions. Thanks for clarifying.19:46
KeybukI think we only have a problem if technical decisions for Ubuntu are made entirely within Canonical, and that's an appropriate juncture for the TB to step in, at least if only to bring the community back into the mix19:46
KeybukScottK: the lowercase "f" was deliberate19:46
sabdflthe English sense of "forum" :-)19:46
cjwatsonUbuntu fora, to distinguish ;-)19:46
* cjwatson hides19:46
sabdflthe Latin sense of fora :-)19:46
sabdflalright19:46
sabdfllet's stop buggering around19:46
Keybukcjwatson: fora, forii or foruum?19:46
* ScottK knew, but it was too funny to leave there.19:46
sabdflAction: mdz to attach missing patches for debian bugs 151820 308832 35325 and 32667719:47
ubottuDebian bug 151820 in dhcp3-client "dhcp3-client: Does not send hostname to server by default" [Wishlist,Open] http://bugs.debian.org/15182019:47
Keybukpitti: I think there will always be bias, humans are biased things19:47
Keybukbut another word for bias is passion ;-)19:47
pittifrom my POV, the TB was quite the right place to resolve that question of "unity by default", modulo sabdfl decision19:47
pittiKeybuk: that's what I really meant, I guess19:47
Keybukand I think if one person is particularly passionate about something, and the opposing side can't drum up equivalent amounts of passion to debate19:47
Keybukthen meh, passion wins :)19:48
pittiand I can't really claim that I have always been 100% objective in my appraisals for unity by default19:48
cjwatsonthe second and third of those Debian bugs have been dealt with19:48
cjwatsonor at least in progress19:48
cjwatsonI don't see action on the first and fourth, though I know mdz is tracking this as part of DEX and perhaps we don't need to track it hre19:48
pittiKeybuk: fair enough19:48
cjwatsonbut how about we leave it on the list 'til mdz's next here to answer19:48
* Keybuk has to run in a minute19:49
sabdflok19:49
sabdfl[TOPIC] Mailing items outstanding19:49
MootBotNew Topic:  Mailing items outstanding19:49
cjwatsonhttps://lists.ubuntu.com/archives/technical-board/2011-May/000857.html is the biggest one19:50
Keybukthere's the item from Evan, but since neither Evan or Steve are here to debate it, we should probably defer19:50
cjwatsonI don't know if we can do it justice in ten minutes, anyway19:50
cjwatsonlet's apologise and properly agenda-ify it for next time, maybe?19:50
sabdflthis is brand new, isn't it?19:50
sabdflyes19:50
cjwatsonit is19:50
sabdflok, we should give it some email air19:50
sabdfl[TOPIC] Community bugs19:51
MootBotNew Topic:  Community bugs19:51
sabdflanything of note?19:52
cjwatsonmdz has assigned https://bugs.launchpad.net/ubuntu-community/+bug/252368 to us19:52
ubottuUbuntu bug 252368 in Launchpad itself "Automatically associate DD and DM accounts with GPG keys in keyring packages" [Low,Triaged]19:52
cjwatson(the other one is old)19:52
sabdflsounds like something for the stakeholders meeting, or a call-for-a-patch19:53
cjwatsonbut I'm not clear what he wants to discuss there - it seemed to me that Debian had already offered some suggestions and it was just that it wasn't easy to do in LP?19:53
sabdflsounds entirely scriptable with LP's API19:53
pittithe "if" is (hopefully?) not much of a debate, or does anyone think this shouldn't be done for some reason?19:53
sabdfliirc, this was something we wanted to do at the start, so no debate here19:54
pittiso, "Triaged"?19:54
sabdfldoes it being assigned to us mean we need to do something beyond raise it on the stakeholders discussion with LP?19:55
sabdflsure19:55
micahgjust to clarify, this is only for e-mail access and not soyuz, right?19:55
pittithat's how I understand it; for actions in emails to be effective you need to gpg sign19:55
pittilike " status fixcommitted"19:55
persiaUnless someone does something special, it would work for soyuz as well (but is unrelated to upload rights to Ubuntu: initially affects Soyuz through PPAs)19:56
sabdflok. i think that's a wrap19:56
sabdflnext meeting? and chair?19:56
cjwatsonI have one AOB19:56
cjwatsonjust briefly?19:56
sabdflgo ahead of course19:56
cjwatsonsomebody (I forget who, sorry) asked me at UDS about the status of appointing an Ubuntu community representative on the Launchpad stakeholders meeting19:57
cjwatsonI remembered that we discussed it but couldn't remember how far we got19:57
sabdflelected by the non-Canonical contributors to LP? ;-)19:57
cjwatsondoes anyone remember the status, or shall I put it on the agenda for next time?19:57
cjwatsonno, somebody to put forward the interests of the Ubuntu community as opposed to Ubuntu Platform Engineering19:58
pittiI think we discussed something like this in Orlando, but back then it wasn't "non-Canonical"19:58
persiaI don't remember getting any feedback to my mail to the TB from some time back: I asked for the TB to appoint someone, without restrictions on the person the TB selected.19:58
sabdfli'm sure Francis would be happy to entertain it19:58
pittijust "someone who is credibly speaking for the ubuntu community"19:58
cjwatsonsabdfl: yes, he was, and we discussed it in the TB19:58
cjwatsonwhat I have no idea about, stateless automaton that I am, is how far we got :-)19:58
cjwatsonhow about I do some homework on it and follow up next time, then19:59
sabdfli was only partly joking about picking from the pool of contributors19:59
pittia year ago we had three candidates on the table, IIRC19:59
sabdflsome familiarity with processes, scale, pace of change, complexity would be helpful if that person wants real influence19:59
pittiKeybuk, bryce, sladen were proposed back then19:59
persiahttps://lists.ubuntu.com/archives/technical-board/2010-November/000571.html19:59
sabdflbryce has certainly climbed in with both feet20:00
pittihttps://lists.ubuntu.com/archives/technical-board/2010-November/000571.html20:00
pittiah20:00
sabdfli'd be +1 bryce20:01
cjwatsonanyway, I realise we're out of time, so I'll chase down the discussions I'm sure I remember beyond that mail20:01
persiaIt's probably worth reconfirming with the nominees that they would still be willing to serve.  I haven't spoken to any of them about it in ~6 months.20:01
sabdflpersia, will you chat to bryce about it?20:01
sabdflnext meeting is...20:01
persiaSure.  I can re-canvass, and send another mail.20:01
sabdfland chair... mdz?20:01
cjwatsonseems like his turn20:02
sabdflanyone know the date?20:02
sabdflthen we can wrap :-)20:02
persia2nd June (UTC)?20:02
sabdflok, done. thank you all!20:02
sabdfl#endmeeting20:02
MootBotMeeting finished at 14:02.20:02
pittithanks everyone!20:02
cjwatsoncheers20:03
=== Technovi1ing is now known as Technoviking

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!