zrhoffman commented on issue #7456:
URL: 
https://github.com/apache/trafficcontrol/issues/7456#issuecomment-1931226180

   > I had guessed that the author of that PR opened it only because this issue 
exists.
   
   I could be wrong, but from the implementer's contribution history, I got the 
idea that they are using ATC in some capacity. So it stands to reason that, if 
they opened a PR, they would find practical benefit to the feature being 
implemented. In some cases, though maybe not this one, a contributor is even 
using the feature they are PRing before it is even merged.
   
   > Which is what this is, ultimately. I'd be more than happy to take this to 
the mailing list.
   
   Sure
   
   > But this is kind of totally standard procedure. Somebody proposed a 
change, I have concerns that it would ultimately be a net negative impact, and 
I voiced them. Then nobody else addressed - or even acknowledged - those 
concerns. So to somehow accuse me of standing in the way of something everyone 
wants is pretty strange to me.
   
   To be clear, I don't take issue with anything you've said, only that you 
-1ed the Issue on a contributor's PR. 
   
   > Requiring consensus on changes to the project isn't my dastardly plan to 
impede some specific PR, it's a founding principle of the ASF and older by far 
than this project. I'm just taking part, is all.
   
   Agreed, but IMO special care should be taken in cases when -1ing an Issue 
only after a contributor has submitted a PR for it, and that includes not -1ing 
the Issue on that PR. The will of users of ATC to give back to the project is 
often fragile and contributors are easily dissuaded, so we need to do what we 
can to instead encourage their contributions, even in cases where discussion on 
an Issue means that a contributor's corresponding PR is not likely to be 
accepted.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to