Closing Survey Feedback “Got to know lots of Liferay Facts.Was surprised to see that Liferay even has its University” “We use the community edition because the policy of our enterprise is to use open source software (that option wasnt among the answers).” “I dont see any reason to use EE, but that was not an option.” "Hello, I really like this initiative taken by Liferay. Its really very good to know that Liferay took things to individual member level and provided them a chance to share their experience with Liferay." “I was expecting another type of survey. Something more related to the problems we encounter when developing. For instance interporlet comunication, speed in development.” "Hi, it is a great idea to do this, I will participate even next time." “This survery, its a great idea. Manage a so huge community its not so simple. IMHU James Falkner contribution has been a good decision for a product like Liferay.” “I hope this survey will help to improve the Liferay Portal quality” “More open questions would be interesting. This is only superficial information not in depth.” Other areas to focus on “Got to know lots of Liferay Facts. Was surprised to see that Liferay even has its University” modularity An upgrade process that works without trashing my data in Oracle. Dont delay the release. Integration with Maven "Usability & Consistency -‐ Its getting better and better, but.... It is difficult to design new intranet for our customer -‐ in every project we have to fix lot of bugs or change lot of behaviors... Some examples: 1) WebContent can work with Scope (Global/Site/PAGE) but TAGs and Categories only with Site/Global scope. So ""page scope"" is unusable! 2) We made WebContent structures (advertisement, ...). We have to permit all users publish any web content -‐ portal dont allow permit only one structure. So, structures are useful olny for editors....
3) AssetPublisher is very powerful portlet. Its too complex and it cant do lot of things... Lets make more similar portlets for more use cases. Our typical requirement is: ""Asset publisher will aggregate all contents from all portal sites. When I click on title I will be redirected on page with this article"". 4) I have 2 Wikis, 2 pages (for every wiki). I have WebContent with related assets (wiki1_page1, wiki2_page1) -‐ all wiki pages are shown in wiki1 (ignoring allowed wiki in configuration) There are lot of work done, I know. But work on details ;) Needs more quality in features, More stability required. "I would prefer Liferay making its Core lighter ... There are too many portlets that are not being used by us, but still all these portlets remain unused. If the Core is light, then the number of DB tables will be less and more over all the Core Portlets if provided as separate portlets just like the Knowledge Base portlet ... It would be better. So that We could choose on what we want to use, rather than dumping everything and not using them. I do not know the ramifications of making the core lighter, but Liferay needs to think about it." More OOTB portlets with integration with various frameworks and technologies like spring,solar, scheduler,jasper reports,SAP,SSO etc. "Stability was VERY poor with 6.1 EE SP1 -‐-‐ Henry N., Matt, and the rest of the VERY talented Support Team heroically saved the day and a potentially HUGE (reference) customer in HigherEd. Please focus on QA going-‐forward.