gt-state_machine and GemMaintainers

[gemtainers]

Becouse of CanCan, StateMachine and others I deside to create OpenSource organization to maintain gems.

People disappear, lose their passion about coding, get new interests, families, children. But if us many we can support gems much longer.

I dont pretend to be an expierenced ruby developer, but I can do administarative work: managing teams, members, approve simple pool-requests.

If you think it good idea and want to support some inactive gems, not life time, maybe just a little - welcome to organization.

I think there is two ways to reanimate gem:

1. Current maintainer can transfer gem

2. If maintainer have no response - we can add to gem prefix 'gt-' and publish it under new name

https://github.com/GemMaintainers

[carols10cents]

There's actually discussion among the rubygems team about a process for putting gems "up for adoption" that you might be interested in: http://www.benjaminfleischer.com/2014/08/17/rubygems-adoption-center/

[huoxito]

hey I've started doing some work to support activerecord 4.2 because spree depends a lot on it. The code lives here for now https://github.com/huoxito/state_machine/tree/spree-rails4.2-upgrade and my current intention is drop everything non activerecord related and move it to spree-contrib organization with a new name. Will inform here once thats done in case anyone else wants to help.