Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Accession review: Dunbar Library and Archive

Aperta
  • Qualcosa non va?
#39 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
css, html, javascript
Ambito
devops, documentation

Direzione di ricerca

Start by comparing DLA, DLA-CMS, DLA-locator, and Dunbar-Letters, then inspect the 15 open issues and the current data location. Try a clean clone within the 30-minute limit, check dunbar.udayton.edu, the org site, RERUM and TPEN docs, and published exhibits. Record deployment, runtime, and advisory findings, then make exactly one of the requested reactivate, archive, absorb, or leave calls.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

task

Alive but carrying a backlog. Created 2021-04-23, last pushed 2025-12-18. 15 open issues. HTML, JavaScript, CSS.

The DLA is not one site, it is a suite: DLA, DLA-CMS, DLA-locator, plus Dunbar-Letters as a test case. This issue covers the main repo. The suite relationship is the actual thing to resolve.

Specific things to check

  • Which of the four DLA repos are load-bearing and which are historical
  • Whether the 15 open issues are still valid or are 2021 thinking nobody cleaned up
  • Where the DLA data lives now and whether dunbar.udayton.edu still serves it. The Encoding Ambiguity proposal cites the Dunbar virtual archive as a comparable, so a dead link there is a grant problem, not just a repo problem.

What to produce

  1. Status line. One sentence: what this was for, and whether that purpose still exists.
  2. Health check. Does it run from a clean clone today? Timebox this to 30 minutes. If it does not run, record the blocker rather than fixing it.
  3. Live surface. Is anything from this repo still deployed or linked from a live page? Check the org site, the RERUM and TPEN docs, and any published exhibits. A dead URL that other people's pages still point at is a real problem.
  4. Dependency audit. Anything with a known advisory, anything pinned to a runtime that no longer ships.
  5. One call. Pick exactly one:
    • reactivate - worth working on again, and there is a reason
    • archive - historically useful, no future. Archive the repo and write the README eulogy.
    • absorb - the useful part belongs somewhere else. Name the destination and what moves.
    • leave - no decision needed now, revisit next year. Say so and close this issue.

Why bother

Filed from cubap/DriftMD#4. Low priority by design. These are free-cycle tasks, and the point of writing them down is that a future pass has somewhere to start instead of re-deriving everything from a git log.

Lingua principale
HTML
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CenterForDigitalHumanities/DLA

Tutte le issue di CenterForDigitalHumanities/DLA

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.