airflow-site
airflow-site copied to clipboard
apache
Update _index.md
Well. one comment here @dabla - I think you should not publish it under apache-airflow-providers-* name. While we do not have a way to prevent it - this might be misleading to publish it with the apache-airflow- prefix, that it is an Apache Software Foundation project.
Since you are managing it on your own - I would strongly suggest you to choose a different name and remove the apache-airflow-* or - even better - remove it and pass the ownership of the project to the Apache Airflow organization so that it is not misused.
This might change in the future, where organization and provenance of the packages in PyPi is more visible, also we do not have written rules about it, so this is more of a kind request rather than requirement, but I think it would be good to follow this approach - that is currently pretty much universal - where apache-airflow- prefix is for the projects that are managed by the Apache Airflow PMC.
Would that be possible @dabla ?
Well. one comment here @dabla - I think you should not publish it under
apache-airflow-providers-*name. While we do not have a way to prevent it - this might be misleading to publish it with theapache-airflow-prefix, that it is an Apache Software Foundation project.Since you are managing it on your own - I would strongly suggest you to choose a different name and remove the
apache-airflow-*or - even better - remove it and pass the ownership of the project to the Apache Airflow organization so that it is not misused.This might change in the future, where organization and provenance of the packages in PyPi is more visible, also we do not have written rules about it, so this is more of a kind request rather than requirement, but I think it would be good to follow this approach - that is currently pretty much universal - where
apache-airflow-prefix is for the projects that are managed by the Apache Airflow PMC.Would that be possible @dabla ?
Hello Jarek (@potiuk),
Well if possible I would like to hand over the provider to the Apache Airflow project, as this was the whole point from the start, at least if there is interest in it... otherwise I will rename the provider and remove the apache prefixed one from pypi. I started a discussion about that operator at the end of last year at the Airflow project: https://github.com/apache/airflow/discussions/36315
While awaiting a decission about that discussion (a vote is required if I understood well), I opted to already deploy it to pypi so it is open source and others can profit from it as well and maybe even improve it and do contributions. If Airflow would take over the provider that would of course be even better.
We have multiple DAG's interacting with MS Graph API endpoints, and as we want to avoid custom code as much as possible as we have to handle lot's of data due to paging. We though of implementing an operator for it using the official python client from Microsoft, that way we can simplify our dags and remove custom code as much as possible.
Please start discussion about it at the devlist https://airflow.apache.org/community/
We have multiple DAG's interacting with MS Graph API endpoints, and as we want to avoid custom code as much as possible as we have to handle lot's of data due to paging. We though of implementing an operator for it using the official python client from Microsoft, that way we can simplify our dags and remove custom code as much as possible.
Discussion started in [email protected]
I think we can close this PR in favor of https://github.com/apache/airflow/pull/38111 ?
I think we can close this PR in favor of apache/airflow#38111 ?
Hey Elad yes this one can be closed.