This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 74fc61aaab Publish built docs triggered by
90a821a061643763e9e7b2a36d4bbf275b6511f1
74fc61aaab is described below
commit 74fc61aaabcc9bb4100c2256ab4813a88546b43b
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jan 29 20:35:04 2024 +0000
Publish built docs triggered by 90a821a061643763e9e7b2a36d4bbf275b6511f1
---
_sources/contributor-guide/index.md.txt | 39 ++++++++++++++++++++++++++-------
contributor-guide/index.html | 37 ++++++++++++++++++++++++++-----
searchindex.js | 2 +-
3 files changed, 63 insertions(+), 15 deletions(-)
diff --git a/_sources/contributor-guide/index.md.txt
b/_sources/contributor-guide/index.md.txt
index da3908d7e1..a372d30f6c 100644
--- a/_sources/contributor-guide/index.md.txt
+++ b/_sources/contributor-guide/index.md.txt
@@ -19,17 +19,40 @@
# Introduction
-We welcome and encourage contributions of all kinds, such as:
+We welcome and encourage contributions of all kinds, from all levels, such as:
-1. Tickets with issue reports of feature requests
-2. Documentation improvements
-3. Code, both PR and (especially) PR Review.
+1. Tickets with issue reports or feature requests
+2. Discussions
+3. Documentation improvements
+4. Code, both PR and (especially) PR Review.
-In addition to submitting new PRs, we have a healthy tradition of community
members reviewing each other's PRs. Doing so is a great way to help the
community as well as get more familiar with Rust and the relevant codebases.
+In addition to submitting new PRs, we have a healthy tradition of community
+members reviewing each other's PRs. Doing so is a great way to help the
+community as well as get more familiar with Rust and the relevant codebases.
-You can find a curated
-[good-first-issue](https://github.com/apache/arrow-datafusion/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
-list to help you get started.
+## Finding and Creating Issues to Work On
+
+You can find a curated [good-first-issue] list to help you get started.
+
+DataFusion is an open contribution project, and thus there is no particular
+project imposed deadline for completing any issue or any restriction on who can
+work on an issue, nor how many people can work on an issue at the same time.
+
+Contributors drive the project forward based on their own priorities and
+interests and thus you are free to work on any issue that interests you.
+
+If someone is already working on an issue that you want or need but hasn't
+been able to finish it yet, you should feel free to work on it as well. In
+general it is both polite and will help avoid unnecessary duplication of work
if
+you leave a note on an issue when you start working on it.
+
+If you plan to work on a new feature that doesn't have an existing ticket, it
is
+a good idea to open a ticket to discuss the feature. Advanced discussion often
+helps avoid wasted effort by determining early if the feature is a good fit for
+DataFusion before too much time is invested. It also often helps to discuss
your
+ideas with the community to get feedback on implementation.
+
+[good-first-issue]:
https://github.com/apache/arrow-datafusion/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
# Developer's guide
diff --git a/contributor-guide/index.html b/contributor-guide/index.html
index 34f6bf4ea7..9319b40569 100644
--- a/contributor-guide/index.html
+++ b/contributor-guide/index.html
@@ -356,6 +356,13 @@
<a class="reference internal nav-link" href="#">
Introduction
</a>
+ <ul class="visible nav section-nav flex-column">
+ <li class="toc-h2 nav-item toc-entry">
+ <a class="reference internal nav-link"
href="#finding-and-creating-issues-to-work-on">
+ Finding and Creating Issues to Work On
+ </a>
+ </li>
+ </ul>
</li>
<li class="toc-h1 nav-item toc-entry">
<a class="reference internal nav-link" href="#developer-s-guide">
@@ -538,16 +545,34 @@
-->
<section id="introduction">
<h1>Introduction<a class="headerlink" href="#introduction" title="Link to this
heading">¶</a></h1>
-<p>We welcome and encourage contributions of all kinds, such as:</p>
+<p>We welcome and encourage contributions of all kinds, from all levels, such
as:</p>
<ol class="arabic simple">
-<li><p>Tickets with issue reports of feature requests</p></li>
+<li><p>Tickets with issue reports or feature requests</p></li>
+<li><p>Discussions</p></li>
<li><p>Documentation improvements</p></li>
<li><p>Code, both PR and (especially) PR Review.</p></li>
</ol>
-<p>In addition to submitting new PRs, we have a healthy tradition of community
members reviewing each other’s PRs. Doing so is a great way to help the
community as well as get more familiar with Rust and the relevant codebases.</p>
-<p>You can find a curated
-<a class="reference external"
href="https://github.com/apache/arrow-datafusion/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22";>good-first-issue</a>
-list to help you get started.</p>
+<p>In addition to submitting new PRs, we have a healthy tradition of community
+members reviewing each other’s PRs. Doing so is a great way to help the
+community as well as get more familiar with Rust and the relevant
codebases.</p>
+<section id="finding-and-creating-issues-to-work-on">
+<h2>Finding and Creating Issues to Work On<a class="headerlink"
href="#finding-and-creating-issues-to-work-on" title="Link to this
heading">¶</a></h2>
+<p>You can find a curated <a class="reference external"
href="https://github.com/apache/arrow-datafusion/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22";>good-first-issue</a>
list to help you get started.</p>
+<p>DataFusion is an open contribution project, and thus there is no particular
+project imposed deadline for completing any issue or any restriction on who can
+work on an issue, nor how many people can work on an issue at the same
time.</p>
+<p>Contributors drive the project forward based on their own priorities and
+interests and thus you are free to work on any issue that interests you.</p>
+<p>If someone is already working on an issue that you want or need but hasn’t
+been able to finish it yet, you should feel free to work on it as well. In
+general it is both polite and will help avoid unnecessary duplication of work
if
+you leave a note on an issue when you start working on it.</p>
+<p>If you plan to work on a new feature that doesn’t have an existing ticket,
it is
+a good idea to open a ticket to discuss the feature. Advanced discussion often
+helps avoid wasted effort by determining early if the feature is a good fit for
+DataFusion before too much time is invested. It also often helps to discuss
your
+ideas with the community to get feedback on implementation.</p>
+</section>
</section>
<section id="developer-s-guide">
<h1>Developer’s guide<a class="headerlink" href="#developer-s-guide"
title="Link to this heading">¶</a></h1>
diff --git a/searchindex.js b/searchindex.js
index cd6ba71766..6152e7e07a 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["contributor-guide/architecture",
"contributor-guide/communication", "contributor-guide/index",
"contributor-guide/quarterly_roadmap", "contributor-guide/roadmap",
"contributor-guide/specification/index",
"contributor-guide/specification/invariants",
"contributor-guide/specification/output-field-name-semantic", "index",
"library-user-guide/adding-udfs", "library-user-guide/building-logical-plans",
"library-user-guide/catalogs", "library-user-guide/custom-tab [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["contributor-guide/architecture",
"contributor-guide/communication", "contributor-guide/index",
"contributor-guide/quarterly_roadmap", "contributor-guide/roadmap",
"contributor-guide/specification/index",
"contributor-guide/specification/invariants",
"contributor-guide/specification/output-field-name-semantic", "index",
"library-user-guide/adding-udfs", "library-user-guide/building-logical-plans",
"library-user-guide/catalogs", "library-user-guide/custom-tab [...]
\ No newline at end of file
