Well, that escalated quickly and unexpectedly.
@EliasAlucard I think you know quite well that your last post at Marc went way over the top, escalated the heated debate to the next level and violated the code of conduct. Someone flagged it now, and I think rightly so.
Not excusing Marc’s behavior, though, which also was inappropriate.
But maybe a few words from me as maintainer of open source projects: I kind of get were Marc’s feelings and reactions are coming from. If you have an open source project people actually use, there will be people telling you how you really should support feature X, how easy this would be, that others do this and hence should you etc. etc. At times that can feel really demanding or patronizing; you feel people try to educate you on things you know about well and asking you for stuff you have explained already a trillion times. More than once I read comments on my projects that really made me feel angry, even though there was probably no ill intention on the person who wrote it. But the way they formulated their requests just felt demanding and/or patronizing. Let’s give a recent example: When you answered me with explaining the merits of the GPL my gut reaction to it was “this guy for sure does not need to educate me on the GPL”. That’s partly because of my experience that small seemingly harmless questions about “why license XY” usually is a sneaky way to drag one into a often point- and endless licensing discussion. I think I most of the time manage to get some distance to situations like these and either ignore it or answer neutrally. But small things like this can build up. I don’t know why Marc reacted as he did, but there likely is some history behind it.
Anyway, enough of this and back to topic: Great you had the code and thanks for preserving it. But the repository now is based upon an older fork of mine I created to preserve the code after Marc’s last rage quit and contains some obsolete parts. Marc in the meantime had set up a fresh repository, and I had setup a fresh fork for it. Unfortunately it had been a while since my last sync, so the changes for 1.1.2 and 1.1.3 had not been included. I have now updated the fork with the changes from your repo:
I think this is now the most accurate representation of the previous repository we have.
I still have no real interest in actively developing this further myself, but I’m happy to give this minor maintenance or merge pull requests until someone stands up and continues to properly develop this.