github-triage.txt 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. Use this tool to assign and/or label a Github issue.
  2. You can assign the following users:
  3. - thdxr
  4. - adamdotdevin
  5. - fwang
  6. - jayair
  7. - kommander
  8. - rekram1-node
  9. You can use the following labels:
  10. - nix
  11. - opentui
  12. - perf
  13. - web
  14. - zen
  15. - docs
  16. Always try to assign an issue, if in doubt, assign rekram1-node to it.
  17. ## Breakdown of responsibilities:
  18. ### thdxr
  19. Dax is responsible for managing core parts of the application, for large feature requests, api changes, or things that require significant changes to the codebase assign him.
  20. This relates to OpenCode server primarily but has overlap with just about anything
  21. ### adamdotdevin
  22. Adam is responsible for managing the Desktop/Web app. If there is an issue relating to the desktop app or `opencode web` command. Assign him.
  23. ### fwang
  24. Frank is responsible for managing Zen, if you see complaints about OpenCode Zen, maybe it's the dashboard, the model quality, billing issues, etc. Assign him to the issue.
  25. ### jayair
  26. Jay is responsible for documentation. If there is an issue relating to documentation assign him.
  27. ### kommander
  28. Sebastian is responsible for managing an OpenTUI (a library for building terminal user interfaces). OpenCode's TUI is built with OpenTUI. If there are issues about:
  29. - random characters on screen
  30. - keybinds not working on different terminals
  31. - general terminal stuff
  32. Then assign the issue to Him.
  33. ### rekram1-node
  34. ALL BUGS SHOULD BE assigned to rekram1-node unless they have the `opentui` label.
  35. Assign Aiden to an issue as a catch all, if you can't assign anyone else. Most of the time this will be bugs/polish things.
  36. If no one else makes sense to assign, assign rekram1-node to it.
  37. Always assign to aiden if the issue mentions "acp", "zed", or model performance issues
  38. ## Breakdown of Labels:
  39. ### nix
  40. Any issue that mentions nix, or nixos should have a nix label
  41. ### opentui
  42. Anything relating to the TUI itself should have an opentui label
  43. ### perf
  44. Anything related to slow performance, high ram, high cpu usage, or any other performance related issue should have a perf label
  45. ### desktop
  46. Anything related to `opencode web` command or the desktop app should have a desktop label. Never add this label for anything terminal/tui related
  47. ### zen
  48. Anything related to OpenCode Zen, billing, or model quality from Zen should have a zen label
  49. ### docs
  50. Anything related to the documentation should have a docs label
  51. ### windows
  52. Use for any issue that involves the windows OS