Bryan Cheung

A repeat guest - today I've talked to one member of my team, Bryan Cheung. 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 &amp; 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)            

A repeat guest - today I've talked to one member of my team, Bryan Cheung. Bryan was part of my welcome committee when I started working for Liferay in 2010, and that's where we start the conversation. <ul> <li> Bryan is one of Liferay's founders, and serves as CEO, out of the US office close to Los Angeles. </li><li> Bryan's secret project that he announced at Devcon was finally released in May </li><li> How do you turn a 4 person company into a 1000 person company, keeping sanity, personality and culture? </li><li> How publishing OpenSource software fits into the strategy </li><li> Liferay's announcement of an Enterprise Edition in 2008, and the promise made then, to keep the Open Source release alive and kicking </li><li> How recommendations, focus, and attention to environments developed from application servers &amp; databases and </li><li> 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. </li><li> 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. </li><li> 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 </li><li> We can't go without mentioning the Covid times (briefly) </li><li> Bryan turns the table and asks about my experience (in which I can't go without plugging /dev/24 one more time) </li></ul>

RL070 Bryan Cheung

RL069 David Gómez

David is part of Liferay's Developer Relations Team, and we took some time to talk about the upcoming /dev/24 livestream of developers and other users of Liferay DXP and Liferay Portal with a technical background. 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)	

David is part of Liferay's Developer Relations Team, and we took some time to talk about the upcoming /dev/24 livestream of developers and other users of Liferay DXP and Liferay Portal with a technical background. Here are some of the topics that we talked about: <ul> <li> 	David is part of Liferay's Developer Relations team </li><li> 	Liferay's Developer Relations, and the people involved with the community 	</li> <li> 	/dev/24 is a community effort, streaming technical content on Liferay following the sun or the moon (your preference) 	</li> <li> Who's presenting? (Hint: <a href="https://liferay.dev/blogs/-/blogs/-dev-24-call-for-presentations" rel="nofollow" target="_blank">Submissions are open</a> - Employees as well as Community Members, Customers, Partners must submit) 	</li> <li> 	Topics: All open, but we're actively looking for 7.3 related content. 	</li> <li> 	Early submissions are picked early, late submissions have less spots to fill: The earlier you submit, the higher your chances for participations are. 	</li> <li> 	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) 	</li> <li> 	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 <a href="http://liferay.com" rel="nofollow" target="_blank">liferay.com</a> </li> <li> 	My (Olaf's) favorite content in conferences and webinars: Trivial Knowledge (and what that means). 	</li> <li> 	/dev/24 unrelated bonus content: What David is currently working on (assuming we'll cover that in a later episode) 	</li></ul>

RL069 David Gómez - /dev/24

Yasuyuki Takeo

Yasuyuki, short Yasu, is Supportability Engineer at Liferay. He's working out of Japan for ~8 years now, and in that time has started an interesting side project that you might be interested in. Well - I was interested, so I asked him for some time and we talked about it: Damascus. 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 

Yasuyuki, short Yasu, is Supportability Engineer at Liferay. He's working out of Japan for ~8 years now, and in that time has started an interesting side project that you might be interested in. Well - I was interested, so I asked him for some time and we talked about it: Damascus. Here are some of the topics that we talked about: <ul> <li> Yasu is working on <a href="https://github.com/yasuflatland-lf/damascus" rel="nofollow" target="_blank">Damascus</a>, an extension of ServiceBuilder that helps you set up a new project extremely quickly. And it's <a href="https://github.com/yasuflatland-lf/damascus-doc" rel="nofollow" target="_blank">documented</a>. </li> <li> Its purpose: Quick generation of master data applications, that you can edit further to enrich as a proper application </li> <li> Starting from a json file, you'll generate persistence and UI for multiple Liferay Portal versions </li> <li> A similar (but discontinued) project was mentioned on Radio Liferay in <a href="http://radioliferay.com/episode/30" rel="nofollow" target="_blank">episodes 30</a> and <a href="http://radioliferay.com/episode/32" rel="nofollow" target="_blank">32</a>: XmlPortletFactory. </li> <li> What to do to make Damascus an officially maintained project </li> <li> REST additions in Damascus </li> <li> Updates of the tool to 7.3, and of custom code generated with Damascus (should be easy) </li> <li> Freemarker to Java ratio - what it's like to write code that generates code. </li> <li> Best Practices and where they're worked around in the generator </li> <li> The heritage of the name Damascus, and how it relates to Liferay's "blade" tool </li> <li> Bonus Tool: <a href="https://github.com/yasuflatland-lf/liferay-dummy-factory" rel="nofollow" target="_blank">DummyFactory</a> </li></ul>

RL068 Yasuyuki Takeo on Damascus

RL067 Bryce Osterhaus

For this episode of Radio Liferay, I've talked with Bryce Osterhaus, Frontend Developer at Liferay for ~ 6 years. With his experience, he's a perfect complement to me: While he feels at home in the browser, client side, I'm comfortable on the backend, away from all of the messy frontend stuff - prepare for some naïve questions coming his way.  We spoke about a design decision that has been made in some internal projects: His team has built a UI that does not utilize Liferay's page/site infrastructure. It's rather  an application that utilizes some of the infrastructure but not what's typically used to compose frontend applications on a portal.  Or, in the rage of the day, you could say: "Headless". ;) 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 

For this episode of Radio Liferay, I've talked with Bryce Osterhaus, Frontend Developer at Liferay for ~ 6 years. With his experience, he's a perfect complement to me: While he feels at home in the browser, client side, I'm comfortable on the backend, away from all of the messy frontend stuff - prepare for some naïve questions coming his way. We spoke about a design decision that has been made in some internal projects: His team has built a UI that does not utilize Liferay's page/site infrastructure. It's rather  an application that utilizes some of the infrastructure but not what's typically used to compose frontend applications on a portal. Or, in the rage of the day, you could say: "Headless". ;) Or, in more detail, here are some talking points <ul> <li>Systems that Bryce worked on - e.g. Loop (a timeline based Intranet solution used within Liferay), Analytics Cloud UI.</li> <li>Reasons to go headless, not utilizing Liferay's pages</li> <li>What's still being used from the platform (only touching)</li> <li>How maintainable is such an approach? Does it upgrade well?</li> <li>quo vadis react@Liferay?</li> <li>Clay, a web implementation of the Lexicon Experience Language <a href="https://github.com/liferay/clay" rel="nofollow" target="_blank">https://github.com/liferay/clay</a>, <a href="https://clayui.com" rel="nofollow" target="_blank">https://clayui.com</a></li> <li>Highlighting dropzones, a long story that <a href="https://liferay.dev/blogs/-/blogs/drag-drop-indication-on-liferay-ce-7-3-1-ga2" rel="nofollow" target="_blank">finally came to an end</a></li> <li>Where does the frontend team hang out?</li> <li>Versions of Liferay and React - running together?</li> <li>React and Liferay's SPA framework</li> </ul>

RL067 Bryce Osterhaus on Frontend Development

RL066 Ryan Schuhler

A while ago I sat down with Ryan Schuhler. He's Associate Program Manager at Liferay, which is a fancy name for Webteam Lead, and we talked about "dogfooding" Liferay DXP to build liferay.com - which features are used, how the site evolved and what is fed back into the product. 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  

