Update the Chat page to highlight Discord info and de-emphasize/remove outdated links
まだ誰も着手していません。
評価
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 初心者へのやさしさ
- 72/100
- issue の種類
- ドキュメント
- 明瞭さ
- おおむね明確
- 活発さ
- 静か
- 技術スタック
- markdown
調査の方向性
chat.htmlをレンダリングするソースファイルを見つけ、Community channelsセクションを確認してください。ルールとFAQの案内を含むDiscordを主要な選択肢にし、IRC、フォーラム、wikiが二次的または古い代替手段であることを明確に示してください。レンダリングされたChatページとそのリンクを確認してください。
索引モデルが issue の本文から書いたものです。
説明
The gbdev.io home page has, at the very top:
Game Boy Development community
We are a non for profit collective of passionate developers and hackers working on development tools, homebrew games, emulators, preservation and documentation for the Nintendo Game Boy handheld console, the original gray brick from 1989.
This is great! All the social links are actively updated, and the Discord link is where the reader can truly join the community, and start chatting with us. (Maybe it should be listed first?)
However, the Chat page is not. Here's what it currently says:
Join our community on the following channels. Before posting, read the rules and the FAQ (usually in the welcome threads or in the signup).
- Discord Server.
- IRC:
#gbdevon Libera.chat is bridged to the Discord chat.
#gbdev-ot,#gbdev-casual,#gbdev-hw,#gbdev-meta,#gbdev-asm,#gbdev-gfx,#gbdev-emudev,#gbdev-romhackingand#gbdev-researchare also available for discussion about specific topics.- Forum: https://gbdev.gg8.se/forums/
- Wiki: https://gbdev.gg8.se/wiki/
The first link is fine, but I think the second link looks a lot more important than it is (to the point of de-emphasizing the first link where we actually want people to go), and the last two links are basically dead.
The GBDev Discord is the place where members new and old can actually communicate. I think the "Before posting, read the rules and the FAQ" instruction should be a sub-bullet of this link, so it can be more precise about where to find that info once you join the server.
The IRC server basically just exists in 2026 as a bridge to Discord, and even that only for perhaps a dozen[^1] people. (Only one of whom I'd recognize as actually regularly using it, beware.) We shouldn't encourage new users to do the same, since it can't handle replies, videos, reactions, etc. But having the longest list item makes it look more important than it is.
The forum looks dead. The last post in its "Site News" is from 2019. Only 2 of the 7 sub-forums have posts from 2026, and only the one from March has a reply (the one from February went unanswered). (It's now July.)
The wiki also looks dead. I mostly know it as being the old Pan Docs site -- the very first link in the very first section of its Main Page, "Developer Information -> Documentation", starts off with a big red "The copy of Pan Docs hosted on this wiki is considered deprecated" banner (as some may recognize from outdated links via Google et al). I thought maybe there'd be more than just the old Pan Docs, since supposedly "A few articles up -> There a couple of articles up on the Wiki." But as of today there were no changes to any page in the last 30 days. (It's not even really a "chat" method; still at least a collaborative community effort, but nobody new to the community should be futilely trying to share info by editing this website.)
I don't think these should all still be presented as four equal-weight options. Explaining how to join and use the Discord server should be the primary purpose of this page. Then maybe in a <hr>-separated bottom section, or some other clearly secondary area, it could list the IRC, wiki, and forums as historical alternatives, and mention that they're less likely to be read/responded to any more.
[^1]: Edit: Turns out that, not counting me, there's 13, a whole baker's dozen! None of whom are talking. :P Oh, and one is the gb-bridge bot, so I guess it's max 12 real humans after all. Even the #pret channel has 25 others, despite pret only mentioning it at pret.github.io, not in its repos' READMEs.
- 主要言語
- Assembly
- スター
- 34
- フォーク
- 16
- PR マージ指標
- 30日以内にマージされた PR はありません
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
gbdev/gbdev.github.io のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
gbdev/gbdev.github.io#107 · リアクション 2 件 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
gbdev/gbdev.github.io#86 ·
-
help wanted question
難易度 5/5 1週間以上 初心者へのやさしさ 20/100
gbdev/gbdev.github.io#103 · コメント 54 件 · リアクション 2 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 35/100
gbdev/gbdev.github.io#89 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 20/100
gbdev/gbdev.github.io#88 ·
gbdev/gbdev.github.io の issue をすべて見る
似ている issue
-
sync-en
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
agilepathway/label-checker#640 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
BasedHardware/omi#15662 · コメント 1 件 ·
-
documentation help wanted
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
-
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100