Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
TD-StorageBay_introduction
TD-StorageBay_introduction
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • TD-StorageBay_introductionTD-StorageBay_introduction
  • Wiki
  • Using IRC

Last edited by Jackson Nov 12, 2018
Page history

Using IRC

TD-StorageBay Integrated IRC

TD-StorageBay contains an integrated IRC server, reachable at irc.tdstoragebay.com, port 6667 for normal IRC or port 6697 for secure IRC using SSL/TLS.

Official channels

Any user is free to create their own channel(s), the IRC server was set up to allow team members on a project easy collaboration and a place to discuss ideas. But, there are a few official channels that cannot be deleted and exist for special purposes. Those channels are:

#help

Help channel for all of TD-StorageBay. What features are offered, how to get your preferred SCM to connect, requests for email addresses, etc.

#gitlab

GitLab on TD-StorageBay has an active Irker IRC relay, this channel is where it points to by default. If you enable it for your project, you might want to add a custom (private) channel for your work. The gitlab channel is not to be used for permanent work, only as a designated default. If your project is sending messages here, please change it.

#gitlab-help

Help channel specific to GitLab.

#opers

Private channel for all IRCOps.

#secops

Like #opers, but also +z, meaning that all users, require +z (secure connection) to be able to join.

Official channels are moderated through various tools, such as bad word filtering, spam filtering, and the like. Admins are required to give only one warning before issuing a kill or k-line.

IRCOps (admins)

The list of IRCOps/admins/moderators is found on the list of TD-StorageBay administrators.

Connecting

TD-StorageBay uses UnrealIRCd for IRC, and therefore most IRC clients can connect. You will receive modes +xw on joining, meaning that your host name will be hidden (+x, "cloaked"), and you are allowed to listen to WALLOPS messages (+w). If you want to be hidden from the list of users on the server, you can set mode +i (invisible) on yourself.

If you decide to join the IRC server, please set your username to your gen account, GitLab account, or email if nothing else. This way, regardless of your desired nick, an IRCOp is still able to recognize you. Nicks are allowed to be free-form, yet nicks impersonating IRCOps, channel services, or containing vulgar/inappropriate/abusive words/phrases are not permitted. You will be asked to change it once if this happens, and then you will be issued a kill. The GECOS ("Real name") field is also free-form, and a convenient place to keep your email or other quick contact information if your username is something else.

You are allowed to join the IRC if you do not have any accounts tied to TD-StorageBay, but remember that it was initially added for account holders to discuss and collaborate with team members.

Disciplinary guidelines

The rules for disciplinary measures are being laid out here for everyone to view, such that everyone is (hopefully) on the same page about what is and is not allowed.

Rules

  • Be respectful. We are a community of rational developers, not little kids. Be respectful of and towards others, and the admins.
  • Keep on topic in the official channels. They each have a specific purpose, and that's listed not only here but in the channel topic.
  • Listen to the admins. If we tell you to do something, please do it. We just want to keep the IRC server a nice and stable place for the exchange of ideas. If you think one is out of line, look at the list of admins, find their superior, and politely bring the issue to their attention.
  • Respond to an admin when they address you. If you are asked privately by an admin for something, do not ignore them. Doing so will lead to a kill, and a temporary k-line for repeated offenses.
  • No spam, advertising, or using the IRC server as your soapbox. This rule should be pretty self-explanatory. Nobody wants that here.

Admin behavior

  • First and foremost: The owner's decisions are final. I, @root, am at the top of the admin hierarchy. Anything I say or any decision I make is final, unless I myself go back later.
  • An admin is required to give one warning or ask once before enacting actions. Some may even be nice and give you more. But they are only required to once.
  • Actions get worse the more offenses you have. Admins do have a record of offenses by individuals, and are capable of bypassing +x modes on users. Break the rules too many times and you will be left permanently banned from the IRC server, and potentially have the rest of your accounts wiped too if the situation was serious enough, though that should only happen very rarely, if at all. This also applied to breaking the same rule repeatedly.
  • Avoiding actions can be met with instant termination, no warnings. If you're switching IP addresses, changing names, or in general trying to avoid a disciplinary action that was handed down to you, it will be found out sooner or later, and an admin that notices this is allowed to permanently remove you from the server with no warning. You know what you're doing already, we don't have to tell you.
  • Admins will investigate before making a decision. Just because something looks suspicious doesn't always mean that it is. Especially in the cases of permanent removal, admins should always be 100% sure that they have the full trust before making a decision.
  • Any admins caught holding bias, playing favorites, or willingly refusing to consider all the facts in an incident can and will be stripped of their power. We all make mistakes. But a mistake is an accident. Failing repeatedly to do your job or do it fairly can result in loss of rank, or temporary or removal of admin status by either a superior or the site owner.
  • Except for clear and obvious cases of ban avoidance, admins are required to consult the owner for permanent removal, and only the owner can authorize the permanent removal of someone from the IRC server.
Clone repository
  • Git for TDSB
  • Old
    • getting started
    • setting up git
    • using cvs
    • using subversion
  • TDSB structure
  • The Keyserver
  • The package server
  • Using IRC
  • global todo
  • guide to changelogs
  • Home
  • using mattermost
  • using the runners