A while ago I sat down with Ryan Schuhler. He's Associate Program Manager at Liferay, which is a fancy name for Webteam Lead, and we talked about "dogfooding" Liferay DXP to build <a href="https://liferay.com" rel="nofollow" target="_blank">liferay.com</a> - which features are used, how the site evolved and what is fed back into the product. Or, in more detail, here are some talking points <ul> <li>the versions in use and how Liferay DXP is used to build the different <a href="http://liferay.com" rel="nofollow" target="_blank">liferay.com</a> sites.</li> <li>How use of the features changed over time - e.g. today, marketing authors are writing their own content, utilizing Content Pages</li> <li>How similar pages are maintained - using events as examples</li> <li>Integration of external tools into the site - e.g. for analytics, marketing, business development, and who's working with that data</li> <li>What goes back into the product? Feedback? Tools? Integrations?</li> <li>Maintainable Plugins (my presentation in german language) (via LDSF-On-Demand 2020 <a href="https://www.liferay.com/de/web/l/events-ldsf-dach-recap" rel="nofollow" target="_blank">https://www.liferay.com/de/web/l/events-ldsf-dach-recap</a>) and the Maintainable Plugins Challenge (english) <a href="https://liferay.dev/blogs/-/blogs/maintainable-plugins-challenge" rel="nofollow" target="_blank">https://liferay.dev/blogs/-/blogs/maintainable-plugins-challenge</a></li> <li>To what extent does Liferay DXP get extended for use on <a href="http://liferay.com" rel="nofollow" target="_blank">liferay.com</a> vs using stock features?</li> <li>The infrastructure required to run <a href="http://liferay.com" rel="nofollow" target="_blank">liferay.com</a></li> <li>geographically distributed clusters vs recent developments in accellerating the speed of light ;)</li> <li>Ryan's Devcon presentation "Migrating <a href="http://liferay.com" rel="nofollow" target="_blank">liferay.com</a> to 7.2 and DXP Cloud" <a href="https://youtu.be/FrJRhIFzc0M" rel="nofollow" target="_blank">https://youtu.be/FrJRhIFzc0M</a></li> <li>And , of course, "eat your own dogfood" vs "drink your own champagne" as illustrated in <a href="https://www.flickr.com/photos/eannieb/3201083662" rel="nofollow" target="_blank">this image</a>, CC by-sa 2.0, by anne beaumont </li> </ul>

RL066 Ryan Schuhler on creating liferay.com

RL065 Zsolt

Zsolt Balogh

Oops - in times of fast news like this, I sat on the recording for a while. Unacceptable, but as almost nobody is commuting in April/May 2020, it's questionable if you'd have put it on during your commute anyway... Happy 10th Birthray to Zsolt and me and several others (listen to the episode if you want to know what that means) 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.

Oops - in times of fast news like this, I sat on the recording for a while. Unacceptable, but as almost nobody is commuting in April/May 2020, it's questionable if you'd have put it on during your commute anyway... Happy 10th Birthray to Zsolt and me and several others (listen to the episode if you want to know what that means) 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: <ul> <li>Zsolt's and my story: How did it all begin (at Liferay)?</li> <li>The founding of the hungarian office and its development in the past 10 years</li> <li>What Liferay <a href="https://liferay.dev/blogs/-/blogs/getting-through-covid-19-together-with-liferay" rel="nofollow" target="_blank">does for customers</a> in Covid-19 times</li> <li>Hamburger-Parties in Hungary and Steaks in Germany (this post's illustration)</li> <li>he various teams in Budapest</li> <li>Public Speaking 	<ul> <li>(which gives me an opportunity to shamelessly plug a <a href="https://youtu.be/MA857jtm7JU" rel="nofollow" target="_blank">public speech about a business trip with Liferay</a>)</li> </ul> </li> <li><a href="https://www.presentationzen.com/" rel="nofollow" target="_blank">Presentation Zen</a>.</li> <li>David Nebinger's <a href="http://radioliferay.com/episode/64" rel="nofollow" target="_blank">Horror Stories episode</a></li> <li><a href="https://youtu.be/lpvgfmEU2Ck" rel="nofollow" target="_blank">Life after Death by Powerpoint</a>.</li> </ul> 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.

RL065 Zsolt Balogh - Happy Birthray

David Nebinger

An episode that was recorded together with episode 62, but got a bit lost (well, I admit - it was just sitting on my disk). But here we are: David shares four of his favorite horror stories - those that tought him what he never wants to see again. Hopefully it's useful so that you learn from it before experiencing those stories yourself. We've talked about  David's experience of bringing in Hibernate into Liferay projects versus utilizing ServiceBuilderUpgrading 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 applicationsThe 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.

An episode that was recorded together with episode 62, but got a bit lost (well, I admit - it was just sitting on my disk). But here we are: David shares four of his favorite horror stories - those that tought him what he never wants to see again. Hopefully it's useful so that you learn from it before experiencing those stories yourself. We've talked about <ul> <li> David's experience of bringing in Hibernate into Liferay projects versus utilizing ServiceBuilder </li><li> Upgrading strategies, when you have a lot of customizations, and especially when you combine upgrades with further changes. </li><li> Making up a proper, custom, framework for developing their applications </li><li> The <a href="https://liferay.dev/blogs/-/blogs/working-with-liferay-support" rel="nofollow" target="_blank">three rules of dealing with Liferay Support</a> (also helping a lot for improving Forum- and Slack-questions as well) </li><li> Rather a success-, not a horror story: A pointer to <a href="http://radioliferay.com/episode/48" rel="nofollow" target="_blank">Episode 48</a> about predicting an exact release date, announced months earlier, for 6.2 GA3. </li><li> </li></ul>

RL064 - David Nebinger - Horror Stories

RL063 Andrew Jardine

For this episode I spoke with Andrew Jardine, Community Contributor Award winner for 7 years in a row about his history with Liferay, the community, how to improve it and, of course, his new passion project, https://masteringliferay.com/                 We've recorded this episode during Devcon 2019, but I've been keeping it back for a bit, to give Andrew a bit more time to produce more content for the site that we mainly talk about. Check it out - prepare to be amazed.              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. 

For this episode I spoke with Andrew Jardine, Community Contributor Award winner for 7 years in a row about his history with Liferay, the community, how to improve it and, of course, his new passion project, <a href="https://masteringliferay.com" rel="nofollow" target="_blank">https://masteringliferay.com/</a> We've recorded this episode during Devcon 2019, but I've been keeping it back for a bit, to give Andrew a bit more time to produce more content for the site that we mainly talk about. Check it out - prepare to be amazed. Here are some of the topics that we talked about: <ul> <li>How long he's around (and how he got his first fix of Liferay)</li> <li>His motivation to stay around, to help people</li> <li>How he started with <a href="https://masteringliferay.com" rel="nofollow" target="_blank">masteringliferay.com</a> and what you find on the site</li> <li>How does Mastering Liferay relate to Liferay University?</li> <li>Passion versus Business</li> <li>Potential for contributions, "Share an idea"</li> <li>Target Audience (currently Developer-centric, but conceptionally not limited to this audience)</li> <li>Shameless plug for <a href="https://web.liferay.com/marketplace/-/mp/application/170064253" rel="nofollow" target="_blank">ControlPanel Documentation</a> (because I can ;) ) - by now you can find the first links to masteringliferay right in that plugin</li> <li><a href="https://youtu.be/HSu-etVDfLc" rel="nofollow" target="_blank">Andrew's presentation</a> at Devcon, together with his business partner Julian "The journey of a Liferay Developer - Empowering the community"</li> <li>Thanking Andrew by making him work more - he was part of <a href="https://youtu.be/pTeYG4_n2dI" rel="nofollow" target="_blank">Opening Devcon</a>, playing an authentic Canadian.</li> </ul>

