=== asac_ is now known as asac === GunbladeIV is now known as GunbladeIV- === GunbladeIV- is now known as GunbladeIV-- === GunbladeIV-- is now known as GunbladeIV [10:55] Hello, everyone. [10:56] Hello [10:56] G'day... [10:57] I hope everyone's doing all right this 10:00 UTC. [10:58] * persia peers about [10:58] persia: morning [10:59] czajkowski, Good evening [11:00] elky, lifeless, TheMuso: All about? [11:00] yep [11:01] persia: Since I just joined the channel, and since I am never in here when I don't have to be... [11:01] hai [11:01] persia: lifeless: will highlight for me. lifeless, won't. [11:01] lifeless, o hai thar [11:01] Excellent. That provides not only clear quorum, but record of quirum. [11:02] I hear there is a meeting robot here. [11:02] lifeless, nifty. Is that specifically to get around the limits of my IRC client :) [11:02] Who wants to chair, as amachu can't make it? [11:03] persia does [11:03] #startmeeting [11:03] persia: its so that regular use of lifeless doesn't hightlight. [11:03] I would if I didn't have my head full of stuff that I need to dump to a file after the meeting. [11:03] * persia thinks there isn't a meeting robot around [11:04] Anyway: agenda: https://wiki.ubuntu.com/Membership/RegionalBoards/AsiaOceania [11:04] Only one person to review. [11:04] First up: Bryan Basil [11:04] yay, quick meeting [11:04] BslBryan, Could you introduce yourself? [11:04] * persia sees two applicants [11:04] that's still quick meeting. yay [11:04] Hello, everyone. :-) My name is Bryan Basil, and I believe that the best page to introduce me is my wiki page. [11:04] wiki.ubuntu.com/BslBryan [11:05] It details much of the contributions I have made to the Ubuntu community [11:05] as well as linking to all of them. [11:05] ...Or most of them anyway. :P [11:06] I have been left testimonials by ubuntu forums staff, as well as the LoCo president for US-GA. [11:06] And other people who have felt the need to leave a message. [11:06] I have really only been active online for a couple of months, [11:06] but my contributions thus far speak louder than words, [11:07] so, please, click around. :-) [11:08] BslBryan: Is there anybody here to speak about your work in the community/cheer lead for you? :) [11:08] Unfortunately, since it is 6 AM on a Tuesday here that no one could make it. [11:08] BslBryan, What brings you to this board? It must be an awkward hour for you there. [11:08] :-( [11:09] I saw that the American board had many applicants, [11:09] and still a meeting was TBD. [11:09] I figured it would be easier for all ubuntu members [11:09] if I just made a meeting a little shorter [11:09] while making one a little longer. [11:09] If it would make things easier, [11:09] Thats dedication for ya. :) [11:09] Haha. [11:09] Thanks. :-) [11:10] BslBryan, Can you talk in a bit more detail about your work with the Marketing team? [11:10] Sure. [11:11] I would like to first say that the reason that I did not speak much about it in my wiki page is because I am afraid that, to the community, my contributions in that team are all ideas. [11:11] I have, of course, spoken about Ubuntu to friends to switch them, but that team is more than that. [11:11] My work in the marketing team will concentrate entirely on advocacy to new users. [11:12] And, as I mention in my plans for the future, [11:12] I will most likely speak to the IT department at University [11:12] so you've contributed these ideas somewhere like irc or mailing list? [11:12] to make Linux more widely used. [11:12] This is correct. [11:13] I also plan on starting a university Ubuntu team, [11:13] seeing as several people on campus do use Ubuntu. [11:13] I would like to add, though, that I have not posted anything to their mailing list. [11:14] Ideas are just ideas, and I wanted to go [11:14] a little bit further with my plans to implement them before throwing them around to anyone else. [11:14] Soon, however. [11:15] BslBryan, i'm confused. have you contributed to the marketing team, or just joined the team on launchpad? [11:16] elky, I certainly have contributed to it, [11:16] but not directly. [11:16] I'm sure that sounds bad, [11:16] what did you contribute? [11:16] but let me explain. [11:17] I joined the Ubuntu marketing team because it explains what I have already done [11:17] for Ubuntu [11:17] as well as what I will do. [11:17] Considering I am a public speaker, [11:17] and a visual artist, [11:17] I found that many of the activities [11:17] done in the team is what I do today. [11:17] All I have yet to do is show my ideas to the team. [11:18] As well as repeat things I have already done. [11:18] Since that is sort of lame... :P [11:18] Or, sounding anyway, [11:18] I did not mention it much in my wiki. [11:18] I wanted to wait, [11:18] until my contribution to that team [11:18] was a little more pronounced. [11:18] But I truly believe that I am a member [11:18] of that team. [11:20] BslBryan, Just to make sure, Your current and planned future activities are part of the scope of the Marketing team, and you are a member of that team, but you have yet to do much interaction with other members of that team? [11:20] Who of the people testifiying are members, do we know? [11:20] Only Hellow [11:20] persie, yes. [11:20] persia, [11:20] (or at least as far as I could tell from hunting) [11:20] Jon Reagan [11:20] is up for [11:21] membership at the America meeting, but he [11:21] is the US-Georgia LoCo president, [11:21] and has been for 2 years (I believe.) [11:21] Also, wieman is ubuntu forums staff. [11:21] And Therion has made substantial contributions in the area [11:21] of support. [11:21] /c/c [11:21] I am certain he has a better chance of membership [11:22] than I do. [11:22] i'm not convinced. 0 from me. [11:22] elky, [11:22] may I say something? [11:22] wiki.ubuntu.com/Membership [11:23] Membership of the Ubuntu community means recognition of a significant and sustained contribution to Ubuntu and the Ubuntu community. Contributions in all areas are welcome, from support to advocacy, from programming to artwork and documentation, from LoCoTeams activities to core packaging. [11:23] Also, read the requirements. [11:23] yes, and i'm not convinced that your contribution is significant. [11:23] I trust your decision, but [11:23] have you seen my artwork? [11:23] My tutorials? [11:23] Read the one on merging partitions. [11:23] It took me hours. [11:23] I have 7000 in karma [11:24] from launchpad [11:24] from Spanish translations [11:24] and questions. [11:24] I have only been active for a little over 2 months [11:24] (which is the requirement) [11:24] and I believe I have [11:24] really done a lot for that time. [11:24] I have dedicated so much time and effort to Ubuntu. [11:24] And I promise that will not stop. [11:24] BslBryan, It's best not to argue the decisions of board members: you may end up hardening opinions. [11:25] Ah, sorry, that. :-) [11:25] BslBryan, In the worst case, if you're not approved today, you'll be asked to come back in a few weeks. [11:25] Okay. :-) I am still hoping, however. [11:25] BslBryan, So, you've written a bunch of HowTos. Have you thought about joining the documentation team? [11:26] Hmm. Perhaps. I suppose I haven't thought about it much. [11:27] May I move this topic to my artwork temporarily? [11:27] http://porfolio-bslbryan.webs.com/ [11:28] I'm +0.5 because: you've been very active. Very! And this has a tendency to be a flare kindof thing. [11:28] I'm on the fence, and give +0.5. Work on answers and in the beginner forums is *great*. Partitipation with the art team is to be commended. With a couple more member testimonials, some live fans, or documented work with the doc team or marketing team, I'd be +1. [11:28] you're doing great things. I'd like to see more follow through on teamwork with docs or marketing. [11:28] Thanks, persia. :-) [11:28] Lifeless. :-) [11:28] I am +0.5 as well. I feel you are spreading yourself a bit too thin. I think you should focus on one area and push hard to do lots of work in that area. [11:29] You will feel better knowing you are giving your best to your favourite part of the Ubuntu community. [11:29] You're probably right. [11:29] Thanks, everyone. :-) [11:29] TheMuso, would you suggest leaving my name on the American board? [11:30] BslBryan, You're doing great, but probably just need a bit more time and coordination. When you feel you've addressed the comments above, please apply again to any of the RMBs, and I'm sure you'll be approved. [11:30] Do you believe, personally, that I would be ready [11:30] by that time? [11:30] by what time [11:30] That's the point. The next meeting is still [11:30] BslBryan: I can't really answer that, since it comes down to when you can make their meetings. They may also look to see what our vote was, and decide based on that. [11:30] TBD [11:30] you said the us tz board meeting was TBD [11:30] so, it would probably be at least another couple of weeks. [11:31] * persia thinks it's better to take one's name down, and put it back up later, as the board will see this as active management of membership intention, rather than apathy. [11:31] Nice status, persia. :-) [11:31] Okay, then. Will do. [11:31] BslBryan, But don't expect a different set of questions or concerns from a different board. We all read each other's meeting logs. [11:31] No, of course. [11:32] Next up is Scott Evans [11:32] VK7HSE-Eee, Could you introduce yourself (again). [11:32] Hi, my name is Scott Evans, I first applied for Ubuntu Membership three months ago but I didn't have sufficient credentials to meet the requirements, I'm hoping that I do now, I'm actively involved as a moderator for the Ubuntu-au Mailing list. I've just recently introduced two friends to ubuntu although this is only a small contribution, I believe it is a start! If we all managed just one person each think of the [11:32] did all that text go through? [11:32] each think of the [11:32] hm, purple cuts off text. [11:33] where did it get cut off? [11:33] Hobbsee: same cut off here. [11:33] sorry for this [11:33] "each think of the" was the last text seen [11:34] I believe it is a start! If we all managed just one person each think of the numbers! I only have a small circle of friends and I have mention Ubuntu to those that I feel would either be interested or keen to give something new to try... (sorry the cat is of my lap! sorry if typing is slow) [11:34] ... IRC has a maximum line length of about 400 letters. [11:34] wish pidgin recognised that I'm sorry... [11:35] Sorry to interrupt. :) [11:35] persia: we do? [11:36] lifeless, At least someone from each board admitted to doing so at the RMB review two weeks back. [11:37] I have plenty of time that I can dedicate to the ubuntu-au loco as I'm currently not working (due to past illness) [11:38] I can't remember what your wiki page looked like last time, but I don't see any testimonials. [11:38] hmm, I should probably join the ubuntu-au list [11:38] VK7HSE-Eee: Have you done any packaging work with the MOTU community yet? [11:39] I have yet to find someone to speak on my behalf... [11:39] how busy is the list/ [11:39] not yey no.. only or theMe TV project... [11:39] you say you moderate it - is that 10s/100s/.../ of mails a day that need your time? [11:40] the ubuntu-au list see's more spam than active users, but [11:40] plus I'm not the sole moderator, [11:41] but as I'm regularly close to the PC I respond to the requests quickly.... [11:43] you've been doing this solidly for three months? [11:43] I realise that I may be recommended to pursue MOTU, but I've not made a firm decision on that just yet... [11:43] yes, since I was approved by elky [11:44] so, I'm +0.5. Sustained contribution, but not significant. [11:44] which was late march from memory. [11:44] Agreed with lifeless, +0.5 [11:44] well that better than my last application! [11:45] ;) [11:45] I'm +0 still, but for the same reasons (not significant yet). [11:46] VK7HSE-Eee: I suggest either diving deep into community or into tech [11:46] i'm +0 too. i'm not seeing a significant change from last time. [11:46] You can dive deeper into both, but it will take longer. [11:47] Ok well I thank you all for your time... I'll re asses and reconsider future applications... [11:47] VK7HSE-Eee: to be blunt, 16 bug reports touched, moderating a single list and getting two people involved is not that significant. [11:48] lifeless: That's one POV from many... ;) [11:48] VK7HSE-Eee, come and see me before you put your name down next time, please. [11:48] elky: ok... [11:48] VK7HSE-Eee, We truly would like to see you on the team, we just need more stuff. Since your last application you've taken on moderation of a mailing list, and expanded your beta testing a bit. That gets you from consensus -1 to consensus +0.25. You just have a bit farther to go. [11:49] persia: that's fine, this for me is part of the experience, to learn and evolve... [11:49] VK7HSE-Eee: We look for 2 key things: doing stuff long term, and doing 'significant' contributions, which is admittedly vague. And yes, my POV is one of many... [11:50] VK7HSE-Eee: but 'many' in this case is '4'. [11:50] VK7HSE-Eee: Like persia, I'd like to see you graduate to full member. [11:50] well that's concluded... once again I thank you for your time... [11:51] VK7HSE-Eee, Good luck with your progress. We'll see you back (after checking with elky) in September or so. [11:51] ok... [11:51] And that concludes our listed agenda items. [11:51] Anyone have anything else to raise? [11:51] nothing specific [11:52] no] [11:53] elky, TheMuso If you have time to respond to the outstanding ML thread regarding the nomination, that would be great. [11:53] I'll see what I can do about that either later tonight or tomorrow. [11:54] Alright then. Meeting adjourned [11:54] #endmeeting [11:56] I'm here to support BslBryan. [11:56] You're a little late. :-) [11:56] What? Why? [11:56] 10:54:26 < persia> Alright then. Meeting adjourned [11:56] 10:54:29 < persia> #endmeeting [11:57] The meeting was an hour ago, and recently adjourned, as you see. [11:57] Well, and that BslBryan was first on the agenda. [11:57] I'm sorry Bryan... [11:57] Haha, no worries. :-) Next time. === GatoLoko is now known as GatoLoko^ === Pici is now known as ZarroBoogs === ZarroBoogs is now known as Pici === beuno_ is now known as beuno === yofel_ is now known as yofel [16:00] hello [16:00] \o [16:00] o/ [16:00] yo [16:00] o/ [16:00] o/ === beuno__ is now known as beuno [16:01] good day folks! [16:01] let's get the server team meeting started [16:01] #startmeeting [16:01] o/ [16:01] o/ [16:02] Today's crazy agenda: https://wiki.ubuntu.com/ServerTeam/Meeting [16:02] What happened last week?? -> https://wiki.ubuntu.com/MeetingLogs/Server/20090602 [16:02] ttx: thanks for running the meeting last week [16:03] mathiaz: my pleasure [16:03] ttx: and preparing the minutes [16:03] Any actions from last week meeting? [16:03] I don't see any on the wiki page [16:03] did i miss the bugsquad meeting? [16:04] mathiaz: did you review new members applications, if any ? [16:04] that was an hidden implied action :) [16:04] pace_t_zulu: it's in one hour according to http://fridge.ubuntu.com/calendar [16:05] ttx: sure he did, i'm in :-) [16:05] ttx: new members application for the server team in LP? [16:05] alex_muntada: heh, welcome :) [16:05] mathiaz: yes [16:05] ttx: yes - I went through most of the applicate yesterday [16:05] *application* [16:05] mathiaz: thanks... i need to figure out UTC ;) [16:06] As of today there are 173 members of the ubuntu-server team in LP [16:06] pace_t_zulu: date -u will always give the UTC time [16:06] Anything else from last week meeting? [16:07] mathiaz: nothing from me [16:08] ok - let's move on [16:08] [TOPIC] Merges [16:08] so the development team is focusing on merging packages from debian [16:08] There are 104 outstanding merges in main [16:08] (https://merges.ubuntu.com/main.html) [16:09] and 196 outstanding merges in universe [16:09] (https://merges.ubuntu.com/universe.html) [16:10] For those of you that are interested in packageing and already have a bit of knowledge of packaging pick one package out of the list and work on a merge [16:10] once you've got something file a bug in LP and ask for sponsorship === pgraner_ is now known as pgraner-afk [16:10] I'll publish another list of packages that look easy to merge [16:11] [ACTION] mathiaz to update the list of easy-merges for the Server team [16:11] If you have any questions about the merge process or packaging in general, stop by #ubuntu-motu or #ubuntu-devel [16:11] Any questions about Merges? [16:12] mathiaz, related to that, would you be able to sponsor openvpn please? bug #372358 [16:12] Launchpad bug 372358 in openvpn "Please merge openvpn 2.1~rc15-1 (main) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/372358 [16:12] RoAkSoAx: It's on my TODO list - I'll have a look at it [16:12] mathiaz, cool thank you :) [16:13] RoAkSoAx: sorry for not processing earlier - I was busy with UDS [16:13] mathiaz, np :) [16:14] mathiaz: i'll pick one from the list once it's been updated, it'll be my first merge [16:14] alex_muntada: great - I'll publish it in the Roadmap wiki page [16:14] https://wiki.ubuntu.com/ServerTeam/Roadmap [16:14] yeah, I'm already subscribed ;-) [16:15] If there isn't anything else related to Merges, let's move on [16:16] [TOPIC] Karmic Alpha2 [16:16] is there a city that is always in UTC? [16:16] pace_t_zulu: no [16:16] So we're gearing up for the next milestone release [16:16] alpha2 is scheduled for Thursday [16:17] The archive is still soft-frozen until then [16:17] so hold on to your upload unless they fix a blocker for alpha2 [16:17] That also means iso testing will be required in the coming days [16:17] as we're responsible for testing the ubuntu-server iso [16:18] iso candidates will be posted to http://iso.qa.ubuntu.com/ once ready [16:18] so if you wanna help out testing the isos, subscribe to the Server amd64 and i386 test cases [16:19] and you'll get automatically notified when new candidates are available for testing [16:19] pace_t_zulu: Reykjavik, Iceland. [16:19] stop by #ubuntu-testing to follow what's going on [16:20] Testcases for ubuntu-server isos are described on the testcase wiki: [16:20] http://testcases.qa.ubuntu.com/Install/ServerWhole [16:21] http://testcases.qa.ubuntu.com/Install/ [16:21] Any help in conducting the test cases and reporting results to the Iso tracker is welcome [16:22] Any questions wrt to Alpha2 and/or the iso testing process? [16:24] nope - let's move on [16:25] [TOPIC] Drafting specifications [16:25] According to the KarmicReleaseSchedule: https://wiki.ubuntu.com/KarmicReleaseSchedule [16:25] Specifications should be finalized this week in time for FeatureDefinitionFreeze [16:26] So how is everyone doing wrt to their specification draft? [16:26] :-)... but mines pretty easy [16:26] mathiaz: it will be a busy week :) [16:27] I've started to write down notes on the session I lead at UDS [16:27] * soren is doing ok [16:27] Thanks for asking :) [16:27] sommer: Thanks for taking notes - they're precious while writting down things [16:28] soren: that's because you're a born drafter. [16:28] mathiaz: np [16:28] ttx: HAHAHAHAHHAHAHHAHAH! [16:28] ttx: Good one. I get it :) [16:28] I've already written down some draft for the directory related sessions: [16:28] https://wiki.ubuntu.com/NetworkDirectoryArchitecture [16:28] https://wiki.ubuntu.com/NetworkDirectoryUserLogin [16:29] Although they're not in a final state yet, feedback/comments on them is welcome :) [16:31] Any questions on the specification draft process? [16:32] nope - let's move on. [16:33] [TOPIC] Open discussion [16:33] anyone? [16:33] mathiaz: is it where we discuss the "New members integration" topic ? [16:33] ttx: sure [16:34] ttx: open discussion is when there is nothing left on the agenda or on my topic to discuss list [16:34] mathiaz: well, that topic was on the agenda ;) [16:34] ttx: hm - you are right [16:34] Last week we had so many new heads around, I thought there was a need to explain the different areas of contribution [16:35] I missread the Agenda [16:35] so taht newcomers could tell us where they think they would best fit [16:35] ttx: good idea [16:35] mathiaz: could you detail the different types of server team actions ? [16:36] or should I ? [16:36] the GettingInvolved page has a list of different roles: [16:36] https://wiki.ubuntu.com/ServerTeam/GettingInvolved [16:36] Help on the mailing list and the IRC channel [16:37] The helpers answers questions on the ubuntu-server mailing list, the #ubuntu-server irc channel and the server forums. [16:37] Triagers dig into bugs the ubuntu-server LP team is subscribed to. [16:37] Our LP team is a bug contact for a list packages, such as samba, openldap, mysql or apache2. [16:37] he current list of packages can be found in Launchpad (https://bugs.launchpad.net/~ubuntu-server/+packagebugs) and is growing every release. [16:37] hm, we lost like 75% of our new heads in one week :) [16:38] :-D [16:38] Once bugs have been triaged, it's time to fix them. This is when the packagers come into the game. [16:38] This role requires an interest in packaging. [16:38] We maintain a list of bugs that are easy to fix: https://bugs.launchpad.net/~ubuntu-server/+mentoring [16:38] Fixes can make their way into the ubuntu repositories via the sponsorship process as described in the wiki page https://wiki.ubuntu.com/SponsorshipProcess [16:38] Doing work on the packaging front leads to a close a collaboration with the MOTU team and is a great way to gain experience to become a MOTU - https://wiki.ubuntu.com/MOTU [16:39] Testing is another way to take part of the Server Team activity. This role doesn't require a lot of deep technical knowledge. [16:39] Browsing the ubuntu-server mailing list archive, lurking in the #ubuntu-server irc channel or going through the forum posts shows patterns in user's questions. [16:39] Recurring themes are identified and turned into documentation. A wiki page in the community section of help.ubuntu.com is first created. Once the quality has improved, a new section is added to the server guide. [16:39] All this work is undertaken by the Documentors of the Server Team. [16:40] Adam Sommer (sommer) leads the update and review of the Ubuntu Server guide. The source document is maintained in a bzr tree. Helping Adam will introduce you to docbook and distributed versioning with bazaar. [16:40] * sommer \o/ [16:40] So these are the different roles one can take to get started with the Server team [16:40] support, bug triage, packaging, documentation [16:41] there are other ways to get involved but these are the main ones. [16:41] Most of the information related to the ServerTeam can be found in the ServerTeam wiki pages: https://wiki.ubuntu.com/ServerTeam. [16:41] If you're overwhelmed by all the available information and you're lost, come talk to me. You can find me in #ubuntu-server amongst other channels. I'll help get out of the mist and we'll find a way you can get involved in the Server Team. [16:42] Any questions? [16:42] alex_muntada: is it clear ? do you see where you would best fit ? [16:43] ttx: I think I'll start with a bit of support, triaging and testing maybe packaging and documenting a bit later [16:43] alex_muntada: sounds great ! [16:44] great [16:44] there's a lot of stuff to learn, I'll start slowly ;-) [16:44] any other questions? [16:45] I do have something to report: Regarding to the Ubuntu-HA team... Debian has already Heartbeat 2.99.3 in experimental. That is one of the packages we want in Ubuntu, along with pacemaker and openais. However it is not a good idea to sync it from Debian yet, right? I've uploaded it to my PPA though, so that I can start doing some testing. [16:45] be it related to getting started or anything else *somehow* related to the Server team [16:45] RoAkSoAx: which version is in unstable for now? [16:46] mathiaz, same as the one in Ubuntu 2.1.4 [16:46] RoAkSoAx: why the version in experimental should be pulled in instead of unstable? [16:46] mathiaz, Heartbeat from 2.99.x and up now uses Pacemaker as the Cluster Resource Manager [16:47] RoAkSoAx: is 2.99 stable according to upstream? [16:47] mathiaz, and it's recommended by upstream to use Pacemaker from now on [16:47] RoAkSoAx: or is it just a beta that in time will become 3.0 (as the versionning seems to suggest) [16:47] RoAkSoAx: ? [16:47] mathiaz, yes it will become 3.0 [16:48] RoAkSoAx: so would you use 2.99 in a production environment? [16:48] in the talk I had with horms, he pretty much told me that those packages where going to debian experimental for final testing.. and if they passed the tests, they were going to sid as stable [16:49] mathiaz, they have also settled a debian-ha team to handle this packages [16:49] RoAkSoAx: horms is the debian maintainer? [16:49] mathiaz, yes [16:50] RoAkSoAx: what's the timeline for getting 2.99 in unstable? [16:50] mathiaz, I actually don't know yet. I'll talk to him about that... though he told me it was a big transition getting the code out of heartbeat and leave it in Pacemaker [16:50] so they were requiring testing [16:52] RoAkSoAx: ok - it seems that the version in ubuntu doesn't have any change [16:52] RoAkSoAx: so if hearbeat hits unstable, it will be pulled in ubuntu automatically before DebianImportFreeze [16:53] (which happens end of June) [16:53] mathiaz, stable debian version and ubuntu version are the same. the Cluster Resource Manager code has been removed from Heartbeat since 2.99.x , and it now uses Pacemaker as the CRM [16:53] RoAkSoAx: right [16:53] So it seems that testing is what's required for now [16:54] mathiaz, yes, and that's on my ToDo list :) [16:54] RoAkSoAx: Have you uploaded the experimental package to a PPA? [16:55] mathiaz, yes it is on my PPA: https://launchpad.net/~andreserl/+archive/ppa I'll start testing and provide a testing case and then call for help [16:55] RoAkSoAx: seems like a good plan to me [16:55] RoAkSoAx: using the ubuntu-ha team to call for testing and a blog post [16:55] indeed [16:56] allright anything else before we wrap up? [16:56] not from me [16:56] [ACTION] RoAkSoAx to write a test case for heartbeat [16:56] [ACTION] RoAkSoAx to write a blog post for a call for testing heartbeat 2.99 from a PPA [16:57] [TOPIC] # Agree on next meeting date and time. [16:57] Next week, same place, same time? [16:57] sure [16:58] all right then [16:58] see you all next week, same place, same time [16:58] happy iso testing [16:58] and merges [16:58] ... and specs... [16:59] see you all around [16:59] #endmeeting [16:59] coolio, thanks mathiaz [17:00] hey ya! [17:00] hi [17:00] so, who runs these meetings? :P [17:00] last time was me! [17:00] * bcurtiswx-mini sits down then [17:01] so if anyone steps up, i can try it for the second time [17:01] hey everyone. [17:01] * BUGabundo waves [17:01] o/ [17:01] Hi [17:01] \o/ whats that supposed to be [17:01] ok, let's start this [17:01] 1st time on this meeting so be gentle. thanks [17:01] (i supposed me waving :) [17:01] i got yelled at when i wasn't here last time :P [17:01] #startmeeting [17:01] * charlie-tca waves [17:01] heya [17:02] o/ [17:02] holly gosh, shouldn't the bot respond to startmeeting? [17:02] idk, didn't for the server meeting [17:02] [17:02] mootbot is MIA [17:02] ok. [17:03] it should, but maybe it is broke again [17:03] ok, np. So this is our second meeting, and the proposed topic is at [17:03] https://wiki.ubuntu.com/BugSquad/Meeting [17:03] and the last minutes from the previous meeting are at [17:03] https://wiki.ubuntu.com/BugSquad/Meeting/Minutes/2009-12-05 [17:04] first my apologies for emailing too late the reminder to the ML.. it didn{ t make it into the the newsletter, but anyway we're here so let's start === jussi01 is now known as jussio1 === jussio1 is now known as Android [17:05] [TOPIC] UDS BugSquad related topics -- BugSquad UDS atteendes === Android is now known as Tuhina [17:06] anyone of the attendes want to share some of the highlits from UDS related to bugsquad? === Tuhina is now known as jussi01 [17:06] * bcurtiswx-mini pokes maco [17:07] well i know maco went to UDS.. but i think shes @ work [17:08] or school [17:08] anyone else? [17:08] There were quite a few things I found interesting [17:09] making the greasemonkey triaging scripts into extensions and available in a PPA [17:09] a Bug Squad mentoring program [17:09] an Ubuntu Reviewers team for patches attached to bug reports [17:10] and some discussions about how to write apport package hooks and what packages to target [17:10] to the Bug Squad mentoring program... i think we mentor each other in the bugs channel pretty well [17:10] how would a mentoring program be different? [17:11] We talked about making it a bit more structured to make it easier for people to find a mentor and to help people are who are shy. [17:11] bdmurray: this is the spec right? https://wiki.ubuntu.com/QATeam/Specs/SpecialisationWithinBugcontrol [17:12] andresmujica: that's right [17:12] pedro_: anything more to add on that? [17:13] i like the idea, i just ask a ton of questions :). how can i help build the spec up.. i can come up with a few ideas [17:13] well what bdmurray said is mostly why we started to do the mentoring program [17:13] that's based on the experience of previous months/years [17:14] we clearly need a more defined and structured way to start helping new triagers who want to be involved in the bugsquad [17:14] doing triage, participating in our activities, meetings, decisions, etc [17:14] agreed [17:14] bcurtiswx-mini: we are still drafting the spec at this point in time [17:14] the bugsquad is not just about doing triage and that's it, people need to get involved in the team as well [17:15] bdmurray: understood, i would love to help build this "program" up [17:15] i' ve got a doubt about bugsquad membership, it would be open for everyone or it was decided to ask for some prereq ? [17:15] bcurtiswx-mini: great! feel free to add any thoughts to the end of the Discussion section of the spec [17:17] andresmujica: IIRC we agreed on having it now as a close team and the requirements for join there would be: sign the coc and read the how to triage guide [17:17] I think we should talk about that a wee bit more, the 1st item is easy to verify the second hard. [17:18] similar to bug control... they e-mail the list answering pre-made questions about the triage guide ? [17:18] yeap, maybe some questions as bug-control application [17:18] right, maybe we could ask a few easy questions related to that guide [17:19] At least that would let them know the guides exist. [17:19] I think that would add a lot overhead and might lean the other way [17:20] verify coc is signed, approve and in approval notification send links to triaging documentation and mentoring program [17:20] bdmurray: ok, what about a "trial" period, like bug control [17:21] after 90 days ping a bug squad admin to update the membership [17:21] sounds good to me [17:21] and check bugs triaged in that period [17:22] I think that'd be part of the mentoring program [17:22] should a new member must have a mentor? [17:22] No, I don't think so [17:23] so , by request, a mentor? [17:24] If I understand correctly - new members could request a mentor yes [17:24] But it would not be required [17:24] i think it may be help to have bug squad newbies build up their wiki pages and review that upon 90 days are up [17:25] put a couple triaged bugs in there? [17:26] We make them do that to join bug-control, I would think to stay in bug-squad it should not be the same. [17:26] Reviewing the bug control applications takes a lot of time, but maybe we can make a streamlined simplified process for the Bug Squad [17:27] charlie-tca: I agree [17:27] the point is that bugsquad needs a lot of members that can do a good triage work, so with mentoring and some commitment to be members they can grow and get more involvement. [17:27] Anyway, we can discuss this more in the spec / on the mailing list [17:27] yeap. [17:27] perhaps one way is to have mentors assigned to newbies [17:28] b.g.o does something similar, at least with evo [17:28] there were some more topics at uds that worth mentioning, kernel bug handling, Desktop Bug workflow and Symptom based bug reporting [17:29] I think mentoring helped me get acclimated faster [17:30] as the mentoring program is so new and it's a volunteer work, i believe we can let it move and it would reacht the point were new members can be assigned to a mentor.. [17:31] if needed.. [17:31] Right, I've some concern about the quantity of mentees versus mentors [17:32] ask for volunteers in the two ML's ? its going to be difficult to coordinate best times to meet too.. since were from all around the world [17:32] i'd recommend assigning people from the same time zones.. or close time zones [17:33] bcurtiswx-mini: that's the idea, yes [17:33] the issue is mentoring is a voluntary action, right now. We, er, mentor by answering questions on IRC. Perhaps stress IRC presence? [17:34] ok, as the time moves, i'd propose to discuss that remaining points in the ML, and as the spec is being drafted it surely can be greatly improved. [17:34] hggdh: +1 [17:35] about the kernel bug handling, i believe it's important to note that a bug bankrupcy was discussed, as the high volume of kernel bugs (around 5000) is really hard to manage, and is not feasible to triage them all and solved [17:36] 5k? [17:36] https://wiki.ubuntu.com/specs/KernelKarmicBugHandling [17:36] https://bugs.launchpad.net/ubuntu/+source/linux [17:36] that's what the kernel team gets for prefering to have all kernel bug filed in separate [17:36] so the kernel team is discussing what should be the best path of action... [17:37] well, I"m sure that at least 20% are from old kernels if not more [17:37] yeap, [17:38] so. What can we do about that? [17:38] I would suggest getting rid of any bug not touched before hardy was released [17:38] kernel hug day? [17:39] just mark invalid [17:39] probably be aware of the issue and check the kernel bug policies page https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies [17:39] in case someone has a real issue, they can reopend [17:39] I'd rather people focus on kernel bugs coming in today, tomorrow, the next day, rather than the old crufty stuff [17:39] micahg: what would you do with dapper, which is still supported on servers for two years? [17:40] bcurtiswx-mini: the team is organizing kernel hug days almost every Tuesday since a few weeks ago: https://wiki.ubuntu.com/KernelTeam/BugDay [17:40] charlie-tca: it doesn't even show up in the versions provided [17:40] in fact there's one today [17:40] That makes it more wrong, then [17:40] pedro_: maybe have them announced on the bug squad list? [17:41] http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090609.html [17:41] charlie-tca: the dapper bugs are reported about linux-source-2.6.15 [17:41] unless a dapper bug is an omg kittens are dieing or a security fix it's likely Won't Fix [17:42] bdmurray: my point was you can't just invalid a bug because it is before hardy. It could be valid against dapper [17:42] and the kernel bug day announcement was sent to ubuntu-qa, ubuntu-bugcontrol, kernel-team, and ubuntu-bugsquad [17:42] ogasawara, then we *could* close these as wont fix, correct? [17:42] hggdh: in my opinion, yes [17:43] OK. Anyone against? [17:43] thanks for clearing that, ogasawara [17:43] Again I think closing old bugs is less useful than triaging new bugs [17:43] some magic script can do it instead of us.. [17:43] as for closing old stale kernel bugs, I've got some scripts I'm going to run to clear them out [17:43] bdmurray, I agree, but there's still the reporter needing some sort of ACK [17:44] hggdh: just one Q: how about those that remain past the old release, and are not identified as such ? [17:44] bdmurray: I agree also, but it can be mentally disheartening to see such a large number of bugs in a package and never seem to make decent headway [17:44] BUGabundo, this is actually a question of quantity vs quality. There is only so much we can do [17:45] I know [17:45] True but it'd be better for the release as a whole if we worked with the "live" bug reports and work on getting those fixed [17:45] and a nicely written automagic script can tell the reporter to reopen if needed [17:46] I guess the closing message could/will ask the subscribers to reopen if they persist [17:46] indeed bdmurray, I don't think anyone is disagreeing with that [17:46] +1. I understand ogasawara will run his magic on the old bugs [17:47] btw, I just ran a search for dapper in the linux package and came up with 144 bugs [17:47] ogasawara, sorry. *her* magic. [17:48] hggdh: :) [17:48] for those interested in helping triage, I recently updated the https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies [17:49] OT - Just got a compliment on the apport-collect command from a user [17:49] note the added importance of having bugs test with the mainline kernel build as well [17:49] ogasawara: is that in the "debugging proceedures" page? [17:49] bcurtiswx-mini: I'll have to check. if not I'll add it. [17:49] The DebuggingProcedures page could use some reorganizing [17:50] yeah, and additions [17:50] bcurtiswx-mini: additions as in links to existing pages or new pages added? [17:51] another interesting discussion held at UDS was the Symptom Based Bug Reporting https://wiki.ubuntu.com/DesktopTeam/Specs/Karmic/SymptomBasedBugReporting, that would be an extension to apport hooks that would try to get some common information about the issue by asking questions to the reporter... mr pitti is working on that ... [17:51] andresmujica: he blogged about it today or yesterday [17:52] bdmurray: well, idk of all the wiki pages we have on debugging this and that. but the list seems small from the different amount of packages we have.. so if i don't find a debugging page, i resort to finding basic triage info.. and i am afraid its not enough for devs and to mark as triaged [17:52] oh, that was the interactive hook [17:53] ohh, that's great!! http://martinpitt.wordpress.com/2009/06/08/interrogation-with-apport-hooks-qt-developer-needed/ [17:54] so, we've got 5 more minutes... [17:55] yay for going to the 2nd discussion topic :P, to which i have no info for anyways [17:55] LP Improvements for triagers -- bcurtiswx [17:55] hehe [17:56] that was more of a question, than a "i know this" thing [17:56] bcurtiswx-mini: well, we did have a meeting with the launchpad bugs team at UDS [17:56] there were some talks about it at UDS... duplicate bug handling, related bugs, what else? [17:56] some of the things we talked about were negated tag searching, bug nominations [17:56] bdmurray: about that greasemonkey made FF extension.. sounds like a great idea [17:57] searching for bugs with bzr branches, displaying patches in bug listings [17:57] what about running apport collect on all bugs reported against jaunty and karmic when reporters use the launchpad page to report [17:58] is that possible? [17:58] you mean forcing code on the local machine? [17:58] Instead we are trying to get people to just report bugs via ubuntu-bug / Report a Problem [17:58] * hggdh apriori is against [17:58] Additionally with the symptom based bug reporting this will make much more sense [17:58] hggdh: not forcing, lol.. you'd ask first and get their permission through a form [17:58] er, be much more beneficial [17:59] ok, time is rover... [17:59] [18:00] so, i' ll summarize to the mailing list.. [18:00] well, bdmurray suggested using the ML more... maybe a good idea ;-) since we've got tons to talk about still [18:00] yeap [18:00] hope it was benefical to every one! [18:00] thanks for the assistance [18:00] #endmeeting [18:01] #startmeeting [18:01] Kernel Weekly Meeting [18:01] * smb pops in [18:01] * cking here [18:01] Agenda for this weeks meeting: https://wiki.ubuntu.com/KernelTeam/Meeting [18:01] roll call! [18:01] Thanks, andresmujica, for chairing again [18:01] * jjohansen here [18:02] * ogasawara waves [18:02] evening all [18:02] [TOPIC] Open Action -- apw,smb,ogasawara arrange phone discussions on the bugs list [18:02] apw: done [18:02] we had a concall on this subject, we are going to leverage some helpers to drive triage [18:02] done \o/ [18:02] and we have refocused the triage effort on getting the fixes from upstream to pushed [18:02] upstream in general [18:02] indeed :) [18:02] [TOPIC] Open Action -- smb review the policy docs w.r.t. SRU and ensure they match the updated reality [18:02] I updated the spec with my understanding of the agreed changes. If all agree I w [18:02] ould go forward and update the SRU on the wiki. [18:02] have you sent that out to the mailing list? a reminder to read? [18:03] * lieb here [18:03] Npe, but will do [18:03] [ACTION] smb to get feedback on the SRU updates [18:03] [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb) [18:03] Dapper : same as last week [18:03] Hardy : New kernel and LRM have been accepted into proposed. Currently [18:03] checking the milestoned bugs for 8.04.3. Two of them need more [18:03] work. [18:03] Intrepid: New kernel and LRM accepted into proposed. LBM was missed but [18:03] uploaded today. [18:03] Jaunty : Has been in -proposed for 7 days now. Possibly move that to updates [18:03] to make way for the pending last stable update. [18:04] how long before jaunty moves do you think? [18:04] have we got a lot pending for jaunty after that batch? [18:04] is it slowing down there? [18:04] Yeah, I'll ask after the meeting [18:05] A bit with no more stable [18:05] But there are still a few on the mailing list i have to get to [18:05] i see we keep getting more regressions ... any feel for where they are coming from most, whcih series? [18:05] (i hate the number 18) [18:06] Probably just found under that pile [18:06] smb: indeed. likely recently tagged and fell on the radar. [18:07] And one by trying things on an UDS [18:07] we should probabally put together a breakdown of which releases are getting the regressions [18:07] if its jaunty mostly then i guess its as expected [18:07] [TOPIC] Karmic Status - Alpha-2 june 11th (apw) [18:07] karmic is at 2.6.30-rc8, the expected 2.6.30 release over the weekend did not materialise [18:07] given the dates we will keep 2.6.30-8.9 for the Alpha-2 release [18:07] starting to see the first regression-potential bugs and working those [18:08] [TOPIC] ARM Tree (bradf/amitk) [18:08] not sure if either of them are here. the only thing of which i am aware [18:08] brad is working on integrating patches for babbage 2 [18:09] is that the arm support in karmic is still out of sync with jaunty [18:09] apw: it is totally broken ATM [18:09] yeah it builds something, just no idea what [18:09] brad is looking at bring the jaunty patches forward and then add the new ones [18:09] ack [18:09] anything else? [18:09] thats about it [18:10] [TOPIC] LPIA Tree (sconklin) [18:10] not sure i've seen him today [18:10] put that on hold for this week [18:10] [TOPIC] Incoming Bugs (oggasawara) [18:10] Nothing to report - been busy with a fire drill. I need to rebase hardy netbook-lpia on top of stefan's proposed. [18:10] There were 2 regression-potential bugs for karmic and one regression-release bug for jaunty that I added to the buglist this week. [18:10] http://qa.ubuntu.com/reports/ogasawara/kernel-buglist.html [18:10] They've all been assigned to a kernel dev already. [18:11] or not. [18:11] sconklin, thanks [18:11] ogasawara, how is the bug day going [18:11] today's bug day is looking good so far - http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090609.html [18:11] I added delta's the the stats at the top so you can monitor progress. [18:11] You've already closed over 30% of them. [18:11] I also want to give a quick shout out to andresmujica who did a great job helping out the last kernel bugday and has again tackled a few from today's list. [18:11] \o/ [18:11] thanks andresmujica for that! [18:12] +1 [18:12] +1 [18:12] +1 [18:12] :) np glad to do it. learning a lot [18:12] we will make a community :) [18:12] apw: that's it for now [18:12] i plan to do bug fixing tomorrow, since i spent a whole with customers [18:12] cooloney, no problem [18:12] today [18:12] apw, thanks [18:12] [TOPIC] UDS Deliverables [18:12] should we be starting to track the UDS blueprints in this meeting once they are being implemented? [18:13] i think we probabally should be tracking those which are features being added [18:13] if people agree, i think we should begin with that for 'Started' ones from next week [18:13] anyone? [18:14] i'll take that one offline then [18:14] [TOPIC] Open discussion [18:14] anything anyone wants to bring up? [18:15] just fyi, I'm going to start some dry runs of the kernel arsenal triaging scripts [18:15] i guess not, we are pretty thin on the ground today [18:15] ogasawara, sounds good [18:15] got a projected live date for that lot? [18:16] apw: I'm hoping in a day or so we'll start on a live small subset of bugs [18:16] sound plan [18:16] anything else? [18:16] [TOPIC] Next Meeting Chair Selection [18:16] whos turn is it? [18:17] I could give it a try [18:17] jjohansen, you're it :) [18:17] unless anyone has anything else ... we're probabally done [18:17] sounds good to me [18:17] thanks all [18:17] #endmeeting [18:17] thanks [18:17] * apw slaps mootbot [18:18] useless [18:18] bye [18:20] thanks === Igorot is now known as Knightlust === kalon33 is now known as kalon33-eating === kalon33-eating is now known as kalon33_ === kalon33_ is now known as kalon33-sleeping === kalon33-sleeping is now known as kalon33-packagin === kalon33-packagin is now known as kalon33 === txwikinger_work is now known as txwikinger3 === txwikinger3 is now known as txwikinger_work === Moot2 is now known as MootBot === hggdh is now known as hggdh_ === hggdh_ is now known as hggdh__ === hggdh__ is now known as hggdh