Gonna quote what I said in another thread here because its possibly a better place to discuss it.
(12-19-2019, 09:49 PM)Karlotta Wrote: I voted 250 non refundable because I think that will make it less frustrating to fail and lead to less accusations of bias.
But I think the price isn't the most important issue in this. The most important thing is that you make these requests transparent by making them visible to the community, and for about a week give the community the chance to comment on them before and not after they are submitted, not with the goal of seeking the community's approval or disapproval, but with the goal of pointing out possible problems and suggesting improvements, which both the supplicants and developers can totally ignore if they wish.
This will:
- Enhance general understanding of the process before filing a request
- Reduce accusations of bias and suspicions of foul play behind closed doors
- Raise the quality of the submitted requests
- Reduce developer workload
It was mentioned in the RCR thread that "it is a good idea to ask developers before making a request". What channel one is to use should be specified, and the answer of "yes thats theoretically possible" or "no it isn't" should also be a matter of public record for similar reasons as the above.