RL063 Andrew Jardine - Mastering Liferay

A conversation with David Nebinger, the number one contributor on the Liferay forums, about frequently asked questions.  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 ;)

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

RL062 David Nebinger

RL061 Caris Chan

It took me long enough to bring her on: She's followed Liferay's history for longer than some of the other founders: Caris Chan. And yes, that name means that she's Brian Chan's wife. During my last visit in Liferay HQ, I took the opportunity and asked her about her view on Liferay's history - about 15 years for the company and 20 years for the software project. 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?

It took me long enough to bring her on: She's followed Liferay's history for longer than some of the other founders: Caris Chan. And yes, that name means that she's Brian Chan's wife. During my last visit in Liferay HQ, I took the opportunity and asked her about her view on Liferay's history - about 15 years for the company and 20 years for the software project. Here are some of the topics that we talked about: <ul> <li>The history of Liferay as a product: How and why Brian started Liferay, and the first offer to buy the product.</li> <li>Caris' role from history to the present</li> <li>Early expansion and how Caris' pessimism balances Brian's optimism</li> <li>How Open Source opens doors that you didn't know where there (Shoutout to Bala)</li> <li>The reason for a lack of an exit strategy among the owners - why Liferay stays privately held without venture capital</li> <li>10% of Liferay's profits go to Liferay Foundation - as smart investments in the world</li> <li>How does a company that strives to stay private get into the acquisition business, acquiring two companies?</li></ul>

Radio Liferay - the podcast about Liferay: The people, the project, the product and the company

One of my favorite podcast.  I would like to see more community members and partners on the show to know about different implementations of Liferay

Very nice!!

Radio Liferay

Bryan Ho

 	I had a short meeting with Bryan Ho, Lead Graphic Designer at Liferay - With that role it's obvious that we're bridging the audio/visual gap again: A very visual topic in an audio only podcast. But if you're not driving while you listen to this podcast, you can click the links from the shownotes and browse through the archives.  	Apart from being the creator of the Radio Liferay Logo, Bryan is the creator of "Ray's intergalactiv adventures". You can check out this series at https://www.liferay.com/ray.  	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:

I had a short meeting with <a href="https://www.liferay.com/web/bryan.ho" rel="nofollow" target="_blank">Bryan Ho</a>, Lead Graphic Designer at Liferay - With that role it's obvious that we're bridging the audio/visual gap again: A very visual topic in an audio only podcast. But if you're not driving while you listen to this podcast, you can click the links from the shownotes and browse through the archives. 	Apart from being the creator of the Radio Liferay Logo, Bryan is the creator of "Ray's intergalactiv adventures". You can check out this series at <a href="https://www.liferay.com/ray" rel="nofollow" target="_blank">https://www.liferay.com/ray</a>. 	We talked about <ul> <li> 		The history of Ray:  He is an "old" mascot, has been around on the <a href="http://web.archive.org/web/20040401154517/https://www.liferay.com/home/index.jsp" rel="nofollow" target="_blank">very old website</a></li> <li> 		Bryan started to get involved with Ray for a T-Shirt contest in 2010 and continued to draw him</li> <li> 		How <a href="https://www.liferay.com/ray" rel="nofollow" target="_blank">Ray's intergalactic adventures</a> were started (Shoutouts to Paul Hinz and <a href="https://www.liferay.com/web/martin.yan" rel="nofollow" target="_blank">Martin Yan</a>)</li> <li> 		At Devcon Bryan  created a lot of variations on Ray "on demand". You can find several of them on the <a href="https://www.flickr.com/photos/liferay/sets/72157646508956289/page2/" rel="nofollow" target="_blank">flickr stream</a> from that event.</li> <li> 		Luckily, Bryan keeps Ray around, for example on community T-Shirts, even though the cartoon series is currently on hyades.</li> <li> 		And other things that the design team works on (Website, Events, improve overall visual appearance)</li> </ul> 	Here's Ray listening to Radio Liferay:

RL045 Bryan Ho on Design and Ray 

James Falkner

	In this episode I'm talking probably one last time to James Falkner about upcoming changes... James was the first guest on Radio Liferay (back in episode 1 - as well as others) and now - at least temporarily until episode 66 is published - will be the last. We're talking about upcoming changes, and sadly it looks like this will be his last appearance on this program.  Note: Currently the audio is still in post production, I'll publish it soon. Just subscribe to the Radio Liferay feed in your favorite podcatcher to get it delivered automatically. 	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

In this episode I'm talking probably one last time to <a href="https://www.liferay.com/web/james.falkner" rel="nofollow" target="_blank">James Falkner</a> about upcoming changes... James was the first guest on Radio Liferay (back in <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-1%3A-james-falkner" rel="nofollow" target="_blank">episode 1</a> - as well as others) and now - at least temporarily until episode 66 is published - will be the last. We're talking about upcoming changes, and sadly it looks like this will be his last appearance on this program.  Note: Currently the audio is still in post production, I'll publish it soon. Just subscribe to the Radio Liferay feed in your favorite podcatcher to get it delivered automatically. 	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: <ul> <li> <a href="http://dangerouslyawesome.com/2014/04/community-management-tummling-a-tale-of-two-mindsets/" rel="nofollow" target="_blank">Community Tummler</a></li> <li> <a href="https://git-man-page-generator.lokaltog.net/" rel="nofollow" target="_blank">git manpage generator</a></li> <li> <a href="https://dev.liferay.com/web/community-security-team" rel="nofollow" target="_blank">Community Security Team</a></li> <li> <a href="https://www.liferay.com/marketplace" rel="nofollow" target="_blank">Marketplace</a></li> <li> 		Events App (<a href="https://itunes.apple.com/de/app/liferay-events/id650199231?mt=8" rel="nofollow" target="_blank">iOS</a>, <a href="https://play.google.com/store/apps/details?id=com.liferay.events.global.mobile" rel="nofollow" target="_blank">Android</a>)</li> <li> <a href="https://dev.liferay.com/de/web/liferay-7-community-expedition" rel="nofollow" target="_blank">Community Expedition</a></li> <li> <a href="http://vanilla-js.com/" rel="nofollow" target="_blank">Vanilla JS</a></li> <li> <a href="https://en.wikipedia.org/wiki/Climate_of_Antarctica" rel="nofollow" target="_blank">Climate of Antarctica</a></li> <li> 		James' video farewell note</li> </ul> 	Stay tuned for further updates on what changes in community relations

RL055 James Falkner on Change

RL054 Scott Nicklous

Neil Griffin

	In this episode, recorded at Liferay's Devcon 2015 in Darmstadt/Germany, I'm talking to Scott Nicklous and Neil Griffin. Scott is the specification lead for JSR-362 - otherwise known as the Portlet Specification 3.0 - and Neil serves as Liferay's representative on the expert group. 	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

