This is the real crux of the matter. The notion that making providing patches or PR's easier is IMO pointless until we solve how to deal with reviewing them. Which is really a resource issue. If someone really truly wants to help the project then review patches.
Doesn't the mailing list code send an email back saying that the email was delayed as sender isn't subscribed? I think that'll indicate to new people they'll did something wrong.
-
-
Wonder if we could just advise to create a community account and use that email. And then allow unmoderated emails from emails matching that database? Not sure how realistic it is to tie them together however.
-
they'd have to log into the list server at least. That said, right now it's enough to be subscribed to *any* list in order to be aallowed to post to most others. We could create a mode that says you just have to log into the listserver (which confirms your addr)
- 3 more replies
New conversation -
-
-
We do send a mail back, but we don't actually tell them the reason: https://gitlab.com/pglister/pglister/blob/master/mailtemplates/moderation_response.txt … That text can most likely be improved upon, of course. But I don't think it directly indicates "go subscribe to make this go away"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.