Sorry for bad English , I was chosen one framework for my company in 6 year .I want to know how long fuelphp can improve and maintain ? I have read some of blog which speak 2 member of team to leave ? I feel to worried about that new . I love structure of fuel, but i fear it can be abandoned . I need answer to persuade my director to chose fuelphpframework . Thanks in advance
Some leave, other joins the team. They are already working on 2.0 so i guess they dont want to abandone the project.
FuelPHP is a great framework, maintained by great developers. As much as will be collaborators on any open-source projects they will just not be abandoned.
Absolutely not. We're going strong, we will go on.
You don't need to be a 'team member' to contribute to the framework, almost 200 people already did, from simple one-liners to complete functionality like recently soft-delete and temporal model for ORM.
FuelPHP is a community framework, and it will stay that way.
As for the continuity, my employer has selected FuelPHP almost two years ago, and allows me to work on the framework in company time to ensure it's continuity. For me, that's not (only) about development, but more about strong project management, the ability to set a roadmap, and to make sure everything stays on track. Also, it is important that new functionality is introduced gradually, and that special care is taken to make sure compatbility is guaranteed or that changes are small enough to make upgrade easy.
We understand that companies have a (sometimes sizable) investment in the development platform they have selected, and that switching frameworks or having to upgrade to a not-compatible new version is an expensive undertaking.
Once you get to a certain size as open source project, you stop being working on a "hobby", and start working on a "product". When means listing to your users. Spend time supporting them. Make sure the framework supports their business.
One of the reasons some early team members left was because they were reluctant to make the switch to "adulthood". They wanted to continue to use it as a pet project that they can change as they saw fit. You can't do that when people depend on you and your work. So, from a framework (and from you as a user) point of view, it's a good thing they are no longer a member of the team, and not a bad thing!
Donate
