You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/08/16 19:00:40 UTC
[GitHub] [airflow-site] OmairK opened a new pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
OmairK opened a new pull request #280:
URL: https://github.com/apache/airflow-site/pull/280
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] mik-laj commented on pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
mik-laj commented on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-674566191
@mschickensoup, Can I ask for review?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] OmairK commented on a change in pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
OmairK commented on a change in pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#discussion_r474322247
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,29 @@
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of REST API(s) so I thought it
+would be easier to get started with the contributions. I had never contributed to FOSS before so this part
+was overwhelming but there were plenty of issues labelled “good first issues” with detailed descriptions and
+some even had code snippets so luckily that nudged me in the direction of my first PR.
+
+My first PR made me familiar with the feedback loop and those feedbacks on my subsequent PRs were the focal
Review comment:
That sounds fantastic! I have made this PR WIP for now. I want to add some more lines to this blog, I kinda skimped on some incidents related to my first PR :sweat_smile:.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] OmairK edited a comment on pull request #280: [WIP][Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
OmairK edited a comment on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-683133023
> Should we merge @OmairK ? Or do you plan to add more content ?
@potiuk I just remembered something I wanted to add. I will ping you for the review, sorry for any trouble.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] potiuk merged pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
potiuk merged pull request #280:
URL: https://github.com/apache/airflow-site/pull/280
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] potiuk commented on pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-683119214
Should we merge @OmairK ? Or do you plan to add more content ?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] potiuk commented on pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-683396612
Love it. Merging !
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] mik-laj removed a comment on pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
mik-laj removed a comment on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-674566074
@mschichensoup Can I ask for review?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] mik-laj commented on pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
mik-laj commented on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-674566074
@mschichensoup Can I ask for review?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] OmairK commented on pull request #280: [WIP][Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
OmairK commented on pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#issuecomment-683133023
> Should we merge @OmairK ? Or do you plan to add more content ?
> Should we merge @OmairK ? Or do you plan to add more content ?
@potiuk I just remembered something I wanted to add. I will ping you for the review, sorry for any trouble.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] OmairK commented on a change in pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
OmairK commented on a change in pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#discussion_r474322247
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,29 @@
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of REST API(s) so I thought it
+would be easier to get started with the contributions. I had never contributed to FOSS before so this part
+was overwhelming but there were plenty of issues labelled “good first issues” with detailed descriptions and
+some even had code snippets so luckily that nudged me in the direction of my first PR.
+
+My first PR made me familiar with the feedback loop and those feedbacks on my subsequent PRs were the focal
Review comment:
That sounds fantastic I have made this PR WIP for now. I want to add some more lines to this blog, I kinda skimped on some incidents related to my first PR :sweat_smile:.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] leahecole commented on a change in pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
leahecole commented on a change in pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#discussion_r474264430
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,29 @@
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of REST API(s) so I thought it
+would be easier to get started with the contributions. I had never contributed to FOSS before so this part
+was overwhelming but there were plenty of issues labelled “good first issues” with detailed descriptions and
+some even had code snippets so luckily that nudged me in the direction of my first PR.
+
+My first PR made me familiar with the feedback loop and those feedbacks on my subsequent PRs were the focal
+point of the overall learning experience. Through actively and passively participating in discussions I
+learnt that even if there is a difference of opinion I could always learn from the different approaches.
+Throughout my internship I learnt a lot about different frameworks and technologies but the biggest takeaway
+for me was that a code is read more often than its written, and I started writing code with that in mind.
Review comment:
Love this!! So true.
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,29 @@
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of REST API(s) so I thought it
+would be easier to get started with the contributions. I had never contributed to FOSS before so this part
+was overwhelming but there were plenty of issues labelled “good first issues” with detailed descriptions and
+some even had code snippets so luckily that nudged me in the direction of my first PR.
+
+My first PR made me familiar with the feedback loop and those feedbacks on my subsequent PRs were the focal
Review comment:
Consider linking to your PR on "my first PR" - I bet folks would love to see it! Additionally, consider listing your additional ones somewhere - not only will it give users some good examples of healthy PR discussions, it'll be a nice reference for you in the future :)
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,29 @@
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of REST API(s) so I thought it
+would be easier to get started with the contributions. I had never contributed to FOSS before so this part
+was overwhelming but there were plenty of issues labelled “good first issues” with detailed descriptions and
+some even had code snippets so luckily that nudged me in the direction of my first PR.
+
+My first PR made me familiar with the feedback loop and those feedbacks on my subsequent PRs were the focal
Review comment:
grammar nit - "those feedbacks" -> the feedback
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow-site] potiuk commented on a change in pull request #280: [Blog entry] Journey with Airflow as an Outreachy intern
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #280:
URL: https://github.com/apache/airflow-site/pull/280#discussion_r479744452
##########
File path: landing-pages/site/content/en/blog/experience-with-airflow-as-an-outreachy-intern.md
##########
@@ -0,0 +1,60 @@
+---
+title: "Journey with Airflow as an Outreachy Intern"
+linkTitle: "Journey with Airflow as an Outreachy Intern"
+author: "Omair Khan"
+github: "OmairK"
+linkedin: "omairkhan64"
+description: ""
+tags: [Community]
+date: "2020-08-15"
+draft: true
+---
+
+[Outreachy](https://www.outreachy.org/) is a program which organises three months paid internships with FOSS
+projects for people who are typically underrepresented in those projects.
+
+### Contribution Period
+The first thing I had to do was choose a project under an organisation. After going through all the projects
+I chose “Extending the REST API of Apache Airflow”, because I had a good idea of what REST API(s) are, so I
+thought it would be easier to get started with the contributions. The next step was to set up Airflow’s dev
+environment which thanks to [Breeze](https://github.com/apache/airflow/blob/master/BREEZE.rst), was a breeze.
+Since I had never contributed to FOSS before so this part was overwhelming but there were plenty of issues
+labelled “good first issues” with detailed descriptions and some even had code snippets so luckily that nudged
+me in the right direction. These things about Airflow and the positive vibes from the community were the reasons
+why I chose to stick with Airflow as my Outreachy project.
+
+### Internship Period
+My first PR was followed by many new experiences one of them being that I introduced a
+[bug](https://github.com/apache/airflow/pull/7680#issuecomment-619763051) in it;).
+But nonetheless it made me familiar with the feedback loop and the feedback on my subsequent
+[PRs](https://github.com/apache/airflow/pulls?q=is%3Apr+author%3AOmairK+) was the focal point of the overall
+learning experience I went through, which boosted my confidence to contribute more and move out of my comfort zone.
+I wanted to learn more about the things that happen under the Airflow’s hood so I started filtering out recent PRs
+dealing with different components and I would go through the code changes along with discussion that would help me
+get a better understanding of the whole workflow. [Airflow’s mailing list](https://lists.apache.org/list.html?dev@airflow.apache.org)
+was also a great source of knowledge.
+
+The API related PRs that I worked on helped me with some of the important concepts like:
+
+ 1) [Pool CRUD endpoints](https://github.com/apache/airflow/pull/9329) where pools limit the execution parallelism.
+
+ 2) [Tasks](https://github.com/apache/airflow/pull/9597) determine the actual work that has to be carried out.
+
+ 3) [DAG](https://github.com/apache/airflow/pull/9473) which represents the structure for a collection
+ of tasks. It keeps track of tasks, their dependencies and the sequence in which they have to run.
+
+ 4) [Dag Runs](https://github.com/apache/airflow/pull/9473) that are the instantiation of DAG(s) in time.
+
+Through actively and passively participating in discussions I learnt that even if there is a difference of opinion
+one could always learn from the different approaches, and [this PR](https://github.com/apache/airflow/pull/8721) with
+more than 300+ comments is the proof of it. I also started reviewing small PRs which gave me the amazing opportunity
+to interact with new people. Throughout my internship I learnt a lot about different frameworks and technologies
+but the biggest takeaway for me was that a code is read more often than it's written, and I started writing code with
+that in mind.
+
+### Wrapping Up
+So with my project of extending Airflow’s REST API as well as the Outreachy internship coming to an end I would like
+to thank my mentors [Jarek Poutik](https://github.com/potiuk), [Kaxil Naik](https://github.com/kaxil) and
Review comment:
```suggestion
to thank my mentors [Jarek Potiuk](https://github.com/potiuk), [Kaxil Naik](https://github.com/kaxil) and
```
----------------------------------------------------------------
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:
users@infra.apache.org