You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/02/07 19:08:16 UTC

[GitHub] [airflow] potiuk edited a comment on issue #21336: Override the dag run_id from within the ui

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


   > I'm confused, why does this not require a feature request? 
   
   Because we work on PR base. If the PR is accepted, it is merged. This is how a governance in an open source world (and in Airflow in particular) work. There is no-one to 'accept' feature requests so it cannot be 'accepted'. It can be rejected and closed if there is is a justified -1 from a committer though. 
   
   And even if people think a feature is good and there is a consensus about it, l it might never be implemented if no-one, well, implement it.
   
   So the most certain way to implement a feature if you want it is to ... Implement it as a PR yourself. Or pick someone's interest and convince them to implement it. Or mark it as a good first issue and hope someone will pick it as their first issue if this is an easy fix.
   
   That's why you do not need issues - good PR is enough. But if a change is big you want to discuss it before PR to check if there is a consensus on  this being good direction. And it might turn you need to create and vote on Airflow Improvement Proposal, when both change is really big.
   
   Airflow has more than 1900 contributors BTW.
   
   You can take a look at our CONTRIBUTING.rst for more details 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org