Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Chat for open source projects

未關閉
#29 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯

研究方向

審查列出的需求,並將 Discord、Slack、Matrix 和 Element、IRC 以及 Zulip 與這些需求進行比較。該 issue 標記為「未完待續」,因此要完成它,就需要明確的平台建議和已定義的後續變更;沒有指定專案檔案或測試。

由索引模型根據 Issue 內容生成。

描述

question

It is difficult to find a good chat platform for an open source project. What are the attributes I am looking for?

  • viewable without a login needed. This is the open in open source!
  • supporting threaded conversations in a decent and usable way
  • searchable log
  • low resources desktop and mobile app, and equally capable web client
  • support moderation for trolls
  • preferably open source
  • simple integrations to keep abreast of commits, issues and Ci/CD events
  • preferably free, with option for commercial, paid-for support and hosting

The contenders are Discord, Slack, Matrix and Element, IRC, Zulip and a few more.

Discord and Slack are proprietary, but that is not the mostly disqualifying problem. Both required to be logged in making them not openly viewable. Discord web and Electron uses a huge amount of resources, and Slack threading is not usable at all. Slack free version has no history: after 10K messages or some time, the messages disappear unless you unlock a commercial plan.

IRC is (or was) awesome, but not something for the less trained casual user, and lacks history short of a bouncer and bots to log it.

Matrix and Element are great, but the Electron desktop client, like that from Discord is resource drag or worse. Its emphasis is on security, and while I like security, confidential and e2e encrypted messages are a decision factor for my use case.

To be continued....

主要語言
JavaScript
星號
9
分支
17
平均合併
7 小時 55 分鐘
30 天內合併 PR
2

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

aboutcode-org/www.aboutcode.org 的其他 Issue

查看 aboutcode-org/www.aboutcode.org 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。