Re: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Kevin Yang
Excellent work! I really like it, esp. the documentation part. Thank you everyone who contributed to it đź‘Ť +1 for it is very subjective and I'm in favor of the moving elements. I'm not so sure how being a project for serious user would conflict with just showing some moving elements in the landing

Re: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Deng Xiaodong
Very nice work! - Personally I quite like the moving background elements, and I do not find it distracting. I believe this is very subjective, and we can discuss on each other’s preference forever. So... But anyway, if there will be any vote, mine is +1 for the current one. - At Documentation

Re: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Soma S Dhavala
On Sat, Nov 9, 2019 at 6:00 AM Aizhamal Nurmamat kyzy wrote: > Thank you both for your feedback. > > I really dislike the moving background elements on the lading page. I > > already found the previous example when they weren't moving hard to focus > > on other elements such as finding the header

Re: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Aizhamal Nurmamat kyzy
Thank you both for your feedback. I really dislike the moving background elements on the lading page. I > already found the previous example when they weren't moving hard to focus > on other elements such as finding the header menu and going to the > documentation, for me this is now easily twice

Re: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Ash Berlin-Taylor
Looking good overall, and a huge improvement in what we currently have! (Not sure how much of this is relevant at this stage) - On mobile the integration boxes are rather oversized (see screen shot of it attaches) - Those link to readthedocs - but they should link to versioned docs hosted on o

RE: [Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Shaw, Damian P.
Hi Aizhamal, I really dislike the moving background elements on the lading page. I already found the previous example when they weren't moving hard to focus on other elements such as finding the header menu and going to the documentation, for me this is now easily twice as worse. If no one else

[Final review] Airflow website + need your input to the web copy

2019-11-08 Thread Aizhamal Nurmamat kyzy
Hi everybody, We are super close to the final version of the Airflow website and we really need YOU to play with the prototype to make sure that everything is working properly. Here is the link: https://airflow-website-s5z26d2t7a-ew.a.run.app/ Please submit your feedback on the prototype in this

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Jarek Potiuk
Let me then cancel this vote and I will restart it next week. Yeah. It's a bit like re-opening the Pandora's box but now that we know that we can do it, and we are unblocked in moving to google (which is now the biggest move in-progress), we can spend more time on getting better (and more final)

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Kaxil Naik
Yes, that makes sense. On Fri, Nov 8, 2019 at 3:22 PM Kamil Breguła wrote: > In the case of Hadoop, it is published by Apache, so it can be in the > apache directory. This will mimic the grouping presented in the > documentation. > https://airflow.readthedocs.io/en/latest/operators-and-hooks-re

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Kamil Breguła
In the case of Hadoop, it is published by Apache, so it can be in the apache directory. This will mimic the grouping presented in the documentation. https://airflow.readthedocs.io/en/latest/operators-and-hooks-ref.html#software-operators-and-hooks On Fri, Nov 8, 2019 at 3:47 PM Kaxil Naik wrote

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Kaxil Naik
I think we should keep the vote open at least until mid next week to have more thought and inputs on this one. In general, I am happy with the approach but operators/hooks and sensors shouldn't be a provider. "hadoop" can be its provider and hdfs can be a part of it. providers/ google

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Jarek Potiuk
I really like to make everything a provider. That's a great idea ! This way everything "backportable" will have to be in "providers" package. Really nice and clean separation (and less mess in "airflow"). And we will not have to have any artificial grouping (we can still group them at the documenta

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Ash Berlin-Taylor
Do we need to include `-backport,`? What was the thinking behind that? I think software and protocol should be merged. I would also say _everything_ is a provider, so airflow.providers.ssh.SSHOperator for instance is what I would prefer -a On 8 November 2019 08:32:42 GMT, Jarek Potiuk wrote:

Re: [VOTE] AIP-21 update for Airflow 1.10.* backportability

2019-11-08 Thread Jarek Potiuk
One more day to go. I would love to see some opinions on this AIP-21 update :). Executive summary: * we will be moving a number of integrations to sub-packages of airflow. * they will be backportable to 1.10.*. There will be 'apache-airflow-[package]-backport' pypi installable with python 3 that