I don't think anyone is proposing that new developers get push access or bypass review by existing developers. We're all in agreement that it would not be acceptable. Matthew's question of how to avoid long review delays doesn't have a great answer; I can't think of anything beyond keeping the tasks much smaller than purge-db4o was.
Sent from ProtonMail mobile -------- Original Message -------- On May 9, 2017, 3:21 AM, wrote: On Tuesday, May 09, 2017 09:12:21 AM x...@freenetproject.org wrote: > On Monday, May 08, 2017 04:57:10 PM Ian wrote: > > There is also a trust issue, since we would probably need to give them > > access to source repos and other things - and it would be irresponsible to > > do that with someone we know nothing about. > > For security reasons I don't think any of the core contributors will accept > giving direct push and/or release privileges to someone who hasn't been on > the project for years, me included. > > If we hire a stranger they will have to commit to their own repository and > send pull requests just like any other unknown new contributor. > > Further, for code quality reasons, payment should only be sent once their > code has been reviewed and accepted by the core team. > Freenet is a complex project, we cannot blindly merge code from someone who > hasn't proven to be familiar with the codebase yet. Proving this takes > years. I'm sorry, I wasn't clear enough: You seemed to say that hiring a non-anonymous person would solve this problem. I meant to reply that knowing their real name does *not* solve it: Any new contributor will have to prove their skill by sending PRs for a long time, anonymous or non-anonymous. Direct push/release access and payment is not an option IMHO.
