Milestone 4 Report
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 20/100
- issue の種類
- ドキュメント
- 明瞭さ
- 説明が足りない
- 活発さ
- 停滞
- 技術スタック
- prometheus
調査の方向性
これはコード作業ではなくマイルストーンのレポートです。まず、受け入れ条件、リンクされたロードマップ、Prometheus の uptime クエリ、issue と pull request のステータス一覧を確認してください。各条件の根拠と関連するプロジェクト活動へのリンクを含む、完全な公開レポートが完成すれば完了です。
索引モデルが issue の本文から書いたものです。
説明
This issue is meant to track progress on the acceptance criteria and evidence of milestone completion for M4.
Acceptance Criteria
The following is a breakdown of the acceptance criteria for M4, along with explanation as to how each have been satisfied.
The roadmap clearly outlines a strategy for moving from a centralized, MLabs hosted testnet, to a decentralized testnet maintained by the SPO community.
The roadmap outlines a strategy involving multiple phases, which are clearly outlined. (See link below.)
Interested SPOs will receive some marketing/promotional support on social media from us and will also benefit from community good will. That said, because SPOs are independent business operators we cannot guarantee that any number will be interested.
We have contacted numerous SPOs and provided support as outlined in the roadmap. However, no SPOs have shown interest in hosting the testnet thus far.
The roadmap is made public.
The roadmap is publically available (see link below).
SPOs and Cardano developers have been engaged and are aware of the congested testnet. We have released a series of 10 marketing posts across several channels promoting the project, following up with interested SPOs as needed.
We have engaged numerous SPOs and released 10 marketing posts (details below).
The testnet remains accessible throughout the duration of this milestone with at least 99% uptime for this 2 month period.
The average uptime over the last 60 days is greater than 99% (details below).
Evidence of Milestone completion
Link to public roadmap.
Congested Testnet Roadmap for Community Engagement and Adoption
List of any SPOs that have committed to maintaining the testnet going forward (if there are any at this point).
30 SPOs were reached out to, 9 responded in meaningful dialogue around hosting and 6 joined our Telegram support channel. But thus far none have committed to maintaining the testnet.
Links to social media posts where the community was engaged.
Twitter:
- https://x.com/MLabs10/status/1900213700340179143
- https://x.com/MLabs10/status/1912842341771301335
- https://x.com/MLabs10/status/1914276345661858192
LinkedIn:
Youtube:
Telegram:
Discord:
- https://discord.com/channels/826816523368005654/868025141668503582/1362416011550392530
- https://discord.com/channels/1136727663583698984/1136727664036692103/1363811719608008906
- https://discord.com/channels/386191477333557248/397539471702360084/1364120728928256064
NOTE: we also have a Telegram support channel we have been engaging SPOs
https://t.me/+3kNyHmpMwGc2ZDA1
PDF (or updated Gitbook) showing uptime for the duration of this milestone as well as progress on issues (issue names, current status, links to PRs with fixes, and reasons for any not addressed).
Due to the limited number of issues reported thus far, a separate PDF or Gitbook is unnecessary. Below are the uptime and issue details:
Uptime
Uptime for the congested testnet is being tracked using Prometheus. The following URL will show the average uptime over the 60 day period prior to 2025/04/21:
Congested Testnet 60 Day Avg. Uptime
The average uptime is 99.99521604938032%
Issue Progress
Below is a current breakdown of issues by status as of 2025/04/21.
Backlog
- Uptime reports #5
- Uptime history is currently accessible through Prometheus
- Downtime alerts #8
- Downtime alerts will be useful but are not strictly necessary due to limited usage
- Project closeout report and video #13
- This will be completed in the final milestone
- Transition and full handover of the congested testnet to the SPO community #14
- We have not yet received sufficient interest from the community
Completed
- Milestone 3: Improvements and Maintenance #6
- Add another instance / increase spammer capacity #7
- Milestone 3 Report #10
- Roadmap for community engagement and adoption of the testnet #12
Relevant PRs for This Milestone
- 主要言語
- Dhall
- スター
- 4
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
mlabs-haskell/congested-testnet のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 18/100
-
難易度 3/5 1〜2日 初心者へのやさしさ 30/100
-
Downtime alertsオープン
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
-
Uptime reportsオープン
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
mlabs-haskell/congested-testnet#5 · コメント 1 件 ·
mlabs-haskell/congested-testnet の issue をすべて見る
似ている issue
-
難易度 1/5 1〜3時間 初心者へのやさしさ 78/100
btclib-org/portanode#699 ·
メンテナーはふだん 1 日以内に返信
-
ObjectMapper
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
symfony/symfony-docs#23390 ·
メンテナーはふだん 2 日以内に返信
-
Guidelines: redundant use cases, stale dev bundle after snapshot bumps, looking up snapshot API対応中かも @totally-not-ai が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
vaadin/use-cases#441 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
sync-en
難易度 1/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
sync-en
難易度 1/5 1時間未満 初心者へのやさしさ 83/100
メンテナーはふだん 3 日以内に返信