Reorganize Discord channels

[aidanjungo]

Should we have better organization of the Discord channels, more interaction with people?

Idea: We could maybe use the Github Discussion for the tech part and keep Discord more "social"...

[GresilleSiffle]

suggestion

I'd like to propose a first read-only INFO section for our Discord server, tell me what do you think.

I'm gonna propose several channels in this section, feel free to give your feeling and to ask questions about each of them.

The goal of this section is to help the users to discover the project, and gives us a main channel to communicate with the community. Users will also be able to enable notifications on these channels, without worrying about being pinged too often, as it can be with the current general channel where everyone can write.

[INFO]
+- welcome
+- rules
+- announcements
+- papers
+- donate
+- FAQ

The channel welcome could contain:

• very small presentation of the platform and the extension, with links to join tournesol.app and download the extension
• also mention the tweeter bots
• an invitation to check the source code
• an invitation to check the Discord rules

This channel will be the first entry point of all users, and will invite them to contribute ( and read the rules : ).

The rules could contain:

• the code of conduct everyone accept to follow by joining the Discord
• how to contact an administrator in case of need
• maybe the sanction we could take in case of need ( temporary ban, permanent ban )
• we can take inspiration of existing codes of conduct
  • https://www.python.org/psf/conduct/
  • https://www.contributor-covenant.org/version/2/1/code_of_conduct/

I think it's possible with Discord: we could hide all channels expect welcome and rules, and display all the others when a user use the emoji white check mark :white_check_mark: or thumb up :+1: on the rules text. It could act as a explicit consent to follow the community rules.

The announcements could contain (it's my favorite section):

• new front end features
• new API features
• new extension releases
• new paper submitted / reviewed
• anything worth pinging the community

I think regular communications through announcements will keep the community involved and will pleased everyone curious about the new features released on Tournesol.

... to finish ...

[aidanjungo]

Just a few ideas:

• Having clearer user status, e.g.:

  • Core-team
  • Dev: people who are developer on Github
  • Moderator: people who know the project an can answer newcomers
  • Top contributor: e.g. people with at least 100 comparisons

• For important channel, having pinned info which help newcomers

[aidanjungo]

From Tournesol association general assembly, an idea came up:

• having a channel where we propose some well defined task to accomplish so people could get involved easily

[lfaucon]

We did some re-organization already. It's in a better state. Let's re-open a more precise ticket to propose more changes.