[ 
https://issues.apache.org/jira/browse/AIRFLOW-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509450#comment-16509450
 ] 

Verdan Mahmood edited comment on AIRFLOW-2598 at 6/12/18 10:00 AM:
-------------------------------------------------------------------

Facebook actually removed all the BSD + Patent-licensed code from ReactJS last 
year with the launch of React 16. (which was the reason ASF took the drastic 
step of banning the library)
 React is now MIT licensed.
 ref: [https://github.com/facebook/react/blob/master/LICENSE]


was (Author: verdan):
Facebook actually removed all the BSD + Patent-licensed code from ReactJS 
(which was the reason ASF took the drastic step of banning the library) last 
year with the launch of React 16. 
React is now MIT licensed. 
ref: https://github.com/facebook/react/blob/master/LICENSE

> Migrate Airflow to ReactJS
> --------------------------
>
>                 Key: AIRFLOW-2598
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2598
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webapp
>            Reporter: Verdan Mahmood
>            Priority: Major
>              Labels: frontend
>
> Hi guys, 
> In an effort to make the frontend of Apache Airflow more interactive and 
> feature-rich, I am planning to migrate the frontend to ReactJS.
> The whole idea involves adding/updating the backend APIs and redesigning the 
> frontend in ReactJS, along with fixing bugs and improving layouts. This issue 
> is the starting point to discuss the need, process and timeline to make it 
> happen collectively.
> For the next couple of weeks I would be working on backend in order to add 
> remaining APIs and make them ready for the frontend use. Question: Do we have 
> any kind of documentation or list of existing and outstanding APIs (roadmap)?
> I am hoping to get your input on how to structure the frontend code, so that 
> we can deliver more frequently and incrementally in the best possible way. It 
> could be a separate repository or a directory within the same repository. 
> Thoughts? It would be great if I can also get some feedback on UI/UX, as 
> whether to keep it same or do some user research to improve that?
> Note: I'll make sure to keep the backward compatibility in mind all the time 
> while doing that :) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to