In this episode, recorded at Liferay's Devcon 2015 in Darmstadt/Germany, I'm talking to <a href="https://www.xing.com/profile/MartinScott_Nicklous" rel="nofollow" target="_blank">Scott Nicklous</a> and <a href="https://www.liferay.com/web/neil.griffin" rel="nofollow" target="_blank">Neil Griffin</a>. Scott is the specification lead for JSR-362 - otherwise known as the Portlet Specification 3.0 - and Neil serves as Liferay's representative on the expert group. 	Here are some of the topics that we talked about: <ul> <li> <a href="https://www.jcp.org/en/jsr/detail?id=362" rel="nofollow" target="_blank">JSR 362 page</a> with all the latest and current information (<a href="https://java.net/projects/portletspec3" rel="nofollow" target="_blank">spec</a>, <a href="https://java.net/projects/portletspec3/downloads/directory/V3Prototype" rel="nofollow" target="_blank">prototype implementation</a> and <a href="http://msnicklous.github.io/portletspec3/apidocs/index.html" rel="nofollow" target="_blank">javadoc</a>)</li> <li> 		The expert group</li> <li> 		JSR 286 portlets will run unchanged on JSR 362 (runtime and compiletime compatibility)</li> <li> 		My repeat <a href="http://geek-and-poke.com/geekandpoke/2014/11/8/frameworks" rel="nofollow" target="_blank">favourite statement about frameworks</a> in the web world.</li> <li> 		JSR 362 and its impact on UI, there's a Client-Side standard (on ECMA script) for the first time in the portlet spec</li> <li> 		The big question: When will it be done? (Some time 2016)</li> <li> 		Early Draft Review Spec available, ~80-90% of content is expected to be there (That's the statement from Devcon, in October 2015)</li> <li> 		Reference Implementation (to prove that the spec can be implemented) and TCK still missing (again, October 2015)</li> <li> 		Reference Implementation and TCK will be implemented under the Apache Pluto project, help required</li> <li> 		New Features include Bean-Portlet-Approach (portlet methods specified through Annotations in any Managed Bean), portlet.xml file no longer required if Annotations used</li> <li> 		specifies a JS API despite being a JSR, which covers traditionally only Java</li> <li> 		Dependency to JavaEE: Minimum is JavaEE 7, e.g. Servlet 3.1 etc.</li> <li> 		Portlet Spec is not part of the JavaEE, but extends some of its elements.</li> <li> 		CDI</li> <li> <a href="https://www.jcp.org/en/jsr/detail?id=378" rel="nofollow" target="_blank">JSR 378</a>: Portlet 3.0 bridge for JSF (where Neil is the spec lead), being built in parallel with JSR-362</li> <li> 		Multiplatform Support, Websocket, Devices</li> <li> 		The E-Mail Archive of the specification process <a href="https://java.net/projects/portletspec3/lists" rel="nofollow" target="_blank">is public</a> - contribution and comments are very welcome</li></ul>

RL054 Scott Nicklous and Neil Griffin on JSR 362 - Portlet 3.0

	I met repeat guest Nate Cavanaugh, Liferay's Director of UI Engineering, at this year's Devcon and he answered all UI-based questions that we could quickly think about - specifically with regards to Liferay 7. 	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.

I met repeat guest <a href="https://www.liferay.com/web/nathan.cavanaugh/profile" rel="nofollow" target="_blank">Nate Cavanaugh</a>, Liferay's Director of UI Engineering, at this year's Devcon and he answered all UI-based questions that we could quickly think about - specifically with regards to Liferay 7. 	As we recorded this on site at Devcon, you'll hear more background noise than usual - <a href="https://auphonic.com" rel="nofollow" target="_blank">Auphonic</a> did their best to clean the recording, and they did a great job. 	Here are some of the topics that we talked about: <ul> <li> 		UI frameworks get out of style soon. <a href="http://geek-and-poke.com/geekandpoke/2014/11/8/frameworks" rel="nofollow" target="_blank">Can I still use AngularJS</a>?</li> <li> 		Do I have to throw everything away that I have invested already?</li> <li> 		The YUI story and what its discontinuation means for AlloyUI</li> <li> 		Will AUI be reimplemented on jQuery? Is jQuery part of Liferay 7? What about different versions of jQuery?</li> <li> 		metal.js</li> <li> 		Lexicon, UI-Language, User Interface Guidelines</li> <li> 		Artifacts and Implementation of Lexicon</li> <li> 		Bootstrap, Bootstrap components, Atlas, the bootstrap versions in <a href="https://www.liferay.com/de/web/nathan.cavanaugh/blog/-/blogs/the-nitty-gritty-theme-improvements-and-bootstrap-in-liferay-6-6" rel="nofollow" target="_blank">Liferay 6.2</a> and the components of it that are available.</li> <li> 		What happens when Bootstrap 4 comes out?</li> <li> 		Single Page Application, SPA, <a href="http://sennajs.com/" rel="nofollow" target="_blank">SennaJS</a>: Go without full page reloads, largely by default.</li> <li> 		New Theming Tools - You can also use new tools in Liferay 6.2 (AYOR though). No more <code>_diffs</code> folder, pure frontend packages, themelets.</li> <li> 		What kind of themelets do we wish to have?</li> <li> 		We probably have forgotten something. Ask your questions in the comment section of this episode to be covered in future episodes.</li></ul>

RL053 Nate Cavanaugh - UI news in Liferay 7

Raymond Augé

 	A continuation of last week's episode, Milen Dyankov stepped in as a co-host and helped me ask the right questions: Ray Augé answers all sorts of questions about the Modularization in Liferay 7 and what to do with your existing investment in Liferay Plugins - what to do with the plugins you already have, where you will have to re-learn and what you can, should or shouldn't continue to do..  	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.

A continuation of last week's episode, <a href="https://www.liferay.com/web/milen.dyankov" rel="nofollow" target="_blank">Milen Dyankov</a> stepped in as a co-host and helped me ask the right questions: <a href="https://www.liferay.com/web/raymond.auge" rel="nofollow" target="_blank">Ray Augé</a> answers all sorts of questions about the Modularization in Liferay 7 and what to do with your existing investment in Liferay Plugins - what to do with the plugins you already have, where you will have to re-learn and what you can, should or shouldn't continue to do.. 	As we recorded this on site at Devcon, you'll hear more background noise than usual - <a href="https://auphonic.com" rel="nofollow" target="_blank">Auphonic</a> did their best to clean the recording, and they did a great job. 	Here are some of the topics that we talked about: 	Portlets: <ul> <li> 		If you're not interacting with Liferay, e.g. a pure JSR-286 portlet: No changes required</li> <li> 		JSF: Last kinks are worked out - test the more complex the JSF implementation is</li> <li> 		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 <a href="https://github.com/liferay/liferay-portal/blob/master/readme/7.0/BREAKING_CHANGES.markdown" rel="nofollow" target="_blank">these breaking changes</a> - well documented, huh? And even better: The document is machine-readable and there will be migration tools (future episode planned) 		<ul> <li> 				If the service is still in Liferay's core: No change needs to be made.</li> <li> 				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.</li> </ul> </li> <li> 		Circumstances under which Liferay automatically "translates" WAR file into OSGi bundles - and the caveats</li> <li> 		Extensions to Liferay MVC portlet: Check for the nature of those changes</li> <li> 		The use of CDI - especially when the appserver's implementation/resources are utilized - still requires some work.</li> <li> 		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</li> <li> 		How little of OSGi can I get away with?</li> </ul> 	Hooks <ul> <li> 		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.</li> <li> 		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. 		<ul> <li> 				(most likely: You need to convert to an MVC Command, injected as an OSGi module. There are samples available)</li> </ul> </li> <li> 		Liferay 7 has a lot more extension points than prior versions. The documentation is being made available on <a href="https://dev.liferay.com" rel="nofollow" target="_blank">dev.liferay.com</a> - obviously this is still work in progress, but is scheduled to be there until release.</li> <li> 		How can <a href="https://www.youtube.com/watch?v=CfHqAUz3I1Y" rel="nofollow" target="_blank">IDE</a> and other tools help identifying which extension points are in use? And how to make lots of friends within the Liferay Community</li> <li> 		Overriding Language Keys is quite simple - choose "global" or "per portlet" - those are the two available scopes that a translation can live in. 		<ul> <li> 				For migration you might have to decide which scope your changes should go into.</li> <li> 				Encoding still is done in UTF-8</li> </ul> </li> <li> 		JSP-Hooks: The elephant in the room: Seems to be very popular, but always has aimed at the implementation rather than to an API. 		<ul> <li> 				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...</li> <li> 				New options: JSPs can be deployed as proper OSGi bundles.</li> <li> 				There's still <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/overriding-jsps-from-multiple-hooks-promising-the-cure" rel="nofollow" target="_blank">danger</a> because technically the implementation is unchanged compared to earlier versions</li> <li> 				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. 				<ul> <li> 						replace the render-phase of a portlet through a portlet filter.</li> <li> 						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</li> </ul> </li> </ul> </li> </ul> 	Ext <ul> <li> 		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?</li> <li> 		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.</li> </ul> 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.

RL052 Raymond Augé - Upgrading your 6.x plugins to 7.0

Preston Crary

An episode on the "Per" things: Performance and Permissions. I spoke to Preston Crary, who amazingly was not mad at me for losing an earlier recording. 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.

An episode on the "Per" things: Performance and Permissions. I spoke to <a href="https://web.liferay.com/en/web/preston.crary" rel="nofollow" target="_blank">Preston Crary</a>, who amazingly was not mad at me for losing an earlier recording. We're talking about these (and more) topics <ul> <li> 		We open with the attention to detail that's required for working on performance tuning and some short conversation about this topic.</li> <li> 		Sadly, there's not often a single silver bullet, but many areas of dust.</li> <li> <a href="https://xkcd.com/221/" rel="nofollow" target="_blank">Sometimes the fastest code is not the most optimal</a></li> <li> 		Continuing with Preston's work on Permissions:</li> <li> 		ResourceBlock is deprecated, <a href="https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/com/liferay/portal/upgrade/util/BaseUpgradeResourceBlock.java" rel="nofollow" target="_blank">and there's an easy migration path</a> <ul> <li> 				an example <a href="https://github.com/liferay/liferay-portal/blob/master/modules/apps/collaboration/bookmarks/bookmarks-service/src/main/java/com/liferay/bookmarks/internal/upgrade/v2_0_0/UpgradeBookmarksEntryResourceBlock.java" rel="nofollow" target="_blank">upgrade path for bookmarks</a></li> </ul> </li> <li> 		The usecase for Resources, ResourcePermission, and ResourceBlocks (as they're not at all visible on the UI)</li> <li> 		Preston's way through Liferay from Support to working on the topics that he's now working on</li> <li> 		The <a href="https://github.com/liferay/liferay-portal/tree/master/portal-kernel/src/com/liferay/portal/kernel/security/permission/resource" rel="nofollow" target="_blank">new API for Permissions</a> - and the <a href="https://github.com/liferay/liferay-docs/tree/master/develop/tutorials/articles/140-application-security/01-application-permissions" rel="nofollow" target="_blank">documentation is also done</a> already (as of me writing this article, not yet published, but available on github - should be a matter of days or hours) 		<ul> <li> 				And an example: The <a href="https://github.com/liferay/liferay-portal/tree/master/modules/apps/web-experience/journal/journal-service/src/main/java/com/liferay/journal/internal/security/permission/resource" rel="nofollow" target="_blank">implementation of this API in Journal</a></li> <li> 				more documentation on <a href="https://github.com/liferay/liferay-docs/blob/master/develop/tutorials/articles/140-application-security/01-application-permissions/03-registering-permissions.markdown" rel="nofollow" target="_blank">registering</a> and <a href="https://github.com/liferay/liferay-docs/blob/master/develop/tutorials/articles/140-application-security/01-application-permissions/05-check-permissions.markdown" rel="nofollow" target="_blank">checking</a> permissions</li> </ul> </li> <li> 		Should you implement your own permission system? (and how the answer to this question might change in 7.1)</li> <li> 		Upgrades are being performance tuned. I smell a future episode coming up. Paging the team that is working on this area</li> <li> 		The remarkable memory savings that refactoring the UserBag introduced</li> <li> 		What happend during login</li> <li> 		Passwords are PBKDF2WithHmacSHA1/160/128000 hashed, a deliberately expensive password hashing algorithm.</li> <li> <a href="https://issues.liferay.com/browse/LPS-75747" rel="nofollow" target="_blank">LPS-75747</a> 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.</li></ul>

