=== tsimpson_ is now known as tsimpson === jporsini is now known as jfi_ [10:44] Hello, is there an IRC canal to get in touch with "ubuntu release team" ? [10:51] jfi_: you can reach some members of that team at #ubuntu-motu [10:51] acarpine, ok, thanks [10:52] jgi_: my pleasure! :) === Nafallo_ is now known as Nafallo [11:52] pedro_: i wanted to follow up on our work item from UDS regarding the bug squad mentoring and beginners team cooperation. [11:53] hello duanedesign! sure [11:56] pedro_, while you're here! [11:56] https://launchpad.net/~bugsquad-mentorship/+members#proposed <- :D :D [11:57] ikt, looking [11:58] ikt, did you send an application to the bugcontrol mailing list? [11:59] oh [12:00] I thought you had to have a mentor first, then they can pass you through to the bug control [12:00] when they feel you are ready [12:00] but that's ok, I'll make an app [12:01] ikt, thank you :-) [12:02] ^^ [12:03] top of the morning hggdh! [12:03] Good morning to you also, pedro_ :-) [12:09] hello hggdh [12:09] hggdh, we were talking with duanedesign about the Beginners Bugs team and the Mentoring program we have [12:10] one of the problems we've noticing with the mentoring program is the not a lot of new members replying and just joining the program probably just 'because' [12:11] so since the Beginners Bugs Team is also doing some work similar to the mentoring program (teaching people how to work with bugs) [12:11] what about if we add a 'little' extra step before joining the mentoring program [12:12] being that step: contact the Beginners Bugs Team and see if the bugs thing is for you or not [12:12] and if our Bugs Focus Group Members are also BUg Squad Mentors the contributors transition could be 'seamless' [12:12] so they can explain you what a bug is, some bugs status, really simple things [12:13] so new members can decide if they're interesting or not in Bugs and if they are they can join the Mentoring program [12:13] and we can explain to them the bugs work in more depth [12:14] hggdh, what do you think about it? [12:14] morning kamusin [12:14] hi duanedesign [12:14] pedro_: we do get a lot of people in the Beginners team who are, not quite sure where they want to contribute. [12:15] pedro_, duanedesign: I think it makes a lot of sense [12:15] pedro_: and we try and give them a brief introduction into the different areas [12:15] pedro_: so that kind of fits into this idea [12:15] duanedesign, awesome \o/! [12:16] I have been wondering if most people wanting to join really wants to join, or just to collect one more icon on their LP pages [12:16] good morning folks :) [12:16] kamusin: good morning! [12:21] pedro_: sounds really good. === om26er_ is now known as om26er [14:01] Hi! I just filed bug 735478 [14:01] alex_mayorga: Bug 735478 on http://launchpad.net/bugs/735478 is private [14:01] anything else I need to give? === ogra is now known as Guest56191 === Guest56191 is now known as ogra_ [16:32] the meeting is in 30mins right? [16:47] * evilvish stabs yofel in the meantime.. >.< [16:47] huh? [16:48] * yofel wonders what he did this time ^^ [16:48] yofel: just bored till the meeting, tisall ;) [16:48] lol :) [16:48] and he is evil after all [16:48] indeed === JayFo is now known as JFo [17:02] bdmurray: ping [17:02] meeting should have started? [17:02] * charlie-tca waves [17:04] where does the time go? [17:05] wish I knew [17:06] Okay, welcome everybody! [17:06] o/ [17:07] It's March 15th and time for the Bug Squad Meeting [17:07] The agenda is at https://wiki.ubuntu.com/BugSquad/Meeting [17:08] First off we had a couple of action items from the last meeting [17:08] Brian Murray to clean up regression-potential tagged bug reports [17:08] I've done this! [17:08] o/ [17:09] why are we removing regression-potential tags ? I seem to have missed this discussion.. [17:09] they were replaced by 'regression-release ' [17:09] oh! cool.. [17:10] looong time ago, too [17:10] well or they were replaced by regression-release and should also have a release tag [17:10] yea, i always wanted to ask but kept forgetting :) [17:11] but what about the bugs discovered during alpha/beta? [17:11] The apport kernel hook for Maverick still tags some regression-potential but I have a script that fixes this after they are filed. [17:11] evilvish: if they aren't fixed they'll be a regression in the release [17:11] evilvish: the release isn't not going to happen so it is less work this way [17:12] OK, but i was wondering since we would not have a way to track the potential ones.. dint know what to do there. :) [17:13] evilvish: is your question answered or is there another question there? [17:13] nope, its answered.. [17:13] okay, cool [17:14] nigelb: there is an outstanding item regarding editing bugsquad headers to be similar. Does this sound familiar to you? [17:15] bdmurray, he is marked away [17:16] okay, I'll follow up with him via e-mail [17:17] then we have " Brian Murray to email Bug Squad regarding splitting of HowToTriage page up into a simple page and an advanced page [17:17] this I did not get to [17:18] I'll do it this week though. [17:18] maybe duanedesign, from beginners team, be able to might help with that? they might know what beginners expect? [17:18] hello [17:19] yes [17:19] duanedesign: we've been looking at w.u.c/Bugs/HowToTriage and thinking its a bit overwhelming [17:19] i was just looking at action items that have not been completed from UDS and noticed one about helpng w/ the Bug Squad wiki [17:20] that was assigned to us [17:20] bdmurray: ok. and have a simple and advanced page [17:21] duanedesign: yes, so if you have any ideas about the simple one we'd appreciate it [17:21] ahh isee. it is a bit long [17:21] where doesx it link from? [17:21] duanedesign: right there are so many things one *can* do as a part of triage [17:22] ahh, i see a link on /Bugs to the page [17:22] duanedesign: and the bugsquad header [17:23] aha [17:24] duanedesign: I'd be happy to discuss this in depth with you after the meeting but think we should move on. Okay? [17:24] bdmurray: sounds great. [17:25] duanedesign: thanks! [17:25] evilvish: Are there any specific mentorship program topics to discuss? [17:26] well, just that there has been 0 activity this month too, and that there are 26 members waiting approval, oldest applicant is from 2010-12-14 , and latest is 2011-03-14 yesterday [17:26] o/ [17:26] duanedesign: go ahead.. [17:27] i talked with pedro some today about better cooperation between the beginenrs Team and Bug Squad Mentor program [17:27] * evilvish was just thinking about the very same thing :) [17:28] we definetly want to get the folks in the Beginners team who are doing mentoring for bugs into the Bug Squad mentor program [17:28] and possibly help pre staging some of the mentees [17:29] some people are a bit unsure if bug triage is exactly for them. We could help them with an introductory knowledge [17:29] then when they are still interested they can join the bug Squad Mentoring program [17:30] i have noticed with the Beginners team this can help also with giving the team a 'window' to round up a mentor [17:31] the contributor is busy w/ very basic stuff and this will keep them busy for a week or so while a mentor is found [17:31] that was an idea we had and would love thoughts on it [17:31] but we definetly want to get our follks involved in the Bug Squad Mentor program being mentors [17:32] duanedesign: for this cycle, we have formed ยป https://launchpad.net/~bugsquad-mentorship-group-alpha , where the mentoring is to take place on the mailing list(supposed to) by a team of mentors.. this is mainly to get the folks ready to apply to BugControl.. but we are seeing low activity.. maybe they are overwhelmed? not sure.. [17:33] that is a neat idea. [17:33] If it helps, I just signed up with the bugsquad and I have no idea how to get started...I tried applying for a mentor but have not heard anything...maybe that can give some perspective [17:33] bdmurray: duanedesign: what we could do is send the initial applicants first to beginners team and then if they are interested to then jump into the mentoring team.. but this seems like a long route.. might ensure that the mentoring team only has folks interested are in the main team.. [17:34] cinfantino: yes it is perspectives like yours that would help us alot [17:35] cinfantino: yup, i'm aware.. hence i mentioned ".. and latest is 2011-03-14 yesterday" :) [17:35] :) [17:35] cinfantino: feel free to mention your thoughts.. [17:35] cinfantino: It would be interestig to hear how you got to where you are [17:35] bdmurray: same here, joined the bug squad a few days back... looked into HowtoTriage... but thats all....then applied for mentor and no update. [17:36] im new to the team and can verify that the guide does make it seem overwhelming but once you get in there and read some and stick to basic stuff at first and keep an eye on ones that have been done before get a better feel for it [17:37] evilvish: and where are the pending members? [17:38] bdmurray: https://launchpad.net/~bugsquad-mentorship/+members [17:38] geoffmcc: I agree with you , but some situations you just cant make head or tails [17:38] evilvish: and how does that relate to group-alpah? [17:38] I essentially wanted to start contributing and I looked through the Ubuntu wiki...thought this might be the best place to start. I signed up to become a bugsquad member and I am lost from there...it is daunting to say the least how to get started [17:39] Maybe it is just my ignorance but it seems very difficult to find out how to get started...even signing up was "difficult". [17:39] ravitejavad: please if you run a cross a situation you can't make heads or tails of ask here or email the bugsquad mailing list [17:39] bdmurray: thats how we have been doing it, members apply to the mentoring team and then we approve to the alpha team.. this was supposed to be several alpha/beta teams, hence this was the way it was chosen.. [17:40] bdmurray: well I have solved a few situations asking here, but I guess a mentor would make it a lot easier. [17:40] the guide should also maybe make better mention to the email list as other than new bug submissions and notice of new bugs it seems kinda quiet [17:40] bdmurray: the current members in the apha group have shown very little activity, and i fear we might be loosing new members like cinfantino ravitejavad and other 24 waiting there.. maybe we can approve the whole batch and see how this goes? [17:41] might overwhelm us, or maybe not.. but i dont think waiting another month would be a great option :) [17:41] +1 [17:41] evilvish: right, I recall. I think that makes sense. if the alpha group gets too busy then split it up / reevalute [17:41] Cool! [17:42] geoffmcc: what email list are you referring to? [17:42] and btw, we lost sense, maybe we can rope in ddecator to the mentors? [17:42] the bugsquad list [17:42] i will make it a point to talk to evilvish about how we can get the interested folks on the beginners team, who are bug control involved in the mentoring program to help out [17:42] geoffmcc: ubuntu-bugsquad@lists.ubuntu.com? [17:42] i meant to say other than new bug submission and notices of meetings [17:43] yes [17:43] duanedesign: sure thing.. [17:44] geoffmcc: what discussion would you like to see? most of the people who know how to perform bug triage do it, so don't often talk about it. [17:44] geoffmcc: which might lead one to believe nothing is happening... [17:45] i was just saying that questions can be asked there if no answer immediate answer in irc, right [17:45] geoffmcc: yes, that's how it's supposed to be used, where do you think we should make that clearer? [17:46] well i was just making a statement based on above mention of new members waiting for a mentor and it seemed like they havent tried to do it yet. [17:47] and someone mentioned coming in and getting some answers in irc. [17:48] evilvish: so you'll add more people to the alpha group - right? [17:48] sure, will do.. [17:49] I've already communicated to the mailing list regarding asking question in IRC then on mailing list so I think that particular issue is covered well [17:50] It might be interesting to have something similar to the ubuntu-devel pilots where people take a 1 hour shift here to answer questions [17:50] bdmurray: sound interesting [17:51] I'll email the bugsquad mailing list about that. [17:51] Moving on then [17:51] micahg: just in time [17:51] micahg: you wanted to talk about filing RFP bugs in Debian? [17:51] o/ [17:52] yes [17:52] what is RFP? [17:52] request for packaging [17:52] so based on the messages on the debian-derivatives ML, it seems that we should only file RFPs after the package is in Ubunut [17:52] *Ubuntu [17:53] I'm fine with removing the open RFP language [17:53] er open an [17:54] bdmurray: ok, adding an RFP once we package something is a good idea in case someone in Debian wants to adopt it [17:54] but I guess we should move that language to the new packages page vs triage [17:55] micahg: I don't quite understand how it is in an RFP if there already is a package but I'm not really concerned about it [17:55] Is that really bug triage or developer's thing? [17:55] bdmurray: if we add a package not from Debian [17:55] charlie-tca: the new packages page is developer oriented I believe [17:56] charlie-tca: that would be a developer thing at that point [17:57] Okay anybody else have an opinion about RFP bugs in Debian? [17:57] Well or needs-packaging bugs [17:57] evilvish: what's that now? [17:58] micahg: so you'll edit the relevant wiki page? [17:58] bdmurray: sure :) [17:59] micahg: thanks! [17:59] ddecator: hey.. would you be interested in joining the mentoring alpha team along with RedSingularity ? so that it is not so much as one-on-one but more of a team mentoring? [17:59] evilvish: if tim ( RedSingularity ) is up for it then that's fine with me, although he submitted his application for BC so i'm not sure if he'll be my mentee much longer [18:00] ddecator: cool, then RedSingularity is not a main factor,.. https://launchpad.net/~bugsquad-mentorship-group-alpha < right now the mentees are being added there and no mentor is being assigned a mentee as before, its just a group thing now [18:00] I wanted to congratulate Robert Roth (evfool) and Christopher Penalver on joining the Ubuntu Bug Control team. [18:01] evilvish: alright, sounds good. mostly irc and ML? [18:01] ddecator: yup.. cool, thanks! :) [18:01] We do need to clarify to new mentee applicants that triage is not a starting point for development/fixing bugs, but the place to get bugs ready for fixing [18:01] charlie-tca: agreed [18:01] +1 [18:01] penalvch ^ [18:01] They've both been doing some fantastic bug work. [18:02] evilvish: since the team is restricted i'm guessing you'll take care of adding me? [18:02] +1 [18:02] ddecator: yup, on it [18:03] evilvish: danke :) [18:03] Are there any other topics for discussion? [18:05] evilvish: What's up? [18:05] penalvch: I wanted to congratulate Robert Roth (evfool) and Christopher Penalver on joining the Ubuntu Bug Control team. [18:05] :D [18:05] ] They've both been doing some fantastic bug work. [18:05] Congratulations, penalvch, on bug control! [18:05] :) [18:05] * kamusin \o/ [18:06] huh! i totally forgot kamusin ! ;) [18:06] welcome :) [18:06] kamusin: free for mentoring team? ;) [18:06] great work penalvch [18:07] Okay, I guess that's it for the meeting proper. Thanks everyone! [18:07] thanks! [18:07] * evilvish bbiab [18:07] Thanks, bdmurray, for chairing! [18:07] thanks bdmurray [18:08] i need to put these meetings on my calendar so i don't forget them.. [18:08] thanks bdmurray [18:08] next meeting on april 12? [18:09] yes [18:09] thanks bdmurray [18:11] evilvish, no problem ;) === bdmurray changed the topic of #ubuntu-bugs to: Ubuntu BugSquad - next meeting 4/12/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [18:14] kamusin: awesome! adding you to the team where it is not one-on-one mentoring.. thanks :) [18:16] excelent :) [18:21] ddecator: dont forget to subscribe to that teams ML ;) [18:21] evilvish: i did. my inbox is filling up rather quickly with your work :p [18:22] ddecator: haha, we have a backlog, i should have probably done that before making you admin [18:22] atleast i'll do that for kamusin , saves him from my spam ;p [18:23] evilvish: haha, i got the email saying i was an admin about 10 emails in. it's fine though, easy enough to delete [18:24] evilvish: i am going to send my email to "ubuntu-bugcontrol at lists dot launchpad dot net" to become a mentor [18:24] duanedesign: we've sucked you in, eh? :) [18:25] duanedesign: awesome! [18:25] you catch me evilvish, now you address is clean :) heh [18:35] hey all...I need a place to start...I have joined the team read through the "how to triage" but am stuck...where to next? [18:35] * ddecator is glad to see how many people are being added for mentorship :) [18:35] grab a bug in your package of choice and see how far you get in your how to triage knowledge cinfantino [18:36] then when you get stuck, ask questions here :) [18:36] Ok...that is available through launchpad? [18:36] indeed [18:36] OK, thank you very much [18:37] cinfantino, https://bugs.launchpad.net/ubuntu [18:37] that is the main page for bugs in ubuntu [18:37] my pleasure [18:37] awesome, thanks! It now makes sense :) [18:40] well there's evidence that the wiki needs to do a better job of getting people started [18:41] ddecator, TRUE [18:41] sorry caps-lock fail [18:41] * ddecator plans on coming up a concept for how the wiki can be streamlined, at least the HowToTriage page [18:42] cinfantino: if you have any recommendations in terms of what was confusing, what should be included on the wiki, etc., please let me know in an email. ddecator at gmail dot com [18:44] ddecator: done [18:44] ddecator: let me know what you come up with. I volunteered to help on that. Also we can ask around the beginners team and see if any 'beginners' have any suggestiond [18:45] duanedesign: sounds good. i was talking with hggdh about it before. i plan on coming up with a PDF with a concept of how it can be changed so it's more informative yet less overwhelming. it'll tie into the slides i make for the triaging class as well. i'll probably send it to both teams for feedback [18:45] cinfantino: thanks :) [18:45] ddecator: no prob :) [18:46] cinfantino: I would look for bugs about a package / piece of software I used a lot or like [18:47] bdmurray: Makes sense [18:47] ddecator: souonds like a plan [18:48] at the very least, i think there needs to be screenshots so there are visual aids instead of just a wall of text [18:48] ddecator: got a few eager wiki folks on the BT we might be able to solicit for help implementing the changes if we need it [18:48] duanedesign: yah, that's a great idea [18:48] ddecator: launchpads user interface changes quite regularly so my concern has always been maintaing those screenshots [18:49] ddecator: yeah and maybe some sub pages for 'advanced' or lengthy topics [18:49] bdmurray: true. i'll take that into consideration to see if there are visuals we can use that aren't likely to need updating consistantly [18:49] cinfantino: you can search for a package at https://launchpad.net/ubuntu/ [18:51] a video walkthrough would be great, but i doubt the time and effort would be worth it since it would most likely need regular updating [18:52] I'm in the same boat as cinfantino, just getting started here. I see this big list of bugs and wonder which status makes the most sense to start with. New, confirmed or crash reports? [18:52] areeda: normally, you start with bugs in "new" status [18:52] Probably my most frustrating buts are with VNC but comments in the bugreports and forums seem to make [18:52] that daunting [18:52] areeda: i recommend new since you can start from the beginning and it gives you the chance to test and confirm the bugs if nothing else [18:53] OK I'll go find a new bug to start with [18:53] areeda: a list and explanation of some of the Status' at https://wiki.ubuntu.com/Bugs/Status [18:53] If we know of a fix, can we mark that in a comment to let the submitter know. [18:54] and this page is great one to bookmark https://wiki.ubuntu.com/Bugs/Responses :) [18:54] cinfantino: workarounds are helpful to know :) [18:54] um, there shouldn't be a fix if the bug is valid. There might be a workaround, which allows for a way to not hit the bug, but it is not a fix [18:55] on a similar note, this extension is great: https://launchpad.net/~gm-dev-launchpad/+archive/ppa [18:56] ddecator: yes that is a timesaver [18:58] i find these debugging guides can be helpful to get more information on a bug https://wiki.ubuntu.com/DebuggingProcedures 'til you start getting more familiar with the area or package your interested in [19:08] Thank you, I have plenty to read and a place to start. I'll keep notes on my progress and perhaps I can help with the wiki by organizing stupid newbie questions. [19:09] I do agree my biggest issue is being overwhelmed with an unclear idea of what to do first [19:09] that was organizing MY stupid newbie questions [19:18] hggdh, eeebotu is gone [19:58] kamusin: looking into it, thank you [20:01] kamusin: thank you. Seems I have a power failure, and eeebotu was sulking at the corner [20:10] hggdh, heh [20:46] What is CVE as in CVE reports in releases of Ubuntu? [20:47] areeda: CVE - Common Vulnerabilities and Exposures (CVE), cve.mitre.org [20:47] thank you [21:01] duanedesign: you just need to wait for hggdh or bdmurray reply to your BC mail.. [21:02] duanedesign: just letting you know that they'll look into it .. :) [21:06] evilvish: heh [21:06] duanedesign: approved :-) [21:06] duanedesign: thank you, etc, etc, and so on ;-) [21:06] hggdh: just letting him know you da man! ;) [21:07] evilvish: I am starting to understand the 'evil' in vish ;-) [21:07] :D [21:43] does anyone have the meeting logs i missed it [21:45] trinikrono: http://irclogs.ubuntu.com/2011/03/15/%23ubuntu-bugs.html#t17:07 [21:46] :D thanks [22:45] !727290 [22:45] Factoid '727290' not found [22:45] !bugs 727290 [22:45] Launchpad bug 727290 in compiz (Ubuntu) (and 1 other project) "Zoom doesn't follow to text (affects: 3) (heat: 441)" [Undecided,New] https://launchpad.net/bugs/727290 [22:45] Factoid 'bugs 727290' not found [22:45] erkan^: bug 727290 [22:46] bug 727290 [22:46] !bug 727290 [22:46] erkan^: the bot's a little slow [22:46] ow ok [22:46] i have found [22:46] thx [22:46] erkan^: also, if you just want to query the bot, send it a PM [22:47] erkan^: I mean if it's not relevant to a conversation [22:47] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/727290 --> i have found micahg [22:47] Launchpad bug 727290 in compiz (Ubuntu) (and 1 other project) "Zoom doesn't follow to text (affects: 3) (heat: 441)" [Undecided,New]