## Context / Background
Currently, `login.wikimedia.org` is used by stewards for cross-wiki CheckUser (CU) operations. While technically these checks could be performed on `meta.wikimedia.org`, stewards cannot carry out CU actions on MetaWiki without also being elected as CheckUsers there, since MetaWiki has its own local CUs.
Additional technical distinction:
- **LoginWiki CU data**: contains only a single entry โ the account creation action.
- **MetaWiki CU data**: contains broader local data.
---
## Questions for Discussion
- Why do we currently have local MetaWiki CheckUsers separate from stewards with CU rights on LoginWiki?
- Can the need for local CUs on Meta be replaced or redefined?
- Would steward workflows benefit from shifting to MetaWiki instead of LoginWiki?
- What policy and technical changes would be needed?
---
## Proposed Directions
### Option 1: Consolidate CU on MetaWiki via Stewards
- Retire the concept of local CheckUsers on Meta.
- Grant stewards CU access on Meta directly.
- Make only the account creation actions available on Meta for CU (as currently shown on LoginWiki โ i.e., a single entry).
- ๐ข **Pros**: Simplifies workflows, aligns global checks with Meta-centric steward activities.
- ๐ด **Cons**: Requires policy/community consensus and technical implementation.
---
### Option 2: Improve and Retain LoginWiki Use
- Keep LoginWiki as the steward CU platform.
- Possibly enhance the visibility or scope of CU data (e.g., include additional login metadata or improve usability).
- ๐ข **Pros**: No policy changes required. Preserves clear division of responsibilities.
- ๐ด **Cons**: May remain less convenient or visible in daily steward workflows.
---
### Option 3: Status Quo
- Maintain dual systems:
- Stewards use LoginWiki for cross-wiki CU.
- Local MetaWiki CUs continue operating independently.
- ๐ข **Pros**: No changes needed.
- ๐ด **Cons**: Potentially redundant and confusing; may not scale well with evolving workflows.
---
## Next Steps
- Input from:
- Stewards
- MetaWiki local CUs
- WMF Legal / Trust & Safety (re: policy implications)
- Perform a technical feasibility assessment for CU data availability and integration changes (if needed).