Thread

Who didn’t see THAT coming.

woopee Phil.

I fixed two bugs in CI this morning. It feels good to contribute the community doesn’t it wired.

Oh wait, I don’t see any pull requests from you. Hmm.

This gave me a chuckle this morning. If you don’t want to contribute only download the official releases off the website. Stop complaining.

By the way, I didn’t vote since the average option is “Don’t really care”, that’s not what I’d like to state.

After some thoughts I voted Yes, but it’s important to note that it is not “the best thing after sliced PSDs”. Reactor team worked hard on the framework itself, but in my opinion there hasn’t been enough (or good enough) orchestra conduction.

CI has been since the very beginning an EllisLab product, so its audience habit was to have a “provider” and to act as “customers”. CI users had to make requests and to wait for someone to fulfill their needs.
Then CI became a community project, but establishing a Reactor Team, in my opinion, helped to consolidate dichotomy, just setting a new provider for old customers.

How many times, Phil, you heard “Why can’t we have this feature” or “how long will it take to solve that bug” etc?
How difficult is it ever been to reply “you could fix it by yourself and contribute back”?
This mindset is dangerous for CI as a community project, in my opinion, not RT establishment per-se.

There is a change to undergo for both parts of the barricade:

- Reactor Team must spend more time on coordination that on mere code, learning to communicate and harmonize each single effort
- The community must be helpful, trying to explain what RT should do so that we can contribute better software, in a more effective way. But it also have to stop whining for features, bugfixes etc.

What I feel is that RT should code a lot less but provide much more guidance and leadership, even as a benevolent dictator. It is a successful model that drives project such as Drupal or symfony, so why not?

That is exactly what is happening. CICON was a great chance for the Reactor team to get together and talk about things and we have some brilliant plans.

Already you can see version Milestones for issues. Planned features are issues. We’re vetting every pull request closely and even incorrect spaces or tabs are enough to deny a request until they are fixed. We all know what each other are doing and new features (important ones) have to be vetted by other Engineers. Everything is put past EllisLab so they have first-refusal and the option to totally vito a feature, but this has yet to happen.

We DO know what we are doing, it’s was just 2.0.2 that sucked.

Anyway, one thing we’ll be doing is blogging for EllisLab a lot more, so there will be more information on whats going on.

Is everyone forgetting that prior to Reactor, EllisLab essentially stopped updating CI for months and fans/users were clamouring for answers?

One thing I would like to see is more social media involvement. The @CodeIgniter Twitter account is a joke. All these major changes going on and not one fuckin’ peep. I agree with Phil, there should be a blog that’s at least updated a few times a month.

These major changes were all coming from the event and blogged about. The ones that haven’t been blogged about is because we haven’t had time! I hope to write up a “Working with Git” guide today and blog personally about some of the new things happening + CICON stuff.

@phil & everybody else - sorry for stirring all of this up. http://ellislab.com/forums/viewthread/197712/  None of you deserved any of this, and it was wrong of me to be such an ass about it all.

Is everyone forgetting that prior to Reactor, EllisLab essentially stopped updating CI for months and fans/users were clamouring for answers?

One thing I would like to see is more social media involvement. The @CodeIgniter Twitter account is a joke. All these major changes going on and not one fuckin’ peep. I agree with Phil, there should be a blog that’s at least updated a few times a month.

+1 on more communication.

These major changes were all coming from the event and blogged about. The ones that haven’t been blogged about is because we haven’t had time! I hope to write up a “Working with Git” guide today and blog personally about some of the new things happening + CICON stuff.

I am a developer that hasn’t used CodeIgniter in a good number of years. It just so happens that I know two of the Reactor engineers (now, three) and I came out to NYC to attend this event. I was using CodeIgniter years ago, before the 2.0 release, and before the Reactor team was even envisioned. I was driven off because bug fixes weren’t happening, there was no unit testing, and generally Rails was a much better alternative.

Fast forward to last weekend. I had an absolute great time, was thrilled to hear that the project was actually becoming open source (e.g. I can contribute bug fixes), and the integration with the Sparks tool was the cherry on top. Last weekend I hammered out about fifteen issues between drinking with Phil and carting him off to some random town in New Jersey.

Good times. I am also planning on at least two CI projects, and going to the UK for the Feb. conference.

These major changes were all coming from the event and blogged about. The ones that haven’t been blogged about is because we haven’t had time! I hope to write up a “Working with Git” guide today and blog personally about some of the new things happening + CICON stuff.

I appreciate all the work you’ve done, Phil. I don’t know how you do it. I would never classify myself as a PHP expert, more of an intermediate. I would never waste anyone’s time by trying to contribute poorly written code or fix bugs that end up creating more bugs. I’m not a contributor. I’m just a user. I sometimes feel bad complaining about CI because I can’t contribute.

I think it would be great if the CodeIgniter home page was redesigned, included a blog that could be updated by the Reactor team, and the Twitter account was maintained properly. CICON was going on and the CodeIgniter Twitter account was dead. A missed opportunity.

@dallen33 - The redesign is on the todo list. Not sure about the others since this site runs off the same EE install as all the other EllisLab sites.

@johnbellone - Thanks for all the work you put in. Great meeting you too.

@Developer13 - Thank you. It is hard to not take complaints personally when we are just trying to see CodeIgniter progress and giving up our free time in order to see that goal come through.

@wiredesignz - We are all human. We all make mistakes. Sorry if you don’t agree with the team put in place.

There are only so many hours in a day, and people have families to tend to and spend time with, as well as paying jobs… first & foremost, I applaud the efforts of the Reactor Engineers and thank them tremendously for their time and energy taken to help bring CI where it is today. I’ve made money (and continue to) from your work and the work of other volunteers & contributors. I’d be interested in contributing back too, so looking forward to the guide if/when it gets written.

It’s much easier to harp on flaws than it is to appreciate the good things people do.

Again, thank you ALL contributors, your work and time is very much appreciated.

It’s much easier to harp on flaws than it is to appreciate the good things people do.

Agreed.

Again, thank you ALL contributors, your work and time is very much appreciated.

Agreed.

Thanks to all who are volunteering their time for this.  Sorry I’ve been such a $hithead.