1. 46
  1.  

  2. 16

    Oof, I can relate to this. I’ve had the same loss of interest on some of my open source projects. I’ve been trying to power through it by making it a habit to at least check and respond to issues and pull requests. It’s helped, but not by all that much.

    Sadly, the developer’s 6-week release schedule doesn’t seem to have worked, or at least not forever. exa made it to 0.9.0, but as of when I’m writing this comment there hasn’t been a commit for about six months.

    1. 1

      Tangent: I and my coworkers are all big fans of exa and have all aliased ls to it. Thanks!

      1. 1

        I’m glad you like exa (I use it as well) but I haven’t contributed to it myself.

    2. 10

      Just let it die. It really is ok. Either pass off the project or let it die. You don’t owe anything to anybody. If you want to be respectful about it then just add a deprecated to the top of the readme and do something to improve your life. No reasonable person expect you to be able to spend your entire life working on the same project for little or no pay. If any of the maintainers for the code that I use were to bow out at any point in time I would completely respect their decision. I hope he takes care of himself.

      1. 3

        Does anyone remember a talk or blog post given by $old-semi-famous-programmer where they explain something like “when software is finished”? Because it’s extremely relevant to this but I can’t find it :(

        1. 2

          I wonder if I’m imagining this, or is it because it’s probably the programming community I’m the closest to… but it seems that this is not uncommon in the Rust community. I might jokingly guess that this is because of the language. More seriously, perhaps the community’s inclusivity encourages talking about these things more.

          1. 1

            I had similar issues because job was eating up all my programming juice.