potiuk commented on issue #22298: URL: https://github.com/apache/airflow/issues/22298#issuecomment-1668488612
> We know exactly what needs to be changed, but I have no experience contributing to open source projects, so I ask that you guys can do this, please, because it would be easier and faster. You cannot be more wrong. No. It's NOT easier nor faster. In many cases it's just not happening if you thinl "someone else will obviously do it". In most cases, what happens if you don't do it and there is no-one interested in fixing it, it will just ... not get implemented. It's not "you" and "we" here. We are all same community. Maintainers (committers) are mostly there to make sure the code is in good order and take care of the direction of the project. And they can veto some proposals. Look it up - Airflow is ceated by more than 2500 contributors. Mostly people who knew what they missed and contributed it. Generally the idea is that if you care about something and can convince others, then you implement it and submit PR to improve it. This is how open-source works. > It is necessary to change the order of [this list](https://github.com/apache/airflow/blob/v2-6-stable/airflow/kubernetes/pod_generator.py#L422) to [base_worker_pod, dynamic_pod, pod_override_object]. Then multiNamespaceMode works! Sure - make an appealing case. Explain why it works and why it did not work before. Make a PR. Add tests. Ping reviewers if you don't get response. Otherwise you see exactly what haappens - "more than a year and nothing happened" . Yes. And I would say it's because you knew it can be fixed, you knew how and during the year you have done nothing to fix it. (all the things from the list above). -- 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]
