Piotr Paradiuk 3 Years Ago - Edited I'm glad you're taking steps towards a real open source collaboration. I hope you keep pushing in this direction, although I can still see challenges that are ahead to having actually good contribution process in place where it's useful for Liferay source and helps improve functionalities that have flaws which can be easily enhanced by the community. Please sign in to reply. Reply as... Cancel
Fredi B 3 Years Ago - Edited Sorry to say but Liferay is far, far away from "take Open Source roots seriously". A main principle of open source is to have "documentation freely available to the public". You will have a hard time searching for really good, free available Liferay documentation. Some breadcrumbs here, some breadcrumbs there and you need to always hope for the help of the competent people in the forums. This needs to be taken definitely more "seriously". Please sign in to reply. Reply as... Cancel Olaf Kock Fredi B 3 Years Ago Hi Fredi, There are several layers on which to comment on your post - first of all: If that's your perception, then it's valid - because obviously your expectation has not been met. And while I don't want to go into an argument about validity or correctness of the assumptions, or completeness of the available information: With this statement here, others will read it and might assume that your opinion is fact. Currently, there's a lot of documentation available on help.liferay.com and learn.liferay.com. (I'm saying "currently" as I don't know where more official documentation will have popped up when someone is reading this comment in the future). Also here, on the community site in the forums, on slack, community blogs, on Liferay university and on various external blogs that publish specific information and tipps. (and more - I'm not trying to be exhaustive here) There's a whole team paid to document more and more features. Just the salary of the documentation team by far exceeds the revenue from the Open Source licenses (0 €). And that's not even mentioning the developers' salaries. Naturally, documentation for the latest version might lag behind the feature implementation. The alternative would be to hold back the releases until documentation has been written. Writing documentation always targets a specific audience - ideally that's me (on my specific level of knowledge), but I'd also be happy if it was you (on your level). But sometimes it's somebody else - who might be neither on my nor on your level of experience. They might be happy about that piece of documentation, or it might go over their head. I've just had a conversation with Bryan, Liferay's CEO, to be edited and published on Radio Liferay soon - in it we cover Open Source being at the heart of Liferay as well. And for me, that goes back 12 years with an unbroken promise (https://www.olafkock.de/ok/2008/09/26/making_money_with_opensource_software.html) I won't even be going into arguments over what makes up taking Open Source seriously. But anything that you're not happy with is easy to fix with the right contributions. Matija describes that this now is a lot easier than before. That being said: More free documentation will be available during /dev/24. You've been heard, no matter if I agree with you or not, or to what extent. Please sign in to reply. Reply as... Cancel
Olaf Kock Fredi B 3 Years Ago Hi Fredi, There are several layers on which to comment on your post - first of all: If that's your perception, then it's valid - because obviously your expectation has not been met. And while I don't want to go into an argument about validity or correctness of the assumptions, or completeness of the available information: With this statement here, others will read it and might assume that your opinion is fact. Currently, there's a lot of documentation available on help.liferay.com and learn.liferay.com. (I'm saying "currently" as I don't know where more official documentation will have popped up when someone is reading this comment in the future). Also here, on the community site in the forums, on slack, community blogs, on Liferay university and on various external blogs that publish specific information and tipps. (and more - I'm not trying to be exhaustive here) There's a whole team paid to document more and more features. Just the salary of the documentation team by far exceeds the revenue from the Open Source licenses (0 €). And that's not even mentioning the developers' salaries. Naturally, documentation for the latest version might lag behind the feature implementation. The alternative would be to hold back the releases until documentation has been written. Writing documentation always targets a specific audience - ideally that's me (on my specific level of knowledge), but I'd also be happy if it was you (on your level). But sometimes it's somebody else - who might be neither on my nor on your level of experience. They might be happy about that piece of documentation, or it might go over their head. I've just had a conversation with Bryan, Liferay's CEO, to be edited and published on Radio Liferay soon - in it we cover Open Source being at the heart of Liferay as well. And for me, that goes back 12 years with an unbroken promise (https://www.olafkock.de/ok/2008/09/26/making_money_with_opensource_software.html) I won't even be going into arguments over what makes up taking Open Source seriously. But anything that you're not happy with is easy to fix with the right contributions. Matija describes that this now is a lot easier than before. That being said: More free documentation will be available during /dev/24. You've been heard, no matter if I agree with you or not, or to what extent. Please sign in to reply. Reply as... Cancel