RL060 Performance and Permissions with Preston Crary

	Another Devcon "private" session - I missed his presentations, but got the summary right when he was done: Ray Augé took the time to answer all sorts of questions about the Modularization in Liferay 7. In fact, he answered so many questions that we made it a 2-episode recording. This week it's about the motivation for modularization: What problem does it solve? Next week will be more technical, telling you about the implications of the updated architecture to your code. 	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 :)

Another Devcon "private" session - I missed his presentations, but got the summary right when he was done: <a href="https://www.liferay.com/web/raymond.auge" rel="nofollow" target="_blank">Ray Augé</a> took the time to answer all sorts of questions about the Modularization in Liferay 7. In fact, he answered so many questions that we made it a 2-episode recording. This week it's about the motivation for modularization: What problem does it solve? Next week will be more technical, telling you about the implications of the updated architecture to your code. 	As we recorded this on site at Devcon, you'll hear more background noise than usual - As usual, <a href="https://auphonic.com" rel="nofollow" target="_blank">Auphonic</a> did their best to clean the recording, and they did a great job. 	Here are some of the topics that we talked about: <ul> <li> 		OSGi in Liferay 6.2 vs Liferay 7.0</li> <li> 		Modularization of Liferay 7.0</li> <li> 		Surprisingly (not!), modularization is not yet fully done, but it came a lot further than expected initially</li> <li> 		How much do you have to re-learn to build plugins for Liferay 7</li> <li> 		James: Community Roadmap Talk from <a href="https://www.liferay.com/web/events2015/devcon/recap" rel="nofollow" target="_blank">Devcon</a> (note: Ray also had several presentations at Devcon, you'll find his recordings there as well)</li> <li> 		Now everybody should be able to work the same way: Internally in Liferay's core as well as externally, in the plugins.</li> <li> 		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</li> <li> 		Of course we cover a release date :) I'm getting a very rough one from Ray :)</li></ul>

