This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v3-1-test by this push:
     new 69492228b78 [v3-1-test] Proposes clarification about information sent 
to the devlist (#59335) (#59386)
69492228b78 is described below

commit 69492228b78232c22c12db90f3d2428756ff9598
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Sat Dec 13 12:00:39 2025 +0100

    [v3-1-test] Proposes clarification about information sent to the devlist 
(#59335) (#59386)
    
    (cherry picked from commit 220023740a8458567c2bfac8460091b5ffc5d54a)
    
    Co-authored-by: Jarek Potiuk <[email protected]>
---
 contributing-docs/02_how_to_communicate.rst | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/contributing-docs/02_how_to_communicate.rst 
b/contributing-docs/02_how_to_communicate.rst
index 1d0739c2c40..89e2783ca3e 100644
--- a/contributing-docs/02_how_to_communicate.rst
+++ b/contributing-docs/02_how_to_communicate.rst
@@ -93,7 +93,30 @@ We are using certain prefixes for email subjects for 
different purposes. Start y
   * ``[ANNOUNCE]`` - only used by PMC members to announce important things to 
the community such as
     releases or big changes in the project
 
-Voting is governed by the rules described in `Voting 
<https://www.apache.org/foundation/voting.html>`_
+Apart of regular discussions on development of the project, the community also 
appreciates if various
+stakeholders, community members and participants share their experiences, case 
studies, best practices
+as well as updates on what's going on in their organizations related to Apache 
Airflow.
+
+There are certain rules for this kind of communication, it cannot be 
commercial in nature,
+it should not promote specific products or services, and it should not suggest 
that the PMC or
+the ASF endorse any specific products or services. The subject of such 
messages should refer to
+Airflow in "Nominative fair use" way as described in
+`Apache Trademark Policy <https://www.apache.org/foundation/marks/>`_.
+
+Such messages can contain summary and digest of what happens in the community 
- as long as it is unbiased
+and not commercial in nature. This kind of communication should be shared on 
devlist and
+whoever sends such messages should be open to include information from other 
community members who
+ask them to include their case studies, experiences or information.
+
+Like all the communication in our project - such messages should follow the
+`ASF Code of Conduct <https://www.apache.org/foundation/policies/conduct>`_.
+
+If you are in doubt whether your message is appropriate for the devlist - ask 
the community on devlist.
+
+**Voting**
+
+Voting happens on the devlist and is governed by the rules
+described in `Voting <https://www.apache.org/foundation/voting.html>`_
 
 What to expect from the community
 ---------------------------------

Reply via email to