Hi everyone,

I've been reading through Slack(mifos fineract and main channel) and trying
to understand how contribution within the community works in general. From
what I understand the contributors generally create their own stories
discuss them with the community and then work on them.

I had a few questions or doubts for the mentors I wanted to be cleared:
Should new contributors first become familiar with the overall codebase
before picking up issues or stories, so they can identify and report bugs
themselves?
or is it okay for beginners to be assigned existing open issues to get
started?
If getting familiar with the codebase is the preferred approach, would it
be helpful for newcomers to contribute to documentation first (reviewing,
improving, or adding documentation)? I feel that would help both us and
future newcomers while we learn the project.

I was hoping to start working on some beginner issues, but most of the ones
I found already have open PRs linked to them. In that case would it be
appropriate to contribute by reviewing those PRs, testing them, or
otherwise helping the existing contributors? or can we be assigned issues
also but I fear the lack of identity within the community might come as an
hindrance there.

I'd really appreciate any advice from the mentors. This is my first time
working with Jira in an open-source project, so it's a bit intimidating 😅.

Reply via email to