New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
annoucements: Mention bitcoin-core-dev mailing list #648
Conversation
WIP |
Adding the core-dev mailing list is a good idea, but I'd suggest the text mention that it's a discussion list (in theory, at least) not just an announcements list. IMO, the problem with recommending users subscribe to discussion lists is that many of them aren't interested in the discussions, so they stop reading the posts and miss the actual announcements. (Heck, not even several major Bitcoin protocol devs want to read the posts on the protocol discussion list.) Maybe the new list infrastructure will allow us to create a third announcements-only list (e.g. every post must be manually approved) so we can restore the old list feature. Alternatively, we could just use a commercial email service designed to deliver blasts (I think this has been opposed in the past based on concerns over sharing user emails with a commercial service; I personally think it's better than not having an announcements list at all); this can be combined with an rss-to-email feature if we wanted to automatically send readers posts using this website's announcement tag. |
I am not aware that it has been used for anything other than update reminders in the past, but if we want to have to separate mailing list I won't object. Example |
Heh, good point. |
Concept ACK. In practice it's not used as a discussion list, to be honest I wouldn't really like it to be used for discussion. IRC and github together cover the project's communication quite well. We don't need a discussion mailing list. So I'm ok with officially turning it an announcement list where only specific people can post, and/or all posts need to be approved. |
Sorry for waiting so long with this I only just realized I can do this myself 🤦♀️ I've changed the settings of https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two tiny changes needed. Otherwise LGTM. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested ACK fb9acf7 Thanks!
0494064 Apply #912 to japanese page (azuchi) 3c11c0d Apply #772 to japanese page (azuchi) 118bb6b Change freenode to libera in japanese translation (azuchi) bf7b505 Update japanese translation of meeting pages (azuchi) 111784b Update japanese translation to apply #648 (azuchi) 5fe0857 Apply #749 to japanese page (azuchi) b469d0e Update japanese translation of contribute page (azuchi) Pull request description: The following PR changes also apply to the japanese translation. * #648 * #714 * #759 * #749 Top commit has no ACKs. Tree-SHA512: dc1ebd514b392f9bc66450a0aad8b77beba33320db2d384b5d0a5dd8483a496dd415ecbb56d0bcc42cbf48e64dba62b36b741399638e2b9805051f068bef0a26
No description provided.