Just moving old stuff around, and figured The Community is the best place to put the flodd.net website, rather than having a whole domain for it (at the time). Note: Admins/Mods: Don't edit this any more, its archive type stuff. --Dave.
Project Flodd.net: Index Project Flodd.net Revision History. (Tue Sep 21, 2004, 12:13am) 580Bytes 1) Policy and Procecture. (Sun Sep 12, 2004, 6:21pm) 1.4Kb 2) Objectives. (Mon Sep 6, 2004, 12:43am) 158Bytes 3) Governing. (Sun Sep 12, 2004, 6:27pm) 4.6Kb 4) Voting Process. (Sun Sep 5, 2004, 7:58pm) 188Bytes 5) Power Definitions. (Tue Sep 21, 2004, 12:13am) 1.5Kb 6) Controlling Interests. (Mon Sep 20, 2004, 11:58pm) 2.3Kb 7) Acceptable Use Policy (AUP). (Sun Sep 5, 2004, 9:12pm) 1.8Kb 8) Link Procedure. (Sun Sep 5, 2004, 9:16pm) 3.8Kb 9) Resource Link Application (RLA). (Sun Sep 5, 2004, 8:45pm) 1.8Kb Other Stuff: - Interm Staff List - All of the above documentation in a single page Project Size: 18.1Kb, last modified: Tue Sep 21, 2004 12:13am ET. 1023 visits since Sun., Sept 5, 2004. (As of Jun 16, 2006 11pm ET)
Revision History. 2004-09-05: Dave: Split everything from the old document up into various sections to allow mutiple people to work on it at the same time. 2004-09-05: cyde: added the interim staff list, and base for AUP. 2004-09-05: Dave: Spiffed up mainpage to include filesizes, and last mod dates. 2004-09-05: Dave: Added Resource Link Application, modded AUP. 2004-09-06: Dave: Modded Governing. 2004-09-08: cyde: Modded Governing. 2004-09-20: cyde: Modded Controlling Interests 2004-09-20: cyde: Modded Interim Staff List 2004-09-20: cyde: Modded Power Definitions
1) Policy and Procecture. Nickname and Channel Registration policies: Nicknames and channels may be registered on a first-come-first serve basis. Nicknames, and registered channels are issued under the discression of RawIRC Network Staff. The network's staff reserves the right to revoke registered nicknames, and channels at any time for any reason. Nicknames not identified for over 45 days are subject to expiration. Channels not occupied for over 45 days are subject to expiration. Channels that have moved to other networks, and are advertising other chat networks in the topic are required to set +s. Server Staffing Policys Server administartors are responsable staffing their own servers with a reasonable number of staff. Staff are highly encouraged to volunteer to participate in one of the major network sub-groups, but it is not required. Requirements for adding a new oper: Server administrators are required to submit a notifcation to the admins list one week in advance to providing any access whatsoever. New Opers are to be initally added with local server operator privs for the first 30 days. New Operators that have been newly opered for less than 60 days are not subject to obtaining Services Operator (SO) access. After 60 days, the oper' sponsoring admin may apply to the Services and Anti-Spam Board (SS) to obtain access to Services Operator (SO) functions.
2) Objectives. Project Flodd.net. (C) 2004 PureVanity.net, All Rights Reserved. Objective: - To provide a stable and friendly chatting enviroment to our (humble) gathering of users.
3) Governing. Project Flodd.net: 3) Governing. Last modded: 04/09/05 - Dave. (C) 2004, PureVanity.net. All Rights Reserved. GA -> Admins/AAs -> Opers Boards and Teams: Boards and Teams will, with the exception of the GA, operate outside the standard network heirarchy as independant organizations responsible for the duties detailed below. ---------------------------------------------------------------------------------------------------------------- PostMaster (PM) *cyde (PostMaster) Duties and Responsibilities include: Responsible for maintaining the Mailing Lists, and email aliases. Uphold Network Policy and Procedures for DNS. ---------------------------------------------------------------------------------------------------------------- HostMaster (HM) *Dave (HostMaster) Duties and Responsibilities include: Responsible for maintaining DNS services, including pooling. Responsible for maintaining a group of secondary DNS services. Uphold Network Policy and Procedures for DNS services. Maintaining Network's NOC portal. Verifying that all linked resources comply with linking policy. Verifying security percautions of linked resources at versious times. Responsable for performing a security audit on new Resource Link Applications (RLA). ---------------------------------------------------------------------------------------------------------------- Governing Admin(s) (GA) *Dave (Interim GA) Duties and Responsibilities include: Enforcing Network Policy and Procedure from an administrative standpoint. Overseeing operation, and management of Postmaster, Hostmaster, Services, and User Relations teams. Responsible for keeping the network focused on achieving it's objectives. Solving issues with internal management. Solving staffing issues, and quibbles. ---------------------------------------------------------------------------------------------------------------- User Relations (UR) *cyde (User Relations Director) *Siana *xachen (webmaster) *vampibella (staff forums) Duties and Responsibilities include: Providing a communications link between the network and it's users, allowing users concerns to be raised at appropriate levels. Administrating the network's official user forum. (cyde) Moderating the network's official user forum. Administrating the network's official staff forum. (vampibella) Creating and maintaining the network webpage and oper portal. (xachen) Maintaining and staffing the network's official help channel, #Help. Maintaining and staffing the network's official abuse channel, #Abuse. Maintaining and staffing the network's official 'Lobby' channel, #RawIRC. Providing assistance in moving groups of users from other networks, presenting a migration plan, not spamming. Communicating with ISPs and other end-providers of abusive, and infected users. Defined Roles: Webmaster. - Manages and updates the primary website. Forum Admin. - Manages the staff, and user forums. UR GC. - Oversees management of UR group. Liaison ---------------------------------------------------------------------------------------------------------------- Services and anti-Spam (SS) *derfy (Services/Anti-Spam Director) Duties and Responsibilities include: Maintaining network Services daemons, functions and portals. Testing new services software versions on our Test Network (TN). Patching and Upgrading services software when appropiate in a timely matter. Taking regular backups, and testing recovery plan. Keeping spam and other commercial jibba-jabba a non-issue. Maintaining Network's Blacklist services. ---------------------------------------------------------------------------------------------------------------- The five sub-groups operate as follows: Each group will have an elected Group Chairperson (GC) to oversee the primary function of the sub-group. The Group Chairperson (GC) may appoint network staff to take various roles within the groups. The GC must be subscribed to the admins list, and should be considered an admin, with exception to voting rights regardless of their role on their sponsoring server. Each GC is responsible for appointing his own staff in a manner timely to his appointment as group GC. Each GC is responsible for insuring goals and deadlines are met for projects submitted to their sub-group by the network's staff. Each GC is responsible for creating guidelines for his or her staff and making sure that each member of their staff is aware of them and adheres to them.
4) Voting Process. - Voting The following is how the votes will be counted *admin vote: Founding partners, server admins (or their AAs as needed) *oper vote: Founding partners, admins, AAs, Opers
5) Power Definitions. Distribution of Powah: Servers are required to be staffed with no more than one Admin, and one Assistant Admin. Server admins are responsible for staffing their servers with an appropriate amount of responsible candidates. The Services Superuser(s) are responsible for the maintenance of the services access list and the appointment of SAs Services Admins (SAs) are responsible for sorting out nick/chanserv problems for users as the need arises and for the (approved) appointment of SOs New Operator candidates must meet the following qualifications: Have a nickname registered with the network for at minimum one month. Be registered on the network's general public mailing list. Sponsoring admin must submit a request for feedback (RF) to the admins mailing list. An RF will not determine if the operator candidate will be approved, its merely provided as a channel to raise any serious issues with the sponsoring admin, and the network's staff. The sponsoring Admin must wait a minimum of one week after an RF has been submitted before a new operator can be given any access whatsoever. (proposed) A minimum one month trial period must be passed before a local oper (LO) is given global oper (GO) status Server Admins are responsible for providing a reliable, stable, and predictable platform for network servers and services to operate from. A server admin must be willing to delink their server if it causes a detriment to the network's wellbeing
6) Controlling Interests. Controlling Interests (in descending order) Pre-Model Phase (nearing completion!) *Founding partners (Dave, cyde, derfy) The role of this partnership is to, with input from parties wishing to contribute, create a model upon which the network will be based. Until all the details of the model are hammered out, this partnership will dictate temporary policy and assign delegates to work on specific projects. Aforementioned policy will be outlined in the following sections of this project. The Controlling Interests Partnership (CIP) was established to define the overall network's goal, establish a list of policies and opering procedures, and establish a willing group of volunteers to participate in the project. The CIP's ultimate goal is to create a structure that will work to establish a stable, and friendly chatting enviroment that is not subject to dramatic changes in organization, or shifts in operating policy. Chat channels, and nicknames can almost be considered property on today's growing networks. Users are looking for a chat network to plant roots in, a place to establish a channel, or meeting place for friends. Our vision is to create a chat network for all purposes, and all for all types of users to call home. We want to establish a network that people would be willing to participate in, be it as a user, or as an operator, or as a server administrator, and be able to work towords a common set of goals that we can all benifit from. The CIP welcomes any and all comments from our users, and interm staff regarding these policys. Post-Model Phase *Founding partners (Dave, cyde, derfy) *Server Administrators (vampibella, xachen) *Assistant Admins (byrnsy) *IRC Operators (Psionic, Siana, dancefighter, Don, feek) *Our users Once the model is completed, controlling interests in the network at large, as well as the further creation, implementation and upholding of policy will fall completely to the founding partners and server admins. From there, authority will be delegated to the AAs and Opers respectively. We hope that in doing so, we will be able to create a stable, drama-free environment for all of our users to enjoy.
7) Acceptable Use Policy (AUP). The RawIRC Chat Network - Acceptable Use Policy Your privilege to remain connected to RawIRC is stringent upon your behavior in accordance with this AUP, as well as the rules of the individual server that you are connected to. RawIRC is a completely FREE and unmoderated service that acts as an intermediary between users. We are therefore not responsible for the actions and words of said users. While we do not condone illegal or immoral activity of any kind, we also know that the ramifications of policing our network is a concept that is simply too overwhelming and locale-specific to be feasible for anyone aside from qualified law enforcement agencies. We therefore encourage you to act in accordance with the laws in your region, as well as the Terms of Service of your ISP. Specific limitations may be enforced by servers linked to this chat service that go beyond items covered in this AUP. Please refer to /motd on the server you are connected to in regards to its AUP. All servers connected to this network enforce the following policies: Connections from insecure locations are subject to removal from the network. In order for us to verify that your location is not insecure, various checks are performed when you connect to our service. Your system is probed for common insecurities, torgans, and viruses. By connecting to the RawIRC Chat Network, or one of it's servers, you agree to allowing us to perform these probes. Connections from locations our blacklist services deems as insecure, or abusive are subject to removal from the network. Users that act in an abusive way to network staff, or other users are subject to removal. Connections sending excessive amounts of data (flodding) to our chat servers are subject to removal from the network.
8) Link Procedure. Linking Resources to RawIRC will be completed in the following mannor: A Resource Link Application (RLA) needs to be completed by proposed site administration, and submitted to network staff. The Resource Link Application (RLA) is passed to the Admins Discussion list, for general discussion. If the RLA meets the minimum requirements for the network service being proposed, the application will be stripped of any sensative information, and passed to the opers list, and general network information located on the network's website. The voting members of the Admins group will now have 12 days to submit a vote, the type of vote depending on the type of application. ** _ see below. After the test period has been completed, the admins will have one week to submit a vote to either permanetly link the resource, to extend the test period, or delink the resource. During this period, the resource will remain in the testlink status. ** For Client Servers: 30 Days Testlink period. For Secondary DNS Servers: 20 Day Non-Listed period. For Services-related Locations: 20 Day testconnect period. Minimum requirements for Primary DNS location: DNS server daemon must be stable, and secure. bind-8.x or bind-9.x is recommended. Must have a dedicated IP address, with only the dns daemon listening publicly to incoming connections. DNS server daemon must only be servicing authoritative network-related zones. DNS server daemon must not be configured to provide non-authoritative responses. DNS server daemon must be operating on a secure, up-to-date UNIX platform. Minimum requirements for Secondary DNS location: DNS server daemon must be stable, and secure. bind-8.x or bind-9.x is recommended. DNS server daemon must not provide public non-authoritative responses. DNS server must correctly draw zones from the primary within 5 minutes of receiving a notify from the master. Secondary servers not quickly updating are grounds for removal. DNS server must not provide zones transfers, or access to, any network zone, for any reason whatsoever. Minimum requirements for Services hosting location: Services location must be top secret. Generally, only the SS GC (and its appointed staff), and the GA are aware of services' location, or address. Any publicly known location (IE: donating admin is known to host at company X) adds security, and stability risks. Platform stability and performance is one of the most important aspects. The hosting server must be able to provide large amounts of CPU, and ram, at needed times without notice. A dedicated box is not required, however, is highly recommended. The hosting platform must be operating on a secure, stable UNIX-like platform, preferably FreeBSD. Limited access by non-involved parties. Access to the server hosting services must be tightly controlled. The network's staff must maintain a list of all parties with remote-access, or local-access to the hosting server. Bandwidth for regular offsite services database backups must be available. Minimum requirements for Client Servers: 500HMz Intel, AMD, or compareable equillivant. 128MB RAM min, for dedicated server, more if not. Multi-Homed, multi-T1 for most North American locations. Other regions vary. Applications from Cable, DSL, Dialup, ISDN, or any other end-user type connections will not be considered for application (however, they may be considered as objects of humor). Servers dedicated to Dedicated servers are highly prefered. TCP Wrappers, or firewalling must protect any ssh, or remote management interfaces. Resolvers must not repond to non-local unauthoratative queries.
9) Resource Link Application (RLA). Resource Qualifications: IRC Server Application: Client Server: Multi-Homed. tcpwrappers and/or firewall. 500 clients minimum. no shell servers. 500mhz or faster with 128+mb of ram. Hub Server: Milti-Homed. non-disclosed, or publicly unknown location. tcpwrappers. no shell servers. Proposed Admin: Name: Email Address: Phone Number: RawIRC Nickname: Server Owner: Name: Email Address: Phone Number: RawIRC Nickname: Server Info: Proposed Server Name: Proposed Server IP: FDs compiled into kernel: FSs allociated to IRCd: If linking as a client server, how many users will you be holding at max (500min): Physical Hardware: Please describe the server hardware (IE; O/S, RAM, proc & speed) Please provide a full ps aux listing: Please list all resolvers listed in /etc/resolvers.conf, and their world-accessable IP addresses: Please describe your hardware's primary function: Have you participated in any other IRC networks, either as an operator, or server admin (established networks only please): If your server were to be a detriment to the network, would you be willing to remove it? Please list any proposed staff, and their IRC nicknames. Please provide a description of you peering and transit, we will verify your claims: Please provide traceroutes to the following addresses: dione.purevanity.net - 66.38.200.89 Please provide an extended ping session of, at minimum, 300 packets, 1 second delay, to the following addresses at the following times of day: Times are in EDT, please provide output from one week day, and one weekend day. 11AM 6PM 10PM dione.purevanity.net - 66.38.200.89
