Hmm, something to discuss. Our tooling ensures issues are disabled on all repos - so none of our repos have issues enabled. We’d need to ensure someone (or multiple someones) are monitoring any repos we enable issues on, as they’ll be “special cases” compared with the rest of our code.
I think our “high profile gems” should have issues enabled:
GitHub - discourse/logster: Log viewer UI and framework for rack · GitHub
GitHub - discourse/mini_mime: minimal mime type library · GitHub (has issues)
GitHub - discourse/mini_scheduler: Adds recurring jobs for Sidekiq · GitHub
GitHub - discourse/mini_sql: a minimal, fast, safe sql executor · GitHub (has issues)
Etc…
A good litmus test is “more than 20 stars” perhaps
Interesting, I wonder why that isn’t disabled…(edit: ah, we don’t disable if issues exist on the repo)
I can go enable it for the other repos, not a problem.
Here are the repos where I’ll be enabling issues (if not already enabled):
GitHub - discourse/discourse_api: Ruby API for Discourse · GitHub
GitHub - discourse/discourse_theme: CLI helper for developing Discourse themes · GitHub
GitHub - discourse/email_reply_trimmer: Library to trim replies from plain text email. · GitHub
GitHub - discourse/logster: Log viewer UI and framework for rack · GitHub
GitHub - discourse/message_bus: A reliable and robust messaging bus for Ruby and Rack · GitHub
GitHub - discourse/mini_mime: minimal mime type library · GitHub
GitHub - discourse/mini_scheduler: Adds recurring jobs for Sidekiq · GitHub
GitHub - discourse/mini_sql: a minimal, fast, safe sql executor · GitHub
GitHub - discourse/onebox: (DEPRECATED) A gem for turning URLs into website previews · GitHub
GitHub - discourse/prometheus_exporter: A framework for collecting and aggregating prometheus metrics · GitHub
GitHub - discourse/pups: Simple yaml based bootstrapper for Linux machines · GitHub
GitHub - discourse/rails_failover · GitHub
GitHub - discourse/rails_multisite: Multi tenancy for Rails applications · GitHub
Look good Sam?
I think we can still keep issues off on discourse_api and discourse_theme
The rest looks good ![]()
If I understand correctly, it seems like the criteria is something like: “is this gem intended also to be valuable to projects that don’t have anything specifically to do with discourse?”
Issues enabled on the repos. Tooling updated to ensure issues aren’t disabled again on the above list.