Minutes for 2025-08-20. #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The process I use for this is generally described in the repo README.
I get a pointer to the raw log from IRC using "rrsagent, pointer". I use CURL to add this to a file named "irc.log" within a directory based on the timestamp (e.g., 2025-08-20/irc.log).
The I run the publish script, which does the rest.
(cd scribe-tool; ./publish.sh ../2025-08-20)Sometimes this requires iterating by making hand-edits to irc.log, moving entry points around, or adding things that are missing/incorrect.
If a new participant shows up, it might need a new entry in scribe-tool/people.json.
Then, once it shows up on https://minutes.json-ld.org, a link can be added at the end of the calendar invite (without sending update) so that they can be easily found in the future.