How To Get Started With Open Source Software Contribution (Apache Solr)
Nazerke Seidan19:582021
A student's open source search engine work turned into a Salesforce job
A computer science student, unsure which path to choose, picks an open source search engine, asks its developer community for help, and that contribution later gets her hired. Salesforce software engineer Nazerke Seidan, who has worked on Apache Solr since 2017, shows why open source can supply the experience employers ask graduates for. So why do so many newcomers grab a beginner ticket and then hear nothing back?
Learn a practical route to a first open source contribution, from first message to reviewed PR
Nazerke Seidan, a software engineer at Salesforce, explains what open source software is, why contributing is worth it and how beginners can get started. Drawing on her own path from student contributor on Apache Solr to a job at Salesforce, she argues that talking to a project's developer community first, not grabbing an issue, is the key to a successful start.
“Software is eating the world and open source is eating software.”
“That's why first not like immediately picking an issue is not a good idea.”
What you will learn
Explain what open source software is and why licenses such as Apache 2.0, MIT and BSD set the rules for changing it
Identify the career benefits of contributing, from real coding experience to a global network and stronger job applications
Approach a project's developer community with an introduction and a request for a mentor before picking an issue
Choose an entry point that fits your skills: fixing issues, watching the bug tracker or improving documentation
Find structured programs such as Google Summer of Code and Outreachy that support new contributors
Key takeaways from the speaker
open source contribution
motivation to contribute open source
apache solr
Details
Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Student, Early career
Length
19:58
Published
June 2021
Questions this talk answers
What is open source software?
It is source code that is available to its users, such as developers, so they can modify, update, share and maintain it. Every project carries a license that defines how far it can be changed.
Why should a student or new graduate contribute to open source?
Contributing gives real programming experience on large codebases, exposure to tools such as build systems, a global community and personal reward. Employers like hiring engineers and new grads with open source experience.
How do you get started contributing to an open source project?
Find a project you are interested in, introduce yourself to its developer community and ask for help or a suitable issue. If you already code you can pick an issue and open a PR; if not, documentation is a valuable place to start.
What if beginner issues on GitHub are taken very fast?
Do not rush to pick an issue; first reach out to the developer community, explain your experience and ask for a mentor. She found her own mentor, a committer, this way.
How do open source developers benefit when companies use their work for free?
Contributors and committers know the code deeply, so companies that rely on the project hire them as contractors or full-time staff to fix issues. She describes it as a two-way street.
About this talk
This talk focuses on open source contribution in particular Apache Solr (https://solr.apache.org/). The following questions will be addressed:
What is Open Source Software Contribution?
Why to contribute to Open Source Software?
How Open Source Contribution works?
How to contribute to Open Source Software (Apache Solr) ?
How open source got her hired at Salesforce (65 s)
Your first step: talk to the dev community (89 s)
Beginner tickets gone? Ask for a mentor (69 s)
My name is Nazerkhe. I'm a software engineer at Salesforce, currently working in search cloud. So before bringing this topic, basically there is a story behind it to why did I decide to talk about open source software contribution. Basically while I was studying at a college back in the days, maybe almost three years ago, I was kind of puzzled and I was a bit lost what I'm going to choose in computer science.
Because as you know, computer science is a very big field. There are so many paths, so many ways to choose. And then one day I found this open source project. I heard about open source project, contribution, all this kind of stuff, but I didn't know how to contribute basically. And then at the end, you know, finally I figured out how to contribute. And then I found one project, basically that is a search engine, open source project.
And then I picked the deaf community to ask their help, like how I'm going to store it in this journey. And so in short, basically that open source contribution brought me to get a job at Salesforce. And so I got a job at Salesforce, thanks to open source contribution, because in open source community, there were so many like engineers or like usually companies like, like Salesforce, like tech companies love open source contributors to hire.
And that's why I thought maybe I will, you know, just talk and share my story and to help others, maybe if they're puzzled and they don't know how to get started. And so today I will talk about what is open source software and why to contribute to open source in this work, how to contribute. The last one, I'm going to give an example that currently actually I'm working on that project.
By the way, if I have any questions, please put in the chat, I will respond them at the end of the chat. Feel free. So, what is open source software? Basically, if we, based on the definition, open source software is a source code, you know, which is available to its users, like developers, like to us, and so that we can modify, update, or share, or basically maintain that code.
And for example, open source can be any, anything basically can be, can be a programming language or currently very popular open source. Open source is programming language like Python, Ruby, or pro or operating system like Linux, or the orchestration system is like Kubernetes, Or machine learning TensorFlow, or machine learning TensorFlow, the react native, or a text data atom, or search engine like solar.
All of these are open source. Basically, the source code is available on the internet so that you can just fork it, you can modify, maintain, and then contribute. So then there was a saying that I really love in our open source dev community. This is kind of a very, very liked statement. Software is eating the world and open source is eating software.
So apparently, nowadays, many, many tech companies are leveraging this open source project. Because what? Because you don't need to pay. So already there are, if the open source is very solid, there are really nice and well-developed, maintained dev community. And so they are so helpful. And basically, everything is free. You just want to leverage. This is why currently in tech industry, there are so many companies are using open source projects.
So basically, there is a non-profit organization, so-called open source initiative, who maintains these open source projects in general. And this open source initiative also supports and looks, basically takes care of this open source definition. Like free distribution or distribution of license or anti-discrimination, etc. Because we need some rules for open source projects to update, to modify, because we can't modify how we want.
So that's why there must be some regulations. For example, license. License are very important in open source projects. Why? Because, you know, basically license defined how to modify open source projects. So very popular open source license, for example, Apache 2.0, or MIT license, or BST, Berkeley license, etc. So every open source project has a license where the regulations are written, how you can modify or what extent you can modify or update, maintain the open source project.
So then, you know, basically you have kind of understanding of what is open source project. So open source project is a source code that is available to users, its users, and can modify, update, maintain the project, contribute that event. And then the next question, why do you contribute to open source? There are many reasons. And mainly I brought here some of them that I thought may be useful and interesting.
So first is, of course, is the experience. Because like when you are at school, at university, literally, some companies, many companies ask you experience. But how are you going to get experience? You know, because you are just studying at the university. And so the open source is contributing to open source is one way of getting experience, basically.
The solid open source project gives you valuable experience in programming. The second one is improved coding skills. Because the open source is a very large code base. Many open source projects, like millions of lines of code, so that you get to know how the code is written. Because every open source code has their own standards, you know, like how it's written and all these like documentations.
That's why it's the best practice to learn. And then also, there are tools or cutting edge technologies every open source project uses. For example, build, build system, for example, or package management, etc. So every open source has so that you will have a great opportunity to learn this kind of tools, technologies along with. And the third one is global community.
Because open source is to everyone, basically. So then you will have a chance to collaborate or communicate with people around the world. So it's not only tied to your location or to your place, but it's global community. And giving back is also very important. Because, you know, once you contribute to open source, and then you see that your commit or your like PR, which is merged to master, for example, let's say, that's yours, your code, and your name is written on it so that you feel kind of reward, you know, like personal reward, I would say.
So once you have some open source contribution, and so then when you put it on your resume or CV, then the employers love hiring software engineers or new grads with some kind of open source experience. Because so you have some experience, you know, how to browse a large code base in the, you know, some tools, colleges, and so yeah, currently software engineers with open source background are in high demand.
And so this is or several of them there, but I'm sure there are many, many opportunities if you have open source background. And so, so now next question is, so you know now what is open source, why to contribute, so it is how to sort. So basically, you could start first is the first and foremost is project communication, basically pinging or reaching out the open source project, basically deaf community, because every open source project has a deaf community.
Where developers, contributors, interact with each other, and so then first you have to find an open source project you are interested in, and then just ping that community, deaf community to say, hey, introduce yourself. And I'm interested in the project, please help me figuring out this kind of thing. Well, I'm willing to learn basically, right, is there any like kind of issue that that is suitable to me, etc.
So then this community is, you know, they're, they're just helpful, they can help you, I'm sure. So then or if you have some experience, you know, you know how to code, and you have some experience in coding programming, you just like a pick up your one issue, and then you fix, and then you just create a PR, basically.
And then the deaf community will review it and give some feedback. And then another way as doing, in open source projects, there are backtracking systems like JIRA, or a backlog, and etc. So you just, you know, you just like, sign up for that backtracking system, and you keep an eye on that backtracking system on your particular project, open source projects.
So then you continuously look at these issues, maybe sometimes, you might be interested in that issue and to fix quickly and to get some review. And that's the one or if you are not sure about this coding or if you are not, if you don't know how to code, you know, at school, it's possible to, for example, in your early years, maybe junior, for example, first or second year at a university.
So you might start from documentation basically, because documentation is very, very important. A good open source project has very good documentation, well documented, so that, like, outside people or users come into that project. So by reading the documentation, they have a kind of sense of feeling, you know, oh, the project is this kind of thing. That is why documentation is very crucial.
You just, you know, you just, again, ping the project and then say, hey, I would like to, hey, I read this one, this is kind of unclear to me. Maybe I could help with this documentation, you know, with this part of it. So then they, of course, they welcome you and that's another part of document, contributing to open source project.
And this documentation is very valuable because many software engineers, I see that, they don't see this as valuable, you know, oh, writing some documentation. This is not coding. Oh, it is, it just, you know, kind of wasting time, but it's not. This is important as, as like coding. So now, you know, this, basically, how to get started.
And then also, I would like to mention some opportunities. Globally, there are many opportunities for open source contributions. And then here, I would like to name three of them, which are very popular currently. In the 20th, Google, Google Summer of Code. This is very popular, sponsored by Google. And so this is kind of summer internship, remote, I would say.
So you, during summer, you can pick up an open source project and you contribute to the project and you'll get some stipend during that period. And then Lynx Foundation, for example, Lynx Foundation has a one project called LIFT program, which is, again, open source project. So you contribute. And this is once a year or maybe three months internship program.
Another one is very popular. Again, it's about, again, open source projects, sponsored by Outwechy. So this is twice a year. Basically, they hire mostly students who are studying bachelor or master's students and to contribute to open source project. You can select any open source project basically. So, and here is an example. Apache Solar. Why? Because currently, I'm working in this Apache Solar project.
I started contributing to this project since 2017. While I was studying at school. And then thanks to the Solar, I was hired by Salesforce. And currently, I'm in that project still. I'm still contributing to this open source and still in that team that we contribute to open source. And so what is Apache Solar? This is basically a search engine or a library, I would say, for enterprise.
So we build a search engine, like for example, like Bing, for example, when you type something, you will search something behind it. Of course, it's search engine. And this is a backend project written in Java, distributed and distributed scalable, highly reliable platform. And if you're interested in search, for example, you could just search for the solar. So how it works, all these kinds of things.
And we have a very solid deaf community to help you and to help you start with this open source project. So, and open source, as I mentioned, is everywhere. And currently, many tech companies are using open source projects. So for you is just to choose the first your field, what topic you are interested in. Like me, I'm interested in search and then look for open source in that field.
You know, so what kind of open source projects out there related to search? The same applies for you. For example, if you're interested in front end, maybe you could choose a react native, which is very hot topic, hot like framework currently developed by Facebook. And so then you just pick in the short contributing. Then once you are familiar who is code based, maybe you get hired by other companies who are using this react native.
So thank you very much for listening. And if you have any questions, I will answer. I'll have three more minutes. I will go here. So if you have any questions, please ask me. Otherwise, I am done speaking. Beginner tickets get taken very fast. How do you go around this? Oh, what do you mean by tickets? Maybe you could elaborate.
Oh, in GitHub. Oh, I see. So that's not like, you know, so the first thing is just going to the deaf community. Just go and ask what I did was basically before I did. Hey, I'm looking for a mentor. Basically, I introduced myself to a deaf community list. I'm here. And then who has barely like, you know, knowledge in Java, but who is willing to learn?
Lauren, Lauren, this open source project. And then I'm looking for a mentor who had helped me along with this open source contribution. And then in one guy who is a commuter in open source projects, like responded to email that then my journey started basically in open source. That's why first not like immediately picking an issue is not a good idea.
Just first interacting with deaf community, pinging yourself, you know, hey, this is the one. My experience is one, but I'm willing to learn this one. Is there anybody to help me along this way? Then you'll get, you know, because I see some people that go to the jury issue and then pick that issue and then figure out that no one looks at the code.
And then, you know, so they will be disappointed because no one looks at it. Well, I have to contribute. And that's why a communication, you know, solid communication is very, very crucial in this project. So any other questions? I was wondering your thoughts on offering open source as free to use to companies for profit. Do you think this has been trained to open source community?
Do you think there isn't enough support global for us? No, basically, like usually the open source project is free. Everyone can use it. But the other side that open source developers benefit is that they support this open source project. Because open source contributors and the committers, they know the code. Basically, they know everything in open source project so that they can help these, you know, profit organizations by supporting this project.
Basically, if something doesn't work, basically the company asks developers, these contributors, how to fix. Maybe I'll hire you, you know, as a contractor or like full time to help me to fix my issue. And that's why the open source project benefits from this. Basically, there are two ways, two streets. Yep. I don't know, Samantha, I answered your question or not, if you get an answer.
Okay, guys, thank you very much. Time is over. And I hope you learned something, you know, from this, from this talk 20 minutes. I didn't speak for nothing. I hope you learned. Thank you very much. And I'm happy to connect on LinkedIn and have a nice day.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why your first open source contribution should start with a message, not a pull request
Salesforce engineer Nazerke Seidan explains how contributing to Apache Solr as a student turned into a job, and how beginners can follow the same path.
In short
Open source contribution is one of the most practical ways for students and early-career developers to gain the experience employers ask for. Nazerke Seidan, a software engineer at Salesforce, argues that the most important first step is not picking an issue but introducing yourself to the project's developer community and asking for guidance. Her own path, from a student contributing to the Apache Solr search engine to a job at Salesforce, shows how that approach pays off.
Key takeaways
Open source contribution: what it is and how it works
Motivation to contribute to open source
Apache Solr as a concrete example of a project to contribute to
From lost student to Salesforce engineer
Seidan opens with a familiar feeling. Around three years before the talk, as a computer science student, she was unsure which direction to take in such a broad field. She had heard about open source but did not know how to contribute. Eventually she found an open source search engine project and turned to its developer community for help. That contribution, she explains, is what brought her to Salesforce, because tech companies like hiring open source contributors.
She began contributing to Apache Solr while still at school and has stayed with it: "I started contributing to this project since 2017. While I was studying at school." (14:03) Today she is still on a team that contributes to the project.
What open source is, and why it has rules
Seidan defines open source software as source code available to its users, so developers can modify, update, share and maintain it. Examples range from programming languages such as Python and Ruby, to Linux, Kubernetes, TensorFlow, React Native and the Solr search engine. She shares a line popular in her developer community: "Software is eating the world and open source is eating software." (3:14)
Companies lean on open source, she says, because it is free and well-maintained projects come with helpful communities. Because anyone can change the code, rules matter. She points to the Open Source Initiative, a nonprofit that looks after the open source definition, and to licenses such as Apache 2.0, MIT and BSD, which set out how far a project can be modified.
Why contribute at all
Seidan lists the reasons she finds most useful. The first is experience: students are asked for experience by employers but have few ways to get it, and a solid open source project provides real programming experience. The second is better coding skills, since large projects with millions of lines of code have their own standards, documentation and tools such as build systems and package management. The third is a global community that is not tied to your location. The fourth is giving back, and the personal reward of seeing a merged PR with your name on it. Finally, she says employers like hiring software engineers and new graduates with open source experience, because they already know how to navigate a large codebase.
How to get started
Her first and foremost step is communication with the project. Every open source project has a developer community, so she advises finding a project that interests you and introducing yourself, saying you are willing to learn and asking whether there is an issue that suits you. Those with coding experience can pick up an issue, fix it and open a PR for the community to review. Another route is to sign up to the project's bug tracker, such as Jira, and keep watching for issues you could fix quickly.
For students who are not yet confident coding, she recommends documentation. Good projects are well documented, and clear documentation is how outsiders first understand a project. She pushes back on engineers who see this as a waste of time: "This is important as, as like coding." (12:07)
She also names programs that support newcomers: Google Summer of Code, a remote summer program with a stipend; a Linux Foundation mentorship program; and Outreachy, which runs twice a year and mostly takes bachelor's and master's students. Her closing advice is to choose your field first, then look for open source projects in it, whether search like her or front end with React Native.
Beginner issues disappear fast: what then?
In the Q&A, an attendee asks what to do when beginner tickets on GitHub are taken almost immediately. Seidan's answer returns to her central point. When she started, she wrote to the developer mailing list, introduced herself as someone with limited Java knowledge who was willing to learn, and asked for a mentor. A committer replied, and her journey began. "That's why first not like immediately picking an issue is not a good idea." (17:17) She has seen people pick a Jira issue, find that nobody reviews their code and give up disappointed. "And that's why a communication, you know, solid communication is very, very crucial in this project." (17:58)
Asked whether companies using open source for free is unfair to the community, she describes a two-way street: contributors and committers know the code, so companies that rely on a project hire them as contractors or full-time staff to fix their issues.
Watch the talk
How To Get Started With Open Source Software Contribution (Apache Solr), by Nazerke Seidan, 20 minutes: https://www.womentech.net/video/how-get-started-open-source-software-contribution-apache-solr
About the speaker
Nazerke Seidan is a Software Engineer at Salesforce based in France, with a bachelor's degree in Computer Science from Eötvös Loránd University in Budapest. Before Salesforce she worked and interned at CERN, ETH Zürich, HENNGE in Japan and Cloudera in Hungary.
Questions this talk answers
What is open source software?
Why should a student or new graduate contribute to open source?
How do you get started contributing to an open source project?
What if beginner issues on GitHub are taken very fast?
How do open source developers benefit when companies use their work for free?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Open Source Definition
Apache License 2.0
MIT License
BSD License
Resources mentioned
Apache Solr (solr.apache.org)
Google Summer of Code
Linux Foundation mentorship program
Outreachy
Jira
Cite this talk
Nazerke Seidan. "How To Get Started With Open Source Software Contribution (Apache Solr)." WomenTech Network, 2021. https://www.womentech.net/video/how-get-started-open-source-software-contribution-apache-solr