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
If there does end up being a core group of maintainers and there's room in that group for someone with more enthusiasm than experience, I'd love to be a part of it!
I've never maintained a project of any size, but I'm looking to get some experience in that area, so I'd like to throw my name out there as someone who could support the maintenance of HAML.
We use HAML for all our client work at Hashrocket and I think its fair to say that we couldn't live without this awesome project. I'd love to give back by helping, even on basic stuff. We do have company-sponsored open source time every week and I'd be happy to use it for working on HAML. Let me know if I can help!