potiuk edited a comment on issue #14396:
URL: https://github.com/apache/airflow/issues/14396#issuecomment-937630215


   100% what @kaxil wrote. There is no "bar" to clean (and we are not going to 
close it). 
   
   I was merely answering your question @r-richmond  - you asked for the 
additional context so I did:
   
   >  Can you provide any additional context?
   
   The context is - in open-source project if no-one is interested in working 
on the issue, it will not get implemented. It's as simple as that. 
   
   So answer "why" things are pushed back is very simple - it's not pushed 
back. Simply NOONE (including maintainers) is finding it worthy to work on it. 
And it does not mean that the issue is invalid - it just means it's either not 
urgent enough or not important enough to spend our time on it. If you now the 
"urgent/not-urgent" vs. " important/not-important" matrix - it means it falls 
into "not-urgent and not-important". There plenty of other issues that fall 
into the 3 other squares in the matrix. And this "matrix" is different for 
different individuals - i.e. it can be "urgent" or "important" for various 
resons for YOU, but apparently it's not for most other people. 
   
   So if YOU think it's either important or urgent, then the best way to get it 
done (if no-one else does not think the same) is that YOU take a lead and 
implement it.
   
   And if it's not gonna be commented or worked on for quite some time it will 
be closed automatically - because that will mean that even the author lost 
interest in it.
   
   It's reallly really as simple and straightforward as this. There is no 
politics, there is no-one to decide which issue we are working or not (except 
that every one of the people involved - either committer or contributor) makes 
individual decision "this is what I am going to work on next" . 


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