<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lukas on Medium]]></title>
        <description><![CDATA[Stories by Lukas on Medium]]></description>
        <link>https://medium.com/@laporta?source=rss-68b248970978------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6dAAIdKyFGEZltvwxFuzaA.jpeg</url>
            <title>Stories by Lukas on Medium</title>
            <link>https://medium.com/@laporta?source=rss-68b248970978------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:38:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@laporta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — November 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-november-2018-a25dac1455f2?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/a25dac1455f2</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Wed, 28 Nov 2018 13:30:51 GMT</pubDate>
            <atom:updated>2018-11-28T13:30:51.211Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>OpenPaaS’ Newsletter — November 2018</h3><h4>Around building software</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j3afRmCeFSlXEcztYkPJjw.jpeg" /><figcaption>What synchronous and non-distributed work look like. Is software development akin to that kind of work? Spoiler alert: it is not.</figcaption></figure><p>Beware readers: this newsletter is about <strong>the context around building a software</strong> and wasn’t written by a developer. Don’t run away yet, as it has however been signed off by a handful of them.</p><p>Good reading!</p><h4>Planning before writing</h4><p>Building a complex software is a long endeavor, which (arguably) starts long before you even start to write your first line of code. Prior to typing on your keyboard, a handful of critical decisions much be made that will have long lasting effects on the life of your project:</p><ul><li><strong>Programming language to use</strong> (i.e.: JavaScript; Java; Go; Rust; Swift; Kotlin; etc.);</li><li><strong>Components and libraries to rely on</strong> (i.e.: MongoDB or Cassandra; RabbitMQ or Apache Kafka; VueJS or React; etc.)</li><li><strong>Functionalities to implement </strong>(i.e.: what your software will do and perhaps more importantly, <em>won’t do</em>)</li><li><strong>The architecture of your software </strong>(i.e.: how to model your software’s internal structure)</li><li><strong>The right level of abstraction for your infrastructure</strong> (i.e.: from bare-metal to serverless architecture)</li><li><strong>Platforms to target</strong> (i.e.: Android; iOS; Windows; macOS; web)</li><li><strong>Development method to use</strong> (i.e.: Agile Scrum; Kanban; etc.);</li><li><strong>Target market</strong> (i.e.: B2B; B2C; the entire universe and beyond)</li><li><strong>Business model to follow</strong> (i.e.: an open source core with proprietary and paid functionalities built on top of it; a fully open source with paid services such as integration and support: the latter is what LINAGORA is pursuing)</li><li><strong>Licensing scheme to choose</strong> (i.e.: permissive open source licenses such as the MIT or Apache License, or less permissive ones such as Affero General Public License, which OpenPaaS <a href="https://github.com/linagora/openpaas-esn/blob/master/LICENSE">uses</a>)</li><li>and so forth.</li></ul><p>This list is not ordered. Jonathan, from the newly created LinShare SaaS, would put it in this order:</p><blockquote><strong>What?</strong> What kind of service do I want to offer? <strong>With whom</strong> do I want to work? (a method is needed if more than one person is involved)? <strong>For who?</strong> Just for me, to sale it, or to offer it to the community?<strong> How? </strong>First: design the architecture, then pick the language, the database and at the end the libraries.</blockquote><p>Each decision implies trade-offs. For instance, if you write system-level programs, you might want to pick a really recent programming such as Rust, which is considered to be safer than other alternatives, but if you do so, it will come at the cost of having lesser developed libraries (which is arguably balanced by the fact that Rust libraries are known to be of high quality. I am looking at you <a href="https://ieeexplore.ieee.org/document/6470829">npm</a>).</p><p>For this short article, we will focus on three elements only: <strong>the model</strong>, <strong>the tooling</strong>, <strong>the programming language and its libraries</strong>, from a developer’s perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Qo57noz7YO48Aqu-LaJNw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/R-HXWCbCBGU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Holyoake</a> on <a href="https://unsplash.com/search/photos/open-source?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>The model</h4><p>Just like architects, developers are using a variety of tools to build complex artifacts. But unlike architects, developers’ tools are rapidly evolving.</p><p>A striking difference between software engineering and pretty much any other industries is the fact that developers are allowed if not encouraged to reuse a tremendous amount of existing components to build their project faster, thanks most notably to Open Source software.</p><p>OpenPaaS, which was released <a href="https://medium.com/linagora-engineering/openpaas-is-out-773704eadfbc">earlier this year</a>, is built on top of many Open Source components, and, perhaps, would not exist if those elements were not widely available and free to use. At the very least, <a href="https://open-paas.org/product/">we acknowledge</a> the use of those components, such as <a href="http://mongodb.org/">MongoDB</a>, <a href="https://www.rabbitmq.com/">RabbitMQ</a>, or <a href="http://james.apache.org/">James</a>, and whenever we can, <a href="https://github.com/sabre-io/dav/pull/1088">we contribute back</a>. In the case of <a href="http://james.apache.org/">James</a>, we even lead the development of the component being used.</p><p>The open source model allows to reduce the number of components you would need to normally have to build yourself, and to reduce the maintenance burden. It can greatly accelerate the pace of your development. It comes at the cost, tough: you rely on the work of others, and as it the case of MongoDB, you may not appreciate where they are heading too, from a technical or a <a href="https://techcrunch.com/2018/10/16/mongodb-switches-up-its-open-source-license/">legal standpoint</a>.</p><p>LINAGORA’s software such as <a href="http://www.linshare.org/en/">LinShare</a> — which we dedicated our <a href="https://medium.com/linagora-engineering/openpaas-newsletter-october-2018-3788021438a4">newsletter</a> to last month — and <a href="https://open-paas.org/">OpenPaaS</a>, are both embracing the open source model, without any proprietary features built on top of it. We call it the free-free model.</p><h4>The tooling</h4><p>At <a href="https://linagora.com/">LINAGORA</a>, we use <a href="https://about.gitlab.com/">GitLab</a> to host our code repositories. Just about two years ago, we were relying on Atlassian Stash, now known as <a href="https://bitbucket.org/">BitBucket</a>. Nowadays, on top of hosting our repositories, GitLab is also used to do issue tracking and to implement continuous integration, something that was done by individual tools before. On top of that, GitLab allows code to be reviewed, which is an important part of a developer’s job. According to <a href="https://twitter.com/Aymane93600">Ayman</a>, which is primarily working on the calendar part of OpenPaaS, this consolidation has been beneficial:</p><blockquote>No need to swap between three applications anymore. Everything is available in one yet powerful application.</blockquote><p>Bonus point, our internal development teams are using GitLab in creative ways, such as by relying heavenly on Mermaid to draw diagrams and flowcharts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*yq6X3Fr6KpvqCVEfMJLj0w.png" /><figcaption>How a sprint is organized internally</figcaption></figure><h4>Language and libraries</h4><p>More than five years ago, the foundations on top of which OpenPaaS was about to be built were laid.</p><p>OpenPaaS, our open collaborative platform, is mainly written in JavaScript, the language of choice for developing dynamic web applications. JavaScript is more than a language, it is an entire ecosystem, and OpenPaaS is heavily relying on it, since the beginning as a research project to nowadays, as a system running in production.</p><p>A few words on JavaScript. At the beginning of its journey as a programming language, JavaScript was meant to only run code on the client, directly within internet browsers. But popular projects such as Node.js came to life, to allow JavaScript to control what would happen on the server side.</p><p>Node.js has its own package manager, called npm, which allows developers to look for useful components they could reuse to build their applications upon.</p><p>What about the front-end? In the case of OpenPaaS, which relies on <a href="https://angularjs.org/"><strong>AngularJS</strong></a> in its first iteration, we recently had to make a choice for a new framework: we ended picking <a href="https://vuejs.org/"><strong>VueJS</strong></a>, against <a href="https://reactjs.org/"><strong>React</strong></a> as the main contender.</p><p>Consider the present article to be a teaser, as in a not-so distant future, our reasoning behind this choice may be laid down on a technical article.</p><p>In the meantime, we may want to have a look at past articles on AngularJS and its dynamic directives, as it used by OpenPaaS.</p><ul><li><a href="https://medium.com/linagora-engineering/angularjs-dynamic-directives-eee56a86f7ed">AngularJS dynamic directives</a></li><li><a href="https://medium.com/linagora-engineering/best-practice-to-test-your-angular-directive-and-component-bdb2776e0068">Best practice to test your Angular directive and component</a></li></ul><h4>Conclusion</h4><p><strong>That’s about it! </strong>We hope you have enjoyed reading this newsletter!</p><p>Keep in touch with <strong>OpenPaaS</strong> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub,</a> and our dedicated <a href="https://forum.open-paas.org/">Forum</a>. For LinShare, follow its <a href="https://twitter.com/LinShare_FOSS">Twitter</a> account.</p><p>Interested in joining <strong>LINAGORA</strong>? <a href="https://jobs.linagora.com/">We are hiring<em>!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a25dac1455f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-november-2018-a25dac1455f2">OpenPaaS’ Newsletter — November 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — October 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-october-2018-3788021438a4?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/3788021438a4</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[file-sharing]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Mon, 29 Oct 2018 10:26:59 GMT</pubDate>
            <atom:updated>2018-10-31T09:51:03.160Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>OpenPaaS’ Newsletter — October 2018</h3><h4>…Upgrade successfully completed…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*R0lWeNqtayyRJx_X_L_Arw.png" /><figcaption>LinShare illustrated: “a picture is worth a thousand words”</figcaption></figure><p>New versions of both OpenPaaS and LinShare have been released recently, respectively 1.2 and 2.2. In OpenPaaS’ case, <a href="https://open-paas.org/">its website has been overhauled</a>, and we invite you to take a peek at it. Throughout this newsletter, recent software changes will be introduced and a special attention will be dedicated to <strong>presenting LinShare</strong>, its history, and where it is heading to. But as a start, let’s talk about OpenPaaS, which has recently reached a new milestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*QnLqpwlDQQzpc4jyQD-TRg.png" /><figcaption>Open Collaborative Platform</figcaption></figure><p>OpenPaaS, our open collaborative platform, has hit version 1.2, also known as <strong>Botein</strong>.<em> </em>Botein, which also goes by the name <a href="https://en.wikipedia.org/wiki/Delta_Arietis">Delta Arietis</a>, is a star located in the northern constellation of Aries. Its name derives from Al Bīrūnī’s <em>Al Buṭayn, </em>which roughly translates to “The Belly”.</p><p>What Botein does introduce? Botein<em> </em>further increases OpenPaaS’ <strong>modularity</strong>, provides minor fixes in the core and its modules: in many respects, it can be considered a maintenance release, meant to further increase OpenPaaS’ <strong>stability</strong>, especially in a <strong>clustered environment</strong> like Kubernetes, that we are primarily targeting for <a href="https://medium.com/linagora-engineering/when-linagora-embraces-kubernetes-1609792e955b">our deployments</a>. Botein’s <a href="https://open-paas.org/releasenotes-v1-2-0/">release notes</a> are now available on <a href="https://open-paas.org/"><strong>our website</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8bsenohNJjRIvCOuhILlSw.jpeg" /></figure><p>Speaking of which, in coordination with our in-house<strong> </strong><a href="https://linda.digital/"><strong>digital agency</strong></a>, a <a href="https://open-paas.org/"><strong>new website</strong></a> has been created, which will be easier to modify and will allow faster iterations. Please tell us in the comment section what you think of it!</p><p>OpenPaaS is a collaborative platform made out of many elements, software and technologies. It provides businesses more than the sum of its parts. But what does parts are? As you probably already know, LinShare, a standalone solution, is now integrated into OpenPaaS, as a module.</p><p>What does LinShare do, where it comes from and how can it help your business?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*JfDa9ZZAIqfsIaXy0cfOBQ.png" /><figcaption>File sharing made easy</figcaption></figure><h3>History</h3><p><strong>LinShare is an easy-to-use file sharing server</strong> that does what it names entails: it allows the sharing of large files across networks using a simple web application, which is especially useful when those files are too big to be attached to emails, or when you want to share information with external correspondents. <strong>Traceability</strong>, through auditing and monitoring, is paramount to this solution, which makes it a perfect fit for any business or institutional environments. Just like OpenPaaS, this Open Source solution is proudly maintained by <a href="https://linagora.com/"><strong>LINAGORA</strong></a>.</p><p>That sounds great, but where does LinShare come from?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/287/1*tXl82WlyGYCzHPh0SuSEXg.png" /><figcaption>LinShare’s first customer</figcaption></figure><p>Perhaps like every great applications out there, LinShare was created as an answer to a demonstrable need expressed by an identified customer, in this case the <a href="https://en.wikipedia.org/wiki/Inserm">French National Institute of Health and Medical Research</a> (INSERM). In 2008, the said institute wanted to adopt a new application to securely share large files. LINAGORA successfully won the call for bids and started just thereafter to develop a solution from scratch. After only one year of intense development, LinShare 0.6 was released in 2009 and published under an Open Source license.</p><p>Three years after, in 2012, the software hit version 1.0.0. This version introduced many functionalities: <strong>shared folders</strong>, allowing multiple files to be shared at once<strong>; file request</strong>, to let an external contact upload files in a dedicated space.</p><p>A few years after, in 2017, <strong>LinShare 2.0</strong> was released. The user interface has been entirely revamped to match more closely current trends: <strong>a brand new interface </strong>has been shaped from the ground-up, which allows users to access files from any devices, in a responsive way.</p><p>Together with version 2.1, those are some of the features that were introduced:<strong> </strong>an<strong> upload queue</strong>, to let you upload multiple files in a sequence; the <strong>preview ability</strong>, to see what the content of a file looks like before you download it; a <strong>personal space</strong>, to offer you a dedicated space for your own personal files; support for <a href="https://wiki.openstack.org/wiki/Swift">OpenStack Swift</a>, to leverage this public cloud’s service; <strong>guest accounts support</strong>, to let administrators create accounts for guest users; and finally, a <strong>personal activity log</strong>, to get a fully detailed view of all your past activities.</p><h3>Present-day time</h3><p>Just a few weeks ago, at the beginning of October this month, LinShare reached version 2.2, adding a few pages in its already impressive <a href="https://github.com/linagora/linshare/blob/master/CHANGELOG.md">changelog</a>.</p><p><a href="https://www.adnovum.ch/"><strong>AdNovum</strong></a>, a Swiss company working in High-End and Security Engineering, funded some of those changes, which are now available for everyone using LinShare. Without further due, let’s introduce those features:</p><ul><li><strong>Theming</strong>. Now, you can personalize LinShare, so that it matches more closely your company’s corporate identity. There is more information <a href="https://github.com/linagora/linshare/blob/master/documentation/EN/configuration/setting_the_theme_for_linshare.md">here</a> and even a guide for <a href="https://github.com/linagora/linshare/blob/master/documentation/EN/development/linshare-ui-user/creating_a_theme_for_linshare.md">creating your own theme</a> there.</li><li><strong>A new role. </strong>Now, there is a new role, the contributor, siting between the reader and the writer. Writer’s privileges have been revamped. In sum, more granularity have been added when it comes to permission. More information is available <a href="https://github.com/linagora/linshare/blob/master/documentation/EN/user/linshare-user.md#4-shared-spaces">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyjFB4kKcxyYeuRxGBXFbg.png" /></figure><ul><li><strong>Group synchronization with LDAP. </strong>Groups created in an LDAP directory will be automatically synchronized with LinShare. Further information can be found <a href="https://github.com/linagora/linshare/blob/master/documentation/EN/configuration/configure_ldap_synchronization.md">there</a>.</li><li><strong>JSON Web Token (JWT)</strong> <strong>authentication. </strong>Thanks to JWT<strong>, </strong>a backend feature, server-to-server authentication will be made more simple! Do you want to use it yourself? If so, head over to <a href="https://github.com/linagora/linshare/blob/master/documentation/EN/configuration/how-to-use-jwt.md">the documentation</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QlZ1Ra3OctrKEdA9" /><figcaption>LinShare’s theme can now be personalized, thanks to version 2.2!</figcaption></figure><h3>The future</h3><p>Wouldn’t it be nice to have <strong>file versionning</strong> in LinShare, so that you could keep a complete history of any file, and roll back in case a mistake was done? Or to be able to create a set that would include many shared folders, so that you could better mimic how a company is organized, and let information be shared more easily?</p><p>File versionning and bigger organizational units are big features the LinShare team is actually working on.</p><p>That’s about it! We hope you have enjoyed reading this newsletter!</p><p>Keep in touch with <strong>OpenPaaS</strong> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub,</a> and our dedicated <a href="https://forum.open-paas.org/">Forum</a>. For LinShare, follow its <a href="https://twitter.com/LinShare_FOSS">Twitter</a> account.</p><p>Interested in joining <strong>LINAGORA</strong>? <a href="https://jobs.linagora.com/">We are hiring<em>!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3788021438a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-october-2018-3788021438a4">OpenPaaS’ Newsletter — October 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — September 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-september-2018-c7c846e66317?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7c846e66317</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[voice-assistant]]></category>
            <category><![CDATA[research-and-development]]></category>
            <category><![CDATA[mail]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Mon, 24 Sep 2018 09:01:02 GMT</pubDate>
            <atom:updated>2018-09-24T09:01:02.086Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>OpenPaaS’ Newsletter — September 2018</h3><h4>Aiming for the star</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JDO1nJaDpllIJ7rt-BwCMg.jpeg" /><figcaption>LINAGORA products illustrated as planets. The R&amp;D team has contributed to bootstrap some of those products, in particular OpenPaaS and LinTO.</figcaption></figure><h4>Exploring uncharted territories</h4><p>Just like a small solar system, <a href="https://linagora.com/">LINAGORA</a> is made out of multiple independent entities that are all revolving around the sun. For us, those astronomical objects represent <a href="https://medium.com/linagora-engineering/openpaas-newsletter-july-2018-e24419ce4e0e">products</a> such as <a href="https://open-paas.org/">OpenPaaS</a> or <a href="http://www.linshare.org/en/">LinShare</a>, or company offices located in a handful of countries including France, Vietnam, Canada and Tunisia.</p><p>In this analogy, the sun illustrates the sense of purpose within the company, perhaps most importantly the support for free software — for which we all thrive — and which is illuminating the path so that we can go further, both individually and collectively.</p><p>Just as in outer space with the <a href="https://en.wikipedia.org/wiki/Voyager_program">Voyager space probes</a>, explorers are needed when it comes to discovering new planets, building new systems and helping us to better comprehend reality.</p><p>Members of the Research and development (R&amp;D) team, which are part of the LINAGORA Lab, are not unlike those explorers. Their research is used to nurture in-house software products like OpenPaaS, our open source collaborative platform.</p><p>This newsletter will be dedicated to showcase some of their most recent results, and will give us a glimpse into what is coming next for OpenPaaS when it comes to email processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*q-QMKQjTVLYOc3DyMPe9sw.png" /></figure><h4>Research fuels development</h4><p>The <a href="https://research.linagora.com/">LINAGORA Lab</a>, based in Toulouse, is working closely with universities, contributing to lead researches on topics ranging from cloud computing to voice processing. Within LINAGORA, those innovations are used to propel our products.</p><p>Take OpenPaaS for instance. As explained by Michael Bailly during <a href="https://medium.com/linagora-engineering/behind-the-software-lie-the-humans-40541dd53b1">his interview</a>, OpenPaaS started as a research project, originally called OpenPaaS:NG, for “New Generation”. This research project has contributed to laid the foundations for what would later become the integrated platform of today.</p><p><a href="https://medium.com/linagora-engineering/behind-the-software-lie-the-humans-40541dd53b1">Behind the software lie the humans</a></p><p>More recently, in April this year, LinTO has officially started as a research project: the new generation of open source smart assistant will receive three years worth of public funding.</p><p>If you wish to learn more about LinTO, please have a look at this <a href="https://medium.com/linagora-engineering/openpaas-newsletter-april-2018-888482f0e08e">previous article</a> (also, I have heard that another article was planned on that matter. Stay tuned on the company-wide <a href="https://twitter.com/linagora">social account</a> to stay posted).</p><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-april-2018-888482f0e08e">OpenPaaS’ Newsletter — April 2018</a></p><h4>Mail overload as a modern-day society problem</h4><p>Answering emails takes a toll on productivity. Often, just a simple answer could suffice, but writing it might become tedious overtime, especially if the process has to be repeated more than a dozen time per day, such as when you seek the best time for an appointment.</p><p>That is a good news… at least for software engineers, as they are always looking for clever ways to automate repetitive tasks. How can we use intent detection to select emails that require a reply and pre-write a pertinent answer for those? Manon, which recently worked for LINAGORA Labs to complete her master thesis in linguistics, took part to the development of a OpenPaaS feature to do that. The approach, the tool and some interesting results are presented in the following medium article.</p><p><a href="https://medium.com/linagoralabs/ontology-based-meeting-intents-detection-for-automatic-email-answering-7990e4a1e22">Ontology-based Meeting Intents Detection for Automatic Email Answering</a></p><p>The main takeaway?</p><blockquote>Our tool is able <strong>to analyze incoming emails and decide which one requires a response </strong>and then<strong> retrieve relevant items to be able to generate an adequate answer.</strong></blockquote><p>What do they would like to do in the future?</p><blockquote>We are planning to <strong>link the answering mechanism to the OpenPaaS calendar to automatically check availability and generate answers depending on the user’s constraints</strong>. We also plan to detect and answer to other intents as administrative workflows […]</blockquote><h4>How can computer better recognize the human voice?</h4><p>How can we, as humans, recognize a voice in a noisy environment? How is our brain able to tell apart background noises from significant and meaningful sounds? More importantly for us, how can we transfer this ability to computers?</p><p>Voice processing is one of the problem <a href="https://en.wikipedia.org/wiki/Computational_linguistics">computational linguistics</a> tries to tackle. But before voice can be processed, it needs to be detected. Voice activity detection (VAD) represents the ability for a computer to detect the human voice among other noises. How can a machine do the same?</p><p>Please read article by Rudy Baraglia to learn more about it, starting from the basics.</p><p><a href="https://medium.com/linagoralabs/voice-activity-detection-for-voice-user-interface-2d4bb5600ee3">Voice Activity Detection for Voice User Interface.</a></p><h4>Conclusion</h4><p>We hope you have enjoyed reading this newsletter. If you do, do not hesitate to leave a comment in the section bellow.</p><p>Please keep in touch with <a href="https://open-paas.org/">OpenPaaS</a> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora">GitHub</a>.</p><p>Interested in joining LINAGORA?<strong> </strong><a href="https://job.linagora.com/"><strong>We are hiring</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7c846e66317" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-september-2018-c7c846e66317">OpenPaaS’ Newsletter — September 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is hardware the black hole of computing ?]]></title>
            <link>https://medium.com/linagora-engineering/is-hardware-the-black-hole-of-computing-4bd07f749129?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bd07f749129</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[open-hardware]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[free-software]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Fri, 14 Sep 2018 13:26:22 GMT</pubDate>
            <atom:updated>2018-09-14T13:30:05.848Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Part II: shedding light on the darkness</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*pcG0YxCl3u4ZjK4x" /><figcaption>Hardware: irreducible complexity. Photo by <a href="https://unsplash.com/photos/FO7JIlwjOtU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alexandre Debiève</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>The problem</h3><p>As stated in the <a href="https://medium.com/linagora-engineering/https-medium-com-linagora-engineering-is-hardware-the-black-hole-of-computing-bdb9977ed5a8"><strong>part 1 of this article</strong></a>, hardware is indeed the black hole of computing today. Unsurprisingly, it is even <a href="https://blog.invisiblethings.org/2015/10/27/x86_harmful.html">considered harmful</a> by some. The problem can be summarized in these words:</p><pre><strong><em>The fundamental building block of any computing system, the hardware, is also the least trustworthy. </em></strong></pre><pre><strong><em>If hardware cannot be trusted, neither can software.</em></strong></pre><pre><strong><em>Thus, software, which supervenes hardware, is unavoidably weakened and irremediably contaminated.</em></strong></pre><p>What can be done to change this situation? <strong>How can hardware be made more trustworthy</strong>? There are at least two angles to approach the problem:</p><ul><li><strong>Political answers, </strong>which include market or product regulations, dedicated public policies, increased pressure on silicon vendors, etc.</li><li><strong>Technical answers</strong>, which propose ways to mitigate risks in the short-term and offer new ways to build hardware and firmware in the long-term. Risk mitigation is the focus of this current article.</li></ul><p><em>Thanks to LINAGORA, </em><a href="https://job.linagora.com/offres/"><em>which is currently looking for new talent</em></a><em>, for its support and for making this article possible! This opinion piece doesn’t necessarily reflect my employer’s stance on the subject.</em></p><h3>Taming the firmware</h3><p>Closed source components, such as the <a href="https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface">Unified Extensible Firmware Interface</a> (UEFI), the <a href="https://en.wikipedia.org/wiki/System_Management_Mode">System Management Mode</a> (SMM), the <a href="https://en.wikipedia.org/wiki/Intel_Active_Management_Technology">Intel Management Engine</a> (Intel ME) and the <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">AMD Secure Technology</a>, are tightly integrated with the hardware.</p><p>They need to be pruned, and whenever possible, completely removed and replaced with open source alternatives. This is not as easy as a shell command.</p><pre>sudo apt purge UEFI SMM IntelME </pre><pre>E: Unable to locate package UEFI<br>E: Unable to locate package SMM<br>E: Unable to locate package IntelME</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*aPCX_EY40fuUrRCQAaLdCg.png" /><figcaption>The UEFI logo by Mouagip <a href="https://commons.wikimedia.org/w/index.php?curid=10985103">(Public Domain</a>)</figcaption></figure><h4>The UEFI</h4><p>Before we look at ways to neutralize the Unified Extensible Firmware Interface (UEFI), let’s define it. As <a href="https://lwn.net/Articles/748586/">explained</a> by J.B. Crawford, a UEFI computer boots in four phases:</p><blockquote>The security phase (SEC) and the Pre-EFI Initialization Stage (PEI) are responsible for low-level operations to prepare the hardware and are usually specific to the hardware they are implemented for. After these two stages, the Driver Execution Environment (DXE) loads various drivers, and then the Boot Device Select (BDS) phase can begin.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*csZNH4sSJFro8vbUmKc2Wg.png" /><figcaption>You can spot the System Management Mode (SMM) in the bottom-right corner. Contrary to the UEFI, it stays active after the boot process is complete. <a href="https://www.tianocore.org/">TianoCore</a> is an open source implementation of the UEFI maintained by Intel, but is unavailable on bare-metal hardware. <a href="https://www.seabios.org/SeaBIOS">SeaBIOS</a> is an open implementation of the BIOS. (Illustration is borrowed <a href="https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-147.pdf">from BIOS Protection Guidelines</a>. © National Institute of Standards and Technology)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*3cHX2Qzt2kJUdsx9cbpV8A.png" /><figcaption>The Coreboot logo by <a href="https://coreboot.org/about.html">Coreboot</a>.</figcaption></figure><h4>Silencing the UEFI and the SMM</h4><p>What are the primary solutions available today to make the early stages of the boot process, the so-called SEC and PEI stages, more flexible and trustworthy?</p><p><a href="https://coreboot.org/"><strong>Coreboot</strong></a>, alas not entirely free but deployed on a vast number of hardware — including almost all <a href="http://Chrome OS">Chrome OS</a> devices — and <a href="https://libreboot.org/"><strong>Libreboot</strong></a>, entirely free but available only on a limited number of very old <a href="https://libreboot.org/docs/hardware/">hardware platforms</a>, represent two of the best options.</p><p>Coreboot has <a href="https://coreboot.org/users.html">many advantages</a> over UEFI, including faster boot time and more flexibility.</p><p>The process of installing Coreboot requires flashing the actual motherboard with a new firmware, something that is both non-trivial and hardware-specific.</p><p>Fortunately, this service is <a href="https://tehnoetic.com/laptops/tet-lis">offered</a> by third parties, at least when it comes to Libreboot. Some hardware vendors like <a href="https://puri.sm/">Purism</a> offer newer computers with Coreboot pre-installed.</p><p>Unfortunately, as of now, the System Management Mode (SMM) cannot be easily removed or replaced and has been included into Coreboot, as it is needed by laptops. However, there are attempts to move it <a href="https://www.youtube.com/watch?v=6GEaw4msq6g">into the kernel</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*2Btm5SJ2xVkavfs4O1COfQ.png" /><figcaption>The LinuxBoot logo by <a href="https://dribbble.com/LittleSue">Susanne Nähler</a> from <a href="https://9elements.com/">9elements</a> (<a href="https://www.linuxboot.org/page/artwork/">CC BY ND 4.0</a>)</figcaption></figure><h4>Linux under Linux</h4><p>Coreboot and Libreboot require a payload to continue the boot process and to load specific drivers. In other words, how do we deal with the so-called DXE and BDS stages in the UEFI boot?</p><p>What piece of software is open, flexible and compatible with a wide range of hardware?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*7uopS5H77U2jQnI9gTuo8w.png" /></figure><p>Originally called NERF (for Non-Extensible Reduced Firmware — a pun directed at the Unified Extensible Firmware Interface (UEFI)), <a href="https://www.linuxboot.org/"><strong>LinuxBoot</strong></a><strong>’</strong>s intent is to replace the aforementioned DXE and BDS stages by — you guessed it — a Linux kernel and an initial ram file system file (initramfs). The initramfs are used to load the root file system in the memory.</p><p>Still in its infancy, LinuxBoot is intended for server hardware, with the notable exception of Heads (check out <a href="http://osresearch.net/Installing-Heads">this great guide</a> by Trammel Hudson on how to install Heads on a Laptop, or <a href="https://trmm.net/LinuxBoot_34c3">this transcript</a> of his presentation on <a href="https://trmm.net/LinuxBoot_34c3">LinuxBoot</a> at the Chaos Communication Congress in 2017.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/0*G-bC1gAPubuRLke1.png" /><figcaption>Where LinuxBoot fits in. LinuxBoot is agnostic,and supports several different initramfs. (© LinuxBoot.org)</figcaption></figure><p>With LinuxBoot, Linux takes care of booting Linux. With Coreboot, hardware initialization is more transparent than with the original firmware. (<a href="https://phoronix.com/scan.php?page=news_item&amp;px=Intel-Better-FSP-License">Intel recently made the Firmware Support Package</a> (FSP) license easier to read and to comply with. These open firmware, LinuxBoot and Coreboot, rely on the FSP and are likely to be ported on more hardware thanks to the re-licensing.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*RLelktjuyEDegou-Zp3CJw.jpeg" /><figcaption>Rocky Raccoon, MINIX’s mascot. (<a href="http://www.minix3.org/">MINIX</a><a href="https://creativecommons.org/licenses/by-sa/4.0">, CC BY-SA 4.0</a>)</figcaption></figure><h4>Targeting the Intel ME</h4><p>What about <a href="https://en.wikipedia.org/wiki/MINIX_3">MINIX</a>, the operating system lurking under Linux inside the Intel ME?</p><p>It appears that a <a href="https://www.theregister.co.uk/2017/08/29/intel_management_engine_can_be_disabled/">kill switch exists</a>, and that is had been put in place to comply with stringent security environments, in particular the NSA High Assurance Platform (HAP).</p><p>A Python script aptly named <a href="https://github.com/corna/me_cleaner"><strong>me_cleaner</strong></a> is leveraging this possibility, and can be used to deactivate most of the Intel ME.</p><h4>Update your peripheral firmware</h4><p>On Linux, or really any platform for that matter, it is often difficult to patch the firmware located in your hard disk, your Bluetooth dongle and other peripherals.</p><p>An initiative by Richard Hughes named the <a href="https://fwupd.org/">Linux Vendor Firmware Service</a> (LVFS) offers a dedicated software called <strong>fwupd</strong> which allows Linux users to patch some of the firmware attached to their machine. It offers a place for vendors to send their updated firmware so they can be easily consumed by end-users through the fwupd software. On top of that, the project <a href="https://fwupd.org/vendorlist">lists vendors</a> that are willing to send updated firmware, alongside those that aren’t.</p><h3>The need for starting from scratch</h3><p>Current attempts to fix firmware are akin to patching a software in production sold by a monopoly which you have to use but cannot know about. This problem should not exist in the first place, and even though it does:</p><blockquote><strong>it is not up to customers to fix faulty products.</strong></blockquote><p>Common and widely available hardware are flawed beyond repair.</p><p>There is a need to build more open platforms from the get-go. How can we go further?</p><p><em>How about building open hardware…</em></p><p>Incidentally, the <a href="https://osfc.io/"><strong>Open Source Firmware Conference</strong></a> (OSFC) is currently happening in Erlangen, Germany. Have a look at <a href="https://osfc.io/schedule">their program</a> to see what is being done now by whom. Hopefully, they will publish transcripts or video recordings of their conferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n4iz5Xt8x7w83lx4.jpg" /><figcaption>What it takes to make your hardware freer. At the very least one Club Mate. (<a href="http://osresearch.net/Installing-Heads">Photo</a> © Trammel Hudson)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bd07f749129" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/is-hardware-the-black-hole-of-computing-4bd07f749129">Is hardware the black hole of computing ?</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is hardware the black hole of computing ?]]></title>
            <link>https://medium.com/linagora-engineering/https-medium-com-linagora-engineering-is-hardware-the-black-hole-of-computing-bdb9977ed5a8?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdb9977ed5a8</guid>
            <category><![CDATA[open-hardware]]></category>
            <category><![CDATA[free-software]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[firmware]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 12:31:01 GMT</pubDate>
            <atom:updated>2018-09-14T13:29:41.179Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4><strong>Part I : a descent into the abyss</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tYyk0P-LFifUafjnA188ug.png" /><figcaption>An illustration of a black hole, used as a metaphor for today’s hardware, alongside dazzling points of lights, which can be associated to free and open source software. (© Alain r, <a href="https://creativecommons.org/licenses/by-sa/2.5/">CC BY-SA 2.5</a>)</figcaption></figure><blockquote><a href="https://medium.com/linagora-engineering/is-hardware-the-black-hole-of-computing-4bd07f749129"><strong>The second part of the article has been released!</strong></a></blockquote><h4>Introduction</h4><p>Let’s face it, amid revelations of hardware-level vulnerabilities such as <a href="https://meltdownattack.com/">Meltdown and Spectre</a>,<strong> </strong>deploying software in today’s world looks a lot like shooting stars next to a black hole: very entertaining and deeply unsustainable. Why? Because <strong>computer hardware is sick</strong>. The layer on top of which every information system on earth is built is flawed, perhaps beyond salvation. Are we doomed? No, some glimpses of hope can be seen on the horizon: it may even be a good time to wage a fight to take the power back at the most fundamental level, and to start building a truly open information ecosystem, from top to bottom. Shall we ?</p><p>There are few places on the surface of the earth that haven’t been trod on by a human foot, explored and carefully mapped. However, below the surface, whether underground or undersea, it is a different story: there still lurks darkness and ignorance, oblivious to our attempts to shed lights on this no-man’s Underland.</p><p>In that regard, <strong>computing devices are no different from Earth</strong>. On the surface, at the level of the operating system, we can and have studied software, thanks to free and open operating systems such as Linux. But <strong>what runs beneath the operating system, before it takes control over the hardware, remains largely a mystery</strong>. Why is that the case? Why is the hardware such a black box nowadays, and why does it matter?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaLv7l6_p6Lnqo0MDkXhLQ.png" /><figcaption>There is more than what meets the eye. (The earth is adapted from © Hawk-Eye, <a href="https://creativecommons.org/licenses/by-sa/3.0/">CC BY-SA 3.0</a>; The Tux mascot was made by © Larry Ewing and GIMP; the rest is in Public Domain)</figcaption></figure><p><strong>This two-part article will explore what lies beneath the software you run every day,</strong> and make a case for moving to a radically more transparent planet, where artificial barriers to our understanding of reality are not shamelessly erected by hardware oligopolies and manufacturers.</p><p>In this part, we are going to describe some problems that hardware suffer from, with a special focus on the traditional <a href="https://en.wikipedia.org/wiki/X86">x86 architecture</a>, notably prevalent in the server and desktop computing markets. In the second part, we will illustrate some solutions, both short and long term. We will showcase hardware hackers that are cracking open the surface of the planet, to make apparent what was once invisible and give the control back to the user, where it should have remained.</p><p><em>Thanks to LINAGORA, </em><a href="https://job.linagora.com/offres/"><em>which is currently looking for new talent</em></a><em>, for its support and for making this article possible! This opinion piece doesn’t necessarily reflect my employer’s stance on the subject.</em></p><h4><strong>Could you please draw me a computer?</strong></h4><p>A computing device is usually made from three distinct elements:</p><ol><li><strong>The hardware</strong>: it is the physical part of a computer, the foundations on top of which the software runs. It is composed of a central processing unit (CPU), some persistent and non-persistent memory, and a motherboard to hold everything together. The hardware is not made to change, hence the suffix “<strong>hard</strong>”. Examples: the <a href="https://en.wikipedia.org/wiki/ARM_architecture">ARM architecture</a>, used mostly in mobile phones and embedded devices, and the <a href="https://en.wikipedia.org/wiki/X86">x86 architecture</a>, largely used in desktop and server computers.</li><li><strong>The firmware</strong>: it is a read-only file-system which acts as an intermediary between the hardware and the software layer. It is often located on the motherboard itself. It can be modified under certain conditions, but not as easily as the software, hence the suffix “<strong>firm</strong>”. Computer parts such as solid state drives (SSDs) are also equipped with firmwares. Examples: The <a href="https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface">Unified Extensible Firmware Interface</a> (UEFI); the <a href="https://en.wikipedia.org/wiki/BIOS">Basic Input/Output System</a> (BIOS), which the UEFI supersedes.</li><li><strong>The software</strong>: it is the operating system that ultimately manages the hardware and allocates resources to other software, so they can work properly. The software part of a computer can be modified and reprogrammed easily, hence the term “<strong>soft</strong>”. Example: Linux; Windows; macOS.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*8lJpwOhAq0WFKwutRmBZGQ.png" /><figcaption>The (U)EFI in the stack. In this article, we conflate the firmware and the (U)EFI. This schema is more prevalent among the x86 computer architecture than in the ARM ecosystem which is more fragmented and diverse. (Public Domain)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/0*Nh6jujr55xkBuF_9.jpg" /><figcaption>Not a smart watch, just good ol’ plain hardware.(Public Domain)</figcaption></figure><h4><strong>Fairytales in software Wonderland</strong></h4><p>In an ideal situation, when you buy a computer or a smartphone, it would run <strong>a free operating system with complete and transparent control over the hardware</strong>. It would be complete in the sense that no hardware components could escape the authority of the operating system; it would be transparent in the sense that the operating system could explore processes and devices attached to it, down to the firmware level. For the software to be able to truly control the hardware and the firmware, those elements would need to be open too, in order to be scrutinized and eventually trusted.</p><p>One of the key benefits of an open platform would be to allow the creation of a chain of trust, whose root would ultimately reside in the user’s hands. In other words, such a platform would give the control back to the user. An open platform would also allow more bugs to be discovered and corrected: “<a href="https://en.wikipedia.org/wiki/Linus%27s_Law">given enough eyeballs, all bugs are shallow</a>”, is a claim about software development called the Linus’s Law.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/0*jqOd4-_KCdvsg2c5.png" /><figcaption>This ghost is going to hit you with its stick for the foreseeable future. (Public Domain)</figcaption></figure><h4><strong>Spoiler alert: what you buy is not what you get</strong></h4><p>In today’s world, the situation is grim, at the exact opposite of the ideal scenario just described: <strong>hardware has gone wild</strong>. Computing devices have grown into full-blown deceiving machines, and are ridden with silicon-level bugs as illustrated by the ongoing <a href="https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)">Meltdown</a> and <a href="https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)">Spectre</a> fiascoes. Is that really surprising?</p><p><strong>Throughout the years, extra layers of complexity have been added at a firmware level, to the point that your surface-level operating system has lost control of the hardware.</strong></p><p><a href="https://schd.ws/hosted_files/osseu17/84/Replace%20UEFI%20with%20Linux.pdf">According to a conservative estimate</a> [PDF], on a typical x86 laptop such as the Ubuntu-powered HP ProBook 430 G4 that I currently use, there are 2½ operating systems or kernels running between the hardware and the surface-level operating system: <strong>this amounts to millions of lines of code you have no choice but to blindly trust. </strong>Those lurking operating systems are not only out of reach of the surface-level operating system, they also run with more privileges. On top of that, they are bloated, difficult if not impossible to patch or deactivate, and rely on security by obscurity. <strong><em>What could go wrong?</em></strong><em> </em>Before we answer this question and uncover those hidden systems, the notion of ring of protection needs to be introduced.</p><h4>Rings of death</h4><p>A traditional operating system has several protection rings, with various levels of privilege. The kernel’s code or processes are being executed in Ring 0, the most privileged ring of all. User applications, such as internet browsers and word processors, run in Ring 3, and are the least privileged. Device drivers, such as your graphic card driver, require a deeper access to the hardware, and therefore are located in-between, in Ring 2 and Ring 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*pIfYJjJ7HSA43OR772IMXQ.png" /><figcaption>As many rings as you want. (© Hertzsprung at English Wikipedia, <a href="http://www.gnu.org/copyleft/fdl.html">GFDL</a>, <a href="https://creativecommons.org/licenses/by-sa/3.0/">CC-BY-SA-3.0</a>)</figcaption></figure><p>There is more to it.<strong> Negative rings also exist. </strong>At Ring -1, you would typically find a <a href="https://en.wikipedia.org/wiki/Hypervisor">Type-1 hypervisor</a>, such as Xen. <a href="https://www.qubes-os.org/">QubesOS</a>, a desktop-operating system geared towards security-minded people, relies on this. These kinds of virtual machine managers— often simply called hosts in this context — have greater privileges than the guest operating systems they maintain. This is a precondition to enforce isolation between guests, and prevent them from spying on each other.</p><p>On a side note, at the exception of Azure, each major public cloud provider is either relying on Xen (Amazon Web Service) or <a href="https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine">KVM</a> (Google Compute Engine; Alibaba Cloud; OVH; and more recently Amazon Web Service too): both are open source. <strong>Up until Ring -1, there is no controversy, as the code running here can be open.</strong></p><h4>Going down the rabbit hole</h4><p>You have probably guessed it by now, but the so-called lurking and closed operating systems that were mentioned before are running below the Ring 0 and even -1, with higher privileges than the kernel and the hypervisor. We have already named one of these operating system or kernel: it is the <strong>Unified Extensible Firmware Interface (UEFI</strong>). What does it do? It is responsible for initializing and checking the hardware at boot-time so it can be used by your surface-level operating system. Among other things, the <strong>UEFI runs at Ring -2</strong>, has network capabilities and can run full blown applications, including the legacy BIOS, the EFI version of <a href="https://en.wikipedia.org/wiki/GNU_GRUB">GNU GRand Unified Bootloader</a> (GRUB), and of course <a href="https://conference.hitb.org/hitbsecconf2015ams/sessions/how-many-million-bioses-would-you-like-to-infect/">malware that will persist across operating system re-installation</a>, while remaining invisible to every antivirus software available on the market. Some of its code is hardware-dependent and varies from one machine to another and some of it isn’t, but almost everything is closed-source, with notable exceptions that we will cover in the second part of this article. Although we have found the first operating system: there is 1½ kernels to go.</p><p>At the same level of privilege as the UEFI resides<strong> the </strong><a href="https://en.wikipedia.org/wiki/System_Management_Mode"><strong>System Management Mode</strong></a><strong> (SMM), a special CPU mode which is notably responsible for some power management </strong>— such as when you close your laptop’s lid — as well as some hardware monitoring. By design, it cannot be removed or disabled and has been in the past targeted by so-called <a href="https://www.schneier.com/blog/archives/2014/01/souffletrough_n.html">NSA’s software implants</a>, which gave the agency persistent and covert access to infected systems. There goes ½ a kernel. Is that all? No, we are about to reach the darkest corner of the Intel x86 platform.</p><h4>A computer inside your computer</h4><p>Let’s go back in time. In the early nineties, Andrew Tannenbaum — Linus Torvalds’ former computer science professor — <a href="https://en.wikipedia.org/wiki/Tanenbaum%E2%80%93Torvalds_debate">had an argument</a> over operating system design with his former pupil. <strong>Professor Tannenbaum was advocating for microkernel design, while Linus was defending a monolithic design. </strong>Linus remained unconvinced and continued the development of Linux — then only 1 year old — and it later became the most popular monolithic operating system in the world. However,<strong> has Tannenbaum and his microkernel-based approach really lost the battle?</strong> Without the unsolicited help of Intel, it would certainly have been the case…</p><p>Shipping in each of of Intel’s processor and chipsets since 2008, behold the <a href="https://en.wikipedia.org/wiki/Intel_Management_Engine">Intel Management Engine</a> (Intel ME), which provides management capabilities for IT departments, and runs at… Ring -3, owning the entire platform. Among other things, it has full access to the network stack. It the event of an operating system failure, its superset, the <a href="https://en.wikipedia.org/wiki/Intel_Active_Management_Technology">Intel Active Management Engine</a>, can be used to re-image a computer over the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hl6eEzWJFjNlrfGVJLAxYw.png" /><figcaption>Your typical intel-based x86 computer illustrated, or as many rings as you don’t want. In an ideal world, the kernel would be running at with the highest privileges, actually owning the hardware. But it appears that we are not living in the best possible world. In red, at the center of the platform, at the hearth of your computer, you will stumble across closed-source code.</figcaption></figure><p><strong>The Intel ME is quite literally a computer inside your computer. </strong>The most recent version is based on an Intel Quark CPU used in the embedded market, and <a href="http://blog.ptsecurity.com/2017/04/intel-me-way-of-static-analysis.html">until the year 2017</a>, nobody knew which operating system it was running, including the aforementioned public cloud operators — who are not exactly amateurs. Deep inside your computer, unbeknownst to your surface-level operating system, let me introduce <a href="https://en.wikipedia.org/wiki/MINIX_3">MINIX 3</a>, a microkernel operating system whose father is… Professor Tannenbaum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*6lUQOL0_UITuixqZ2wTX8Q.jpeg" /><figcaption>Meet Rocky Raccoon, MINIX’s mascot, lurking in your Intel computer since 2008. (<a href="http://www.minix3.org/">MINIX</a><a href="https://creativecommons.org/licenses/by-sa/4.0">, CC BY-SA 4.0</a>)</figcaption></figure><p>So, after twenty years, Professor Tannenbaum not only got his revenge but won by K.O. against Linus, although he had to wait <a href="https://www.cs.vu.nl/~ast/intel/">press reports</a> to learn the good news, as he didn’t know that Intel was using his creation (which doesn’t constitute a violation of the permissive license associated to MINIX, but would have been in the case of Linux). The result:<strong> MINIX 3 is running on hundreds of millions of machines</strong>, and became one of the most used operating system on earth overnight — and likely triggered some job openings for MINIX 3 specialists at the NSA and its counterparts around the world…</p><p>AMD, Intel’s historic competitor, has it own version of the Management Engine, called the <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">AMD Platform Security Processor</a> (PSP). It is powered by an ARM processor, and surprisingly, it appears to be doing <a href="https://arstechnica.com/information-technology/2018/03/a-raft-of-flaws-in-amd-chips-make-bad-hacks-much-much-worse/">the exact opposite of what its name entails</a>.</p><p>This pervasive problem extends to your everyday devices and peripheral as well. Take for instance hard disks drives, which are equipped with a CPU, a firmware and some non-trivial amount of random-access memory (RAM). Unsurprisingly, the NSA has also successfully targeted their firmwares, a technique that can be replicated <a href="https://motherboard.vice.com/en_us/article/ypwkwk/the-nsas-undetectable-hard-drive-hack-was-first-demonstrated-a-year-ago">by skilled hackers</a>.</p><p>What the NSA is capable of today is an indicator of what could be done by amateur groups in a decade or so, or even by your resentful tech-savvy ex-boyfriend or girlfriend. The problem is that even ten years from now, it is not clear how we will be able to protect against security vulnerabilities that are affecting the hardware layer. As a society, we are not ready, and aren’t preparing ourselves seriously enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*TpTRCZb13s23UW1XgDCFmg.png" /><figcaption>The IT industry-wide problem illustrated. Privileges given to any layer of the platform stack are inversely proportional to the layer’s openness. Hardware is as closed as it is privileged. As a result, any hardware bug has trickle-down effects, and therefore will affect the entire ecosystem, for years to come… Humanity is building a stronghold on top of moving sands.</figcaption></figure><h4>How did we get here?</h4><p>Until now, we have described some of the problems that exist in hardware today, and we have focused our attention on the x86 architecture. But <strong>what put us in this situation?</strong> Let’s list a few of the usual suspects:</p><ul><li>The<strong> lack of competition</strong> in the x86 market, which has been dominated by Intel for more than twenty years</li><li>The<strong> technical debt </strong>associated to the backward-compatible x86 architecture, which dates from the <a href="https://en.wikipedia.org/wiki/Intel_8086">late 70s</a></li><li>The almost irreducible difficulty associated with designing and shipping your own silicon, and the cost associated with it</li><li>The suspected overall mediocre quality of the software code written by hardware manufactures and Original Equipment Manufacturers (OEM)</li><li>The <strong>lack of technical documentation</strong> available (and when available, its legal protections) which make it unnecessarily difficult to study or modify any of the code below the surface-level operating system</li><li>The <strong>ongoing miniaturization process</strong>, which allows more components to be embedded in a platform without the user’s knowledge</li><li>The weak customer demand for an open computing platform</li><li>The difficulty of patching exploit-ridden firmware</li></ul><p>These are some of the possible reasons that led us to the present situation. Any successful solution to the problem will have to address some of these issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JeyAFMI3XMB1EJaAeHkBjQ.jpeg" /><figcaption>A personal view on computer hardware aptly illustrated. (Public Domain)</figcaption></figure><h4>Hardware : the root of the problem</h4><p>During the last decade, large amounts of software code has been freed or released under open source licenses. What was once the exception is becoming the rule. Although much remains to be done at the software-level, <strong>it is critical to direct some of our efforts to free the hardware</strong>, including the firmware, so we can be assured that the foundations on top of which we build software infrastructures are trustworthy enough to sustain increasingly critical workloads. <strong>Any open society which relies on information systems to function requires open computing</strong>.</p><p>As has been uncovered throughout the first part of this exploration, there is a lot of work to be done. Nowadays, any desktop or even mobile computing device is more like a set of loosely coupled elements which are all living a life of their own, untrustworthy and unaccountable. <strong>This situation is unacceptable</strong>.</p><p>We are required to use computing devices in our daily life, at work and also increasingly as citizens interacting with the state. To some extent, smartphones and personal computers can even be viewed <a href="https://www.researchgate.net/publication/272741099_The_brain_in_your_pocket_Evidence_that_Smartphones_are_used_to_supplant_thinking">as extensions of our minds</a> and could someday be granted <a href="https://aeon.co/ideas/are-you-just-inside-your-skin-or-is-your-smartphone-part-of-you">the same protections.</a> However, these devices are flawed by design. <strong>What would life be like if we could not trust our own brains? </strong>Nobody should be forced to rely on a fundamentally flawed and untrustworthy machine as vessel for their life.</p><p><strong>How can we restore some sanity in the computing world?</strong></p><p>In the second part of this article [<a href="https://medium.com/linagora-engineering/is-hardware-the-black-hole-of-computing-4bd07f749129">now available here</a>], due for next Thursday, we will showcase some available techniques to better mitigate the risks and recover some autonomy, and we will also illustrate longer term solutions. Stay tuned and don’t throw away your computer (yet).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdb9977ed5a8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/https-medium-com-linagora-engineering-is-hardware-the-black-hole-of-computing-bdb9977ed5a8">Is hardware the black hole of computing ?</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — August 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-august-2018-4dc837adfa67?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dc837adfa67</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[video-editing]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 09:46:33 GMT</pubDate>
            <atom:updated>2018-08-28T09:46:33.554Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>A focus on side-projects</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gc-oHt0IVmz8keXfI0xu3g.png" /><figcaption>Photo by <a href="https://unsplash.com/photos/oqStl2L5oxI?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clark Tibbs</a> on <a href="https://unsplash.com/search/photos/to-do?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Introduction</h4><p><a href="https://open-paas.org/"><strong>OpenPaaS</strong></a>’ developers and more generally <a href="https://linagora.com/"><strong>LINAGORA</strong></a>’s employees are passionate and committed: they are working hard to ship better software, to exceed customer’s expectations and to seek new markets so that open source services and products can thrive.</p><p>This commitment does not only manifest throughout their job but also sometimes during their free time. It is the purpose of this newsletter to showcase some <strong>side-projects </strong>our team members and employees are involved in.</p><h4>Making movies with Walid</h4><p>Let’s start with <strong>Walid</strong>, a web developer who has joined the LinShare team a couple of months ago, after a successful training with <a href="https://openhackademy.com/"><strong>OpenHackademy</strong></a>, LINAGORA’s initiative to help individuals acquire critical skills in information technology (Note: <a href="http://www.linshare.org/en/"><strong>LinShare</strong></a> is LINAGORA’s secure file sharing solution). When Walid is not hacking into JavaScript and <a href="https://vuejs.org/">VueJS</a>—his favorite framework so far — you could surely stumble across him<strong> filming and doing video montage</strong>,<strong> </strong>one of his other passion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*kT8dlOF_vZnKlgWBfyI7Dg.png" /><figcaption>© Keep Smile</figcaption></figure><p>His favorite playfield? His hometown of Aulnay-sous-bois, a northeastern neighborhood of Paris located at around fifteen kilometers of the capital, where <strong>Keep Smile </strong>is born in 2015 — an association dedicated to teaching the art of filming, especially to local inhabitants — and which Walid joined in 2016. With eight members in the crew, with skills such as acting, photography, communication and video editing, they are trying to spread their passion, and successfully so, as they are about to organize the second edition of the <a href="https://www.facebook.com/hallnaywood/photos/a.160079501354600/220796901949526/?type=3&amp;theater"><strong>Festival Hallnaywood</strong></a>, dedicated to short-movies, and which will take place <strong>September the 1st</strong>. Let wish them good success!</p><h4><strong>Resurrecting electronics with Alexandre</strong></h4><blockquote>Darned it, that TV remote control’s led is not blinking anymore! What if I try to fix it rather than to throw it away?</blockquote><p>According to Alexandre, support engineer for <a href="https://obm.org/"><strong>OBM</strong></a> — Open-PaaS’ predecessor—this decade-old event is the tipping point when<strong> his interest in electronics grew up to become a passion</strong>. He has then studied high-current electronics, but would ultimately focus on low-current electronics, as shown by the home-based smartphone repair shop he had once set up on his desk and used to ran after school.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7hmC6idmgyC-IGVESmt2Q.jpeg" /><figcaption>Alexandre’s video game arcade cabinet. (© Alexandre)</figcaption></figure><p>His operation scaled up when he moved to a shared-flat and got more space. Here, his focus turned to two side-projects, both built around the now iconic <a href="https://www.raspberrypi.org/">Raspberry Pi</a> computer. The first project was about <strong>home automation</strong>, and its goal was to allow the remote control of infrared-aware electrical switches via a web-server and some PHP codes; the other was about <strong>retro-gaming</strong>, and it consisted in building a <strong>video game arcade cabinet </strong>from scratch, powered by <a href="https://retropie.org.uk/">RetroPie</a>, a popular cross-console and open source video game emulator. For the latter, he had to practice carpentry, a skill his grand-father taught him when he was a kid. Alexandre is now about to finish his first arcade and to start building a second one; he will also begin to restore a vintage radio and will power it with <a href="https://volumio.org/project/">Volumio</a>, an open source audiophile music player.</p><p>Sorry, he no longer accept orders. And yes, he got the TV remote control fixed.</p><h4>How to make a lot of honey with Kevin</h4><p>At the beginning of spring this year, when flowers started to blossom, Kevin — full stack software engineer working on LinShare — joined <a href="https://www.happyculteur.co/"><strong>Happyculteur</strong></a>, a non-profit dedicated to<strong> raising awareness around bees</strong>, honey and their habitat in the Ile-de-France region. To achieve their intended goal, Happyculteur organizes beekeeper trainings and initiations, and help individuals install and maintain beehives, inside and outside of Paris.</p><p>How to help like-minded people better discover each other? Thanks to Kevin, the twelves members of this non-profit are now exploring a new avenue: to create a web application around a map, listing people with the same interest: <strong>make honey not money</strong>. This project is a great occasion to work on a purposeful project which represents the perfect playground to try new exciting tools and technologies, from cloud computing to serverless infrastructure. Unfortunately, we won’t be able to name all technologies involved as we don’t want to inadvertently trigger the buzzword detector or more seriously, advertise for those that don’t need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*0t2N4OqxXVGTB2dd9PlvvA.png" /><figcaption>There are five beehives hidden in this picture. Will you be able to find them all? (© Happyculteur.co)</figcaption></figure><p>That being said, we can speak freely about the application itself, which is still in the early stages of its development. Let the sneak peek begins: the application is written in <a href="https://www.javascript.com/">JavaScript</a>, the language of choice for web applications; the power of typing is provided by <a href="https://www.typescriptlang.org/">TypeScript</a>; the back end is powered by <a href="https://nodejs.org/en/">NodeJS</a> and the front is made with <a href="https://reactjs.org/">React</a>; for logging, Kevin relies on <a href="https://sentry.io/welcome/">Sentry</a> ; <a href="https://snyk.io/">snyk</a> is used to scan the code and look for vulnerabilities; finally, for the map, the open-source JavaScript library <a href="https://leafletjs.com/">Leaflet</a> has been chosen: a forward thinking technological stack indeed!</p><blockquote>This stack and the freedom to make it evolve do constitute a wonderful playground to test new things and improve your skills while helping someone else; a perfect combo for me, and probably for you too!</blockquote><p>Let us concludes with an announcement: <strong>Happyculteur is looking for new developers, </strong>willing to spend a few hours per months to help Kevin ship the web application. Please, <a href="https://www.happyculteur.co/contact.html">do contact them if you are interested</a>.</p><h4><strong>Conclusion</strong></h4><p>We hope you have enjoyed reading this newsletter. For those that were on holidays and are going back to work, we wish you the best!</p><p>Please keep in touch with <a href="https://open-paas.org/">OpenPaaS</a> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora">GitHub</a>.</p><p>Interested in joining LINAGORA?<strong> </strong><a href="https://job.linagora.com/"><strong>We are hiring</strong></a><strong>!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dc837adfa67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-august-2018-4dc837adfa67">OpenPaaS’ Newsletter — August 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the software lie the humans]]></title>
            <link>https://medium.com/linagora-engineering/behind-the-software-lie-the-humans-40541dd53b1?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/40541dd53b1</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 13:32:50 GMT</pubDate>
            <atom:updated>2018-07-26T07:20:02.965Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Michael Bailly, OpenPaaS’ Product Owner, under the spotlight</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pu6DJXFVmRL6dxaCVgwCcA.jpeg" /><figcaption>A representation of each and every files and directories located in the main OpenPaaS repository, as displayed by the open source software Gource. Directories appear as branches and files as leaves.</figcaption></figure><h3>Introduction</h3><p>Just like a plant, a software requires constant care so it can grow and flourish. <a href="https://open-paas.org/">OpenPaaS</a> is no exception to the rule, except that it would be better pictured as the fertile soil — the platform — and the collection of plants that are being nurtured by it — its set of software. In other words, <strong>OpenPaaS is an ecosystem where applications can grow in symbiosis</strong>. If OpenPaaS is like a blooming garden, its main botanist-in-chief and visionary warden for the past five years has undoubtedly been Michel Bailly, OpenPaaS’ Product Owner. <em>Where OpenPaaS comes from?</em>; <em>where it is heading?</em> Let the interview begin to figure that out!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ftp4JsYocqj7cvJ89_tGA.jpeg" /></figure><p><strong><em>Dear Michael, could you please introduce yourself and tell us more about your work within LINAGORA?</em></strong></p><p>Sure, my name is Michael Bailly and I am responsible for OpenPaaS, <a href="https://linagora.com/">LINAGORA</a>’s flagship product. As such, I have three main missions:</p><ul><li>My first and perhaps most important one is to <strong>manage the people</strong> who makes up the team: geeky developers, business analysts, communication specialists and testers.</li><li>My second mission is to <strong>take care of the product</strong>, which means to define the road map and to sort the backlog.</li><li>Finally, my third mission is to make sure customer deployments go well, and in general <strong>to accompany the customer</strong>.</li></ul><p><strong><em>OpenPaaS’ version 1.1.0, also known as Antares, is now live: what is the first word that comes to your mind?</em></strong></p><p><strong>Maturity</strong>. Technically, the first version has been released in December and publicized in February. However, at that time it was still lacking some important features: it couldn’t be deployed in production just yet. In just over six months, a lot of efforts has been invested by the team to change that, to make OpenPaaS more stable and feature rich, and in general <strong>to industrialize the product</strong>. Two main aspects were improved :</p><ul><li>The first aspect was to do <strong>cloud deployments on top of Kubernetes</strong> correctly. Deploying to the cloud is vastly different as what you do, with say DEB or RPM packages.</li><li>The second thing was about <strong>adding missing features</strong> and bug fixes.</li></ul><p>I am now using OpenPaaS every day and I feel a real stability, an ease of use, a demonstration that the product has indeed matured enough to be used in production.</p><p><strong>What makes OpenPaaS stand out in front of the competition?</strong></p><p>I guess you’re referring to competing products like Office 365 or G Suite. I think we need to put the product in the right place. It is true that OpenPaaS provides general purpose collaboration features such as mails, calendars, contacts and the like. But it goes beyond that, as it can also be used to become <strong>the backbone of an information system</strong>, allowing the interconnection of legacy software that are usually mostly running in silos, as well as to allow the interconnection with external partners. In other words, it is important to insist on the fact that<strong> the platform is a toolbox to propel digital transformation</strong>.</p><p>The second thing, which I think is hugely important, is the <strong>Open Source</strong> aspect of our product. Our competitors are far from being Open Source. We, on the contrary, are Open Source from the bottom to the top, something that makes us genuinely proud. LINAGORA is insisting on this aspect and was able to deliver a high level of professional quality while at the same time remaining truly committed to the Open Source philosophy.</p><p>The third thing is <strong>data privacy</strong>, a component we refer to as ethical computing, and which is extremely important. When our customers deploy our solution, they can be fully assured that their data will not leave their infrastructure. It is reassuring for them.</p><p><strong>Customers have been testing and using the platform. How would you describe their first feedbacks?</strong></p><p>I could just say that all of our customers are satisfied but that would be dishonest.</p><p>On the negative side, customers expected to see features that were lacking at that time, such as interoperability with popular proprietary software. I am confident that this is only a matter of time before we can implement all of those. OpenPaaS <em>Antares</em> is a significant step in the right direction.</p><p>On the positive side, core functionalities are working well. In short, the application does its job and does it well. Secondly, OpenPaaS is reported as being pleasant, simple and intuitive to use. For us this is a great achievement because we have indeed invested a lot of energy to have a <strong>great level of user experience</strong>, something that is quiet unique for an Open Source project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*1Ar4236zazgK6wK2uuZSJA.jpeg" /></figure><p><strong>How those feedbacks are being taken into account to improve the platform?</strong></p><p>Simply. We create a customer-specific backlog that includes two kinds of tickets: tickets for new features and tickets for bug fixes. We collect issues and inject those in the client backlog. Then we discuss with stakeholders and we prioritize solutions.</p><p><strong>Let’s go back in time. Where does OpenPaaS come from?</strong></p><p>In 2007, LINAGORA acquired <a href="https://obm.org/"><strong>OBM</strong></a>, a groupware, and was able to market and sell the software successfully. However, it turns out that in 2018, architecture standards and models are different than ten or twenty years earlier, when there were no smartphone and when OBM first came out. Rather than to refactoring OBM, <strong>we needed a new solution built from the ground up</strong>. LINAGORA invested significant resources to make that happen.</p><p>The second thing is research. OpenPaaS started as a research project in 2012, a project that is still running today. Thanks to our research team, the technical foundations and collaboration aspects were laid out during this period. It has been rewarding to work with people from universities and prestigious laboratories which were able to shape the product at an early stage.</p><p><strong>Is OpenPaaS the successor to OBM, our groupware?</strong></p><p>At first, OBM has been developed to do mail, contact and agenda management, and to do it well. It was in the early 2000s and groupware were all around. OpenPaaS goes beyond that: <strong>OpenPaaS is a two-stage rocket</strong> which alongside business collaboration applications such as contacts, communities, instant messaging, and the collaborative edition of documents, provides a less visible foundation that to me is more important than the rest. This part, which I have already mentioned, is the <strong>platform</strong> around which businesses will be able to expand services and design business logics.</p><p>Let’s take the example of a large hospital: in a hospital, we need a business software like an appointment booking software for doctors. Obviously, it takes a calendar system because you need to register bookings but it goes beyond that: you also have to know what doctors are doing, what is their specialization so we can match them with the right patient. If I am looking for a rheumatologist, I don’t want to be received by an ophthalmologist. The kind of system we are looking at must manage leaves and small work-flow of acceptance. In the example, <strong>the goal of OpenPaaS would be to provide all the collaboration primitives</strong> and to allow the hospital to create its own business application on top of it, an application that could be used by other hospital as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CdtfX3FU5AWTID40P8ceDQ.png" /><figcaption>OpenPaaS under the hood. The user on the left is accessing the platform through her web-browser. When she sends an email, it will be processed by <a href="https://james.apache.org/">James</a> and stored in <a href="https://cassandra.apache.org/">Cassandra</a>. When she creates an event in her calendar, it will be dealt with by <a href="http://sabre.io/">SabreDAV</a> and then stored in <a href="http://mongodb.org/">mongoDB</a>. In either cases, <a href="https://www.elastic.co/">Elasticsearch</a> is building its own database and indexing the information. Whenever she will look for an event or mail, she will be able to look for it by using a simple query.</figcaption></figure><p><strong>There will be three upgrades per year. Could you tell us a bit more about the next upgrade due for October?</strong></p><p>So actually, the first important thing to report, it seems to me, is that we are going to switch to a system called <strong>time-based release</strong>. New versions will be released on predefined dates, and will be published three times a year: on February, June and October. It will offer our customer more visibility into our road map. For the next release, we will continue to polish out our product and thrive to answer customer-driven issues. More concretely, we will rethink the way different business objects in the platform can interact, to bring more flexibility, to be able to stick closer to our different customers use cases and workflows. In short,<strong> it will be the first customer-driven upgrade</strong>, intended to facilitate their life.</p><p>The social part will be improved: we would like to rework the social part, and to ship a mobile application, so you could chat as you would do with any other popular solution.</p><p>On top of that, if we have enough time, we will deepen LinShare’s integration into the OpenPaaS platform. As of now, we already have a nice level of integration but we have thousands of ideas to make it even more fun to use.</p><p><strong>Can you discuss what OpenPaaS is offering as a collaborative office suite?</strong></p><p>As a result of the OpenPaaS research project, we have been able to integrate <a href="https://cryptpad.fr/"><strong>CryptPad</strong></a> to OpenPaaS. CryptPad, which is developed by <a href="https://labs.xwiki.com/"><strong>XWiki Labs</strong></a>, one of our partner, is basically <strong>pads on steroids</strong>. Its integration to OpenPaaS is now done, which is great because it means that within our platform, users have now the opportunity to work collaboratively in real-time. Although CryptPad is rich and have quite a few formating options, it is still less powerful than a more traditional word processor, and for instance won’t typically offer a traditional page layout.<br>This is the reason why, apart from CryptPad, we are now working to <strong>integrate OnlyOffice into OpenPaaS</strong>, following a two-steps strategy. At first, we will integrate with the <a href="http://onlyoffice.org/">OnlyOffice.org</a> cloud. In a second time, we would like to integrate the OnlyOffice server directly within our platform, as a micro-service. It will guarantee that customer’s data do actually stays at home.</p><pre><em>Which one do you like the most? </em>The interview within the interview</pre><pre>Richard Stallman or Linus Torvald?<br> &gt; <em>Linus Torvald</em><br>Reddit or Hackernews?<br> &gt; <em>Hackernews</em><br>VScode or Atom?<br> &gt; <em>VScode, unfortunately</em><br>KDE or GNOME?<br> &gt; <em>KDE obviously, as it is the only one that works</em><br>QWERTZ or AZERTY?<br> &gt; <em>AZERTY by habit, but I have nothing against the QWERTZ layout</em><br>APT or RPM?<br> &gt; <em>RPM</em><br>Bash shell or Z shell?<br> &gt; <em>Bash</em></pre><p><strong>As of now, OpenPaaS is relying on NodeJS for the back end and AngularJS for the front end. Is there any change planned for the near future when it comes to web development frameworks?</strong></p><p>Internally, everyone likes <a href="https://nodejs.org/en/"><strong>NodeJS</strong></a>: we have no reason to switch to anything else. We are keeping it up-to-date which is usual when you are in the software editing business. The problem lies more on the front end: on this side, we are using <strong>AngularJS</strong> version 1, and this framework has been supplanted by version 2 and more. However, version 2 is largely incompatible with the version we are currently using. We are now considering moving to a new framework.<br>Nowadays, there is a very strong community and business attraction towards a framework called <a href="https://reactjs.org/"><strong>React</strong></a>. Apart from that, a third framework called <a href="https://vuejs.org/"><strong>VueJS</strong></a> is skyrocketing because it is simpler to use than React and entirely community-driven, as opposed to AngularJS which is backed by Google and React which is backed by Facebook.<br>As of today, the strategy for OpenPaaS is to keep AngularJS as a framework for dealing with personal information management: after all, it has served us well so far. On the more socially-oriented parts of the platform, VueJS is going to be used.<br>In the long run, the idea is to offer developers a way to develop applications for the OpenPaaS ecosystem regardless of the framework they currently use. This goal could be achieved by providing <strong>ready-made templates</strong> for the three main aforementioned frameworks, and any other one that could appear in the meantime.</p><p><strong>New employees, including trainees, have recently joined the OpenPaaS team. Do you have any advice for young developers who are starting their career in France?</strong></p><p>It is a bit boastful of me, but first of all, they are doing <strong>the best job in the world</strong>. Secondly, in France, there is a small problem which is that we give less value to technical expertise than to project management functions, which I think is a mistake. <strong>Technical experts are essential</strong>, and as a developer you should not hesitate to go along this path rather than to become a team manager. Thirdly, as a developer you tend to always look for technical challenges to solve, which is what we are expecting of you. But you should not forget what the end goal of your job is, which is to <strong>create value for your customers</strong>. For instance, changing your test framework every month is great but it does not create any value for the customer who bought your product. In sum, your work will always be about balancing several priorities, such as what can you do to improve your productivity and what can be done to deliver more value for the customer.</p><p><strong>Michael, thank you for your time.</strong></p><p>You’re welcome.</p><p>Keep in touch with <strong>OpenPaaS</strong> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub,</a> and our dedicated <a href="https://forum.open-paas.org/">Forum</a>.</p><p>Interested in joining <strong>LINAGORA</strong>? <a href="https://jobs.linagora.com/">We are hiring!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40541dd53b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/behind-the-software-lie-the-humans-40541dd53b1">Behind the software lie the humans</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — July 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-july-2018-e24419ce4e0e?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/e24419ce4e0e</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[upgrade]]></category>
            <category><![CDATA[interoperability]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 15:07:31 GMT</pubDate>
            <atom:updated>2018-07-17T15:07:31.937Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Behold the new star in the sky</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtZ0KIBGLkXIUaeqd7riUw.png" /><figcaption>OpenPaaS v.1.1.0 <em>Antares</em> is now on orbit!</figcaption></figure><h3>Introduction</h3><p>Earlier this year, while we could still be greeted with snowflakes on our way to work, OpenPaaS — the open source web-based collaborative platform — was officially launched. Six months and more than 2400 commits<em> </em>later, we are releasing the first major upgrade, version 1.1.0 dubbed <em>Antares. </em>It represents the work of more than 50 contributors.</p><p>For the first time, we have decided to name our release: astronomical objects will be used as a theme. Welcome to <strong>OpenPaaS <em>Antares</em></strong>, one of the brightest star in the sky, and which is also designated as <em>Alpha Scorpii</em>. Let’s take advantage of July’s newsletter to introduce recently added features to our product.</p><h3>From wishful thinking to reality</h3><p>That is an understatement to say that we would like OpenPaaS to be widely adopted, and at the same time just wishful thinking if we don’t make our solution easy to adopt and deploy. With this release,<strong> importing </strong>and <strong>exporting</strong> data is now available, as well as user <strong>quotas</strong> and <strong>email redirections</strong>; another main focus has been <strong>interoperability</strong> with proprietary software, a must-have in many environments; finally, it is now easy to deploy OpenPaaS on top of <a href="https://medium.com/linagora-engineering/when-linagora-embraces-kubernetes-1609792e955b"><strong>Kubernetes</strong></a>. Those are the main points we have worked on to make OpenPaaS deployments go like a breeze.</p><p>From a development perspective, we have now switched from feature to <strong>time-based releases</strong>. What does that mean? As a consumer, you will have a <strong>better visibility </strong>into our product life cycle, which will allow you to better<strong> plan</strong> <strong>upgrades</strong> if you are running OpenPaaS on premises. From our side, we will be able to plan releases more in advance and maintain a steady pace to our development. Now, let’s dive into our new features!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*sgafdVhzOenzIKuPKF5IpA.png" /></figure><ul><li><strong>Advanced Search.</strong> The search engine now supports specific search criteria, and allow the user to filter emails by sender, recipient, subject, to exclude words or to only look for emails with attachments. The very content of your email attachment is now indexed and can be searched!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*rz7CcLZfOJuwF2jIdlBqVQ.png" /></figure><ul><li><strong>LinShare integration</strong>.<strong> </strong>The<strong> </strong><a href="http://www.linshare.org/new/en/">LinShare file sharing software</a> is now integrated to OpenPaaS. It is now possible to save an email attachment to LinShare — something that will happen automatically if it exceeds a certain threshold — or to add a file stored in LinShare to an email.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oMNGbMz0xjzvDrpi4XZ15A.png" /></figure><ul><li><strong>Quota</strong>. Using the web interface, administrators can now set a mailbox size quota on a per domain or a per user basis, a must-have feature for professional deployments.</li><li><strong>And also</strong>. You can now write an email in a <em>dedicated window</em>; OpenPaaS can now be set as <em>the default program</em> for managing emails; <em>read receipts</em> have been added; visual indicators are being triggered when an email is sent or received; a <em>refresh button</em><strong><em> </em></strong>to fetch latest emails has been added; finally, in the Sent mails folder, the recipient rather than the sender is now being shown.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/123/1*NY_cN-UG72UJ_G6dVfIyCw.png" /></figure><ul><li><strong>Address books</strong>. A users can now have multiple address books, as well as the ability to move and copy contacts between them.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtEm7jbXP7pa92TA1ljEnQ.png" /></figure><ul><li><strong>Address books sharing</strong>. Users can now share their address books with read or read and write access, either with all domain members at once or just with one user at a time, in the latter case also with full administrative mode.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLrvbmnhZnRo35zU1dResg.png" /></figure><ul><li><strong>vCard Import and Export support</strong>.<strong> </strong>Contacts can be imported and exported using the vCard standard, such as <em>contact.vcf.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YnJ40XVeVxSGnuHV5mOcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/154/1*GqEeyRQH-Ec8Aqr03xwDSA.png" /></figure><ul><li><strong>Availability</strong> (Free-Busy). If an attendee is busy for a selected time frame, the platform will notify you.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hVGo-DdK1UNrvwOHCPe2Dw.png" /></figure><ul><li><strong>Gorgeous attendees list for events</strong>. The attendee list is now clearer, more responsive, display people avatars including their answer’s state.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*gI2zvTZCXz3jP9VPdhVJOg.png" /></figure><ul><li><strong>Suggest a new time</strong>. Any person invited to an event can suggest a new date to the event’s organizer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*vVCThkiqg9NKnx9MFhY1rw.png" /></figure><ul><li><strong>iCalendar import and export support</strong>. Users are able to export or import their calendar using the iCalendar format, such as the <em>calendar.ics.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*B1GNXgcA4Son6MZ1JvF1Bg.png" /></figure><ul><li><strong>Interoperability.</strong> OpenpaaS’ calendar is now compatible with Microsoft Exchange and Microsoft Office 365 as well as with the Google G Suite. It is a significant feature which has required a lot of efforts, something that isn’t suprising considering the closeness of those solutions. For instance, timezones, which are difficult to implement because every external providers have peculiar ways to handle them, are now supported across the board. Last but not least, the <a href="https://obm.org/">OBM</a> events interchange format is now also supported.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*QccO2GXGtJD3ODgrih6JrA.png" /></figure><ul><li><strong>User interface and experience improvements.</strong> The community module has a brand new look. The right panel, which is displaying community members and the widget to invite new members, has been improved. Embedded media elements, like videos and presentations, now look awesome on any type of display.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xb3U_zRTJynfGt_CqrleQQ.png" /></figure><ul><li><strong>Remove, remove. </strong>Community managers are now able to remove a member from a community. Communities and their associated data can now also be deleted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/177/1*UBbd5R5VP6JrgYWun1Fe1A.png" /></figure><ul><li><strong>Notifications. </strong>This update brings real-time notifications to the chat module. Users can see channels were new messages have been posted, and messages in which a user is mentioned now trigger a more visible highlight. Notifications for chat messages are now available platform-wide.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9nNwgwittT8aGL18906Mw.png" /></figure><ul><li><strong>New emojis</strong> ! The emoji library has been updated to use the beautiful ones provided by Twitter (thanks!). We have also added emoji groups, to give you an easy and quick access to that very icon you’re looking for.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*Z4brR1EurmSLJ-n_UPFndg.png" /></figure><h3>Conclusion</h3><p>The next trove of features will happen October this year. Please do not hesitate to suggest new ones, for instance on the General section of our <a href="https://forum.open-paas.org/">Forum</a>.</p><p>We hope you have enjoyed reading this newsletter! As usual, you can install OpenPaaS on your favorite <a href="https://docs.open-paas.org/getting-started/linux/">Linux distribution</a> or try it by using <a href="https://docs.open-paas.org/getting-started/docker/">Docker Compose</a>.</p><p>Keep in touch with <strong>OpenPaaS</strong> on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub,</a> and our dedicated <a href="https://forum.open-paas.org/">Forum</a>.</p><p>Interested in joining <strong>LINAGORA</strong>? <a href="https://jobs.linagora.com/">We are hiring<em>!</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e24419ce4e0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-july-2018-e24419ce4e0e">OpenPaaS’ Newsletter — July 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — June 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-june-2018-ca8e9bea0ed1?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca8e9bea0ed1</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 14:03:38 GMT</pubDate>
            <atom:updated>2018-06-26T14:03:38.895Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>One quarter after OpenPaaS’ launch : reaching cruising speed</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcmJEti-HV1Vnjdw_JLbdg.jpeg" /><figcaption>The French aerobatic team at work: more than the sum of its parts. Photo by <a href="https://unsplash.com/photos/OSVh2HgbaZc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joe deSousa</a> on <a href="https://unsplash.com/collections/1859420/downloaded?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>A quarter has passed since <strong>OpenPaaS’ official launch</strong> at the <em>Mobile World Congress</em> in Barcelona. It was back in February this year, and at this occasion, we released an <a href="https://medium.com/linagora-engineering/openpaas-is-out-773704eadfbc">article</a> to reveal some of the inner workings of our <a href="https://open-paas.org/">awesome Open Source collaborative platform</a>.</p><p>What happened since the launch? In this late June’s newsletter, lights will be shed on our latest teams’ achievements. Rather than a lengthy article, we will cover updates — with a focus on the <strong><em>Contact </em></strong>application — and discuss the state of the project in general.</p><h4><strong>General overview</strong></h4><p>How is OpenPaaS thriving since its debut? In one word: <em>well</em>! At the time of writing, our collaborative platform is being tested in half a dozen places and counting, in France and around the world. Future deployments are intended for as low as one hundred individuals to <strong>the tens of thousands</strong>. Now that OpenPaaS has been released, valuable external feedbacks are pouring in, allowing us to spot and fix bugs, and overall to make sure the platform is genuinely matching customer’s expectations.</p><p>How are we serving our customers? For the most part, <strong>OpenPaaS is offered as a Service, </strong>so end-users can have a better grasp of the platform, without having to deploy it themselves. Who are we working with?</p><p>Among others, we are proud to work with the Togolese <a href="http://www.numerique.gouv.tg/"><em>Ministry of Posts and Digital Economy</em></a>, which after having tested out and validating the platform, will soon rolling out OpenPaaS on top of their own infrastructure. Another customer, with <strong>stringent security requirements</strong>, asked us to deploy our platform on premises in an air-gapped environment, a mission we were keen to lead, and which illustrates the plasticity of our solution. What can we learn from those two examples? The fact that OpenPaaS is <strong>Open Source</strong> give system administrators a lot of flexibility when it comes to means and ways to deploy it, regardless of the context.</p><h4>System administration</h4><p>Speaking of system administration, it is now possible to deploy OpenPaaS from scratch — alongside the file sharing solution <a href="http://www.linshare.org/en/">LinShare</a> — in <strong>less than 30 minutes!</strong> As stated in the past, we target Kubernetes clusters, and will continue to tweak our platform to better take advantage of this environment. Follow the link bellow if you want to learn more about <strong>how OpenPaaS met Kubernetes</strong>.</p><p><a href="https://medium.com/linagora-engineering/when-linagora-embraces-kubernetes-1609792e955b">When Linagora embraces Kubernetes</a></p><h4>Development</h4><p>As a team, we would like to release new OpenPaaS versions more frequently, in a steady and regular pace. As a result, we have decided to transition to <strong>time-based development cycles</strong>, which will allow us to deliver more contents to our customers more frequently. Each year, three major version will be released. The next major release is planned for… July!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*KKIMVEISVhbLdLCNGFa4PQ.png" /></figure><p>Microsoft has recently acquired GitHub, home of many Open Source projects from the Linux kernel to Kubernetes. This acquisition has triggered a movement to look for alternatives and to find a more neutral ground for Open Source software projects. Among those potential new places, <a href="https://motherboard.vice.com/en_us/article/ywen8x/13000-projects-ditched-github-for-gitlab-monday-morning">GitLab is scoring high</a>. What are <em>we</em> using internally? Will we need to migrate too?</p><p>No, in-house, we are already relying on a self-hosted <a href="https://about.gitlab.com/">GitLab</a> instance, which we use as our central git repository, and which is mirrored to a <a href="https://github.com/linagora">GitHub repository</a>. Recently, our GitLab instance has been updated, and we can now benefit from all of its majors fixes and new features!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/181/1*Zr9jMK0xTXITKB74hy4qQg.png" /></figure><h4>Contact under the spotlight</h4><p>OpenPaaS is built around three main applications: <strong><em>Inbox</em></strong>, for emails; <strong><em>Calendar</em></strong>, for events; and <strong><em>Contacts</em></strong>, for…well, you guessed it: Contacts! Recently, the former application got some noticeable improvements, which are worth mentioning:</p><ul><li><strong>Default domain visibility</strong>. As a user of OpenPaaS, you are part of a domain, which typically matches the name of your organization (such as tux@<em>freesoftware.org</em>). By default, as a member of this domain, you will be able to see each and every other members of this domain. No need to ask for your colleague’s email address anymore.</li><li><strong>Import contacts.</strong> OpenPaaS is all about standards. Information should be able to flow in-and-out of the platform without friction. So far, it was possible to import your contact from a preexisting Google account. On top of that, it is now possible to import contacts from a vCard, as illustrated in the screenshot below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/263/1*4L-fkmErV4c-cknSgaozaQ.png" /><figcaption>In order to import contacts from a vCard file, go to the Contact App. From there, select the plus sign at the top left corner, which will reveal a list. The last item <strong>Import contacts from file</strong>, should then be selected, and will trigger the opening of a window. At this point, it should be straightforward. Note that you can choose to which address book your imported contacts will be merged to.</figcaption></figure><ul><li><strong>Export contacts.</strong> The export feature allows you to export an entire address book at once, for use in any other compatible applications.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*HW-ZCiTZDXR4LiYGHklNiQ.png" /><figcaption>In order to use the export feature, go to the Contact App. When you are there, select the three vertical dots (also known as “more options”) next to the desired address book, and then click on the <strong>Export</strong> feature. A window will pop up. From there, select the <strong>Export</strong> button.</figcaption></figure><ul><li><strong>Multiple address books.</strong> Up until recently, a user could only possess one address book. It is now possible to have multiple address books, including shared address books. If you are working in a team, you may want to rely on the same resource and source of truth. Rather than to manage an address book per each individual, you could decide to share a global address book, to foster the sharing of information.</li><li><strong>Address book delegation.</strong> Last but not least, you can now delegate the management of your address book to a particular user, from viewing-only rights to full-blown management rights. In the former case, the user with those rights will be able to manage the address book as if it was his or hers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0nJxkB0oUaOlTC6oDpYq4Q.png" /><figcaption>In order to use the <strong>Delegation</strong> feature, go to the Contact App. When you are there, select the three vertical dots (also known as “more options”) next to the desired address book, and then click on the<strong> Settings</strong> item in the list. From there, go to <strong>Delegation</strong>, search for a user to delegate your address book to, pick your level of permission and select <strong>Add</strong>.</figcaption></figure><h4>Conclusion</h4><p>We could have covered mobile and desktop synchronization, which have made a huge leap forward recently; ongoing works on platform-wide notifications; a recent departure and an upcoming one<em> (Farewell Maxime and Sang! Thanks for your awesome work and good luck for the future!) </em>and a handful of new arrivals… But rather than to spoil it, let’s build up the suspense a bit and keep some announcements for later, like the next upcoming release for instance!</p><p>In the meantime, we will try to align as well as the French aerobatic team, and to continue to work collaboratively to release a great milestone!</p><p>Keep in touch with<strong> OpenPaaS </strong>on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub</a>.<br>Interested in joining <strong>Linagora</strong>? <a href="https://jobs.linagora.com/">We are hiring!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca8e9bea0ed1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-june-2018-ca8e9bea0ed1">OpenPaaS’ Newsletter — June 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenPaaS’ Newsletter — May 2018]]></title>
            <link>https://medium.com/linagora-engineering/openpaas-newsletter-may-2018-b55c37c84e6d?source=rss-68b248970978------2</link>
            <guid isPermaLink="false">https://medium.com/p/b55c37c84e6d</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[esb]]></category>
            <dc:creator><![CDATA[Lukas]]></dc:creator>
            <pubDate>Tue, 29 May 2018 07:29:23 GMT</pubDate>
            <atom:updated>2018-05-29T07:29:23.152Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>OpenPaaS and Entreprise service buses: on the road to full-on integration</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bJAfxV4qB-R6ajA8GdSKQA.jpeg" /><figcaption>You can picture Entreprise Service Buses (ESB) as freeways connecting multiple cities from different countries (=<em>applications </em>written in many languages), allowing them to exchange individuals and merchandises (=information or services) using a standardized transport path or road (=bus). <strong>Photo taken in Shanghai by </strong><a href="https://unsplash.com/photos/7nrsVjvALnA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><strong>Denys Nevozhai</strong></a><strong> on </strong><a href="https://unsplash.com/search/photos/software?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><strong>Unsplash</strong></a></figcaption></figure><h3>Introduction</h3><p>Among its other area of expertise, <a href="https://linagora.com/"><strong>LINAGORA</strong></a> is proud to be a software editor focused solely on developing free and open source software. This openness has many benefits, including making integration between in-house applications much easier, and ultimately allowing for the consolidation of its portfolio.</p><p>In <a href="https://medium.com/linagora-engineering/openpaas-newsletter-april-2018-888482f0e08e">last month’s newsletter</a>s, we covered the long-term prospect of integrating <a href="https://linto.ai/"><strong>LinTO</strong></a>, our open source smart assistant in the making, with <a href="https://open-paas.org/"><strong>OpenPaaS</strong></a>, our beloved collaborative platform. This late-May newsletter will illustrate how another in-house software, <a href="http://petals.ow2.org/"><strong>Petals ESB</strong></a><strong> — </strong>which is currently being integrated to OpenPaaS — can team-up with OpenPaaS to offer customers an even more complete experience. But first, we will shed some light on the kind of problems Entreprise service buses (ESB) software are trying to solve and where they come from.</p><p>Happy reading!</p><h3><strong>Application wilderness</strong></h3><p>Any given institution has various sets of needs when it comes to software — overlapping or not — from the organization itself to the individual worker: the finance department needs accounting-related software; the marketing department requires customer relationship management software; almost everyone needs an office suite; etc. The information technology (IT) department, which seeks stability above anything else, is nonetheless expected to quickly satisfy this internal demand, while coping with external pressures to adopt new technology (<a href="https://medium.com/@kaistinchcombe/decentralized-and-trustless-crypto-paradise-is-actually-a-medieval-hellhole-c1ca122efdec">blockchain, anyone?</a>).</p><p>As a result of this, the number of software your IT department is managing is likely to grow steadily — to the point of becoming unmanageable. Without thoughtful architectural decisions along the way, entropy, understood as the gradual decline into disorder, may ensue, driven by strong centrifugal forces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NJrU5t04uhB-afrnRE3PBw.jpeg" /><figcaption>The history of many IT infrastructure or information systems often looks like rock sedimentation, also known as stratum in Geology: through time, software layers are added on top of each other, without any kind of integration. <strong>Photo by </strong><a href="https://unsplash.com/photos/PfxjrYOd3pc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><strong>Cosmic Timetraveler</strong></a><strong> on </strong><a href="https://unsplash.com/search/photos/sediment?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><strong>Unsplash</strong></a><strong>.</strong></figcaption></figure><p>Unsurprisingly, this particularly problematic outcome, which can be called <strong>application wilderness</strong>, is especially acute for organizations that have decades-old IT departments. Application wilderness is the coexistence within one company, business or information technology environment of a great number of isolated software, which have grown over time like weeds, with desperate need for integration.</p><p>Application wilderness is not just a made-up expression: it has real negative consequences. Among them is <strong>information siloization</strong>. When insular software are coexisting within a specific domain, the information sent to them will eventually grow to constitute compartmentalized silos. In information management, this phenomenon is called <a href="https://en.wikipedia.org/wiki/Information_silo"><strong>information silo</strong></a>, and is illustrated in the diagram below. How can we avoid this outcome?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/0*eHXQ9nPHvQSysUqV.png" /><figcaption>The letter A represents an individual using software B and C. As shown by this illustration, those two software are unable to talk to each other. The result is information siloization, and yes, it is bad for your health. <strong>Diagram by Theodoxxi </strong><a href="https://creativecommons.org/licenses/by-sa/4.0"><strong>CC BY-SA 4.0</strong></a></figcaption></figure><h3>Business-oriented computing</h3><p>Ideally, within a company, an IT infrastructure and network would grow organically with the business, with little to no friction. But the actual world isn’t the best of all possible worlds. In reality, the IT and non-IT part of a company often clash, due to contrasting if not opposing interests. How can they both be reconciled? Rather than to try to change people themselves, a more promising approach is often to adjust their environment, without trying to change the way they work.</p><p>Let’s enter the way-back machine and shrink ourselves down to the level of a software in order to introduce component-based software engineering, which <strong>alongside its offspring </strong>have offered answers to help solve the so-called application wilderness problem. Or at least, that is what will be defended.</p><p><a href="https://en.wikipedia.org/wiki/Component-based_software_engineering">Component-based software engineering</a> (CBSE), also known as component-based development (CBD), is an approach to software engineering born in the 80s that stresses the need to create software out of reusable and loosely coupled components. Here, components are seen as <a href="https://en.wikibooks.org/wiki/Computer_Programming/Component_based_software_development">black boxes</a> which <strong>only defines the way they will talk to other parts of a software</strong>, allowing developers to reuse them without knowing how they work internally. Alongside object-oriented programming or software quality insurance, to quote only a few, CBSE has represented one of many answer to the early 70s <a href="https://en.wikipedia.org/wiki/Software_crisis">software crisis</a>, a crisis triggered by the rise of available computing power and the lack of appropriate tooling to meet the then exploding demand for software. The promise behind CBSE was that by raising the level of abstraction, it would be simpler to write useful and efficient computer programs, allowing the software industry to better cope with the demand at the time.</p><p>One beneficial side-effect of this approach is that it has improved the readability of software for non-technical audiences, contributing to filling the gap between the software folks and the layman. How so? Components can be easily tied to real-world events and link to business workflows.</p><p>Take for instance the <a href="https://en.wikipedia.org/wiki/Unified_Modeling_Language">Unified Modeling Language</a> (UML): this language was developed in the 90s and is being used to model the way interactions between components work in a software, making it easier to associate lines of code to their corresponding process. (Shameless plug: OpenPaaS has implemented UML diagramming through an additional module.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/190/0*TkxOptRZMyltcoiM.png" /><figcaption>This is an illustration in UML showing how two components interact. In order for the checkout to happen, the customer’s card should be processed. The CardProcessing component provides this functionality to the Checkout component. <strong>Diagram in Public Domain.</strong></figcaption></figure><p>Let’s now elevate ourselves to the level of the operating system, where component-based ideas have also largely been applied, most notably to programmatically link the user-generated contents of various software together.</p><p>In the 90s, Microsoft jumped on the CBSE train and created <a href="https://en.wikipedia.org/wiki/Object_Linking_and_Embedding">The Object Linking &amp; Embedding</a> (OLE) alongside the <a href="https://en.wikipedia.org/wiki/Component_Object_Model">Component Object Model</a> (COM), two proprietary systems infamous for being routinely abused by hackers and riddled with vulnerabilities, thanks notably to <a href="https://en.wikipedia.org/wiki/ActiveX">ActiveX</a>, which made those technologies accessible from untrusted networks such as the World Wide Web. (<a href="https://www.microsoft.com/com/tech/activex.asp">The ActiveX page on Microsoft’s website</a> is no longer available. Rest in Peace, ActiveX?). IBM too has its own implementation, the <a href="https://en.wikipedia.org/wiki/IBM_System_Object_Model">System Object Model</a>, which was tightly integrated to their now defunct OS/2 operating system. Finally, <a href="https://en.wikipedia.org/wiki/JavaBeans">JavaBeans</a>, which regroups many Java objects into a so-called bean, is yet another example of a component-based model.</p><h3>Entreprise service buses to the rescue</h3><p>Let’s now rise again and go back to the level of the architecture of an information system itself. Within a company, multiple software are coexisting. In order to avoid application wilderness, they need to be integrated with each other. <a href="https://en.wikipedia.org/wiki/Enterprise_application_integration">Entreprise application integration</a> (EAI) is a set of tools used to link existing software together while avoiding point-to-point connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*45hxCfLT5fZXddoj2iJt-w.png" /><figcaption>From point-to-point communication to central communication. Copyright by LINAGORA 2016</figcaption></figure><p>This approach comes with many benefits:</p><ul><li>Applications are treated as black boxes;</li><li>They only have one system to talk to;</li><li>Information will flow more easily from one application to the other.</li></ul><p>When services are provided through an network, the expression <a href="https://en.wikipedia.org/wiki/Service-oriented_architecture">Service-oriented architecture</a> (SOA) is used. It is worth noting that a service, in this context, share familiar traits with containers, which are also self-contained entities treated as black-boxes by their environment. In a similar vein, the SOA model has championed the idea of microservices, one of the foundation of the DevOps movement.</p><p>So what are <a href="https://en.wikipedia.org/wiki/Enterprise_service_bus#/media/File:ESB.svg">Entreprise service bus</a> (ESB)? <strong>ESB are middleware that implement both SOA and EAI</strong>. They allow applications to talk to each other by translating and moving their requests, often across a network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/0*JVrP0PyLG_g6yYcy.png" /><figcaption>Here is an illustration of what an ESB looks like. BPEL stands for <a href="https://en.wikipedia.org/wiki/Business_Process_Execution_Language">Business Process Execution Language</a>. <a href="https://commons.wikimedia.org/wiki/User:Silver_Spoon"><strong>Silver Spoon</strong></a><strong> CC BY SA 3.0</strong></figcaption></figure><p>ESB software are intimately tied to business workflows, and are designed to break information siloization by allowing software to exchange information over a common bus. As such, they represent a good way to reduce the architecture debt of an IT ecosystem, because they take into account legacy systems by design, and therefore help long-running businesses to manage their current infrastructure.</p><h3><strong>Petals ESB meets OpenPaaS</strong></h3><p><a href="http://petals.ow2.org/">Petals ESB</a>, LINAGORA’s ESB and part of the <a href="https://www.ow2.org/">OW2 community</a>, is a Java-based platform used to mediate heterogeneous systems by exposing them as services in a common communication layer, the bus.</p><p>More concretely, Petals ESB receive as input information from applications (in the <a href="https://en.wikipedia.org/wiki/Representational_state_transfer">REST</a>, <a href="https://en.wikipedia.org/wiki/SOAP">SOAP</a> or any other format it understands) and when an application requests data back Petals ESB will convert it so that the output will be compatible with what the application is requesting (for example the SOAP format).</p><p>Architecturally speaking, Petals ESB is made up a kernel called the container and of many extensions known as Petals components. These components support various standards such as SOAP, BPEL, <a href="http://www.oasis-opencsa.org/sca">SCA</a>, <a href="https://en.wikipedia.org/wiki/XSLT">XSLT</a> alongside communication standards such as HTTP, Mail, FTP, and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*d6IqKslbpXfiwcpTG9ZMyQ.jpeg" /><figcaption>Copyright by LINAGORA 2016</figcaption></figure><p>Petals ESB’s main characteristics are:</p><ul><li><strong>Distributivity</strong>: Petals ESB is a distributed platform, made out of many instances that are able to communicate with each other over a network.</li><li><strong>Guaranteed Message Delivery</strong>: a message that is sent to a service will always be delivered. If the service is off-line or unreachable, the message will be either stored, or sent to an equivalent service.</li><li><strong>Message Routing</strong>: the effective recipient of a message can be chosen at runtime in function of various criteria.</li><li><strong>Robustness</strong>: In case of an incident, the platform can restore its last-known working state and resent messages that were not processed.</li><li><strong>Respect of standards</strong>: Petals ESB is built around open standards.</li><li><strong>Monitoring</strong>: the content and the properties of the messages that transit in the bus can be monitored.</li><li><strong>Extensibility</strong>: with its component-based architecture, it is possible to extend, update and modify the platform dynamically.</li><li><strong>Tools</strong>: Petals ESB is completed by several tools, including a development environment, a web console, a governance solution, a Maven plug-in, and administration ANT scripts and many more, making it a complete suite.</li></ul><p>Not unlike the DevOps trend, which is bridging the gap between developers and system administrators, ESB like Petals ESB brings business people and information technology specialists closer together.</p><p>What will Petals ESB brings to OpenPaaS? Petals ESB will allow legacy applications to transfer data back and forth to OpenPaaS. But not only that, depending on the context, it will also play the role of a gateway, allowing multiple instances of OpenPaaS to talk to each other. For instance, each and very municipalities could manage its own instance of OpenPaaS and decide through Petals ESB what service should be available to other instances.</p><h3>Conclusion</h3><p>New architectural trends and innovations such as ESB don’t just magically appear. They are built on top of decades-old concepts and mature technologies; and they try to solve real problems, such as to break information silos. Throughout this newsletter, the pre-history of ESB has been illustrated, just as the benefits they can provide to organizations. Let’s wish those technologies and trends continue to thrive.</p><p>Talking about thriving, the<strong> 7 and 8th of June 2018</strong>, the <strong>OW2 consortium</strong>, — which hosts Petals ESB among many other great open source projects like <a href="http://glpi-project.org/">GLPI</a>, an IT asset inventory we use at LINAGORA — will held <a href="https://www.ow2con.org/view/2018/"><strong>its yearly conference in Paris</strong></a>. It is free as in free beers, and <a href="https://www.ow2con.org/view/2018/Program?year=2018&amp;event=OW2con18">showcase many interesting talks</a>. The word is out!</p><p>For next month newsletter’s, we will focus on <a href="http://www.linshare.org/en/"><strong>LinShare</strong></a>’s history and future development. LinShare is LINAGORA’s open source file sharing application.</p><p>Keep in touch with<strong> OpenPaaS </strong>on <a href="https://twitter.com/AwesomePaaS">Twitter</a>, <a href="https://www.facebook.com/AwesomePaaS/">Facebook</a>, <a href="https://github.com/linagora/openpaas-esn">GitHub</a>.<br>Interested in joining <strong>Linagora</strong>? <a href="https://jobs.linagora.com/">We are hiring!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b55c37c84e6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/linagora-engineering/openpaas-newsletter-may-2018-b55c37c84e6d">OpenPaaS’ Newsletter — May 2018</a> was originally published in <a href="https://medium.com/linagora-engineering">Linagora Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>