[Chapter-delegates] Bug in the AMS system

[Franck Martin]

Alex,

The solution is rather simpler, a public bug list, like bugzilla.

You have a place to register your bug, and to see the progress of fixing it and get a message once it is fixed.

You can also search to see if you are the only one or not, vote for the bugs that are important to you,..etc,etc..

Obscurity in an organization like ISOC, is never good and lead to these kind of extreme behavior

Franck Martin 
http://www.avonsys.com/ 
http://www.facebook.com/Avonsys 
twitter: FranckMartin Avonsys 

Check your domain reputation: http://gurl.im/b69d4o 


----- Original Message -----
From: "Alejandro Pisanty" <apisan at servidor.unam.mx>
To: "Sabrina Wilmot" <wilmot at isoc.org>
Cc: "Chapter Delegates" <chapter-delegates at elists.isoc.org>
Sent: Friday, 13 August, 2010 6:39:29 AM
Subject: Re: [Chapter-delegates] Bug in the AMS system

Sabrina,

I will take exception to the use of "polluting" in the sense you've used 
it here; I find it excessive.

I do think that most bug reports should be made discreetly and directly to 
those responsible for confirming and repairing them. We all know bugs, and 
we should therefore know we never are 100% sure what we find is actually a 
bug.

And, there is no need to leverage the power of the group just to report a 
bug. In fact that conduct can be nasty and useless, and only cause hurt in 
relationships in the long run.

But... there is also room for discussion that must be preserved. We may 
not be sure if something is going wrong and wish to ask colleagues whether 
they are seeing the same as we do, for example, or warn others about it, 
which is not going to happen by the silent route.

So I guess we can all agree that it better to report bugs to the people 
who can act on them, but can't really forbid their discussion on the list.

Yours,

Alejandro Pisanty