Organizational Structure and Governance - Amendment No. 3 ABSTRACT

TeapotChat Administrator Council
Request For Comments: 7
Category: Standards Track
Status: Standard

Netizen Land - The Internet
Wael Karram
December 2024

This document describes the organizational and governance structure for TeapotChat. Subject to amendment at a later date.
Third amendment to define network bylaws.

Status of This Memo

This document specifies a standards track for the TeapotChat network, and requests discussion and suggestions for improvement.
Distribution of this memo is limited strictly to authorized network administrators within the teapot chat network or any third party authorized by them.

Copyright Notice

Copyright (C) 2024 TeapotChat Administrator Council. All rights reserved.

Table of Contents

. . . . . . . . . . . . . . . . . . . . . . .
3

. . . . . . . . . . . . . . . . . . . . .
3

. . . . . . . . . . . . . . . . . . . .
3

. . . . . . . . . . . . . . . .
4

. . . . . . . . . . . . . . .
4

. . . . . . . . . . . . . . . . . . . .
4

. . . . . . . . . . . . . . . . . . . .
4

1. Introduction

1.1. Overview

Running internet-facing systems which are spread across time zones, administrators and different physical hardware is complicated and requires coordination and a clear operational structure of the organization. This document aims to denote what structure shall be followed by TeapotChat concerning administration. This amendment creates a mechanism to create and enfore network bylaws.

1.2. Terminology

Definition:
The TeapotChat Network Bylaws (or simply: network bylaws) are a set of laws codified by the Upper Council to aid in network management.
The keywords denoting requirements, including optional requirements, shall be interpreted as defined in IETF RFC 2119.

2. TeapotChat Network Bylaws

2.1. Creation and Removal

Network bylaws come into existence by a major-type vote of the core administration team, and so too does their removal behave similarly.
Note that both creation and removal have a reserved veto right for any of the core council members, so long they inform the others of their reasons for vetoing the motion within 24 hours of the veto.

2.2. Publication

Network bylaws MUST be published somewhere accessible (reasonably so) to the users of the network, examples include (but aren’t limited to) the TeapotChat website and the MOTD text sent by the different nodes on the network.

2.3. Enforcement

Enforcement of network bylaws happens in two tiers: channel operators are forced to enforce them in their own channels (failure to do so might incur penalties as decided by the core adminstrative council).
Ultimately though, enforcement falls upon the shoulders of network aides, net ops and the core adminsistrative council (or whomever said council wishes to delegate this task to).
Sanctions to be levied against offending user are to be decided by the council per law. The council is allowed to give space for the enforcer’s judgment.

Authors’ Addresses:

Wael Karram - wael@waelk.tech/wael@teapot.chat