3
Why users cannot create Issues directly (Ghostty) (github.com)
submitted 10 months ago by to c/ghostty@lemmy.world
comment fedilink hide all child comments
 

cross-posted from: https://lemmy.bestiver.se/post/836737

Comments

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
5 comments in c/opensource@programming.dev view that post
[–] [S] 29 points 10 months ago

A relatively uncommon but reasonable, good approach to issue management.

Discussions allow for different formats, including explicit voting, which is useful for things like feature requests.

  • permalink
  • fedilink
  • source
    •
    [–] 25 points 10 months ago (1 child)

    “Issues are for work items only. Communications go in discussions.”

    posts this communication as an issue

    Seriously though, this approach makes sense to me and I wish more projects did it.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 5 points 10 months ago

    Makes sense, since the go to for github issues is opening an issue, using a non-standard way needs communication visible for people who try to do it the standard way. This allows for them to click issues, see the pinned issue of "Why users can't create issues" and move to discussions.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 11 points 10 months ago

    I think Hyprland does something similar: https://github.com/hyprwm/Hyprland/issues/9854

  • permalink
  • fedilink
  • source
    •
    [–] 4 points 10 months ago

    Not sure what effort this would save other than creating a "To Be Triaged" category in Issues and filtering it from issues tools.

  • permalink
  • fedilink
  • source
    •