Many SIPB members use zephyr to communicate about projects, discuss what's new (or old) in the computing world, and generally keep in touch. Here's a list of some zephyr classes you might be interested in subscribing to.
Note: If you're new to zephyr or to any of these classes, you're encouraged to just listen to the class at first and get a feel for the class's typical modes of behavior. If you jump right in, you might risk accidentally offending someone.
<sipb,*,*> — The archetypal zephyr class for SIPB members and prospectives. Features general discussion about the SIPB, from brainstorming about projects to random bits of humor. It's considered polite to always use an instance when sending to -c sipb. High traffic.
<sipb-door,*,*> — Receives a zephyr whenever SIPB's office door opens or closes. Great way to keep track of whether the office is open or not.
<sipb-auto,*,*> — High traffic. Receives a variety of automatically generated zephyrs, including...
In general, you should only sub to these classes if and only if you're interested in helping with a specific project.
<hyades,*,*> — If you're interested in getting involved with Hyades, subscribe here to see Hyades development happens in real time. High traffic.
<scripts,*,*> — If you're interested in getting involved with Scripts, subscribe here to see what the Scripts team does behind the scenes. High traffic.
<barnowl,*,*> — Discussion of BarnOwl, a zephyr client written and maintained by SIPB members.
<debathena,*,*> — Discussion of Debathena, a project designed to bring the functionality of Athena to your Debian or Ubuntu system. Debathena is also the basis of the next official version of Athena. High traffic.
<dodona-discuss,*,*> — Discussing the development and coding of Dodona, a SIPB zephyrbot.
<clockworks,*,*> — Discussion of clockworks.
<mitex,*,*> — Discussion of the development of mitex. Note that this class receives a zephyr with each commit made.
These are not actually SIPB-related classes, although many people affiliated with SIPB and/or IS&T listen to them. You should not send zephyrs to any of these classes unless you have a good reason.
<consult,*,*> -
<filsrv,*,*> — Announcements of filesystem outages
<3down,*,*> — Recieves zephyrs about MIT service status (see also 3down website)