RL051 Raymond Augé - Motivation for Modularization

Jens Bruhn

 	Wow, 50 episodes already. At this year's Devcon I spoke with Jens Bruhn. He's Software Architect at Prodyna AG, a Liferay Partner and the author of Nabucco Script Center, a Liferay App available on the Marketplace. He also convened the "Pimp my Scripting Engine" workshop at Liferay's Devcon 2015, which I missed. But this only provided a perfect reason and excuse to speak to him.  	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 

Wow, 50 episodes already. At this year's <a href="https://www.liferay.com/web/events2015/devcon" rel="nofollow" target="_blank">Devcon</a> I spoke with <a href="https://www.liferay.com/de/web/jens.bruhn/profile" rel="nofollow" target="_blank">Jens Bruhn</a>. He's Software Architect at <a href="https://www.prodyna.com" rel="nofollow" target="_blank">Prodyna AG</a>, a Liferay Partner and the author of <a href="https://www.liferay.com/de/marketplace/-/mp/application/55972350" rel="nofollow" target="_blank">Nabucco Script Center</a>, a Liferay App available on the Marketplace. He also convened the "Pimp my Scripting Engine" workshop at Liferay's Devcon 2015, which I missed. But this only provided a perfect reason and excuse to speak to him. 	As we recorded this on site at Devcon, you'll hear more background noise than usual - As usual, <a href="https://auphonic.com" rel="nofollow" target="_blank">Auphonic</a> 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 <a href="https://www.prodyna.com/scriptcenter" rel="nofollow" target="_blank">plugin's homepage</a>. 	Here are some of the topics that we talked about: <ul> <li> 		The Elevator Pitch: What's Nabucco Script Center?</li> <li> 		Scripting in Liferay: The native script console, its use and its shortcomings (solved in NSC)</li> <li> 		a short demo of Script Center. It makes sense to check the screenshots alongside, or even install the plugin: 		<ul> <li> 				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) <a href="https://www.liferay.com/documents/1339770/62755788/Overview.png/fbc1294b-17c7-49e2-9199-cbba2ec5d9e0" rel="nofollow" target="_blank"> </a></li> <li> 				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 <a href="https://www.liferay.com/documents/1339770/62755788/Interception_OVERVIEW_01.png/9641278f-9e96-4987-8f21-11abbe46a9d5" rel="nofollow" target="_blank"></a></li> <li> 				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. <a href="https://www.liferay.com/documents/1339770/62755788/Schedule_UPDATE_WebContent_01.png/fdd82768-0642-4916-89c7-f545aec667dc" rel="nofollow" target="_blank"></a></li> <li> 				Prodyna has scripts available on <a href="https://www.prodyna.com/scriptcenter" rel="nofollow" target="_blank">the app's homepage</a> - 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.</li> <li> 				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.</li> </ul> </li> <li> <a href="https://twitter.com/docbruhn" rel="nofollow" target="_blank">Feadback required</a> - is this useful and what else is needed to make it more useful?</li> <li> 		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: </li> <li> 		Best Practices when implementing features in scripts: It's easy to accidentally make mistakes - there should be some basic safeguards.</li> <li> 		Script Center offers a third option to two customization approaches mentioned my <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/the-right-tool-for-the-job-chapter-2-customizing-a-core-portlet" rel="nofollow" target="_blank">earlier blog article</a></li> </ul>

RL050 Pimp My Scriptengine with Jens Bruhn

	It's been a long time and finally... Radio Liferay is back with several episodes in the queue. Today, Tomáš Polešovský starts of by talking about Liferay's security team and -procedures as well as his work within that team. Tom has already been a guest on Radio Liferay's ancient episode 9 	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)

It's been a long time and finally... Radio Liferay is back with several episodes in the queue. Today, <a href="https://www.liferay.com/web/tomas.polesovsky" rel="nofollow" target="_blank">Tomáš Polešovský</a> starts of by talking about Liferay's <a href="https://dev.liferay.com/web/community-security-team" rel="nofollow" target="_blank">security team</a> and -procedures as well as his work within that team. Tom has already been a guest on Radio Liferay's ancient <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-9:-community-contributors" rel="nofollow" target="_blank">episode 9</a> 	Here are some of the topics that we talked about: <ul> <li> 		The glorious glamorous days one has on the security team (consisting mostly of email, tickets, pullrequests) 		<ul> <li> 				Different ways to make Liferay more secure</li> <li> 				Gathering <a href="https://dev.liferay.com/web/community-security-team/process" rel="nofollow" target="_blank">feedback</a> from community and customers</li> <li> 				Monitoring Liferay Forums and full disclosure mailing lists (also about the various libraries that are used in Liferay)</li> <li> 				Scan source code for problems</li> </ul> </li> <li> 		Liferay cooperates with external security researchers for penetration testing</li> <li> 		Customers perform external audits as well.</li> <li> 		An example of an actual audit report: 49 very alarming false positives vs. 1 real cornercase</li> <li> 		The <a href="https://dev.liferay.com/web/community-security-team/process" rel="nofollow" target="_blank">security issue fixing process</a></li> <li> 		The first <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-22-samuel-kong-on-securi-1" rel="nofollow" target="_blank">security episode with Sam Kong</a></li> <li> 		Link to community security update page. CE updates always only against the latest GA version</li> <li> 		Some low hanging fruits in secure Liferay administration (on the fly) 		<ul> <li> 				Disable "create new accounts" if you don't want random users to create new accounts (e.g. in an intranet)</li> <li> <a href="https://www.youtube.com/watch?v=OhwfrimJsiE" rel="nofollow" target="_blank">JSONWS</a> access</li> <li> 				Disable Control Panel, add "My Account" to user's personal pages instead</li> <li> 				The <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/securing-liferay-chapter-1-introduction-basics-and-operating-system-level" rel="nofollow" target="_blank">securing Liferay</a> series and <a href="https://dev.liferay.com/web/community-security-team/overview" rel="nofollow" target="_blank">"additional Resources" here</a></li> </ul> </li> <li> 		What will happen with Liferay 7?</li> <li> 		OAuth, and the related <a href="https://www.liferay.com/web/olaf.kock/blog/-/blogs/radio-liferay-episode-44-stian-sigvartsen-on-social-apps-proxy" rel="nofollow" target="_blank">Radio Liferay episode 44 with Stian</a></li> <li> <a href="https://www.grc.com/sqrl/sqrl.htm" rel="nofollow" target="_blank">SQRL</a> (disclaimer: I misled Tom by mispronouncing this library - he's aware, but there's no implementation - yet - for Liferay)</li></ul>

RL049 Security with Tomáš Polešovský

Thomas Schweiger

	The nerdiest topic so far: I'm speaking to Thomas Schweiger, 	german national barista champion 2010-2012. He was sponsored by our german partner 	Prodyna to prepare coffee during this years Devcon and Portal Solutions Forum Germany. 	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.

