Dear Airflow maintainers,
Please accept this PR. I understand that it will
not be reviewed until I have checked off all the
steps below!
- [x] My PR addresses the following [Airflow JIRA]
(https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For
example, "[AIRFLOW-XXX] My Airflow PR"
-
https://issues.apache.org/jira/browse/AIRFLOW-1603
- [x] Here are some details about my PR, including
screenshots of any UI changes:
- added my company to README.md
- [x] My PR adds the following unit tests __OR__
does not need testing for this extremely good
reason:
- [x] My commits all reference JIRA issues in
their subject lines, and I have squashed multiple
commits if they address the same issue. In
addition, my commits follow the guidelines from
"[How to write a good git commit
message](http://chris.beams.io/posts/git-
commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not
"adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Closes#2603 from matthiashuschle/pr2
Dear Airflow maintainers,
Please accept this PR. I understand that it will
not be reviewed until I have checked off all the
steps below!
### JIRA
- [/] My PR addresses the following [Airflow JIRA]
(https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For
example, "[AIRFLOW-XXX] My Airflow PR"
-
https://issues.apache.org/jira/browse/AIRFLOW-108
### Description
- [/] Here are some details about my PR, including
screenshots of any UI changes:
Adding an entry to the companies list in README.md
file.
### Tests
- [/] My PR adds the following unit tests __OR__
does not need testing for this extremely good
reason: Documentation change only.
### Commits
- [/] My commits all reference JIRA issues in
their subject lines, and I have squashed multiple
commits if they address the same issue. In
addition, my commits follow the guidelines from
"[How to write a good git commit
message](http://chris.beams.io/posts/git-
commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not
"adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Closes#2554 from r39132/master
added to currently **officially** using Airflow:
[California Data Collaborative](http://californiad
atacollaborative.org) powered by [ARGO
Labs](http://www.argolabs.org)
Dear Airflow maintainers,
Please accept this PR. I understand that it will
not be reviewed until I have checked off all the
steps below!
- [x] My PR addresses the following [Airflow JIRA]
**https://issues.apache.org/jira/browse/AIRFLOW-13
84**
- The California Data Collaborative is a unique
coalition of forward thinking municipal water
managers in California who along with ARGO, a
startup non-profit that builds, operates, and
maintains data infrastructures, are pioneering new
standards of collaborating around and
administering water data for millions
Californians.
ARGO has deployed a hosted version of Airflow on
AWS and it is used to orchestrate data pipelines
to parse water use data from participating
utilities to power analytics. Furthermore, ARGO
also uses Airflow to power a data infrastructure
for citywide street maintenance via
https://github.com/ARGO-SQUID
- [x] My PR adds the following unit tests __OR__
does not need testing for this extremely good
reason:
Change to README.md does not require unit testing.
- [x] My commits all reference JIRA issues in
their subject lines, and I have squashed multiple
commits if they address the same issue. In
addition, my commits follow the guidelines from
"[How to write a good git commit
message](http://chris.beams.io/posts/git-
commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not
"adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Update README.md
added to currently **officially** using Airflow
section of README.md
[California Data Collaborative](https://github.com
/California-Data-Collaborative) powered by [ARGO
Labs](http://www.argolabs.org)
Added CaDC/ARGO Labs to README.md
Please consider adding [Argo
Labs](www.argolabs.org) to the Airflow users
section.
**Context**
- The California Data Collaborative is a unique
coalition of forward thinking municipal water
managers in California who along with ARGO, a
startup non-profit that builds, operates, and
maintains data infrastructures, are pioneering new
standards of collaborating around and
administering water data for millions
Californians.
- ARGO has deployed a hosted version of Airflow on
AWS and it is used to orchestrate data pipelines
to parse water use data from participating
utilities to power analytics. Furthermore, ARGO
also uses Airflow to power a data infrastructure
for citywide street maintenance via
https://github.com/ARGO-SQUIDCloses#2421 from vr00n/patch-3
Matthew Housley
Austin Gibbons
Sasa Brankovic
Romain NIO
Stéphanie Baltus
WS Hoekstra
Daniel Huang
Walkoss
Dustin Stansbury
Sid Anand
Andy Cooper
Daniel Cassiano
Duy
Jacob Trunsky
Clinton Boys
Alexis Rosuel
Kaxil Naik
lindsey anne
Jetsada Machom
Andy Hadjigeorgiou
warthur
Mahendra Yadav
Michael Crawford
Keeon
Bolke de Bruin
matthiashuschle
Thomas Buida
Adam Boscarino
Felipe Sabino
Varun
Maxime Beauchemin
Siva Pandeti
Kevin Gao
Richard Garcia
Tanmay
Yu ISHIKAWA
Greg Finley
Abhijeet Dhumal
David Clubb
Ignasi Peiró
Antoine Augusti
Ace Haidrey
Marc Weil
Siddharth Anand
Hamed Saljooghinejad
Maxime Beauchemin
zkan
Tongbo Huang
