AVID:Requests for Comment/Proposers cannot vote on their own RFC
Proposers cannot vote on their own RFC (one proposal only)
I have seen a few users who gave their own requests a vote for it to pass or fail. The issue with this is that it makes them look selfish and manipulative by changing the results of the RFC to their advantage, resulting in an unfair victory for one side. This tactic may possibly be used for RFCs they proposed with little to no traction in order for it to get passed/rejected. Since this rule is not mentioned on the main RFC page, I think it should be stated so that the voting counts are more fair, meaning one side does not get the upper hand because one person who supported/opposed the proposal is the author.
And one last reason: this is like non-staff requesters closing their own RFCs; both may delve into manipulation to get their request to a certain status (snowball closures may also come to mind with these issues).
EDIT: EMG raises a fair point about RFCs with single and multiple proposals. So, the focus of this proposal will shift specifically to those with just one proposal. To add on what he said, multi-proposal RFCs may not clearly state the requester's stance, so it makes sense for them to pick which one to side. Camenati (talk) 03:38, 15 March 2023 (UTC)
Support
Support in the case of a 1-proposal RFC. 
(Lets chat!) 03:42, 15 March 2023 (UTC)- Support in the case of a 1-proposal RFC per EMG.
· Talk · Edits 03:45, 15 March 2023 (UTC) - Support in the case of a 1-proposal RFC. IAmThe789Guy (talk) 15:09, 15 March 2023 (UTC)
- Support in the case of a 1-proposal RFC as per above
(Talk to Me!) 15:12, 15 March 2023 (UTC)
Abstain
Oppose
Oppose in the case of a multi-proposal RFC, so the creator can make clear their preferred option. (Lets chat!) 03:42, 15 March 2023 (UTC)- Oppose in the case of a multi-proposal RFC per EMG. · Talk · Edits 03:45, 15 March 2023 (UTC)
