Update links and markdown

w3c · Jan 9, 2025 · c59b9a2 · c59b9a2
1 parent 1efbeba
commit c59b9a2
Show file tree

Hide file tree

Showing 3 changed files with 43 additions and 44 deletions.
diff --git a/teamcontact/liaison-role.md b/teamcontact/liaison-role.md
@@ -3,33 +3,33 @@ title: Role of Liaison
 toc: false
 ---
 
-The [Staff Contact](staff-contact) for a Working Group, with the [Chair's](chairs-role) assistance, appoints a liaison as needed where two groups have strong dependencies; see the list of [W3C liaisons](/2001/11/StdLiaison). The Liaison's primary role is to facilitate resolution of the dependency between the two groups.
+The [Staff Contact](role.md) for a Working Group, with the [Chair's](../chair/role.md) assistance, appoints a liaison as needed where two groups have strong dependencies; see the list of [W3C liaisons](https://www.w3.org/liaisons/). The Liaison's primary role is to facilitate resolution of the dependency between the two groups.
 
 An overall question: is there always a "Group A" & "Group B," in other words a "home" group that is having its requirements considered in a "host" (or 'target'??) group, or is the liaisoning relationship sometimes completely mutual?
 
 
 ## Ensures adequate Dependency statement
 
-- Is familiar with [W3C Process](/policies/process/) and [Member Guide](../).
+- Is familiar with [W3C Process](https://www.w3.org/policies/process/) and the [W3C Guide](../).
 
 - Reviews (hopefully) existing dependency statement, otherwise ensures that appropriate dependency statement is written.
 - Contributes additional ideas to dependency statement as needed to update or make more accurate.
 
 ## Monitors discussion in both Groups
 
-- Keeps current with discussion and document progress in both Group? (?Should a liaison have to fulfill active membership requirements in both groups? could be prohibitive)
+- Keeps current with discussion and document progress in both Groups? (?Should a liaison have to fulfill active membership requirements in both groups? could be prohibitive)
 - Monitors status of technical issues related to areas of dependency.
 - Maintains coordination with Chairs of both Groups.
 
 ## Keep each Group informed of the other's requirements & timelines
 
 
-- Notifies either group when dependency issues need discussion/negotiation.
-- Explain, or ensures explanation of, technology or requirements of the other Group as needed (e.g., a tutorial, for instance of Group B's technology for Group A's requirements exploration)
+- Notifies either Group when dependency issues need discussion/negotiation.
+- Explain, or ensures explanation of, technology or requirements of the other Group as needed (e.g., a tutorial, for instance of Group B's technology for Group A's requirements exploration).
 
 ## Ensure resolution of dependencies
 
-- Ensures discussion and consensus in Group A on requirements to bring to Group B
+- Ensures discussion and consensus in Group A on requirements to bring to Group B.
 - Represents requirements of Group A to Group B.
-- Assist in negotiating requirements of Group A with Group B *with assistance of Staff Contact, and Project Lead as needed.*
-- Brings back follow-up items for discussion as needed...
+- Assists in negotiating requirements of Group A with Group B *with assistance of Staff Contact, and Project Lead as needed.*
+- Brings back follow-up items for discussion as needed...
diff --git a/teamcontact/remote-maintainers.md b/teamcontact/remote-maintainers.md
@@ -7,31 +7,31 @@ W3C's mailing lists are managed using a customized version of SmartList.
 
 ## E-mail command interface
 
-Many W3C lists allow people to sub and unsub using an [e-mail command interface](https://www.w3.org/Mail/Request).
+Many W3C lists allow people to sub and unsub using an [e-mail command interface](https://www.w3.org/email/).
 
 ## Web interface
 
 The [List admin tool](https://lists.w3.org/admin/manage) allows list maintainers to add or remove subscribers, view info about the list's config, and view recent log entries.
 
-If you need more info about a list that is not provided by the list admin tool, please contact &lt;[[email protected]](mailto:[email protected])&gt;.
+If you need more info about a list that is not provided by the list admin tool, please contact [[email protected]](mailto:[email protected]).
 
 ## Handling \[Moderator Action] messages
 
-If your mailing list has posting restrictions enabled and a previously unknown address sends mail to the list, you will receive a message with \[Moderator Action] prepended to the Subject, e.g.:
+If your mailing list has posting restrictions enabled and a previously unknown address sends mail to the list, you will receive a message with `[Moderator Action]` prepended to the Subject, e.g.:
 
 > `Subject: [Moderator Action] original subject`
 
-If this is a legitimate message for your list, you should approve it through to the list using the [Moderator action queue review](https://lists.w3.org/admin/moderate) web interface or your mail client's "bounce", "resend", or "redirect" feature. Smartlist will remove the \[Moderator Action] prefix and the message will appear to come from the original sender (and not from you). Some custom headers may be added to indicate you forwarded the mail, for example `Resent-From:`.
+If this is a legitimate message for your list, you should approve it through to the list using the [Moderator action queue review](https://lists.w3.org/admin/moderate) web interface or your mail client's "bounce", "resend", or "redirect" feature. Smartlist will remove the `[Moderator Action]` prefix and the message will appear to come from the original sender (and not from you). Some custom headers may be added to indicate you forwarded the mail, for example `Resent-From`.
 
 If a message was sent to multiple mailing lists, the easiest way to figure out which list(s) caused the moderator action, is to display / view the `X-Envelope-To` header.
 
 Here are some notes on how to handle these messages in various mail clients:
 
-- For Thunderbird you need [this extension](https://addons.mozilla.org/en-US/thunderbird/addon/mailredirect/). Although it doesn't allow you to edit the subject line, so it will still say \[Moderator Action] on the outward-going mail, as pointed out above the W3C servers strip it off.
-- For Mac Mail, hit shift+cmd+e, or use the "Redirect" button that you can add to your Toolbar
-- [Outlook 2000](http://web.archive.org/web/20030720050852/spamassassin.taint.org/faq/index.cgi?req=show&file=faq03.003.htp)
-- For Gmail, see [Bouncing a message from Gmail](http://intertwingly.net/blog/2011/04/03/Bouncing-a-message-from-Gmail) by Sam Ruby.
-- For mutt, type 'b' to bounce then enter the list's address.
+- For Thunderbird you need the [Simple Mail Redirection extension](https://addons.thunderbird.net/en-US/thunderbird/addon/simple-mail-redirection/). Although it doesn't allow you to edit the subject line, so it will still say `[Moderator Action]` on the outward-going mail, as pointed out above the W3C servers strip it off.
+- For Mac Mail, hit `shift+cmd+e`, or use the "Redirect" button that you can add to your Toolbar
+- [Outlook 2000](https://web.archive.org/web/20030720050852/spamassassin.taint.org/faq/index.cgi?req=show&file=faq03.003.htp)
+- For Gmail, see [Bouncing a message from Gmail](https://intertwingly.net/blog/2011/04/03/Bouncing-a-message-from-Gmail) by Sam Ruby.
+- For mutt, type '`b`' to bounce then enter the list's address.
 
 ## Handling \[Moderator Action (size limit exceeded)] messages
 
@@ -40,16 +40,15 @@ You can find the size limit in the "configuration" information of a mailing list
 A message may be stuck because of an attachment that is too large, and the list moderator may not bypass a list's size limit. Here's how to proceed in this case:
 
 1. Forward to an archive mailing list (see below for guidance)
-2. Find the link of the attachment(s) in the list web archive
-3. Go back to your mailer:
+1. Find the link of the attachment(s) in the list web archive
+1. Go back to your mailer:
 
    1. strip the attachment(s) from the mail to moderate
-   2. type somewhere e.g., at the top, that the attachment(s) is/are archived elsewhere and paste the link
-   3. redirect
+   1. type somewhere e.g., at the top, that the attachment(s) is/are archived elsewhere and paste the link
+   1. redirect
 
 Guidance for which archive mailing list to choose depending on the confidentiality-level of the target list:
 
-
 member-visible: [email protected] (indicative size limit: 25971520 bytes)
 : cf. [https://lists.w3.org/Archives/Member/w3c-archive/](https://lists.w3.org/Archives/Member/w3c-archive/)
 
@@ -59,6 +58,6 @@ team-only: [email protected] (indicative size limit: 41943040 bytes)
 public: [email protected] (indicative size limit: 41943040 bytes)
 : cf. [https://lists.w3.org/Archives/Public/www-archive/](https://lists.w3.org/Archives/Public/www-archive/)
 
-If you have useful info not listed above, please contribute it by [editing this page](https://github.com/w3c/Guide/blob/master/teamcontact/RemoteMaintainers.html) or by sending email to [[email protected]](mailto:[email protected]).
+If you have useful info not listed above, please contribute it by [editing this page](https://github.com/w3c/guide/blob/master/teamcontact/remote-maintainers.md) or by sending email to [[email protected]](mailto:[email protected]).
 
 If you would like someone to be able to post directly to a given list without having their messages flagged for `[Moderator action]`, use the [list admin tool](https://lists.w3.org/admin/manage) to add their email address to the "accept2" file for the list in question. Future messages from their address will be distributed directly to the list without needing to be moderated.
diff --git a/teamcontact/role.md b/teamcontact/role.md
@@ -3,43 +3,43 @@ title: Role of the Team Contact
 toc: false
 ---
 
-*Note:* W3C designates a Team Contact to monitor the progress of every [Submission request](../Project/Submission) and to write a Team Comment which is published as part of the Submission. This document, however, discusses the Team Contact of a Working Group, rather than the Team Contact for a Submission.
+*Note:* W3C designates a Team Contact to monitor the progress of every [Submission request](https://www.w3.org/Project/Submission) and to write a Team Comment which is published as part of the Submission. This document, however, discusses the Team Contact of a Working Group, rather than the Team Contact for a Submission.
 
-W3C designates a Team Contact ("Contact") for every W3C Working Group and Interest Group ("Group"). The Contact helps set the strategic direction of the Group in the chartering phase. Many of the Contact's tasks involve helping the Chair complete his or her [roles](chair-roles.html), such as ensuring that the group runs smoothly, actively aiding consensus building, ensuring wide review of specifications, tracking feedback from implementors, and so forth. The Team Contact reports to the Project Lead.
+W3C designates a Team Contact ("Contact") for every W3C Working Group and Interest Group ("Group"). The Contact helps set the strategic direction of the Group in the chartering phase. Many of the Contact's tasks involve helping the Chair complete his or her [roles](../chair/role.md), such as ensuring that the group runs smoothly, actively aiding consensus building, ensuring wide review of specifications, tracking feedback from implementors, and so forth. The Team Contact reports to the Project Lead.
 
 ## Technical coordination
 
 Coordination and communication is a primary role for the Team Contact, who acts as the interface between the Group Chair ("Chair"), Group Members, other Working Groups, and the W3C Team:
 
-{% include quote.html content="The team contact role is largely one of communication. This involves becoming as aware as possible of the technical requirements and issues in the group, and simultaneously being aware of the general [architecture of the Web](/TR/webarch) as evolving in the other work of W3C. This is of course a general responsibility of the group - and the chair and group members have this duty too. The staff contact has the benefit of being employed full time in W3C, and having access to other team members. The team contact's existence does not dilute in any way the group's obligation to ensure the technology interoperates with that of other groups. " footer="TimBL 2001-09-11" %}
+{% include quote.html content="The team contact role is largely one of communication. This involves becoming as aware as possible of the technical requirements and issues in the group, and simultaneously being aware of the general [architecture of the Web](https://www.w3.org/TR/webarch/) as evolving in the other work of W3C. This is of course a general responsibility of the group - and the chair and group members have this duty too. The staff contact has the benefit of being employed full time in W3C, and having access to other team members. The team contact's existence does not dilute in any way the group's obligation to ensure the technology interoperates with that of other groups. " footer="TimBL 2001-09-11" %}
 
 The Team Contact is also charged with representing the views of the Team to the Working group. Just as all Members do not have the same views, neither does all the Team. The Team Contact collects the various viewpoints and summarizes them so that the Working Group benefits from the widest range of inputs. Where the Team does not have a single position, it is inappropriate to merely abstain. Instead, the various points of view should be summarized. For a good example of Team input where the Team did not have consensus, see [Team response on the 'canvas' element](https://lists.w3.org/Archives/Public/public-html/2007Nov/0449.html).
 
 ## Assist Group organizers in creating charter and convening Group
 
 - *Assist* in creating the group charter. When rechartering, discuss the proposed charter with the existing Working group and with the Team. See also the [charter template](https://w3c.github.io/charter-drafts/charter-template.html) and [ongoing charters](https://github.com/w3c/strategy/issues?q=label%3Acharter).
-- Act as the [charter shepherd](../process/charter.html#charter-shepherd). If approved, the Team will announce the creation of the group and ensures a call for participation is announced.
+- Act as the [charter shepherd](../process/charter.md#charter-shepherd). If approved, the Team will announce the creation of the group and ensures a call for participation is announced.
 - *Assist* the organizers in understanding dependencies on other groups, and act as coordinator when necessary.
 - *Ensure* that the Chair is familiar with key documents, including:
 
-  - [The Process Document](/policies/process/)
+  - [The Process Document](https://www.w3.org/policies/process/)
 
-    - [General Information about Groups](/policies/process/#GAGeneral)
-    - [Working Groups](/policies/process/#GroupsWG)
-    - [Interest Groups](/policies/process/#GroupsIG)
+    - [General Information about Groups](https://www.w3.org/policies/process/#GAGeneral)
+    - [Working Groups](https://www.w3.org/policies/process/#GroupsWG)
+    - [Interest Groups](https://www.w3.org/policies/process/#GroupsIG)
   - [The Art of Consensus](../)
 
-    - [Pubrules](/pubrules)
-    - [W3C Invited Experts](/invited-experts/) principles and review requirements
+    - [Pubrules](https://www.w3.org/pubrules/)
+    - [W3C Invited Experts](https://www.w3.org/invited-experts/) principles and review requirements
     - [Archive of [email protected]](https://lists.w3.org/Archives/Member/chairs/) (member-only)
-  - [Code of Conduct](/policies/code-of-conduct/)
-  - [Antitrust and competition policy](/policies/antitrust/)
-- *Ensure* that Chair is marked as such (checkbox) in the [group's homepage](/groups/) (which subscribes him/her to [[email protected]](mailto:[email protected]))
-- *Ensure* that Group Members are oriented to W3C process and their roles when Group convenes or new Group Members join.
+  - [Code of Conduct](https://www.w3.org/policies/code-of-conduct/)
+  - [Antitrust and competition policy](https://www.w3.org/policies/antitrust/)
+- *Ensure* that Chair is marked as such in the [group's homepage](https://www.w3.org/groups/) (which subscribes him/her to [email protected])
+- *Ensure* that Group Members are oriented to W3C Process and their roles when Group convenes or new Group Members join.
 - *Ensure* that Group sets milestones for document development, charter renewals, etc.
 - *Ensure* that Chair understands the different stages of document development (Editor's Drafts, Working Drafts, Candidate Recommendation, Proposed Recommendations, Recommendations), and confidentiality and status issues for each stage.
 - *Assist* Chair in assessing need for charter renewal and/or closing of the Group.
-- *Ensure* that previous Chair is removed in the [group's homepage](/groups/).
+- *Ensure* that previous Chair is removed in the [group's homepage](https://www.w3.org/groups/).
 
 ## Monitor group participation and operations
 
@@ -60,16 +60,16 @@ The Team Contact is also charged with representing the views of the Team to the
 - *Assist* the Communications Team and Chair in soliciting testimonials for press releases.
 - \[*Active Role*] Work with Communications Team to draft press releases and/or review for accuracy.
 - \[*Active Role*] Coordinate the act of publishing documents with the Communications and Sys/Web Teams.
-- \[Active Role] Follow communications with other W3C groups and functions to identify areas where coordination is needed.
+- \[*Active Role*] Follow communications with other W3C groups and functions to identify areas where coordination is needed.
 - *Assist* Chair in coordinating with other W3C groups as needed.
 - *Ensure* liaisons between Group and other W3C groups are assigned as needed.
 - \[*Active Role*] Coordinate with the Systems Team to ensure that Chair and group Editors have appropriate access to the W3C site, and that their access works, e.g. GitHub.
 - *Ensure* that Group editors understand how to use [GitHub at W3C](https://w3c.github.io/).
 - *Ensure*, before publishing any Group document in W3C/TR space, that it is:
 
-  1. Being published properly (see [Pubrules](/pubrules)).
+  1. Being published properly (see [Pubrules](https://www.w3.org/pubrules/)).
   2. Spell-checked
-  3. HTML validated (see, for example, the [HTML validator service](http://validator.w3.org/)).
-  4. CSS validated (see, for example, the [CSS validator](http://jigsaw.w3.org/css-validator/)).
-  5. Accessible (see [Accessibility evaluation resources](/WAI/eval/Overview.html))
-  6. Published in the appropriate places, using Team conventions for document status information, naming schemes, etc.
+  3. HTML validated (see, for example, the [HTML validator service](https://validator.w3.org/)).
+  4. CSS validated (see, for example, the [CSS validator](https://jigsaw.w3.org/css-validator/)).
+  5. Accessible (see [Accessibility evaluation resources](https://www.w3.org/WAI/eval/))
+  6. Published in the appropriate places, using Team conventions for document status information, naming schemes, etc.