Proposal - community - communication - Telegram (juror channel) and Slack revitalisation


#1

Telegram

Currently most of the discussions are about pixels, quality of the logo, whether the name has proper capitalization and whether we use the latest brand colours.

Some other important topics

  • escrow
  • realito
  • esperanto (noticed a few new commits)
  • dev onboarding (noticed some questions recently)
  • real life integrations
  • blockchain week in NYC
  • partnerships

There is a Telegram dedicated for trading.

There should be a channel dedicated for 2px logo discussions.

In that way there will be more space for meaningful strategic high-level discussion.

Slack

Currently, it’s rather empty.

Reminds me of: https://en.wikipedia.org/wiki/Broken_windows_theory

The theory suggests that policing methods that target minor crimes such as vandalism, public drinking, and fare evasion help to create an atmosphere of order and lawfulness, thereby preventing more serious crimes.

If Slack was better maintaned, there would be more discussions.

I suggest the following new channel layout:

  1. Announcements (only admins, new blogposts)
  2. General (Kleros focused)
  3. Random (not Kleros, anything and everything)
  4. Support Help Questions Feedback
  5. Dev Technical Support
  6. Press / Ethereum News / Reading
  7. Research Math Game Theory
  8. Pilot: Doges
  9. Pilot: Tokens
  10. Pilot: Escrow
  11. Twitter bot
  12. Github bot
  13. Build bot

Forum

The forum allows users to spend a few minutes into forming a precise thought, not real-time back and forth.

I became too engaged on Telegram.

It had negative effect to my focus and concentration.

(that’s why I voluntarily left the channel)

I’m not here to tell you what to do. I’m just a guy on the internet - I have no authority to tell you what to do. I’m putting these proposals to a discussion with the intention to empower the community.

More space for meaningful indepth discussion.


#2

There is a Telegram dedicated for juror: https://t.me/klerosjuror

@m as admin :fire::fire::fire: