User:MDP23/BAG todo
Appearance
This is a list of things I feel should be discussed with reference to BAG, with the aim make it more transparent to the community while maintaining the co-operation of bot operators.
Closed membership - members admitted by voteDone- Group has more "clout", and members are elected by the community in a !vote.
- Downside: community didn't bother with the reconfirmation votes.
- Group has more "clout", and members are elected by the community in a !vote.
- Probationary periods
- For new BRFA requests - stimulate community input
- Should there be too many exceptions? IMO, no - to avoid the headache of "experienced bot ops should be able to do what they like", whichhas been endemic for some time.
- On request for existing bots - can be reopened by any BAG member at any time, generally when prompted by the community.
- For new BRFA requests - stimulate community input
- Require noticeboard spamming during BRFAs?
- Clarify means of appeal against bots
- Clarify role of 'crats
- Membership/"expulsion" procedures to be clarified and made community-friendly.
- "Primer" about bot procedures: BAG, BRFA, etc, to be posted to AN, VP, and in signpost to raise community awareness of bot issues.
- "Lay members" to be recruited to BAG? Represent community as opposed to technicalities, but have the obligation to take part by virtue of their actually being a member
- Is there a way to make WP:BRFA as an applications process more "operator friendly"? I'm not sure if this is a real problem but might be worth addressing
- When community input is high and confidence in BAG is restored, clarify bot policy to require BRFAs for all tasks.