Reactor Engineers

[eluser]Vheissu[/eluser]
Phil,

I have started writing an auth library, but time is major a restriction for me as I also work full-time with lots of overtime hours and balance freelance as well. Instead of forking Ion Auth I have started writing a role based auth library called WolfAuth: https://github.com/Vheissu/WolfAuth-for-Codeigniter-2.0- it's not driver based at present.

I was thinking of using the Codeigniter drivers functionality in 2.0, but due to lack of documentation and not much time to sift through code, I've shelved that for now. The library at present mostly works, but I've hardly tested it really.

You can restrict controllers and functions by using the restrict() and restrict_usernames functions which let you restrict things to role IDs and usernames (which works). But because I am only one person, things take longer and because I have most likely not been careful / repeated myself big time in parts of the code, I'll probably have to rewrite the code-base a little.

If others would like to contribute to the library, please by all means do so. Any contribution to the library would be appreciated. I would like to get it to the point where integrating it and using it is really easy. I am using helper functions a lot to simplify things instead of having to go $this->wolfauth->login you can go login(), etc.

Back to the situation at hand. Because all of the developers on the Reactor team have varying opinions, personal preferences and their own ways of how things should be done, won't this hamper any chance of an auth library being integrated into Reactor, amongst other needed things? How are things decided? Is it majority wins?

What is the process of fixing / integrating something in Codeigniter Reactor? Also, do EllisLab get any say in what you integrate as well? The process doesn't seem overly transparent to me and I am sure others as well.