ifme VS cve-bin-tool

ifmeorg/ifme- 2 pull requests

Similarly, I spent a significant amount of time setting up the ruby on rails project of if-me for Hacktoberfest. It was hard and I wanted to give up in the middle, but every time I wanted to quit – there was this invisible force inside me that would kick in and make me go on.

On a more positive note - I did write all the other tests required. I sent a PR anyway, even though I could not cover all lines.

So far I think I've been doing pretty well. While the scope of my contributions has varied, I've been able to work on a few projects - some larger than others, but all of them being software that people actually use (as opposed to someone's side project): cve-bin-tool, libplanet, ByteChef, Ghostfolio, and Mattermost.

CVE Binary Tool Release Notes page hasn't been updated for v3.3 and now v3.4 was just made #4458

I was looking for issues to help with on GitHub and found one that was a simple documentation update. The project, cve-bin-tool, hadn't had its release log updated for the past few releases. I'd been advised to start with something small so I could get used to the process and this seemed like a good place to begin, especially since one of the maintainers said it was a simple copy-paste job. I left a comment on the issue saying I would like to give it a shot and got to work.

intel/cve-bin-tool - 2 pull requests

Intel/cve-bin-tool: There are several issues in this repository that are interesting to me, particularly the ones about creating checkers. I would say it is not very coding-heavy, but it needs a lot of research before doing it.

Whether you contribute small or big chunks of code, being consistent about them carries vital importance. Small contributions to a particular project help you to get familiar with it at first and leads to something bigger. Take a look at some pull requests I have raised to the following projects; withfig, cve-bin-tool, my-photohub, pr-approve-generator.

For my release 0.3 for OSD600, I have to create a pull request for an external repo. The repo I contributed to was cve-bin-tool. This post was late because I had was busy with other commitments and projects compounded with problems finding workable issues. In the future, I would definitely follow my own advice and search for issues early and often. I didn't follow this advice and found myself in this position.

The issue was to fix mypy type issues in __init__.py. I was able to fix the type issues and also added type annotations to the codebase. The project was well documented and I faced no issues running it. Big projects like nodejs, vscode or this, cve-bin-tool all have strict guidelines for contributions. Even on the commit messages get checked when you raise a PR. See one of the commit messages from gitlint in their workflow.

My two PRs for Intel’s CVE-Binary-Tool got merged! These (Fix1 , Fix 2) were my first ever Hacktoberfest merges. These were small contributions but big confidence boosters. I am a beginner in programming, and if I can make small contributions, so can you. From one beginner to another – start small, try your best, trust the process, and ask for help.