docs(distribution): Tier 3 adoption — Show HN, awesome lists, dogfood badge

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
github, java
Área
devops

Línea de trabajo

Start with release_plan.md and its Tier 3 distribution steps; check the v0.3.1 patch queue and related issues #319 and #321 for launch dependencies. The work spans promotion, repository dogfooding, and external list submissions. It is done when the bot reviews this repository, a README badge is added, a launch post is published, and an awesome list PR is merged or its rejection and retry are documented.

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

Descripción

documentation enhancement
Problem Statement

ThrillhouseBot is feature-rich but invisible (~14 ⭐ vs PR-Agent ~12k). release_plan.md Tier 3 (distribution) has not started. Technical parity without visibility will not move adoption.

Proposed Solution

Execute Tier 3 distribution from release_plan.md:

  1. Show HN / r/selfhosted / r/java launch post (after v0.3.1 patch ships)
  2. awesome-* list PRs — self-hosted, devops, Java/Quarkus where appropriate
  3. Dogfood on this repo — enable ThrillhouseBot on devops-thiago/ThrillhouseBot, add “Reviewed by ThrillhouseBot” README badge
  4. Optional: demo GIF replacing live-streaming.png (noted in release_plan backlog)
Related issues
  • #319 — hosted docs site (launch asset; do docs before or with launch)
  • #321 — PR-Agent migration guide (link from launch post)
  • v0.3.1 patch queue — ship polish before loud launch (#296–#311, #302, #237, #11)
Acceptance criteria
  • Bot reviewing PRs on this repository (public proof)
  • README badge or equivalent social proof
  • At least one launch post published with link to repo + docs
  • At least one merged PR to a relevant awesome list (or documented rejection + retry)
Alternatives considered
  • Launch before v0.3.1 — risks first impressions on known patch items.
Priority

P0 — equally important as feature work per competitive analysis (PLAN.md → Competitive landscape). Scheduled after v0.3.1.

Code of Conduct
  • I have searched for existing issues and this is not a duplicate.
Lenguaje dominante
Java
Estrellas
35
Forks
7
Merge medio
10 h 5 min
PR fusionados (30 d)
179

Preparar el entorno

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 devops-thiago/ThrillhouseBot

Todos los issues de devops-thiago/ThrillhouseBot

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.