11JAN 97 Written
Last Modification - Amendment
5 May 2006
StarLink-IRC RULE #1: Do not annoy others.
StarLink-IRC RULE #2: Do not be too
Part I : Charter and Foundation
StarLink-IRC was originally founded on 15 July 1996
the purpose of providing IRC users with a good place to meet, exchange
ideas, and generally have fun. On 1 January 1997, these concepts were
in the StarLink-IRC network where the original spirit of communication,
cooperation and user support that has become our hallmark.
StarLink-IRC is a network
Our Services infrastructure support the channels that comprise the
homes, offices, meeting halls, and parks where people can safely meet,
exchange ideas and form 'families' and common interest groups.
The founding members of StarLink-IRC,
due deliberation, adopted the following principles:
- The inherent and self-evident rights, authorities
responsibilities of Host Services, Channel Services, and Users shall
- StarLink-IRC exists for the sole purpose of
its users with a safe, reliable, and secure place to chat.
- All Users shall, wherever possible, be provided
assistance, support, and a voice in network.
- Deliberate abuse or harassment of persons or
not be tolerated
- Abuse of authority is absolutely prohibited and
be dealt with swiftly and severely.
- StarLink-IRC Operations shall deal immediately
reports of abuse by members of StarLink-IRC organizations.
- Within a Channel, the Channel Manager defines
behavior and may deal with violators as they see fit.
StarLink-IRC balances the inherent
of free speech and the rights of users. Although supportive of
viewpoints and lifestyles, StarLink-IRC will NOT support advocacy of
or abuse of the rights or property of others. The following Special
- Channels and users providing or supporting Warez
software) distribution or acquisition.
- Openly pornographic channels soliciting,
conducting on-channel sexual activities.
- Channels and/or users advocating abuse of human
including cruelty, intolerance, child pornography, or similar subjects.
- Cloning or flooding for the purposes of
network or its users.
- Repeated abuse of privmsg or DCC chat to
or repeatedly harass users.
Violators will be permanently and immediately
from StarLink-IRC, possibly without warning or appeal. Relevant records
of prohibited activities or advocacy may be provided to appropriate
for further action.
Part II: StarLink-IRC Structure
StarLink-IRC is an interactive group
people who all have a common interest in the success of our network.
from affected parties will be solicited and considered. While
Groups are autonomous and not subject to review by other activities,
decisions affecting StarLink-IRC as a whole are subject to review by
Part II-A Services and Organizations
SERVICES: The technical or administrative functions that support
the network. De-facto Services are those which appear on a /map or
listing and are an integral part of the net. The principal services
by StarLink-IRC are:
- HOST Services: Systems which run the programs used by or for
- OPER Services: Global network control functions.
- CHAN Services: Channel-based control functions to channel
- AUX Services: Support features and functions messaging
mail lists, web pages, etc.
ORGANIZATIONS: StarLink-IRC Named Organizations are defined
which determine the character and nature of SERVICES and coordinates
implementation. The Five StarLink-IRC named organizations and
- OPERATIONS GROUP: Overall network coordination and policies.
- HOST SERVICES GROUP: Host Server and Networking (HOST
- Server Administration: Server Administration and
- Operator Services: Network Operation and Protection
- CHANNEL SERVICES GROUP: Channel Administration (CHAN Services)
- Registration: Channel Registration and Policy
- CService Representatives: Channel Operations assistance
- TECHNICAL SERVICES GROUP: Technical Activities (OPER Services,
- Routing Services: Connectivity Support and Testing
- Coding Services: Services Design, Development, Testing
- Web Services: World Wide Web Presence
- Mail List Services: Mailing List Administration
- USERS GROUP: User Representation
- Channel Owners (Channel Ownership)
- Channel Ops (Channel Operations)
Part II-B General Provisions
The founding administrators have agreed that, regardless of any
permissions or approvals deemed necessary, the unanimous consent of ALL
current Administrators is a prerequisite to permanently adding a server
to the network.
Service Administrator Authority
The authority of a service administrator over their service is
and final and includes: Addition, removal and discipline of priviliged
users and the proper implementation and management of services provided.
Nothing in this charter shall be construed to infringe upon the
property rights of any individual. The owner of any intellectual
used by StarLink-IRC by permission may withdraw such permission at any
time and for any reason. The domain name, StarLink-IRC.org, belongs
to the StarLink-IRC network as a whole. Network identifiers, logos, and
similar design elements that have been assigned or licensed to
belong to StarLink-IRC as a whole and not to any specific individual or
Structure and Representation within Groups
Structure: Named organizations shall determine their own
internal structure, and operating procedures.
Representation: Within a named organization, no
have more than ONE vote. Authorized proxy votes of absent voting
may be presented by anyone so authorized by the voting member.
Proxies: General proxies are prohibited. If a voting
be present, they shall appoint an authorized voting delegate for any
or votes. The selected delegate conveys all rights, authorities and
of the voting member. The delegate shall NOT be a current voting member
of the applicable group prior to their selection.
Network representatives are the privileged users of server,
or channel service functions who are charged with maintaining network
Network Representatives are NOT responsible for any activity
on a channel and will NOT interfere with internal channel operations,
When on a channel, Representatives are GUESTS of the channel and
act appropriately. In EMERGENCY situations, any Network Representative
may take immediate action to restore channel or network stability.
Use of special authority to act contrary to the wishes of
channel managers or operators is absolutely prohibited and may result
the loss of that authority.
StarLink-IRC OPERATIONS GROUP will ensure that any Network
found or reported to be abusing their authority is fairly investigated
and, if appropriate, disciplined by the appropriate group. HOST
GROUP will handle issues regarding IRC Operators and CHANNEL SERVICES
will address infractions by Channel Services members.
Part III: ORGANIZATIONAL RESPONSIBILITIES
Part III-A OPERATIONS GROUP
- StarLink-IRC Operations is a representative group that provides
coordination and network policy direction. No specific individual shall
be designated as head of or coordinator for the OPERATIONS GROUP.
- Voting Membership:
- The voting membership shall consist of ONE and only ONE
each named Group:
- HOST SERVICES GROUP (Host Services Delegate)
- CHANNEL SERVICES GROUP (Channel Services Delegate)
- TECHNICAL SERVICES GROUP (Technical Services Delegate)
- USERS GROUP (User Group Delegate)
- Mediate discussion and resolve conflicts between (or, if
among) its member groups. This group shall ensure that all members of
StarLink-IRC community are provided a voice in network activities,
of issues and decisions, and provided a safe and efficient network.
- None. No service or group shall be part of the Operations
Part III-B HOST SERVICES GROUP
- Administration and overall operation of StarLink-IRC servers. The
Services Coordinator shall ensure that Server Administration and
Services needs and interests are adequately represented and are
with the goals and spirit of the network.
- Voting Membership:
- Voting membership consists of TWO delegates for each connected
or server as follows: For IRC servers: ONE server administrator and ONE
operator on that server. For Services: ONE service owner/designer and
administrator of the service.
- Individual service administrators are totally responsible for
and management of their service.
- Server Administrators are expected to abide by any agreements
their affiliation with StarLink-IRC.
- For their systems, Server Administrators are responsible for
of service/server configuration changes and permissions or prohibitions
- IRC ops are the assistants, representatives and agents of their
Administrators. IRC ops shall safeguard the net from disruption and
timely assistance to users upon request.
Part III-C CHANNEL SERVICES GROUP
- Channel Services is responsible for channel registration, setup,
channel user assistance. The Channel Services Coordinator is
for ensuring that Channel Service activities support the user community
and are in concert with the overall spirit and charter of StarLink-IRC.
- Voting Membership:
- Voting membership consists of the StarLink-IRC Channel
Deputy Administrator, and the channel
- services programmer/owner.
- CService consists of experienced IRC channel managers, IRC
and Server Administrators who: WILL NOT enter into discussions on how a
channel is run WILL mediate discussions of channel managers. WILL
to provide stability to channels.
- Responsible for approving the initialization or deletion of
- Responsible for assisting users in maintaining channel stability,
questions, and assisting users in the proper utilization of
Part III-D TECHNICAL SERVICES
- Technical Services are responsible for evaluation, analysis,
and coordination of the various technical features and characteristics
of the network. The Technical Services Coordinator is
for ensuring coordination of technical activities both within the
SERVICES group and with StarLink-IRC OPERATIONS GROUP. For
discussion or other activities, the Technical Services Coordinator
ensure that appropriate representatives or experts are 1: given an
voice in overall StarLink-IRC operational decisions, and 2: provided
to groups or individuals as needed to perform their duties.
- Voting Membership:
- Voting membership shall consist of the Technical Services
and ONE member from each committee within the group.
- Each committee shall perform the activities shown below and
a coordinator or point of contact who is
- responsible for 1) ensuring committee activities are
performed in a
timely manner and 2) properly coordinated among affected
Routing Services Committee:
- Connectivity Support and Testing
Coding Services Committee:
- Services Design, Development, Testing
Web Services Committee:
Mail List Services Committee:
- Mailing List Administration
Part III-E USER GROUP
- Represents all users of the StarLink-IRC network. The selection,
and roles of the User Group Coordinator will be
- determined at a later date and, upon ratification by NETWORK
become part of this charter.
- Voting Membership:
- All channel managers, operators, and visitors are members of
- Channel managers are the registered "owners" of their
- Shall ensure that channel content and behavior is within the
of the StarLink-IRC Charter.
- May appoint additional channel operators as deemed necessary.
- Are the final authority within the channel.
- Are NOT responsible for other-channel activities of their
- Channel Operators:
- Are representatives and agents of the Channel Manager
- Should maintain order within the channel as needed
- Abuse on Other Channels
- Abusive behavior on other channels by Channel Managers will
- Channel managers repeatedly violating this rule may be
WILL be removed or suspended for an indefinite period.
Part IV: Channel Registration
Part IV-A Registration
Given the nature of IRC networks, all channels are inherently
.. they only exist because a user or bot sets them up. The registration
process recognizes this and is designed to reduce the administrivia
found in channel registrations.
In general, only one channel will be registered to any
Failure of a channel owner to appear (authenticate and join the
for 45 consecutive days will constitute abandonment of the channel.
- CService will review applications for content and
send a response letter to the applicant.
- CService may deny registration to anyone who has been abusive
net or its users.
- Any registered Channel may be removed for necessary and
- Temporary channels may be set up from time to time for
but must be either removed or formally registered as soon as
- CService will periodically purge channels that appear to be
- With suitable justification, a channel that has been
will be immediately reinstated.
Part IV-B Changes
- The channel manager must send an E-mail request to the current
registration address stating:
- The channel name. and owner identification (userID, owner
- The requested action (Addition, Deletion, Transfer,
- The reason for the request.
- Transfer: The channel owner may request that channel
ownership be transferred
to another individual. Such transfers are final and, upon completion,
requester may not claim any further ownership of the channel.
- De-Registration: Upon request of the channel manager, the
bot may be permanently removed from a channel. Note: A deleted channel
will NOT be re-registered to the same owner within 30 days.
Part III-C Objections
Any reasonable objection to a channel will be considered by
Upon receipt of an objection, the CSC will:
- Immediately convene a meeting of any available CService
determine the seriousness and nature of the objection.
- Designate or set up a channel for discussion of the issues
due to the nature of the objection).
- The discussion date/time will be set to accommodate as many
individuals as possible yet still provide a timely response.
- No final decision will be made until BOTH sides of any
or objection have been heard.
- Meeting attendance by parties NOT involved in the issues will
AMENDMENT 1: Founding Membership
During the meeting establishing this charter, the following
were established. Each group and service will meet as needed to make
to these positions. Link to AMENDMENT 1
AMENDMENT 2: Current Membership
As needed, SL-IRC makes adjustments to positions. Current Membership
is shown on the StarLink-IRC organization web
AMENDMENT 3: Advertising
This charter is hereby amended to include:
Advertising/spamming is prohibited. Particularly advertising of
AMENDMENT 4: Deception
May 2003. This charter is hereby amended to include:
Malicious deception is annoying and thus prohibited. Malicious
is simply lying to accomplish a dishonorable purpose. An example is
posing as a network staff member, channel op, or anyone else in order
falsely obtain trust or privilege.
Specifically, malicious deception in order to obtain personal
or undue control in a channel is absolutely prohibited and will result
in loss of privileges up to and including being banned from the
Channel Services may or may not consider reinstating privileges lost
to this Amendment as they see fit.
Starlink-IRC staff and administrators will collectively enforce any
sanctions resulting from violations of this rule.
AMENDMENT 5: Mail System
May 2006. This charter is
hereby amended to include:
SLIRC Mail System Charter
Proper mail list management is critical to the reputation and character
of the net. It doesn't take much to end up on a bunch of
blacklists these days. Therefore, the starlink-irc.org domain
owner will be the final authority on the mail lists that will exist and
their management. Within that authority, the Channel Services
administrator will determine the SLIRC-Register membership list.
The SL-IRC Mail Administrator will manage all mail list activities and
functions. The Mail Administrator is selected or removed by the
SL-IRC domain owner as necessary.
A. Lists. There are three network email lists,
All lists are "open" for posting to by members and non-members.
for non-members. Unmoderated for members.
restricted to SL-IRC Staff
for non-members. Unmoderated for members
restricted to CService Only
posts are moderated.
Unrestricted membership (subject to admin control for abuses)
B. Net Aliases. Email aliases for the net include:
webmaster@ to webmaster
newsletter@ to newsletter editor(s)
C. Individual Aliases;
Additional aliases for individuals (staff) may be available at the
discretion and willingness of the services provider being used.
D. Administration and Management
The Mail Adminitrator:
monitors and provide general management of all lists
selects and approve helpers, moderators or assistants as necessary.
and deletes list members, (except SLIRC-Register).
as the primary point of contact for changes to email aliases
the final authority on mail list management, issues, rules, and
These are basic principles of operation and may be modified as
necessary by the Mail Administrator.
One person will monitor all lists as primary with alternates as
needed. For the staff lists, it's cleaning up spam mostly.
The administrator and helpers will work out the best way to share
duties so that there is backup without too much redundancy.
Staff Mail: Mail received at slirc-mail that should be addressed
to staff (bans, glines, general administrivia) will probably be thrown
away. The staff knows which lists they should be using. If
you posted to general mail and it didn't show up, you might want to
resend it to the right list.
Newsletter Mail: Mail received that is FOR the newsletter should be
redirected to the newsletter editor. Time permitting, send a note
back to the user and tell them that in the future, submissions should
be sent directly to firstname.lastname@example.org.
General Mail; The mail list is a sensitive critter. Users
will unsubscribe if there is too much traffic on it that isn't
interesting to them. If staff want to exchange chatter on a post,
they should use SLIRCERS or even wallops (we have a chat net, after
all). Staff should NOT reply to general mail postings on the
general mail list unless it is a critical correction or expansion.
Forum: We have a forum over on gmail. There is virtually
zero interest in it. And has been since about 1998. The
complainers want to use a captive audience - which is why slirc-mail is
moderated. We have #Townhall meetings for that.
Moderation: The general list is for the newsletter and critical net or
news information (major security issues, channel purges, things of
direct and compelling interest.) Remember, our subscribers will
unsubscribe if there are 3 or 4 posts to the list a MONTH.
Occasionally the administrator may let a funny go through if it's short
and to the point however, that's totally up to them, so don't be
surprised if your post doesn't make it. Also don't be surprised
if the administrator pulls the plug on a thread.
For all users: Mail list moderation decisions are treated like
channel bans. You can complain about them all you want to the
administrator. Even ask to be reconsidered. Do NOT beat up on the
administrator because your favorite post didn't make it - it is a very
difficult job and is bound to tick just about everybody off at one
point or another. Be thankful YOU don't have to deal with it and
AMENDMENT 6: Bots
This charter is hereby amended to include:
Bots are automated programs owned by users of the network that run
unattended at any time while connected to StarLink-IRC. Temporary bots
are those related to a client connection and which go away when the
user is offline. All other bots are considered permanent, must be
'homed' in a registered channel, and may only connect to specific
server(s) as permitted by the server admin. Bots must not interfere
with CStar, the network, or channel operations and must have the
channel owner's permission to be present. Bots shall only reside in
channels and may only be in five (5) channels at any given time.
StarLink-IRC reserves the right to unilaterally remove any bot for any
reason without recourse. Channel operators and owners may rescind
permission for bots to be present at any time, with or without notice
to the bot owner.
(CStar, Deathstar, and the scanners are not bots. They are
2007 StarLink-IRC.org All Rights Reserved.