Accession review: aybee reader

Aperta
#2 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
35/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript

Direzione di ricerca

Start by reading the repository entry point and README, then check whether RERUM or TPEN documentation, the org site, or published exhibits link to the project. Try a clean clone for up to 30 minutes and inspect dependencies for advisories or runtimes that are no longer supported; record blockers rather than fixing them. Finish with the requested status line, health check, live surface and dependency findings, and exactly one recommendation: reactivate, archive, absorb, or leave.

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

Descrizione

task

Dormant since 2023-05. Created 2020-10-22, last pushed 2023-05-26. JavaScript, HTML, CSS. Zero open issues. No description on the repo at all.

The name is a phonetic spelling of ABI, which suggests an annotation or IIIF reader. Confirm that before assuming it.

Specific things to check

  • What it actually does. With no description and no open issues, the repo is undocumented to itself. Read the entry point and write a paragraph.
  • Whether it overlaps illuminator or the TPEN interfaces
  • Whether any RERUM or TPEN documentation links to it

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
JavaScript
Stelle
0
Fork
0
Merge medio
2g 21h
PR unite (30g)
1

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/aybee

Tutte le issue di CenterForDigitalHumanities/aybee

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.