sbp commented on PR #456:
URL: 
https://github.com/apache/tooling-trusted-releases/pull/456#issuecomment-3724186869

   @developer-ravi-03 Thanks for the detailed reply! You can update this PR or 
make a new PR at your option. Please see [special considerations for 
ATR](https://release-test.apache.org/docs/how-to-contribute#special-considerations-for-atr)
 for more detailed notes about why and how our contribution process is 
different from ASF TLPs. ASF Tooling is not a TLP.
   
   The fact that you were able to use a non-existent interface indicates two 
things:
   
   1. You did not run the server to test your changes.
   2. You did not run pre-commit lints.
   
   We have a [guide to running the 
server](https://release-test.apache.org/docs/running-the-server). For the 
lints, we obviously run those lints in GitHub workflows as well, but we always 
run the lints locally before pushing, because there's no point in anybody 
reviewing a PR which is still failing lints. Testing and linting contributions 
is a minimal requirement.
   
   Again, we appreciate the fact that you're contributing to ATR as a 
volunteer, giving us your free time to help us and enhance our project. At the 
same time, we are receiving so many unusual (and low quality) PRs that we don't 
know how to handle them as a broad policy. I would still, therefore, like to 
understand more about your motivations for contribution. What is it, for 
example, that attracted you to contribute to ATR rather than one of the many 
thousands of other open source projects? What would be your advice to us to 
attract a higher number of contributors, of high quality?
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to