I have just started using Fuel at work, and there is a team of 8 developers here at our agency also using it, so we are really giving fuel a baptism of fire by using it on about half a dozen new projects at once.
We are not planning on jumping ship to another framework, as we have already wasted enough time pissing around with Code Igniter, so unless we see the light and start using Ruby on Rails, we are committed to using Fuel for the long term.
Therefore it would benefit us to contribute towards Fuel.
The general impression I have of Fuel so far that is that there is an awful lot of functionality available, but there are certain things that are lacking that are not necessarily bugs, but are features that could possibly be implemented.
The problem is, if I were to dedicate a day to adding certain functionality, but it were rejected as a pull request, then I'd be a little bit stuck. We don't want to be in a position where we are maintaining our own fork and backporting your fixes to it, we want to be using and contributing towards Fuel.
So some sort of discussion needs to be raised about feature requests, and then allow anyone from the community to see approved feature requests to be able to work towards it.
Things get discussed in IRC with the Fuel developers, but it is unfair to rely on them to do all of the work, or have to wait for them to get X, Y and Z working. But as they are discussed in IRC, they can be easily forgotten.
I noticed there is a Roadmap that has just been created, but this is too general, and only applies to the core fuel developers. There needs to be something more specific that either breaks down these tasks, or shows approved feature requests.
I don't want to put issues in GitHub for things that aren't bugs, as it just feels like I am looking a gift horse in the mouth. I want to contribute towards a pre-defined goal.
The interstateapp makes it possible to split items on the roadmap in different sub items to make them more manageble. It's something I haven't looked at.
At the moment, we use github's issue tracker for feature requests as well. I feel we should continue to do so, as it allows some interaction through the comments. And we have IRC to have a more in-depth discussion.
It would indeed be wise to have some sort of sign-off before you start working on something. In general, features are marked as such in the issue tracker. As long as we're not sure it should be included, it will have a status 'pending' as well. Once the decision has been made the feature should be included, the 'pending' status is removed, which means you can start if you want.
Using GitHub Issues for managing feature requests seems ideal as they can eventually be related to a pull request.
I just felt like I was moaning by writing something in there. I didn't write in the Issue tracker because I wanted someone else to do it for me, I just wanted to get approval from the Fuel developers before I started working towards improving something.
I know exactly what you mean about wanting changes in the core and them being refused. It was exactly these frustrations with CodeIgniter that spawned Kohana and got me and other developers banging on at EllisLab to let us interact.
It is incredibly important for developers to get involved because the more the merrier, as long as we are all pushing in the right direction.
GitHub issues rock for this. Make an issue marked as a feature request. If one of us wants to reserve it or are already working on it you'll find out as soon as we reply what is going on. If we are not working on it but would love for it to be done then you'll find out right away and other developers will see what you are up to.
Meaning if anyone spends a day building a feature and finds out somebody else has already done it... well thats their fault for not looking at the issue tracker first. AMIRITE?!
Everyone is welcome, this framework is built by the community.
Donate
