[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: bug in moving/overwriting a FOLDER
From:       Zé <mmodem00 () netvisao ! pt>
Date:       2004-11-16 15:34:57
Message-ID: 200411161534.57804.mmodem00 () netvisao ! pt
[Download RAW message or body]

Em Terça, 16 de Novembro de 2004 14:56, o Nathan Toone escreveu:
> A few things:
>         1 - Be patient.
>         2 - Don't include the whole thread in your replies - I read them
> already. 3 - Miscommunications happen - just restate your question if the
> wrong one was answered
>         4 - Remember that the KDE development community doesn't exist for
> you and you alone
>         5 - Log a bug on bugs.kde.org - it's designed for such things...and
> all the right developers see your bug report.  Then it can be prioritized.
> 6 - If it seems that the developers are moving slower than you like, you
> are more than welcome to try and fix the problem yourself.
>         7 - Believe it or not, this probably *isn't* the most important bug
> in there, but based on your postings, it seems to be a real hot item for
> you.  See number 5 and 6 above.
>         8 - Before coming to the kde-devel mailing list and making demands,
> over and over, and then bugging them less than a week later when it isn't
> fixed, try fixing it yourself and asking questions...kde-devel is not a
> place to make demands.  You'll get a lot further in your quests if you show
> that you are willing to put forth effort instead of trying to get a free
> ride.  Free software isn't a free ride...it requires work on your part too.
>
> -Nathan


If i would know how to develop in langage C i would be glad to help, 
unfortunely im steel a learning user of C#.
Meanwhile i thought would be good to going in report things that dont work 
well. 
And other thing, i dont demand, if its not possible to fix now that bugs i 
reported, thats ok.
I just want to contribut that kde be better.

Zé
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]