If your company doesn’t allow the doc to be public please create it on a personal account. We can’t comment
I agree with what Jarek said though, and also: Why does this need to be _in_ core Airflow at all? Given that it is possible to extend the Webserver via plugins, what in your proposal (that I can’t yet read, so maybe there is something) couldn’t be done as just a “third” party module? -ash > On 15 Nov 2023, at 19:44, Yulei Li <yule...@pinterest.com.INVALID> wrote: > > Hi Ash, > > Missed your email, unfortunately my organization disabled the Google Doc > option to share the Doc Link that is readable to everyone, so I tried to > grant the read access to the "dev@airflow.apache.org" email alias but it > did not work. > > I have granted commenter permissions to all the requests that I have > received. But if it makes it easier, I can convert the Doc into an AIP > <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals>, > just need to request edit access to it. And my Wiki ID is: *yuleili*. Thanks > > Best, > Yulei > > On Fri, Nov 10, 2023 at 4:16 AM Ash Berlin-Taylor <a...@apache.org> wrote: > >> Please make the document readable by anyone with the link. >> >> Thanks, >> Ash >> >>> On 9 Nov 2023, at 21:10, Yulei Li <yule...@pinterest.com.INVALID> wrote: >>> >>> Hi Airflow community, >>> >>> My name is Yulei and I'm a software engineer from the Workflow Platform >>> team at Pinterest. On behalf of the Workflow Platform team and the >>> Analytics Platform team at Pinterest, I would like to raise an AIP to the >>> open source community to discuss the proposal to build a "UI DAG >> Composer" >>> into Airflow. >>> >>> At Pinterest, we built our internal workflow system on top of Airflow. >> And >>> over the past few years, we have done intensive development on the system >>> and built customizations to meet the workflow orchestration requirements >> of >>> our internal customers. >>> >>> Currently, the two teams are working on building a feature that brings >> the >>> "UI-based" workflow composing experience into our "internal Airflow" >>> system. The motivation of this project is: >>> >>> - Enable our internal customers who might not be familiar with coding >> to >>> be able to use Airflow. >>> - Consolidate our internal systems to simplify the product offerings. >>> >>> Given that, the goal of the project is to build an “UI Composer” into the >>> Airflow system and expose it from the Airflow UI. Users can then utilize >> it >>> to build their workflow without the need to know the underlying Airflow >> DAG >>> domain specific language (DSL). >>> >>> As we are working on this project internally, we would also like to >> propose >>> this feature to the Airflow community and discuss the potential of >>> contributing it back to open source, since we believe this feature can be >>> beneficial to other users/organizations as well. >>> >>> You can find the details of the proposal in this Google doc: [AIP >> Proposal] >>> Airflow UI DAG Composer >>> < >> https://docs.google.com/document/d/1KGrLj1vSmtsNXRyj909xO8-niB1s5db35bPuM7FQuXc/edit#heading=h.mnaz328tvctz >>> >>> (please >>> request access if you hit any access issue with the doc). We would love >> to >>> hear your inputs/feedback, thanks in advance. >>> >>> Best, >>> Yulei >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org >> For additional commands, e-mail: dev-h...@airflow.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
