My Personalized lab set-up for OSS Cotributions.

Often we require to test the projects on our own lab before making a PR.

How to Find Open source projects.

For newbies like me, trying to dwell into OSS projects, ending up in this dilemma common :-

1. GitHub is always a good starting point. Most if not all oss is hosted on there. Free to fork or download to your environment.
2. G soc — Google Summer of Code, lists projects available for contributions when the open for proposals.
3. CV-Es and Forums. With recent advancements, a lot of projects require maintenance against found CV-Es that affect it.

You’re not limited.

What does the project expect of me.

OK. The hustle is done, you found a project you are confident about. But where exactly do you start.

1. Issues & Discussions. OSS projects usually contain issues, listed where hosted. As the name suggests, there need be someone to handle the issue.
2. Pull Requests (PRs). Most of the work done, we presume lies in writing code. But tonnes of devs ignore code reviewing, so browsing PR and opening a discussion or fast forwarding it for merging is a contribution too.
3. Developer Bookmark patterns. As code is being written, even in agentic systems there are instructions to leave that for later, or, we shall get back to that once ‘a library fix is released’. Developers and agents leave out a lot of TODOs, FIXME, XXX, HACK etc marks in source code.

use todo radar to be on the look out.

I have the project, the changes I recommend, what next ?

The above are just the starting points, things are now beggining to boil up.

A good starting place is setting up an environment. Here me out, not testing locally on your setup directly, in project level isolation.

Get Pseudonotes’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Docker might be the correct word for this.

Isolation creates a failsafe for the project, preventing external factors/dependencies from hindering its existence. All the dependencies and libraries it requires at a point, can be spin up and tear down on demand.

This allows for a very mature and robust project configuration control.

I mentioned Docker, even though I stopped using it.

I settled for a close competitor, Podman.

Syntatically and format matches docker word for word, infact, you can alias docker as podman. But Podman has some key tradeoffs over docker that operate well just for me. I might share insights in another Blog.

In this small blog, I share my local configuration. Currently my entire lab is on a single PC. I believe, among other delusions, that this is enough. With keen setup resource tracking and optimized tooling, I can manage this.

Kudos and Cheers.