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
I propose that we create a Haml organization on GitHub, and have a core group of maintainers. That would allow the project to grow (as well as the core group change) over time without being limited by one specific owner's repo. This seems to have become the accepted solution to this kind of problem in many of the open source communities as the idea of open source on GitHub has evolved (Rails being the most obvious example.) I think this also helps to solve two problems 1) Single developers from doing crazy things with the language and 2) A single developer not having enough time on his own.
I'd of course be willing to be a founding member of the core team if this works out.
Thoughts? Anyone else willing to participate as a core team member?
If one or two others are interested in seeing how this might work out, I'm willing to (if @nex3 will do this) create the organization with myself and @nex3 as the organization owners, @nex3 can transfer the repo ownership to the organization and I'll look into some of the pull requests/issues. That way assuming this works out, no one has to do the double work of porting back issues information to the "new" official repo.
Edit: part of my reasoning for suggesting this is that I'm willing to be the maintainer/coordinator, but I know I don't have time to fix every bug or develop new features. But I'd be willing to coordinate/oversee others involvement and be active in guiding the discussion on bugs/patches.