How can I become a vouched contributor to Frappe Framework?

Prasant_Pant · October 26, 2026, 3:47pm

Hello Frappe community,

I would like to contribute a fix to Frappe Framework, but my pull request was automatically closed because my GitHub account (pantcr7) is not currently in the vouched contributors list. The contribution guidelines say that only vouched contributors may open pull requests.

Could someone explain the process and criteria for becoming vouched? Should I make a contribution elsewhere first, or is there a maintainer I should contact? I would also appreciate guidance on the right next step for the existing fix, so I do not open another pull request that will be closed automatically.

Context

I reported issue #45304: when multiple workspaces share a module, clicking a dock item can load the requested workspace while leaving the wrong sidebar selected.
I submitted PR #45305 to prioritize a sidebar that directly links to the selected workspace, while retaining the existing fallback. The PR was closed by the bot because my account was not vouched.
I reproduced the behavior on Frappe v16.53.0. I have before-and-after screen recordings available if they would help; the fix has not yet been tested on a running latest-develop bench.

Thank you for explaining how I can become eligible to contribute.

avc · October 26, 2026, 6:33pm

Hi @Prasant_Pant

Please, ping maintainers @ejaaz / @sohamkulkarni among others from your issue / PR. After some good minor contributions maybe you could be vouched … They had to start applying some criterai due the really high volume on contributions

github.com/frappe/frappe

Suspension of community PRs

opened 06:17AM - 19 Mar 26 UTC

closed 06:44AM - 19 Mar 26 UTC

ankush

meta

We have suspended accepting community PRs temporarily. This decision was taken c…onsidering: - The volume of PRs received. - The percentage of PRs that were largely AI generated. They required more work from our side than effort put in by contributors. - Lack of maintainer/reviewer bandwidth to work on and merge those PRs. - Perverse incentive in job market and colleges to have "open source contributions" on resume. We understand the value of community contributors and long-term contributors to the projects. Many such contributors have shaped our projects, but at present it isn't practical to accept PRs from everyone. Workaround: We are still accepting small, easy to review/merge fixes. To do this... 1. Open a detailed bug report. Do not generate entire bug reports using LLMs. A good bug report is almost as valuable as a PR that fixes the problem. 2. Ask if maintainers are open to a fix from community. 3. Create a branch on **your fork** and add commits that fix the problem. 4. Share the link to your fix branch, maintainers will create a PR from it and merge it if it's appropriate. 5. Alternatively you can also share `.patch` file for your commit and maintainers can apply it directly. Those who have enough such fixes are invited to the repository. They can create PRs without any restrictions.