Group Registration

freenode group registration is currently suspended, as the group registration process became significantly backlogged to the point that it was not viable to continue taking new registrations. This is an unfortunate side-effect of the combination of the following:

We apologise for the inconvenience and delay and ask that you have patience with us while we attempt to adjust to the exceptional growth and popularity the network has experienced as of late and the transition to being entirely volunteer-run.

This page describes group registration and the use of the freenode group contact. Group registration allows your project or organization to maintain unambiguous "real world" contact with the freenode network staff. Groups can be associated primary or "about" channels. In either case, group registration represents an official relationship with freenode.

Once you've gone over the material below, this form will allow you to set up your registration by submitting one or more group contacts. Group registration, contact list maintenance and requests for assistance are currently handled directly by network staff, but at some point these procedures will be replaced by a web-based system, which we hope will make the process much smoother, and allow more timely updates to your group configuration.

Group registration:

  1. Represents an official relationship between freenode and your project or organization. By registering your group, you're indicating that you are maintaining an official presence on the network. If your group is a legal entity, we want to make sure that management has approved your registration.

  2. Requires no special type or level of participation. You may maintain as little or as much control over your channels as desired. You may cloak your members, employees or participants, or not, as you decide. You may apply to sponsor a server if that's something you wish to do.

  3. Is accomplished by submitting one or more group contact form(s). Group contacts represent your project or organization to freenode staff. Forms may be submitted by the group contact or on behalf of that person ("proxy submittal") with his or her permission. They are verified by phone. The process takes about fifteen minutes.

    If the group contact has limited availability, he or she can provide scheduling information for the phone call in the 'Contact Notes' field of the form. There is currently an extensive backlog in form submittal; if we're unable to contact you at the scheduled time, we'll email you to ask for another time to schedule the call.

Two types of group contacts exist for freenode:

  1. The Primary contact. This contact registers to establish that your group intends to create a relationship with freenode. The primary contact should have the authority to make the determination that your group intends to register, with the specifics depending on the type of group:

    • Legal entities. A primary contact should belong to upper management or the organization's board. This authority can be delegated further in the case of larger organizations, but it's not recommended; in cases where such delegation occurs, contact with the organization is often lost and the group registration must subsequently be removed.

    • Informal, project-oriented groups. Informal groups vary considerably in their internal organization. If the group is run by a single project leader or developer, that person should submit a group registration form. If the group is run by two equal participants, each should submit a group registration form to make it clear that both wish to have the group registered. If it's run by a larger core group or by voting across the project, the voting group should make a collective decision to register and should appoint one of their number as primary contact.

  2. The secondary contact. Secondary (or approved) contacts are appointed by the primary contact. A secondary contact may be assigned limited access and/or privileges. They need no special level of authority; delegate whatever level of authority seems appropriate. We won't expect them to make policy decisions, just to find out the answers to any questions that are raised.

Group registration provides:

  1. Additional channel management capabilities. Network policy states that projects and organizations are entitled to own channels bearing their names. Your group contact can request changes in channel ownership in accordance with this policy and can directly request changes to access lists and configuration for any channels you own.

  2. Group hostname cloaks. Cloaks allow your project or organization to grant official recognition to project participants. Your group contact maintains this cloak list.

  3. Server maintenance. If you're sponsoring a freenode server, your group contact acts as technical liaison.

  4. Problem solving. When there's a problem with one of your channels or with a server you sponsor, a complaint by a user or a question about policy, we'll pass it on to your group contact.

Your group contacts:

  1. Are designated by your project or organization. For example, a group contact might be your IT manager or someone involved with your project infrastructure.

  2. Can be one person or several. You decide who acts as group contact. Each contact can be designated to handle issues pertaining to your entire group, or to a limited set of projects or users. You can designate primary and backup contacts if you wish.

  3. Acts as your "goto". When you need someone to talk to us about a network issue, your group contact is the person. They're your formal point of contact with our network staff.

  4. Acts as our "goto". We'll ask your group contact whenever we have any question about your project or organizational policies as they pertain to participation in the network.

freenode Group Advisory Board

In order for freenode to provide the best possible service to the communities we serve, it is important for us to get feedback from the projects with which we have relationships.

We invite all current (and future) Group Contacts to join GAB, the freenode Group Advisory Board. While we hope to see many Group Contacts involved with GAB in an advisory capacity, GAB membership is of course optional.

freenode will seek the opinions of GAB members on any issue relating to services given to groups/projects, any addition to, or change of, group specific policy and other relevant issues.

If you are a current Group Contact and wish to get involved with GAB, please contact staff on IRC or email groups at freenode dot net for instructions on how to subscribe to the freenode-groups mailing list and for an invite to the #freenode-gab channel.

Thanks in advance for any help you can provide!

Copyright © 2002 – 2016 by freenode Creative Commons License
Comments to email address: support at freenode dot net