I think it’s inevitable that MGRC members will have “favorite” projects that they advocate for. That’s not what I’m referring to when I said I was concerned about a conflict of interest. There are subtle differences between advocating and leading a project.
Kek had brought up the point that the MGRC should more proactive about doing things, which I agree with, but where do you draw the line about the MGRC members involvement in said project?
For instance, two scenarios:
-
A MGRC member could be proactive and put out a “I really wish someone would do X for Zcash” and be very specific about what needs to be done. Maybe even calling some of his friends, telling them about it. Allowing multiple parties to submit for the project, and when a party is selected (with MGRC consensus) that MGRC member would be a advocate/mentor for that project setting goals for them to meet.
-
Would it be OK for a MGRC member to create a project and begin hiring individual developers to work on it (with MGRC funds) acting as the manager for that team they assembled? Perhaps forming a business/ LLC for the project to pay the workers?
I personally think the first scenario is fine, keeping the MGRC as a mentor/leader for projects while trying to be fair to all parties that would want to apply. And remaining neutral when assessing if they meet the goals/milestones.
The second is a step too far, that is the COI. The MGRC member would be too deeply involved in the project to not be biased if others tried to apply for the same work. And would not be in a position to be neutral when assessing performance of the team.