-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathREADME.txt
More file actions
34 lines (26 loc) · 1.31 KB
/
Copy pathREADME.txt
File metadata and controls
34 lines (26 loc) · 1.31 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
Put the Slack export here. Nothing in this directory is committed except this
file -- the export is several hundred megabytes and is kept separately.
Expected layout:
source/
└── slack/
├── users.json
├── selenium/
│ ├── 2015-09-08.json
│ └── ...
└── selenium-tlc/
├── 2018-07-01.json
└── ...
A Slack export arrives as a zip with one directory per channel and a pile of
day files inside each. Copy over the "selenium" and "selenium-tlc" directories
as they are, plus users.json from the top level of the export.
users.json is required -- it maps user IDs to the display names that appear in
the logs. Without it every message is attributed to something like U4C5DHACT.
Everything else in the export (channels.json, integration_logs.json, canvases,
other channels) is unused and can be left out.
Then, from the repository root:
python3 scripts/build_slack.py
The older IRC logs under selenium/ are not generated from anything here. They
sit in a few shapes depending on where they came from -- flat .log files in
2011, plain month directories through 2015-08, and -irc suffixed months where
an IRC and a Slack record cover the same period. All are checked in as-is.
See the README for that history.