Skip to content

Consider: Place for Historical Records #64

@marinamatic

Description

@marinamatic

Consider: Establish a Historical Records Section for Key Legacy Documents

  • Identify which old documents are important enough to be preserved.
  • Confirm whether these documents are already captured in ADRs, ODRs, or other existing records.

Description:

As we continue updating and restructuring documentation, it may be valuable to maintain a dedicated location for key historical documents that are not already captured in ADRs or ODRs. This section would serve as an archive for critical legacy documents, such as early versions of the pipeline description, the MVP outline, or other foundational documents that may provide historical context for future reference. (eg. fatalities002 or similar)

Key Areas to Cover:

  • Document Identification: List important legacy documents that should be preserved.
  • Storage Location: Determine the best place within the documentation structure to maintain these records.
  • Versioning Strategy: Consider whether documents should be kept in their original form or if brief summaries should be written for clarity.
  • Access and Visibility: Ensure the section is well-organized and easily accessible to those who may need historical context.

Objective:

To establish a structured approach for preserving important historical documents, ensuring that key legacy information remains accessible for future reference without cluttering active documentation.

Tasks:

  • Identify if there are key historical documents that should be preserved.
  • Verify if any of these documents are already stored in ADRs, ODRs, or other repositories.
  • Decide on an appropriate location for storing historical records.
  • Define a strategy for organizing and maintaining these documents.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions