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/12/06 10:18:14 UTC
[GitHub] [airflow] eladkal commented on a change in pull request #12617: Moved Contributors' Guide to CONTRIBUTING.rst file
eladkal commented on a change in pull request #12617:
URL: https://github.com/apache/airflow/pull/12617#discussion_r537005460
##########
File path: CONTRIBUTING.rst
##########
@@ -20,9 +20,55 @@
Contributions
=============
-Contributions are welcome and are greatly appreciated! Every little bit helps,
+Contributions to Airflow are welcome and are greatly appreciated! Every little bit helps,
and credit will always be given.
+We would like more people to use, contribute to, and help maintain Airflow.
+These three goals align with the three main membership roles within our community:
+users, contributors, and committers/maintainers.
+
+We would like to instill a sense of ownership and pride among the members of our community
+by encouraging:
+
+- people to use Airflow
+- users to contribute ro Airflow
+- contributors to become committers
+
+You can contribute to Airflow in various ways such as:
+
+- reporting bug
+- suggesting new features and Road Map items
+- submitting Pull Requests (PRs) for bug fixes and new features.
+- attending Airflow meets-up events near you:
+
+ - search for Airflow `Meetup <https://www.meetup.com/>`_
Review comment:
I wouldn't say that attending to a meetup considered contributing.
##########
File path: CONTRIBUTING.rst
##########
@@ -20,9 +20,55 @@
Contributions
=============
-Contributions are welcome and are greatly appreciated! Every little bit helps,
+Contributions to Airflow are welcome and are greatly appreciated! Every little bit helps,
and credit will always be given.
+We would like more people to use, contribute to, and help maintain Airflow.
+These three goals align with the three main membership roles within our community:
+users, contributors, and committers/maintainers.
+
+We would like to instill a sense of ownership and pride among the members of our community
+by encouraging:
+
+- people to use Airflow
+- users to contribute ro Airflow
+- contributors to become committers
+
+You can contribute to Airflow in various ways such as:
+
+- reporting bug
+- suggesting new features and Road Map items
+- submitting Pull Requests (PRs) for bug fixes and new features.
+- attending Airflow meets-up events near you:
+
+ - search for Airflow `Meetup <https://www.meetup.com/>`_
+
+- helping to answer questions on gitter, the dev email list, PRs, and Jiras.
+
+
+Best Ways of Engaging Yourself in the Community
+-----------------------------------------------
+
+There are several ways for members to connect meaningfully in the community.
+These include:
+
+- Sending an email to: `<de...@airflow.incubator.apache.org>`_
+
+ - This is the best way to get a Committer to answer a question.
Review comment:
We do not encourage asking troubleshooting questions in the dev mailing list.
The dev mailing list is to discuss the development of the project, voting on releases/AIPs.
Troubleshooting questions can be asked on troubleshooting channel in Slack or in Stackoverflow
##########
File path: CONTRIBUTING.rst
##########
@@ -20,9 +20,55 @@
Contributions
=============
-Contributions are welcome and are greatly appreciated! Every little bit helps,
+Contributions to Airflow are welcome and are greatly appreciated! Every little bit helps,
and credit will always be given.
+We would like more people to use, contribute to, and help maintain Airflow.
+These three goals align with the three main membership roles within our community:
+users, contributors, and committers/maintainers.
+
+We would like to instill a sense of ownership and pride among the members of our community
+by encouraging:
+
+- people to use Airflow
+- users to contribute ro Airflow
+- contributors to become committers
+
+You can contribute to Airflow in various ways such as:
+
+- reporting bug
+- suggesting new features and Road Map items
+- submitting Pull Requests (PRs) for bug fixes and new features.
+- attending Airflow meets-up events near you:
+
+ - search for Airflow `Meetup <https://www.meetup.com/>`_
+
+- helping to answer questions on gitter, the dev email list, PRs, and Jiras.
+
+
+Best Ways of Engaging Yourself in the Community
+-----------------------------------------------
+
+There are several ways for members to connect meaningfully in the community.
+These include:
+
+- Sending an email to: `<de...@airflow.incubator.apache.org>`_
+
+ - This is the best way to get a Committer to answer a question.
+
+- Open a JIRA ticket when you discover a bug and propose a PR with a fix.
Review comment:
We moved from Jira to GitHub issues.
##########
File path: CONTRIBUTING.rst
##########
@@ -20,9 +20,55 @@
Contributions
=============
-Contributions are welcome and are greatly appreciated! Every little bit helps,
+Contributions to Airflow are welcome and are greatly appreciated! Every little bit helps,
and credit will always be given.
+We would like more people to use, contribute to, and help maintain Airflow.
+These three goals align with the three main membership roles within our community:
+users, contributors, and committers/maintainers.
+
+We would like to instill a sense of ownership and pride among the members of our community
+by encouraging:
+
+- people to use Airflow
+- users to contribute ro Airflow
+- contributors to become committers
+
+You can contribute to Airflow in various ways such as:
+
+- reporting bug
+- suggesting new features and Road Map items
+- submitting Pull Requests (PRs) for bug fixes and new features.
+- attending Airflow meets-up events near you:
+
+ - search for Airflow `Meetup <https://www.meetup.com/>`_
+
+- helping to answer questions on gitter, the dev email list, PRs, and Jiras.
Review comment:
Gitter and Jira are not used any more.
##########
File path: CONTRIBUTING.rst
##########
@@ -20,9 +20,55 @@
Contributions
=============
-Contributions are welcome and are greatly appreciated! Every little bit helps,
+Contributions to Airflow are welcome and are greatly appreciated! Every little bit helps,
and credit will always be given.
+We would like more people to use, contribute to, and help maintain Airflow.
+These three goals align with the three main membership roles within our community:
+users, contributors, and committers/maintainers.
+
+We would like to instill a sense of ownership and pride among the members of our community
+by encouraging:
+
+- people to use Airflow
+- users to contribute ro Airflow
+- contributors to become committers
+
+You can contribute to Airflow in various ways such as:
+
+- reporting bug
+- suggesting new features and Road Map items
+- submitting Pull Requests (PRs) for bug fixes and new features.
+- attending Airflow meets-up events near you:
+
+ - search for Airflow `Meetup <https://www.meetup.com/>`_
+
+- helping to answer questions on gitter, the dev email list, PRs, and Jiras.
+
+
+Best Ways of Engaging Yourself in the Community
+-----------------------------------------------
+
+There are several ways for members to connect meaningfully in the community.
+These include:
+
+- Sending an email to: `<de...@airflow.incubator.apache.org>`_
+
+ - This is the best way to get a Committer to answer a question.
+
+- Open a JIRA ticket when you discover a bug and propose a PR with a fix.
+
+ - This is the only way to get PRs approved or to report bugs.
+
+
+Is Your Company Using Airflow?
+------------------------------
+
+If so, then add your company name (along with your Github handle) as links to the
+`README.md <https://github.com/apache/airflow/blob/master/README.md#who-uses-apache-airflow>`_
+and submit a PR (with associated JIRA). We will be happy to merge it.
Review comment:
The file is [INTHEWILD.md](https://github.com/apache/airflow/blob/master/INTHEWILD.md)
Would be better to refer to https://github.com/apache/airflow/issues/12012
----------------------------------------------------------------
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