Submission guidelines

What belongs here

• Open-source software with a public repository and an OSI-approved or otherwise open licence (or a clearly stated lack of one).
• Dormant or abandoned: the maintainers stopped, or there has been no meaningful maintenance for a long time.
• Worth reviving: people still use it, need it, or would benefit from what it did.

What does not

• Actively maintained projects, even if they are slow or have many open issues.
• Closed-source software, or projects whose code is not available.
• Your own new project looking for contributors (unless it revives a listed project).
• Duplicates. Search first; if it is already listed, add a revival or suggest a correction.
• Malware, spam, or anything that breaks the terms.

Writing a good project entry

• Link the original repository, not a fork or a mirror.
• Describe it neutrally in one or two sentences: what it does, for whom. No marketing.
• Why revive it: who still depends on it, what is missing elsewhere.
• Pick the status carefully. “Abandoned” needs evidence such as an announcement, an archived repository, or maintainers who are unreachable. If you are not sure, choose “Dormant”. Explain your evidence in “Why it was abandoned”.
• Be honest about effort and work needed, so newcomers can find projects they can actually take on.
• Be respectful about the maintainers. People stop maintaining software for good reasons.

Adding a revival

• Link the revival's own repository or website, and choose the relationship: fork, rewrite, successor, alternative and so on. A revival does not have to share code with the original.
• The revival should be real: published code or a public project, not just an idea.
• If you maintain the revival, say so in the description.

Review

A moderator reviews every submission, usually within a few days. They may edit it for clarity or accuracy, or reject it with a note. You can see the state of your submissions on your account page. See the methodology for what “verified” means.

Found a mistake?

Use Report a problem or Suggest a correction on the project page. Include a source (a link to an announcement, release or commit) whenever you can.