verto.sh simplifies your entry into the open-source world by curating accessible projects. Ideal for beginners making their first contribution, founders building teams, and maintainers seeking new contributors.
It used to be firstissue.dev, which sounds like everything else. It had to be verto.dev, but someone else took the domain. Verto is a word of significance in my native language, and one dear to me at that.
This is cool - I can think of some projects that are amazing as first contributors, and others I can think of that are terrible.
One thing I think the tool doesn't address is why someone should contribute to a particular project. Having stars is interesting, and a proxy for at least historical activity, but also kind of useless here - take argoproj/argo-cd [1] as an example - 14.5k stars, with a backlog of 2.7k issues and an issue tracker that's a real mess.
Either way, I think this tool is neat for trying to gain some experience in a project purely based on language.
This kind of speaks to how stars on GitHub are kind of a mess themselves. What would be really interesting is if there were some kind of a metric that captured oss-contributor sentiment - projects that were easy to contribute to, with healthy ecosystems, would have higher scores, and projects where your PRs sit forever half-reviewed, or unmerged, get lower scores.
Not exactly a beginner friendly OSS project. Pretty rigorous contribution guidelines (for good reason... but probably not a great first project for beginners).
The goal is also to contribute to a project that you'd be proud contributing to. For example, my cousin's Twitter clone is easy to contribute to, but it has no effect on your resume.
I was surprised to see AWS projects at the top of the list. In my experience contributing to anything maintained by them isn't a great time for first timers.
This is neat. As someone recently laid off and looking to stay sharp with coding while searching for a new opportunity, a suggestion (if possible)…
Maybe add an option to sort by issues?
I’m currently working on a personal project to better understand how to stand up both the backend and frontend (one of the awesome things about my former team was we had templates that made standing up a new service a breeze) but I would really like to use my time to try and resolve issues in some OSS.
Unfortunately, a lot of my more recent experience was project management and features/fixes, so I need to brush up on the fundamentals but it would also be nice to utilize my productivity to the advantage of others.
27 comments
[ 3.3 ms ] story [ 60.5 ms ] threadOne thing I think the tool doesn't address is why someone should contribute to a particular project. Having stars is interesting, and a proxy for at least historical activity, but also kind of useless here - take argoproj/argo-cd [1] as an example - 14.5k stars, with a backlog of 2.7k issues and an issue tracker that's a real mess.
Either way, I think this tool is neat for trying to gain some experience in a project purely based on language.
[1] https://github.com/argoproj/argo-cd/issues?q=is%3Aissue+is%3...
https://www.lucavall.in/blog/meet-verto-sh-your-gateway-open...
Maybe add an option to sort by issues?
I’m currently working on a personal project to better understand how to stand up both the backend and frontend (one of the awesome things about my former team was we had templates that made standing up a new service a breeze) but I would really like to use my time to try and resolve issues in some OSS.
Unfortunately, a lot of my more recent experience was project management and features/fixes, so I need to brush up on the fundamentals but it would also be nice to utilize my productivity to the advantage of others.
Thanks for sharing