theappslab - Latest Comments in Fixes and New Stuff for Mix

Re: Fixes and New Stuff for Mix

Jake — Wed, 14 Jan 2009 12:32:41 -0000

If you poke around here, you can trace the history of Mix. The short version is that we're a small team of 4 (2 developers), driving innovation within Oracle, i.e. not a product team per se. We have Rails skills already, so it was an easy way to get started and make some headway.

Mix is JRuby on Rails, running on the Oracle stack (apps server and database); that's what it is now, but I have no insight into its future. We no longer manage it, so you'll want to ping the Marketing team (on the Mix blog?) for specifics.

Re: Fixes and New Stuff for Mix

Saleem — Wed, 14 Jan 2009 01:37:29 -0000

This is a great place, well done for putting this together. Now answer this are you using anyting from WebCenter here? is not why not? and where can I find something similar to Mix built on WC Suite.

I could use this site as a proof of concept for my entire E2.0 strategy :)

Re: Fixes and New Stuff for Mix

davidhaimes — Thu, 03 Jan 2008 18:57:05 -0000

Fair point, it's probably more a case of showing that there is a lot we can say and how well that is received by customers.

Let me know if you need help with that!

Re: Fixes and New Stuff for Mix

Jake — Thu, 03 Jan 2008 13:31:01 -0000

I understand the reasons, since we've all had the same training on what you can/can't say. You know I can't provide guidelines on this aside from 'read the policies legal has established'.

However, saying something is better than saying nothing, and most legal restrictions, e.g. rev rec, are well understood by customers. Even if they don't like the answer or think it's evasive, customers would rather have that than silence.

People need to establish a voice anyway, like you've done.

Re: Fixes and New Stuff for Mix

davidhaimes — Thu, 03 Jan 2008 13:03:00 -0000

One reason people can be cautious communicating in an open forum is they are not sure what info is ok to share and what legally we cannot.

Providing guidelines for oracle folks in this area would be a good idea.