potiuk commented on PR #25732:
URL: https://github.com/apache/airflow/pull/25732#issuecomment-1218089432

   > Please, next time you are working on an issue that is assigned to someone 
else, please notify the issue. I do not want to sound rude, but it is simple 
fact that I just wasted time on this because I implemented it as well. Time 
that could have been spent more wisely.
   
   I think the problem was .... you were not assigned @sbrandtb :). It was 
likely an omission :) when you read all the conversation it looked like you 
wanted to work on it , but yeah - it's our fault we have not assigned you.
   
   BTW. I think it's quite expected that there is some duplication of work. 
There is also a value in doing stuff (learning). Merging is not the ultimate 
and only value, the process of making PR. getting reviews and feedback is 
valuable as well. There is no sane way to make sure that there is no 
duplication of work, but when you realise this is not the only value, you get 
more acceptance of doing stuff in parallel by different people. Code is often 
liability and if you get others contribute the code you came with as an idea, 
this is actually cool opportunity to work on it together.
   
   Since this PR is alrady out - in the spirit of what I wrote above - I'd 
encourage you @sbrandtb to turn into reviewer here and make your comments and 
help with leading that to completion. There is even bigger value in being 
reviewer when such code is contributed - you learn how to communicate your 
review comments, you learn how to look at the change with other perspective and 
you will likely notice things that you wouldn't have noticed when you wrote it. 
And a good learning experience too.
   
   At the end "Community over code" is what matters most (this is the ASF 
motto).


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