Hello there

[Henry W. Miller]

Well the short answer is fix whichever you want and can.  It appears that
nobody is working on either of these (though I am not the one to ask, and
I'm not even sure who is), so either would be a big help.  It is more a
matter of what you can fix, both should be fixed.

There a Votes line that suggests how interested people are in various
reports.   From the vote line it appears that these two are not
interesting enough for someone to vote for them.   However votes don't
have much meaning until they get > 100 votes IMHO.   (which accounts for 5
people caring).   Even then I don't care about votes, but someone should.
Note though that if a bug gets alot of votes it is likely a complex task
that may require significant work to fix, you might want to start
elsewhere to get your feet wet.

The next quesiton is can you duplicate the problem?   I've seen a number
of bugs that I don't have the hardware to duplicate.  If you have strange
hardware (USB memory cards, multipul monitors...) I suggest starting with
bugs related to those areas because not everyone has the ability to make
progress there.

Or in the case of the two problems you pointed out, I'm unable to
duplicate 76811, as is the one other commenter.  My guess is a
configuration issue, something that needs to be sorted out and documented,
not a place for code changes.  A good place to start if you are not much a
coder, but are good at dealing with configurations.

Note, you don't need to fix a bug that you start on.  If you conclude it
is over your head, just write comment to the bug on what you have found so
far.   76811 might be a really simple bug to fix once we know how to
make it happen.   The guys who really know kde are busy, if you can spend
10 hours to save them 1 hour of work, we are still better off.  (You know
more about KDE, and they have saved an hour)

Old bugs in a well maintained program (konqueror for example) often imply
something is complex, otherwise why hasn't it been fixed already.  Old
bugs in a less updated program mean that you should take over that
program!

Good luck.

-- 
Henry Miller       hank at black-hole.com

On Fri, 5 Mar 2004, 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.
>
> 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.
>
> 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.
>
> Should I be looking for newer bugs, such as :
>
> http://bugs.kde.org/show_bug.cgi?id=76811
>
> 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. :)
>
> 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. :)
>
> 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 ;/
>
> Cheers
>
> .mark
>
> Carlos Leonhard Woelz wrote:
>
> >On Fri, 05 Mar 2004 02:24:13 -0800, "Mark Berry" <mark at bx2.net> said:
> >
> >
> >>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.
> >>
> >>
> >
> >
> >Bugs database:
> >
> >http://bugs.kde.org
> >
> >It is bugzilla based indeed.
> >
> >
> >
> >
> >>2.  Is there documentation on the KFM testing framework, and where can I
> >>get a hold of that software and begin work.
> >>
> >>
> >
> >There is the khtmltests module on KDE CVS.
> >
> >
> >
> >>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.
> >>
> >>
> >                                                           ^^^^^^^^^^
> >_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,
> >
> >
>
>