Phil Sturgeon, one of those selected to a spot in the Engineer group of the CodeIgniter Reactor community branch, has posted a few thoughts of his own about the moves EllisLab has made and the reaction from the community he's seen.

Since what some have referred to as "CodeIgniter-gate" EllisLab's have done a great job of listening to the points raised by me and other members of the community and in part I believe we have effected change. [...] Good news right? Hell yes. This is exactly what the CodeIgniter community has been looking for. EllisLab need to keep their core version working for themselves of course and have always suggested that if a feature is to be integrated then it needs to be heavily tested first.

He follows this with a "but" in the form of a few common comments from the community - unfortunately negative. He also mentions the UserVoice forum where developers can suggest new features and hash out ones suggested by others. If you'd like to contribute code, you can still fork the main repository for now and push back with pull requests.

The CodeIgniter project (from EllisLab) has posted the latest community efforts they've been making to try to advance not only the framework but the CodeIgniter community as well. They've introduced three new things - CodeIgniter Reactor, Core and UserVoice.

EllisLab, Inc. is formally announcing CodeIgniter Reactor, a community driven branch of CodeIgniter that will enable faster adoption of the best community submitted code to the CodeIgniter open source PHP framework. CodeIgniter Reactor will be available the first quarter of 2011. A second branch, CodeIgniter Core, will be maintained by EllisLab and incorporate the best of Reactor at a slower, more enterprise-friendly pace.

The Reactor branch will be the one headed up by the six engineers they selected from the CI community. EllisLab has handed this branch off into their capable hands. The Core branch will remain as-is and will be updated as EllisLab sees the need for some of their products. The UserVoice system has been set up to allow other developers a voice in what they think needs to be included in the next versions of the framework. If you're interested in contributing, you can find that here.