<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body>
<br>
Ok, <br>
<br>
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.<br>
<br>
I have built a bleeding edge version of KDE out of CVS and have it
running in a second X term (yay). I have the khtmltests module checked
out, and now I am sorta lost on what I should do next. <br>
<br>
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.<br>
<br>
I am not sure what I am supposed to be doing now though ;-/ . Should
I pick a bug, such as :<br>
<br>
<a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=33903">http://bugs.kde.org/show_bug.cgi?id=33903</a><br>
<br>
<br>
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. <br>
<br>
Should I be looking for newer bugs, such as :<br>
<br>
<a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=76811">http://bugs.kde.org/show_bug.cgi?id=76811</a><br>
<br>
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. :)<br>
<br>
I look forward to helping chip-away at whatever I can, I love to feel
like I am helping things progress. Helping smack bugs down in bugzilla
is a very measurable way of accomplishing that. :)<br>
<br>
Thanks again in advance for the response, and for your patience,
hopefully I am not missing the wide open clues to answer my own
questions ;/ <br>
<br>
Cheers<br>
<br>
.mark <br>
<br>
Carlos Leonhard Woelz wrote:
<blockquote
cite="mid1078532191.6102.182193018@webmail.messagingengine.com"
type="cite">
<pre wrap="">On Fri, 05 Mar 2004 02:24:13 -0800, "Mark Berry" <a class="moz-txt-link-rfc2396E" href="mailto:mark@bx2.net"><mark@bx2.net></a> said:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
I was recommended to come here and see if I could help you guys out with
some testing. Any tips for a newbie getting started? I suppose I need
the advanced KFM testing framework, and access to the bug database.
1. Where is the bug database located, do we use bugzilla? Where can I
read on where to get started with procedures on that and whats expected
in terms of bug reports and testing reports.
</pre>
</blockquote>
<pre wrap=""><!---->
Bugs database:
<a class="moz-txt-link-freetext" href="http://bugs.kde.org">http://bugs.kde.org</a>
It is bugzilla based indeed.
</pre>
<blockquote type="cite">
<pre wrap="">2. Is there documentation on the KFM testing framework, and where can I
get a hold of that software and begin work.
</pre>
</blockquote>
<pre wrap=""><!---->
There is the khtmltests module on KDE CVS.
</pre>
<blockquote type="cite">
<pre wrap="">I am very anxious to get started and help where I can. If you can point
me in the right direction, and surely answer a few silly questions (I am
guaranteed to have a few), I hope to be a great asset to your team.
</pre>
</blockquote>
<pre wrap=""><!----> ^^^^^^^^^^
_Our team_ :)
For questions about general volunteer support and general KDE stuff,
please use and subscribe to the kde-quality mailing list. For specific
KFM and khtmltests questions, subscribe to kfm-devel and post there. Do
you kfm developers have something else to add?
Cheers,
</pre>
</blockquote>
<br>
</body>
</html>