Skip to content

Add more Famous Casualties to the graveyard #9

@dotsystemsdevs

Description

@dotsystemsdevs

What

Two hand-curated lists of famously abandoned repos power different surfaces of the site:

  • src/lib/scoring.tsKNOWN_REPO_CAUSES — short cause strings used on generated death certificates when one of these repos is scanned.
  • src/lib/hallOfShame.tsHALL_OF_SHAME — full entries surfaced in the Recently Buried section on the landing page.

We'd love more entries from the community.

How to contribute

In src/lib/scoring.ts — add a lowercase owner/repo key to KNOWN_REPO_CAUSES:

'owner/repo': 'A short, witty, accurate cause of death',

In src/lib/hallOfShame.ts — add an entry to the HALL_OF_SHAME array:

{
  fullName: 'owner/repo',
  cause: 'short cause of death (~60 chars)',
  score: 8,                    // 6–10 depending on how dead it is
  deathDate: 'Dec 2022',
  lastWords: 'one-line quote in the repo\'s voice',
},

You can contribute to either file (or both — ideally both, for repos that deserve a full tombstone).

Guidelines

  • Repos must be genuinely abandoned or officially deprecated
  • Causes should be factually accurate and written in the same dry, deadpan tone as the existing ones
  • Keep cause under ~60 characters
  • lastWords should feel like something the repo would mutter on its deathbed
  • Check existing entries first — no duplicates
  • Good candidates: Parse, Flash SDK, Backbone.js, jQuery UI, Google+ APIs, Heroku free-tier client, SourceForge tooling

Acceptance criteria

  • At least 3 new entries added (to either file, or both)
  • Each entry is factually accurate
  • Tone matches existing entries
  • npm run lint passes

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions