We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Kolab Summit 2.0 - Panel Discussion: Putting the freedom back in the cloud

00:00

Formal Metadata

Title
Kolab Summit 2.0 - Panel Discussion: Putting the freedom back in the cloud
Title of Series
Number of Parts
63
Author
Contributors
License
CC Attribution 3.0 Unported:
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.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Join us this June 24-25 in Nürnberg, Germany for the second annual Kolab Summit. Like last year's summit, we've accepted the invitation of the openSUSE Community to co-locate the summit with the openSUSE Conference, which will be held June 22-26 in the same location. And because we have some special news to share and celebrate, we're also putting on a special edition Kolab Taster on Friday June 24th. The overarching theme for this year's summit will be how to put the freedom back into the cloud.
13
38
Thumbnail
23:08
44
Thumbnail
25:53
Point cloudRight angleoutputNetwork topologyStreaming mediaXMLUML
DeterminismSound effectOpen setCopyright infringementLecture/Conference
Point cloudOpen sourceResultantCollaborationismCubeFrequencyVisualization (computer graphics)Materialization (paranormal)DigitizingDisk read-and-write headComputing platformLevel (video gaming)Lattice (order)Group actionSinc functionComputer hardwareSoftwareBranch (computer science)Euler anglesInclusion mapMoment (mathematics)Exterior algebraMultiplication signPresentation of a groupStack (abstract data type)Heegaard splittingRight angleFeasibility studyIntegrated development environmentFocus (optics)Goodness of fitSystem callFile formatLecture/Conference
Point cloudWeb-DesignerPhysical systemSource codeWritingOffenes KommunikationssystemProper mapSoftware developerPrototypeMereologyGoodness of fitStandard deviationConnectivity (graph theory)SI-EinheitenLevel (video gaming)Formal languageSoftware frameworkRight angleIntrusion detection systemDifferent (Kate Ryan album)2 (number)Meeting/Interview
Hacker (term)Point cloudElectronic mailing listMoment (mathematics)Goodness of fitComputer virusData managementLevel (video gaming)1 (number)Point (geometry)Sign (mathematics)EmailDependent and independent variablesComputer clusterOnline helpTask (computing)Self-organizationRight angleExtension (kinesiology)CASE <Informatik>Exception handlingSystem callSoftware developerBitQuicksortShared memoryLecture/Conference
Computer animation
Transcript: English(auto-generated)
Well, I mean, I propose we just turn the Q&A into an open discussion, actually. Does it work? Excellent. Alright, questions, comments, thoughts, input?
In general, it's good to see you're making yourself more visible in the ecosystem. I think we'll need to use the microphone for the value of the stream.
Microphone is coming. So, let's not stand in front of the speaker because that will entice interesting surround effects.
My comment actually is that being one of the people who organized last year's Caleb Simmons, first of all, I'm very happy to see you guys putting this off this year, so thanks for that.
And also, I think it's a good thing to be more visible as you're doing with the Caleb Tasters and in the Open Power Foundation. And it's also a very targeted visibility, I guess. So, you're profiling yourself as a full stack technology partner, not just the group of niche you're fulfilling.
And in that aspect, since you're currently also looking at the hardware side and developing the software side yourself, what are your insights on other open source platforms you might want to connect to in the future?
I mean, you've done a lot of work on Roundcube, you've done a lot of work with the KE community, you're currently also doing a lot of stuff yourself, you are on Cube and some other stuff. Where do you see that going? Do you see more collaboration there? Well, I mean, we, as you know, oh, now it's getting interesting, the audio engineer.
So, yes, thank you for the comments and the questions. Indeed, we've deliberately started to work more professionally also in the way we position ourselves and of course communicate, and that's a good thing.
Because while geeks may not be overly enthused always by design, although personally, to be honest, I always was, but it is the only way that you can ever really reach a large audience by doing this professionally.
I mean, that level also must be professional and we had the huge, fortunate situation that we could win Giles over to do our creative director. In fact, I remember that Giles approached me at the last Collab Summit in The Hague with the thought of maybe doing this full-time for us.
So, it's like summit to summit improvement in a way. And of course, we were ecstatic to have him with us because his work is all over the taster format, it's all over our corporate design, it's in the way that you see our visuals now, our materials for partners develop,
all of that is his work, right? I mean, he is the person leading that. And given that he was managing director of a creative digital agency in London that he had co-founded and was running that was very successful, one of the celebrated agencies in London, in fact, and decided to leave that behind to join Collab and push the Collab story with us,
for me, that was an incredibly moving moment, actually. I mean, I was humbled, to be honest. On the technical side, of course, we will continue to work with others. I mean, we work with LibreOffice now a lot. There is a couple of others I am sure we will work with,
although on the technical side, I mean, Aaron is the guy who makes that call, right, together with Jeroen. These two guys, when they put their heads together, magic things happen. I get informed of the results. So, but yeah, I mean, the only way we actually do this is
by engaging with Upstream, by doing it in a collaboration. For us, Upstream is always king. If it is not going into the Upstream, it is a liability. Simple as that. So, we want the Upstreams. I mean, we are working very, very hard to convince the Upstreams. In fact, if you follow how Cube has come about,
we are working extremely hard over a long period of time to show these are the shortcomings we need to address to help people understand why certain approaches were not sustainable if you want to run this in a professional environment, why certain things had to be addressed. We gave presentations about that.
We had long meetings about that. I mean, there were multiple meetings of the KDPIM community through which we actually communicated all of this and then we ultimately said, all right, this is the way it needs to go and we'll do it now. Please, everyone who wants to join, join in. But we always try to do things in the most inclusive way possible.
We take a lot of extra effort and work often to do it the right way. Because for us, the goal needs to be that the entire community gets stronger. We cannot fragment our community. Splitting away very often seems like the easiest solution. Forking, a lot of people think, oh, let's fork this.
I don't like how this goes, let's fork it. And sometimes that may be necessary. There may be moments when there is no other alternative. But at the same time, of course, fragmentation also has a cost. So we try to reduce the fragmentation to not just create yet another branch on something,
but work with the community, make it upstream. And then build a stronger community as the result. So yes, that's very much an attitude for us in the future as well. Aaron, anything you want to add? Jeroen, go for it.
So a part of what we do now is be the glue between a lot of components. This makes us currently maintain stuff
and write stuff in seven languages, Aaron? Seven languages. This is overly cumbersome. I speak most of them. And sometimes I work in C on something that is Cyrus AMAP. To need to happen to resolve actual issues is just quite costly.
It doesn't allow me to learn and experience C at a pace that actually makes me a proper good C developer. And the same goes for Python. And we have Erlang, and we have PHP, and we have C++. And so it becomes overly difficult. Part of what you'll be seeing online
will shift that. We have set Elixir, Phoenix and Elixir, as a web development framework, as the standard to start prototyping and things. So you'll see a bunch of those prototypes,
maybe screencasts, or what we otherwise do in agile development retrospectives. These are weekly occurrences. We think we have something that is sufficiently visually appealing and not embarrassing. We'll post that online. The source code will be online, so you could look it up yourself and laugh at us.
But a lot of prototyping. So new ideas that we can whip up something for in two to four hours maybe, and then decide whether or not that's indeed what we want and what we would like to see and how it should work. And then let the rinse repeat. Do it again. Get a different idea. Prototype that.
Yep. Thank you. And by the way, just to point it out, git.collab.org is where you want to have a look. That is where we go for our own sprint planning developments and so on and so forth. It's an open system. Everyone is welcome to make an account there and get active.
You can be part of this with zero burden. And you're going to be working in the exact same system as us. There's no second system. We're not having a secret internal system that's the system. I think if I stand here and start singing. Who's next?
Hello. This is my chance. So I wanted to ask, can Junior collaborate or help to Collab Summit
by having few skills? Well, I'm asking the level of knowledge. Which can be at Junior level? Oh yeah. I mean, we have use for people at every level. I mean, we generally follow a culture
of giving people things to tackle that they feel that they can tackle. And then if we see that they need help, we help them. But often people are also capable of doing more than they think they are. So we try to work with people at all levels.
And yes, a senior person might be able to do certain tasks a lot faster or better. But there's always things that even at junior level you can do. In fact, I believe we need a lot more junior people to get involved. Because junior people will turn to senior people at some point. And so we have plenty of things that can get done.
So you are very much encouraged to get involved. Thanks. And I mean, just hit the mailing list or the RFC channel or whatever. Just approach us. We are generally pretty approachable. I hope.
I mean, most of us tend to be usually quite friendly. I haven't seen anyone bite anyone else yet. So, yes, I am. Well, I mean, he's Dutch. You've got to forgive him. He's blunt, but he means well. I mean, with him you never have a doubt
of what he's actually thinking, which has its own merit. But once you get to know him, he's actually a very sweet character. He just hides it very well. All right. Who else?
Any more comments? Any more thoughts? Sorry, what?
An artistic moment. Well, that'd be Aaron's thing. Aaron went out to Nuremberg last night to do karaoke. So, actually, Peter, you went with him. So, uh-oh.
Yeah, I mean, one of the organizational principles from day one has been to actually have fun. Because, I mean, while we want to save the world, you know, we don't want to end up
as sour, bitter people at the end of it. So, you know, we need to somehow also have a little bit of fun. Therefore, it's a... I hope at least it's an interesting place to work. So, anyway, and by the way, we are always looking for people who also
want to work full-time for us or part-time, right? I mean, don't hesitate to send us your CV. Apply, please, because we're constantly on the lookout for people. And especially good people, of course, are always sought by anyone. We realize that. But we have a pretty cool team. I mean, working with the likes of, you know,
Aaron and Jeroen has its merits. They have a lot of insight to share. And even people who joined us as junior developers, such as Christian, have meanwhile taken on a lot of responsibility,
including in management responsibilities by now. So, we believe in people, and we believe in actually allowing people to grow and helping them to grow into new roles. I mean, Lisha, she's been joining us, you know, in the Colab Now support realm, and is now, you know, starting to organize the support,
as well as help us with the conference organization. I mean, the Colab Summit here was, to a very large extent, her work. So, thank you very much for that, Lisha. So, yes, we want people to grow.
And if you want to grow with us, apply, please.
I think that concludes it. Lisha is giving me the almighty nod of conclusion, so, it's fine. I mean, yeah. That again.
I know. All right. In that case, thank you all very much. Enjoy the rest of the afternoon. Hang around. Cheer for Switzerland. Except the ones from Poland. They are excused. We forgive you, Alec. Ah, yes, yes, yes.
And if you still want one of those Zig bottles, we will, at some point, these beautiful red ones, right, sign up on Conference, Summit Colab Org, and get your red bottle, because we will otherwise be taking them back with us.
So, make sure that we have very little to load, please. All right. Thank you very much.