Marking people's bugs as INVALID is great, but do add a word why. Which bug? I mean in general. Customer relations principles still apply, paid staff or volunteer.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dan Jacobson wrote:
Marking people's bugs as INVALID is great, but do add a word why. Which bug? I mean in general. Customer relations principles still apply, paid staff or volunteer.
Well, it would probably help if you didn't flood the bug queue with duplicates and vague issues every few days. ;)
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
On 2/5/07, Brion Vibber brion@pobox.com wrote:
Well, it would probably help if you didn't flood the bug queue with duplicates and vague issues every few days. ;)
Where can one see this bug queue?
Steve
On 2/4/07, Steve Bennett stevagewp@gmail.com wrote:
On 2/5/07, Brion Vibber brion@pobox.com wrote:
Well, it would probably help if you didn't flood the bug queue with duplicates and vague issues every few days. ;)
Where can one see this bug queue?
bugs.wikimedia.org
On 04/02/07, Steve Bennett stevagewp@gmail.com wrote:
On 2/5/07, Brion Vibber brion@pobox.com wrote:
Well, it would probably help if you didn't flood the bug queue with duplicates and vague issues every few days. ;)
Where can one see this bug queue?
There's a mailing list which most developers and other interested parties are subscribed to that receives details of changes to bugs, rather than having individual component owners. Bug spam and mass posting of unhelpful bugs and comments shows up in our inboxes, and can get irritating.
Rob Church
wikitech-l@lists.wikimedia.org