Volunteer & Mutual Aid Coordination
Versioning & Update Policy (v1)

Purpose

This document explains how versions of the Volunteer & Mutual Aid Coordination tools are labeled, updated, and distributed.

Clear versioning helps communities understand what they are using and whether updates are available.

--------------------------------------------------

Version Labels

Each document includes a version label in the format:

(vMajor.Minor)

Examples:
(v1)
(v1.1)
(v2)

--------------------------------------------------

Meaning of Version Numbers

Major Version Changes (v2, v3, etc.)
- Structural changes
- Significant philosophy updates
- New assumptions or boundaries

Minor Version Changes (v1.1, v1.2, etc.)
- Clarifications
- Formatting improvements
- Expanded examples
- Non-breaking updates

Minor updates should not require communities to change behavior.

--------------------------------------------------

Backward Compatibility

Whenever possible:
- Core principles remain stable
- Older versions remain usable
- Communities are not required to upgrade

No automatic migration is expected.

--------------------------------------------------

Update Frequency

Updates are:
- Infrequent
- Intentional
- Driven by real-world use

There is no fixed update schedule.

--------------------------------------------------

Distribution of Updates

Updated documents may be:
- Posted alongside prior versions
- Made available through public archives
- Shared through community channels

Older versions may remain accessible for reference.

--------------------------------------------------

Community Responsibility

Each community is responsible for:
- Deciding whether to adopt updates
- Reviewing changes before use
- Maintaining internal consistency

--------------------------------------------------

Modified or Forked Versions

Communities that modify or fork documents should:
- Adjust version labels as appropriate
- Avoid using official version numbers for altered content
- Clearly distinguish modified versions

--------------------------------------------------

Why This Policy Exists

Clear versioning prevents confusion and unintended changes.

This policy exists to support long-term stability and trust.
