Internet DRAFT - draft-tjw-wgchairs-socialmedia
draft-tjw-wgchairs-socialmedia
Network Working Group T. Wicinski. (ed)
Internet-Draft 26 July 2023
Intended status: Informational
Expires: 27 January 2024
Social Media Suggestions for WGChairs
draft-tjw-wgchairs-socialmedia-00
Abstract
This memo provides some suggestions for working group chairs in
utilizing social media.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 27 January 2024.
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Long running working groups . . . . . . . . . . . . . . . . . 2
4. Using Social Media . . . . . . . . . . . . . . . . . . . . . 2
Wicinski. (ed) Expires 27 January 2024 [Page 1]
Internet-Draft wgchairs-socialmedia July 2023
5. Normative References . . . . . . . . . . . . . . . . . . . . 2
6. Informative References . . . . . . . . . . . . . . . . . . . 3
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction
Many working groups in the IETF are focused in their length and
direction. There are others which exist for a much longer period of
time, especially operations groups among others. With these groups
the chairs should make an effort to use other platforms than the
datatracker and ietf mailing lists to make work visible.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. DNS terminology is as described in
[RFC8499].
3. Long running working groups
There are several long running working groups in the IETF, and the
work touches other organizations. DNSOP, HTTPBIS, TLS are just a
few. With these groups, the chairs should adopt an approach of
"oversharing is a good thing".
Currently a number of working groups are using github to store
materials, documents being worked on, etc. But these working groups
should always be looking for new avenues to promote the documents
being working on in the working group.
4. Using Social Media
Currently, there is a tool to pull data from the datatracker API to
automate posting into twitter [https://github.com/ietf-github-
services/datatracker-tweet (https://github.com/ietf-github-services/
datatracker-tweet)]. This has proven useful for working groups.
DNSOP has modified this code to automate posting to Mastodon
[https://github.com/ietf-wg-dnsop/datatracker-toots
(https://github.com/ietf-wg-dnsop/datatracker-toots)].
The Working Group Chairs should take this under consideration for
busy, long running working groups.
5. Normative References
Wicinski. (ed) Expires 27 January 2024 [Page 2]
Internet-Draft wgchairs-socialmedia July 2023
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
6. Informative References
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>.
Acknowledgements
Mark Nottingham for the datatracker-tweet code, and for the quote
"Busy working groups should over share".
Author's Address
Tim Wicinski
Elkins, WV 26241
United States of America
Email: tjw.ietf@gmail.com
Wicinski. (ed) Expires 27 January 2024 [Page 3]
