User1: good day all
User2: good afternoon Vietnam
User1: I'm trying to remember which countries have holidays today
User3: .no, .dk, .de, .fr AIUI.
User4: not me
User3: I'm not really here, I'm leaving for dinner at my father's in 15-ish minutes.
User1: that certainly accounts for a chunk
User1: User5 kernel team accounted for?
User2: so I'm expecting BenC, bryce_, kylem, pkl, rtg
User1: Keybuk is ill today
User5: missing two
User2: and bdmurray
User1: and Riddell is on leave
User1: but I believe iwj is expected
User6: here
User4: I'm here too
User7: .pt is not a holiday, I am here.
User5: I think everyone thought like I did, meeting in an hour from now
User2: ok
User2: User8 ping?
User1: User5 why?
User5: 16:00 UTC == 12 noon my time
User2: -!- Topic for #ubuntu-meeting: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 17 May 16:00 UTC: Ubuntu Development Team | ...
User1: oh, Scott's reminder and the distro team calendar disagree
User5: right
User1: I have a conflict at 1700 BST
User2: User9 ping?
User1: if everyone is here, I'd prefer to do it now
User5: pkl and kyle are probably not required, so I say move on, and let them catch up
User2: User1 also adilson?
User1: he's apparently at lunch, so probably expecting 1600 UTC
User1: User2 the email I sent to you/Scott earlier outlines my current areas of interest
User1: User2 could you run the meeting at 1600 UTC for me?
User2: I had been hoping to leave at 1630 UTC today
User2: but I guess so
User1: User2 do you have any agenda items?
User8: User2 I'm here
User2: User1 not at this point
User9: Hi.
User9: Oh, now would be OK.
User8: now's fine for me too
User2: why don't we just go ahead now; we seem to have nearly everyone
User1: sounds good
User2: first item is UDS output
User2: all the workshops should be written up, ideally by the end of this week
User1: Colin and Scott will review with each of you
User2: if there are any parts you can't remember, the sysadmins are working on producing voice recordings, but hopefully you all have notes
User1: it's important to have the writeups from UDS done soon, as memory fades
User2: does anyone have any questions about that process?
User1: for specs which were produced independent of UDS, the hard deadline is 31 May
User1: but enough detail is needed at this stage for the selection process
User2: mdz and I have done an initial pass over everything we could find and tried to set priorities
User1: everything which is concrete and feasible should be proposed as a gutsy goal
User2: no doubt some things will need to be added, and others tweaked
User9: gutsy goal> Oh, I should check that for mine.
User1: the tech board, canonical, etc. will review the list and construct the overall roadmap
User1: is everyone clear on what's expected for gutsy specs?
User1: silent assent :-)
User3: is there anything different than before?
User3: I'm aware of the template changes Scott made
User3: but anything else?
User1: the timeline we just explained
User3: I meant the content.
User3: (sorry for not being clear)
User1: nope
User2: speaking of which, the spectemplate now has a release note as a mandatory item
User2: I can well imagine that a release note will not be appropriate for everything
User1: the template has changed slightly; if it's not self-explanatory, ask
User9: I've been writing those in the past tense even though they're in the future.  I assume that's correct ?
User2: how about "mandatory for user-visible items"?
User2: User9 writing which?
User9: == Release Note ==
User2: yes, it's for cut-and-pasting
User1: User2 it's a good exercise to describe the value of the work, even if it's not user-visible
User2: (theoretically)
User9: I think the person assembling the release notes can decide to ditch it if it doesn't seem sufficiently interesting.
User2: in that case, I will edit the template to say that not all notes will necessarily be included
User1: it should be obvious who the approver should be for each spec, if it isn't already set
User1: User2 works for me
User9: User1 Do you mean that we should set the approvers or do you mean the techboard will know ?
User2: if in doubt about the approver of a spec, it's the manager of the main person in Canonical responsible
User9: Right.
User1: User9 you should
User2: unless there's some exceptional circumstance (e.g. other expert)
User1: otherwise it won't show up on that person's approval list
User1: ok
User1: we're planning a mobile mini-sprint next month, which just a few folks will attend
User1: if you're working on a team project which would benefit from such an event, please let me know
User1: that's pretty much all from me today
User1: other business for the meeting?
User2: oh, other item is merges
User2: I assume everyone is aware from -devel-announce that the merge-o-matic is running
User2: the gutsy release schedule calls for Debian auto-syncs to be frozen on 21 June, by which time all packages in main requiring a merge should have been merged at least once
User5: User2 any chance of getting a merges-bof for people who aren't yet familiar with the process?
User5: docs are currently geared toward people who already know debian packaging
User1: I think there's an existing MOTU school bit for that
User5: ah, maybe those docs are a bit better
User2: by my count, that would be amitk, asac, bdmurray, bryce, evand, pkl, rtg, maybe kwwii
User2: but it's not too critical for the kernel team or bdmurray
User2: or kwwii come to that
User5: merges seemed a good way for amitk, pkl and rtg to get into packaging
User8: kees schooled brian and I on merges (but using DaD not MoM)
User2: User5 a fair point
User2: if the MOTU school documentation isn't adequate, let me know and I'll be happy to run a quick bootcamp
User5: ok
User1: sounds like a good topic for the mailing list, as some new folks aren't at this meeting
User2: to clarify, after the Debian import freeze on 21 June, merges and explicitly-requested syncs are still permitted without approval until 16 August
User2: https://wiki.ubuntu.com/GutsyReleaseSchedule
User2: User1 ok, that's all from me
User1: ok
User1: last call for other business
User4: The distro sprint is in early July on that schedule right?
User2: User4 correct, the "Developer Sprint" item
User1: that wasn't on the calendar yet, fixing that
User4: Some was trying to tell me it was August but I won't name names.
User2: if it was me, I claim temporary insanity. :)
User5: I think it was me, but I claim too much beer in Spain
User4: heh
User5: sprint is London, correct?
User9: t
User6: How many days? It starts on a Thursday.
User1: User5 yes
User1: User6 monday-friday that week
User9: User6 No, that Thursday is in the middle.
User2: I'll edit the schedule to note that
User9: All of the week-long things are on the schedule `on the Thursday' just because that's how the schedule is laid out.
User10: BenC, dont forget the fridge magnet ;)
User2: any other business?
User5: we don't have magnets here, we staple things to the cows
User10: so bring a cow then i heard there is lots of space ;)
User1: ok, that's a wrap then
User1: thanks, all.  apologies for the time confusion
User5: bye everyone
User4: bye
User11: yeah, bye
User12: User1 I'm here, what's up?
User1: User12 the weekly team meeting was held a bit early
User12: User1 the weekly team meeting? I'm sorry but I wasn't aware of that.
User1: User12 we have some catching up to do. you are subscribed to the distro-team mailing list, though, yes?L
User1: a reminder  is sent out the previous day
User12: Sorry, I'm not. I missed this list I guess.
User12: I'll subscribe right now.
* ..[topic/#ubuntu-meeting:ubotu] : Current meeting: Ubuntu Development Team | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 May 20:00 UTC: Forum Council | 20 May 17:00 UTC: Xubuntu Developers | 22 May 20:00 UTC: Technical Board | 23 May 20:00 UTC: Edubuntu | 24 May 20:00 UTC: Ubuntu Development Team
* ..[topic/#ubuntu-meeting:ubotu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 18 May 20:00 UTC: Forum Council | 20 May 17:00 UTC: Xubuntu Developers | 22 May 20:00 UTC: Technical Board | 23 May 20:00 UTC: Edubuntu | 24 May 20:00 UTC: Ubuntu Development Team | 29 May 15:00 UTC: Kernel Team
User13: @schedule Andorra
User14: Schedule for Europe/Andorra: 18 May 22:00: Forum Council | 20 May 19:00: Xubuntu Developers | 22 May 22:00: Technical Board | 23 May 22:00: Edubuntu | 24 May 22:00: Ubuntu Development Team | 29 May 17:00: Kernel Team
ubuntu-meeting
Ubuntu IRC