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/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a1f1c053f6 Publish built docs triggered by
24f1bb5418fb9e452649cecf84d2c058b07858ca
a1f1c053f6 is described below
commit a1f1c053f6d238f504829fd0bc1e194e047b82f4
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jun 16 21:19:27 2025 +0000
Publish built docs triggered by 24f1bb5418fb9e452649cecf84d2c058b07858ca
---
_sources/contributor-guide/index.md.txt | 20 ++++++++++++++++++++
contributor-guide/index.html | 23 +++++++++++++++++++++++
searchindex.js | 2 +-
3 files changed, 44 insertions(+), 1 deletion(-)
diff --git a/_sources/contributor-guide/index.md.txt
b/_sources/contributor-guide/index.md.txt
index e38898db5a..a4e3e4cb94 100644
--- a/_sources/contributor-guide/index.md.txt
+++ b/_sources/contributor-guide/index.md.txt
@@ -108,6 +108,26 @@ Features above) prior to acceptance include:
[extensions list]: ../library-user-guide/extensions.md
[design goal]:
https://docs.rs/datafusion/latest/datafusion/index.html#design-goals
+### Design Build vs. Big Up Front Design
+
+Typically, the DataFusion community attacks large problems by solving them bit
+by bit and refining a solution iteratively on the `main` branch as a series of
+Pull Requests. This is different from projects which front-load the effort
+with a more comprehensive design process.
+
+By "advancing the front" the community always makes tangible progress, and the
strategy is
+especially effective in a project that relies on individual contributors who
may
+not have the time or resources to invest in a large upfront design effort.
+However, this "bit by bit approach" doesn't always succeed, and sometimes we
get
+stuck or go down the wrong path and then change directions.
+
+Our process necessarily results in imperfect solutions being the "state of the
+code" in some cases, and larger visions are not yet fully realized. However,
the
+community is good at driving things to completion in the long run. If you see
+something that needs improvement or an area that is not yet fully realized,
+please consider submitting an issue or PR to improve it. We are always looking
+for more contributions.
+
# Developer's guide
## Pull Request Overview
diff --git a/contributor-guide/index.html b/contributor-guide/index.html
index 100ddb9fb0..09b19d7e16 100644
--- a/contributor-guide/index.html
+++ b/contributor-guide/index.html
@@ -579,6 +579,11 @@
What Contributions are Good Fits?
</a>
</li>
+ <li class="toc-h3 nav-item toc-entry">
+ <a class="reference internal nav-link"
href="#design-build-vs-big-up-front-design">
+ Design Build vs. Big Up Front Design
+ </a>
+ </li>
</ul>
</li>
</ul>
@@ -752,6 +757,24 @@ Features above) prior to acceptance include:</p>
<li><p>New data sources (e.g. support for Apache ORC)</p></li>
</ol>
</section>
+<section id="design-build-vs-big-up-front-design">
+<h3>Design Build vs. Big Up Front Design<a class="headerlink"
href="#design-build-vs-big-up-front-design" title="Link to this
heading">¶</a></h3>
+<p>Typically, the DataFusion community attacks large problems by solving them
bit
+by bit and refining a solution iteratively on the <code class="docutils
literal notranslate"><span class="pre">main</span></code> branch as a series of
+Pull Requests. This is different from projects which front-load the effort
+with a more comprehensive design process.</p>
+<p>By “advancing the front” the community always makes tangible progress, and
the strategy is
+especially effective in a project that relies on individual contributors who
may
+not have the time or resources to invest in a large upfront design effort.
+However, this “bit by bit approach” doesn’t always succeed, and sometimes we
get
+stuck or go down the wrong path and then change directions.</p>
+<p>Our process necessarily results in imperfect solutions being the “state of
the
+code” in some cases, and larger visions are not yet fully realized. However,
the
+community is good at driving things to completion in the long run. If you see
+something that needs improvement or an area that is not yet fully realized,
+please consider submitting an issue or PR to improve it. We are always looking
+for more contributions.</p>
+</section>
</section>
</section>
<section id="developer-s-guide">
diff --git a/searchindex.js b/searchindex.js
index 5bdc3cc386..9a988b5457 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[57,"op-neq"]],"!~":[[57,"op-re-not-match"]],"!~*":[[57,"op-re-not-match-i"]],"!~~":[[57,"id19"]],"!~~*":[[57,"id20"]],"#":[[57,"op-bit-xor"]],"%":[[57,"op-modulo"]],"&":[[57,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[12,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[57,"op-multiply"]],"+":[[57,"op-plus"]],"-":[[57,"op-minus"]],"/":[[57,"op-divide"]],"2022
Q2":[[10,"q2"]] [...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[57,"op-neq"]],"!~":[[57,"op-re-not-match"]],"!~*":[[57,"op-re-not-match-i"]],"!~~":[[57,"id19"]],"!~~*":[[57,"id20"]],"#":[[57,"op-bit-xor"]],"%":[[57,"op-modulo"]],"&":[[57,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[12,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[57,"op-multiply"]],"+":[[57,"op-plus"]],"-":[[57,"op-minus"]],"/":[[57,"op-divide"]],"2022
Q2":[[10,"q2"]] [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org
