[00:26] So, how could a noob like me be useful around here? [05:16] Fableflame: well, that's too generic of a question. What would you like to do? Testing, sorting bugs? writing some stuff? advocating? there's a lot to do... === bladernr_ is now known as bladernr_afk [10:03] gema - are you planning to create a subpage for each task on : https://wiki.ubuntu.com/QATeam/TasksPrecise (or link to a blueprint if appropriate) [10:04] brendand: I have no plans yet, didn't know how to handle it so I created a wiki [10:04] brendand: sounds like a good idea to have subpages for that [10:07] brendand: since in the blueprints we need to put people's launchpad ids and I don't know most people's ids (plus the work is going to be collaborative) I haven't figured out how to do that [10:08] gema - since the bp's are used for status.ubuntu.com you probably don't want people messing with them. better to co-ordinate on a wiki and have one or two people updating the blueprints [10:08] brendand: ack [10:09] gema - for the testcases in the tracker, shall we update them in place? or leave them as they are there and update them somewhere else? [10:10] brendand: I would like to see them in a spreadsheet, like the one I uploaded to the wiki [10:10] so that we can put them in the TCMS of our choice once they are reviewed [10:10] and approved [10:10] we may end up with some spreadsheets , one per person or so, but at least we know they are good and finished [10:10] gema - which spreadsheet? [10:11] * gema looking at the email again, I keep losing wiki links... [10:12] brendand: https://wiki.ubuntu.com/QATeam/TestCase <- look at the bottom of this page [10:16] gema - i added links to the current testcase tracker and the page above in the task on https://wiki.ubuntu.com/QATeam/TasksPrecise [10:17] gema - do you think we could give the tasks a name? instead of calling them tasks 1-7 :) [10:18] brendand: go for it xD [10:18] brendand: I would have trouble finding a name for my own child, so you better take that (since you have more experience naming) [10:19] brendand: any changes you deem necessary feel free to do them and inform the list afterwards, or report them in today's meeting, whichever works for you [10:20] brendand: thanks! [10:22] gema - the meeting is from 5-7 right? for both topics? [10:27] Whoa, activity! [10:27] brendand: the meeting is for all we've done this week [10:27] Figures you guys are active when I should be sleeping, lol. [10:27] brendand: things that are in the list and things that we are doing but are not in the list [10:28] brendand: i.e. difficult to share and needing access to internal systems [10:28] Fableflame: indeed [10:29] gema - great, i have it on my calendar now [10:34] So say I wanted to get involved in Testing. What should I be testing? I've already install 12.04, should I just use it like I would every other day, or is there a list of procedures? [11:04] Fableflame - we do have a list of test cases, but as the email says they are out of date and not very good === _salem is now known as salem_ [11:05] Fableflame - For effective testing you shouldn't use it 'as you do everyday' but try doing as much as possible, doing unusual things etc [11:06] Really effective testing is controlled and based on knowledge of the software design and past experience, and encoded in test cases [11:07] Hmm. I'm a bit lacking in knowledge. === bladernr_afk is now known as bladernr_ === jibel_ is now known as jibel [16:47] gema - i need to babysit now so i won't be that active in the QA meeting unfortunately [16:48] brendand: no problem, you can answer to anything on the list later [16:48] brendand: I will publish the log straight away === salem_ is now known as _salem === bladernr_ is now known as bladernr_afk === bladernr_afk is now known as bladernr_