Modify CODEOWNERS for translation folder #484
Description
Remember, an issue is not the place to ask questions. You can use our Slack channel for that, or you may want to consult the following Slack channels:
- #project-top10-for-llm
- #team-llm-web
- #team-llm_diagrams_and_visuals
- Each vulnerabilities has its own dedicated Slack channel for discussions in the format of
#team-llm0X, I.E (#team-llm03_data_and_model_poisoning)
When reporting an issue, please be sure to include the following:
- Before you open an issue, please check if a similar issue already exists or has been closed before.
- A descriptive title and apply the specific LLM-0-10 label relative to the entry. See our available labels.
- A description of the problem you're trying to solve, including why you think this is a problem
- If the enhancement changes current behavior, reasons why your solution is better
- What artifact and version of the project you're referencing, and the location (I.E OWASP site, llmtop10.com, repo)
- The behavior you expect to see, and the actual behavior
Steps to Reproduce
New translation process is going to be based off branches and forks.
I would like to enforce an approval step on that folder since some parts of it will be automated with Github by being added to CODEOWNERS for that directory.
Specifically the automations to be built for translations are:
- reporting on percentage of the top ten that has been translated already
- generating WIP pdfs
What happens?
n/a
What were you expecting to happen?
n/a
Any logs, error output, etc?
n/a
Any other comments?
…
- Slack post link (if relevant)
What versions of hardware and software are you using?
Operating System: …
Browser: …
- Chrome
- Firefox
- Edge
- Safari 11
- Safari 10
- IE 11