For Developers‎ > ‎

Slack

For discussions around Chromium development, we have a Slack instance at chromium.slack.com.

Account

To join Chromium's Slack, the organization or person needs to be listed in Chromium's AUTHOR file. If you have ever contributed a change or belong to one of the active contributor organizations you will be there.

Anyone with a @chromium.org address can join directly. Others will have to follow an invite link that you get by mailing a request to chromium-slack-invites (at) chromium.org.

Furthermore, if you are part of a project that is significantly related to Chromium and that is significantly owned or maintained by Chromium AUTHORS, you can also have access without being in the Chromium AUTHORS file. The list of accepted projects are current:
  • Angle
  • Skia
  • V8
  • WebRTC

Channel examples:

  • #halp - project related questions about anything
  • #misc - anything
  • #slack-help - the one mandatory channel
  • #sheriffing - what is going on? Is anyone on it?
  • #mojo - you're also confused? Join and ask/learn
  • #jumbo - about the awesome unity build system
  • #cxx - a place to rant about discuss C++

Any Slack member can create channels when they need one. There are many.

Tips and tricks

There are many pages listing Tips and Tricks for Slack. These are a couple selected to make the transition from earlier systems smoother.

Read like IRC?

Enable "All unread" in settings and read all channels amalgamated.

Quieter slack

  • Mute channels by clicking on the channel name. A muted channel will still notify you if someone triggers an alert by using your name

Favourite features compared to IRC

Remind me

/remind me in 20 minutes to eat lunch
/remind #release at 11:45 May 20, 2020 Release Chromium 80
Right click a post and select "remind me in ..." to get reminded about that post later

Add your custom emoji

Anyone can upload an image and use as an emoji. There are already dozens or hundreds.

Official information

Official information needs to go on public mailing lists and in public bugs. Don't believe you've informed everyone because you've said something in a Slack channel.

Security

Company proprietary information must not go on Slack. Use company internal channels for that.


Comments