It's become increasingly apparent that between my full-time job and my work on Sass, I don't have the cycles any more to properly maintain Haml. I'd like to pass on the mantle to someone else, but I don't want to do it blindly.
If you're interested in becoming the maintainer of Haml, please demonstrate this by creating a fork of the repo and starting the maintenance process of addressing the issues and code-reviewing and merging pull requests into your fork. What I'm looking for is evidence that you'll be more diligent than I currently can, as well as the ability to both write good code and get good code from other contributors.
In a week or so, if anyone's taken up this challenge and done well, I'll hand them the reins.
- Nathan Weizenbaum, Haml maintainer
Hi all, I did an implementation of Haml in Lua a while back and wrote Haml Spec, a test suite used by Ruby's Haml and a few other implementations. When I was working on Lua Haml I became fairly familiar with Haml's internals as I read through the source quite a bit, and submitted a few (small) fixes.
It's been a while since I've given my full attention to the project, but I do have the time and interest in maintaining Haml. My company allows a certain amount of dedicated time to open source work, and I'd be happy to spend almost all of that on Haml, at least for a solid few months. I talked about it with my work mates yesterday and have their blessing, if you consider me an acceptable maintainer.
I agree that it would be ideal to have an organization that facilitates and encourages more community contribution, as long as there's somebody who will oversee the general direction of the project.
I'm going to work on Haml a bit this week to see if I can address some of the more urgent issues in the queue as @nex3 requested. If you'd like me to maintain the project, I'm willing to do it, but if somebody else is chosen I'm still happy to make a contribution since this library is very important to me and I don't want to see it fade away.