Canonical Meet & Greet
Open source needs contributors who never write a line of code
A painfully slow student laptop got a new life when a friend installed Ubuntu on it, and that moment pulled a social sciences student toward infrastructure software. Product manager Miona Aleksic, who runs Canonical's LXD and MicroCloud products, and three colleagues explain why so few women contribute to open source and why that matters for everyone who builds on it. So where does a newcomer actually begin?
Get concrete first steps for joining an open source project, with or without coding skills
In short
In this Canonical meet and greet, product manager Miona Aleksic and colleagues Lidia, Andreea Munteanu and Varshi describe their paths into open source and how Canonical runs as a remote-first company. They argue that anyone can contribute to open source, through code, documentation, feedback or community organising, and that the field needs more women for diversity of thought.
“And then we actually installed Ubuntu on my laptop, and it gave it a new life.”
“So it doesn't, you don't need to be a software engineer, you can use your soft skills as well and just be a part of the community and, you know, facilitate this collaboration.”
What you will learn
- Find beginner-friendly open source work by filtering a project's GitHub issues by labels such as easy
- Contribute without coding through documentation fixes, product feedback, beta testing and organising meetups
- Approach project maintainers directly or join public channels such as Mattermost to ask where help is needed
- Apply written, asynchronous habits like set agendas, shared notes and recorded demos to coordinate teams across time zones
- Prepare for a hiring process that includes a written interview, psychometric assessments, technical evaluation and panel interviews
Key takeaways from the speaker
- Meet & Greet sessions
Details
- Level
- All levels
- Format
- Demo
- Technical depth
- Introductory technical
- For
- Early career, Career changer, Mid-career
- Length
- 28:40
- Published
- May 2023
Questions this talk answers
How can a beginner start contributing to open source?
Browse projects that interest you, filter GitHub issues by easy labels, and reach out to the listed maintainers to ask how you can help. Public channels such as Canonical's Mattermost let you talk directly with developers.
Do you need to be a software engineer to contribute to open source?
No. The panel says documentation improvements, showcasing how to use a product, giving feedback and organising meetups all count as contributions.
How does a remote-first company keep a global team working well?
Canonical groups new hires into time zone specific teams, relies on written and asynchronous communication, and brings teams together in person roughly every six months for a week-long sprint.
Why are there so few women in open source, and why does it matter?
The panel suggests open source is often done in free time, which favours people with few outside responsibilities. They argue software meant for everyone needs different people and mindsets building it.
What is Canonical's hiring process like?
It includes a written interview, psychometric assessments, technical evaluations and panel interviews, and candidates may be redirected to a role that fits them better.
About this talk
Join this session to learn more about Canonical and our work in open source
Topics
Highlights
- How Ubuntu revived a student's laptop (82 s)
- Contributing to open source without code (54 s)
- Why open source needs more women (73 s)
Hi, everyone. Thank you for joining us for this meet and greet with some of the lovely women working at Canonical. We really would like this to be a meet and greet. So we will, of course, talk a little bit and tell you a little bit about ourselves. But please feel free to drop your questions in the chat and ask us really anything that you're curious about, and we will happily share. If I start with just introducing myself, my name is Miona Aleksic.
I'm a product manager working for Canonical and I take care of some infrastructure products. We have a virtualization platform called Lexi and also our micro cloud offering. I started my career in telecommunications and I'm not actually, well, I'm not an engineer by education. I come from social sciences, but I kind of took my strengths and apply them into the technology field, starting first as a program manager where I mostly use my kind of organization.
People skills. But then over time, I just got, I was curious and I got deeper and deeper and deeper into tech and now I work with some very geeky things. So I've been in Canonical for about a year and a half. I really like it. I love working with everyone. I love working with my engineering team. And again, yeah, feel free to ask any questions and I would happily share my experience.
Thanks, Miona. Hi, everyone. My name is Lidia. Today, I have a very coarse, weird voice. So please follow that. Um, I'm a senior user researcher in the design team. Um, my job is to see what users things feel and do about all of our products. And then based on that, we can change the goals, the strategy, the design and make better experiences for everyone. We try to do things that are accessible and accessible.
Hello everyone, my name is Lidia. Today I have a very coarse, weird voice. I'm a senior user researcher in the design team. My job is to see what users think, feel and do about all of our products. And then based on that, we can change the goals, the strategy, the design and make better experiences for everyone. We try to do things that are accessible and that includes different locations, different backgrounds, etc.
Before I joined Dynamical a year and a half ago, I was living in Singapore where I did a PhD and I work in a couple of startups. And I'm originally from Spain. I'll go next then. Hello, I'm Andrea. I'm originally from Romania. I work as a product manager, similarly to Miona, but on machine learning tooling. So I'm tempted to say it's the cool thing these days. I started in Telco as well. I think that's by chance. And I have an engineering background, but I quickly understood that I like data science and I like playing with data.
So I evolved and I grew my career there. I've been in Canonical for three years now. I'll have my anniversary in two months and I'm quite excited about that. I started here doing data science and doing a lot of data work and I moved or changed roles a year ago and I'm quite excited about it. I figured it out once I joined that I like working here and it's a great place to actually grow your career, to discover what you like as well, because there are tons of opportunities that you can explore and also tons of very passionate people that you can easily learn from and improve your skills.
So I'm the last one. Thanks Andrea. Hi everyone. It's great to have all of you be here and be a part of this chat. Feel free to use the chat option and engage with us, ask questions. I'm Varshi. I'm the engineering director for our internal DevOps teams. My teams are mostly engineering teams that work closely with our operations team to identify and build solutions that can help manage, install applications, enterprise applications easily, simplify the operations a bit more for managing infrastructure at scale.
I have a background in technical product management and architecture before Canonical and I had a very interesting journey similar to Andrea. I had applied for a different role when I had joined Canonical and through my conversations with leadership and now my colleagues, I will be redirected me to a different role, which was the perfect fit for me.
So that's like something unique about Canonical hiring process. If the hiring manager or lead feels that you are not a right fit for a particular role, but a good fit for the organization, they would redirect you and they would empower you to apply for the other role. So before we dive deeper into what Canonical is, I just wanted to get a handle off whether you know anything about Canonical at all.
So maybe if you can go to the chat, type in a couple of words about what you know about Canonical. If you don't know anything about it, that's fine as well. So let's see if anyone here knows what Canonical does. Should I break the news and say Ubuntu Varshi? Yeah. Okay, so Ubuntu is something I think a few of you at least would must have heard about.
Canonical is the publisher of Ubuntu, but beyond Ubuntu, we have a much wider vision and mission. We want to be the company that delivers the best experience of open source. We want to amplify the positive impact of open source, whether it is in platforms or Ubuntu or applications. So deploying the best data source experience or AI experience or to device.
So your smart earphones or your bikes, OSs and software for that. So we are into everything. And as a company, we want to provide the best experience of open source. If you think about it for organizations and even individuals, it is very hard sometimes for us to consume open source in an effective way. Like how do you figure out what software to use?
How do you store it, maintain it? How do you make sure that it is something that's secure? And that's the gap that we are trying to fill in. We want to enable our clients, our organizations and individuals to be able to innovate on open source and to be able to find a cost effective way of consuming open source.
A lot of organizations now are becoming remote after COVID or have a hybrid sort of a work culture. For Canonical, though, we were founded in 2004. And now we have a thousand employees in over over 70 countries. So ever since we were founded, we were a remote first company. So over 80% of our workforce is remote. And though that presents like some interesting challenges on how do you manage working in APAC and America simultaneously?
Or how do you manage a workforce that is not working in the same time zone? We have found some effective processes around how to do that. So one of the things that we do is if we hire someone, we try to put them in a time zone specific team. So if you're hired in APAC, most probably you'll have a team that is working in similar time zones as you.
Thailand, Philippines, India, Japan. So you'll have teammates who have a significant overlap with you. Or if you, the other thing that we do is we try and prioritize travel over commute. So if you are, we try and meet at least once every six months for a week and we work together as a team. We identify what our focus area is for next six months and we work together as a team and have fun together.
In the last year itself, we've been to Frankfurt, Copenhagen, Prague, and we're planning on going to Riga next. So it's a very dynamic and a very diverse sort of a culture. And I let Miona go a bit further. Actually, Andrea, I let Andrea go a bit further into open source and its impact on women. Thank you, Varshi.
And it's great that you actually captured it that we, it's not that we are very much a multicultural environment, but we also explore new cultures by meeting our colleagues around the world. But when we think of open source, I firstly met open source when I was a student, I started using Ubuntu back then, but then over time, the more that I grew, I figured it out that actually I can use other tooling.
And I already mentioned that I'm a product manager for AIML. And the great part of it is that often we get questions on, hey, but how can I get started? How can I actually use it? It's simple, you go on our website, or on one of our websites, you go on ubuntu.com, and you think of what are your needs, and you can easily deploy or install, let's say any product you want.
What does it mean? Well, it means that anyone can try it out. And as Varshi already said, anyone can actually innovate using our products. And there's no barriers. It really goes back to, well, we can all do it, and it's just our responsibility to try it out. I'm curious, Miona. I see you agree with me. Would you like to help me?
Yeah, I mean, you mentioned that you used Ubuntu before, and I can share maybe my story of how I came to use Ubuntu. Because as I said, I come from social sciences, so I never really was too deep into technology. And then I was somewhere in the middle of my university studies, and my computer was getting extremely slow.
It was running one of the older Windows versions, and it just wasn't working properly. It would take forever to boot. It was becoming super slow. I couldn't do my assignment. But I was a poor student, and I had no money to actually buy a new computer. And then I had a friend that was a software engineer that recommended, oh, why don't you try installing Ubuntu?
And I was like, what is that? And it's like, it's a Linux operating system. But isn't that not user-friendly and weird and so on? And it's like, no, no, no, it's fine. And then we actually installed Ubuntu on my laptop, and it gave it a new life. Like, it would turn on in like 10 seconds, you know, I could do everything that I needed to do.
And that's when I first realized that, hey, you know, there are all these people that are creating software that is accessible to everyone, that is useful, that is user-friendly. And you, I mean, you maybe just don't know about it, because it's not necessarily visible to you, but it's out there. And there's this whole community of people that care about it, and then, you know, contribute to it, and, you know, spend their free time, actually.
Like, not just, you know, during working hours, but actual free time to make it better. And I think that's pretty cool. I'll add one more thing here, because you mentioned about, hey, you might know about it, or it might not be user-friendly. And it's interesting, because I think in Canonical, first of all, you have a lot of materials to use it.
But also, we started spending more time educating people and helping them get started on AIML. I can easily recall that in February, I was at PyCon Namibia just playing around with Kubeflow and showcasing how it can be used. And it's a similar thing that I'll be doing in a couple of months at another open source event, where we have an entire two hours just talking about ML tooling and how to use it.
And it's open source, so anyone can try it out, which is quite nice, right? I mean, another example I can give, and this is something I've experienced for the first time this February. My team joined a conference called FUSDEM, which is a free and open source developer conference. It's happening in Brussels every spring. And it's a conference that is basically built up by the community.
So it's completely free. It doesn't even have registration, which means that anyone can go. Like, it doesn't matter how many people, anyone can just show up, they can see the program, they can join one of the developer rooms, they can hear about, you know, new things that are happening, or they can experiment with them. And it was the first time that, you know, I mean, I've been to many conferences, but you typically, you know, you register, you have some sponsors, you see a program, and those kind of things.
And this was just purely driven by, you know, people wanting to share the stuff that they're doing, which, again, it's a part of what makes me excited to work for Canonical as well. Because usually open source is something that, you know, you contribute to in your spare time. I mean, a lot of companies do have open source programs, and now we see that happening more and more.
But it's still something that people usually do in their free time. Whereas I think in Canonical, we really have this unique chance to work with open source as our job, you know, work with open source and actually get paid to work with open source, which I think is something that doesn't happen easily in other companies. And I'll go, I'll circulate back to it, because you mentioned contributions.
And one of the questions that I got a lot in the past was, well, how can I actually contribute? And since we have all our repositories open, you go on GitHub slash canonical, it's quite easy. You can always contribute there. And I know LXD projects, for example, that Miona is looking after, it even has labels with easy for people who are just getting started.
Exactly, you can filter the issues by easy. And then those that are labeled easy are, you know, kind of user friendly, and you can actually, you know, try to solve them, which is, yeah, it's a good way to get started. But also, if you look on our docs, for example, you can always, most of our products have an area with contribute or buttons to, hey, make these docs better.
And these are two of the options. Another interesting thing is, for example, in Kubeflow, again, I talk about it, because that's what I know the best. And we run beta sessions. We have before any release, we have a beta session or a beta period where people can contribute, provide feedback. And we have a couple of users who, I think they're our power users.
And they go on this course, once we go with the announcement out, and they tell us about so many bugs, problems, workarounds that they figured it out, that it's really, it's a real contribution. And the engineering team is, these days, is really looking forward for that period of the year when they get feedback and contributions back from our users, because they know the best what their pain points are, I would say.
If someone, someone is asking for particular examples of projects they could contribute to. Can you share some from your AI and your work? Yes. I can also, I will find a link for the project that I am a part of and a product manager for. We have a page describing how you can actually contribute. And then, I mean, as I mentioned already, if you go to our GitHub page, you can, you can sort the issues by easy.
And then, you know, get started that way as well. Right. And I'll share a couple of links in the chat as well for good places for you to start looking for projects or things that we are working at. You can start with our blog. You can go to GitHub, like Miona mentioned. And we'll also share certain links of projects that we are interested in and are working on.
And I think one more important thing to mention is that, you know, of course, when we talk about open source, we talk about software most, most likely. And we talk about contributions in terms of actual code. But it's important to mention that you can be a part of the open source community, even if you're not a software developer or an engineer, because there is a lot that goes on that, you know, requires organizational skills, communication skills, even documentation, you know, just having someone to go through the documentation and say, hey, this doesn't make sense.
You know, like, can we maybe adjust this so that it's easier for people to understand. Or when we have these kind of meetups and community events, it's always, you know, it's always helpful to have someone join in and kind of help bring people together, help organize, help communicate, help plan. So it doesn't, you don't need to be a software engineer, you can use your soft skills as well and just be a part of the community and, you know, facilitate this collaboration.
Yeah, definitely. In the design team, we have some cool design opportunities. We also look for potential users to talk to them and let them try our products and see what's working, what's not. So there's a lot beyond just coding. Maybe Varshi, I can ask you a question, like, even that you're an engineering director and you actually lead teams, what is it like to be a leader at Canonical and how do you, you know, how, how, how do you lead effectively in a multicultural company?
Right. So Canonical is very unique in that aspect that most of our workforce is very global. We are a very dynamic and agile organization, and it's a very flat organization. So things that are effective for my part of the org is written communication, asynchronous communication. So I have teams that will follow the sun. So we have teams in Americas, EMEA, APAC, all the time zones.
And the way that we coordinate between the teams is trying to make sure we are coordinating a lot through written communication. If we have a meeting, we make sure we have a set meeting agenda before it, and we capture meeting notes for other people to follow if they weren't able to attend. We try to record meetings, which are important things like demos, product demos, or retrospectives, which people can then view later and get information from.
We share our updates and discourse at times for other teams in the company to view those. So we have a very strong written culture in the company that helps with the aspect of collaborating with each other. I think the sprints really help as well. Getting to meet everyone, getting to have that human connect with everyone. I think that helps.
And also just in general, I think we are a team of very bright engineers who are very passionate about what we are doing. So it's actually not that hard managing such works. So it's actually a blessing to be learning from all of them. And people are the greatest asset of our company, which is what I have always believed in.
And we have a workforce of really bright engineers who have both the heart and head, which is very difficult to find. I think it's easier when you have such nice and smart colleagues. I do see another question. It came to the Q&A regarding how to get started in engaging with open source community. Are there any suggestions? I'm not sure if anyone in this panel has experience in contributing to open source or maybe how you got started.
I mean, for example, one thing that we do for the project that I work with, we try to do everything publicly. So, you know, we share kind of what is our roadmap. What are we planning to do? What are we developing? We kind of try to keep everyone informed. And for example, we've had people just coming in our forum, which is usually where we get to kind of most of the interaction with the team.
I mean, you can just kind of post a question, but like we had people come up to us with suggestions like, hey, do you know, like I would like to I think this is like a super useful thing and I would like to maybe help create like an education for people that are interested in learning this. So, I mean, I think, you know, it's it's hard because there is so many different open source projects that exist.
But I think if you find something that is interesting for you, you know, like maybe a tool that makes making websites easier or, you know, an automation thing that, you know, makes configuration a breeze or AIML and those kind of things. So just try to kind of browse through, search, read up and then if you find a project that you like, that seems interesting, you can always kind of reach out to the maintainers that are typically listed there and say, hey, you know, is there anything I can help?
I could help with. Like, I'm curious about this. How can I get involved? And then, I mean, it will be a different answer with different communities, but for sure everyone would just appreciate that, you know, someone wants to help out because we are working on this collectively. I will love to add one more thing here. If we think of Canonical specifically, we do have on Mattermost some of the channels publicly where you can just engage directly with some of us and you see what the teams are working on and you can ask directly the developers.
How could I help? Or, hey, I bumped into this problem. I found this solution and it's Charm Hub is one of the examples that I can recall from the top of my. Mine. It's, if gone, Mattermost. It's publicly. You see, they're all our contributions because I think at the end of the day, we're kind of also contributors to the projects that we are working on.
I mean, yeah, I don't contribute in code, but I contribute in spirit and in, you know, a lot of other things as well. I think you said, sorry to jump in. I think you said something very interesting. It's a discussion that we had in the upstream QPSO community on, hey, can I only contribute by writing code? And the short answer is no.
You can contribute by writing docs, by showcasing how to use the product. And that's actually a contribution as well. It's not just the code itself that should be, is considered a contribution, but knowing how to use a product, it's something very, very valuable as well. And showcasing it. But I mean, I think even things like, you know, if there's a topic you're curious about, trying to organize a meetup, you know, like interacting with, you know, someone like trying to invite, I don't know, a product manager and engineering lead and trying to organize a meetup for other people.
Even that is contributing because you're creating a platform for people to kind of, you know, learn, learn about something. So just kind of, I would just advise, try to browse through different projects and try to find some that you find curious, that you find interesting and then try to get involved. And typically by talking with people that are already in the project, you will find ways that you can, you know, pitch in and give your contribution.
Sorry. I was just going to say, if nothing else, you can always just provide feedback that could be a way of contributing as well. So if you have used a product and if you wanted to open source software and if you want to provide feedback for that, that could be a way to contribute as well. Go ahead, Lydia.
Yeah. I was just going to ask whether any of you would like to share about the role of women in open source. I mean, I didn't talk briefly about it, and I think I mentioned it a bit. And I think it's kind of, there is no really a reliable statistic, but some statistics shows that only about 10% of open source contributions are made by women.
And I think a part of it is also what I previously mentioned. It's kind of a thing you do in your free time, you know, like it's not, it's hard for you to be included in your career development. So it's, I think in some ways it's, you know, geared towards people that don't necessarily have too many responsibilities outside of work and that don't mind spending their free time, you know, just being stuck in their computer screen.
But I think we really need more women in open source just because, I mean, it's just a general diversity of thinking. We are building something that should be freely open to anyone and that should help anyone innovate. That means that we need different people in different mindsets working on these kinds of things. And not just, you know, the same, the same geeky people that, you know, have time to actually stand on this in their free time.
You know, I'll have to challenge this because on 8th of March this year, and it was by chance, we had a release party with the team and we ended up being three ladies talking about open source tooling in machine learning. Yes, we were live on YouTube and someone notices it and we're like, oh, we didn't even notice.
For us, it was normal. It was the normality that we have ladies that work on open source tooling. They are software developers. And it's nice to see how the team in general has different skills. Some are more organized naturally. Some others are more creative naturally. And it came natural. So it depends on the team. That's my challenge.
It depends on it. And I think it depends also on kind of the layer. Like I work with infrastructure and unfortunately we don't have too many ladies in infrastructure. And if anyone has even the tiniest interest, I would gladly help, you know, just kind of teach you everything you need to know. But, you know, it's not so scary.
I know it sounds scary. It's like that down in the basement with a lot of cables and a lot of boxes, but it's actually a lot of fun. Right. I think with the operations, we have the same problem as infrastructure as well. It might, it might feel difficult, but it isn't as, as, as difficult. But the problems that we are challenging, I think they are relevant to all the genders and they're very diverse problems that are applicable to anyone and everyone.
So we want that a diversity of thought in people who are building it as well. And if there's something that I'll say, so I started my career in quite an old school company, I would say, where I was the only woman back then. And I was extremely young. I was extremely scared. And I think it, it kind of followed my career.
So when I joined Canonical, I was very surprised to figure it out that there is an entire community of women that support each other, that we go and have dinners whenever we meet during screens. And then we do connect in different manners, such that it's, it's easy not to ever feel lonely because you're not the only one out there who might have a challenge at some point.
So if I have a bad day as a product manager, I have Miona who's in my team and I'm like, well, Miona, how do you feel today? And it's something very important that, and quite unique, I would say for Canonical as well. We are almost out of time, so maybe Varsha, you can take the last few minutes just to kind of share with people how, how can they find out more about us and also potentially see some of the open roles we have.
Right. So I think there was a question about hiring here as well. So for everyone who's interested in applying for a role, you can go to careers.canonical.com or we also have a virtual booth here. So you can visit a virtual booth, it is under Expo. And if you go to Gold Sponsors, you'll see a Canonical logo. And if you go into it, you will see a virtual booth and you'll find someone you can interact with further as well.
And there is, there is a link for our careers page there as well. You can apply using that in terms of our hiring processes. We, considering how we are trying to do the, do what's not been done before, we have a very unconventional hiring process. We have, like I mentioned, written culture is very important for us, having good writing skills is important to us.
So we have a written interview, we have psychometric assessments after that, then we have technical evaluations and a panel of interviews. So it is, the process itself is, has been created, keeping the candidate in mind as well. During the process, you would get enough opportunities to know about Canonical and whether Canonical is a fit for you or not as well.
So it's an interesting process to be a part of. A lot of people give us feedback that they learn about themselves in the process. So I would encourage everyone to apply. And do feel free to reach out to any of us over LinkedIn or during this conference to the virtual booth. And we would be able to answer more queries and redirect you to the right places for hiring as well.
And maybe a final thing to add. I think both Andrea, me and Varashi initially applied for different roles when we wanted to join Canonical. And then throughout the recruitment process, it was identified that we might be a better fit for something else. So we do really try to take care of our candidates and try to really make sure that we match them with the best possible role for them.
So I think we don't have much time left. So I'd like to thank all of you for attending. Thanks for your time today. And do reach out to us with any further questions. Thank you everyone. It has been a pleasure. Thank you very much. Bye.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Resources mentioned
- ubuntu.com
- Canonical repositories on GitHub (GitHub slash canonical)
- careers.canonical.com
- Canonical blog
- Canonical public Mattermost channels
- Charmhub
- FOSDEM
Cite this talk
Miona Aleksic. "Canonical Meet & Greet." WomenTech Network, 2023. https://www.womentech.net/video/canonical-meet-greet-miona-aleksic