Skip to content

Repo Tagging #30

@RossKen

Description

@RossKen

As part of improving knowledge sharing across the team we want to improve the README and tagging of projects.

README:

  • What makes a good README?
  • Approach the README as if it were going to be a public repo - focus on how you would explain the project to someone coming to the project for the first time.
  • Include brief description of the high level aim, basic outline of what techniques are used, list main packages for usage

Tagging:

  • customer/project area
  • key packages
  • key techniques

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