1
0
Fork
You've already forked circle.vision
0
No description
Find a file
Ctem 5cf03de7ec
 fix: complete session journal template update 
This fix includes:
- removal of the redundant logbook block from shell task "address
 non-routine tasks"
- refactor of schedule property-equipped routine "adjourn" into logbook
 block-equipped routine "finalize session journal PR" to reflect the
 change to a Git-based session workflow
- alphabetical placement of custom task block property `led-by`
2025年01月27日 14:05:14 +00:00
journals docs(journals): add 20250121-1400UTC 2025年01月22日 01:41:48 +00:00
pages fix: complete session journal template update 2025年01月27日 14:05:14 +00:00
README.md docs(readme): rename circle to Vision Circle 2025年01月23日 18:21:22 +00:00
TODO.md docs(todo): add template refactor task 2025年01月06日 18:11:10 +00:00

One Big Eyeball Foundation Vision Circle

Repository Structure

This repository contains the following directories:

  • journals: This directory holds the session journal files. These files are considered "agendas" when they are new and in a temporary branch, and they are considered "minutes" once they have been merged into the consent branch.
  • pages: This directory contains the journal template, which serves as a starting point for creating new entries.

Branching Strategy for Session Management

This repository uses a two-tiered trunk-based workflow to manage session journals. This workflow allows for efficient collaboration and version control while maintaining a clear and organized record of session minutes.

  • The consent branch serves as the central trunk, storing the permanent records of all session minutes.
  • Temporary journal branches are created from the consent branch to manage the journal for each session. These branches are used as a collaborative workspace for the team to add and update items until the session is complete. They are named according to the convention journal/<YYYYMMDD-HHMM>UTC[-<suffix>], where <YYYYMMDD-HHMM> is the scheduled date and time of the session in UTC, and <suffix> is an optional unique identifier (e.g., for distinguishing between multiple sessions on the same date).
    • Note: If the session date or time changes, the branch name should be updated to reflect the new schedule.
  • Changes to journal branches are submitted via pull requests from branches in forks of this repository. They are named according to the convention <journal branch name>/<type>/<description>, where <type> corresponds to the Conventional Commits specification (described in the Conventional Commits section).
  • Once a session is complete, the corresponding journal branch is merged into the consent branch and then deleted.

Commit Message Conventions

When making a commit, please follow these formatting conventions for commit messages:

  • Subject Line: Use the imperative mood in lowercase (except for proper nouns) (e.g., "add feature").
  • Body (optional): If included, write in complete sentences with proper grammar and punctuation, providing context for the changes.

50/72 Rule

  • The first line (subject) should be 50 characters or less, summarizing the changes.
  • Leave a blank line after the subject.
  • Optional: If a body is included, it should be wrapped at 72 characters per line for better readability.

Conventional Commits

The subject line should follow the format <type>[(<optional scope>)]: <description>. For session journal-related commits, <type> will typically be one of the following:

  • docs: for documentation changes.
  • style: for formatting changes.

Session Journal PR Review Checklist

  • Does each task apply to this circle?