• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Mailing List Policies

This version was saved 14 years, 4 months ago View current version     Page history
Saved by Chris Messina
on November 29, 2009 at 5:38:04 pm
 
This page is a work in progress. You may comment on this page by requesting permission to edit and contribute to this wiki.

The contents of this page:

  • Introduction
  • Policies
  • Credits 

Introduction

The community mailing lists cover are divided among several topics and constitute one of the primary "places" where members of the OpenID and identity communities come together to confer about digital identity, technology and protocol development, security, user experience, community enrichment, and the spread of OpenID generally.

The community is comprised of individuals, representatives from companies, governments, and academic institutions, and technologists, designers, and all manner of interested person from all over the world. Therefore, critical to productive, useful, and inclusive discussions is an understanding of what kind of behaviors and contributions the community values and benefits from. 

This document is an attempt to provide a guide describing expectations, etiquette, and techniques for creating a positive and constructive atmosphere.

Please read the entire document before your first post to one of the lists, as it explains the list policies and contains a few words about the kind of culture we've created and hope to maintain.


Policies

  • Unsubscribing. Do subscribe and unsubscribe using the web-based list management tool found here. Don't make the whole list sad over your departure by mailing everyone about it.
  • Crossposting. Do send each message to ONE and only ONE list at a time. Don't send a single message to multiple lists. If you want to send your message to multiple lists, do so individually so that replies maintain proper context. This applies to all lists, not just OpenID-managed lists.
  • Efficient replies. Do trim down replies to the essential content needed to make your point. Do accurately present and cite quoted material, but prune down unrelated content with ruthless abandon. Everyone else will thank you for it. Don't quote long messages completely and respond with single words or votes. Instead, only include the part of the original message that you wish to endorse or vote against.
  • Reply inline. Do insert your replies at the appropriate insertion point in a reply. Don't just reply at the top of a message (so-called "top posting") because your message will lack context and be difficult to respond to effectively.
  • Keep your signature short. The shorter the better. Use a standard sig-separator like dash dash space return ("--").
  • Employment solicitations, etc. Don't solicit members of the OpenID mailing list for employment, working on custom applications, or specific implementations, especially if they will not result in code or product that the entire community will freely benefit from. There are plenty of  job boards, websites, mailing lists, and other venues for helping stimulate your economic situation. Do use them instead. When in doubt, ask the list owner first.
  • Commercial announcements. Don’t send advertisements to the list. Do share announcements of new tools, software, publications, and other resources. In other words, a one-time announcement like "I just published a new book called 'OpenID for Moms' with O’Hara and Friends" is okay, but "Buy my book at 30% off and get a free back massager!" is not. If you're not sure, ask the list owner before posting.
  •  

Credits

These policies were inspired by the microformats mailing list policies, which in turn were influenced by the css-discuss mailing list policies.

Comments (0)

You don't have permission to comment on this page.