Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin status? #316

Open
bitboxer opened this issue Jun 29, 2014 · 15 comments
Open

Plugin status? #316

bitboxer opened this issue Jun 29, 2014 · 15 comments

Comments

@bitboxer
Copy link

Hei @obrie , just want to know if this plugin is no longer maintained?

@radar
Copy link

radar commented Jul 1, 2014

@bitboxer I have emailed @obrie several times about this and have received no replies. There's also a lot of issues that haven't been replied to, which leads me to thinking that this repo is no longer maintained. 😢

@bitboxer
Copy link
Author

bitboxer commented Jul 1, 2014

@radar I am now starting a fork here : https://github.com/automat-gem/automat and will try to rename the gem and go through the pull requests here to cleanup the gem. Any help is welcome!

Let's restart this like the cancancan gem did for cancan 👍 !

@seuros
Copy link

seuros commented Jul 1, 2014

@bitboxer are you interested in joining this project instead ?

@bitboxer
Copy link
Author

bitboxer commented Jul 1, 2014

Sorry @seuros , but I am not interested in a rewrite. There are tons of different state machine gems out there. That particular one only had one week of activity and than stopped. I am interested in maintaining the state_machine gem because I have a few bigger projects that rely on the unique feature set of it.

@seuros
Copy link

seuros commented Jul 1, 2014

@bitboxer it not a rewrite, it same with all the plugins extracted and with passing tests. anyway it ok!

@bitboxer
Copy link
Author

bitboxer commented Jul 1, 2014

Than you should say so in the readme. It's not very polite to just grab the code and reuse it without acknowledgement in there. And it would also help people to understand what that gem is 😉 .

@seuros
Copy link

seuros commented Jul 1, 2014

It is in the code, the README was just a generic one as you can see. It still a WIP !

@jufemaiz
Copy link

jufemaiz commented Jul 7, 2014

@radar any thoughts on what's a good alternative to work with?

@radar
Copy link

radar commented Jul 7, 2014

@jufemaiz I like the look of the workflow gem.

@jufemaiz
Copy link

jufemaiz commented Jul 7, 2014

@radar thanks for the speedy reply sir! Will look into it :)

@momer
Copy link

momer commented Jul 15, 2014

👍 looks like I'll be using Workflow for a new project here. Good reco @radar

@chunkerchunker
Copy link

@radar, can you tell me if there are any plans to move spree off of state_machine? (it seems that'd be a major change, so i assume not and that none of the state_machine issues are blocking forward dev?)

thanks-

@radar
Copy link

radar commented Sep 8, 2014

@chunkerchunker I can't speak for the current state of Spree, because I stopped working there a month ago. When I was working there though there were no plans (immediate or otherwise) to move off state_machine. The state_machine gem works in all the situations that Spree requires it to work in and Spree relies on it heavily for checkout flow customization.

Therefore there is no reason for Spree at all to move off the state_machine gem. An unmaintained gem that still works in all cases is not a good reason to move.

@chunkerchunker
Copy link

@radar Thanks for the insight. I didn't know you'd left spree. I just took a look at your blog.. LIFX sounds like it'll be a lot of fun :)

@gemtainers
Copy link

#331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants