ilusha/imgui
1
0
Fork 0
mirror of https://github.com/ocornut/imgui.git synced 2026-09-26 16:05:45 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Help Wanted (markdown)

omar 2026-06-25 15:07:37 +02:00
parent 8f034fe88c
commit 1120e98a5e
1 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
Help-Wanted.md

@ -15,11 +15,14 @@ Currently looking for help with those things.
- [Open Issues/PRs related to Android](https://github.com/ocornut/imgui/issues?q=android).
- [Open Isuses/PRs related to Linux](https://github.com/ocornut/imgui/issues?q=state%3Aopen%20label%3Alinux%2Fbsd).
Standard backends are for many the gateway to access Dear ImGui. Each backend have thousands of users and use cases.
Important prerequisite to be a helpful regular contributor:
- Need to be sitting on the right side of [the Dunning-Kruger Effect peak](https://www.editage.com/insights/the-dunning-kruger-effect-uncovering-the-concept-with-examples).
- Need to be careful about user experience, support for varying API versions, potential API breakage, coding style. Each change to a backend should raise many questions.
- Need to be able to explain to me how/why different features are used and needed, which needs dedicated support vs which can safely cohabit with existing features.
- You can learn all those things. All I am asking is to be careful and take time to do things and explains them clearly. If you are not careful, then the number of open PR grows even more. The goal to reduce that number, and you can help reduce it by creating confidence.
- Need to be careful about user experience, support for varying API versions, potential API breakage, coding style.
- Each change to a backend should raise many questions. If a change doesn't raise a question, there's probably something that you have not considered or investigated. It is ok to not know. It is better to state what you don't know rather than be overly confident.
- Need to be able to explain to me how/why different features are used and needed, which needs dedicated support vs which can safely cohabit with existing features or can be implemented within existing constraints.
- You can learn all those things. All I am asking is to be careful and take time to do things and explains them clearly. If you are not careful, then the number of open PR grows even more. The goal is to reduce that number; you can help reduce it by creating confidence.
- You don't need to ask permission to start helping.
**Documentation/Wiki**