Thread

I think beer tastes nasty… :sick: yuck!

Give me a Chi w/ Soy.

Give me a Chi w/ Soy.

I’ll swap you a Chi w/ Soy for an EE with 2.0.

😊

I would like to add to the evolutionary process described so brilliantly by supersusie:

#25. Operating System debate

I wouldn’t think it would be too fair if they went and added them in to the system as standard as then it would effectively kill of any 3rd party offerings.

You mean like Apple?

#26. Discuss the authenticity of this video: http://www.youtube.com/watch?v=XRCbkBfdBrQ

Don’t drink and fly!

Do we really need beer with a base EE install?  I’ve built about 67 EE sites over the past two years and only ONE of them needed beer.

I’d prefer Scotch, but I don’t know how to write that extension.

Just use a Global Variable

{embed='Barley|Yeast|Water'}

Just don’t drink and code.  You might get Wordpress…Ooops!

You’re going to have to be more specific about what communication you think is lacking.  I can’t say that we will choose to communicate exactly what you’re looking for, it’s certainly our prerogative to communicate what we want about upcoming products, but I would like to know what information you’re looking for that is not being addressed.

For me, as a 4-year user of ExpressionEngine, and someone who relies on it more than anything else for my business, the one thing that has frustrated me more than anything is lack of planned features.

Sure, features can be cut, and that is fine.

But at the very least, seeing a list of planned feature additions would save me a hell of a lot of money. If I knew, for example, that Module X is planned to be released as part of EE 2.0, then I would know not to have Module X built from scratch at a rate of $75-150, depending on who I use to code it.

I can then plan around those planned features, brainstorming changes, etc. Everything would be a lot more proactive on my end, than knee-jerk reactive when EE 2.0 is released.

I know a File Manager is coming, but that’s about it I think. Oh and Accessories, which look cool. But I’d love to see a “Here’s a list of what’s planned - caveat, this is planned and not all may make the 2.0 release”.

Heck, Microsoft showed off their New Xbox Experience at E3 like 6 months ago. It launches Nov 19, and they had to cut quite a bit out of it, with those things planned to be included after the launch. Sure, it’s disappointing, but knowing what is coming is still very, very beneficial months in advance rather than a week in advance (or days, or day of release).

Anyway, my two cents as one of the top EE cheerleaders in the world. 😉

