Bryan was part of my welcome committee when I started working for Liferay in 2010, and that's where we start the conversation.

• Bryan is one of Liferay's founders, and serves as CEO, out of the US office close to Los Angeles.
• Bryan's secret project that he announced at Devcon was finally released in May
• How do you turn a 4 person company into a 1000 person company, keeping sanity, personality and culture?
• How publishing OpenSource software fits into the strategy
• Liferay's announcement of an Enterprise Edition in 2008, and the promise made then, to keep the Open Source release alive and kicking
• How recommendations, focus, and attention to environments developed from application servers & databases and
• Bryan actively encourages contributions - editing took a bit longer, so the call for submissions for /dev/24 is already over: If the agenda still has some holes - check if you can still offer your knowledge. The submission form is still there.
• For a while now, Liferay offers more than just one product. Bryan talks about the heritage and reasons to start with DXP Cloud, Commerce and Analytics Cloud - and which problems they solve.
• I force Bryan to pick a 7.3 feature to describe, in preparation for /dev/24 - we'll see who explains it in detail during the livestream - and if he got it right
• We can't go without mentioning the Covid times (briefly)
• Bryan turns the table and asks about my experience (in which I can't go without plugging /dev/24 one more time)

Here are some of the topics that we talked about:

• David is part of Liferay's Developer Relations team
• Liferay's Developer Relations, and the people involved with the community
• /dev/24 is a community effort, streaming technical content on Liferay following the sun or the moon (your preference)
• Who's presenting? (Hint: Submissions are open - Employees as well as Community Members, Customers, Partners must submit)
• Topics: All open, but we're actively looking for 7.3 related content.
• Early submissions are picked early, late submissions have less spots to fill: The earlier you submit, the higher your chances for participations are.
• The time is set: /dev/24 will be on Sep 24 (midnight to midnight) for the US-Pacific timezone (UTC-7). Or, in easier to calculate times for anybody not in that timezone: Starting 24 September, 7:00 UTC, running until 25 September, 7:00 UTC (9:00 CEST)
• If you want to help without submitting a presentation (e.g. co-host at some time during the 24h, moderate the chat, provide additional questions, provide fun content, comment the submissions): Send mail to dev24 at liferay.com
• My (Olaf's) favorite content in conferences and webinars: Trivial Knowledge (and what that means).
• /dev/24 unrelated bonus content: What David is currently working on (assuming we'll cover that in a later episode)

Here are some of the topics that we talked about:

• Yasu is working on Damascus, an extension of ServiceBuilder that helps you set up a new project extremely quickly. And it's documented.

• Its purpose: Quick generation of master data applications, that you can edit further to enrich as a proper application

• Starting from a json file, you'll generate persistence and UI for multiple Liferay Portal versions

• A similar (but discontinued) project was mentioned on Radio Liferay in episodes 30 and 32: XmlPortletFactory.

• What to do to make Damascus an officially maintained project

• REST additions in Damascus

• Updates of the tool to 7.3, and of custom code generated with Damascus (should be easy)

• Freemarker to Java ratio - what it's like to write code that generates code.

• Best Practices and where they're worked around in the generator

• The heritage of the name Damascus, and how it relates to Liferay's "blade" tool

• Bonus Tool: DummyFactory

Or, in more detail, here are some talking points

• Systems that Bryce worked on - e.g. Loop (a timeline based Intranet solution used within Liferay), Analytics Cloud UI.
• Reasons to go headless, not utilizing Liferay's pages
• What's still being used from the platform (only touching)
• How maintainable is such an approach? Does it upgrade well?
• quo vadis react@Liferay?
• Clay, a web implementation of the Lexicon Experience Language https://github.com/liferay/clay, https://clayui.com
• Highlighting dropzones, a long story that finally came to an end
• Where does the frontend team hang out?
• Versions of Liferay and React - running together?
• React and Liferay's SPA framework

Or, in more detail, here are some talking points

• the versions in use and how Liferay DXP is used to build the different liferay.com sites.
• How use of the features changed over time - e.g. today, marketing authors are writing their own content, utilizing Content Pages
• How similar pages are maintained - using events as examples
• Integration of external tools into the site - e.g. for analytics, marketing, business development, and who's working with that data
• What goes back into the product? Feedback? Tools? Integrations?
• Maintainable Plugins (my presentation in german language) (via LDSF-On-Demand 2020 https://www.liferay.com/de/web/l/events-ldsf-dach-recap) and the Maintainable Plugins Challenge (english) https://liferay.dev/blogs/-/blogs/maintainable-plugins-challenge
• To what extent does Liferay DXP get extended for use on liferay.com vs using stock features?
• The infrastructure required to run liferay.com
• geographically distributed clusters vs recent developments in accellerating the speed of light ;)
• Ryan's Devcon presentation "Migrating liferay.com to 7.2 and DXP Cloud" https://youtu.be/FrJRhIFzc0M
• And , of course, "eat your own dogfood" vs "drink your own champagne" as illustrated in this image, CC by-sa 2.0, by anne beaumont
  

This is a quite non-technical episode, just two people remembering the "good old times": Don't expect to learn anything new about the product(s) - instead you'll hear about how we got from "there" to "here" in the past 10 years.

And about these topics:

• Zsolt's and my story: How did it all begin (at Liferay)?
• The founding of the hungarian office and its development in the past 10 years
• What Liferay does for customers in Covid-19 times
• Hamburger-Parties in Hungary and Steaks in Germany (this post's illustration)
• he various teams in Budapest
• Public Speaking
  • (which gives me an opportunity to shamelessly plug a public speech about a business trip with Liferay)
• Presentation Zen.
• David Nebinger's Horror Stories episode
• Life after Death by Powerpoint.

We couldn't go without some references to Covid19, but they're easy to ignore if you've heard already enough about that these days. We'll not attempt to solve the problems, promised.

We've talked about

• David's experience of bringing in Hibernate into Liferay projects versus utilizing ServiceBuilder
• Upgrading strategies, when you have a lot of customizations, and especially when you combine upgrades with further changes.
• Making up a proper, custom, framework for developing their applications
• The three rules of dealing with Liferay Support (also helping a lot for improving Forum- and Slack-questions as well)
• Rather a success-, not a horror story: A pointer to Episode 48 about predicting an exact release date, announced months earlier, for 6.2 GA3.

Here are some of the topics that we talked about:

• How long he's around (and how he got his first fix of Liferay)
• His motivation to stay around, to help people
• How he started with masteringliferay.com and what you find on the site
• How does Mastering Liferay relate to Liferay University?
• Passion versus Business
• Potential for contributions, "Share an idea"
• Target Audience (currently Developer-centric, but conceptionally not limited to this audience)
• Shameless plug for ControlPanel Documentation (because I can ;) ) - by now you can find the first links to masteringliferay right in that plugin
• Andrew's presentation at Devcon, together with his business partner Julian "The journey of a Liferay Developer - Empowering the community"
• Thanking Andrew by making him work more - he was part of Opening Devcon, playing an authentic Canadian.

• David's history with Liferay, reaching back to version 4.x
• Should I use an ext-plugin and what problem does it seem to solve? (TL;DR: No)
• 10:35 Should I make changes to the database? (TL;DR: No)
  • But... I need to add a column to the built-in tables...
  • Liferay's Expando API (Custom Fields)
  • What changes to the database might do to your future upgrades
  • The alternative to change data directly
• Fake Entities (a ServiceBuilder feature that was of good use in earlier versions but is now well superceded by just standard OSGi Declarative Services)
• Things Liferay won't say. Full article, well worth a read
  • What Appserver should I use?
  • How should I build my portlets?
  • What database should I use?
• Why doesn't Liferay tell me how to size my cluster?
• Devcon 2019:
  • David's upcoming presentation on "Programmatically loading your site with content"
  • His interest in Headless features of Liferay
  • His recommendation to come to the Unconference
• How to come up with the topics for David's blog articles, and what's in his queue
• Why should I use ServiceBuilder?
• More reasons to come to Devcon ;)

Here are some of the topics that we talked about:

• The history of Liferay as a product: How and why Brian started Liferay, and the first offer to buy the product.
• Caris' role from history to the present
• Early expansion and how Caris' pessimism balances Brian's optimism
• How Open Source opens doors that you didn't know where there (Shoutout to Bala)
• The reason for a lack of an exit strategy among the owners - why Liferay stays privately held without venture capital
• 10% of Liferay's profits go to Liferay Foundation - as smart investments in the world
• How does a company that strives to stay private get into the acquisition business, acquiring two companies?

We're talking about these (and more) topics

• We open with the attention to detail that's required for working on performance tuning and some short conversation about this topic.
• Sadly, there's not often a single silver bullet, but many areas of dust.
• Sometimes the fastest code is not the most optimal
• Continuing with Preston's work on Permissions:
• ResourceBlock is deprecated, and there's an easy migration path
  • an example upgrade path for bookmarks
• The usecase for Resources, ResourcePermission, and ResourceBlocks (as they're not at all visible on the UI)
• Preston's way through Liferay from Support to working on the topics that he's now working on
• The new API for Permissions - and the documentation is also done already (as of me writing this article, not yet published, but available on github - should be a matter of days or hours)
  • And an example: The implementation of this API in Journal
  • more documentation on registering and checking permissions
• Should you implement your own permission system? (and how the answer to this question might change in 7.1)
• Upgrades are being performance tuned. I smell a future episode coming up. Paging the team that is working on this area
• The remarkable memory savings that refactoring the UserBag introduced
• What happend during login
• Passwords are PBKDF2WithHmacSHA1/160/128000 hashed, a deliberately expensive password hashing algorithm.
• LPS-75747 and an update to my hardball question: Document Library's default.xml is still in core, can't be updated through a module, just through an ext.

I actually talked to them quite a while ago, and the episode has been sitting on my disk since then.The numbers that you hear may no longer be accurate, but the overall information definitely is. Sorry for keeping it a secret for so long (there's an even longer kept secret... up next...)

We're talking about these (and more) topics

• Different levels of Tests:
  • Unittests
  • Integration Tests
  • Functional Tests
• How SPA influenced frontend testing
• Selenium, Selenium IDE, Web Driver, Capybara, Docker, and Jenkins
• How pull requests are tested before they reach their addressee
• The scale of Liferay's testing infrastructure
• KC's (at the time) still unnamed project. Watch out for him at the North American Symposium for updates to this. Oh, and: By now his project actually has a name: Testray
• Maintenance of large test sets - UI locators etc.
• SevenCogs and its resurrection
• How to scale testing infrastructure for potentially a lot more servers and environments
• The Test Pyramid
• A wild idea: Livestream of test runs
• Liferay's Testing Whitepaper and a Testing Webinar
• 50 shades of red and its part 2

As before, we're speaking about various internal and external topics and I've also been teasing him a bit.

We're talking about these (and more) topics

• Microservices vs Monoliths
  • Buzzword or breeze of fresh air?
  • DHH The Majestic Monolith
  • Approach this technology option like any other
  • If you can't build a monolith, you are probably getting an even bigger mess if you approach microservices
  • Milen's presentation: Microservices and Modularity or the difference between treatment and cure (or on youtube)
• Shortly before the release many modules were moved around and renamed. We talk about the reasons and what this meant for the translations
• What's the meaning of "Feature-Complete"?
• A lot of Feedback starts to come in during the Beta Cycle
• Nitpicking on the Beta Criteria: JBoss and Upgrade Routines
• Lookahead on the next episode on Performance Tuning
• Releaseplans (of course, I could have retrofitted an exact release date...)
• What's it like to be hired into Liferay Engineering?
  • https://liferay.com/careers
  • office envy
  • shared spaces, decoration, own desks, separate working environments, inspiration, agora
• Is it forbidden to write Javadoc?

In this episode we're talking about these (and more) topics

• glimpse of history - remembering episode 21 with Jim
• Javadoc coverage went up from then on
• Javadoc metrics tool by Cody
• Javadoc contribution process: Send to liferay user repo, tag Cody @codyhoag
• Javadoc guidelines on dev.liferay.com (two flavors - basic and advanced guidelines)
• Submitting Unit Tests together with Javadoc
• The new home for documentation, dev.liferay.com
• "Edit on github" available for documentation. Use it - it's easy.
  • This edits Markdown files that get imported to Liferay's KnowledgeBase portlet.
    Jim's dev.life session (on youtube)
• Documentation: Javadoc, Taglibraries and other duties of the team.
  (mention Mike Williams on taglib pullrequests)
• docs.liferay.com and its content
  blade repository (in the meantime moved from Ray's to Liferay's repository)
• BREAKING_CHANGES.markdown
• Migration Tutorials (WAR->7.0->modules) on dev.liferay.com
• "blade migrate" is (at least temporarily) out??? (summoning Greg)
• the current Javadoc Contest and a cheesy mentioning of 2015's internal javadoc contest) (#2 Igor Beslic, #1 Moi)
  • (and some hints on how to dominate a javadoc contest)

Jorge gives an update on various internal as well as external topics. I'm also teasing him a bit, and hope that this episode will be as insightful for you as it was for me.

We're talking about these (and more) topics

• the engineering team passed the 150 people mark, distributed world wide.
• Communication in a team that's distributed through the world, tools
• Some nasty german guy recently took Jorge's #3 contributor place on the public forums
• Participation & Contribution: Check https://dev.liferay.com/participate.
• What happens to pullrequests to the Liferay repository? Should you rather direct to the component lead?
• Coding Standards, Design Patterns and how many you want to use in a single project
• Pullrequests and who's working on them.
• The experience of upgrading the architecture to OSGi in Liferay 7
• Jorge's Architecture Blog Article(s)
• News about Developer Network: Many new project documented there
• We're closing (for today) with a short fun quiz about new frontend tools introduced with Liferay 7, in which Jorge earns his street credibility.
• stay tuned for the continuation of this episode, most likely in episode 58.

If you know the background of this story already, you'll understand that I think full shownotes for this episode are not really appropriate. However, here are a few references if you want to follow up on some of the details:

• Community Tummler
• git manpage generator
• Community Security Team
• Marketplace
• Events App (iOS, Android)
• Community Expedition
• Vanilla JS
• Climate of Antarctica
• James' video farewell note

Stay tuned for further updates on what changes in community relations

Here are some of the topics that we talked about:

• JSR 362 page with all the latest and current information (spec, prototype implementation and javadoc)
• The expert group
• JSR 286 portlets will run unchanged on JSR 362 (runtime and compiletime compatibility)
• My repeat favourite statement about frameworks in the web world.
• JSR 362 and its impact on UI, there's a Client-Side standard (on ECMA script) for the first time in the portlet spec
• The big question: When will it be done? (Some time 2016)
• Early Draft Review Spec available, ~80-90% of content is expected to be there (That's the statement from Devcon, in October 2015)
• Reference Implementation (to prove that the spec can be implemented) and TCK still missing (again, October 2015)
• Reference Implementation and TCK will be implemented under the Apache Pluto project, help required
• New Features include Bean-Portlet-Approach (portlet methods specified through Annotations in any Managed Bean), portlet.xml file no longer required if Annotations used
• specifies a JS API despite being a JSR, which covers traditionally only Java
• Dependency to JavaEE: Minimum is JavaEE 7, e.g. Servlet 3.1 etc.
• Portlet Spec is not part of the JavaEE, but extends some of its elements.
• CDI
• JSR 378: Portlet 3.0 bridge for JSF (where Neil is the spec lead), being built in parallel with JSR-362
• Multiplatform Support, Websocket, Devices
• The E-Mail Archive of the specification process is public - contribution and comments are very welcome

As we recorded this on site at Devcon, you'll hear more background noise than usual - Auphonic did their best to clean the recording, and they did a great job.

Here are some of the topics that we talked about:

• UI frameworks get out of style soon. Can I still use AngularJS?
• Do I have to throw everything away that I have invested already?
• The YUI story and what its discontinuation means for AlloyUI
• Will AUI be reimplemented on jQuery? Is jQuery part of Liferay 7? What about different versions of jQuery?
• metal.js
• Lexicon, UI-Language, User Interface Guidelines
• Artifacts and Implementation of Lexicon
• Bootstrap, Bootstrap components, Atlas, the bootstrap versions in Liferay 6.2 and the components of it that are available.
• What happens when Bootstrap 4 comes out?
• Single Page Application, SPA, SennaJS: Go without full page reloads, largely by default.
• New Theming Tools - You can also use new tools in Liferay 6.2 (AYOR though). No more _diffs folder, pure frontend packages, themelets.
• What kind of themelets do we wish to have?
• We probably have forgotten something. Ask your questions in the comment section of this episode to be covered in future episodes.

As we recorded this on site at Devcon, you'll hear more background noise than usual - Auphonic did their best to clean the recording, and they did a great job.

Here are some of the topics that we talked about:

Portlets:

• If you're not interacting with Liferay, e.g. a pure JSR-286 portlet: No changes required
• JSF: Last kinks are worked out - test the more complex the JSF implementation is
• If you're using Liferay API: You'll have to resolve API changes - e.g. recompile and check if the API is still valid. Check these breaking changes - well documented, huh? And even better: The document is machine-readable and there will be migration tools (future episode planned)
  • If the service is still in Liferay's core: No change needs to be made.
  • If the service is now in a module: Check if the package was updated. Fix if necessary and if the migration tool didn't do it for you.
• Circumstances under which Liferay automatically "translates" WAR file into OSGi bundles - and the caveats
• Extensions to Liferay MVC portlet: Check for the nature of those changes
• The use of CDI - especially when the appserver's implementation/resources are utilized - still requires some work.
• Everybody who's doing really advanced stuff on sophisticated frameworks is welcome to try it out now and let us know now if there are any problems that remain
• How little of OSGi can I get away with?

Hooks

• Many of the hooks - especially on services and models will continue to work, but won't have more power than in 6.2. They're prime candidates to be converted to an OSGi module as this will enable them to tap into a lot more extension points in Liferay 7.
• Struts Action Hooks probably need changes - while they still work, most of the underlying actions have been reimplemented without Struts \o/, so possible overloads in Struts actions won't be taken into account for the new implementation.
  • (most likely: You need to convert to an MVC Command, injected as an OSGi module. There are samples available)
• Liferay 7 has a lot more extension points than prior versions. The documentation is being made available on dev.liferay.com - obviously this is still work in progress, but is scheduled to be there until release.
• How can IDE and other tools help identifying which extension points are in use? And how to make lots of friends within the Liferay Community
• Overriding Language Keys is quite simple - choose "global" or "per portlet" - those are the two available scopes that a translation can live in.
  • For migration you might have to decide which scope your changes should go into.
  • Encoding still is done in UTF-8
• JSP-Hooks: The elephant in the room: Seems to be very popular, but always has aimed at the implementation rather than to an API.
  • As drastic UI changes happened in Liferay, these implementation need to be implemented on the new infrastructure, leveraging new techniquest (e.g. Lexicon). Also, most of the functionality has been moved into modules - JSP-Hooks only affected the core jsps...
  • New options: JSPs can be deployed as proper OSGi bundles.
  • There's still danger because technically the implementation is unchanged compared to earlier versions
  • New fragment modules enable you to override JSPs in any portlet - not only core ones.
    But you shouldn't limit yourself to JSP-overrides: There are more ways to change Liferay's UI, e.g.
    • replace the render-phase of a portlet through a portlet filter.
    • A new "dynamic include" API to inject extension points at very specific places - e.g. at those UIs commonly targetted by overrides. (let us know which are missing)
      Application Adapters

Ext

• Ext Plugins work just like before (in core). But most likely, the implementation has changed anyway, so that you need to make sure your code is still valid for the current version - but that's what you expected when you started writing that ext anyways, right?
• Of course you'll have to check if your changes still are contained in Liferay core. If they're extracted to a module, ext won't be yours any more (for these changes)
  Ideally, ext will be the easiest plugin, as it probably will be a lot smaller than before.

We haven't covered all possible questions and are planning a "Listener Questions" episode. Please ask your questions in the comments to the blog article for this episode to get them answered in the next episode with Ray.

As we recorded this on site at Devcon, you'll hear more background noise than usual - As usual, Auphonic did their best to clean the recording, and they did a great job.

Here are some of the topics that we talked about:

• OSGi in Liferay 6.2 vs Liferay 7.0
• Modularization of Liferay 7.0
• Surprisingly (not!), modularization is not yet fully done, but it came a lot further than expected initially
• How much do you have to re-learn to build plugins for Liferay 7
• James: Community Roadmap Talk from Devcon (note: Ray also had several presentations at Devcon, you'll find his recordings there as well)
• Now everybody should be able to work the same way: Internally in Liferay's core as well as externally, in the plugins.
• Ant vs Maven vs others? What's the story with Liferay's supported Build environments? More energy will go into build tools other than the SDK
• Of course we cover a release date :) I'm getting a very rough one from Ray :)

As we recorded this on site at Devcon, you'll hear more background noise than usual - As usual, Auphonic did their best to clean the recording, and they did a great job.

For the visuals, please see the screenshots in this article as well as the plugin's homepage.

Here are some of the topics that we talked about:

• The Elevator Pitch: What's Nabucco Script Center?
• Scripting in Liferay: The native script console, its use and its shortcomings (solved in NSC)
• a short demo of Script Center. It makes sense to check the screenshots alongside, or even install the plugin:
  • various scripts (for example: Reset Terms of Use Acceptance) and instruct content editors to execute this script whenever they change the actual Terms of Use Article)
    
  • Automatically run scripts (again, same example, this time executed automatically on every update of the article) - comparable to a model listener plugin for Liferay's Service Builder
    
  • Scheduled Script execution. And basic sanity checks: When deactivating user accounts, you might want to have a few exceptions to your rules, e.g. in order to not lock out administrators that can help you gaining back control, but are not logging in every day.
    
  • Prodyna has scripts available on the app's homepage - e.g. What happened during the last 24 hours? How many users logged in yesterday? Basic data on usage on the start page ("heartbeat"). Warn authors in time before review dates of their content. Assign permissions based on categorization of content.
  • Fine grained permissions can be granted per script, e.g. just because you're able to upload/edit a script you might not be able to execute it - and vice versa.
• Feadback required - is this useful and what else is needed to make it more useful?
• How to develop without and with Script Center - where can it help you in your development process. Here are the slides that we talk about:
  
  
  
• Best Practices when implementing features in scripts: It's easy to accidentally make mistakes - there should be some basic safeguards.
• Script Center offers a third option to two customization approaches mentioned my earlier blog article

Here are some of the topics that we talked about:

• The glorious glamorous days one has on the security team (consisting mostly of email, tickets, pullrequests)
  • Different ways to make Liferay more secure
  • Gathering feedback from community and customers
  • Monitoring Liferay Forums and full disclosure mailing lists (also about the various libraries that are used in Liferay)
  • Scan source code for problems
• Liferay cooperates with external security researchers for penetration testing
• Customers perform external audits as well.
• An example of an actual audit report: 49 very alarming false positives vs. 1 real cornercase
• The security issue fixing process
• The first security episode with Sam Kong
• Link to community security update page. CE updates always only against the latest GA version
• Some low hanging fruits in secure Liferay administration (on the fly)
  • Disable "create new accounts" if you don't want random users to create new accounts (e.g. in an intranet)
  • JSONWS access
  • Disable Control Panel, add "My Account" to user's personal pages instead
  • The securing Liferay series and "additional Resources" here
• What will happen with Liferay 7?
• OAuth, and the related Radio Liferay episode 44 with Stian
• SQRL (disclaimer: I misled Tom by mispronouncing this library - he's aware, but there's no implementation - yet - for Liferay)

We're talking about general release practice and the plan that was put together last October, how Liferay CE will be delivered and how we're preparing to meet the promise. There's a 6 month release plan for new CE releases - and there will continue to be only one updated version of CE, e.g. once 7.0 is out, there won't be any more updates to 6.2 CE. If you need long term stability and support you should shoot for an Enterprise Edition subscription. This ensures your support for 5 years from release.

We also talk about the next release dates, how to get issues scheduled for that release (hint: Get votes on the issue, talk about it). Also, you get new ideas and features into the next release by rolling the drum for your idea - file an issue and do some marketing for it. This way it will float to the top and get recognized.

James has a quite thorough blog article about the content of 6.2 GA3 which contains quite a lot of fixed issues and - as is typical for maintenance releases - no new features.

To keep up to date on what to expect for Liferay 7.0, keep an eye on the milestones (coming out every 2 months) and Jorge's blog articles about them.

We're trying to bridge the gap and discuss visual topics, e.g. themes, in an audio format:

• the qualities of Liferay
• UX (user experience) and UX guidelines
• Building themes
• How to start new theme projects
• Emil's github repository
• The problem with people like me doing frontend design
• SASS, LESS
• New themes coming to marketplace
• Disabling Bootstrap and the future plans with it
• Best practices on editing/creating themes, how to update servers and test
• Sublime, Webstorm, Brackets
• Developing a Toolchain, ROI
• Upgrading themes to new versions of Liferay (see also Episode 38)
• and probably more topics that I forgot to add to these shownotes.

We talked about

• What do you need to do to become Barista Champion?
• Can you describe upfront what your coffee will taste like when you prepare it?
• Importing coffee, roasting, drying, grinding and preparing
• Latte Art (learn it by just listening to this episode):
  • Foam the milk to be a homogenous liquid - stop adding air at 30°C, then roll around the foam to get microbubbles. The really hard stuff is to determine when to drop the milk under the coffee's crema and start drawing images with the foam on top.
  • Find Latte Art tutorials on Youtube (or find out what it actually is and what pictures people actually do)
• Shoutout to Wolfram Sorg, from Prodyna Sales, who is teaming up with Thomas
• Did you know you can be a coffee consultant? Thomas is. He's consulting on coffee farms, cafés and barista training.

We talked about

• The history of Ray:  He is an "old" mascot, has been around on the very old website
• Bryan started to get involved with Ray for a T-Shirt contest in 2010 and continued to draw him
• How Ray's intergalactic adventures were started (Shoutouts to Paul Hinz and Martin Yan)
• At Devcon Bryan  created a lot of variations on Ray "on demand". You can find several of them on the flickr stream from that event.
• Luckily, Bryan keeps Ray around, for example on community T-Shirts, even though the cartoon series is currently on hyades.
• And other things that the design team works on (Website, Events, improve overall visual appearance)

Here's Ray listening to Radio Liferay:

He did a great job of explaining the background and solution in audio. Here's what we talked about:

• Social Apps Proxy enables you to integrate content from other social networks into your portal.
• It's working through OAuth, basically taking over all of the dirty work of authentication, leaving the actual integration works for the implementor
• Stian's sample app on github (Link): Getting twitter mentions with 10 lines of code
• What problem does OAuth solve? Comparing OAuth with a Valet Key.
• Linking Liferay's identity to twitter's (in this sample)
• How the social apps proxy works: An application just uses it as HTTP proxy, does not care about identity and is happy to get the identity automagically taken care of
• Social Apps Proxy on Marketplace
• Supported Versions of Liferay 6.1 to 6.2 and OAuth 1.0a to 2 to be extended
• Microservices
• All Code is to be open sourced soon, contributors are welcome.

This is a short conversation as we didn't have a lot of time in between different appointments, but we've committed to making this a series of episodes on similar topics - and more in depth.

We talked about

• Application Lifecycle and Performance monitoring, New Relic  (used as a sample here), Compuware , AppDynamics. Or check the Gartner Quadrant
• If you can't host in the cloud, you can use the same strategies that Brett is talking about with on-premise solutions
• How do you know your application is slow?
• ELK-Stack (Elasticsearch, Logstash and Kibana)
• adding page load times to Apache Logs
• It matters where you measure from: Internal network, external network.
• Default configuration of Liferay - memory, garbage collection and other JVM settings
• You can have too much memory in your JVM
• Liferay's Whitepapers have starting points, you shouldn't use them as your final settings.
• ...and you'll actually need to measure for yourself in order to find your number...
• CDN setup and its results on high volume site
• Be proactive. You'll find bottlenecks before your users do.

We talked and joked about

• The structure of the Hungarian Support teams
• How bugs unexpected features are handled
• How to make sure that these don't show up again in the next version
• Fixpacks, Hotfixes, Servicepacks
• Other worldwide support teams

You might or might not know that Liferay's business is built on Enterprise Edition - and specifically on the support services that we offer here. This is what keeps the new versions coming. This episode is meant to give you some information about the procedures that happen when you (as a customer) file an issue for Liferay support. Compared to the actual internal workflow, this is simplified, but gives sufficient insight. If you want more details, please comment.

We talked about

• The problem that staging solves
  • "Workflow" for a whole site
• What's new in staging in Liferay 6.2?
• Staging in custom portlets
  • sample LAR portlet on github
  • Service Builder builds a lot of code required for staging
  • my Ridiculously Simple Portlets and Máté's Staging appearance on dev.life, extending those simple portlets
• How LAR import/export relates to staging
• Local vs. Remote Staging
• The new staging UI: Visible Progress, Background processing
• Performance rule of thumbs: "it depends" - I don't give the numbers here. Listen to the conversation to find out what it depends on.
• Staging through multiple stages
• The future of staging (in 7.0, available in the current milestone)
• The effect of customer feedback on the future of staging. Hopefully you gave your feedback at Devcon, where Máté was attending to get more feedback. This episode should have been out by then; sorry, postprocessing took a while longer than anticipated.

Follow @RadioLiferay, @matethurzo and @olafk on twitter

Again, shoutout and big thank you to Auphonic for postproduction help. This time I really made them work. If you want to compare the result to the actual recording - let me know and you'll get a snippet of the raw file which they de-noised!

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory. If you like this, make sure to write a review for the podcast directory of your choice - or leave your feedback on www.liferay.com/radio.

We talked about

• The upcoming events, how to tell them apart and the target audience. In short: LPSF (Liferay Portal Solutions Forum) is targetted to business users, DevCon is targetted to Developers and technically interested people. Symposium has tracks for both groups.
• You'll find almost all of the upcoming events on Liferay's Events overview - filter for "Conferences". As of publication of this episode, the first brazil symposium is not yet on that list.
• Check if the event you want to go to still has an open Call For Paper. Some are still open the day that this episode is released.
• Final reminder: Unconference seats will be limited. Register early to make sure you get your seat.
• This year, we're going to provide access to the (anonymous) data that backs the events, and hope that you'll create an awesome mashup with this data. Refer to James' blog article "DIY: Liferay Events Hacks: Part 1" for details of the API and let us know if you need more help
• iBeacons and what to do with them at events. (Watch out for a part 2 of James' blog article)
• ...and other topics - but listen yourself... if you listen close enough, you might even hear a secret

(The episode is prefixed with a PSA for all Radio Liferay Listeners: The CfP for Devcon2014 is still open until 22. Aug 2014) and if you intend to come to the unconference on 4. Nov., make sure to register early: We have limited space and already predict that we'll sell out the unconference - there are enough seats available for the regular DevCon)

Juan is a project manager on this very project, working in Spain. Ivica is Senior Software Engineer, implementing LCS with the engineering team (Marko Čikoš and Igor Bešlić) in Croatia. I delayed publishing this episode to wait for the end of the private beta (you couldn't join anyway) until the public beta is just about to start.

We talked about

• How LCS got started and what problems it solves (this is work in progress, designed for constantly added functionality)
• (among the current information shown are things like: Performance metrics on JVM- and portal/portlet level, Fixpack information (EE only) and -installation.
• The public beta is just around the corner (estimated in September). Test results from the private beta are in and lots of feature requests implemented (I can certify on that - some of them are mine)
• Intended new features, to be added over time
• New target audiences (currently it's largely system administrators, but content managers, e.g. for content targetting statistics, could be a possible future extension)
• For the nerds, we talked about how LCS is implemented under the hood, and the mechanics of targetting Liferay 6.1 and 6.2 at the same time.
• ...and others - but listen yourself...

Follow @RadioLiferay @juanferrub @icardic or @olafk (me) on twitter

We talked about

• Alberto has helped Iliyan working on the upgrade tool that we spoke about in episode 37
• The tool helps upgrading AlloyUI JS, CSS and some JSP code from Liferay 6.1 to 6.2
• Alberto presented this tool at the spanish symposium
• The tool is available for Windows, Mac and Linux, Installation instructions are available in the tool / github repository
• It's been used on 100+ portlet plugins already, providing good service in the upgrade process. Sorry, this is the only plugin type that it's good for.

We talked about

• where Iliyan's non-spanish accent comes from
• Iliyan is a long time user and contributor to YUI (since YUI 2.x) and came on board when Liferay was looking for an Ajax Developer after having seen many of the AlloyUI components.
• Liferay's currently open positions (changed since we recorded, but still a lot & interesting positions)
• How to approach AlloyUI, what tools to use
  • start with learning YUI, then continue with AlloyUI components. (Hint, not mentioned in the podcast: Liferay is working on an AlloyUI training course. Watch out!)
  • Orion, Bracket, IntelliJ, Sublime Text.
  • check out Life Reload
• as 6.2 uses Bootstrap for themes, we talk about the migration of existing themes and the way we work with css. (the episode has been recorded just before the actual release of 6.2)
• The Liferay AUI upgrade tool will cover a lot of the upgrade work you need to do to migrate your existing 6.1 plugins to 6.2 - covering various API upgrades etc. (see https://github.com/liferay/liferay-aui-upgrade-tool#what-it-does - doesn't it sound like paradise?)
• AlloyUI now has a testing infrastructure - automatically running a on a huge number of browsers to make sure nobody introduces regressions with a change to AlloyUI
• Roadmap for AlloyUI past 2.0
• Just like all Open Source projects, AlloyUI lives and improves on feedback - please help and get involved, get your impression heard. (and the same goes to podcasts. Please let me know which episodes you like, what to change, topic requests. You have blog comments to this episode on liferay.com, itunes comments and ratings and other platforms - whereever you get this podcast from)
• The AlloyUI team hangs out on Forums, IRC, stackoverflow, twitter, github, jira - use whatever suits you best.
• An alternative to Bootstrap that has been considered
• Though symposium season is over now, you, dear listener, might consider to come to one of the 2014 Symposiums, Portal Solution Forums, Roadshows or DevCon.
• AlloyUI is available through CDN

• He's the one to keep the pootle instance at translate.liferay.com populated and synchronize changes between pootle and the git repository. This started with some script by Milan Jaros
• Liferay has some generated translations (with the help of babelfish or bing translate) as well as some copied (english) texts in all the localizations. This needs to be handled, so that pootle does know which (existing) translation still requires manual work.
• the process of synchronization between pootle and git requires some patches and bugfixes in pootle - an open source, python based product.
• More complication added by maintaining different branches of Liferay, different plugins (not only portal) and different sources of translations (git, pootle, Jenkins, other contributions).
• it's hard to keep 100% completion for a translation as new features are constantly added
• Due to the scripting work, translation can be done either in git or in pootle.
• Liferay provides translations to roughly 42 (sic!) languages.
• Shoutout to Daniel Reuther, who has worked hard on the german translation, standing in for me because my vacation came just at the right time - thanks Daniel.
• History of translations and automatic translations (starting with Yahoo's babelfish, continuing with Bing translator) and if they make sense... (hint: no, with an exception mentioned at the end)
• \o/ : The pootle import scripts ignore automatic translations. They only appear on the UI when they continue to not be translated.
• We're evaluating to use other tools than pootle - however, the existing bidirectional scripting makes it hard to choose something different (even updating pootle can be hard)
• Become part of the Translation Team and communicate on the Translation Forum

We talked about

• Ray, a very new command line project that has been shown and discussed at DevCon, aiming to bring the ease of Application Development of Rails, Play Framework, Grails etc. to Liferay.
• Ray is obviously a very new prototype, designed to rather gather feedback than to demonstrate a ready-for-use environment.
• Ray will be Development-platform-agnostic, e.g. not tied to our eclipse-based developer offering. It's (currently) maven based, built on top of Spring Roo
• Play with Ray and give feedback: Fork or Clone Greg's github version, the release will take at least half a year, but you now can influence what it will be able to do for you in future.
• Ray is aiming to be cross-version compatible, due to this aim, the release plan will be completely independent on Liferay Portal's.
• Liferay IDE 2.0 finally supports Maven, check the latest Milestone if the final version is not yet out.
• Greg needs feedback (link forums) on typical Liferay-Maven-project structures to continue work on the maven integration
• IDE 2.0 is scheduled to be out two weeks after Liferay Portal's GA for 6.2, but the Milestones are supposed to be stable. New features for 2.0: Maven, Freemarker-Debugger (for Themes in M1, for ADT in M2), new Project Wizard with support for more than the SDK
• Underlying Topic in this episode: Feedback is key - if you give feedback early, you can bring your favorite things in.
• IDE Roadmap: Tools that work across different environments - e.g. commandline tools like Ray, IntelliJ Idea, Netbeans or others.
• Greg's move to china that we discussed back in Episode 15 and how to say "cheese" in mandarin.

With the main topics being OSGi and Modularity, we talked about:

• Middleware and Appservers that support OSGi
• 6.2 is the first release to officially be supporting OSGi
• Goal is to shrink Liferay's footprint
• The current state of OSGi in Liferay - is there anything left to do? (guess what - the answer is "yes")
• Extending Liferay with plugins without depending on the Appserver. Liferay can be extended through plugins in an Appserver - in future this should be a lot easier just extending with OSGi bundles. The current mechanism is extremely dependent on the Appserver we're running on.
• Deploying an OSGi plugin to Liferay completely decouples Liferay from the mechanisms of the Appserver,
• What will happen to the existing plugin types - namely "ext"?
• OSGi will make a difference for plugins that extend plugins - this works today, but is not straightforward.
• This way of modularization will help lowering the learning curve for developing plugins - making extensions easier to write with the classic Java knowledge background.
• Feature Bleed and Interdependencies between different unrelated parts of Liferay - as they exist today and will hopefully change in future

Here are our topics:

• the history of name changes, starting with "JSCORM"
• The meaning and origin of the name
• The release schedule (they met the schedule that we discussed during the recording, released end-of-August)
• Features that have been added throughout the history of the project.
• The version released in August now has a Curriculum Portlet that combines different courses into a Learning Path.
• SCORM, the prevalent standard for exchanging E-Learning information. This standard is typically used as distribution format for commercial courses and Valamis supports SCORM 1.2.
• We talked about Liferay Certification being available "soon" - that was true at the time when we recorded the podcast, it's actually available now
• License, Availability and Price (hint: LGPL, and there's professional support available)
• There's a steady team working full-time on Valamis.
• Design aspects: The Arcusys Team really cares about design aspects, both in the software, as well as in their presentations.
• Geography for beginners, we talk about finish climate, ice-fishing, and "where is Finland"
• If you want to try Valamis without installing it yourself, just try it on their homepage: A demo environment is available
• Picking up my favourite code demo, sevencogs, from my last-year's symposium presentation "Well Hidden Features"
• The experience of publishing on Marketplace, PACL and PACL differences between application servers
• Future Features and Release Plans (e.g. Tin Can API)
• How to evolve from a Learning Management System to a Learning Portal
• The principle of Aiming High
• There's no shortage of standards to implement
• The team is working with a school in Afghanistan to provide what might be the first e-learning system in an afghan school, also connecting them to finnish schools and students.
• Upcoming Symposiums, Portal Solutions Forum, DevCon
• Since we recorded, Valamis won the Liferay Marketplace App Contest

Here are our topics:

• Jack started in 2005 with Liferay 3.6, got first trained on Liferay 4.2 in 2007
• He's working as a freelancer, specializing in Liferay, BPM and their integration
• xmlportletfactory. This project generates simple CRUD portlets that make use of servicebuilder and many other aspects of the Liferay infrastructure. With many contributions from its community (e.g. Juan) more and more of the infrastructure is used: ServiceBuilder, Asset Framework, Workflow, IPC, Entity Relationships, Export to Excel, Activities,
• xmlportletfactory is a one-time codegenerator: You generate once, then you can modify the resulting code.
• The code is generated from templates - as it's open source (GPL3), of course you can change it.
• Jack is also currently integrating BonitaBPM into Liferay. This replaces the Bonita Portal, you can interact with the Workflow engine from Liferay as well as from an  Android smartphone. This integration is expected to show up on the marketplace soon.
• As we speak about publication on the marketplace, let me insert a short&shameless pointer to my own fabulous podcasting app. It was not out when we recorded the podcast, but now it is.
• bonitalife.org
• Bonita being recognized by Gartner as the only open-source product that meets Gartner's definition of a BPMS.
• Jack has another site, portlet.es - providing some sample portlets: A Sudoku generator (maybe it appears on marketplace soon), a Lexicon filter (e.g. for forums, blocking keywords), GroupNotification (find marketplace link) - (sends emails to all usergroups or site members)

Here are our topics:

• Liferay Faces started with portletfaces.org, a cooperative work by Triton and Mimacom. Neil started at Triton, then came to Liferay and Triton and Mimacom donated the code.
• Liferay Faces (LF) consists of LF Bridge, LF Alloy, LF Portal, LF Util.
• You can find a lot of Demos for integration with different components, LF Alloy, Icefaces, Primefaces, RichFaces, InterPortletCommunication. (find Demos)
• The history and problems with earlier JSF versions (esp. Version 1) in Portlets: JSR-329 standardized a standard portlet bridge, those were typically built independently of the portals.
• With JSF 2.0 the integration into portlets got easier and the problems vanished.
• We have 20 Legends now - thanks for all the forum participation
• How does a portlet bridge work and why do values end up in the session even though we've declared them to be request-scoped? E.g. what phases from the JSF lifecycle are bridged to what phases in Portlets?
• With JSF 2.2 one can finally go stateless, previous versions have been strictly stateful.
• AlloyUI 2.0 and its integration into Liferay Faces Alloy, a JSF implementation that utilizes AlloyUI and YUI components.
• Liferay Faces 4.1/4.2 is targetting Java EE 7 (e.g. JSF 2.2) and 4.2 is planned to be released with Liferay 6.2.
• Liferay Faces is distributed through Maven Central, thus it's ready for use and the release is technically independent of Liferay.
• Liferay IDE already integrates JSF in the "New Portlet" Wizard, and it will become a lot better in the next versions
• Neil's JSR involvement (JSR 314, JSF 2.0, JSR 344, JSR 2.2, JSR 362 Portlet 3.0)
• Due to the involvement in the new portlet standard: What's the Portlet 3.0 committee working on?
• CDI Context & Dependency Injection, Conversation Scope, liferay-cdi-portlet-bridge.jar, Implementations: JBoss Weld, Open WebBeans, Resin Candi
• Shoutout to the various cooperators, e.g. from RedHat: Ken Finnegan, Stan Silvert, Pete Muir & Jozef Hartinger, from Oracle: Ed Burns, Mike Freedman, Roger Kitain, Manfred Riem, many Liferay Engineers
• Neil will be at DevCon in Berlin and at other upcoming symposium(s?)

Some more keywords from the conversation:

• The upcoming 6.1 GA3 release (sorry, this time I missed asking for the definitive release date)
• JSF & Liferay Faces team, where Neil Griffin is leading the current efforts of transparently integrating the JSF lifecycle with the portlet lifecycle.
• Juan actually sparked an upcoming episode (next, number 31) with Neil about JSF and Liferay Faces.
• He updates me on the version numbers (JSF 2.1) and different JSF flavours (RichFaces, PrimeFaces, IceFaces) and their history, coming from Mojarra (Sun/Oracle) and MyFaces (Apache), and possibility to use them simultaneously.
• Juan's contributions that he provided before he joined Liferay (and what he got the Community Contributor Award for): Audio/Video Preview, now found in the 6.1 Document Library)
• xmlportletfactory, a project started by Jack A. Rider. This tool enables you to build CRUD portlets that are well integrated into Liferay's service-builder infrastructure. Juan provided the Asset-Integration for it.
• The future: Juan is preparing a talk about JSF for the spanish symposium (meet him there) and plans to develop some JSF components, e.g. for dynamic data lists, pdf export
• and as you can see: This time I didn't loose the recording again - that would have been too annoying...

Some more keywords from the conversation:

• Training experiences
• Mobile Device Detection, or Device Recognition as it's labelled on Marketplace
• The UI for DR is not too obvious - which was the original reason for us to have this conversation. Milen describes how to make sense of the UI, how to use it and what features are hidden behind the UI facade
• WURFL and the dimensions of information that it can detect from devices
• The history of his contribution (for 6.0)
• The UI changes in 6.2 have been significantly and will indicate that you'll need to install a plugin to use DR properly (we were not sure and didn't check yet if it's in M6 yet, if/once you see it please give feedback)
• As the UI offers only a selection of the device information: Why we limited the information and what else is available through WURFL
• How to determine if a certain device is a telephone or a tablet (hint: whatever WURFL says is assumed to be correct)
• How to make use of the WURFL capabilities that are not exposed in the UI. Milen promised to post a blog article on it and - in fact - he has already done so.
• Future plans to help with responsive desins
• How DR can be used to serve specific content to devices (e.g. if all you want is to download an App)
• Other mobile strategies:
  • run your own apps (how is that Liferay dependent? Well, take a look at Liferay's Events app (for the upcoming Developer Conference, Liferay Portal Solution Forums or Symposiums) that uses the agenda content directly from the portal, e.g. Liferay's CMS
  • Sync
  • Make use of HTML5 local storage (see the IBA presentation at the 2012 european symposium
• Milen recently got praised for a beautiful presentation he did at a conference, titled "What is a portal?". His motivation and the story behind. (sshhh: He's available for presentations at other events as well)
• Also, we're both showing age remembering Container Managed Persistence from EJB 2 and how Spring and similar libraries have turned the world upside down since then.

Follow Milen, RadioLiferay or me on twitter

Thank you again to Auphonic for improving the sound quality dramatically. AFAIK this time there were no unrecoverable dropouts ;)

Some more keywords from the conversation:

• Change to symposiums: This year we split some of the symposiums into business (Liferay Portal Solutions Forum) and technical (Developer Conference) events - especially in Europe.
• LPSF 24. September in Frankfurt
• DevCon (8.) 9.+10. October in Berlin
• LPSF 7. November in UK
• Symposium October US/SF
• Symposium 16.+17. October Spain
• Call for Paper open or soon to be opened for SF, Spain, Berlin: Help us by submitting long before the deadline
• Unconference style, agenda finding
• Last Milestone (M6) has been published just before we recorded
• BugSquad is on again, finding those pesky bugs in the current milestone releases - thanks a lot to the bugsquad team for the help
• Work done by the Community Verifier Team
• Edward Gonzalez' role to pick up fixes that have been submitted without targetting a specific engineer (and shoutouts to Juan Fernandez, Cynthia Wilburn, Ed Chung)
• Ideation
• The "exit strategy" for ideas: Get it into the portal or create an App for Marketplace.
• Project Learn, an e-learning platform, recently graduated to be a marketplace app (lookup name)
• We're using my fabulous podcasting plugin as a means to describe how to publish an app on the marketplace (it's currently on its way)
• Marketplace now has roughly 70 apps published by independent developers.
• Marketplace App Contest: Participate and win one of 25 iPad minis and a trip to one of the symposiums or Liferay events of your choice - anywhere in the world.
• various birthday coincidences
• Community Leadership Team
• Pointer back to the motivation thread, linked from Radio Liferay episode 1
• Community Blogging
• IRC: #liferay on freenode

Follow James, RadioLiferay or me on twitter

Some keywords from the conversation:

• Changes of the collaboration structure over the year
• Liferay is hiring independent of location, building an internationally distributed team.
• Overcoming the difficulties of this distributed work
• Current team size and structure
• How to bring in code contributions as a community member
• Liferay's coding standard being mandatory to match for contributions, strict Peer Reviews
• Contribution Experience: My quick-win with a small patch that was severely rewritten during peer review (LPS-33455)
• Milestones and when to start the beta cycle for version 6.2
• The accuracy of Liferay's past release date announcements and how to improve - both on Liferay's side as well as externally: What help do we need?
• Hold your breath: I got a target release date from Jorge. Yes, there's a disclaimer, but the intent is out now :)
• The recent feature freeze
• New features in 6.2: AlloyUI 2.0 (more info on that on episode 25), Twitter Bootstrap (we'll need feedback for theme-migration, please help, adopt early and report back), New Dockbar, Controlpanel overhaul, Site Administration (no longer in controlpanel), lots of usability improvements, sharing content across sites, recycle bin
• The swiss army knife of CMS, AssetPublisher, gets a lot of new features (obsoleting some of the well hidden features that I talked about in episode 23): filtering through the search index, scripting for output.
• The big plus on the technical side: OSGI (I sense an interesting topic for an upcoming episode)
• BugSquad
• DevCon (episode with more info already scheduled)
• Jorge's architecture series of blog posts

We talk about

• Turku, Finland
• When to use Vaadin vs. the other available technologies
• How Vaadin differs from GWT (hint: GWT is used for front-end UI rendering, but generally processes server-side
• A performance comparison and benchmarks that have been executed with Vaadin - and how it will change further with Server-Push in Vaadin 7.1
• The Devoxx-Talk "World Wide Wait" included Vaadin in its comparison as the fastest server-side solution.
• Vaadin recently released version 7 which is a huge step forward, unfortunately not 100% backward compatible with the version that ships with Liferay (6.x) but 6.x continues to be maintained. The backward compatibility for version 7 depends on the technology used by the applications, for regular applications it should be ok though.
• Arcusys, a Liferay Partner in Finland, picked up the development for the Vaadin controlpanel
• Vaadin is licensed under the Apache 2.0 license, despite the main product being available for free (like Liferay), Vaadin has built quite a good business around the product. The company is sized at ~60 employees, offering services, consulting, training and some extra components that we briefly talk about.
• Eating your own dogfood vs. drinking your own champagne.
• Vaadin supports SASS and integrates easily with external javascript
• Widgets
• The Vaadin repository is hosted on github - go ahead, fork and collaborate

Follow Ville, RadioLiferay or me on twitter

Thanks a lot to Auphonic for improving the sound quality drastically - this is the first episode I had processed by them and it's been a really good experience - especially given the recording cirumstances.

We start with their history and

• Zeno's project jquery boilerplate. He's also one of the founders of the Brazil JS foundation
• Rosetta Stone, no longer hidden but very prominent on the website, comparing jQuery, YUI, AlloyUI
• The traumatic transition time in 2010 between Liferay 5.2 and 6.0, when AlloyUI replaced jQuery
• How Zeno got assimilated into Liferay
• The new website for AlloyUI with Tutorials, Examples and Documentation (alloyui.com)
• What's new in AlloyUI 2.0, when will it come into Liferay?
• Feedback from the community (portuguese video on youtube)
• Can I run different versions of YUI on the same site/page (as I can with jQuery within YUI with the help of YQuery)?
• who else is using AlloyUI or contributing to it?
• Zeno will be speaking at Jax 2013
• Honorable mention of the library that YUI is unofficially built on top of.
• TaglibGenerator: A tool to generate taglibs and integrate them with Javascript/AlloyUI
• Integration of taglibs into Liferay IDE/Developer Studio (Link to Greg's Episode)
• AlloyUI on twitter and stackoverflow

If you want to see more from Eduardo and Zeno, they also opened the recent 24 hour webcast "Day of Liferay" and the recording is available (click their names to go directly to the video), or follow @eduardolundgren and @zenorocha

Zsolt starts by laying out why Jira was fine for a single project (and it continues to be in use at issues.liferay.com), but not so much for the way we're supporting the enterprise customers.

After introducing the problem space, he's going through implementation timeline, migration, features and requirements, as well as later evolution of the system (naturally, LESA is still being actively developed and extended). Also, there are lots of metrics and how they are helping to improve service or efficiency growing the team.

You'll learn how Liferay's support teams were organized internally over the time and where we're heading to. At Liferay, we're not eating our own dogfood, we're rather drinking our own champagne. Where we don't do this now, we're planning to do so very soon. LESA is part of the activity to move a lot of functionality from 3rd party software into Liferay (or to integrate that software into the portal).

This is a solo episode with yours truly. I had a lot of fun preparing and presenting this session, "Well Hidden Features", at the european symposium 2012 in Wiesbaden/Germany, as well as in Milano. They both built upon earlier presentations at the nordic and french symposiums and have been used as inspirations for other presentations at the north american as well as the spanish symposium. So, if you were at any of these symposiums, there's a good chance that you've heard some of the content.

Also, if you're working with Liferay for some time, there's another good chance for you to know some of the tipps&tricks already. As I mention at the beginning of the recording: This all is trivial knowledge - but in order to be trivial knowledge, it first has to be known - and I hope there's something in it even for the more experienced among you.

For those who want to read along the slides for this presentation: They can be found on the download page for the european symposium

Some of the topics you'll find in this episode

• Memory Management and configuration
• What to do when operating a bundle
• Neat features for builtin portlets and hacks I use on liferay.com/radio
• My favourite generator for UTF-8 test data
• How to use jQuery within AUI, and how to learn the differences between the two (and YUI)
• Extending Plugins
• two simple checkboxes in eclipse that made me unlearn the most simple and basic things
• A usecase that you did not know about the scripting console (disclaimer: found out that this works only once)
• An easy way to learn how to use the Liferay API to create users, pages, content etc.
• Getting debug information from your running production portal
• Activating some monitoring information
• My 2 cents about http and https and the largely unknown protocol relative URLs
• Places where you didn't expect to find great documentation
• portal-ext.properties caveats and properties that you might not want to keep in their default values

This is another episode recorded at the previous Liferay Retreat. I sat together with Samuel Kong, GM of the chinese office and member of Liferay's security team.

As I've been carrying this recording around for quite some while, note that there have been some changes during the last year. First and foremost, we have a new community security team, which was not around at the time of the recording. I'm planning to talk to someone from that team soon (consider yourself warned if you're on that team)

Some of the topics you'll find in this episode

• How to file a security issue - thankfully he is consistent with what Cynthia and Michael have reported: go to issues.liferay.com, file your issue under the component "security", optionally with private visibility. If you've already done so, please try if your issue is reproducible in the latest available version - your issue might already have been reported and fixed.
• OWASP (The Open Webapplication security project) site is a good resource for learning about security in Webapplications in general, independent of Liferay.
• The three tools that Liferay has built-in, helping you to prevent security issues:
  • Redirects: Some Properties, configuring the list of domain names and IPs, that Liferay is allowed to redirect to
  • CSRF: Auth-Token
  • XSS: The various escape-methods in com.liferay.portal.kernel.util.HtmlUtil - There are so many because the correct escaping depends on the context for which one escapes some HTML-Text. Also, the AlloyUI Taglibs help a lot when you're displaying user-content in forms. And also: The "escapedModel" that you can get from ServiceBuilder.
  • Bonus: SqlInjection and its prevention through ServiceBuilder.
• When to escape HTML text in order to be most flexible.
• Sidenote: A call to extract and read the full portal.properties: A long, boring and interesting read. Oh, and the dtds for xml files

This is another episode recorded at the previous Liferay Retreat. I sat together with Jim Hinkey, Knowledge Engineer and part of Liferay's knowledgement and documentation team, since March 2011. He took over ownership of the developer's guide and is the guy to bring back javadoc to Liferay (more about this and how/why Liferay once lost its javadoc at the end of this episode)

We talked about

• How Jim found Liferay
• Life in Raleigh/NC
• One of his biggest chokes, the (re)creation of javadocs for Liferay
• The process that Javadoc now has to go through in order to get into the product
• and other topics

As I managed to get short hold of Brian Chan, I had the opportunity to ask two more quick questions - one about the day when Liferay lost all of its javadoc and one sneaky question about consistency with the example of ThemeDisplay. If you - like me - always wondered where this name came from, you'll have to listen to this episode.

Last but not least, pardon the pun, but this was too good to be true - I just had to include this:

(The source for this cartoon is geekandpoke, licensed under Creative commons by-sa 3.0. Thank you so much, Oliver Widder)

We talked about

• Bruno started 2007 with a Liferay Training in L.A.
• founded the office as General Manager in Recife, Brazil in 2009
• his experience with dressing up in the L.A. office
• starting at Liferay (with the office rented from a church) meant that Bruno could tell his mother that he went to church every day
• how he became Bruno Admin, seemingly taking the role from Julio, and what this means for attending a gym
• Instead of handing out autographs, he got his own "flair", a pin that was handed out at the annual retreat for everybody who knew the password. Check out how much of the password he knows himself ;-)
• The setup and responsibilities of the brazilian office and what he does in the time he's not "generally managing"
• His responsibilities in Liferay Sync and the mobile story for the iOS and Android version
• (some brags about my personal pet-peeve, Linux support for Sync ;-) )
• What my previous company had in common with Liferay (hint: Name duplication - or triplication)

We talked about

• how Juan started with the task to integrate Liferay with Pentaho, becoming a community member and later joining the spanish office
• How Consulting findings are fed back into the product and what Juan did for the internationalization and localization of content in 6.1, default data for structures, related content, etc. (lots of new features for version 6.1 here)
• Juan's demo at the european symposium and what he did when he created a basic application within the WCM system
• If you have already implemented new custom Assets you don't need to do anything to get "related assets" functionality
• the spanish community, contributing features, plugins or other add ons, taking the examples of Jack Rider of xmlportletfactory fame, Aritz Galdos of Lifedroid, Juan Gonzalez (who contributed preview features for the document library)
• the french community, e.g. Leo Pratlong, who did some translations. (Juan also speaks french and helps out in the french community)
• ...and other topic

(I think I finally learnt how to pronounce the "z" in spanish names - challenge me when you meet me next time)

We talked about

• how Mike first met Brian Chan
• You might remember that Brian suggested Mike that he had to use EJB for his wedding website - here's the story behind that, and how it got him involved with Brian and Liferay in the end.
• The parts of Liferay's code that Mike was involved in - starting with "everyone did everything"
• Liferay Sync, OpenSocial and WSRP being the current areas of work
• With Mike I finally found the project lead, responsible for lobbying for a Linux client for Sync and was able to rant on. He delivered a nice and understandable reasoning. Even though this means I'll have to wait, I guess I won't rant any more ;-)
• The mentioned "not yet" released Sync product has actually been released this week
• Mike is the initial implementor of the OpenSocial implementation in 2009 or 2010, but now handed it over to Dennis
• I know Mike best for his involvement with WSRP, "Web Services for Remote Portlets" - we talk about what it is and what it takes to make this really compatible with other portals. There are quite some interpretations of this standard (and not only this) that need to be validated in the respective environments.
• The aspects that eat into performance when you have two portals involved in answering your request - and what the implementors on both side can do to mitigate the drawbacks.
• The nature of WSRP calls and how it all works on a very high level
• The roadmap for OpenSocial and what we're planning to build on top of that for the next release (6.2)

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to the RSS feed, on itunes or with your podcatcher of choice - you'll find all the options on www.liferay.com/radio. And if you want to get notified when the next episode is out, follow @RadioLiferay

This is another recording I did with some new recording gear, but, being new gear, I messed up the levels so I had to denoise it a bit, unfortunately a bit of noise still remains. I'm doing my best to get rid of that in future recordings.

And please remember to rate this podcast in your podcast directory of choice and provide feedback here on the episodes as well. Thank you.

So I sat together with Jeffrey Handa, Senior Training Consultant and Project Manager at Liferay and we spoke about Liferay's training offers, the existing courses, the new offerings, what changes are planned for the next time etc..

We talked about

• Jeff just had his 3rd birthray when we spoke, so he's in his fourth year now (I stole the term "birthray" from someone in the spanish office - can't remember who it was though, help me to get credit)
• Jeff is one of the people with the "classic" way of joining Liferay - sorry, there's no interesting story here.
• Jeff is involved in training: Preparing the material and actually teaching in trainings.
• We're speaking about the training courses Liferay offers and Jeff gives some description of what the courses are about, also on the cooperation with liferay's knowledge management team. This includes the classic courses (PortalAdmin, PortalDeveloper, SystemAdmin) as well as the new courses (ThemeDevelopment and AdvancedPortalDeveloper)
• some impressions of my (Olaf's) experience teaching portal admin training to customers that were using Liferay for some years already: They still got very good value out of it
• What knowledge you should have before taking one of the new courses: "building a theme" and "advanced portal development"
• Part of AdvancedPortalDevelopment is Writing Applications in webcontent. I have talked to Ray about this - he also has blogged about it.
• Jeff is mentioning the ContentAdministrator course and the vision for what PortalAdmin can be about. Now I wonder if we will rename it to PortalNinja sooner or later.
• Plans for what trainings will evolve to
• What PortalAdminExpress is, when it is applicable
• Trainings are available in several local languages as well.
• Plans for certification and exams
• Training is available on all supported EE versions - and public trainings will typically be held on the latest available EE version (but typically be released a bit after the EE release - if you expect the training to be on a specific version it pays to ask upfront. But we also speak about differences between the different versions, so that training is relevant for users of all versions of Liferay.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to the RSS feed, on itunes or with your podcatcher of choice - you'll find all the options on www.liferay.com/radio. And if you want to get notified when the next episode is out, follow @RadioLiferay

We talked about

• what your kids think of your work when you're always looking at the Sesame Street while pretending to work.
• how Sesame frequently releases new content to the site - having fresh content and topics every so often is quite a task for the editorial team.
• Big parts of what have been custom for Sesame geting into the product now (in 6.1), namely staging, versioning and branching (improved from the version 6.0 implementation).
• Sesame being in the process of upgrading a high-traffic, high profile site from 5.1 to 6.1
• the server infrastructure as well as some of the software background (e.g. Alfresco, GSA)
• how is the site built - e.g. how much is stock, how much is custom? How is it all built?
• We close with a discussion about how people do find Liferay and learn about the product and the company.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher or subscribe on itunes.

Something else...

Radio Liferay now has its own landing page at www.liferay.com/radio. So if you want to recommend this podcast to somebody, this is where you should point them to.

Also, I'd like to get more of your feedback: Do you feel this is valuable? Whereever you get the podcast - if there's an opportunity to rate it please do so - e.g. itunes currently does not have enough votes to display an average . Also, please provide feedback to the episodes so that I can balance the next topics and adjust them a bit more to your interest. You can do that on my blog or on twitter.

I do have a long list of community contributors that I'll contact in the next weeks to prepare some more recordings and mix them with the Liferay Employees as this whole program is not purely about the company people. Feel free to suggest more interviewees and topics though.

Thank you!

In this session I talked with Greg Amerson, the author of Liferay's development tooling.

This is one of the first recordings on new gear, unfortunately levelling was not ideal, so it had to significantly be amplified and denoised - bringing some drawbacks in audio quality, mainly noise despite the denoising, but you'll be able to stand it - promised. Also, I hoped to get this out before the holiday season, unfortunately this didn't work out that well for various reasons - Sorry for that, you'll get your late christmas wishes in this episode.

Among other topics we talked about:

• Greg got his exposure to Eclipse Tooling from being one of the first people to work on the MyEclipse product
• The distincion between Liferay IDE (for Liferay CE) and Liferay Developer Studio (for Liferay EE)
• The impressive size of the team to have worked on Liferay Tooling until now and from now on.
• Greg's current location: Working from the China Office and how he got from Texas to China and the future plans.
• The story how Greg found Liferay (you have to hear this - you might even learn your first words in Mandarin)
• The difference the IDE support made in Developer Training - and what ideas he and the team have in addition of the current features (please provide feedback on what you expect from developer tooling)
• Some of the ideas: Maven, personal templates, Marketplace, remote deployment and debugging
• A vision for the stability of Liferay's plugin environment

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

Find Greg as @greg_amerson, me as @olafk or my Alter Ego for just this program as @RadioLiferay on twitter.

Something else...

Radio Liferay now has its own landing page at www.liferay.com/radio. So if you want to recommend this podcast to somebody, this is where you should point them to.

Also, I'd like to get more of your feedback: Do you feel this is valuable? Whereever you get the podcast - if there's an opportunity to rate it please do so - e.g. itunes currently does not have enough votes to display an average . Also, please provide feedback to the episodes so that I can balance the next topics and adjust them a bit more to your interest. You can do that on my blog or on twitter.

I do have a long list of community contributors that I'll contact in the next weeks to prepare some more recordings and mix them with the Liferay Employees as this whole program is not purely about the company people. Feel free to suggest more interviewees and topics though.

Thank you!

In this session I talked with Bradley Wood. Brad is Frontend developer - involved in all things theme, CSS, Velocity. And he's maintaining a nice tumblelog with all kinds of Frontend tipps & tricks for Liferay (which brought him on my radar for the podcast).

Among other topics we talked about:

• Getting theme custom settings (e.g. color picker) through the API - now standardized and extended due to popular demand
• How Sass add power to CSS with variables (integrated in Liferay 6.1)
• Compass, a library of Sass functions with vendor specific CSS3
• Brad's style for creating a new theme, starting from photoshop, through CSS and Velocity
• Parts of adopting a Look&Feel might involve hooks to change the core Liferay JSPs
• Using structures and templates to improve the experience updating the content.
• The alternative to routine when it comes to editing velocity...
• Brad's tumblelog of Liferay Tipps&Tricks
• the marketplace themes for particular industries
• Think outside the box: How a theme can help you create an online shop by integrating google checkout
• Liferay Foundation and how Brad if involved with its projects (World Impact, which is where Brad's first experience with Liferay came from - here are the Camps and Schools sites)
• Upgrading themes from 5.2 to 6.0: How to handle the core css differences and vm
• Recommendation: Have a common way to comment and format your code
• How to use categories to simulate runtime-configurable theme settings in version 5.2 and 6.0 (as they are now standard in 6.1)

Find Brad as @randombrad, me as @olafk or my Alter Ego for just this program as @RadioLiferay on twitter.

Something else...

Also, just in time for the holiday and gift season we finished something new - sadly I've had to delay publishing this episode, so I only partly announced it upfront: Radio Liferay now has its own landing page at www.liferay.com/radio. So if you want to recommend this podcast to somebody, this is where you should point them.

Also, I'd like to get more of your feedback: Do you feel this is valuable? Whereever you get the podcast - if there's an opportunity to rate it please do so - e.g. itunes currently does not have enough votes to display an average . Also, please provide feedback to the episodes so that I can balance the next topics and adjust them a bit more to your interest. You can do that on my blog or on twitter.

I do have a long list of community contributors that I'll contact in the next weeks to prepare some more recordings and mix them with the Liferay Employees as this whole program is not purely about the company people. Feel free to suggest more interviewees and topics though.

Thank you!

Among other topics we talked about

• Frontends for Sync, (Sync was first mentioned in Episode 11 by Alex and Sergio)
• The (currently) missing OS support for Windows ME and Linux and which one will be supported first (most likely)
• Mobile Clients, Desktop Clients
• Sync uses JSON Webservices
• OpenSocial
• Various presentations on OpenSocial on ECS, WCS (by Dennis),  EuCS (by Juan)
• OpenSocial on Liferay LIVE in January 2011

Some of the topics we talked about:

• How they met and started to work despite different music and food taste
• How or if college grades (might) relate to real life
• While they used to live on the same floor some time, now they are still on the same planet...
• Crazy organic growth and the hardest year, Rooming arrangements and sacrifices during the startup phase
• The honorary Brian (the fourth founder, who could not join the recording), Mike Young, and why he should use EJBs for his marriage, what risk he took
• How Caris put up with Brian's activity after 10pm and got Liferay's invoices off of notepad
• The long term plans, "no exit" strategy and how a business can help to do good
• And at the end the microphone unexpectedly turned around, and I give away pieces of my history with Liferay

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

Obligatory Twitter Links: Brian Chan, Brian Kim, Bryan Cheung, me and RadioLiferay

My shownotes:

• Their background and what they worked on in Liferay
• How to pronounce names
• Naturally: The work both did on Document/Media Library and related portlets through the last year: The document library got a good rewrite, Ajax-based UI and a new backend to use Liferay as entry-point into other external repository systems.
• CMIS (short for Content Management Interoperability Something - see link)
• A lot of the document library backend war developed with JUnit and worked within a few days of work with the independently created UI when they were first brought together.
• Different Document types are now first class citizens, so that you have certain metadata as well as separate workflows for different types of content.
• Document Library and Image Gallery changed to Document and Media Library (for storage) and Media Gallery Display (for presentation) - the data and permissions will be automatically migrated
• Previews for many document types will be automatically generated.
• Listing alternative interfaces to the backend: Browser, WebDAV, Sharepoint protocol, Liferay Sync
• Sync will work offline and synchronize any change (bidirectionally) with Document & Media Library when it's online, available for Windows, Mac, Android, iOS. Sadly there's one OS missing...
• Iliyan is now europe's resident AlloyUI/JS expert
• Download Beta 4 (or whatever is current when you read/listen to this) and give feedback, report bugs before Alex 2.0 is released.

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

Obligatory Twitter Links: Alex, Sergio, me and RadioLiferay

]]> Alexander Chow, Senior Software Engineer at Liferay in UK; Sergio González, Liferay Core Engineer, located in Spain This is a conversation with Alexander Chow and Sergio González about their main topic of work for the last year: Liferay's Document Library, or as it's renamed for version 6.1, "Media Library" Olaf Kock no 0:31:23 liferay, Alexander Chow, Alex Chow, alexchow, Sergio González, sergiogonzalez, Document Library, Media Library, olafkock, olaf kock, radio liferay, RadioLiferay, Portal, Portalserver radioliferay@olafkock.de (Olaf Kock) (Olaf Kock) https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-10%3A-michael-han https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-10%3A-michael-han#_33_fm2 Fri, 18 Nov 2011 20:00:00 +0100 https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-10%3A-michael-han Liferay for your ears - Meeting Michael Han, Liferay's Vice President of Operations, at the european symposium, I used the opportunity to record an episode on some of his working areas, namely security and performance. He gives some good background on these issues.

Among other topics, we spoke about:

• His background, how he came to Liferay and what he's mainly working on
• Mike is with Liferay since 4 years - helped setting up the international offices and business.
• "Follow the sun" support: International offices required for support around the clock
• Performance gains from version to version, sampling with logging in.
• Mike's involvement in performance tuning, how the performance whitepaper is built and what you need to understand about your system in order to expect the correct results based on the performance whitepaper's numbers.
• The different ways that the "number of users" can be interpreted and how to find out the required number of servers.
• 3-4 man-years of effort go into performance-tuning enterprise edition
• How to read security reports: Why 50 deep-red issues might show up to not be as bad as they look initially
• Black-box and White-box testing for security issues
• Circumstances under which a possible SQL-injection is not a problem
• Security of Open Source software - with an example
• How to report security issues: File an issue in Jira, set the component to "security" and the visibility to "private", so that only you and Liferay staff can see this issue. Enterprise customers just file an issue in their account and flag it as security issue.
• How to set up a performing system, what parameters should you care for - along with some numbers we see on garbage collections etc. and why you can have too much memory.
• There used to be a Sun/Oracle blog about every single JVM option since version 1.3, as we found out preparing these notes, this is no longer available. But there are alternative links
• Other documentation for other vendor's JVMs
• How we determine which server architecture to build the performance testing environment on.

Part of my original intent was to speak about their contributions and learn what Liferay can do better with regards to accepting contributions. Turns out that this was a handpicked crowd of notorious contributors that praised more than they criticized - well, so be it, it's good to hear this.

Among other topics, we spoke about

• Naturally: The Symposium and what it's all about: Meeting people, the energy. All four of them work with/for Liferay Partner Companies. Stating also my personal recommendation: If you have any chance to make it to one of Liferay's symposium, make sure to go.
• Tomáš best known contribution is the initial Extlet (now ext-plugin). This made it possible to move from the initial monolithic and huge ext-environment (singular) to very lightweight plugins (plural) in 6.0
• Corné started with Liferay 3.x, is the Dutch translation leader.
• Milen contributed the mobile device detection using WURFL, which he also demoed during the symposium.
• Maarten is involved with themes, usability and accessibility. Also, he pushed "commenting as a guest", a new feature in 6.1
• All of them contribute to many of the active community programs, Bugsquad, 100 paper cuts, etc. that James introduced.
• Getting responses from core Liferay developers and personnell during the symposium and in the community.
• Get knowledgable by learning from helping others:
• Milen's and Tomasz's work on the Maven SDK

I hope that a lot of the enthusiasm that I've seen in this round as well as in any symposium I've been to can be transferred through the recording.

It was a great opportunity to get together with these guys, but sadly the episode is shorter than it could have been - we recorded this towards the end of the symposium, just before the community excellence awards were handed out - and as some of the participators were receiving them, I couldn't keep them busy for longer.

No children were harmed during the recording of this podcast - at least not by us: There were a few playing outside, running around and screaming - and the hotel room was not too soundproof, so this got onto the recording.

The introduction is done by Bryan Cheung, another member of Liferay's founding team and the Chief Executive Officer. As this is the full keynote, I really recommend to listen to it in full, and for that reason don't provide a bullet point list of the topics here. Just this: You'll learn a lot about the setup of the company, the vision, the reason why you want to work with Liferay - the product as well as the company. And why the company will stay with this vision for the foreseeable future. And where the name "Liferay" comes from. And so many more things - Brian is a fast speaker.

One of the next episodes will be a follow-up to this episode, as I used the opportunity to sit down with 3/4 of the founder's team, namely all the Brians (This poses a spelling problem: What's the plural of "Brian, Brian and Bryan"? I'll make it "The Brians")

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

You can find Brian, me and (new) the announcements for Radio Liferay on twitter and on many more places on the web.

We spoke about these topics - and probably more:

• User Interface
• Accessibility
• Localization (Translation Team, Forum, Process)
• pootle on http://translate.liferay.com
• Initial translation by babelfish
• Translation workflow and how to find the context for translations
• Visualize all translations and keys on a page (plugin)
• The European Symposium (the recording was made prior to the symposium, release is after the event)
• Accessibility Guidelines by W3C (WCAG 2.0), Screenreaders
• Accessibility through using AlloyUI taglibs and the effect of themes on Accessibility
• Guidelines for developent, How to make consistent UIs and how they are made in Liferay (shameless plug: referencing Aaron Delani and Nate Cavanaugh)
• Getting from Photoshop to a UI
• BugSquad
• Different Kinds of Contribution: Just mentioning an issue somewhere does help. If you can help fix the problem, it might help even more, but don't keep any feedback for yourself..)

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

You can find Julio, me and (new) the announcements for Radio Liferay on twitter and on more places on the web.

We spoke about these topics - and probably more:

•  Photoshop, Gimp, InDesign and other graphical editing tools
• Aaron's hiring procedures
• Hints for "How to design a Theme"
• ControlPanel "S" (and what the S stood for). In the mean time it's just the ordinary ControlPanel again, no fancy name, but lots of fancy functionality was added for version 6.1
• Hidden Gems in ControlPanel
• The new DocumentLibrary
• User Interface Guide
• Liferay's UI for Social Equity
• Presenting mobile content in Liferay and the Roadmap for 6.1, mobile themes, "mobile-enabled" portlets

You'll find this episode - and make sure that you don't miss any of the future episodes - by subscribing to  http://feeds.feedburner.com/RadioLiferay with your favourite podcatcher. You can also subscribe on itunes.: Just search for "Radio Liferay" or just "Liferay" in the podcast directory.

We spoke about these topics - and probably more:

• Cynthia was once mistaken as a Jira bot
• The Product Backlog maintained in Liferay's Jira
• Agile Plugin for Jira (formerly Greenhopper)
• Recommendations on how to file issues in Liferay's Issuetracker, so that they are taken care of.
• security issues and how to file them
• fixpacks and the new patchtool
• Marketplace
• Sevencogs Hook
• Social Office
• The Definitive Release Date (sic!) for the next version (no link, you'll have to listen ;-)
• The release philosophy
• A Releasecandidate planned for 14. Oct. 2011 (Sadly, due to intense work preparing the upcoming european symposium, I didn't manage to publish this before the 14. Oct. So after the fact, this has been relabelled a beta)

We spoke about these topics - and probably more:

• Internet coverage in Northern Ontario
• Forums, IRC, Blog
• The beauty of XML and XSLT (in 2004)
• Bits of Liferay's history since 2004, e.g. the Sourceforge Mailinglist
• Some Features Ray has been involved in: WCMS, Permissions, Document Repositories, Asset API, Service Builder, Staging, Search - basically most of what's somehow related to WCM.
• The enjoyment of sharing information. Not disseminating information is counterproductive. (At this place I'd like to place a completely unrelated shoutout to JT - you know what for ;-) )
• the benefits of keeping hands away from UI code.
• (Learning english in this episode consists of my "inadvertently" stumbling across my tongue)
• Feature talk: The new staging in 6.1, "site variations", how work on it was done.
• The use of the different templating languages: Velocity, Freemarker, XSLT
• WebContent and Templates can partly replace portlet & plugin development.  Documented on Ray's Blogpost Advanced Web Content Example with Ajax and Liferay Live presentation
• OSGi, in Ray's Blog and on github

We spoke about these topics - and probably more:

• Liferay's UI history
• Javascript, Drag&Drop positioning of portlets on page
• The introduction of jQuery in Liferay and the standardization on it in 5.1
• The reason behind the switch to YUI and AlloyUI (also here)
• Delivery of AlloyUI from Yahoo's servers
• Nate and Eduardo Lundgren working with the Yahoo Team
• The Liferay AlloyUI team (Eduardo, Nate, Bruno Basto, Ilyian Peychev, John Mak)
• Learning AlloyUI. Start with yuilibrary.com (then change Y to A)
• Namespacing and Sandboxing in AlloyUI
• JSP Taglibs for AlloyUI, TagBuilder
• YUI documentation builder
• Liferay IDE and Developer Studio, Greg Amerson
• Looking forward: AlloyUI will be the UI library of choice for 6.1 - no changes planned ;-)
• jsrosettastone - translating jquery to yui. And another version for jquery to AlloyUI on github
• Oh, and Olaf is learning english again: Capitalization
• AlloyUI is on github, help, participation and pull requests are welcome
• Erik Andersson (honorable mention)

We've had a few audio quality issues, so please bear with some dropouts or cracks in there, it's only episode 2 and I'm learning the best setup for skype for these purposes.

We spoke about these topics - and probably more:

• Bruno Admin, Rich Editor, Michelle Writer and John Regular User
• Liferay Administration Guide, Liferay Development Guide and Liferay documentation at large
• Liferay in Action, Rich's upcoming book
• documentation in markdown on github
• Liferay's Javadoc Master (Jim Hinkey)
• Storytelling (The Chocolate Monster)
• Olaf learns english and discovers the opposite of fiction: Non-fiction
• Teaching
• Liferay's Training program (new: Advanced Developer & Themes Training, incidently: held the day before WCS)

After a long time of "just intending" I finally went ahead and started recording a podcast about Liferay - the project, the product, the people and the company. Episode 0, a brief introduction with the intent and some generic information is available for manual download. It's only 4:12.

Episode 1 will be out within a day - I sat together with James Falkner, Liferay's community manager, who luckily agreed to be my guinea pig. Episode 2 is - contrary to what I say in episode 0 - already recorded and will need a bit of post-production. Stay tuned for this - I'm speaking with the Alter Ego of "Rich Editor".

You might have noticed that I said "manual download" - there's no feed yet. But as I had the content, and it's kind of timely because we talk about the symposiums, I wanted it out in public as soon as possible. So please bear with me while I create a feed that somehow contains what the typical feedreader - especially itunes - does expect. The whole setup, hosting etc. is temporary and will change soon.

So use this to practice manual download and listening to yours truly. Episode 1 will probably also predate the feed, but it should not be by far.