For Slack, I've been using an invite link that "does not expire", however,
the invite link does have a limit of 1,000 people. Therefore it's not very suitable for a long time usage or as a permanent link and it will need to be regenerated
occasionally. This is what makes GitHub Discussions much more accessible.

Additionally, discussions has more powerful organizing features and can be linked
whereas Slack discussions tends to get lost.

So +1 from me to use GitHub discussions for support.

On 2022-11-21 3:10 a.m., Niklas Merz wrote:
Hey everyone,

I quite like GitHub discussion for support over chat tools like Slack.
Slack is not really accessible for users and the limitations of the free
plan are not good. We still could use the official ASF Slack for some
things like chatting in the PMC, DMs etc.

A nice thing about GitHub discussions is that you can convert
discussions to issues and vice versa. So it's easy to turn an issue
which is actually a support question to a discussion or the other way
around.

Therefore big +1 from me.

On November 20, 2022, Jesse <purplecabb...@gmail.com> wrote:
Hello all,

github discussions are a great way of keeping code conversations very
close
to the actual code and I think would suit our project better than our
use
of #slack

The apache airflow project switched to use discussions [1]
This is not configurable via asf.yml [2] and requires an infra ticket
linking a consensus reaching discussion. [3]

I propose that we enable discussions on the apache/cordova repo [4] to
evaluate, and we can possibly make a decision to include other repos
later.

What do you think?

Cheers,
  Jesse

[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions-
GithubIssuesandDiscussions
[2]
https://cwiki.apache.org/confluence/display/INFRA/Git+-
+.asf.yaml+features
[3]
https://cwiki.apache.org/confluence/display/INFRA/Git+-
+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions
[4] https://github.com/apache/cordova

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to