Seeking guidance for initial contributions to Bitwarden beyond the documentation

Ask the Community Password Manager
, ,
1

Hello Bitwarden Community,

I’m excited to introduce myself as a new contributor to the Bitwarden open-source project! Over the past few weeks, I’ve carefully reviewed the contribution guidelines and documentation, set up the project locally, and familiarized myself with the codebase structure.

While I’ve been exploring the “good first issues” to find a starting point, I haven’t yet identified an issue that aligns with my current confidence level. To gain momentum, I’m considering two potential paths:

  1. Refactoring opportunities (e.g., improving code readability, modernizing patterns).
  2. Enhancing test coverage by adding unit/integration tests, provided they align with project priorities.

Could the community share advice on:

  • Areas of the codebase that would benefit from non-breaking improvements or tests?
  • Best practices for proposing or discussing such changes before implementation?
  • Any overlooked resources for onboarding contributors?

I’m eager to learn and contribute meaningfully. Thank you in advance for your guidance!

2

Hopefully, you’ve already seen this:

The above announcement includes links to Github Discussion pages where you can propose and request feedback on code contributions, as well as a link to a live chat app (Gitter) for discussion contributions with Bitwarden devs.

1 Like