Skip to content

Latest commit

 

History

History
95 lines (67 loc) · 4.39 KB

chat.adoc

File metadata and controls

95 lines (67 loc) · 4.39 KB
Raw
layout title
simplepage
Chat

The Jenkins project meets to discuss various topics on Gitter and IRC. In addition to the general purpose rooms and channels listed below, special interest groups and sub-projects have their own spaces, and you will see chat rooms linked from their pages.

Gitter

The Jenkins community discusses various topics in multiple rooms on Gitter. Various special interest groups also use Gitter to meet, and you will find their rooms linked on the SIGs overview page.

jenkinsci/jenkins

General discussions about Jenkins.

Internet Relay Chat (IRC)

The Jenkins community discusses various project-related topics in multiple channels on the Freenode IRC network.

For information on how to connect, see the Freenode website.

Note

Because of irregular spam attacks, we sometimes have to make some channels protected. In such circumstances, we make the targetted channel(s) only accessible to registered IRC nicks. Example error:

[10:28] -NickServ- my_nickname is not a registered nickname.
[10:28] == #jenkins Cannot join channel (+r) - you need to be identified with services

That means you basically need to create a reserved nick for you, following the official documentation. Once done, you will be able to connect to #jenkins even if that channel is undergoing a spam attack. Note that even without this, this is a recommended practice so that people know this is you, and cannot be someone else, when a given nick is online.

#jenkins

This is the primary channel for discussions about Jenkins. If you have questions about Jenkins, you’ll probably want to ask them here.

Note
 if you have a question about Jenkins, just ask it — don’t ask whether you can ask a question. It’s common to not receive an answer for quite a while if no active contributors are currently checking IRC. In that case, just stick around, and periodically (every few hours) ask your question again.

Conversations in this channel are automatically archived to both echelog and botbot.me.

We use the jenkins-admin bot to automate common administrative operations. Its use is limited to users with voice or op in this channel. Learn more.

Board members and officers typically have op (@) in this channel. Established contributors typically have voice (+) in this channel.

#jenkins-meeting

We conduct bi-weekly project meetings in this channel. These meetings are open to everyone. Learn more about the project governance meeting.

Meetings are logged, and the channel is unused the rest of the time. We use the robobutler to run these meetings. See the about project meetings for more details.

#jenkins-community

The channel to help organize events, documentation and more "meta conversations" around the Jenkins project. We don’t discuss Jenkins — the software — here. You can find conversation logs on botbot.me.

#jenkins-infra

Discussions of the Jenkins project infrastructure, i.e. most services running on jenkins.io, jenkins-ci.org, and related domains.

Cloaks

#jenkins is not only a registered channel, but the Jenkins project has an official relationship with Freenode (see the Freenode site for more details). Because of this, we can provide IRC cloaks for developers. IRC cloaks are used to protect the privacy of developers. Cloaking is also a common way for projects with an IRC presence to designate status for contributors and developers. We currently offer the following cloak levels:

  • jenkins/developer/(username)

To obtain a cloak:

  • ensure you have a registered user on Freenode

  • ensure you are already recognized as a developer (have +vV voice privilege)

  • email [email protected] with those details

  • monitor your memoserv notices for updates from Freenode staff requesting confirmation of cloak request

    • /msg memoserv help