[06:17] <xequence> First day of debconf
[06:25] <knome> :)
[06:25] <knome> shouldn't your nick be debuence?
[06:31] <xequence> knome: maybe next year :). This year I feel more like a tourist.
[06:39] <smartboyhw> zequence, yeah
[06:41] <smartboyhw> xequence, ^
[06:42] <smartboyhw> knome, it should be dequence rather
[07:42] <smartboyhw> Hey xequence 
[07:42] <smartboyhw> How's Debconf?
[07:57] <xequence> smartboyhw: Great weather. Introduction just started.
[07:57] <xequence> Met some Canonical folks just now
[07:58] <xequence> cjwatson and stgraber among others
[07:59] <smartboyhw> xequence, great
[13:09] <smartboyhw> xequence, (or zequence) When will you send out the e-mail to call for testcase writing?
[14:48] <xequence> smartboyhw: As soon as I've established a structure for how and by whom the the test should be written
[14:49] <smartboyhw> xequence, by whom? ...
[14:49] <smartboyhw> How is easier than "by whom" I think
[14:49] <smartboyhw> The community writes testcases:)
[14:49] <smartboyhw> *more difficult actually;P
[14:49] <smartboyhw> How: Propose merge
[14:49] <xequence> http://en.wiktionary.org/wiki/whom
[14:50] <smartboyhw> xequence, I know, but how = propose merge and whom = community
[14:50] <xequence> That much is clear, yes
[14:50] <smartboyhw> How can that be difficult:P
[14:50] <xequence> smartboyhw: Nothing is difficult
[14:51] <xequence> it's just a matter of doing, and doing well
[14:51] <smartboyhw> xequence, I know, but I don't think the "structure" is different from what we are using in main QA team
[14:51] <xequence> smartboyhw: What would you look for when writing a test for ardour?
[14:52] <smartboyhw> xequence, quality, typos, formatting
[14:52] <smartboyhw> And of course, testing:)
[14:52] <xequence> I don have time to chat right now. bbl
[14:52] <xequence> smartboyhw: your missing the point
[14:52] <smartboyhw> xequence, ...
[14:52] <xequence> to be able to write a test for ardour, you need to be an ardour user
[14:53] <xequence> many of these applications are quite different from other kinds of applications
[14:53] <xequence> you dont simply look for typos
[14:54] <xequence> in that case we can skip testing all together
[14:54] <smartboyhw> xequence, uh huh... But of course you have to be an Ardour user to write the test...
[14:55] <xequence> the tests should be written for long term use
[14:55] <xequence> and we need documentation for this stuff
[14:55] <smartboyhw> xequence, yes (as in the others)
[14:56] <smartboyhw> xequence, what do you mean by "documentation"?
[14:56] <xequence> smartboyhw: Since you seem to know how this is done, why don you prepare a proposal for me?
[14:56] <smartboyhw> xequence, I just don't understand what you are meaning by "documentation"?!?
[14:56] <xequence> I'll happily accept one within the week
[14:57] <xequence> smartboyhw: Do you think you will have time for it?
[14:57] <smartboyhw> xequence, answer me first...
[14:57] <smartboyhw> If you want "HOWTO write", you can just refer to all the QATeam wiki
[14:58] <smartboyhw> If you want how to test, again, the QATeam wiki
[14:58] <xequence> smartboyhw: I don't need your advice in this matter smartboyhw. And I'm done wasting my time right now
[14:58] <xequence> either you do it, or I do it
[14:58]  * smartboyhw still can't understand why a proposal is needed, sorry
[14:59] <xequence> then I do it
[14:59] <smartboyhw> xequence, sure
[15:00] <smartboyhw> OvenWerks, what do you think about this? ^