Re: [onap-tsc] Mailing list netiquette
> On Jan 8, 2019, at 6:02 PM, Krzysztof Opasiak wrote: > > Please share your opinion about above issues. I do agree having ML practices for ONAP would be beneficial, and I’m all in favour the two mentioned points. I’m not sure how to enforce but I believe it is more a best / educational practices. > If you would like to have some discussion about that or to present to > the broader audience on this topic I'm available during current event. I believe it worth having a discussion about this; could be a 15mn item during TSC meeting. Thanks, Alexis -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4462): https://lists.onap.org/g/onap-tsc/message/4462 Mute This Topic: https://lists.onap.org/mt/29073941/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[onap-tsc] Mailing list netiquette
Dear TSC members, As a follow up to my comment on ONAP wiki[1], I would like to propose to make ONAP mailing lists following USENET and other good ML practices followed by most of Open Source related mailing lists (for example [2]). Currently there is probably no defined (or at least I haven't found one) mailing list netiquette for ONAP. This results in: 1) HTML content being sent to the list This is not only annoying for people who for a security reasons read emails in plain text but also can be used as a potential attack vector to spread the malware to many ONAP developers at once even without having their emails. That's why many of open source mailing list (like linux kernel one for example) simply rejects all the emails that are not sent in plain text. 2) Top posting without any proper citing Why it is bad: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? It's very hard to follow the discussion when people use top posting. I don't want to blame anyone so I don't provide any link to the archive but I recommend to just try to open any longer (above 10 messages) topic and then try to read, understand and guess who wrote which part of the email and how a consensus has been reached. 3) Fancy html footers in emails html footers are really nice in a corporate environment but when it comes to mailing lists collaboration they cause only problems. First problem is related to #1 (HTML in ML is a potential security issue). Second one is very prosaic, when you read emails in plain text those footer are hard to be distinguished from email content because all the fancy formatting is stripped off. The alternative (which is recognized by most of email clients) to that is simple plain text footer separated with two dashes from email knowledge. Please share your opinion about above issues. If you would like to have some discussion about that or to present to the broader audience on this topic I'm available during current event. Footnotes: 1 - https://wiki.onap.org/display/DW/Mailing+Lists 2 - http://linux.sgms-centre.com/misc/netiquette.php -- Krzysztof Opasiak Samsung R Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4458): https://lists.onap.org/g/onap-tsc/message/4458 Mute This Topic: https://lists.onap.org/mt/29073941/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
