ownCloud 11 - The strategic approach to the future of ownCloud
CC Attribution - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Böhm, Felix
ownCloud 11 marks a turning point for the ownCloud Development Vision and Strategy outlook for ownCloud
 Because I forgot something really important. Actually we want to thank our sponsors, OpenSuser, Univention, BoxCryptor and Copano. I hope somebody is there already. For sponsoring the conference, for making this possible. And also thanks to our media partners, which is O'Reilly Media, D-Punk Verlag and of course the awesome guys from the OpenSuser video team and C3Voc Media CCC team. We all know they do a great job. Thank you for all your efforts. Hello, I want today to take the opportunity to start the conference with a bit of the backgrounds on why we are doing all this and personally why I am doing this. About the strategy and the future of Enclod. And I will not talk too much about what we do. I leave this to the team and the team will tell you in detail what we have achieved, feature-wise and what we have planned on the roadmap. And I am very proud of the team and want to present my team to you. Let me talk a bit more about where we go and why we are doing this. So let me start with introducing where I come from. I founded a co-working space in Nuremberg and I always cared about how people work and how they collaborate. And in that co-working space I met Holger and he was sitting there and founding a little company called Enclod, that was the first touch point for me with Enclod and soon I started to work for Enclod because basically I am a full stack developer and not a co-working space founder from where I come from. But this is a topic which was very, very close to what brings my fulfillment in my life to care about how people can work together efficiently and how people can work better together than alone. And the co-working space was a bit of an infrastructure I spent to the city here and Enclod was very promising for me because I can take the opportunity to shape the future of collaboration. How people work at home with their families share images and how people work in their workplaces and for me it is very important to do this by exceptional user experience and uncompromising privacy. Privacy is so much important that Enclod becomes the most important software for me when I start a startup. When a team starts on a project you need to have that email communication and you need to have good communication channels of course but then if you start working and collaborating it comes down to Enclod so that you can have your files under your control, don't share your stuff with people out there in the US and you really can collaborate in an easy and efficient way. So this is my vision, my very personal vision and where I come from working for Enclod now for five years and this is why I do this. So this vision is not so much away from the wordings of the Enclod companies using. I'm very happy that we are very close together and let me go a bit more into the strategies how we are doing this and I think the first thing is we are open, we are open source, we will stay open always. This is very important for all the teams. I would have not a single developer anymore if we would change this because these people are really into open source. There is no question about it, we will stay open source and we learned something very important so Enclod needs to be a sustainable project. We want to spend our time we are investing into Enclod in a way where we know that Enclod will always be there and Enclod will stay as a product and on the market. We want to use Enclod also in ten years. So open or sustainable is not so easy to do but it's this combination which is so important and that's also why the Enclod foundation is important that we found it now and we achieved this milestone and it's only one example but this is the next milestone in being open and sustainable. Christian Schmitz will have a talk on the Enclod foundation and if you want to be part of the Enclod foundation have a look on the website or in the talk. I think this is a great opportunity for everyone here. We built extensible and secure code. This means you all can collaborate, you can have your use cases built up on Enclod because it's extensible and modular and we built a very professional software. This secure code, it's enterprise grade code which is really, really possible to use in a production environment. This is really important and this is also a thing which changed a bit for Enclod. Enclod was not always sort of when you think of high quality software but this is where we want to go and this is a very, very major strategy. We want to have professional development involved. I want to have people involved in this project who really know what they are doing when they start coding and this defines our community a lot for me. We are building an ecosystem with partners and people in the community who are experts at what they are doing about encryption, about storages, about how to handle files, about performance and we are listening to people on the use cases and this is not only a project because we are doing what we want. We are doing this together with you in a huge ecosystem. About our partner strategy, Jörg, our partner manager will have a talk. He is quite new to the company and he is doing an awesome job. Thank you, Jörg. I really recommend you to be part of that talk. The last point here is one of the most important things. Innovation and leading technology is our passion. Enclod is all about passion. These people do this because they are really convinced and motivated about this idea and they have all their own reasons why they are doing this. These are all developers, right? We really strive to have, we want to be experts at what we are doing and these people, this team I am working with, they are experts at what they are doing. They are really a great team. They are so good in what they do and they are getting better and better. Enclod needs to bow to that. We need to use latest technology. We can't have experts on legacy technology. It's not working. Latest technology for Enclod means we will have great developers working on Enclod. This is a very important thing and a very important strategy. These people, the smartest people I know around development, they will bring innovation in an area where we have big competitors. But our product, our little community and ecosystem is bringing a lot of innovation to that area. I am so proud of that team and I am proud to see you here and I want to welcome you to the Enclod conference in 2018. Thank you. This is not all. Let's have a little deep dive in what we achieved. According to these strategies, one of the most important things is to have a stable and high quality software and hear some numbers about what we achieved in our quality assurance. The newest, we have coding standards now. We have static code analyzers and we have improved testing frameworks. We care about our quality. Having a close look at our numbers for the testings, we have more unit tests because we just have unit tests with every pull request we do. We had unit tests before, but unit tests are not enough. We also have acceptance tests and these acceptance tests have grown to really ensure that our software is doing what we expect it to do. We have grown the acceptance tests to up to 2,200 tests and it is continuously growing. This is a huge shing. Especially because these tests are not run in one environment. So some of you have one on-cloud running and we care about a huge test matrix. We test with different databases, with different kinds of storages. We test with antivirus integrations or not. We test encrypted storages or not. We test different PHP versions and so many combinations of all of that, all of our apps. This is a huge test matrix and it has grown the coverage we have achieved in this test matrix. We have a dedicated QA team built up for this to achieve this because this is a major, really major task in the last years and we have invested a lot. So as Ruby has already said, we have also gained some success out of that. It's not like we have less support tickets because on-cloud is not running anymore. We have while having a growing customer base, less support tickets coming in and the support tickets which are open right now are at 60% of what they have been. Half a year ago, this is this 60% number. This is so awesome. And if you work with on-cloud in the latest version, I think they will release today, be today about the 10.10. Vincent, is that correct? We are really proud about this version because this version will be the most stable and best on-cloud we ever had. Thanks Vincent and team. Few more numbers which are really impressive. So I was astonished by my QA team. Really, we are running the whole test suite on over 100 of the workers and they are doing 2,000 days of testing time each month. This is so much. They are running every night, they are running on every pull request, on the pull request. The tests need eight hours CPU time and they are finished under 30 minutes because my developers would have too many coffee breaks if that would be a different thing. So we plan to have this time even more down on 15 minutes to work efficiently and have a good coverage on testing. I think we agree that this is something you demanded to on-cloud for on-cloud. You wanted us to become a stable product and we invested heavily into QA. I think we are in a very good way. Thank you for that hint. Thank you for your feedback. We tried really to listen to you. But there is more. For the future of on-cloud, I think there is more mindset we need to have a shift in. There is stuff when you think about on-cloud, which is different today and in the past and we have a lot of discussions about this because in the former times we were doing it like this and now we are doing it like that or how should we do it? We think a lot about it and let me share with you what I think we should do in the future of on-cloud. First and most important, let us use latest technologies. Not only support the latest PHP version, which is very natural thing to do. Of course we are doing this. But there is more high-perform protocols HTTP too. We need to switch a lot in our stack to do this. We should go down that route. We need to do this. We are building new clients. The Phoenix is a project name for our standalone web front-end. The whole web front-end is reworked. It is split out of the core. It is a standalone front-end. You can run it in app or you can run it on a different server, however you like. This is ongoing work. It is based on the latest technologies, on the Vue.js framework, which is latest technology. We are really happy to work with that because it motivates us to use the latest and greatest stuff. It really works very nicely. You can learn Vue.js as a JavaScript developer in 30 minutes. The guide is really very cool and everyone can start work on the Phoenix project very quickly. I think this is a very good reason to use that framework. The iOS app and the app store is a bit older now. Software code is not so maintainable anymore. We decided some time ago to build a new one. Michael Stigl and his team around the clients is building a great mobile app. We hope that this code base will be exceptional in terms of education. We will show how to build an iOS app. With this example, we have gathered the best iOS developers we could get. I think I can say thank you to Felix Schwartz at this point. Outstanding developer who pushed this project so much with the rest of the iOS team. I recommend you to have a look at this code because this is really great software. This is where we want to go. We, talking about the clients, have a big challenge at OnCloud to care more about our APIs. We need to document them. We need to rework them. We need to redesign them. We need to be versioning for APIs to have proper change in APIs and our protocols. This is a demand I hear very often because you also want to use these APIs. All our clients need to use the same APIs in a clean way. I think this is something we were not so good in the past, but in the future, we really will care about this topic. All our clients will use the same API and this will be a documented thing. The protocols we use will be, of course, open standards alongside with all the stuff we will document on top. Product quality and coding styles, the way how we work, that move so much. The team was understanding the way we worked was not ideal and we were sitting together and the team found a very good way on how they wanted to work and changed. The change came from the team, which is making me very proud because I didn't need to use the hammer to put the change into the team, which is very difficult. The team is using sprint planning today and suddenly my planning capabilities are much better. I can tell you when will be the next release or the release after that. That's working quite nicely. You need to do it to understand how it works. This team is doing this in a very good way now. We want to work test-driven or behavior-driven, whatever it will be. We understood that we need to write the tests also upfront coding stuff to specify our features and to enlarge the acceptance test framework and to allow our product management to understand the feature set of OnCloud. There's some very, very cool projects out there who are doing this already and we are having a close look at this to learn from them. We really want to become better at this. I think this is very, very important for our motivation and to become experts at what we are doing. Last point is a bit more on the product. Our strategy was in the last two years, we had a big monolithic OnCloud. We split all this in parts, pushed out functionality into apps. Every app can be released independently today. There's a bug. We are very quick in fixing stuff because we don't need to make the QA and the release for all the software, we can just release that one single app and we can test this apps dependencies. This is so much more efficient. Modularity is so important. Now when we split out the front end with a Phoenix project out of the core, the core stays as a back end only part with some APIs and an app framework, managing users, groups, managing storage and files, and a bit more. Not so much more. It became small. This small core, it's the smallest core we ever had, it's now maintainable, it's now touchable. We can do change in that core. Before that, having all the front end code in there and mixed apps into all of that, we could not have made a change into the core, architectural change, real change. We need to think about to build an SDK like core. We need to think about to use industry leading framework components like this, for example, we could have a symphony based core, which is a PHP framework, which is used in lots of very major enterprisey projects and on cloud core could become one of them or we could at least use the components of symphony a lot. That would help so much to not code everything on our own, but use a logging mechanism which is used by so many projects. This is also part of being open source. This is also part of having good quality in the code. Clean modules based on industry leading framework components is bringing more efficiency to our development and is a big chance now because our core is ready to be touched. There's two topics which are important for me when we go hands on on the core. The user management needs some rework. I would like to propose the strategy to have OpenID connect everywhere. This is based on OAuth2. It's an authentication flow. OpenID connect is the technology I hear from even large companies. We want to get rid of single sign on SAML integrations. We want to use OpenID connect today because although the big IP firewalls are offering that protocol and it's a clever thing, it's much more easy to integrate with that. I think it makes sense that we in future have OpenID connect everywhere for every client, every part where we use authentication. This is something we need to do in the next months. The storage. Yeah. On-tot is often measured performance wise. What do you measure? You measure the upload and the download. And it is having quite good requirements on our performance. You've seen that right now. Olga has shown you some numbers. So let's care about the storage because if you build up a data center with modern SSD disk space, and this is bringing performance a lot, and you put on-tot on top, this on-tot, this on-tot needs to become not the bottleneck at this point and to utilize the performance of the underlying file system, whatever you use. And to provide this performance also, we on-tot to your users. Otherwise, there will be always a limit. So we want to really scale. We want to really scale with the performance and the file system. And there's different strategies we worked out. And Jörn Dreier is pushing a lot on this, designing and re-designing the APIs of the storage internally, the mechanisms we work and so on. And he's doing a workshop on the storage. Tomorrow, Jörn invited to discuss and to understand our plans and the details. This storage rework will be a major highlight for me in the on-cloud development I'm part of. And it makes me very proud to have that innovation into that product. So saying that, come to the workshop, I think this is really, really thrilling and innovation. So this is what I want to achieve in the future of on-cloud. But right now, we need to have some focus. And let me come down to the topics where we have identified, where we need to have the focus when we think about on-cloud and on-cloud's future. We are listening to the market and the customers and our partners a lot. This is very important, you need to understand that we are very open, come to us and speak to us, like on this conference, but at every day in the year. So we want to know what you're using on-cloud like and what you're doing with on-cloud. This is very important because we're building this for you. I think we can agree, and this is the top item here, the end user experience is one of the most important things. It's on purpose here on the top, and it's a reason why we build new clients. This is bringing offline capabilities to our clients, standalone clients for the web frontend, and this is the part where we really can say we want to become leading technology. There's lots of talks for that. I've highlighted some of them around the Phoenix project on the iOS. I really recommend to have a look at the iOS SDK. This is great software. Collaboration, I'm very happy to meet so many collaboration partners here, and that we have, that collaborating editing is a soul thing, and we have very good products out there integrating on-cloud nicely, but there's more. We can automate. The processes you need to do every day can be automated via APIs and via on-cloud, and this becomes full workflows, defining how you work with your files in your day-to-day life, and there's one big thing. I called it a-hiving for now. It's a topic about the old files. The most automations we saw is about how to spread files to people, to the right people, and to review something, maybe, before you spread the files. Then files become legacy and become old, and you want to get rid of them again, or you want to have them out of the focus, maybe somewhere else, on the other storage system, maybe, on the tape system. Let's call that topic archiving for now. This archiving becomes really important because on-cloud is seven years old now, and you're using on-cloud for quite some time, and the files in your on-clouds are quite old now, so archiving needs to be solved. Then the whole collaboration also tackles integrations into our software, like Outlook, and there's a talk about this. If you're interested more in the topic around archiving, please contact Patrick Meyer and me, and we can have another talk. There's nothing scheduled about this, but we can sit together on this topic. We are really interested on your requirements on this topic. On-cloud is a platform. So when we have users and groups and permissions and file access, what should we do with that? On-cloud becomes a platform, means let's build applications on top using files now, using the users available in the system. There are great examples for that. For instance, our customer portal. Tom Neatam has built that customer portal and will introduce it today in the talk. He will show what we built on top of on-cloud. Wind River is using it as a software delivery platform. This is great. This is a platform based on on-cloud, or our own brand. This is how you brand on-cloud. This is an on-cloud app, basically, and it's basically made on an on-cloud as a platform part. I think you have more ideas around that if you fully integrate on-cloud into your workflows and into your business processes. Of course, let me welcome the Kupano guys on the conference. They are doing groupware. Not so much the file thingies, but the groupware, like email and calendars and contacts. That was always a very close topic to on-cloud. I think it makes sense to integrate with groupware partners to have all these functionalities you need in your offices very nicely. I think Kupano will tell more about this. By the way, they have written an OpenID Connect server. We are evaluating that server right now to use it and to go into deeper collaboration with Kupano. Here again, the storage. We really have that focus on the storage to push the performance to the limit, to allow you to migrate your storage to other storages, like file storage to a free storage, for example, to migrate users from one storage to another storage. You can in future even migrate data from one on-cloud to another on-cloud, user-based, for example. The goal, of course, is to have a large, geodistributed scale so that you can work around the whole world using and utilizing data centers spread around the world. Here again, join the workshop from Jörn about scaling our storage. Hosting and operations becomes more and more important because our product, we never used it before. Now we are launching on-cloud online and we need to learn and have the detailed insights about how is on-cloud ready for an operator. I think some of you have more experience with that than us. We need to learn more about this. We provide today Docker images, latest technology around that. We care about cloud providers. We build up know-how in the RBS and Kubernetes area to provide help and consultant in these large deployment areas. But the product itself also needs to become ready for that. I think there's something to do and we will focus on improving our product to become ready for large deployments, for large updates, and also for topics like monitoring. You want to see what's happening in your system and if there's something wrong. There's lots of talks about that. This is an important topic for us and our experts telling you a bit more about our attempts on monitoring and what we're interested in what you're doing. About deployment on Kubernetes and Swarm, Thomas will tell you something about that. Let's have a deep dive into the large deployments on public clouds like RBS. The last item here is where we come from, enterprise file sync and share. But the focus here is not to have files and to share them. The focus here has shifted to the security area where we in the latest times have cared about ransomware attacks and to protect your data and file classifications. I think there's a talk about file classification from Patrick, document classification and policies. So this is the latest technology on how you can secure your data if you have sensible data. About all the file sync and share functionalities and our improvements and our roadmap, my team will now tell you the details, show you the roadmap. I'm very happy that you can get in touch with the team and have all your questions. Now Vincent, Oliver, Jesus, Michael, Patrick, at least these guys will show you the latest features and the future roadmap. Thank you and have fun.
 Because I forgot something really important.  Actually we want to thank our sponsors, OpenSuser, Univention, BoxCryptor and Copano.  I hope somebody is there already.  For sponsoring the conference, for making this possible.  And also thanks to our media partners, which is O'Reilly Media, D-Punk Verlag and of course  the awesome guys from the OpenSuser video team and C3Voc Media CCC team.  We all know they do a great job.  Thank you for all your efforts.  Hello, I want today to take the opportunity to start the conference with a bit of the  backgrounds on why we are doing all this and personally why I am doing this.  About the strategy and the future of Enclod.  And I will not talk too much about what we do.  I leave this to the team and the team will tell you in detail what we have achieved,  feature-wise and what we have planned on the roadmap.  And I am very proud of the team and want to present my team to you.  Let me talk a bit more about where we go and why we are doing this.  So let me start with introducing where I come from.  I founded a co-working space in Nuremberg and I always cared about how people work and how  they collaborate.  And in that co-working space I met Holger and he was sitting there and founding a little  company called Enclod, that was the first touch point for me with Enclod and soon I  started to work for Enclod because basically I am a full stack developer and not a co-working  space founder from where I come from.  But this is a topic which was very, very close to what brings my fulfillment in my life to  care about how people can work together efficiently and how people can work better together than  alone.  And the co-working space was a bit of an infrastructure I spent to the city here and Enclod was very  promising for me because I can take the opportunity to shape the future of collaboration.  How people work at home with their families share images and how people work in their  workplaces and for me it is very important to do this by exceptional user experience  and uncompromising privacy.  Privacy is so much important that Enclod becomes the most important software for me when I  start a startup.  When a team starts on a project you need to have that email communication and you need  to have good communication channels of course but then if you start working and collaborating  it comes down to Enclod so that you can have your files under your control, don't share  your stuff with people out there in the US and you really can collaborate in an easy  and efficient way.  So this is my vision, my very personal vision and where I come from working for Enclod now  for five years and this is why I do this.  So this vision is not so much away from the wordings of the Enclod companies using.  I'm very happy that we are very close together and let me go a bit more into the strategies  how we are doing this and I think the first thing is we are open, we are open source,  we will stay open always.  This is very important for all the teams.  I would have not a single developer anymore if we would change this because these people  are really into open source.  There is no question about it, we will stay open source and we learned something very  important so Enclod needs to be a sustainable project.  We want to spend our time we are investing into Enclod in a way where we know that Enclod  will always be there and Enclod will stay as a product and on the market.  We want to use Enclod also in ten years.  So open or sustainable is not so easy to do but it's this combination which is so important  and that's also why the Enclod foundation is important that we found it now and we achieved  this milestone and it's only one example but this is the next milestone in being open and  sustainable.  Christian Schmitz will have a talk on the Enclod foundation and if you want to be part  of the Enclod foundation have a look on the website or in the talk.  I think this is a great opportunity for everyone here.  We built extensible and secure code.  This means you all can collaborate, you can have your use cases built up on Enclod because  it's extensible and modular and we built a very professional software.  This secure code, it's enterprise grade code which is really, really possible to use in  a production environment.  This is really important and this is also a thing which changed a bit for Enclod.  Enclod was not always sort of when you think of high quality software but this is where  we want to go and this is a very, very major strategy.  We want to have professional development involved.  I want to have people involved in this project who really know what they are doing when they  start coding and this defines our community a lot for me.  We are building an ecosystem with partners and people in the community who are experts  at what they are doing about encryption, about storages, about how to handle files, about  performance and we are listening to people on the use cases and this is not only a project  because we are doing what we want.  We are doing this together with you in a huge ecosystem.  About our partner strategy, Jörg, our partner manager will have a talk.  He is quite new to the company and he is doing an awesome job.  Thank you, Jörg.  I really recommend you to be part of that talk.  The last point here is one of the most important things.  Innovation and leading technology is our passion.  Enclod is all about passion.  These people do this because they are really convinced and motivated about this idea and  they have all their own reasons why they are doing this.  These are all developers, right?  We really strive to have, we want to be experts at what we are doing and these people, this  team I am working with, they are experts at what they are doing.  They are really a great team.  They are so good in what they do and they are getting better and better.  Enclod needs to bow to that.  We need to use latest technology.  We can't have experts on legacy technology.  It's not working.  Latest technology for Enclod means we will have great developers working on Enclod.  This is a very important thing and a very important strategy.  These people, the smartest people I know around development, they will bring innovation in  an area where we have big competitors.  But our product, our little community and ecosystem is bringing a lot of innovation  to that area.  I am so proud of that team and I am proud to see you here and I want to welcome you to  the Enclod conference in 2018.  Thank you.  This is not all.  Let's have a little deep dive in what we achieved.  According to these strategies, one of the most important things is to have a stable  and high quality software and hear some numbers about what we achieved in our quality assurance.  The newest, we have coding standards now.  We have static code analyzers and we have improved testing frameworks.  We care about our quality.  Having a close look at our numbers for the testings, we have more unit tests because  we just have unit tests with every pull request we do.  We had unit tests before, but unit tests are not enough.  We also have acceptance tests and these acceptance tests have grown to really ensure that our  software is doing what we expect it to do.  We have grown the acceptance tests to up to 2,200 tests and it is continuously growing.  This is a huge shing.  Especially because these tests are not run in one environment.  So some of you have one on-cloud running and we care about a huge test matrix.  We test with different databases, with different kinds of storages.  We test with antivirus integrations or not.  We test encrypted storages or not.  We test different PHP versions and so many combinations of all of that, all of our apps.  This is a huge test matrix and it has grown the coverage we have achieved in this test  matrix.  We have a dedicated QA team built up for this to achieve this because this is a major, really  major task in the last years and we have invested a lot.  So as Ruby has already said, we have also gained some success out of that.  It's not like we have less support tickets because on-cloud is not running anymore.  We have while having a growing customer base, less support tickets coming in and the support  tickets which are open right now are at 60% of what they have been.  Half a year ago, this is this 60% number.  This is so awesome.  And if you work with on-cloud in the latest version, I think they will release today,  be today about the 10.10.  Vincent, is that correct?  We are really proud about this version because this version will be the most stable and best  on-cloud we ever had.  Thanks Vincent and team.  Few more numbers which are really impressive.  So I was astonished by my QA team.  Really, we are running the whole test suite on over 100 of the workers and they are doing  2,000 days of testing time each month.  This is so much.  They are running every night, they are running on every pull request, on the pull request.  The tests need eight hours CPU time and they are finished under 30 minutes because my developers  would have too many coffee breaks if that would be a different thing.  So we plan to have this time even more down on 15 minutes to work efficiently and have  a good coverage on testing.  I think we agree that this is something you demanded to on-cloud for on-cloud.  You wanted us to become a stable product and we invested heavily into QA.  I think we are in a very good way.  Thank you for that hint.  Thank you for your feedback.  We tried really to listen to you.  But there is more.  For the future of on-cloud, I think there is more mindset we need to have a shift in.  There is stuff when you think about on-cloud, which is different today and in the past and  we have a lot of discussions about this because in the former times we were doing it like  this and now we are doing it like that or how should we do it?  We think a lot about it and let me share with you what I think we should do in the future  of on-cloud.  First and most important, let us use latest technologies.  Not only support the latest PHP version, which is very natural thing to do.  Of course we are doing this.  But there is more high-perform protocols HTTP too.  We need to switch a lot in our stack to do this.  We should go down that route.  We need to do this.  We are building new clients.  The Phoenix is a project name for our standalone web front-end.  The whole web front-end is reworked.  It is split out of the core.  It is a standalone front-end.  You can run it in app or you can run it on a different server, however you like.  This is ongoing work.  It is based on the latest technologies, on the Vue.js framework, which is latest technology.  We are really happy to work with that because it motivates us to use the latest and greatest  stuff.  It really works very nicely.  You can learn Vue.js as a JavaScript developer in 30 minutes.  The guide is really very cool and everyone can start work on the Phoenix project very  quickly.  I think this is a very good reason to use that framework.  The iOS app and the app store is a bit older now.  Software code is not so maintainable anymore.  We decided some time ago to build a new one.  Michael Stigl and his team around the clients is building a great mobile app.  We hope that this code base will be exceptional in terms of education.  We will show how to build an iOS app.  With this example, we have gathered the best iOS developers we could get.  I think I can say thank you to Felix Schwartz at this point.  Outstanding developer who pushed this project so much with the rest of the iOS team.  I recommend you to have a look at this code because this is really great software.  This is where we want to go.  We, talking about the clients, have a big challenge at OnCloud to care more about our  APIs.  We need to document them.  We need to rework them.  We need to redesign them.  We need to be versioning for APIs to have proper change in APIs and our protocols.  This is a demand I hear very often because you also want to use these APIs.  All our clients need to use the same APIs in a clean way.  I think this is something we were not so good in the past, but in the future, we really  will care about this topic.  All our clients will use the same API and this will be a documented thing.  The protocols we use will be, of course, open standards alongside with all the stuff  we will document on top.  Product quality and coding styles, the way how we work, that move so much.  The team was understanding the way we worked was not ideal and we were sitting together  and the team found a very good way on how they wanted to work and changed.  The change came from the team, which is making me very proud because I didn't need to use  the hammer to put the change into the team, which is very difficult.  The team is using sprint planning today and suddenly my planning capabilities are much  better.  I can tell you when will be the next release or the release after that.  That's working quite nicely.  You need to do it to understand how it works.  This team is doing this in a very good way now.  We want to work test-driven or behavior-driven, whatever it will be.  We understood that we need to write the tests also upfront coding stuff to specify our features  and to enlarge the acceptance test framework and to allow our product management to understand  the feature set of OnCloud.  There's some very, very cool projects out there who are doing this already and we are  having a close look at this to learn from them.  We really want to become better at this.  I think this is very, very important for our motivation and to become experts at what we  are doing.  Last point is a bit more on the product.  Our strategy was in the last two years, we had a big monolithic OnCloud.  We split all this in parts, pushed out functionality into apps.  Every app can be released independently today.  There's a bug.  We are very quick in fixing stuff because we don't need to make the QA and the release  for all the software, we can just release that one single app and we can test this apps  dependencies.  This is so much more efficient.  Modularity is so important.  Now when we split out the front end with a Phoenix project out of the core, the core  stays as a back end only part with some APIs and an app framework, managing users, groups,  managing storage and files, and a bit more.  Not so much more.  It became small.  This small core, it's the smallest core we ever had, it's now maintainable, it's now  touchable.  We can do change in that core.  Before that, having all the front end code in there and mixed apps into all of that, we  could not have made a change into the core, architectural change, real change.  We need to think about to build an SDK like core.  We need to think about to use industry leading framework components like this, for example,  we could have a symphony based core, which is a PHP framework, which is used in lots  of very major enterprisey projects and on cloud core could become one of them or we  could at least use the components of symphony a lot.  That would help so much to not code everything on our own, but use a logging mechanism which  is used by so many projects.  This is also part of being open source.  This is also part of having good quality in the code.  Clean modules based on industry leading framework components is bringing more efficiency to  our development and is a big chance now because our core is ready to be touched.  There's two topics which are important for me when we go hands on on the core.  The user management needs some rework.  I would like to propose the strategy to have OpenID connect everywhere.  This is based on OAuth2.  It's an authentication flow.  OpenID connect is the technology I hear from even large companies.  We want to get rid of single sign on SAML integrations.  We want to use OpenID connect today because although the big IP firewalls are offering  that protocol and it's a clever thing, it's much more easy to integrate with that.  I think it makes sense that we in future have OpenID connect everywhere for every client,  every part where we use authentication.  This is something we need to do in the next months.  The storage.  Yeah.  On-tot is often measured performance wise.  What do you measure?  You measure the upload and the download.  And it is having quite good requirements on our performance.  You've seen that right now.  Olga has shown you some numbers.  So let's care about the storage because if you build up a data center with modern SSD  disk space, and this is bringing performance a lot, and you put on-tot on top, this on-tot,  this on-tot needs to become not the bottleneck at this point and to utilize the performance  of the underlying file system, whatever you use.  And to provide this performance also, we on-tot to your users.  Otherwise, there will be always a limit.  So we want to really scale.  We want to really scale with the performance and the file system.  And there's different strategies we worked out.  And Jörn Dreier is pushing a lot on this, designing and re-designing the APIs of the  storage internally, the mechanisms we work and so on.  And he's doing a workshop on the storage.  Tomorrow, Jörn invited to discuss and to understand our plans and the details.  This storage rework will be a major highlight for me in the on-cloud development I'm part  of.  And it makes me very proud to have that innovation into that product.  So saying that, come to the workshop, I think this is really, really thrilling and innovation.  So this is what I want to achieve in the future of on-cloud.  But right now, we need to have some focus.  And let me come down to the topics where we have identified, where we need to have the  focus when we think about on-cloud and on-cloud's future.  We are listening to the market and the customers and our partners a lot.  This is very important, you need to understand that we are very open, come to us and speak  to us, like on this conference, but at every day in the year.  So we want to know what you're using on-cloud like and what you're doing with on-cloud.  This is very important because we're building this for you.  I think we can agree, and this is the top item here, the end user experience is one  of the most important things.  It's on purpose here on the top, and it's a reason why we build new clients.  This is bringing offline capabilities to our clients, standalone clients for the web frontend,  and this is the part where we really can say we want to become leading technology.  There's lots of talks for that.  I've highlighted some of them around the Phoenix project on the iOS.  I really recommend to have a look at the iOS SDK.  This is great software.  Collaboration, I'm very happy to meet so many collaboration partners here, and that we have,  that collaborating editing is a soul thing, and we have very good products out there integrating  on-cloud nicely, but there's more.  We can automate.  The processes you need to do every day can be automated via APIs and via on-cloud, and  this becomes full workflows, defining how you work with your files in your day-to-day  life, and there's one big thing.  I called it a-hiving for now.  It's a topic about the old files.  The most automations we saw is about how to spread files to people, to the right people,  and to review something, maybe, before you spread the files.  Then files become legacy and become old, and you want to get rid of them again, or you  want to have them out of the focus, maybe somewhere else, on the other storage system,  maybe, on the tape system.  Let's call that topic archiving for now.  This archiving becomes really important because on-cloud is seven years old now, and you're  using on-cloud for quite some time, and the files in your on-clouds are quite old now,  so archiving needs to be solved.  Then the whole collaboration also tackles integrations into our software, like Outlook,  and there's a talk about this.  If you're interested more in the topic around archiving, please contact Patrick Meyer and  me, and we can have another talk.  There's nothing scheduled about this, but we can sit together on this topic.  We are really interested on your requirements on this topic.  On-cloud is a platform.  So when we have users and groups and permissions and file access, what should we do with that?  On-cloud becomes a platform, means let's build applications on top using files now, using  the users available in the system.  There are great examples for that.  For instance, our customer portal.  Tom Neatam has built that customer portal and will introduce it today in the talk.  He will show what we built on top of on-cloud.  Wind River is using it as a software delivery platform.  This is great.  This is a platform based on on-cloud, or our own brand.  This is how you brand on-cloud.  This is an on-cloud app, basically, and it's basically made on an on-cloud as a platform  part.  I think you have more ideas around that if you fully integrate on-cloud into your workflows  and into your business processes.  Of course, let me welcome the Kupano guys on the conference.  They are doing groupware.  Not so much the file thingies, but the groupware, like email and calendars and contacts.  That was always a very close topic to on-cloud.  I think it makes sense to integrate with groupware partners to have all these functionalities  you need in your offices very nicely.  I think Kupano will tell more about this.  By the way, they have written an OpenID Connect server.  We are evaluating that server right now to use it and to go into deeper collaboration  with Kupano.  Here again, the storage.  We really have that focus on the storage to push the performance to the limit, to allow  you to migrate your storage to other storages, like file storage to a free storage, for example,  to migrate users from one storage to another storage.  You can in future even migrate data from one on-cloud to another on-cloud, user-based,  for example.  The goal, of course, is to have a large, geodistributed scale so that you can work around the whole  world using and utilizing data centers spread around the world.  Here again, join the workshop from Jörn about scaling our storage.  Hosting and operations becomes more and more important because our product, we never used  it before.  Now we are launching on-cloud online and we need to learn and have the detailed insights  about how is on-cloud ready for an operator.  I think some of you have more experience with that than us.  We need to learn more about this.  We provide today Docker images, latest technology around that.  We care about cloud providers.  We build up know-how in the RBS and Kubernetes area to provide help and consultant in these  large deployment areas.  But the product itself also needs to become ready for that.  I think there's something to do and we will focus on improving our product to become ready  for large deployments, for large updates, and also for topics like monitoring.  You want to see what's happening in your system and if there's something wrong.  There's lots of talks about that.  This is an important topic for us and our experts telling you a bit more about our attempts  on monitoring and what we're interested in what you're doing.  About deployment on Kubernetes and Swarm, Thomas will tell you something about that.  Let's have a deep dive into the large deployments on public clouds like RBS.  The last item here is where we come from, enterprise file sync and share.  But the focus here is not to have files and to share them.  The focus here has shifted to the security area where we in the latest times have cared  about ransomware attacks and to protect your data and file classifications.  I think there's a talk about file classification from Patrick, document classification and  policies.  So this is the latest technology on how you can secure your data if you have sensible  data.  About all the file sync and share functionalities and our improvements and our roadmap, my  team will now tell you the details, show you the roadmap.  I'm very happy that you can get in touch with the team and have all your questions.  Now Vincent, Oliver, Jesus, Michael, Patrick, at least these guys will show you the latest  features and the future roadmap.  Thank you and have fun.
ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_0_203.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_204_251.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_252_323.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_324_407.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_408_491.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_492_587.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_588_659.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_660_707.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_708_767.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_768_899.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_900_1007.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_1008_1079.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_1080_1295.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_1296_1487.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_1488_1547.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_1548_22451.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_22452_22499.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_22500_22727.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_22728_22835.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_22836_22895.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_22896_23051.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_23052_23099.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_23100_23399.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_23400_28523.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_28524_28931.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_28932_28979.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_28980_29147.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29148_29411.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29412_29519.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29520_29675.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29676_29795.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29796_29975.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_29976_30047.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_30048_30599.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_30600_30671.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_30672_30779.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_30780_30935.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_30936_31379.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_31380_31427.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_31428_31739.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_31740_31811.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_31812_32207.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_32208_32315.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_32316_32375.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_32376_32567.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_32568_33419.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_33420_52079.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_52080_52223.png ownCloud_conference_2018_ownCloud_11_-_The_strategic_approach_to_the_future_of_ownCloud_Xx0yM9jBKfc_52224_52367.png