[airflow-site] branch master updated: Add Elena's GSOD impressions (#225)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 41eb4bb  Add Elena's GSOD impressions (#225)
41eb4bb is described below

commit 41eb4bb5bc0951414d5bd84b7da67636ef61bcf1
Author: Jarek Potiuk <ja...@polidea.com>
AuthorDate: Mon Dec 30 16:35:47 2019 +0100

    Add Elena's GSOD impressions (#225)
---
 ...menting-using-local-development-environments.md | 43 ++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/landing-pages/site/content/en/blog/documenting-using-local-development-environments.md b/landing-pages/site/content/en/blog/documenting-using-local-development-environments.md
new file mode 100644
index 0000000..60cd33f
--- /dev/null
+++ b/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;
+and two guides dedicated to the Breeze dev environment and local virtual environment
+(my initial assignment).
+
+I’m deeply grateful to my mentor and Airflow developers for their feedback,
+patience and help while I was breaking through new challenges
+(I’ve never worked on an open source project before),
+and for their support of all my ideas! I think a key success factor for any contributor
+is a responsive, supportive and motivated team, and I was lucky to join such
+a team for 3 months.
+
+Documents I worked on:
+
+* [Breeze development environment documentation](https://github.com/apache/airflow/blob/master/BREEZE.rst)
+* [Local virtualenv environment documentation](https://github.com/apache/airflow/blob/master/LOCAL_VIRTUALENV.rst)
+* [Contributing guide](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst)
+* [Testing guide](https://github.com/apache/airflow/blob/master/TESTING.rst)