This issue is used to track the list of RocketChat channels and their settings.
name
description
Type
Default
Featured
#announcements
This is a read-only channel which is used by organizers to make conference-wide announcements. Only authorized users can post messages in this channel. Other users can only react with emoji to individual threads.
Read Only + Allow Reacting
Y
Y
#general
This channel is used to discuss general conference topics. The conversation can be about anything related to the conference. During the conference, this channel was used to promote their live sessions by authors, workshop organizers, social events organizers, etc.
Public
Y
Y
#helpdesk
This channel is used by all conference attendees to request tech support. We ask people to prefix their questions with a topic, e.g., [Zoom], [RocketChat], etc. On-call volunteers always start a thread when responding to a question. And continue the conversation in the thread. Once the question is resolved, they will mark it with :checkmark: emoji.
Public
Y
Y
#incidents
This channel is used to report incidents in the conference. Conference attendees can request the on-call volunteer in the channel to handle disruptions in RocketChat. They can simply click “Reply” button to start a private conversation with the on-call volunteer.
Broadcast
N
Y
#professional-conduct-committee
This channel is used to contact the Professional Conduct Committee if you need our assistance (e.g. related to a concern that might fall under the anti-harassment policy). PCC members will post a message in this channel to let people know which of them are available. Then the attendee can contact the PCC member via RocketChat private message (similar to the #incidents).
Broadcast
N
Y
#social-media-posts
This channel contains cross-posted social media posts published on various platforms by our official live tweeters and microbloggers, managed by our publicity chairs.
Read Only
N
Y
#sponsor-xxx
For each sponsor, we create a dedicated channel for them to post announcements and interact with conference attendees. These are “broadcast” channels (similar to #incidents, #professional-conduct-committee), i.e., only the channel owner can post messages. Visitors can only start a private conversation with the message author. This setting is due to the privacy concerns -- we do not want to expose who has visited a specific sponsor booth.
Broadcast
N
Y
#paper-xxx
For each paper, we create a channel where the author can interact with visitors to answer questions.
Public
N
N
#tutorial-xxx
For each tutorial, we create a channel where attendees can interact with the tutorial organizers.
Public
N
Y
#workshop-xxx
For each workshop, we create a channel where attendees can interact with the workshop organizers.
Public
N
Y
Plenary Sessions
name
description
Default
Featured
#live
This channel is only used for live plenary sessions. It was read-only for the majority of the time. During the live plenary sessions, we lift the read-only setting and people can use this channel for live QA. People have also used this channel to congratulate award winners, etc.
Mixed Mode (see the note below)
Y
Y
#keynote-xxx
For each keynote, we create a channel where attendees can interact with the keynote speaker.
Mixed Mode (see the note below)
Y
Y
#business-meeting
(only in ACL2020) This channel is used for discussions about the business meeting.
Public
N
Y
#review-meeting
(only in ACL2020) This channel is used for discussions about the review meeting.
Public
N
Y
NOTE: You will need to add/drop these channels depending on the plenary session schedule. For example, there is no review-meeting in EMNLP2020, but there is an industry panel.
Logistics about the #live and #keynote-xxx channels (TODO: This need to be updated for the hybrid conference)
For the #live channel, we set it "Read Only + Allow Reacting" outside the livestream hours, and we leave a message using the admin bot about the next events, e.g.,
Next Events (Nov. 16)
* 8-8:15am GMT: Opening Remark
* ....
This channel will open at 8am GMT on Nov. 16.
The admin bot should add a default react emoji (e.g., :acl-org or :tada) to engage the audience.
10min before the livestream starts
The RocketChat admin should turn-off the read-only flag and post a message in the channel using the admin bot, e.g., "this channel is now open."
Post a message in #announcement using the admin bot as well.
Before the live QA session, use the admin bot to tell people to use emoji to vote for questions. (This may change if we decide to use Dory.app to collect questions)
When the livestream ends, use the admin bot to post a message "This channel will become read-only in 10min."
After 10min, change the channel back to read-only and post a message about the event for the next day (see Step 1).
Socials / Recruiting
name
description
Type
Default
Featured
#introduction
This channel is used for attendees to introduce themselves and say hi to each other.
Public
Y
Y
#new-channels
This channel was used to announce new channels made by conference attendees. It turns out many people have created different channels during the conference, including some topic-based channels (eg., #bio-clinical-nlp), university-based channels (e.g., #uwnlp) to get to know different research groups, location-base channels (e.g., #singapore), etc.
Public
N
Y
#job-listing
This channel was used to post job opportunities. We only get 10 posts in this channel throughout the conference though.
Public
N
Y
Registration Desks
name
description
Default
Featured
#sponsor-registration-desk
This channel is used as the virtual registration desk for sponsors. We need this channel because we need to set the sponsor account as the owner of their channels, and we didn’t develop an automatic way to do this. Since there are only ~20 sponsors, we just ask them to post a message in this channel when they arrive, and we just manually add them to the #sponsor-xxx channel and set them as the owner. After we add the sponsor account to their channel, we post a message “@username Welcome! I have set you as the owner of the channel. You can delete this message with your owner’s permission” so that they can familiarize themselves with the RocketChat usage.
Public
N
Y
#organizers-registration-desk
Similar to #sponsor-registration-desk, this channel is dedicated to organizers who need to be the owner of specific channels.
Public
N
Y
#oncall-volunteers
This channel is dedicated to on-call volunteers for them to coordinate with each other during the conference. On-call volunteers should join the channel by themselves. We didn't make this channel private so the volunteer chair doesn't need to add the volunteers manually. On-call volunteers can create private group discussions by themselves.
This issue is used to track the list of RocketChat channels and their settings.
Plenary Sessions
Logistics about the #live and #keynote-xxx channels (TODO: This need to be updated for the hybrid conference)
The admin bot should add a default react emoji (e.g., :acl-org or :tada) to engage the audience.
Socials / Recruiting
Registration Desks