Should we provide a list of example policy packages in the docs for reference?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 71
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 11
Description
Could be cool to link to some policy packages in docs so that people can see them as examples, e.g.:
- DUNE: https://github.com/jamesp-epcc/DUNERucioPolicy
- CMS: https://github.com/dmwm/CMSRucio/tree/master/src/policy/CMSRucioPolicy
- ATLAS: https://gitlab.cern.ch/atlas-adc-ddm/rucio-policy-package (requires CERN gitlab access)
- Belle II: https://github.com/rucio/temporary-belle2-policy-package
But it might be annoying to maintain this long-term
Contributor guide
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
Review the documentation structure to find the appropriate page for example policy packages, then verify the DUNE, CMS, ATLAS, and Belle II links and their access requirements. Done means reaching a decision on whether the list is maintainable and, if so, documenting the examples with accurate links.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100