Oh, sorry for getting this thread back on track! :(

You’re going to have to be more specific about what communication you think is lacking.  I can’t say that we will choose to communicate exactly what you’re looking for, it’s certainly our prerogative to communicate what we want about upcoming products, but I would like to know what information you’re looking for that is not being addressed.

Heck, Microsoft showed off their New Xbox Experience at E3 like 6 months ago. It launches Nov 19, and they had to cut quite a bit out of it, with those things planned to be included after the launch. Sure, it’s disappointing, but knowing what is coming is still very, very beneficial months in advance rather than a week in advance (or days, or day of release)

And the world loves Microsoft right?

Anyway I’d like to add that Australian beer is the best in the world 😊

And the world loves Microsoft right?

People don’t dislike Microsoft because they showed off their product 6 months ago.  There are plenty of other reasons to not like them. 

I have to agree with most of Andru’s points.  Given that EE 2.0 was schedule to be released (or at least previewed) a couple of months ago, I would venture to guess that a majority of the development has been done.  In his post announcing that EE 2.0 would be delayed, Rick mentioned that this is indeed true and the team has been working on the details.  As such, I would guess that a large portion of the features have been completed or are near completion.  Therefore, there is no guess work on if it will be released with 2.0.

So, why not release which features are done?  That’s a genuine question.  I don’t mean it in any critical way.

The release of any product is an expectations game.  Undoubtedly, it’s expectations that have caused EE 2.0’s delay. Given the quality of the current branch of EE, we wouldn’t accept an unfinished product.  Honest communication from you guys (Ellislab) foster realistic expectations.  Now that 2.0 has been delayed(and it seems that the preview is relatively far away), I would urge EllisLab to spend the 10-20 minutes a week that it takes to make a simple blog post detailing the basic progress of the week.  I’m not talking about anything elaborate here—just a few sentences.  That’s what I expected with the “regular updates” decree. 

Moral of the story—a little transparency goes a long way.  As accessible as you guys are, the status and progress of EE 2.0 has not been a transparent process.  It doesn’t have to be.  But given the circumstances, I think it should be.  If for no other reason than to be a little more fair to people in a similar situation as Andru (such as myself).

/rant

And the world loves Microsoft right?

People don’t dislike Microsoft because they showed off their product 6 months ago.  There are plenty of other reasons to not like them. 

 

No but they dislike them because they promise the earth and deliver little (see Vista for example). It’s surely better to over delivery then under? This can probably only happen if they don’t comment on features that haven’t been finished or started yet.

I do agree that any baked in features or critical stuff should be mentioned, even as a teaser so we have an idea of what to expect. Even if it’s just to satiate my hunger for new information!

Moral of the story—a little transparency goes a long way.  As accessible as you guys are, the status and progress of EE 2.0 has not been a transparent process.  It doesn’t have to be.  But given the circumstances, I think it should be.

The problem here, as I see it, is that the cat’s already out of the bag, the toothpaste doesn’t go back in the tube.

The folks at EE wanted very much to create a somewhat more revolutionary (than evolutionary) leap from 1.x to 2.0. Everyone would have been better off—EE customers, EE support staff, EE development staff—had there be NO pre-announcement of 2.0 so far in advance of any actual release date. In retrospect, of course, that pre-announcement could be considered a huge mistake, although it happens frequently in the application development business. Those who don’t learn from history are destined to repeat it—that kind of thing.

However, since the cat’s not going back in the toothpaste tube any time soon, and assuming that EE 2.0 is tracking on a decent schedule for release sometime in late 2008 or even late 2009, I agree that having some regular morsels of finished, baked in new features (along with the video demonstrating such) would benefit everyone associated with EE.

Makes sense, no?

Makes sense, no?

Cats in a toothpaste tube makes perfect sense to me.

This horse has been beaten to death in the past, but I’ll reiterate.

But at the very least, seeing a list of planned feature additions would save me a hell of a lot of money.

No, it wouldn’t, and speaking frankly, if you make business decisions based on published future feature lists of another company, you’re making critical business mistakes.  Until you actually use and implement a certain application feature in your installation, you have no idea if it is going to meet your individual needs.  So you will see us repeating the mantra: make decisions based on what’s available now in delivered product.  This isn’t PR hooey, it’s good business sense.

I would urge EllisLab to spend the 10-20 minutes a week that it takes to make a simple blog post detailing the basic progress of the week.  I’m not talking about anything elaborate here—just a few sentences.  That’s what I expected with the “regular updates” decree.

I’m not going to ask D’Allard or myself to stop being productive to try to make “converted some more code this week” sound interesting.  I will, however, plan to write a blog post about why the process is taking longer than even we had expected, what the specific challenges are, etc.

I do agree that any baked in features or critical stuff should be mentioned, even as a teaser so we have an idea of what to expect. Even if it’s just to satiate my hunger for new information!

We’ve done this to an unprecedented degree with 2.0, and it’s been fun for many, but it’s undoubtedly contributed to 2.0’s length of development, sometimes requiring complete shifts of dev team priority to get X ready for a teaser, and then to create the teaser.  Do you really want 2.0 to be further delayed just to satisfy your curiosity?  Which is actually better for you?  More teasers, more questions answered, or 2.0 in your hands?

I agree that having some regular morsels of finished, baked in new features (along with the video demonstrating such) would benefit everyone associated with EE.

In all seriousness, how?  How will you benefit from seeing the videos?  How will EllisLab benefit from the developmental disruption to create them?