A new, separate admin team be found (or formed) to handle administration for any instance that is dev-owned.
I agree with this. The act of administering a dev-operated instance with live accounts + users while working on the dev team presents a conflict of interest which is a deal-breaker for too many donors.
So, rather than simply asking the community for more donations (which is understandable but doesn’t address the root of the problem), it would be best to incorporate the feedback of the community and do away with the conflict of interest. IMO, another way to resolve this COI would be to disable live accounts for anyone who isn’t a developer in the “test” environment.
I’ve seen a defense presented in this thread along the lines of “we should be allowed to admin .ml because it’s a test instance” — but again, due to the fact that there are live accounts for live users (outside of the dev team) in the “test” environment, this is a distinction without a difference.
My read is that they’re recommending that
I agree with this. The act of administering a dev-operated instance with live accounts + users while working on the dev team presents a conflict of interest which is a deal-breaker for too many donors.
So, rather than simply asking the community for more donations (which is understandable but doesn’t address the root of the problem), it would be best to incorporate the feedback of the community and do away with the conflict of interest. IMO, another way to resolve this COI would be to disable live accounts for anyone who isn’t a developer in the “test” environment.
I’ve seen a defense presented in this thread along the lines of “we should be allowed to admin .ml because it’s a test instance” — but again, due to the fact that there are live accounts for live users (outside of the dev team) in the “test” environment, this is a distinction without a difference.