Hello there

[Carlos Leonhard Woelz]

On Friday 05 March 2004 21:45, Mark Berry wrote:
> Ok,
>
> I appologize ahead if I am not reading something, or if your repeating
> instructions you already gave me.  I am just trying to get the process
> down of what I should be doing to help, as to not waste valuable testing
> time.

Not at all, we are here for that. Your doubt can be the doubt of others.

> I have built a bleeding edge version of KDE out of CVS and have it
> running in a second X term (yay). 

Congratulations! The first build is kind of tricky

> I have the khtmltests module checked 
> out, and now I am sorta lost on what I should do next.

Have you checked

http://quality.kde.org/develop/howto/howtobugs.php ?

> I have an account setup on bugzilla, and I have been spending a bit of
> time reading other various reports trying to get a feel of what style is
> used when posting a bug.
>
> I am not sure what I am supposed to be doing now though ;-/ .   Should I
> pick a bug, such as :
>
> http://bugs.kde.org/show_bug.cgi?id=33903
>
>
> Now , I pop open the bug.. and it looks like it's very complete.  A test
> case is already completed and various people have already commented on it.

This bug is a great example of how bugs should be handled. The developers can 
take the testcases and put in the khtmltests to ensure that the bug will not 
reappear.

> Should I be looking for newer bugs, such as :
>
> http://bugs.kde.org/show_bug.cgi?id=76811

Here you should test for the bug using head, and tell if it is valid or not.

> I hope I am not sounding too pushy by asking for explicit direction on
> where my time is best spent.  I haven't much experience yet working with
> Open Source projects of this size, and just want to make sure that my
> time is very well spent and productive.  Once I have an effective
> procedure sorted out and a task ahead of me, I should be able to chug
> away and hopefully help make our fav desktop tools even better. :)

As I said, not at all. In fact, I am very happy you are asking all this 
questions, because that's why the project was created.

First: don't worry when you feel you cannot judge the bug: go to the next one. 
You will get better as you go. You could at first take care at first only of 
rendering problems and try to extract test cases or see if the problem 
persist with head.

Cheers,

Carlos Woelz