Quick reminder (or clarification) about the workflow on SourceHut

GitHub has trained you to open issues for *everything*, including support requests, asking questions, feature requests, bug reports, and so on.

On SourceHut, you should not do this. We have mailing lists, and your first stop should be a project-discuss or project-users mailing list. Only when you have confirmed that you have a new bug or accepted feature request should you file a ticket on the bug tracker. This prevents clogging up the bug tracker with duplicate or poorly thought-out tickets, and usually gets you better support for your problem too.

Thinking about changing the default permissions for trackers to prohibit public posting to re-enforce this.

Follow

@sir Would I be correct in interpreting "...the default permissions" to mean that the repository owner could enable public posting if (s)he really likes working that way?

I am all for sane defaults, but I also see the value of options.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml