branch: elpa/flycheck
commit 812a6a187327a032d54fa28aa2f226a71f250acb
Author: Bozhidar Batsov <[email protected]>
Commit: Bozhidar Batsov <[email protected]>
Remove Gitter references from docs and README
All communication now happens on GitHub (issues, PRs, discussions).
Also remove the dead lint-python CI badge from the README and the
stale `make format` entry from the contributor's guide.
---
README.md | 11 ++++-------
doc/community/conduct.rst | 3 +--
doc/community/get-help.rst | 13 +++++++------
doc/contributor/contributing.rst | 9 +++------
4 files changed, 15 insertions(+), 21 deletions(-)
diff --git a/README.md b/README.md
index 647481b9a7..05afa75ba1 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,11 @@
# [![Flycheck][logo]](https://www.flycheck.org)
[][COPYING]
-[](https://gitter.im/flycheck/flycheck)
[](https://melpa.org/#/flycheck)
[](https://stable.melpa.org/#/flycheck)
[](https://elpa.nongnu.org/nongnu/flycheck.html)
[](https://github.com/flycheck/flycheck/actions/workflows/test.yml)
[](https://github.com/flycheck/flycheck/actions/workflows/docs.yml)
-[](https://github.com/flycheck/flycheck/actions/workflows/lint-python.yml)
<https://www.flycheck.org>
@@ -47,8 +45,8 @@ through [Quickstart][] guide.
## Getting Help
-Please ask questions about Flycheck on [Stack Exchange][sx] or in our
-[Gitter chat][gitter], and report bugs to our [issue tracker][].
+Please ask questions about Flycheck on [Stack Exchange][sx] and report bugs to
+our [issue tracker][].
## Contributing
@@ -142,8 +140,8 @@ site. [[Become a
sponsor](https://opencollective.com/flycheck#sponsor)]
We strive to create a safe, friendly and welcoming environment in the Flycheck
community and have a [Code of Conduct][coc] that defines acceptable and welcome
behaviour as well as sanctions for violations. All contributors and all
-participants are expected to follow it, on Github, Gitter, Emacs.SX or any
other
-place that’s part of Flycheck’s broader community.
+participants are expected to follow it, on Github, Emacs.SX or any other place
+that’s part of Flycheck’s broader community.
## License
@@ -163,7 +161,6 @@ details.
[Installation]: https://www.flycheck.org/en/latest/user/installation.html
[Quickstart]: https://www.flycheck.org/en/latest/user/quickstart.html
[sx]: https://emacs.stackexchange.com/questions/tagged/flycheck
-[gitter]: https://gitter.im/flycheck/flycheck
[Issue Tracker]: https://github.com/flycheck/flycheck/issues
[contrib]: https://www.flycheck.org/en/latest/contributor/contributing.html
[coc]: https://www.flycheck.org/en/latest/community/conduct.html
diff --git a/doc/community/conduct.rst b/doc/community/conduct.rst
index 80647cff41..35a6adee43 100644
--- a/doc/community/conduct.rst
+++ b/doc/community/conduct.rst
@@ -49,8 +49,7 @@ Moderation
==========
These are the policies for upholding our community's standards of conduct in
our
-communication channels, most notably in Flycheck’s Github organisation and in
-Flycheck’s Gitter channels.
+communication channels, most notably in Flycheck’s Github organisation.
1. Remarks that violate the Flycheck code of conduct, including hateful,
hurtful, oppressive, or exclusionary remarks, are not allowed.
diff --git a/doc/community/get-help.rst b/doc/community/get-help.rst
index 92ff447164..4c518fefd0 100644
--- a/doc/community/get-help.rst
+++ b/doc/community/get-help.rst
@@ -4,14 +4,15 @@
Get help
==========
-Please ask questions about Flycheck on `Stack Exchange`_ or in our `Gitter
-chat`_. We try to answer all questions as fast and as precise as possible.
+Please ask questions about Flycheck on `Stack Exchange`_ or on our `GitHub
+issue tracker`_. We try to answer all questions as fast and as precise as
+possible.
-To report bugs and problems please use our :flyc:`issue tracker
-<flycheck/issues>`. Please note that we have a special policy for
-:ref:`Windows-only issues <flycheck-windows-issues>`.
+To report bugs and problems please use our `GitHub issue tracker`_.
+Please note that we have a special policy for :ref:`Windows-only issues
+<flycheck-windows-issues>`.
Please follow our :ref:`Code of Conduct <flycheck-conduct>` in all these
places.
.. _Stack Exchange: https://emacs.stackexchange.com/questions/tagged/flycheck
-.. _Gitter chat: https://gitter.im/flycheck/flycheck
+.. _GitHub issue tracker: https://github.com/flycheck/flycheck/issues
diff --git a/doc/contributor/contributing.rst b/doc/contributor/contributing.rst
index aa6f79d951..4590967417 100644
--- a/doc/contributor/contributing.rst
+++ b/doc/contributor/contributing.rst
@@ -10,7 +10,7 @@ with us!
There are many ways to contribute to Flycheck, and we appreciate all of them.
We
hope that this document helps you to contribute. If you have questions, please
-ask on our `issue tracker`_ or in our `Gitter chatroom`_.
+ask on our `issue tracker`_.
For a gentle start please take a look at all the things we `need your help
with`_ and look for `beginner-friendly tasks`_.
@@ -19,7 +19,6 @@ Please note that all contributors are expected to follow our
:ref:`Code of
Conduct <flycheck-conduct>`.
.. _issue tracker: https://github.com/flycheck/flycheck/issues
-.. _Gitter chatroom: https://gitter.im/flycheck/flycheck
.. _need your help with:
https://github.com/flycheck/flycheck/issues?q=is%3Aissue+is%3Aopen+label%3A%22needs+help%22
.. _beginner-friendly tasks:
https://github.com/flycheck/flycheck/labels/beginner%20friendly
@@ -84,9 +83,8 @@ Run ``make help`` to see a list of all available targets.
Some common ones are:
- ``make init`` initialises the project by installing local Emacs Lisp
dependencies.
-- ``make check`` checks all Emacs Lisp sources. This target requires Emacs
27.1.
+- ``make check`` checks all Emacs Lisp sources.
- ``make compile`` compiles Flycheck and its libraries to byte code.
-- ``make format`` formats all Emacs Lisp sources.
- ``make specs`` runs all Buttercup_ specs for Flycheck. Set
:makevar:`PATTERN`
to run only specs matching a specific regular expression, e.g. ``make
PATTERN='^Mode Line' specs`` to run only tests for the mode line.
@@ -215,14 +213,13 @@ Out of tree contributions
There are many ways that you can contribute to Flycheck that go beyond
this repository.
-Answer questions in our `Gitter channel`_ or on StackExchange_.
+Answer questions on StackExchange_ or on our `issue tracker`_.
Participate in Flycheck discussions in other Emacs communities and help
users with troubles.
Write :ref:`extensions for Flycheck <flycheck-extensions>`.
-.. _Gitter channel: https://gitter.im/flycheck/flycheck
.. _StackExchange: https://emacs.stackexchange.com/questions/tagged/flycheck
--------------
