Help wanted with organizing Rack GitHub issues is a huge mess, and I don’t have time to go through it and clean up titles and close solved/obsolete issues. Would anyone like to help with this?

An example:

[V1 Feature Request] disable modules

We don’t need the “fake tags”, and the rest of the title isn’t descriptive. A good title doesn’t require you to read the issue text to determine what the issue is about. Better:

Disable module DSP with context-menu item and key command

Guidelines for closing issues

  • If a bug or feature has been fixed, added, or obsoleted (e.g. suggestions for the v0.6 Module Browser), it can be closed.
  • When closing, post a message such as “Fixed in Rack v1” or “Added in abcd1234” if you really feel like spending the time to find the commit hash.

If this is something you’d like to do, send me a message and I’ll add you to the repo.

1 Like