meeting_base_<shortname> file is the primary configuration source for a meeting group. It uses dotenv format and is parsed by the dotenv library’s parse() function inside readMeetingConfig() in src/meeting.mjs. The resulting key-value pairs drive how meeting issues are titled, where they are posted, which agenda items are included, and how participants join.
File naming
templates/meeting_base_tsc
Format
The file uses standard dotenv syntax:KEY="value" pairs, one per line. Values that span multiple lines must be wrapped in double quotes.
Properties
The exact name of calendar events that identify this group’s meeting slots. The CLI filters the group’s iCal feed using this string to find the next scheduled meeting.
The iCal URL for the group’s meeting calendar. The CLI fetches this URL to determine the next meeting date and time.
The GitHub organization name. Defaults to
nodejs if not set (as defined in src/constants.mjs).The repository name within the GitHub organization where meeting issues are created (e.g.,
TSC, node, community-committee).The full human-readable name of the group. Used in the meeting issue title (e.g.,
Node.js Technical Steering Committee (TSC) Meeting 2025-01-15).The GitHub label used to search for agenda items across the organization. If omitted, defaults to
<shortname>-agenda (e.g., tsc-agenda). Issues and pull requests carrying this label are automatically included in the meeting agenda.A prefix for the meeting title. Defaults to
Node.js if not set. The generated title format is {HOST} {GROUP_NAME} Meeting {YYYY-MM-DD}.Multi-line markdown content with instructions for joining the meeting. Typically includes a Zoom link, a YouTube live stream link, and attendance confirmation instructions. Substituted for
$JOINING_INSTRUCTIONS$ in the meeting issue.An optional GitHub label to apply to the created meeting issue itself. Useful for filtering issues by meeting type in the repository.
The HackMD team namespace under which the meeting minutes document is created (e.g.,
openjs-nodejs). Required if you use the HackMD integration.Example: TSC meeting base file
The following is the actualmeeting_base_tsc file:
The
JOINING_INSTRUCTIONS value spans multiple lines and is wrapped in double quotes. The dotenv parse() function handles multi-line quoted strings correctly, preserving newlines within the value.