Open another topic or pm the user. Please.

Someone should copy Rick’s post to a stand alone locked sticky about where CI/EE will most likely go. As someone else mentioned, it was a great introductory to where things came from, relationships to each-other, and the futures they hold.

Cheers,

—Volte

I loved Rick’s response. This is what we’re doing, and this is why. Make your decision to use CI based on this concrete statement.

Now, get on with your apps.. (hrmm… credit card library… might put that on the todo list!)

Thanks for the great response Rick! I think this is exactly what so many people in the community have been wanting. Some kind of info about the goals of CI. The post really helped clarify what EllisLab’s goal is for CI and it also helps explain the lack of response (you have a very small team who is turning out amazing products - and you want to tie it closely to your commercial product so code diversion is not good). As mentioned above, if we could get Rick’s post stickied in a closed thread, I think it would go a long way in giving people an understanding of what the purpose is behind CI.

Sidenote: I think the community/EllisLabs has been having some miscommunication on terms such as “roadmap”. I think the community in general was begging for what the overall goal, purpose, and future mission of CI is (this has not been made real clear - it was always very vague, at least to me - we need to know this so that we can choose where to best invest our time) and not necessarily a roadmap. When it was asked, the community would get a “we have no roadmap” response. The post by Rick has pretty much cleared up my understanding of what CI is and what CI is not.

Thanks a lot Rick and EllisLabs! Keep up the great work!

I agree with the others… Ricks posting should be made sticky to prevent too much discussion about the future of CI…

But there is still one thing that should be changed - currently, the Bug Tracker lists ~40 Bugs as “New”... and this doesn’t help much because it looks like there is nothing happening (I know that most (most likely all) of those bugs are fixed - but if somebody doesn’t read the tickets and the bug-board, he won’t know this)... so I think it would be great if somebody at Ellis Labs (Derek?) could go through the list and mark everything as Resolved/Fixed/Closed (whatever ) that will be fixed in the next version…

I think it would be great if Rick (or Derek, or whoever ) could write some kind of “we’re alive and working on [something]” postings from time to time to keep the community informed about the progress - I’ve been on the YaBB/YaBB SE-Dev-Team for quite a while so I know how “users” think - the constant “when will the new version be released”, “when will [add feature here] be added?” and other questions like that could get quite “annoying” - and i think they can be reduced if there is a constant flow of information from the devs to the users…

jm2c - other than that, you’re doing a great job and CI is awesome

We’re alive and working on something.

We’re actively going through the bug reports… bear with us, but if you compare the SVN to the download there is already good evidence of this.  I’m not going to make this thread sticky, but not because it isn’t useful, just because the information gets stale pretty quick.  We’re working away.

Perhaps, a synopsis of Rick’s statement could be added to the main CodeIgniter webpage.  I think his statement does an excellent job of explaining where CI came from and how it is maintained.  Maybe adding a “learn more” link after the last sentence in the “Welcome to Code Igniter” paragraph on the homepage.

BTW: I think there is a period missing after the last sentence in that first paragraph on the homepage… “and if you’re tired of ponderously large and thoroughly undocumented frameworks”.

Neovive - 11 June 2007 08:49 AM

Perhaps, a synopsis of Rick’s statement could be added to the main CodeIgniter webpage.  I think his statement does an excellent job of explaining where CI came from and how it is maintained.

That’s what I was suggesting.

—Volte