search

OWASP / www-project-top-10-for-large-language-model-applications

OWASP Foundation Web Respository
Other
449 stars 119 forks source link

The GitHub Issue flow appears to be designed for software bugs, not documentation enhancements #290

Closed codingoutloud closed 2 months ago

codingoutloud commented 2 months ago

Since the flow includes Steps to Reproduce (left intact below) and following sections it is not tuned to the current usage.

Steps to Reproduce

  1. …
  2. …
  3. …

What happens?

…

What were you expecting to happen?

…

Any logs, error output, etc?

Any other comments?

…

What versions of hardware and software are you using?

Operating System: … Browser: …

GangGreenTemperTatum commented 2 months ago

hi @codingoutloud , thanks for reaching out.. this is a limitation of the project as we don't have an official ticketing system current flow is:

GitHub issues -> assigned to LLM lead -> if deemed change needed -> LLM lead submits PR to update

what were you looking to achieve here specifically?

we do have specific per-vulnerability channels, ie #team-llm03_data_and_model_poisoning and the overall project channel #project-top10-for-llm that are more oriented around kicking off discussions, is this what you had in mind?