SSWConsulting / SSWConsulting/SSW.Rules.Content
✨ Rule Owners - Tagging for Rule Categories
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 62
- Forks
- 196
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 112
Description
Introduce the concept of an “owner” at the top of each rule category within ssw.rules. This owner will have authority to approve updates or archival of rules in their category, providing clear accountability.
Acceptance Criteria
- Rule category headers display a designated owner (name or alias)
- Owner is shown in a consistent format (e.g., bold or tagged)
- Only designated owners can authorize a rule to be archived
- Implemented across all rule categories on SSW.Rules
- CTF sent to announce the new protocol
Dev Notes
- Owners for initial implementation:
- GitHub: Wicksy
- Tech doc: uly
- SharePoint: Jean
- Consider adding metadata or YAML headers to each category for extensibility
Source thread RE: Rule Category Masters
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ssw.rules category structure and the source thread “RE: Rule Category Masters”; no specific files or tests are named. Inventory all rule categories and determine how ownership and archival authorization should be represented. Done means every category shows its designated owner, the authorization protocol is defined, and the CTF announcement is sent.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100