The nerdiest topic so far: I'm speaking to <a href="http://www.greenandbean.de" rel="nofollow" target="_blank">Thomas Schweiger</a>, 	german national barista champion 2010-2012. He was sponsored by our german partner 	<a href="http://www.prodyna.com" rel="nofollow" target="_blank">Prodyna</a> to prepare coffee during this years Devcon and Portal Solutions Forum Germany. 	We talked about <ul> <li> 		What do you need to do to become Barista Champion?</li> <li> 		Can you describe upfront what your coffee will taste like when you prepare it?</li> <li> 		Importing coffee, roasting, drying, grinding and preparing</li> <li> 		Latte Art (learn it by just listening to this episode): 		<ul> <li> 				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.</li> <li> 				Find Latte Art tutorials on Youtube (or find out what it actually is and what pictures people actually do)</li> </ul> </li> <li> 		Shoutout to Wolfram Sorg, from Prodyna Sales, who is teaming up with Thomas</li> <li> 		Did you know you can be a coffee consultant? Thomas is. He's consulting on coffee farms, cafés and barista training.</li></ul>

RL046 Thomas Schweiger on Coffee

Kristoffer Onias

Victor Ware

	Yay, another episode, and maybe in time to sweeten your trip to Devcon in Amsterdam. I spoke to Kristoffer Onias and Victor Ware. Both work on testing Liferay with different areas of interest. You'll hear quite a bit about what Liferay does internally on testing. 	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

Yay, another episode, and maybe in time to sweeten your trip to <a href="https://liferay.com/devcon" rel="nofollow" target="_blank">Devcon</a> in Amsterdam. I spoke to Kristoffer Onias and Victor Ware. Both work on testing Liferay with different areas of interest. You'll hear quite a bit about what Liferay does internally on testing. 	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 <ul> <li> 		Different levels of Tests: 		<ul> <li> 				Unittests</li> <li> 				Integration Tests</li> <li> 				Functional Tests</li> </ul> </li> <li> 		How SPA influenced frontend testing</li> <li> 		Selenium, Selenium IDE, Web Driver, Capybara, Docker, and Jenkins</li> <li> 		How pull requests are tested before they reach their addressee</li> <li> 		The scale of Liferay's testing infrastructure</li> <li> 		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</li> <li> 		Maintenance of large test sets - UI locators etc.</li> <li> 		SevenCogs and <a href="https://github.com/olafk/liferay-7kock" rel="nofollow" target="_blank">its resurrection</a></li> <li> 		How to scale testing infrastructure for potentially a lot more servers and environments</li> <li> 		The Test Pyramid</li> <li> 		A wild idea: Livestream of test runs</li> <li> 		Liferay's <a href="https://www.liferay.com/documents/10182/3292406/Liferay+Quality+Assurance+Program+Overview/474b10b6-0ed6-43b7-bca4-5c07588697bc" rel="nofollow" target="_blank">Testing Whitepaper</a> and a <a href="https://www.liferay.com/events?marketingEventId=231439020" rel="nofollow" target="_blank">Testing Webinar</a> </li> <li><a href="http://geek-and-poke.com/geekandpoke/2017/2/15/fifty-shades-of-red" rel="nofollow" target="_blank">50 shades of red</a> and its <a href="http://geek-and-poke.com/geekandpoke/2017/2/18/50-shades-part-2" rel="nofollow" target="_blank">part 2</a></li></ul>

RL059 Testing at Liferay with Kristoffer Onias and Victor Ware

Jorge Ferrer

	Two episodes (or an eternity) ago, I spoke to Jorge Ferrer, Liferay's VP of Engineering. We didn't have enough time to finish the conversation, so we continued a while after - and then I buried the recording /o\. Anyway, apart from it being still from "before the release of the current version", it's still relevant stuff, I feel bad about missing to post it. Check for yourself - here it finally is. 	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?

Two <a href="http://radioliferay.com/episode/56" rel="nofollow" target="_blank">episodes</a> (or an eternity) ago, I spoke to <a href="https://www.liferay.com/web/jorge.ferrer" rel="nofollow" target="_blank">Jorge Ferrer</a>, Liferay's VP of Engineering. We didn't have enough time to finish the conversation, so we continued a while after - and then I buried the recording /o\. Anyway, apart from it being still from "before the release of the current version", it's still relevant stuff, I feel bad about missing to post it. Check for yourself - here it finally is. 	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 <ul> <li> 		Microservices vs Monoliths 		<ul> <li> 				Buzzword or breeze of fresh air?</li> <li> 				DHH <a href="https://m.signalvnoise.com/the-majestic-monolith-29166d022228" rel="nofollow" target="_blank">The Majestic Monolith</a></li> <li> 				Approach this technology option like any other</li> <li> 				If you can't build a monolith, you are probably getting an even bigger mess if you approach microservices</li> <li> 				Milen's presentation: <a href="http://www.slideshare.net/MilenDyankov1/microservices-and-modularity" rel="nofollow" target="_blank">Microservices and Modularity or the difference between treatment and cure</a> (or <a href="https://www.youtube.com/watch?v=O77777Zy_HE" rel="nofollow" target="_blank">on youtube</a>)</li> </ul> </li> <li> 		Shortly before the release many modules were moved around and renamed. We talk about the reasons and what this meant for the translations</li> <li> 		What's the meaning of "Feature-Complete"?</li> <li> 		A lot of Feedback starts to come in during the Beta Cycle</li> <li> 		Nitpicking on the Beta Criteria: JBoss and Upgrade Routines</li> <li> 		Lookahead on the next episode on Performance Tuning</li> <li> 		Releaseplans (of course, I could have retrofitted an exact release date...)</li> <li> 		What's it like to be hired into Liferay Engineering? 		<ul> <li> <a href="https://liferay.com/careers" rel="nofollow" target="_blank">https://liferay.com/careers</a></li> <li> 				office envy</li> <li> 				shared spaces, decoration, own desks, separate working environments, inspiration, agora</li> </ul> </li> <li> 		Is it forbidden to write Javadoc?</li></ul>

RL058 Jorge Ferrer (continued)

Today I'm welcoming a repeat guest, Jorge Ferrer, Liferay's VP of Engineering. I've had the great opportunity to ask him a lot of questions that provide deep insight into what's running behind the scenes in the engineering team. We didn't have enough time, so this is part 1 of our conversation, to be continued in episode 58. I need to squeeze in the (already recorded) episode that contains more information about the Javadoc Contest (please participate). 	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 &amp; 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.

Today I'm welcoming a repeat guest, <a href="https://www.liferay.com/web/jorge.ferrer" rel="nofollow" target="_blank">Jorge Ferrer</a>, Liferay's VP of Engineering. I've had the great opportunity to ask him a lot of questions that provide deep insight into what's running behind the scenes in the engineering team. We didn't have enough time, so this is part 1 of our conversation, to be continued in episode 58. I need to squeeze in the (already recorded) episode that contains more information about the <a href="https://www.liferay.com/c/blogs/find_entry?entryId=71001130&amp;showAllEntries=0" rel="nofollow" target="_blank">Javadoc Contest</a> (please participate). 	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 <ul> <li> 		the engineering team passed the 150 people mark, distributed world wide.</li> <li> 		Communication in a team that's distributed through the world, tools</li> <li> 		Some nasty german guy recently took Jorge's #3 contributor place on the public forums</li> <li> 		Participation &amp; Contribution: Check <a href="https://dev.liferay.com/participate" rel="nofollow" target="_blank">https://dev.liferay.com/participate</a>.</li> <li> 		What happens to pullrequests to the Liferay repository? Should you rather direct to the component lead?</li> <li> 		Coding Standards, Design Patterns and how many you want to use in a single project</li> <li> 		Pullrequests and who's working on them.</li> <li> 		The experience of upgrading the architecture to OSGi in Liferay 7</li> <li> 		Jorge's <a href="https://www.liferay.com/web/jorge.ferrer/blog/-/blogs/liferay-s-architecture-the-beginning-of-a-blog-series" rel="nofollow" target="_blank">Architecture Blog Article</a>(s)</li> <li> 		News about <a href="https://dev.liferay.com/" rel="nofollow" target="_blank">Developer Network</a>: Many new project documented there</li> <li> 		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.</li> <li> 		stay tuned for the continuation of this episode, most likely in episode 58.</li></ul>

