[00:00] yeah, i'm wondering if that is technically still used [00:00] otoh, it's not a ubuntu pkg [00:00] .. i think [00:01] see https://launchpad.net/xubuntu-artwork [00:01] oh wait [00:01] yeah, there is the quantal pkg too [00:02] so the project is probably needed technically [00:02] i updated the description [00:03] yeah [00:09] anyway, got to go. going to a confirmation party tomorrow and need to get up in less than 6 hours [00:09] see you! [00:16] night :) === madnick_ is now known as mandnick === mandnick is now known as madnick [04:27] pleia2: packagesets have nothing to do with the upstream projects [10:51] Morning all [12:42] Heheh, knome, pleia2, well the other day, Scott updated the xfce4-utils replacement to the natty source tree on the Studio side as well. Maybe it's not giving up just yet. :) [15:29] knome: pleia2: I'm a little behind schedule. Can either of you start the meeting in half an hour? I should be available to join in a little later. [15:51] micahg: xubuntu-desktop is considered upstream? [15:54] but yeah, I don't know how packagesets work so I was just guessting :) [15:54] -t [15:58] Hi guys! [15:59] hullo [15:59] hello [15:59] perfectly in time for the rendez-vous :D [16:00] knome: you about? [16:01] Today Q&A right?!?! [16:01] Am I on time?! [16:01] yes [16:01] yes, calm down :) [16:01] Hi :D [16:01] Enthusiasm...sorry [16:02] astraljava is going to be a bit late [16:02] Alright, can I get a show of hands for the participants of Xubuntu QA meeting? [16:02] Heheh. :) [16:02] oh yay! [16:02] want to #startmeeting? [16:02] here am I [16:02] pleia2: No, I don't think we need that today. [16:02] ok [16:02] o/ [16:02] * hobgoblin listens at the touchline [16:03] I'll give it a minute for other hands to be raised, and then I'll introduce a free-form agenda I have in mind for today. [16:04] I apologize in advance, if I'll be a bit late at answering, because I'm updating my system (I'm running on a P3) [16:05] P3, nice! :) [16:05] FiltroMan: I'll try to keep this meeting a little bit more informal than the usual meeting. I'm not in a hurry today, I intend to be here chatting with as many, topics and users, as possible. [16:05] That's why I don't think we need to make the bot keep minutes of today. [16:06] Oh lovely :) [16:06] But still, I'd like to have the topic confined to QA issues only. [16:06] We can't hold the channel hostage all day long. :) [16:06] astraljava: to the worst you can always create a new chan ;) [16:06] Ok, so it looks to be us, then. Anyone is free to join later if feels like it. [16:07] Hi ochosi, yes of course, if we're being threatened around here. :) [16:07] c'mon guys... we shouldn't go off topic that often [16:08] So, welcome everyone, and thanks for showing interest! [16:08] I should probably introduce myself quickly, if anyone's wondering why I'm here doing most of the "formal" style of talking. [16:09] During the precise cycle, I took more part in Xubuntu development, not really on the low-level technical part, but being the handyman and trying to help wherever. [16:09] astraljava: yes, please! and a short info, how this works here. ;-) (for the first time participating on such a thing. [16:09] Hello Os_Maleus, I'll try. :) [16:09] Since precise was an LTS, we needed to pay a lot of attention to quality, and I think we did a decent job. [16:10] What that means is that a lot of testing was involved. [16:10] Our primary means of doing the testing consist of testing the daily images, and milestone releases. [16:11] The latter ones are called Alpha-1, Alpha-2, Beta-1, Beta-2, and then the various amounts of Release Candidates, which usually are desired to be limited to a number of one only, but occasionally we need more if really grave bugs are found that late in the cycle. [16:12] Previously the image testing results were only tracked for the milestones, and the place for them is http://iso.qa.ubuntu.com [16:13] But nowadays you can file results for dailies there as well. [16:13] Anyone is free to file results there, it only requires a username there, which is easiest to do with a ubuntu openid login. [16:14] If you wanna have a look at the site now, I'll give you a minute or two for that, cause I know that you're already that impatient. :) [16:14] didn't know you could file for dailies - would have done that the other day :) [16:15] yeah, it's great [16:15] well organized [16:15] pleia2: well I can do that more or less daily :) [16:16] It is well organized, yes, but for Xubuntu, it still needs a few tweaks. [16:16] I'm talking about testcases of course. [16:17] Obviously [16:17] On there is also possible to file the documentation? [16:17] So basically what you are saying is that you need more testers? [16:17] We're wanting to make a change to the classifications, and the procedures. [16:17] cc_INC: we always need more testers :) [16:17] cc_INC: That, too. :) [16:17] FiltroMan: Could you elaborate on that, please? [16:18] Cool. I have never participated in something like this. [16:18] I was meaning, that the official documentation revisioning has to be posted always into the daily schedule or somewhere else? [16:19] FiltroMan: Are you referring to the testcase description? [16:19] Also [16:19] I'll try to explain better [16:20] I received the mail with the date and time for this rendezvous by Paasi, after I've applied for a role of grammar revisor for Xubuntu-Docs [16:20] FiltroMan: Ahh... no. That's a bit different. [16:20] Can I ask a very quick question regarding quality control? [16:20] doc review will have its own procedures for reviewing (not QA) [16:21] Oh... [16:21] FiltroMan: Sadly I'm not very well versed on how the documentation team is doing. Of course it has to do with QA, but not as directly. [16:21] cc_INC: Sure. [16:21] I'd better to save the whole log of this session (for my personal culture ;D) and send a mail to Paasi [16:21] Don't you think? [16:22] all logs of this channel are available on irclogs.ubuntu.com for reference :) [16:22] On all of my boxes Xubuntu generates an error report whenever something crashes or isn't working properly. Does this error report get sent to the proper people?! [16:22] Just wondering.. [16:22] Pasi (knome) will send out more information about doc team stuff when we have things further organized, but you're welcome to ask specific questions of him [16:22] Perfect! [16:23] cc_INC: It asks whether you want to file a bug about that, doesn't it? It won't automatically, but if you file the bug with apport, then yes, it's possible. [16:23] I'm just not sure we've actually made enough plans for docs review to actually answer your questions right now, the docs haven't been updated in several cycle [16:23] s [16:23] (perhaps we should plan a docs team meeting too :)) [16:23] I always file bugs....figure you could do something with the info [16:23] cc_INC: One moment, I'll link to the apport mechanism. [16:24] cc_INC: https://wiki.ubuntu.com/Apport [16:24] With this in mind, I would love to help out with testing. Given if there is a proper procedure in place to help us new to testing so we get started the right way. [16:24] cc_INC: There is. And I was really getting to that, next. :) [16:24] Thanks astraljava [16:25] cc_INC, there is [16:25] So as I was saying, on the ISO tracker, there are the testcases listed. [16:25] At the moment we're in the process of renewing their decriptions. [16:25] descriptions* [16:26] So far we have one made to the point where we're happy with it. It doesn't mean, though, that it cannot be changed anymore. [16:26] It can be found at: https://wiki.ubuntu.com/Xubuntu/Testing/Short [16:26] Do you wanna go through it now? I can give you 2 minutes for that. [16:27] astraljava: so is the https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Short not for use now? [16:27] hobgoblin: That was the old one. [16:27] We made it a little more to the point. [16:27] cos that's what I used the other day and had some comments on [16:27] k [16:27] astraljava: a couple quick questions before going through it? [16:28] While you're reading, I'll talk about it a little. It's called Short, because we wanted the testers to be really able to go through that for the dailies as well. [16:28] pleia2: Sure. [16:28] is there going to be a replacement for the Long one? [16:28] hobgoblin: Yes. [16:28] k [16:28] so right now on the QA tracker you go to the livecd test page like: http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/17405/testcases/129/results and it links to http://testcases.qa.ubuntu.com/Install/DesktopLiveSession [16:29] would this /Short test replace that Ubuntu-specific live session? or does the /Short go somewhere else not currently linked to the QA tracker? [16:30] pleia2: We're wanting to link to that soon enough. Maybe the /Long would need to be updated first, though, as well. [16:30] ok, where does /Long fit into the QA tracker, an extension of http://testcases.qa.ubuntu.com/Install/DesktopPostInstallation ? [16:31] (DesktopPostInstallation is Ubuntu-specific too, but you can complete all the tasks on Xubuntu) [16:31] I'm thinking it'd be especially used for milestone releases. [16:31] There is the post-installation part in the /Short as well. [16:32] I guess what I'm trying to figure out is precisely where these /Short and /Long tests go with regard to the QA tracker, since right now they're not really in the iso tracker workflow [16:32] so people don't know about them :) [16:32] Yes, it's a good point. [16:33] I think what we were thinking of is that we have the basic testcase for all *buntus. Then we have the Xubuntu-specific parts, which are our /Short and /Long. [16:34] We need to tweak the link in the http://testcases.qa.ubuntu.com to suit our needs. [16:34] links* [16:34] ok, so I think we should keep this in mind as we move forward with the /Short /Long rewrites, since they will have to fit somewhere in this workflow (maybe it doesn't make sense to have a post-installation section of the /Short) [16:34] But the main idea is that half of the image testing is the same for all flavors and the vanilla. [16:35] pleia2: It does, as part of the ISO testing is also to keep track of the applications and the integration of them in the desktop env. [16:35] ok [16:35] my other question - we intend to move /Short and /Long to the QA wiki once we've finished writing, right? [16:35] Yes. [16:35] ok, great :) [16:35] that's all from me, proceed! [16:36] Thanks! :) Dailies testing can become tedious and consuming, that's why the /Short needs to stay short. [16:36] * pleia2 nods [16:36] But enough to gather the most important things of the distribution and its most used parts. [16:37] last cycle it was very unclear to me whether the /Short and /Long were even used because I just followed the QA wiki test cases, not the short and long [16:37] So my question to the new people around here is, how do you feel about it now that you've glanced through it? [16:37] pleia2: Yeah. That's one part I wanted to pay much more attention to QA procedures from now on. [16:38] it all worked ok for me the other day - except I had the old short page lol - didn't know that I could go to the tracker or I'd have filed a bug [16:38] (btw new people: it's ok to say the QA tracker looks confusing and you need help, I sure did) [16:38] or two [16:38] FiltroMan, cc_INC, hobgoblin, Os_Maleus especially, have you read through the document yet? [16:38] pleia2: I will :) [16:38] yes [16:38] you mean this document https://wiki.ubuntu.com/Xubuntu/Testing/Short [16:38] right? [16:38] cc_INC: Yes. [16:39] Cause you guys were talking about Short, Long, Testcase Q&A kinda lost me for a moment :) [16:39] Oh, and GridCube, hi! I saw your nick flash by there earlier. :) [16:39] cc_INC: sorry :) [16:39] cc_INC: Yes, sorry about that. :) [16:39] Yeah I read it. Is quite clear, simpel steps that have to be followed, [16:40] sup astraljava :) [16:40] Again, I want to stress, this is not a very formal meeting. I want a more cozy and relaxed atmosphere here, feel free to voice your questions and concerns about anything. :) [16:40] theres some sort of meeting? [16:40] GridCube: A little bit like that. :) [16:40] :) ok [16:40] im zsyncking images once or twice a week now [16:40] So maybe a stupid question from the newbie. [16:40] but i havent done any tests [16:41] But where does one post the "resluts" of the test?! [16:41] university is on final month [16:41] GridCube: That's alright, that's why we have these new people around here now. :) [16:41] cc_INC: Ok. Have you logged in to the site, yet? [16:41] You mean this site: http://iso.qa.ubuntu.com/qatracker [16:41] ? [16:42] cc_INC: Yeah. [16:42] Not yet...(doing so as we speak) [16:42] cc_INC, :P then you can't [16:42] cc_INC: Ok, once you've done so, you will see the currently open milestones. Yes, dailies is a milestone, too. :) [16:43] We should have a look at 'Quantal Daily', when you've logged in to the site. Can everyone intested do that right now? It's much easier and more beneficial to do talk about stuff when you see everything we see at the same time. [16:43] interested* [16:43] to talk about* [16:44] gah... where'd my typing go today? [16:44] :) [16:44] Oh snap...forgot my password...sorry.... [16:44] cc_INC: No worries, we are not in a hurry. :) [16:45] astraljava Thanks, I feel a bit embaresed tho :) [16:45] :) [16:46] cc_INC: No need. :) I have tens of passwords to even more sites. It's not everyday I forget all of them, but every week at least. :) [16:47] talking about qatracker :( i don't know programing so my idea is not going very far bug: 994816 [16:47] Launchpad bug 994816 in Ubuntu QA Website "Buttons for adding bugs found in previous builds of a product" [Wishlist,Fix committed] https://launchpad.net/bugs/994816 [16:48] * astraljava is not a webdev, so will likely pass [16:48] hehe [16:49] Give me bugs on C/C++ apps, or python, or even perl. But js? [16:49] Nah... [16:49] but adding those buttons to the qatracker would make testing so damn better [16:50] I'm gonna give it 2 minutes still. Let me know with the now legendary 'o/' sign when you're done with logging to the site. [16:50] like "this are the known reported bugs you should look at bro" and people go and say "yep i still see them sis" or "nope they arent they anymore!" [16:50] GridCube: Are you trying to talk me into learning a new script language? [16:50] yes [16:50] :D [16:50] gah [16:51] * GridCube has to learn visualbasic to make excel forms, don't ask why :( [16:51] GridCube: yeah that would be awesome [16:51] You guys are no fun. [16:51] the "hardware profile" link area also confuses people to know end (the answer to what it is even feels hacky :)) [16:51] my internet was interrupted. here is a stormy wind going around. astraljava, would You like to tell me where I find the log again, please!? [16:52] know end? [16:52] no end [16:52] more coffeee [16:52] Os_Maleus, irclogs.ubuntu.com [16:52] http://irclogs.ubuntu.com/2012/06/17/%23xubuntu-devel.html [16:52] http://irclogs.ubuntu.com/2012/06/17/%23xubuntu-devel.txt [16:52] it wouldn't have updated yet [16:52] Well, there you go. [16:52] nope [16:52] specifically that one eventually [16:52] Os_Maleus: http://iso.qa.ubuntu.com/qatracker [16:52] Yeah, but eventually. [16:53] Os_Maleus: Are you willing to participate in this session, still? If so, then do log in on http://iso.qa.ubuntu.com. [16:53] Ok, I guess we'll move on now. [16:53] I read the "/short"-thing. sound/seems to be easily performable [16:53] Os_Maleus: Good to hear. [16:54] When you click on the link 'Quantal Daily', you'll see a few testcases. [16:54] err.. products. [16:54] I need to say, that I didn't send reports back, until now. didn't had the time to deal with that, simply. [16:54] Do I login with my Launchpad details or is this something totally different than launchpad? [16:54] cc_INC, same that lp [16:54] For the record, on your left hand menu, you can limit the products to the ones that appeal to you in the Filters section. [16:55] cc_INC: LP openid works there, too. [16:55] Os_Maleus: Yeah, I mentioned that while you were away, probably. That's why the /Short testcase is really short, now. [16:55] Anyway, if you scroll down enough, you'll find Xubuntu there. [16:56] Let's click on 'Xubuntu Desktop amd64'. [16:56] That's probably going to be used the most. [16:56] mmm [16:56] i wonder if i can do amd64 vbox testings now... [16:56] But of course, if your machine is not capable of handling the instruction set, choose i386. [16:57] Any one of them will do for today's purposes. [16:57] cc_INC, Os_Maleus you should learn to use zsync aswel [16:57] Once you've chosen the product/image you want to test, you'll be facing the various testcase. [16:57] testcases* [16:57] GridCube: Good point, I should cover it now. [16:58] GridCube: zsync? I know Rsync. did You mean that one? [16:58] Select a testcase, for instance, if you only wanna check how the live session works, choose 'Live Session'. (you could not have seen that coming!) [16:58] i know that for some reason zsync is better for isos, cant tell why tho [16:58] works well here [16:58] Okay okay [16:58] It took me a while but I'm in... [16:59] Os_Maleus: similar thing, but zsync can grab diffs of the binary iso images (rsync would redownload the whole image if it's changed) [16:59] Once you've selected the testcase, you can see the links to the image, and the description of the case. [16:59] You can also filter on Xubuntu instead of scrolling down?1 [16:59] If you see the 'Link to the download information', go ahead and click it. [16:59] pleia2, :D that was it! that it downloads only the parts that changed :D [17:00] There you can find the list of images, and on some the ways to acquire them. [17:00] The third one, as GridCube suggested, if very handy for the testers of the daily images. [17:00] I am making my back-ups with rsync. there it is writing the same: only changed files. [17:00] GridCube I have no clue what zsync is but I pick up things fast. So will dig into it ASAP :) [17:01] It only gets the changed part of the .iso, which will mean a dramatic drop of data flowing through your lines. [17:01] cc_INC, astraljava is explaining now ;) [17:01] As you can see, all the links point to http://cdimage.ubuntu.com [17:01] That is the main server that hosts all the images. [17:02] When you have done some testing, you probably won't need that page anymore, and you'll remember to head directly to that site, if necessary even. [17:03] if you want an example I run this cd /mnt/music/Spare/Iso/Daily/ && zsync http://cdimage.ubuntu.com/xubuntu/daily-live/current/quantal-desktop-i386.iso.zsync [17:03] Hehe, thanks hobgoblin, I was just about to type that. :) [17:03] :) [17:04] Although not under /mnt/music... Why music?! :D [17:04] But yeah. Pay attention to that URL. [17:04] Instead of a date in the link, it has current/ [17:04] Testing sounds like music to his ears? [17:04] That's very handy, cause then you don't have to know which date has the latest successful image. [17:05] See, sometimes images fail to build. [17:05] :P i have to .sh files with: zsync http://cdimages.ubuntu.com/xubuntu/daily/current/quantal-alternate-i386.iso.zsync [17:05] And for that date, there won't be anything worth your while. [17:05] :D [17:05] But when you replace the date with current/, it'll find the latest directory that has images that can be tested. [17:06] zsync http://cdimages.ubuntu.com/xubuntu/daily-live/current/quantal-desktop-i386.iso.zsync [17:06] Anything you want to ask about now? [17:06] So far I understand it a little bit. [17:07] FiltroMan, Os_Maleus, still with us? [17:07] Testing can be done in Virtual Box or on actual hardware? [17:07] Especially the zsync crash course was interesting by the way. Much thanks for explaining! [17:08] yes, still here, but can't log in there. ... searching for my pass-word. :-D [17:08] cc_INC: Both will do. [17:08] Great [17:08] I think I have some old boxes lying around I can use as test subjects :) [17:08] Os_Maleus: Ok. Well, you can always ask when you have logged in. Most of the people on the channel know this stuff. [17:08] cc_INC: Yep, I do that as well. [17:09] Okay can I quickly do a recap just to see if I fully understand? [17:09] cc_INC: Of course. [17:10] 1- Go to http://iso.qa.ubuntu.com/ to get the latest daily build with zsync. 2-Go to https://wiki.ubuntu.com/Xubuntu/Testing/Short to follow the steps [17:10] 3- Report the results....ehmm....where again? :( [17:11] don't think we'd got there yet cc_INC [17:11] cc_INC: Ok, once you've downloaded the image, and done the test, you can return to the testcases page. [17:11] Sorry hobgoblin [17:12] There underneath the download information, and the links to the testcase, you see the 'Add a result' section. [17:12] Will have a look straght away... [17:12] The only thing that's mandatory is the result. Did everything work as expected, and this means while you were going through the testcase. [17:13] Ooooh I see now!!! Wicked!! [17:13] seems like I would be too stupid even to create a new profile there. ... can't log in. [17:13] Awesome, I get it now. Thanks for your patience! [17:13] If anything failed, you mark the image as failed. If you didn't stumble upon anything unexpected, you'll mark it as Passed. [17:13] Os_Maleus: not at all :) there should be a password reset thing for ubuntu single sign on [17:14] Boy, this is exciting :) [17:14] can I just add something - if you do find a bug and report it - only put the number of the bug - not the whole URL in the list [17:14] You can also mark it 'In progress', though I must admit I haven't personally done that before. I guess this is more meant for use when time is short, and you need to have results in, and only a handful of people are doing the tests, so you divide the responsibilities. [17:14] I wasted ages on that [17:15] hobgoblin: Yep, good addition. [17:15] thanks :) [17:16] o/ Sorry, again a small question....oh gee, sorry for being a pain in the beezwax guys...but is testing a informal, whenever I have time for it I will get to it kinda thing. Or is it formal as in you need to do it otherwise you're off the testing team kinda thing? [17:16] It does nowadays say 'Comma separated list of bugs preventing you from passing the testcase', so the 'list of bugs' means a list of bug NUMBERS. [17:17] cc_INC: For the dailies, it's very informal. But for the milestone releases, we need to cover enough of them so that the image will be released. [17:17] cc_INC, we are all contributors with our free time [17:17] +1 to that [17:17] cc_INC: No one will be kicked out of the community for not participating, though. [17:17] :) [17:18] Not even frowned upon. :) [17:18] I do have a question here related to bugs in general when there's time for it [17:18] Okay I understand. I will do my best to help where I can guys. I really want to help. Happy to hear that I can manage my own time by myself being a family man and all :) [17:18] hobgoblin: I will do my best in answering it, but I'm not really a bug expert when it comes to ubuntu guidelines. But shoot. [17:19] cc_INC: Yep, do what you can, when you can, but only if you WANT to. :) [17:19] ok - so I tested the daily the other day - one of the tests is plug in a usb - if it mounts cool - it actually failed - the question is [17:19] how do you work out WHAT to fille something against? [17:20] what would I have filed a failure to mount a usb against? [17:20] astraljava I really WANT to :) [17:21] hobgoblin: You can ask on the channels (Xubuntu-specific or #ubuntu-bugs, for instance), check the LP bug lists for certain terms, use google for it (although we never tell anyone to "Go google it!"), whatever you can. [17:21] hobgoblin: ...or, just file the bug, and let the bug triagers point it to the right package. [17:21] lol [17:21] I try not to do that unless I have to :) [17:22] I try not to search launchpad either - therein lies pain [17:22] hobgoblin: We try not to be too limiting, cause we need to know about the problems. Making sure it's filed on the correct package from the first second on, isn't that important. [17:22] ok :) [17:22] cc_INC: Good to hear. :) [17:23] hobgoblin: I ask here for pretty much every bug I report ;) [17:23] pleia2: k [17:23] wb cc_INC [17:23] hobgoblin: Basically it boils down to how computer and ubuntu-savvy you are. If you know about what deals with which functions, you can ease the work of the triagers by doing a bit of research on your own. But it isn't absolutely necessary. [17:23] Sorry guys I got dropped out...:( [17:23] cc_INC: No worries. Welcome back. [17:24] But yeah, back to the filing results. [17:24] So if everything went as expected, just mark it as Passed, and you're done! YAY! :) [17:25] Sounds great!! [17:25] But if you had problems, mark it as Failed, and depending on your mood, spare time, and tiredness, you can file and list the bugs that you stumbled upon, or if you found that LP already knows about some of them, just pick the existing bug numbers, and list them in appropriate text fields. [17:26] Critical bugs box (love the sound of that) is, as it says, bugs that prevent you from passing the testcase. [17:27] Now you might notice that the Bugs box (aaww...) can be used EVEN if you marked the result as Passed. [17:27] While everything listed in the testcase description works, you might still stumble upon some other bugs. This is your chance to make them noted. [17:28] So, to recap, the first box (Critical bugs) is used if you CANNOT pass the testcase. The next one for some bugs that you found, but could still complete the tests mentioned in the testcase description. [17:28] Everything clear so far? [17:30] I think we skipped what you actually test [17:30] there is the link to the testcase, but where do /Short /Long come in? [17:30] pleia2: Yeah, but cc_INC asked. :) [17:30] So I covered that now. [17:30] ok [17:31] Ok, the rest of the text boxes are all just FYI only. If you want, feel free to add information there. It's cool to see what hardware people tested on, but it isn't in anyway necessary. [17:32] If you have anything to add to the tests, or anything at all related to QA, you can type in the Comments box. [17:32] Alright, should we go through the /Short testcase now? [17:32] Yup.. [17:32] I'd like to suggest a short break. Take 5, everyone? :D [17:33] astraljava you're explanation is crystal clear!! Thanks, doing a great job here.. [17:33] yep [17:33] I created a couple wiki pages for my hardware profiles that I test with: https://wiki.ubuntu.com/lyz/LenovoG575 https://wiki.ubuntu.com/lyz/vbox15G [17:33] We've already chatted 1.5 hours by now. Wow.. [17:33] time flies astraljava :) [17:33] pleia2: Cool! If you want, use those as examples, and create your own, and then link to them. [17:34] * astraljava makes a mental note to wrap up in 1h 15min, the soccer games await... ;) [17:34] lol [17:34] okay, astraljava, it took me some time to recognize that my brower war blocking me. I am in there now. [17:34] Yeah I also have some diner that's about to get ready anytime soon :) [17:35] Os_Maleus: yay! [17:35] * hobgoblin desperately wanst whatever happens in footie to result in portugal going home [17:35] PORTUGAL?!?! Going home?!? WHY?!?! :) [17:35] haha [17:35] cos I'm English [17:35] :) [17:36] I think our guys are going home! [17:36] Ooops....going way way off-topic here. Sorry guys :) [17:36] we're having a 5 min break cc_INC :) [17:37] Haha, in that case... [17:37] I live in The Netherlands...I think our guys are gonna bite the dust. [17:37] astraljava: I do have a couple of action item type things I'd like to quickly discuss, but we can do that in 10 minutes or so toward the end of the meeting :) [17:38] My money is either on Spain or Italy on winning the thing. [17:38] cc_INC: +1 to both of those [17:38] Although UK has been a pleasant surprise too man..geez. [17:39] :) [17:39] pleia2: Shoot. [17:40] * astraljava finished hanging the laundry to dry, and grabbed a cider. [17:40] pleia2 can silence me if I start talking funny [17:40] hehe [17:41] Os_Maleus: Cool! [17:41] so the first is that we used to have a https://wiki.ubuntu.com/Xubuntu/Testing/Testers and we still link it on the website and say "Xubuntu Testers team at Launchpad, which you should join after adding your information on the wik" [17:41] on the web side I think I just need to remove this wiki link and adjust the text for the launchpad team to tell people they can just join [17:42] I followed a bunch of those dead links [17:42] (unless there is a defined new process that I missed) [17:42] hobgoblin: were there others? [17:43] yea - pretty sure - 2 secs [17:43] ah, https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo is gone too [17:43] pleia2: Yeah, it's set as an open team now. No listing of testers is there anymore. [17:43] ok, essentially we need to fix http://xubuntu.org/contribute/qa/#testing ASAP because there are broken links :) [17:43] I think I'll just delete "The Xubuntu Testing Info page, which explains the testing process, including describing the tests you should conduct" too [17:43] pleia2: Alright. Hit me when you wanna go over it. [17:43] I think that pretty much covers it actually [17:44] Or... that works as well. :) [17:44] the other thing I have is action plan for 1) final review of /Short 2) basic review and then final review of /Long 3) move these to QA wiki [17:44]