Is this project dead?

[gazsp]

There haven't been any commits for a while, and people seem to be having problems using the gem with Rails 5, so I'm assuming so.

If it is dead, is there any chance of anyone else taking over the project?

[kacy]

I pinged him on twitter. He seems pretty responsive there. 🤞

[andrewculver]

We are still here. I'm scheduled to connect with @yas4891 early next month, so we should be able to get some of the critical pull requests and other updates integrated and released after that.

[asecondwill]

Is it still going? Just had a bad experience with Payola. Is it a good idea to go ahead with Koudoku for a simple membership area for a site or build from scratch is wiser?

[andrewculver]

@asecondwill As far as I know, this still works, but I can't really speak to the experience of using Koudoku on a vanilla Rails app these days. My focus has since shifted to building and maintaining Bullet Train, so that's the only context in which I use Koudoku now, and it's already integrated and working out-of-the-box on all new Bullet Train apps, so no one really thinks about it anymore. It "just works." All of the updates I've made related to Bullet Train are available in #194 (with the exception of our customizations of the views,) so please see my comments there. I'd love to know if this branch works for you better than what's in master or the last Gem release. Best of luck!

[richardonrails]

Especially with Payola now officially archived/unmaintained, it would be great to see this project in a healthy state.

BulletTrain looks really awesome and is something I would strongly consider for starting a new project. Seeing you contribute back to Koudoku improvements from Bullettrain makes BT even more attractive (versus it having its own custom stuff). So I'd love to see #194 merged/released in a usable state for a vanilla Rails app (perhaps this becomes simpler if you drop some of the default CSS/styling from Koudoku, and rely on Stripe instead -- see #195).