[openstreetmap/openstreetmap-website] Maps.me added data producing double name & no messages answers (#1761)

Tom Hughes tom at compton.nu
Mon Feb 26 13:19:27 UTC 2018


[ Moving this off the issue tracker and back to the mailing list
   where it was probably intended to be all along ]

On 26/02/18 12:58, Matt Amos wrote:

> Let's all try and keep this positive and friendly.

Sure.

> This is a public forum, so there are going to be some reports or 
> comments in which the author - intentionally or otherwise - belittles 
> existing contributions or contributors. I think it's best in those 
> situations to try, gently and politely, to explain why such an attitude 
> is unhelpful, while also trying to accept those parts of the report or 
> comment which describe real problems or bugs that we need to address.

The problem is our bug tracker is such an utter cesspit that I mostly
feel like I'm just drowning and it's all I can do to try and stop it
getting any deeper which mostly means trying to close as much stuff
as I can as quickly as I can.

We really need to throw away all our labels and then go through every
single bug and either close it or add a sensible label and then have a
concrete triage system that ensures every new bug is cleaned up and
classified with a proper label.

As you probably know I'm not a great fan of "feature request" tickets
if only because historically very few of them ever get implemented but
if we clearly label them as feature requests and have a process for
doing an initial review of whether they are worthwhile so that they
can be closed if necessary then maybe that would work? I'm not sure
how such a process would work though :-( Maybe also auto-close them
if nobody has done anything about them after a certain period?

Basically I really want to make this work but right now I mostly
feel like the little dutch boy with his thumb in the dyke and a
tidal wave breaking over the top of it constantly.

Tom

-- 
Tom Hughes (tom at compton.nu)
http://compton.nu/



More information about the rails-dev mailing list