1. 26
  1.  

  2. 16

    Alternatively, you can use repostatus.org’s “Abandoned” or “Unsupported” badges:

    • Abandoned – Initial development has started, but there has not yet been a stable, usable release; the project has been abandoned and the author(s) do not intend on continuing development.
    • Unsupported – The project has reached a stable, usable state but the author(s) have ceased all work on it. A new maintainer may be desired.

    repostatus.org is a similar project that defines eight statuses you can mark repos with: Concept, WIP, Suspended, Abandoned, Active, Inactive, Unsupported, or Moved. Each badge links to a short summary such as the ones above.

    It looks like No Maintenance Intended might explain the project status better with its dedicated web page, while repostatus.org is better for being able to categorize the state of all of one’s projects.

    1. 8

      Repostatus sure feels more thought out. “No Maintenance Intended” is vague and open to interpretation, see this HN thread for the same submission.

      Shouldn’t the badge have a green checkmark to show everything’s ok? Or is no maintenance intended supposed to imply your code is broken?

      1. 1

        Seems like ‘no maintenance intended’ means ‘don’t bother me about it’ – i.e., if it’s broken then fork it.

    2. 9

      If your project is on GitHub you can archive to let visitors know it’s no longer maintained.

      1. 8

        It’s sad this is even needed. Unfortunately some people think that publishing some code oblige you to support it.

        I remember people being upset at Dominic Tarr who transferred ownership of one of his npm modules to new maintainer who turned out to have malicious intents. People were upset that Tarr allowed new maintainer to use his old repository (instead forcing regular fork) or something like that.

        Unless you are paid to provide support you don’t have any obligation to user of your FOSS code whatsoever.

        1. 6

          Many people are aware of the “no warranties” part of most FLOSS licenses.

          But Github etc. have made contributing to software development easy and dare I say it , friendly. For better or worse, people expect maintenance and support, and a minority demand it.

          While a gruff “read the damn license and leave me alone” is the techically correct way to communicate an absence of support, having a clear, unambigious and neutral way to communicate that is for the better in general.

          1. 5

            People were upset that Tarr allowed new maintainer to use his old repository (instead forcing regular fork) or something like that.

            Unless you are paid to provide support you don’t have any obligation to user of your FOSS code whatsoever.

            I don’t know anything about that particular situation but there’s a difference between obligation and trust. Open source authors do not have any obligation towards users of their code. However, if you use someone else’s code in your project or on your computer, you have a choice to make. You can either read and personally vet every line of the third-party code (which takes just as much, if not more effort than simply writing it yourself in the first place), or you can choose to trust that the author has no ill intent towards you. Almost without exception, we chose the latter and because of that, the whole open source software community is built upon trust (and to a lesser degree) reputation.

            If you have some code that the open source community trusts, you certainly have the right to hand it off to anyone you chose. There is no obligation to manage the code in any particular way, or at all. But if you don’t vouch for that person, and they do something underhanded with it, those who comprise the community is well within their rights to no longer trust you.

            1. 3

              It’s very useful to know the status of a project when e.g. comparing alternatives or to know whether submitting an issue is not a waste of time. The choice here is not ‘either you buy support or you assume it is abandoned’. There is plenty of communication bandwidth available.