I'm working on the Slack migration from HipChat.
-
Sometime in the next several weeks, you'll be receiving an invite to join lsstc.slack.com
-
You've been identified as the original creator of a HipChat room.
-
Slack's channel name restrictions are different than HipChat; you are limited to 21 lower alphanumeric characters and '-' (or
[a-z0-9-]*). We have also identified a set of prefixes for organization (below). I've made a best-guess suggestion on an appropriate name for the channel that will replace your room given these restrictions, utilizing our identified prefixes. Channels can be renamed at any time in the future. -
Once you receive the invite to Slack, you can create the channel yourself, you can opt to not have the channel created at all, or you can let me create it for you. For channels that I create for you, I will preserve the HipChat topic in the new Slack channel, and Slack will also show me (brianv0) as the creator of that room.
- Please message me your preferences for each room. If no message is received, I will autogenerate the room.
- If you think your room should be private at some point in the future, it's best if you create it.
- For convenience, you can comment below, assuming you have a GitHub account. Otherwise you can message me directly on HipChat.
-
We don't have time scheduled for a full migration of all HipChat message history, as that would be a very manually intensive process. We will work on a system of backing up HipChat for historical records, but the plan for now is to generate new rooms. We will be paying for Slack, and we will have unlimited history going forward.
-
The users of this Slack team (to be lsstc.slack.com) include all of the LSST project, and all Science Collaborations.
-
All DM members are highly urged to use their GitHub ids as their user id because it will simplify integration with automated developer support systems.
-
Science Collaborations will have their own prefixes.
- e.g.
desc-> DESC,desc-wl-> DESC Weak Lensing, etc...
- e.g.
-
Channels may be created by anyone, preferably within the prefixes given below; unused channels may be archived after some time. Archived channels can be un-archived at any time by any team member.
-
We've identified a few natural prefixes for most rooms:
se-> Systems Engineeringcam-> Cameradm-> Data Managementsims-> LSST Simulationsepo-> EPOts-> Telescope and Sitemtg-> Meetings (i.e. AHM, JTM, LSST@Europe, etc...)lsst-> LSST project (if none of the above apply)
For convenience, there will be channels for some institutions and projects; these may also be used as prefixes. These are below:
tucsonuwprincetonslacipacncsabnl
cfhtsubarusdssdecam
bookclub
We realize we are probably missing things, but we hope this framework is good enough that people can self-organize Slack channels in the future, and we think this should cover the majority of use cases in how we currently use HipChat in the project and DM. This is an imprefect process, and I'm tryin to automate as much as possible, but there will be gaps. Please bear with me on this! The important thing to note is that it's all easily fixable!
When a user is searching for a channel, they will be presented the channel name and a description of the channel. If they are still unsure if they want to go into that channel, they can click on it and get a preview before actually joining. Otherwise, the user is already in that channel and they'll probably know what it's for in any case.
That will be perfectly possible, though most DM and project channels should be public. It's a one-way street though, so it's better to keep it public unless you really need it to be private.
Sorry, you can't make a private room public. We can rename the room, archive it, and recreate a new room under the original name, but you won't have the history available to everyone.
Your best-guess name sucks. When I get my invite to Slack, I'm going to create the channel in Slack under a different name.
Comment here or send me an email and I'll fix it. This list should still be updated so people can know where their channel went.
Slack has some truely great documentation. You can usually use Google and the first results will be a Slack help page, or you can directly browse their help center here: https://get.slack.help/hc/en-us.
Lines missing in migrating_rooms.txt means that we haven't either defined a new name for these rooms and/or it's unclear if those rooms need to be migrated.