If you were to write down the growth path of a developer, you might end up with something like:
👶 Junior Developer
💻 Mid Developer
🚀 Senior Developer
🧙 Software Architect
But how does this growth actually happen?
If we examine the true drivers, it might turn out that developers grow by spending time writing code and documentation, collaborating with other developers, using various stacks, and solving different problems.
Even though you might have many years of commercial experience in your resume, your public GitHub profile has a huge impact on your software career. It’s your business card in the software world. Not convinced? Check out my previous post Why contribute to open source?
Contributing to open source projects might be intimidating, but it’s worth getting out of your comfort zone and getting involved. Don’t let inexperience in a given tech stack or a library, or any other difference hold you back!
Here are just 3 steps, the best and quickest way, to become an open source contributor.
Start from picking the stack and go to “the chats”. To make it easier to establish contact, oss maintainers always set up a dedicated slack or gitter channel or a discord server, or more and more popular, Matrix. Approach library maintainers there and say you'd like to get involved.
Here’s a list of some popular Scala and Java projects and their communication channels:
- Zio - discord server
- Cats - gitter channel
- Akka - gitter channel
- Kafka - Jira tickets
- Scala - Scala contributors forum
- Spark - gitter channel
- OpenJDK - census
- Hibernate - follow this guide
- Apache Commons - everything happens on this mailing list
- Micronaut - gitter community
- Quarkus - GitHub page
- Spring - GitHub page
There are also developer tools that need contributions. The general rules here are the same.
GitHub Docs encourage library maintainers to apply the good first issue label to issues in their repositories to highlight opportunities for people to contribute. When looking for something on GitHub to match your needs, search for issues and pull requests, go to isses in a repository and narrow the results using label qualifier.
Another shortcut to find your first repository to contribute to is checking the list created by Masato Ohba. Using his script, he puts plenty of issues waiting for beginners' contribution into this spreadsheet.
Documentation and usage examples might sound boring, but are a good way to get to know the project, and contribute something useful. You’d be surprised how many people resign from using a project as they can’t find a good, working (!) example, or a step-by-step tutorial aimed at beginners. Working on docs will allow you to learn the very basics of the software in question. It will make it easier for you to make meaningful contributions to the code later.
Important information for the first timers. Always start from the README.md file in the repository which contains rules on how to use and set up the project, and (if present), CONTRIBUTING.md, which outlines how to collaborate in the project.
It’s much easier to make time for things that are a part of your current work assignment.
If you’re using an open source software, library or framework, and you find a bug in it, open an issue. Make actual contributions and take it as an opportunity to demonstrate value, build trust, and gain skills. Even starting from a small patch, that gets merged, will build up your confidence. And finally, you'll be able to use it in your project, and ship things faster.
Majority of the projects follow a standard fork and pull model for contributions via GitHub pull requests.
An ideal path to meaningful contribution can look like this:
- Find an issue
- Let library maintainers know you are working on it
- Build the project with your contributions
- Write tests, docs and examples
- Submit pull request
Scala 3 is just around the corner. According to the voices of Scala programmers who took part in te Scala Developers' Survey, we run at the turn of the year, there are many programmers who are quite content with their choice of libraries and frameworks. But thery also point out areas that could be improved.
When analyzing the survey entries, we identified the projects that attract most contributors. These are Zio and Akka.
This is mostly in line with the most liked libraries out there. And probably shouldn’t be surprising: both ecosystems are growing and hence there’s a lot of work to be done around them.
Most popular Scala OSS projects
The results of the survey clearly show that the Scala community is engaged in OSS, also that there’s always a place for more contributors.
When it comes to specific pain points we concluded that these general areas need improvements:
- Relational databases
- Graphics and UI libraries
- ML and data science projects
- Json parsing
- Security and unified observability approach
The Scala community needs you!
Help us improve it.
Want to find out more about the developers' expectations for Scala 3 and their view on the future of Scala? Download the Scala 3 Tech Report!