Is this repository collaboration-ready?

### Repository Settings

- [x] Set appropriate repository visibility (public or private)
- [x] Configure branch protection rules

### Repository Contents

- [x] Create an informative README.md
- [x] Add a LICENSE file
- [ ] Include CONTRIBUTING.md
- [x] Set up CODEOWNERS
- [x] Establish a CODE_OF_CONDUCT.md

### Which license did you choose? (Please specify)

MIT

### Automation/Checks

- [ ] Implement code linting
- [ ] Set up tests / Continuous Integration (CI)
- [ ] Configure status checks
- [ ] Consider Continuous Deployment (CD)

### Security

- [x] Assign appropriate roles/permissions
- [x] Manage secrets securely
- [ ] Set up scanners for dependencies, secrets, general vulnerabilities
- [ ] Consider Dependabot version updates
- [x] Provide a SECURITY.md & enable Private Vulnerability Reporting

### Advanced Options

- [x] Add Issue Templates
- [ ] Configure GitHub Codespaces
- [ ] Define Environments

### Next Steps / Externalities

- [x] Commit to being responsive
- [ ] Use GitHub Projects and Issues for project management
- [x] Promote your project for visibility
- [x] Engage with your community

### Notes:

- contribution info added directly to README
- enabled Discussions
- non-code repo, skipping CI/CD

Examinez les éléments non cochés de l’issue par rapport aux README.md, SECURITY.md et aux paramètres existants du dépôt. Commencez par déterminer quelles capacités ignorées sont nécessaires pour ce dépôt sans code ; le travail est terminé lorsque les paramètres ou fichiers sélectionnés sont implémentés et que la checklist et les notes reflètent correctement le dépôt.

Rédigé par le modèle d'indexation à partir du texte de l'issue.