Hennie de Villiers 14 Years Ago Rather a small fish in the world wide ocean with vision, passion and tenacity than a big fish in a shark tank with only profit and market domination in sight without any soul.Small fish are friends... not food... Nemo http://www.youtube.com/watch?v=1x9W70LJKVwSharks, well they don't change, do they? Please sign in to reply. Reply as... Cancel
Sampsa Sohlman 14 Years Ago Are you watching also Whale wars from TV? I just love that picture Please sign in to reply. Reply as... Cancel
Jonas Yuan 14 Years Ago Nice picture ... thank you, Bryan. Please sign in to reply. Reply as... Cancel
Bruno Vernay 14 Years Ago Given the roadmap: http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/RoadMapI would question the "rapid product releases" and "Liferay was never dependent in any way on Sun for engineering or product development".The state of WSRP in 6.0 CE is also a concern.Thanks for the funny picture and great enthusiasm !Bruno Please sign in to reply. Reply as... Cancel Bryan Cheung Bruno Vernay 14 Years Ago Bruno, while we were in the Sun relationship there were certain things we had to do politically (such as the attributions on the road map) to give the appearance of an equal partnership but the reality is apparent from the commit logs. I'm also not sure why you're questioning the rapid product releases, but keep in mind that we're talking now about six different product versions: 5.1 EE, 5.2 EE, 6.0 CE, Social Office EE, Social Office CE, and 6.0 EE. There's also the Liferay IDE 1.0 and Alloy UI 1.0 that are all being developed and had various releases throughout the last five months. In any case I'm not trying to be defensive or confrontational, I just think it's important that people understand the truth. Please sign in to reply. Reply as... Cancel zaheer mohammed saddapalli Bryan Cheung 14 Years Ago Thats true Bryan ...Live and Let Live Please sign in to reply. Reply as... Cancel
Bryan Cheung Bruno Vernay 14 Years Ago Bruno, while we were in the Sun relationship there were certain things we had to do politically (such as the attributions on the road map) to give the appearance of an equal partnership but the reality is apparent from the commit logs. I'm also not sure why you're questioning the rapid product releases, but keep in mind that we're talking now about six different product versions: 5.1 EE, 5.2 EE, 6.0 CE, Social Office EE, Social Office CE, and 6.0 EE. There's also the Liferay IDE 1.0 and Alloy UI 1.0 that are all being developed and had various releases throughout the last five months. In any case I'm not trying to be defensive or confrontational, I just think it's important that people understand the truth. Please sign in to reply. Reply as... Cancel zaheer mohammed saddapalli Bryan Cheung 14 Years Ago Thats true Bryan ...Live and Let Live Please sign in to reply. Reply as... Cancel
zaheer mohammed saddapalli Bryan Cheung 14 Years Ago Thats true Bryan ...Live and Let Live Please sign in to reply. Reply as... Cancel
Shepherd Ching 14 Years Ago Bryan,The metaphor of shark is overbearing, it is offensive to Oracle. We are just working an independent portal under the war between Oracle and IBM.Survival at the DMZ like Casablanca at WW2 Please sign in to reply. Reply as... Cancel Shepherd Ching Shepherd Ching 14 Years Ago Oracle CEO Ellison challenges IBM: "make our day" in businesshttp://www.nydailynews.com/money/2009/10/15/2009-10-15_oracles_ceo_to_ibm_come_on_make_my_day.html Please sign in to reply. Reply as... Cancel
Shepherd Ching Shepherd Ching 14 Years Ago Oracle CEO Ellison challenges IBM: "make our day" in businesshttp://www.nydailynews.com/money/2009/10/15/2009-10-15_oracles_ceo_to_ibm_come_on_make_my_day.html Please sign in to reply. Reply as... Cancel
Pablo M Mino 13 Years Ago What do you think of the future of CE? Will we watch the same as DotNetNuke, where most module source code is no longer available?I understand that CMS market must be competitive and that surviving from support must be hard, also preventing developers to earn money from your hard work, just hope you don't set a price to each portletThis topic could be worth an article maybe? Please sign in to reply. Reply as... Cancel (You) Pablo M Mino 13 Years Ago Pablo, there is no reason to question the future of Community Edition. We are committed to continuing to making high quality CE releases available. I don't know the details about DotNetNuke, but I think they are VC-funded, which I'm sure adds to the pressure to hit specific numbers in a specific timeframe. Liferay is enjoying strong growth as well but we are ultimately in control of the company and will make our own decisions about how to offer a strong CE and maximize our revenue potential. Please sign in to reply. Reply as... Cancel
(You) Pablo M Mino 13 Years Ago Pablo, there is no reason to question the future of Community Edition. We are committed to continuing to making high quality CE releases available. I don't know the details about DotNetNuke, but I think they are VC-funded, which I'm sure adds to the pressure to hit specific numbers in a specific timeframe. Liferay is enjoying strong growth as well but we are ultimately in control of the company and will make our own decisions about how to offer a strong CE and maximize our revenue potential. Please sign in to reply. Reply as... Cancel
Anil Kumar Sunkari 13 Years Ago yes, that's true this is purely independent.Not let them make this impression again. Thanks Bryan... Please sign in to reply. Reply as... Cancel Lisa Simpson Anil Kumar Sunkari 13 Years Ago I think the you guys have a lot bigger fish to fry than that shark up there. Which license stuff falls under is another bit of distracting trivia. You need to focus on your core objectives - which is working on the next release of your portal product. If you really want to continue to have a future, you need to get to work addressing all of the issues, complaints, etc. that were gathered up and placed into the Proposals wiki. So far, I'm not seeing that very much of that has been addressed. You are also going to have to address your data structure and your security problems. And you have glaring security issues. Added to that, you're also going to have to find some resources address some of the needs of your customers. I've just been checking the Proposals wiki and it doesn't look like very much is being addressed. Please sign in to reply. Reply as... Cancel Pablo M Mino Lisa Simpson 13 Years Ago I'm happy that someone el se is aware that most of the suggestions in Wiki weren't taken into consideration, wrote a post about it, all I got was a negative answer I was concerned when the RC came out, because it meant that the "new features" stage was over Please sign in to reply. Reply as... Cancel Bryan Cheung Pablo M Mino 13 Years Ago Hi Pablo, Lisa. First, thanks for your feedback and sorry for the late reply. It's been a busy month with the Symposium and some personal travels. Regarding the Proposals Wiki, the timeline of things was such that 6.0 was supposed to release early this year but engineering delays got the better of us. I don't quite remember when the Proposals system was first put together but it was probably part way through the 6.0 cycle. We're trying some new initiatives starting with 6.1 that should help address the Proposals Wiki suggestions. 1. We're formalizing Product Management. We're getting to a size where we need to actively consolidate, prioritize, and design the product from a functional and business requirements perspective, not only a feature-by-feature basis but across entire functional areas (WCM, DM, Collaboration, Social Networking) and across the product as a whole. We've done elements of this in the past, but now we're going to make a push into developing a strong Prod Mgmt practice within the organization. This will of course take into account not only our own ideas for Liferay Portal but also funnel in feedback from the community and our customers. 2. We're trying to engineer more capabilities as plugins. This means that while some of the suggestions such as improvements to existing functionality will have to wait for 6.1, others may be released before 6.1 as plugins. 3. We're assigning someone from Prod Mgmt and a Technical Architect to each functional area to own and manage collecting requirements, refining existing features, and innovating new ones. I know it must be frustrating to have to wait so long for some of the requested features to be implemented but we are doing our best and are excited that we've had so much participation from the community already. Please sign in to reply. Reply as... Cancel
Lisa Simpson Anil Kumar Sunkari 13 Years Ago I think the you guys have a lot bigger fish to fry than that shark up there. Which license stuff falls under is another bit of distracting trivia. You need to focus on your core objectives - which is working on the next release of your portal product. If you really want to continue to have a future, you need to get to work addressing all of the issues, complaints, etc. that were gathered up and placed into the Proposals wiki. So far, I'm not seeing that very much of that has been addressed. You are also going to have to address your data structure and your security problems. And you have glaring security issues. Added to that, you're also going to have to find some resources address some of the needs of your customers. I've just been checking the Proposals wiki and it doesn't look like very much is being addressed. Please sign in to reply. Reply as... Cancel Pablo M Mino Lisa Simpson 13 Years Ago I'm happy that someone el se is aware that most of the suggestions in Wiki weren't taken into consideration, wrote a post about it, all I got was a negative answer I was concerned when the RC came out, because it meant that the "new features" stage was over Please sign in to reply. Reply as... Cancel Bryan Cheung Pablo M Mino 13 Years Ago Hi Pablo, Lisa. First, thanks for your feedback and sorry for the late reply. It's been a busy month with the Symposium and some personal travels. Regarding the Proposals Wiki, the timeline of things was such that 6.0 was supposed to release early this year but engineering delays got the better of us. I don't quite remember when the Proposals system was first put together but it was probably part way through the 6.0 cycle. We're trying some new initiatives starting with 6.1 that should help address the Proposals Wiki suggestions. 1. We're formalizing Product Management. We're getting to a size where we need to actively consolidate, prioritize, and design the product from a functional and business requirements perspective, not only a feature-by-feature basis but across entire functional areas (WCM, DM, Collaboration, Social Networking) and across the product as a whole. We've done elements of this in the past, but now we're going to make a push into developing a strong Prod Mgmt practice within the organization. This will of course take into account not only our own ideas for Liferay Portal but also funnel in feedback from the community and our customers. 2. We're trying to engineer more capabilities as plugins. This means that while some of the suggestions such as improvements to existing functionality will have to wait for 6.1, others may be released before 6.1 as plugins. 3. We're assigning someone from Prod Mgmt and a Technical Architect to each functional area to own and manage collecting requirements, refining existing features, and innovating new ones. I know it must be frustrating to have to wait so long for some of the requested features to be implemented but we are doing our best and are excited that we've had so much participation from the community already. Please sign in to reply. Reply as... Cancel
Pablo M Mino Lisa Simpson 13 Years Ago I'm happy that someone el se is aware that most of the suggestions in Wiki weren't taken into consideration, wrote a post about it, all I got was a negative answer I was concerned when the RC came out, because it meant that the "new features" stage was over Please sign in to reply. Reply as... Cancel Bryan Cheung Pablo M Mino 13 Years Ago Hi Pablo, Lisa. First, thanks for your feedback and sorry for the late reply. It's been a busy month with the Symposium and some personal travels. Regarding the Proposals Wiki, the timeline of things was such that 6.0 was supposed to release early this year but engineering delays got the better of us. I don't quite remember when the Proposals system was first put together but it was probably part way through the 6.0 cycle. We're trying some new initiatives starting with 6.1 that should help address the Proposals Wiki suggestions. 1. We're formalizing Product Management. We're getting to a size where we need to actively consolidate, prioritize, and design the product from a functional and business requirements perspective, not only a feature-by-feature basis but across entire functional areas (WCM, DM, Collaboration, Social Networking) and across the product as a whole. We've done elements of this in the past, but now we're going to make a push into developing a strong Prod Mgmt practice within the organization. This will of course take into account not only our own ideas for Liferay Portal but also funnel in feedback from the community and our customers. 2. We're trying to engineer more capabilities as plugins. This means that while some of the suggestions such as improvements to existing functionality will have to wait for 6.1, others may be released before 6.1 as plugins. 3. We're assigning someone from Prod Mgmt and a Technical Architect to each functional area to own and manage collecting requirements, refining existing features, and innovating new ones. I know it must be frustrating to have to wait so long for some of the requested features to be implemented but we are doing our best and are excited that we've had so much participation from the community already. Please sign in to reply. Reply as... Cancel
Bryan Cheung Pablo M Mino 13 Years Ago Hi Pablo, Lisa. First, thanks for your feedback and sorry for the late reply. It's been a busy month with the Symposium and some personal travels. Regarding the Proposals Wiki, the timeline of things was such that 6.0 was supposed to release early this year but engineering delays got the better of us. I don't quite remember when the Proposals system was first put together but it was probably part way through the 6.0 cycle. We're trying some new initiatives starting with 6.1 that should help address the Proposals Wiki suggestions. 1. We're formalizing Product Management. We're getting to a size where we need to actively consolidate, prioritize, and design the product from a functional and business requirements perspective, not only a feature-by-feature basis but across entire functional areas (WCM, DM, Collaboration, Social Networking) and across the product as a whole. We've done elements of this in the past, but now we're going to make a push into developing a strong Prod Mgmt practice within the organization. This will of course take into account not only our own ideas for Liferay Portal but also funnel in feedback from the community and our customers. 2. We're trying to engineer more capabilities as plugins. This means that while some of the suggestions such as improvements to existing functionality will have to wait for 6.1, others may be released before 6.1 as plugins. 3. We're assigning someone from Prod Mgmt and a Technical Architect to each functional area to own and manage collecting requirements, refining existing features, and innovating new ones. I know it must be frustrating to have to wait so long for some of the requested features to be implemented but we are doing our best and are excited that we've had so much participation from the community already. Please sign in to reply. Reply as... Cancel