mik-laj commented on a change in pull request #225: Add Elena's GSOD impressions
URL: https://github.com/apache/airflow-site/pull/225#discussion_r362018719
 
 

 ##########
 File path: 
landing-pages/site/content/en/blog/documenting-using-local-development-environments.md
 ##########
 @@ -0,0 +1,43 @@
+---
+title: "Documenting using local development environment"
+linkTitle: "Documenting using local development environment"
+author: "Elena Fedotova"
+github: "efedotova"
+linkedin: "elena-fedotova-039294110"
+description: "The story behind documenting local development environment of 
Apache Airflow"
+tags: ["Development"]
+date: 2019-11-22
+---
+
+## Documenting local development environment of Apache Airflow
+
+From Sept to November, 2019 I have been participating in a wonderful 
initiative, [Google Season of 
Docs](https://developers.google.com/season-of-docs).
+
+I had a pleasure to contribute to the Apache Airflow open source project as a 
technical writer.
+My initial assignment was an extension to the github-based Contribution guide.
+
+From the very first days I have been pretty closely involved into 
inter-project communications
+via emails/slack and had regular 1:1s with my mentor, Jarek Potiuk.
+
+I got infected with Jarek’s enthusiasm to ease the on-boarding experience for
+Airflow contributors. I do share this strategy and did my best to improve the 
structure,
+language and DX. As a result, Jarek and I extended the current contributor’s 
docs and
+ended up with the Contributing guide navigating the users through the project
+infrastructure and providing a workflow example based on a real-life use case;
+the Testing guide with an overview of a complex testing infrastructure for 
Apache Airflow;
 
 Review comment:
   ``` 
   [the Testing 
guide](https://github.com/apache/airflow/blob/master/TESTING.rst) with an 
overview of a complex testing infrastructure for Apache Airflow;
   ```
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to