Yes, will do! On Wed, Feb 27, 2019, 15:00 Tao Feng <[email protected]> wrote:
> Hi Feng, > > Could you create a pr and put the doc into Airflow repo doc directory? > > Thanks, > -Tao > > On Wed, Feb 27, 2019 at 6:19 AM Driesprong, Fokko <[email protected]> > wrote: > >> +1 from my side, looking good. >> >> Op vr 22 feb. 2019 om 15:54 schreef Kaxil Naik <[email protected]>: >> >>> +1 from me as well. >>> >>> Either confluence of this is fine with me. >>> >>> Regards, >>> Kaxil >>> >>> On Fri, Feb 22, 2019 at 10:48 AM Tao Feng <[email protected]> wrote: >>> >>> > +1 from my side. Thanks Feng. >>> > >>> > On Thu, Feb 21, 2019 at 8:23 PM Feng Lu <[email protected]> >>> wrote: >>> > >>> >> Hi all, >>> >> >>> >> 20-ish people from the community have reviewed this doc. I believe we >>> have >>> >> addressed all comments and the doc is good to go. >>> >> Trying to figure out the right place to publish this GCP operator >>> style >>> >> guide doc, how about the Apache Airflow public doc site >>> >> <https://airflow.apache.org/>? Thinking of: Developer's Guide > GCP >>> >> Operator Style Guide. >>> >> Thoughts? >>> >> >>> >> Feng >>> >> >>> >> >>> >> On Sun, Oct 7, 2018 at 11:56 PM Feng Lu <[email protected]> wrote: >>> >> >>> >> > Hi all, >>> >> > >>> >> > A number of us worked on this GCP operator development style guide >>> and >>> >> > best practice doc, would like to share with everyone and get your >>> >> feedback. >>> >> > >>> >> > GCP Service Airflow Integration Guide >>> >> > < >>> >> >>> https://docs.google.com/document/d/1_rTdJSLCt0eyrAylmmgYc3yZr-_h51fVlnvMmWqhCkY/edit?ts=5bb72dfd#heading=h.3sxddzjr5f6q >>> >> > >>> >> > [*DRAFT*] >>> >> > >>> >> > Airflow committers, once this doc is finalized, any suggestion on >>> the >>> >> best >>> >> > place to host it? >>> >> > Thank you. >>> >> > >>> >> > Feng >>> >> > >>> >> > >>> >> > >>> >> >>> > >>> >>> -- >>> *Kaxil Naik* >>> *Big Data Consultant *@ *Data Reply UK* >>> *Certified *Google Cloud Data Engineer | *Certified* Apache Spark & Neo4j >>> Developer >>> *LinkedIn*: https://www.linkedin.com/in/kaxil >>> >>
