You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sedona.apache.org by ji...@apache.org on 2024/10/29 17:21:08 UTC

(sedona) branch master updated: [DOCS] Change Gitter to Discord (#1659)

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

jiayu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sedona.git


The following commit(s) were added to refs/heads/master by this push:
     new 21c3930ba [DOCS] Change Gitter to Discord (#1659)
21c3930ba is described below

commit 21c3930babfd105f4e4b42d5f03a5d6f3342a7d3
Author: Mohammad Lotfi Akbarabadi <87...@users.noreply.github.com>
AuthorDate: Wed Oct 30 01:21:03 2024 +0800

    [DOCS] Change Gitter to Discord (#1659)
    
    Gitter is no longer available and new conversations are held on Discord.
---
 docs/community/contributor.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/community/contributor.md b/docs/community/contributor.md
index 71f85ce14..30a5f6ca2 100644
--- a/docs/community/contributor.md
+++ b/docs/community/contributor.md
@@ -40,7 +40,7 @@ The PMC regularly adds new committers from the active contributors, based on the
 
 * Sustained contributions to Sedona: Committers should have a history of major contributions to Sedona.
 * Quality of contributions: Committers more than any other community member should submit simple, well-tested, and well-designed patches. In addition, they should show sufficient expertise to be able to review patches.
-* Community involvement: Committers should have a constructive and friendly attitude in all community interactions. They should also be active on the dev mailing list & Gitter, and help mentor newer contributors and users.
+* Community involvement: Committers should have a constructive and friendly attitude in all community interactions. They should also be active on the dev mailing list & Discord, and help mentor newer contributors and users.
 
 The PMC also adds new PMC members. PMC members are expected to carry out PMC responsibilities as described in Apache Guidance, including helping vote on releases, enforce Apache project trademarks, take responsibility for legal and license issues, and ensure the project follows Apache project mechanics. The PMC periodically adds committers to the PMC who have shown they understand and can help with these activities.