Skip to content

Use Purpose and Scope to better set out aims for the work #20

@iadawn

Description

@iadawn

This is related to #14 but coming from a slightly different direction.

The Purpose and Scope reads more like a summary of the document content. This document is something quite different from the other -AUR documents and I am not sure that a similar Purpose and Scope to those documents serves well in this instance.

Given that this is a draft and that "future revisions are expected to have a different structure, and to address topic not treated in the current draft" I think a more valuable use of this section would be to communicates the broader aims and objectives of this work and laying out how the work will contribute to the dialogue on this topic within the community.

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