A recent manifest spec thread lead to a discussion about the group's "top-posting" policy which is a good segue to remind everyone we do have some expectations on the usage of the group's mail lists and I'll quote it here ...

[[
<http://www.w3.org/2008/webapps/wiki/WorkMode#Mail_List_Policy.2C_Usage.2C_Etiquette.2C_etc.>

*WebApps' members appreciate and encourage frank technical discussions on our mail lists but all discussions must be done in a respectful manner. Please note this respect requirement is codified in the Process Document via the following participation criteria "Social competence in one's role <http://www.w3.org/2005/10/Process-20051014/policies.html#ParticipationCriteria>". Additionally, seePositive Work Environment Task Force <http://www.w3.org/2007/06/PWET-statement-of-principles.html>and if you did not attend/Kindergarten/, we expect our list participants to adhere to the basic principles inAll I Really Need To Know I Learned In Kindergarten <http://www.peace.ca/kindergarten.htm>.*


We also expect our mail list participants to adhere to the following:

 * Follow basic/Netiquette/
   <http://en.wikipedia.org/wiki/Netiquette>such as avoiding typing in
   ALL CAPS
 * Messages should be encoded usingplain text
   <http://en.wikipedia.org/wiki/Plain_text>
 * Messages should not usetop-posting
   <http://en.wikipedia.org/wiki/Posting_style#Top-posting>. See
   theWHATWG's top-posting guidelines
   <http://wiki.whatwg.org/wiki/FAQ#Should_I_top-post_or_reply_inline.3F>for
   more information.
 * Subjects should be prefaced with the name of the spec (for
   example:/[DOM4] Blah, Blah, Blah/)
 * Attachments must follow theW3C Guidelines for Email Attachment
   Formats <http://www.w3.org/2002/03/email_attachment_formats.html>,
   in particular:
     o Avoid unnecessary email attachments.
     o Use an attachment only when it is likely to benefit to
       recipients. Otherwise, place the information (in plain text
       format) in the body of your message.
     o If an attachment is necessary, avoid formats that are virus
       prone, proprietary or platform dependent. For example, whenever
       possible you should use HTML instead of MS Word, PowerPoint or PDF.
     o FollowWeb Content Accessibility Guidelines
       <http://www.w3.org/TR/WAI-WEBCONTENT/>(WCAG)

]]

-Thanks, AB



Reply via email to