airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yajna pandith <yajnanpand...@gmail.com>
Subject Re: Clarification request from Season of doc Mentor (SDOC2019)
Date Mon, 13 May 2019 14:06:53 GMT
Thank you for your response.
I have gone through the links and i have started writing my proposal .
Just wanted to know,
1) What is expected of a proposal .
2) On what factors will the proposal be judged.

Thanks,
Yajna.

On Sat, May 11, 2019 at 4:16 AM Aizhamal Nurmamat kyzy <aizhamal@google.com>
wrote:

> Hi Yanja,
>
> In Apache Airflow architecture documentation, we are looking to have the
> following expected deliverables [1]. I think it will be best if you start
> digging into existing relevant documentation on scheduler, worker, web
> server, explore PlantUML, and start drafting your proposal to submit to the
> Google program administrators during the technical writer application
> phase. If you want any  feedback for your draft, consider using Google Docs
> and share, so we can leave our comments and suggestions (please check the
> access to the doc before sending to the mailing list).
>
> We also opened a Slack channel to discuss issues related to documentation
> [2]. Once you create an account join #documentation channel.
>
> Hope it helps. Let me know if you have more questions.
>
> Thanks,
> Aizhamal
>
>
> [1]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Season+of+Docs+2019
> [2] https://apache-airflow-slack.herokuapp.com/
>
> *From: *yajna pandith <yajnanpandith@gmail.com>
> *Date: *Fri, May 10, 2019 at 9:50 AM
> *To: * <dev@airflow.apache.org>
>
> Hello Mentors of SDOC2019,
>>
>> I am interested in documenting Apache Airflow architecture. Further would
>> like to discuss with you on the contents of the proposal and suitability
>> of
>> my profile .
>>
>> Appreciate a response from your end .
>>
>> Thanks
>> Yajna
>> 1st year Engineering [Electronics and communication]
>> Pes University
>> Bangalore  India.
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message