Re: [ jedit-Bugs-3418802 ] Problem with FTP plugin and open dialog

Hi Jarek,

Since you already made the specific item fully traceable, please read
the following as discussion in general term for the future.

Jarek Czekalski wrote:
> This is an expectation to be truly kind to a submitter. Here it is
> backed by his name to which I have great respect. But since the
> submitter is an expert he could read all of that between the lines. I
> expect a follow up from him like that: "I still experience the bug with
> trunk jedit and ftp". Developers don't need many words in conversations
> between them.

Comments on the tracker is read among many people (including those in
the future), not only by the submitter. You should try to write comments
without relying on volatile knowledge of the central players.

> And notice that expert should give his versions without
> being asked from a bug tracker technician. If he made a mistake not
> giving the version numbers and environment, he can do it now. Comments
> are always open when I close a bug.

Information from a submitter is wanted of course, but submitter's
omission is irrelevant to developer's omission which I'm pointing.

> But the main reason for me being not so kind and talkative is a simple
> fact. There is a 1000 of open bugs and only me to close them. Sorry, but
> I have not too much time for being delicate or very kind. I try to do
> the good job but must save my time.

Fair enough.

> Looking for the revision numbers in
> this case would be a waste of time. If I am to work so slowly on every
> bug, please tell me I should stop at all.

You felt it's a waste of time since you had an idea about the recent
fix. But I didn't know that since you didn't write that.

I believe you don't need much time to write some more words like "I
remember a recent fix for a bug like this, but can't tell the exact
revision right now."

Here are some links from producingoss about the issue:
http://www.producingoss.com/en/communications.html#you-are-what-you-write
   > Consider this: the only thing anyone knows about you on the Internet
   >  comes from what you write, ...
http://www.producingoss.com/en/communications.html#rudeness
   > ... People will assume you just didn't have time to say anything.
   >  But if you do react, don't skimp: ...

> Pending state. No. Pending state means in most cases that I will have to
> search bug database for pending entries, reread them and close one by
> one manually. If I have no-one to help me with that, I'll cut it quickly
> with "Closed (comments allowed)".

The absence of sf-robot is an unexpected situation, and must not change
the meaning of Pending state.

You don't have to reread expired Pending items. It is expected that such
items will be closed without rereading them.

Also, I don't see so much benefit to close them manually. I'll help it
if there are enough benefits. Otherwise I'll just wait sf-robot.

> Many bug tracker entries pass unanswered. This one not being an
> exception. It's me who did something with it after 6 months of being
> reported. I believe that submitters prefer a terse reaction than no
> reaction at all.

I agree.

At last, here are some links to back up my previous argument about
not-reproducible bugs.
http://www.google.com/search?q=bug+%22not+reproducible%22
The first 2 relevant pages:
   http://venkatreddyc.wordpress.com/2007/05/07/non-reproducible-bugs-how-to-deal-with-them/
   http://stackoverflow.com/questions/1050552/any-good-strategies-for-dealing-with-not-reproducible-bugs

-- 
k_satoda

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel