Skip to content

Commit

Permalink
Update publish_minutes.md
Browse files Browse the repository at this point in the history
Updated the screenshot, removed zoom option, and cleaned up formatting
  • Loading branch information
kimdhamilton committed Jun 25, 2021
1 parent 33b2ab4 commit b5ad8ce
Showing 1 changed file with 40 additions and 14 deletions.
54 changes: 40 additions & 14 deletions publish_minutes.md
@@ -1,41 +1,67 @@
# Generate CCG Minutes

## Step 1: Fetch and clean up the log file
## Step 1: Create the date directory

Create the date directory inside the `meetings` repo:
- If adding minutes for the main CCG meeting, create a directory named `yyyy-mm-dd` (eg. `2020-12-01`)
- If adding minutes for a task force, add a suitable suffix to the directory name, eg `2020-12-01-vc-education`

## Step 2: Fetch and clean up the log file

Go to the [scribe tool](https://w3c-ccg.github.io/meetings/scribe-tool/) and enter the date of the meeting (see screenshot)

<img src="assets/img/date_chooser.png" alt="date chooser" width="200"/>
<img src="assets/img/scribe_tool.png" alt="date chooser" width="200"/>

Check the following:
- Ensure there's a link to the agenda ("Agenda: ...")
- Ensure the topics are labeled ("Topic: ...")
- Ensure the scribe is identified ("Scribe: ...")
- Look for any find/replace suggestions in irc.log and update them ("s/../..")
- Ensure aliases have matches (see [people.json file](https://github.com/w3c-ccg/meetings/blob/gh-pages/scribe-tool/people.json))
- Download the IRC log by selecting and copying (you can use the copy button in the interface) the IRC log text, and pasting into a new file on your computer using any text editor (eg. Notepad, TextEdit, Sublime Text) and save it with the filename `irc.log`.
- Download the IRC log by doing the following:
- Select and copy (you can use the copy button in the interface) the IRC log text
- Paste into a new file on your computer using any text editor (eg. Notepad, TextEdit, Sublime Text)
- Save it with the filename `irc.log` in the directory created above

## Step 3: Fetch and clean audio

- Open the audio file in your browser by going to `https://meet.w3c-ccg.org/archives/w3c-ccg-{MEETING NAME}-{DATE}.ogg` and File > Save (ctrl+s or cmd+s). Name the file `audio.ogg`, and save it in the date directory you just created.
- for a regular CCG meeting, in the URL {MEETING NAME} will be `weekly`. Otherwise, use the task force name, eg. `education`.
-

Option 1: Use the "download audio" button (see above screenshot) and save in the directory created above

## Step 2: Fetch and clean audio (TODO)
Option 2: Command line: use the `download-raw-minutes` tool in the `w3c-ccg/meetings` repository

### Step 2a: if you used Jitsi
- You can use the `download-raw-minutes` tool in the `w3c-ccg/meetings` repository.
- For example, to download the audio for 2020-09-29 weekly meeting into `2020-09-29`:
`./download-raw-minutes -a 2020-09-29`
- For example, to download the audio for 2020-11-02 education meeting into `2020-11-02-vc-education`:
`./download-raw-minutes -a -m education 2020-11-02`
```
# To download the audio for 2020-09-29 weekly meeting into 2020-09-29
./download-raw-minutes -a 2020-09-29
# To download the audio for 2020-11-02 education meeting into 2020-11-02-vc-education
./download-raw-minutes -a -m vc-education 2020-11-02
```

The `audio.ogg` file will be placed into the correct directory automatically.

### Step 2b: if you used Zoom

- Download the .m4a file from Zoom.
- Convert the .m4a file to a .ogg file. You'll commit this is step 3 as audio.ogg. You can use an online tool like [this one](https://convertio.co/m4a-ogg/).
## Step 4: Create the group file

Create a text file in the created directory with the filename `group.txt`. The contents of this file tell the email-sending script what to put in the subject line when the minutes go out.

- For the regular weekly CCG call, it should say simply `Credentials CG`.
- For task force calls use the appropriate name, eg. `CCG Verifiable Credentials for Education Task Force`.

The automatic email sending won't happen without this.


## Step 3: Commit the files
## Step 5: Commit the files

- Ensure the log and audio files are placed into the github `meetings` repo as follows:
- group: https://github.com/w3c-ccg/meetings/yyyy-mm-dd/group.txt
- log: https://github.com/w3c-ccg/meetings/yyyy-mm-dd/irc.log
- audio: https://github.com/w3c-ccg/meetings/yyyy-mm-dd/audio.ogg
- Example:
- group: https://github.com/w3c-ccg/meetings/2020-11-17/group.txt
- log: https://github.com/w3c-ccg/meetings/2020-11-17/irc.log
- audio: https://github.com/w3c-ccg/meetings/2020-11-17/audio.ogg
- On commit, the rest is handled for you; a github action will generate html and publish
Expand Down

0 comments on commit b5ad8ce

Please sign in to comment.