RL056 Jorge Ferrer

Stian Sigvartsen

	This is my conversation with Stian Sigvartsen, winner of the Marketplace App contest with his Social Apps Proxy (Link) and well known member of the UK Liferay usergroup, working in Devon and quite a lot with Liferay. Our paths cross quite often, but we finally found some time to talk about Stian's award winning app which basically takes all the boring stuff out of OAuth integrations into 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 my conversation with <a href="https://www.liferay.com/de/web/stian.sigvartsen/profile" rel="nofollow" target="_blank">Stian Sigvartsen</a>, winner of the Marketplace App contest with his <a href="https://www.liferay.com/marketplace/-/mp/application/41226182" rel="nofollow" target="_blank">Social Apps Proxy</a> (Link) and well known member of the UK Liferay usergroup, working in Devon and quite a lot with Liferay. Our paths cross quite often, but we finally found some time to talk about Stian's award winning app which basically takes all the boring stuff out of OAuth integrations into Liferay 	He did a great job of explaining the background and solution in audio. Here's what we talked about: <ul> <li> 		Social Apps Proxy enables you to integrate content from other social networks into your portal.</li> <li> 		It's working through OAuth, basically taking over all of the dirty work of authentication, leaving the actual integration works for the implementor</li> <li> 		Stian's sample app on github (Link): Getting twitter mentions with 10 lines of code</li> <li> 		What problem does OAuth solve? Comparing OAuth with a Valet Key.</li> <li> 		Linking Liferay's identity to twitter's (in this sample)</li> <li> 		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</li> <li> <a href="https://www.liferay.com/marketplace/-/mp/application/41226182" rel="nofollow" target="_blank">Social Apps Proxy on Marketplace</a></li> <li> 		Supported Versions of Liferay 6.1 to 6.2 and OAuth 1.0a to 2 to be extended</li> <li> 		Microservices</li> <li> 		All Code is to be open sourced soon, contributors are welcome.</li></ul>

RL044 Stian Sigvartsen on Social Apps Proxy

Brett Swaim

I'm talking with Brett Swaim, Principal Consultant at Liferay US, on application performance monitoring, horror stories and things to avoid. Brett is dealing with a lot of customers. He's one of Liferay's go-to resources for performance tuning and monitoring. Brett had a presentation on &gt;DevOps Best Practices with Liferay, Logstash, Kibana, Elasticsearch, and New Relic at Devcon (among other symposiums and events). If you missed it or just want the audio summary (both were my motivations to talk to him), we're talking about his experience, using one of the projects (an unnamed one) as an example. 	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.

I'm talking with <a href="https://www.liferay.com/web/brett.swaim" rel="nofollow" target="_blank">Brett Swaim</a>, Principal Consultant at Liferay US, on application performance monitoring, horror stories and things to avoid. Brett is dealing with a lot of customers. He's one of Liferay's go-to resources for performance tuning and monitoring. Brett had a presentation on &gt;<a href="https://www.youtube.com/watch?v=Q1M-YDPUJkU" rel="nofollow" target="_blank">DevOps Best Practices with Liferay, Logstash, Kibana, Elasticsearch, and New Relic</a> at Devcon (among other symposiums and events). If you missed it or just want the audio summary (both were my motivations to talk to him), we're talking about his experience, using one of the projects (an unnamed one) as an example. 	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 <ul> <li> 		Application Lifecycle and Performance monitoring, <a href="http://newrelic.com" rel="nofollow" target="_blank">New Relic</a>  (used as a sample here), <a href="http://www.compuware.com" rel="nofollow" target="_blank">Compuware</a> , <a href="http://www.appdynamics.com" rel="nofollow" target="_blank">AppDynamics</a>. Or check the <a href="http://www.gartner.com/technology/reprints.do?id=1-23QQOPU&amp;ct=141029&amp;st=sb" rel="nofollow" target="_blank">Gartner Quadrant </a></li> <li> 		If you can't host in the cloud, you can use the same strategies that Brett is talking about with on-premise solutions</li> <li> 		How do you know your application is slow?</li> <li> <a href="http://www.elasticsearch.org/overview/" rel="nofollow" target="_blank">ELK-Stack</a> (Elasticsearch, Logstash and Kibana)</li> <li> 		adding page load times to <a href="http://httpd.apache.org/docs/trunk/mod/mod_log_config.html" rel="nofollow" target="_blank">Apache Logs</a></li> <li> 		It matters where you measure from: Internal network, external network.</li> <li> 		Default configuration of Liferay - memory, garbage collection and other JVM settings</li> <li> 		You can have too much memory in your JVM</li> <li> 		Liferay's Whitepapers have starting points, you shouldn't use them as your final settings.</li> <li> 		...and you'll actually need to measure for yourself in order to find your number...</li> <li> 		CDN setup and its results on high volume site</li> <li> 		Be proactive. You'll find bottlenecks before your users do.</li></ul>

RL043 Brett Swaim on Application Performance Management

At Devcon, I took the opportunity to meet several people - stay tuned for several more episodes during the rest of this year. For this episode, I spoke with Zsigmond Rab. Zsigmond is Lead Engineer, Technical Support &amp; Trainer at Liferay Hungary. This is a short and informal tongue-in-cheek talk about support-related issues. 	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.

At <a href="https://www.liferay.com/devcon2014" rel="nofollow" target="_blank">Devcon</a>, I took the opportunity to meet several people - stay tuned for several more episodes during the rest of this year. For this episode, I spoke with <a href="https://www.liferay.com/web/zsigmond.rab" rel="nofollow" target="_blank">Zsigmond Rab</a>. Zsigmond is Lead Engineer, Technical Support &amp; Trainer at Liferay Hungary. This is a short and informal tongue-in-cheek talk about support-related issues. 	We talked and joked about <ul> <li> 		The structure of the Hungarian Support teams</li> <li> 		How <strike>bugs</strike> unexpected features are handled</li> <li> 		How to make sure that these don't show up again in the next version</li> <li> 		Fixpacks, Hotfixes, Servicepacks</li> <li> 		Other worldwide support teams</li> </ul> 	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.

RL042 Zsigmond Rab on Enterprise Support

The best podcasts about ourselves as well as the world through the lense of Science. Specific topics include things about our brain, emotions to biology, physics and more!

Best Episodes on Science, Humans & The World

The best podcast episodes on parenting. Interviewing experts and talking through common issues surrounding parenting. This topic is filled with important lessons and insights for anyone listening. Add episodes you're interested into your queue below!