TC.POLICY last updated: 17 November 2001 (Document contains suggested guidelines for conduct in the HumanMarkup Technical Committee.) ------------------------ INTRODUCTION -------------- These are only recommendations, as sometimes they are not appropriate or applicable. Nonetheless, these were brought up by various members over the course of our TC in order to facilitate the discussion process. ------------------------------------------------------ DOCUMENT TEXT ----- -Text-only with no line breaks (no rtf or anything) -No columns -No manual indents, tabs only, no multiple word spaces ------------------------------------------------------ POST TEXT ----- Posts are to be made with as simple a character set as possible, through embedded text (no attachments). If needed, feel free to use underlines or boldface. However, please do not use embedded HTML. If you would like to use additional character sets, fonts, or graphics, please post a link to a URL. Reason: This ensures accessibility of information for text based email clients, and easy reading of documents. ------------------------------------------------------ PERSONAL INTRODUCTION ----- Please post a personal introduction about yourself to the group. 1) interests 2) background 3) desired contributions 4) goal for HumanMarkup effort Reason: This helps us know where each contributor is coming from, and what skills we all have ------------------------------------------------------ EXPLICIT DATES ----- Dates should ideally follow European Convention: 20 October 2001 Reason: This prevents confusion between different conventions (i.e. 10-09-01 may be confusing). ------------------------------------------------------ DOCUMENT-CENTRIC ---- -Post in terms of updated revisions of *documents*, rather than 'posts', whenever possible. -Sometimes, however, these aren't appropriate...that is clear. -Documents should be posted to site, and the administrators will ensure that they are met. -Documents include those that are already posted, or those that you are considering working on. Reason: This promotes referenceability and accessibility of material ------------------------------------------------------ SUBJECT LINE ---- -Adhere to the subject of the post, and when possible, use the following format. -Whenever possible, tie each subject to a specific "document" document: subtopic: subtopic: subtopic: subject "TC.deliverables: Jan312001: addRELAXschema" "TC.policy: footnote: newmembers" Reason: This allows easier updating of key documents. Please be diligent about this, because it increases the likelihood that your ideas can reach fruition within the group. ------------------------------------------------------ ONE TOPIC AT A TIME ---- Posts are to address one topic at a time. Reason: This allows clearer indexing of ideas when referring back to posts. ------------------------------------------------------ TRAILING TEXT ------ -Snip off trailing trailing text at the end of a post, to keep them short and manageable Reason: This prevents long posts from getting too unwieldy and unmanageable ------------------------------------------------------ **INTERACTION AND FEEDBACK ----- -Posts are to be thoughtful, and relevant to the HumanMarkup TC. -Posts should be provocative and direct as possible. -Feedback is to be as honest and respectful as possible. -If you are not responded to, please _post_ again until response is given. Do not take lack of response personally. -Do not feel the need to catch up with the posts if behind. Simply restate your thoughts or ideas. Catching up sometimes is impossible. -Any concerns regarding specific members should be brought up with the TC Chair immediately. Reason: It is important to be cognizant of these issues to prevent getting caught up in destructive cycles of human miscommunication. This is the antithesis of the group's mission. ------------------------------------------------------ **WORKSTYLE ----- -Work is to be done on time, when possible. However, as a TC we realize they may need to be pushed back at times. -Do not take on a workload more than you feel you can handle. -If there is too much work, please let the subcommittee or committee chair know immediately. -Accountability is greater when formally accepting a task from a TC meeting. Reason: Important to address the qualities of proper workstyle for tasks within HumanMarkup to ensure we have clear expectations of each other. ------------------------------------------------------ **SUBCOMMITTEES POLICY ---- -Subcommittee chairs are responsible for all aspects of organizing the effort. -Discussion will take place on the initial mailing list. However, if the subcommittee chair feels the discussion is getting too large, a separate mailing list will be created at the request of the subcommittee chair to the HumanMarkup TC chair. Reason: Important to clarify the roles and progression of the evolution of the subcommittees to ensure resposnibilities are clear ------------------------------------------------------ **CHAT SERVICE ---- We are still considering how we can use the chat service to host our meetings. a) CURRENT: --------- The discussion list is preferred means of communication, but we also have a chat room available if discussion lists are not able to clarify certain technical discussion points. It is only supposed to be used for this purpose. Server: irc.openprojects.net Port: 6667 Channel: #humanml All sessions are required to be logged, and posted to the discussion board. Thanks. b) FUTURE: --------- Users have reported connectivity issues associated with IRC. Future chat service will most likely be hosted at About.com.