Add new maintainers

[Revisor]

It's a nice and useful library, but it needs more care - solve outstanding issues, tag release versions regularly.

If you don't have the time or willpower to work on it, add more maintainers. Please don't let it die.

[ksn135]

👍

[RonRademaker]

Anyone who (like me) likes the 1.0 branch better than where master was heading is welcome to join me on https://github.com/RonRademaker/Finite, I'll actively maintain this 1.0 fork and use semver for new releases.

[phillipsnick]

@RonRademaker haven't looked too much into master vs 1.0, what were the major changes?

[tortuetorche]

@RonRademaker I'm happy with the master branch for both my Laravel 4.2 and 5.1 applications.

[RonRademaker]

@phillipsnick basically the StatefulInterface has been replaced by a StateAccessor that by default uses a public variable state. It's more like the winzou/statemachine I think. I started using and went back to 1.0 fast (it's a matter of taste of course).

[Revisor]

My preferred solution would be for @yohang to add more maintainers to this repo. This is a known quantity, it has articles written about it, two weeks ago someone mentioned it by the way at a conference - it has the most attention in bug hunting and issues.

If that doesn't work, a fork would also be a solution, but forks always have to start from the scratch regarding visibility which might be a disadvantage.

[yohang]

Hi,

I tweeted about adding new maintainers few weeks ago, I agree, send me a mail if interested.

And I'll have some time for updates very soon.

[Revisor]

Thanks, Yohan, we use the library, love it and would like to help. We'll send an email to you.

[tortuetorche]

Hi @yohang,

Can you add me as a contributor, please?
To refresh your mind, I'm the author of Finite State Machine and Finite Audit Trail traits for Laravel.

I'll not be a big contributor, but I can send fix, from time to time.

Cheers,
Tortue Torche