Are there any public planning where the community can participate something like a roadmap.

Because it’s good that we write code modifications to CI that will need to projects and commit to a VCS(before on bitbucket, now on Github), but for a more solid progress I think there should be a path to follow.

I would like to see a roadmap based on feedback from Ellislab developers and other codeigniter community members.

Something like other open source projects.

The Roadmap comes in the form of Issues attached to Milestones on GitHub.

https://github.com/EllisLab/CodeIgniter/issues

Well it is fine, but I prefer something like an official Roadmap with a task/todo list. So we can contact with the feature owner and submit code.

Or a thing like: http://fuelphp.com/roadmap

But with sub… sub tasks lists in a way like “Divide an conquer”.

I think that is an easy way to not duplicate efforts.

I know what Interstate is - from that page you can see that I have an account - but I don’t understand how you think that leads to better integration? And how is it more Official?

My adding Issues to milestones we can add planned features to a Milestone, which clearly show who is working on them, allows for conversation and will allow for the association of commits. The Fuel roadmap just shows “Dan is doing X” with no room for discussion or anything useful. On GitHub I’d just add a comment.

If you think Interstate would be a better option I’d have to disagree. The GitHub milestones are a little empty right now, but thats because we’re still working out what goes where.

Hello Phil,

What I say is, additional to official roadmap (who should be decided by a board [ellislab and others community leaders]) developers from the rest of the community can request new features. The board can disscuss what of these new features are important and relevant to add officialy to the project, make plans public and then any developer can implement this ideas, of course following a sets of rules.

All this is apart from other submited code by the community members( patches, additions, plugins etc.)

Seeing these roadmap/plans as a complement to GitHub milestones because on this (https://github.com/EllisLab/CodeIgniter/issues) I can see any kind of issues and at least for me is a little confusing to know what new features expect on the next stable release of codeigniter appart from bug fixes.

My intention is to have a clean and clear vision about the path that follows the framework.

I think that making something like this gives certainty to the project and makes the community more involved with a positive impact on the framework getting better and robust through an increased community complicity in official releases.

Anyway thank you for your answers and I also apologize for my lack of expertise in the English language.

It’s pretty simple really.

We already have UserVoice for talking about and planning potential new features. When they are accepted we’ll make a new Issue and mark it with “New Feature” and assign it to the correct Milestone.

When it’s done we’ll close it on UserVoice and GitHub, so people can see what has been done for the new feature and it will help provide a changelog.

It works fine, and we don’t need a third place for a Roadmap. We just need to improve the use of labels on GitHub as we go.

I take a deep look, into github issues sections, and I can see what you say.

Any update on this?

What update were we waiting for?

Today I was looking at the CI GitHub repository, discovered the milestones, searched on Google and this Forum and found this thread.

I was wondering if those are still in use (the milestones), or if there is to much other work to be bothered with it?

Since you said:

Phil Sturgeon - 27 August 2011 05:54 PM

“...The GitHub milestones are a little empty right now, but thats because we’re still working out what goes where.”

As a CI supporter and user I’m very curious in were Ci is going.
I’m working on a lot of app’s in CI so I naturally wonder what how and when the next release will be.
My interest peeked more when I landed on a nightly build for CI3 docs through Stack Overflow.

Currently there is not much of a roadmap other than the basics, which are easy to outline:

2.1.1

Should come out soon with some 2.1.0 bugs fixed.

3.0.0

Sparks
Unit Testing
OSL (different license, but the same usage)
Possibly some autoloading

A lot of those things are still unplanned as to how exactly they will happen as all the team members (in EllisLab and us Reactor Engineers) have been busy. For me I spend an hour a day just peer reviewing code, so rarely get any time left to actually work on that todo list.

The fact is that the community is driving progress at the moment, and they are doing so by fixing bugs or improving existing code. If you just look at the activity on GitHub you’ll see 2 or 3 pull requests merged every day and there are still 164 active requests.

If the community would help peer review existing pull requests it would open up time for us to work on new features. There are a few active people on GitHub, but there could certainly be more!

I understand.
Thanks for your reply and all the work!

Yes 165 as of today actually :D.
I wish I could be of any help in peer reviewing, but I don’t think I am of much use for this project as of now in that department. Even the smaller commits It’s hard to get a sense of where the piece fits in the whole project and if it’s well written for CI.

I’ll just keep it to trying to help people with q’s on Stack Oveflow as for now :D

That’s a bit odd Phil, reading your statements gave me the feeling like you really never ever heard or seen what the rest of the industry calls a roadmap.
But thanks to drop one here I still think that roadmaps for an OS project are a good way to keep people interested over a long period and plan their moves as well in regard of it.

EllisLab has never ever had a roadmap for CodeIgniter. Ever. They are specifically against them but it creates false expectations of what is going to happen, imposes deadlines which are unfair, arbitrary and not always possible to stick to. That’s not my opinion, that is theirs.

I have no problems with that.

We do however have issues that get marked as accepted, or some notes of things we want to do that get marked to certain milestones.

What am I going to do in the next month? PR mainly. Reviewing peoples code and checking out whats up. Maybe I’ll work on some autoloading if I have the time. Who knows.

What are you going to do for CodeIgniter this month?

A while ago I was not around here.

I think that a roadmap is not always to force to set deadlines, but to know what the future holds for the project, then community knows where to focus their efforts.

I share a little bit Patlecat’s idea that sometimes EllisLab and some of EllisLab collaborators are not open minded to others ideas for codeignter and express their rejection of these ideas in a categorical and not so diplomatic way.

But, I liked your last sentence: What are you going to do for CodeIgniter this month?

It’s a good start for all of us.