I see what you mean, apparently open source code and skills in understanding it throws off a lot of issues, discussions on GitHub and open dialog contribute to this.
I would like to draw your attention to the fact that this community is developing, growing, quite predictable and logical scenario is an increase in the number of users with starting knowledge, let’s say newbies.
Most of them have not yet discovered registering on GitHub, it will be too early for them to engage in dialogs there, they will be able to understand the code only later.
If you want your product to get the coverage it deserves and due, acceptance, word of mouth.
It would be nice, and I’m speaking respectfully now, not to give the audit a chance to add a spoonful of tar to the honey barrel.
As for the financial question.
It may be reasonable in some cases to allow the community to support the project in the format of a
“donation section for upcoming audits selected by Privacy Guides”
(this is a very raw idea, improvisation)
- The donation section for the audit sounds fun.
- Sounds weird, auditing is the developers’ job.