You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by gi...@apache.org on 2023/11/12 16:13:21 UTC
(arrow-datafusion) branch asf-site updated: Publish built docs triggered by f33244a646f97f0355eab3195d4b89eff3b602c2
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 577fb53c7d Publish built docs triggered by f33244a646f97f0355eab3195d4b89eff3b602c2
577fb53c7d is described below
commit 577fb53c7d1aed3a7a8625458b06cddd4b4231fc
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Sun Nov 12 16:13:16 2023 +0000
Publish built docs triggered by f33244a646f97f0355eab3195d4b89eff3b602c2
---
_sources/contributor-guide/communication.md.txt | 50 +++++-----------
_sources/index.rst.txt | 3 +-
contributor-guide/communication.html | 80 +++++++++----------------
index.html | 2 +-
searchindex.js | 2 +-
5 files changed, 47 insertions(+), 90 deletions(-)
diff --git a/_sources/contributor-guide/communication.md.txt b/_sources/contributor-guide/communication.md.txt
index 11e0e4e0f0..8678aa534b 100644
--- a/_sources/contributor-guide/communication.md.txt
+++ b/_sources/contributor-guide/communication.md.txt
@@ -26,15 +26,25 @@ All participation in the Apache Arrow DataFusion project is governed by the
Apache Software Foundation's [code of
conduct](https://www.apache.org/foundation/policies/conduct.html).
+## GitHub
+
The vast majority of communication occurs in the open on our
-[github repository](https://github.com/apache/arrow-datafusion).
+[github repository](https://github.com/apache/arrow-datafusion) in the form of tickets, issues, discussions, and Pull Requests.
+
+## Slack and Discord
-## Questions?
+We use the Slack and Discord platforms for informal discussions and coordination. These are great places to
+meet other contributors and get guidance on where to contribute. It is important to note that any technical designs and
+decisions are made fully in the open, on GitHub.
-### Mailing list
+Most of us use the `#arrow-datafusion` and `#arrow-rust` channels in the [ASF Slack workspace](https://s.apache.org/slack-invite) .
+Unfortunately, due to spammers, the ASF Slack workspace requires an invitation to join. To get an invitation,
+request one in the `Arrow Rust` channel of the [Arrow Rust Discord server](https://discord.gg/Qw5gKqHxUM).
-We use arrow.apache.org's `dev@` mailing list for project management, release
-coordination and design discussions
+## Mailing list
+
+We also use arrow.apache.org's `dev@` mailing list for release coordination and occasional design discussions. Other
+than the the release process, most DataFusion mailing list traffic will link to a GitHub issue or PR for discussion.
([subscribe](mailto:dev-subscribe@arrow.apache.org),
[unsubscribe](mailto:dev-unsubscribe@arrow.apache.org),
[archives](https://lists.apache.org/list.html?dev@arrow.apache.org)).
@@ -42,33 +52,3 @@ coordination and design discussions
When emailing the dev list, please make sure to prefix the subject line with a
`[DataFusion]` tag, e.g. `"[DataFusion] New API for remote data sources"`, so
that the appropriate people in the Apache Arrow community notice the message.
-
-### Slack and Discord
-
-We use the official [ASF](https://s.apache.org/slack-invite) Slack workspace
-for informal discussions and coordination. This is a great place to meet other
-contributors and get guidance on where to contribute. Join us in the
-`#arrow-rust` channel.
-
-We also have a backup Arrow Rust Discord
-server ([invite link](https://discord.gg/Qw5gKqHxUM)) in case you are not able
-to join the Slack workspace. If you need an invite to the Slack workspace, you
-can also ask for one in our Discord server.
-
-### Sync up video calls
-
-We have biweekly sync calls every other Thursdays at both 04:00 UTC
-and 16:00 UTC (starting September 30, 2021) depending on if there are
-items on the agenda to discuss and someone being willing to host.
-
-Please see the [agenda](https://docs.google.com/document/d/1atCVnoff5SR4eM4Lwf2M1BBJTY6g3_HUNR6qswYJW_U/edit)
-for the video call link, add topics and to see what others plan to discuss.
-
-The goals of these calls are:
-
-1. Help "put a face to the name" of some of other contributors we are working with
-2. Discuss / synchronize on the goals and major initiatives from different stakeholders to identify areas where more alignment is needed
-
-No decisions are made on the call and anything of substance will be discussed on the mailing list or in github issues / google docs.
-
-We will send a summary of all sync ups to the dev@arrow.apache.org mailing list.
diff --git a/_sources/index.rst.txt b/_sources/index.rst.txt
index bb8e2127f1..3853716617 100644
--- a/_sources/index.rst.txt
+++ b/_sources/index.rst.txt
@@ -43,11 +43,12 @@ community.
The `example usage`_ section in the user guide and the `datafusion-examples`_ code in the crate contain information on using DataFusion.
-The `developer’s guide`_ contains information on how to contribute.
+Please see the `developer’s guide`_ for contributing and `communication`_ for getting in touch with us.
.. _example usage: user-guide/example-usage.html
.. _datafusion-examples: https://github.com/apache/arrow-datafusion/tree/master/datafusion-examples
.. _developer’s guide: contributor-guide/index.html#developer-s-guide
+.. _communication: contributor-guide/communication.html
.. _toc.links:
.. toctree::
diff --git a/contributor-guide/communication.html b/contributor-guide/communication.html
index 360f02b42a..b128721e8b 100644
--- a/contributor-guide/communication.html
+++ b/contributor-guide/communication.html
@@ -347,26 +347,19 @@
<nav id="bd-toc-nav">
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry">
- <a class="reference internal nav-link" href="#questions">
- Questions?
+ <a class="reference internal nav-link" href="#github">
+ GitHub
+ </a>
+ </li>
+ <li class="toc-h2 nav-item toc-entry">
+ <a class="reference internal nav-link" href="#slack-and-discord">
+ Slack and Discord
+ </a>
+ </li>
+ <li class="toc-h2 nav-item toc-entry">
+ <a class="reference internal nav-link" href="#mailing-list">
+ Mailing list
</a>
- <ul class="nav section-nav flex-column">
- <li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link" href="#mailing-list">
- Mailing list
- </a>
- </li>
- <li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link" href="#slack-and-discord">
- Slack and Discord
- </a>
- </li>
- <li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link" href="#sync-up-video-calls">
- Sync up video calls
- </a>
- </li>
- </ul>
</li>
</ul>
@@ -421,14 +414,24 @@ questions, and get involved.</p>
<p>All participation in the Apache Arrow DataFusion project is governed by the
Apache Software Foundation’s <a class="reference external" href="https://www.apache.org/foundation/policies/conduct.html">code of
conduct</a>.</p>
+<section id="github">
+<h2>GitHub<a class="headerlink" href="#github" title="Link to this heading">¶</a></h2>
<p>The vast majority of communication occurs in the open on our
-<a class="reference external" href="https://github.com/apache/arrow-datafusion">github repository</a>.</p>
-<section id="questions">
-<h2>Questions?<a class="headerlink" href="#questions" title="Link to this heading">¶</a></h2>
+<a class="reference external" href="https://github.com/apache/arrow-datafusion">github repository</a> in the form of tickets, issues, discussions, and Pull Requests.</p>
+</section>
+<section id="slack-and-discord">
+<h2>Slack and Discord<a class="headerlink" href="#slack-and-discord" title="Link to this heading">¶</a></h2>
+<p>We use the Slack and Discord platforms for informal discussions and coordination. These are great places to
+meet other contributors and get guidance on where to contribute. It is important to note that any technical designs and
+decisions are made fully in the open, on GitHub.</p>
+<p>Most of us use the <code class="docutils literal notranslate"><span class="pre">#arrow-datafusion</span></code> and <code class="docutils literal notranslate"><span class="pre">#arrow-rust</span></code> channels in the <a class="reference external" href="https://s.apache.org/slack-invite">ASF Slack workspace</a> .
+Unfortunately, due to spammers, the ASF Slack workspace requires an invitation to join. To get an invitation,
+request one in the <code class="docutils literal notranslate"><span class="pre">Arrow</span> <span class="pre">Rust</span></code> channel of the <a class="reference external" href="https://discord.gg/Qw5gKqHxUM">Arrow Rust Discord server</a>.</p>
+</section>
<section id="mailing-list">
-<h3>Mailing list<a class="headerlink" href="#mailing-list" title="Link to this heading">¶</a></h3>
-<p>We use arrow.apache.org’s <code class="docutils literal notranslate"><span class="pre">dev@</span></code> mailing list for project management, release
-coordination and design discussions
+<h2>Mailing list<a class="headerlink" href="#mailing-list" title="Link to this heading">¶</a></h2>
+<p>We also use arrow.apache.org’s <code class="docutils literal notranslate"><span class="pre">dev@</span></code> mailing list for release coordination and occasional design discussions. Other
+than the the release process, most DataFusion mailing list traffic will link to a GitHub issue or PR for discussion.
(<a class="reference external" href="mailto:dev-subscribe%40arrow.apache.org">subscribe</a>,
<a class="reference external" href="mailto:dev-unsubscribe%40arrow.apache.org">unsubscribe</a>,
<a class="reference external" href="https://lists.apache.org/list.html?dev@arrow.apache.org">archives</a>).</p>
@@ -436,33 +439,6 @@ coordination and design discussions
<code class="docutils literal notranslate"><span class="pre">[DataFusion]</span></code> tag, e.g. <code class="docutils literal notranslate"><span class="pre">"[DataFusion]</span> <span class="pre">New</span> <span class="pre">API</span> <span class="pre">for</span> <span class="pre">remote</span> <span class="pre">data</span> <span class="pre">sources"</span></code>, so
that the appropriate people in the Apache Arrow community notice the message.</p>
</section>
-<section id="slack-and-discord">
-<h3>Slack and Discord<a class="headerlink" href="#slack-and-discord" title="Link to this heading">¶</a></h3>
-<p>We use the official <a class="reference external" href="https://s.apache.org/slack-invite">ASF</a> Slack workspace
-for informal discussions and coordination. This is a great place to meet other
-contributors and get guidance on where to contribute. Join us in the
-<code class="docutils literal notranslate"><span class="pre">#arrow-rust</span></code> channel.</p>
-<p>We also have a backup Arrow Rust Discord
-server (<a class="reference external" href="https://discord.gg/Qw5gKqHxUM">invite link</a>) in case you are not able
-to join the Slack workspace. If you need an invite to the Slack workspace, you
-can also ask for one in our Discord server.</p>
-</section>
-<section id="sync-up-video-calls">
-<h3>Sync up video calls<a class="headerlink" href="#sync-up-video-calls" title="Link to this heading">¶</a></h3>
-<p>We have biweekly sync calls every other Thursdays at both 04:00 UTC
-and 16:00 UTC (starting September 30, 2021) depending on if there are
-items on the agenda to discuss and someone being willing to host.</p>
-<p>Please see the <a class="reference external" href="https://docs.google.com/document/d/1atCVnoff5SR4eM4Lwf2M1BBJTY6g3_HUNR6qswYJW_U/edit">agenda</a>
-for the video call link, add topics and to see what others plan to discuss.</p>
-<p>The goals of these calls are:</p>
-<ol class="arabic simple">
-<li><p>Help “put a face to the name” of some of other contributors we are working with</p></li>
-<li><p>Discuss / synchronize on the goals and major initiatives from different stakeholders to identify areas where more alignment is needed</p></li>
-</ol>
-<p>No decisions are made on the call and anything of substance will be discussed on the mailing list or in github issues / google docs.</p>
-<p>We will send a summary of all sync ups to the dev@arrow.apache.org mailing list.</p>
-</section>
-</section>
</section>
diff --git a/index.html b/index.html
index 0c83ea619e..391fa14e25 100644
--- a/index.html
+++ b/index.html
@@ -384,7 +384,7 @@ in-memory format.</p>
CSV, Parquet, JSON, and Avro, extensive customization, and a great
community.</p>
<p>The <a class="reference external" href="user-guide/example-usage.html">example usage</a> section in the user guide and the <a class="reference external" href="https://github.com/apache/arrow-datafusion/tree/master/datafusion-examples">datafusion-examples</a> code in the crate contain information on using DataFusion.</p>
-<p>The <a class="reference external" href="contributor-guide/index.html#developer-s-guide">developer’s guide</a> contains information on how to contribute.</p>
+<p>Please see the <a class="reference external" href="contributor-guide/index.html#developer-s-guide">developer’s guide</a> for contributing and <a class="reference external" href="contributor-guide/communication.html">communication</a> for getting in touch with us.</p>
<div class="toctree-wrapper compound" id="toc-links">
<p aria-level="2" class="caption" role="heading"><span class="caption-text">Links</span></p>
<ul>
diff --git a/searchindex.js b/searchindex.js
index 0eba08eca0..63de525e63 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