=== micahg_ is now known as micahg === cjohnston is now known as cwt-bugs === cwt-bugs is now known as cjohnston === fenris is now known as Guest45833 === Guest45833 is now known as ejat === fenris is now known as Guest67783 === apachepanda is now known as apachelogger === doko_ is now known as doko === greyback is now known as greyback|bia === evilserfus is now known as serfus === Ursinha` is now known as Ursinha === greyback|bia is now known as greyback === Quintasan_ is now known as Quintasan === bladernr_afk is now known as bladernr_ [16:00] o/ [16:00] #startmeeting Ubuntu Friendly [16:00] Meeting started Mon Jan 30 16:00:18 2012 UTC. The chair is cr3. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:00] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Friendly Meeting | Current topic: [16:00] Hi everyone, welcome to the weekly Ubuntu Friendly meeting [16:00] hey! [16:01] hi ara and roadmr, anyone else around? [16:01] jedimike: hi there, I was just thinking of you, glad you could join us! [16:01] hi! [16:02] telepathic ping [16:03] topics for today are: [16:03] * Linking to Ubuntu Friendly after running Checkbox: cr3 [16:03] * AOB [16:03] Let's get started! [16:03] #topic Linking to Ubuntu Friendly after running Checkbox [16:03] o/ === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Friendly Meeting | Current topic: Linking to Ubuntu Friendly after running Checkbox [16:04] jedimike: 'sup? [16:04] i think we should link to UF after running checkbox, only if the UF requirements have been met (that is, no tests were manually deselected at the start of the test run) and if the requirements were not met, have a message saying how to participate in UF with future test runs [16:05] otherwise we might get a lot of incomplete runs that don't make it, and have people wondering why [16:05] .. [16:05] jedimike: would you mind if I postpone an answer to that until I give a little summary of the topic? [16:06] cr3: not at all :) [16:06] i may have jumped the gun a bit there I realise now ;) [16:06] This weekend, I sent a message to the ubuntu-friendly-squad mailing list about linking to the Ubuntu Friendly website on the last screen of running Checkbox. [16:06] In summary, the problem is that the current process is synchronous: http://people.canonical.com/~cr3/launchpad-results/before.png [16:06] The solution is that the process should be more asynchronous: http://people.canonical.com/~cr3/launchpad-results/after.png === bladernr_ is now known as bladernr_afk [16:06] First, this requires uploading submissions to the Results Tracker which would be a proxy to Launchpad for safe keeping. [16:06] Second, this also requires introducing the concept of a message queue to allow checkbox and Ubuntu Friendly to subscribe to message queues. [16:06] jedimike: I was prepared, so we should now address your concern. [16:07] jedimike: I agree with you but I have to admit that no solution comes to mind :( === yofel_ is now known as yofel [16:08] jedimike: one solution that just came to mind might be if consumers of the message queue could someone inject their own queues to which other consumers like checkbox could subscribe [16:09] jedimike: I'm not partitularly familiar with message queues nor their best practices, so what would you say if I assign myself an action item to get back to you? [16:09] cr3: sounds good, I only have minimal experience too [16:09] jedimike: if we solve the problem you raised, that would also solve the other problem I wanted to discuss today: [16:09] The only caveat is the slight delay between the time the user receives a message that the submission has been processed by the Results Tracker and the time Ubuntu Friendly has finished processing the results for that submission. [16:10] o/ [16:11] o/ [16:11] #action cr3 to explore message queues so that two consumers could commmunicate with each other, ie Ubuntu Friendly to dispatch a message to Checkbox so that it knows the submission is valid [16:11] ACTION: cr3 to explore message queues so that two consumers could commmunicate with each other, ie Ubuntu Friendly to dispatch a message to Checkbox so that it knows the submission is valid [16:11] ara: the floor is yours [16:11] for simplicity, maybe we should only provide the link back to UF to those that are not submitting anonymously, and, for those that provided their launchpad account, just send them an email when the result made it to UF (with the link) or a message that it ddidn't make it to UF if it didn't contain enough results [16:12] .. [16:12] ara: you mean a generic link to UF, not their submission, right? [16:13] cr3, their submission [16:13] (for those that provided their lp id) [16:14] ara: they just provide an email address so, whether it points to a valid launchpad account or not, you're saying we should email them as a best effort, right? [16:14] cr3, from 12.04 they will provide their launchpad id or just submit anonymously === bladernr_afk is now known as bladernr_ [16:16] ara: I'm not sure I understand how we can provide a "link back to UF to those that are not submitting anonymously", are you saying using the message queue I proposed or something else? [16:17] cr3, what I am trying to suggest is to avoid putting the information back into checkbox, just keep everything on the server side [16:17] ara: so just email, right? [16:17] yes [16:18] ara: ok, that's clear. I'd like to see how others feel about this idea rather than a more elaborate message queue: [16:19] #vote Do you think we should email users instead of providing the feedback directly in Checkbox? [16:19] Please vote on: Do you think we should email users instead of providing the feedback directly in Checkbox? [16:19] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [16:19] +1 (email seems like an easy first step, message queues can come later) [16:19] +1 (email seems like an easy first step, message queues can come later) received from cr3 [16:19] +1 [16:19] +1 received from ara [16:19] +1 and if the email bounces, we zap the submission :) [16:19] +1 and if the email bounces, we zap the submission :) received from roadmr [16:20] +! good solution while we don't have the queues [16:20] +1 good solution while we don't have the queues [16:20] +1 good solution while we don't have the queues received from jedimike [16:20] #endvote [16:20] Voting ended on: Do you think we should email users instead of providing the feedback directly in Checkbox? [16:20] Votes for:4 Votes against:0 Abstentions:0 [16:20] Motion carried [16:20] awesome, thanks folks! [16:20] roadmr: finally, your turn (I didn't forget) [16:21] cr3: I'll just post as I had it prepared, but I think the vote rendered it moot [16:21] Awesome, Ara proposes simplicity, my idea just complicates things more :) maybe checkbox can show a "processing..." progress dialog while UF finishes, and once UF sends the message saying it did, then checkbox pops up the (now functional) link. A safety timeout should be in place to keep users from staring at a checkbox progress bar longer than necessary :) [16:21] and one question, what tool did you use for the diagrams? :) [16:21] .. [16:22] roadmr: plotutils package, pic2plot command [16:22] roadmr: if you want the source, replace .png with .pic... and there's also a Makefile in the same directory [16:22] http://people.canonical.com/~cr3/launchpad-results/ [16:23] roadmr: your idea of "processing..." only works if the whole process becomes asynchronous, the current synchronous cron process would not lend itself well to interaction with the user [16:23] roadmr: however, the idea of introducing the message queue is exactly to provide the user experience you propose: 1. "processing..."; 2. url to *their* hardware in Ubuntu Friendly. [16:23] anything else on this topic? [16:25] #topic Any Other Business === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Friendly Meeting | Current topic: Any Other Business [16:25] anyone have any friendliness on their mind for today? [16:26] quickly in summary, you guys agreed to do away with the launchpad processing queues right? [16:26] balloons: for the time being, seems like everyone would like to see an email dispatched [16:26] o/ [16:26] roadmr: go ahead [16:26] I'd be kinda curious to see updated UF statistics now that we're deeper into Oneiric's 6 months of fame, are these available anywhere? [16:27] oops :) if not, can they be generated, would this be of interest? [16:27] .. [16:28] o/ [16:28] jedimike: your turn [16:28] we can regenerate the stats we had before with the latest data [16:29] there was a request for more detailed stats, but we need to do a bit more development to get them [16:29] jedimike: should I add an action item for you? [16:29] but the simple ones (submissions, etc.) we can get [16:29] cr3: yep [16:29] .. [16:29] #action jedimike to regenerate the stats we had before with the latest data [16:29] ACTION: jedimike to regenerate the stats we had before with the latest data [16:29] anything else? [16:31] seems like we've covered everything... [16:31] Thanks all for attending and for your comments and feedback! Have a great day! [16:31] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [16:31] Meeting ended Mon Jan 30 16:31:42 2012 UTC. [16:31] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-30-16.00.moin.txt [16:31] thanks cr3! [16:32] thanks! [16:32] it was fun :) [16:33] cr3: hey, I'm going to seem like a complete imbecile, but Checkbox is something I know nothing about really. It's a system for manual testing or no? [16:34] greyback: it can do that, or it can work in automatic, headless mode [16:34] greyback: it's for integrating test suites but also supports manual tests indeed [16:35] roadmr: cr3: hmm, ok. I'm a unity-2d guy, and am interested in how these things can work together. We're using a ruby-based automated test system, but I'm curious how other people do it, and how they handle manual tests [16:36] greyback: you work with agateau, right? him and didrocks have been working on checkbox-unity which simply checkbox with some unity specific tests [16:37] greyback: it is intended to enable the community to participate in testing which is where manual testing might be handy [16:37] cr3: Sure. I must check out checkbox-unity and see how well it applies to unity-2d (or not) [16:37] greyback: however, if you need a unit test suite, I'd recommend something that is most native to your project. somehow, I'm surprised you chose ruby, what was the motivation for this system? [16:38] cr3: because ruby rocks :P [16:38] cr3: we're using a test system called "Testability Driver" which allows inspection of Qt-based applications in great detail. It's scripted in Ruby, so we're using that [16:38] roadmr: never used it til now, some bits wreck my head, but it's nice :( [16:38] roadmr: sure, but forth also rocks and you don't see me using forth test suites :) [16:39] cr3: heh :) yes, greyback's reply makes more sense than mine [16:39] cr3: on the bright side, we could all be using java :( and we're not [16:40] roadmr: cr3: thanks for the info, I've something new to check out. If I can make manual-testers' lives easier, it'll be worth it [16:40] cr3: seriously, maybe they chose ruby because it's good for domain-specific mini-languages (see rails, even puppet) [16:40] they as in the creators of "testability driver" [16:40] greyback: if "Testability Driver" works for you, I'd suggest you keep using it. if you start needing multiple test frameworks together, then perhaps checkbox might be useful to run them together and unify the test results [16:41] roadmr: I'm all for using the right tool for the right job [16:41] cr3: it's worth looking into. In future there is hope to unify 3d & 2d's test=suites using cucumber/lettuce [16:41] hm, vegetables [16:41] roadmr: is it just me or does ruby lend itself well to DSLs? [16:41] roadmr: I've no idea why they used Ruby. All the scripts are doing is parsing XML really [16:42] cr3: not you, it does [16:42] greyback: well I'd have to look at the tool to see how it's used [16:42] roadmr: sure. I'm no Ruby jockey, am just getting by :) [16:42] greyback: I've been reluctant to jump on the BDD bandwagon so I'll be very interested to hear if you finally adopt cucumber/lettuce [16:43] cr3: Originally I avoided it too, yet another layer of abstraction complicating things. But it might help close delta between 2d & 3d [16:43] It'll be investigated next cycle. Tis all I'm going to push for [16:44] greyback: indeed, I'm seeing BDD as a bridge between people like customer/client or manager/developer, but it might be interesting that it could maybe bridge between technologies or projects too [16:44] cr3: developer/designer was a suggestion too [16:45] cr3: agreed. Personally I'm sceptical, but it's worth a go [16:45] greyback: agreed, but between unity 2d/3d, that's very interesting! I'll have to remember to ping you next cycle about it :) [16:45] cr3: sure thing [16:49] cheerio folks, thanks again for the excellent meeting! === CharlieMike is now known as ayan === chrisccoulson is now known as chrisccoulson2 [18:03] \o [18:03] \o [18:03] hello [18:04] o/ [18:05] hi! [18:05] sorry a tad late [18:05] let's get started [18:05] #startmeeting [18:05] Meeting started Mon Jan 30 18:05:47 2012 UTC. The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [18:05] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [18:05] The meeting agenda can be found at: [18:05] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:05] [TOPIC] Announcements === meetingology changed the topic of #ubuntu-meeting to: Announcements [18:06] FeatureFreeze is coming in a little more than two weeks (February 16th). Please try to finish any non-bugfix work items that are tied to the release by this date. Please talk to mdeslaur (and optionally me) soon if there are issues meeting this deadline. This is particularly true for essential and high priority items. [18:07] * Thanks [18:07] Jame Page (jamespage) provided oneiric debdiffs for Jenkins (LP: #914628) [18:07] Your work is very much appreciated and will keep Ubuntu users secure. Great job! :) [18:07] [TOPIC] Review of any previous action items === meetingology changed the topic of #ubuntu-meeting to: Review of any previous action items [18:07] jdstrand, np [18:07] :) [18:07] ACTION: jdstrand to make sure ubuntu-security gets QRT bug mail: DONE [18:07] ACTION: sbeattie to follow up on qrt bugs from QA team [18:07] sbeattie: iirc, you did that, right? ^ [18:08] jdstrand: bah, no, sorry, will do this week [18:08] please keep the action around [18:08] sbeattie: hmm, I think there might not be any more, but yes, please do. thanks [18:09] [ACTION] sbeattie to follow up on qrt bugs from QA team [18:09] ACTION: sbeattie to follow up on qrt bugs from QA team [18:09] well, nuclearbob set the status of those to opinion [18:09] which treats them as closed. [18:09] Anyway. [18:09] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [18:09] I'll go first [18:09] In addition to updates, etc, last week I focused a lot on improvements to UCT for CVE triage, particularly around triaging the output of the locate_cves.py script that mdeslaur wrote [18:10] I've handed off the remaining CVEs to tyhicks, and we will pass the list around til we are caught up [18:10] I'm on community this week [18:10] patch piloting today [18:11] have a lot of audits to do-- didn't do any last week [18:11] I would like to finish the essential work items I have that are tied to the release this week. hopefully won't take long [18:11] I'll do an update if I have time [18:11] mdeslaur: you're up [18:12] I'm working at testing a couple of embargoed updates that will be published tomorrow, and will pick some stuff off the CVE list to fix next [18:12] I'm in the happy place this week, and that's it from me [18:12] sbeattie: you're up [18:13] I'm also in the happy place this week. [18:13] Working on finishing up the openssl and glibc updates I have on my plate === chrisccoulson2 is now known as chrisccoulson [18:13] I'll also peek at my work items [18:13] that's pretty much it for me. [18:14] micahg: ? [18:14] I'm trying to get a new chromium in precise before alpha2 (unfortunately, just i386 and amd64 ATM), it's Mozilla release week, so we'll be updating all releases to Firefox 10 [18:15] Rapid release migration was finished last week \o/ [18:15] \o/ [18:15] at least for Firefox :), we're considering doing thunderbird during the 10 timeframe though as well [18:15] \o/ [18:15] I think that's it for me [18:15] * jdstrand hugs micahg [18:16] micahg: did we get any major issues, or did everything go smoothly? [18:16] I know that was not the easiest thing, but hopefully now things will get better on the mozilla front [18:16] mdeslaur: mostly smoothly, we missed promoting a lot of stuff [18:16] and there's an ubufox upgrade bug from the stable PPA to the archive which I'll fix when we push out 10 [18:16] micahg: ok, minor things...good job! [18:17] I'm in the triage role this week [18:17] yeah, we caught the larger regressions in -proposed :) [18:17] micahg: nice job [18:17] anecdotally, lucid users I know had no issues [18:18] tyhicks: sorry, please proceed [18:18] no problem :) [18:18] I'm in the triage role [18:18] I'll be working on triaging the CVE's that jdstrand mentioned above [18:19] I didn't get to my update queue like I had planned last week, due to some work items stealing focus, but I completed those and I will focus on my update queue this week [18:20] That's it for me - jjohansen? [18:20] jjohansen is out today [18:20] I know he is working hard on work items and updates as they come up [18:21] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [18:21] 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. [18:21] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/ocrodjvu.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/libspring-security-2.0-java.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/hammerhead.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/ziproxy.html [18:21] http://people.canonical.com/~ubuntu-security/cve/pkg/smbind.html [18:21] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [18:22] Does anyone have any other questions or items to discuss? [18:23] hi [18:24] kalimojo: hi. this is the weekly ubuntu-security meeting. do you have something to discuss with us? [18:24] i was looking for help on image editing sw [18:25] kalimojo: you would probably want #ubuntu on Freenode [18:25] ok [18:26] mdeslaur, sbeattie, micahg, tyhicks: thanks! [18:26] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [18:26] Meeting ended Mon Jan 30 18:26:10 2012 UTC. [18:26] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-30-18.05.moin.txt [18:26] thanks, jdstrand [18:26] jdstrand: thanks! [18:26] thanks jdstrand! [18:26] quit [18:59] hello everyone [19:00] 1 minute still :) [19:00] * stgraber waves [19:00] hi stgraber [19:01] hi [19:01] micahg, tumbleweed, bdrung, Laney, cody-somerville: ping [19:01] o/ [19:01] o/ [19:01] * tumbleweed was deep in code and almost forgot [19:01] #startmeeting Ubuntu Developer Membership Board meeting [19:01] Meeting started Mon Jan 30 19:01:56 2012 UTC. The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [19:01] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Developer Membership Board meeting Meeting | Current topic: [19:02] Hi [19:02] agenda: https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [19:02] #topic Review of previous action items === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Developer Membership Board meeting Meeting | Current topic: Review of previous action items [19:03] so as you probably noticed, after discussion with the TB, I (with my TB hat on) updated the expiry for the DMB members terms based on what was sent by e-mail to the TB [19:03] this should be a lot more consistent now than it was before and should make renewing the board easier [19:03] cody-somerville: and news on your action or should we keep it there? [19:03] (cody-somerville to write some documentation on how to endorse someone) [19:04] Nothing new to report. Forgot to get around to it last meeting. [19:04] * cody-somerville writes it at the top of his todo list in big letters. [19:04] #topic Package Sets - Ubuntu One === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Developer Membership Board meeting Meeting | Current topic: Package Sets - Ubuntu One [19:04] proposal: https://wiki.ubuntu.com/RodneyDawes/UbuntuOnePackageSetApplication [19:05] Is Rodney here? [19:05] hi [19:06] dobey, Hi. Can you introduce yourself and your proposal? [19:06] I'm failing to see rhythmbox-ubuntuone in the archive (under either name listed on the wiki) [19:07] hi, i'm rodney dawes, on the ubuntu one team, and have been uploading several ubuntu one packages. we want to hae a package set to make it easier to manage the packages we have in ubuntu. [19:07] stgraber: it was dropped in oneiric, and we will have a release of it tomorrow, which should be going back into precise as rhythmbox-ubuntuone [19:08] dobey: ok, for the record we can't give access to non-existing source packages, so if the package set is approved, you'll have to send an e-mail to devel-permissions asking for rhythmbox-ubuntuone to be added once it's in the archive (no extra meeting needed for that kind of change though) [19:08] stgraber: ok, that is fine. [19:09] should be magicicada in the package set? [19:09] bdrung, no, thank you, magicicada is a non official project [19:09] bdrung: no, it's not an official ubuntu one package, and is a side project for a couple of the developers [19:10] k [19:10] dobey: that doesn't technically matter whether it's official or not if it should be part of the packageset, but rather if U1 devs might need to make changes to it and are trusted to do so [19:11] micahg: sure. if nessita wants it added to the package set then we can add it, i suppose. but i'll leave that up to her as it's her project. [19:11] do we have a description of the proposed package set? [19:11] micahg, thanks for the clarification. The devs involved in magicicada would like not to be part of that package set [19:12] bdrung: beyond what is in the proposal? [19:12] bdrung: not that I can find (either on the wiki or mailing-list) [19:13] dobey: this is the criteria for which we can add new packages based on e-mails to devel-permissions [19:13] dobey: when creating a package set we now require a description of the package set that will be used as criteria for inclusion of additional packages [19:13] dobey: anything matching that description will be added to the package set without the need for a meeting [19:13] stgraber: ah. i wasn't able to find any formal documentation on the wiki on applying for a package set. i just found an old application for bzr, and used it as a template. :-/ [19:14] proposed description: "The package set includes those packages that run in the user ubuntu desktop, and is part of the Ubuntu One project (http://launchpad.net/ubuntuone)" [19:15] dobey: https://wiki.ubuntu.com/UbuntuDevelopers#FormingDelegate [19:15] so, let's say "Packages for which Ubuntu One developers will generally need to have upload privileges for, assuming they have been approved by the DMB." [19:15] nessita: it's more a criteria for packages rather than a description [19:16] micahg: though "Packages that are part of http://launchpad.net/ubuntuone and in the Ubuntu archive" sounds like it'd match and is easy enough to check [19:17] tumbleweed: ah, confusion. i was looking at that before, and micahg was saying "what you need is a package set, not a delegated team" and when i searched for "package set" on the wiki, i got no useful results beyond the old bzr application :-/ [19:17] meh, some of those seem iffy, like evo-couchdb [19:18] tumbleweed: perhaps we could clarify that messaging somewhat :) [19:18] micahg, "The package X should be part of the package set if is part of the Ubuntu One project and runs in the ubuntu desktop"? [19:19] suggestion: "Packages from subprojects of http://launchpad.net/ubuntuone that are in the Ubuntu archive" [19:19] micahg: i'd say that's only iffy because we will stop supporting it, and probably won't be uploading it anyway. though in the future we'll probably have an evolution-u1db or something to replace it :) [19:19] nessita: "runs in the ubuntu desktop" doesn't really mean anything, at least not anything we can check. Does run mean doesn't crash, does it mean is seeded in a supported seed, does it mean, it's on a media, ... [19:19] bdrung: +1 [19:19] bdrung: wfm. [19:19] well, I guess if they can break some parts of the desktop, what's a few more :P [19:20] and I guess they are technically upstream for it [19:20] stgraber, right, I was referring to "live" in the ubuntu archive, like bdrung says [19:21] nessita: ok, that sounds good and is easy to check (as if the package wasn't we couldn't grant you upload rights to it anyway ;)) [19:21] :-) [19:21] we probably could reduce the criteria to "Packages from subprojects of http://launchpad.net/ubuntuone" [19:21] the package needs to be in the ubuntu archive anyway [19:21] bdrung: indeed [19:21] are we ready to vote? [19:21] sure [19:23] stgraber: with the proposed criteria? [19:23] bdrung: yes, package list that's on the wiki minus rhythmbox-ubuntuone and with "Packages from subprojects of http://launchpad.net/ubuntuone" as criteria [19:23] i am ready [19:24] micahg, tumbleweed, Laney, cody-somerville: ? [19:24] * micahg too [19:24] sure [19:24] #vote Creation of an UbuntuOne package set with https://wiki.ubuntu.com/RodneyDawes/UbuntuOnePackageSetApplication as initial list (minus rhythmbox-ubuntuone) and "Packages from subprojects of http://launchpad.net/ubuntuone" as criteria [19:24] Please vote on: Creation of an UbuntuOne package set with https://wiki.ubuntu.com/RodneyDawes/UbuntuOnePackageSetApplication as initial list (minus rhythmbox-ubuntuone) and "Packages from subprojects of http://launchpad.net/ubuntuone" as criteria [19:24] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [19:25] +1 [19:25] +1 received from bdrung [19:25] +1 [19:25] +1 received from micahg [19:25] +1 [19:25] +1 received from tumbleweed [19:25] +1 [19:25] +1 received from stgraber [19:25] +1 [19:25] +1 received from cody-somerville [19:25] (for packages listed on wiki) [19:25] #endvote [19:25] Voting ended on: Creation of an UbuntuOne package set with https://wiki.ubuntu.com/RodneyDawes/UbuntuOnePackageSetApplication as initial list (minus rhythmbox-ubuntuone) and "Packages from subprojects of http://launchpad.net/ubuntuone" as criteria [19:25] Votes for:5 Votes against:0 Abstentions:0 [19:25] Motion carried [19:25] ok, I'll create the package set post meeting [19:25] nice! [19:25] yay, thanks guys :) [19:25] yeeps, off by one error [19:25] #action stgraber to create the UbuntuOne package set [19:25] ACTION: stgraber to create the UbuntuOne package set [19:26] which is impressive when you are in gmt [19:26] Laney: hey there :) [19:26] #topic PerPackageUploader Applications - Natalia Bidart === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu Developer Membership Board meeting Meeting | Current topic: PerPackageUploader Applications - Natalia Bidart [19:27] (I guess we'll need to vote on dobey too as it doesn't make much sense to keep him on PPU now that we have the package set) [19:27] * nessita is Natalia Bidart [19:27] nessita: can you quickly introduce yourself? [19:27] sure! [19:28] hello, I'm natalia, I'm the teach lead of the Ubuntu One desktop+ team. I've been involved with most of the desktop application for Ubuntu One since 2010 [19:28] * stgraber notes we probably should convert nessita's PPU request to UbuntuOne packageset + PPU to magicicada [19:28] * bdrung nods [19:28] stgraber: indeed [19:29] nessita, How involved with the actual packaging of the UbuntuOne packages are you? [19:30] I've been packaging Ubuntu One packages since 2010, I started with the ubuntu-sso-client and then I included to my packaging list most of the rest of the project [19:30] I'm also familiar with the SRU process, and with all the release schedule [19:30] nessita, Can you give an example of where you fixed a packaging bug? [19:31] I'm still have some things to learn regarding packaging in general, but I'm always eager to read the documentation and to learn from reviews and advices [19:31] cody-somerville, you mean proposing a patch for the package or as a upstream dev? [19:32] nessita: are you subscribed to ubuntu-devel-announce and read it daily (when doing Ubuntu stuff)? [19:32] nessita, An example of fixing a bug with the packaging of the software vs. fixing a bug in the upstream software. [19:32] stgraber, yes, I am [19:32] cody-somerville: i suppose fixing [needspackaging] bugs counts for that? [19:33] * micahg would think not [19:34] cody-somerville, so, I have made some packaging fixes with, for example, logilab-common to upload to our Ubuntu One nightlies ppa (I can provide the link to that, let me find it) [19:35] cody-somerville, and this https://code.launchpad.net/~nataliabidart/ubuntu/precise/ubuntu-sso-client/ubuntu-sso-client-2.99.2 the latest package proposal I submitted with upstream fixes in it [19:35] nessita: the logilab-common is a code fix, not a packaging fix [19:35] dobey, I undertood that a packaging fix will be such where a patch is provied to apply to the source :-) [19:36] nessita: packaging being a bug in debian/rules or copyright, or typo in the description, or dependencies and such in the control file [19:36] nessita, No. That is different. A packaging fix is changes to the debian packaging files to fix an issue not with the software but with the packaging of it. [19:37] nessita: the difference between packaging a fix, and fixing the packaging itself :) [19:37] dobey, cody-somerville, right. I don't think I have done a packaging-only fix [19:37] most of my branches were for new upstream releases, or patch added to apply to the upstream code [19:37] nessita, How often do you make changes to files under debian/ ? How familiar are you with those files? [19:38] I've of course modified debian/ files in those, but I have not submitted a branch with only changes to debian/ [19:38] cody-somerville, I make changes every time I propose a packaging branch, I usually edit the changelog and very often update dependencies in the control file [19:39] nessita: are there any plans to get the ubuntuone stack to Debian or to work with Debian developers to get it into Debian? [19:39] cody-somerville: we have a hard release schedule for ubuntu one this cycle, so at a minimum of every 2 weeks, i would say nessita and i both, make changes under debian/ in the u1 packages. [19:40] cody-somerville, I'm familiar with the files in debian/, and I usually check the debian documentation when I have a particular doubt, and if needed, I also check with dobey or someone more experienced than me in that regard [19:40] I think cody-somerville is trying to highlight the difference between being an upstream dev and a distro dev [19:40] bdrung, well, atm there are no plans to getting Ubuntu One into debian [19:41] nessita: are there any reasons, why? [19:42] bdrung, well, mostly business desicions, but I'm confiming with my manager for specifics. Is worth noting that we help as much as we can to people that wants to contribute doing that (orpackaging to another distro as well) [19:43] nessita: the overhead to upload a package to debian and sync it to ubuntu isn't that big. [19:44] bdrung: configglue is already in debian. i hope to get dirspec in there in the future as well. as for the rest of ubuntuone, it might only be useful for us to have stuff in sid/experimental, but i don't think we are opposed to getting them there. [19:44] nessita, In what scenario might you need to bump the soname of the libubuntuone package? [19:45] cody-somerville, I'm not 100% sure (my work mainly involves python packaging, but is a good question), but makes sense doing so when there is an API-ABI breakage [19:46] dobey: sid/experimental are the primary upload targets in Debian [19:47] nessita, Who would you ask if you were unsure? [19:47] cody-somerville, dobey for sure :-) [19:47] cody-somerville, he's our packaging master, and a gnome dev [19:48] he thought me a lot of the things i know about packaging, and he also explains to me some sutil differences between one way or another to do things [19:48] any other question for nessita or are we ready to vote (for PPU to magicicada and package set upload for UbuntuOne)? (12 minutes left and we still have dobey and cyphermox on the agenda) [19:49] i am ready [19:49] I'm ready. [19:49] #vote nessita for PPU to magicicada and package set upload for UbuntuOne [19:49] Please vote on: nessita for PPU to magicicada and package set upload for UbuntuOne [19:49] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [19:50] +1 [19:50] +1 received from bdrung [19:50] +1 [19:50] +1 received from stgraber [19:51] +1 - please take some time to read the Debian Library Packaging guide plus seek assistance from dobey if you intend to touch libubuntuone. [19:51] +1 - please take some time to read the Debian Library Packaging guide plus seek assistance from dobey if you intend to touch libubuntuone. received from cody-somerville [19:51] +1 [ and please feel free to ask for help in #ubuntu-motu / -devel with tricky packaging issues, such as sonames ] [19:51] +1 [ and please feel free to ask for help in #ubuntu-motu / -devel with tricky packaging issues, such as sonames ] received from tumbleweed [19:51] micahg, Laney: ? [19:51] +1 same as comment as cody-somerville and tumbleweed [19:51] +1 same as comment as cody-somerville and tumbleweed received from micahg [19:51] ack to all comments, and will do [19:51] +1 also the release team for freeze guidance [19:51] +1 also the release team for freeze guidance received from Laney [19:52] #endvote [19:52]