(01-25-2016, 01:28 AM)V I R U S Wrote: What the reason of hiding it, since CodeIgniter is community-driven?!
I believe there is a difference between open source and community-driven. If you look at the history of CodeIgniter, then I'm confused where you community-driven from. It was released by a company who used it for their own products. Decisions about the framework were often done with their business goals in mind, before it languished. At that point, the Reactor group was formed to spear head the direction of the framework and help it hopefully thrive. Now, there is a council that does the same thing.
Don't get me wrong - community input is very important. CI3 has had more community code contributions than any previous release. But there has to be a person or group at the helm with a vision or it becomes a nightmare mess.
To answer the specific question - which has been addressed before - while Phase 1
of then project is in the works, and the inner workings of the framework are being developed, everything is in flux. Design decisions are changing as some things cannot be effectively determined until you're in the middle of it. While key decisions are being made and implemented, the group working on it had to be kept small, or it would simply turn into an eternal argument about the best way to do things, and nothing would ever get done. Once Phase 1 is done, it will be moved to the BCIT account and will be opened up for contributions at that point. And there will still be plenty of things the community can help with at that point, if they desire.
(01-25-2016, 01:28 AM)V I R U S Wrote: But initial decisions were already made, and no one of them by community, right? So, what then is the reason of community-driven framework?
Since your account was just registered this month, you missed the community input stage, but that doesn't mean it didn't happen. Almost the entirety of the CodeIgniter4 category here on the forums were discussions about the future of CI4. This input went on for several months before the council read through them all, weighed the pros and cons of each, and figured out which parts fit together well with the others, which didn't, which fit the spirit of CodeIgniter, etc, and landed on a basic feature list the was going to get implemented.
So - welcome to CodeIgniter!