Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Milestone 4 Report

Abierto
  • ¿Algo no está bien?
#23 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
prometheus
Área
documentation

Línea de trabajo

Este es un informe de hito, no una tarea de código; comienza revisando los criterios de aceptación, la hoja de ruta enlazada, la consulta de uptime de Prometheus y la lista de estados de issues y pull requests. Se considera terminado cuando haya un informe público completo con evidencias para cada criterio y enlaces a la actividad relevante del proyecto.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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:

LinkedIn:

Youtube:

Telegram:

Discord:

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
Completed

Relevant PRs for This Milestone

Lenguaje dominante
Dhall
Estrellas
4
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de mlabs-haskell/congested-testnet

Todos los issues de mlabs-haskell/congested-testnet

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.