Skip to content

Consider creating and adding an "output register" to Readthedocs #1216

@asteiker

Description

@asteiker

As part of the CSCCE Birdaro training, several "playbook" components were introduced and evaluated, including answers to the "what" of a given open source project. One key aspect includes the communication of a given project's outputs in the form of an output register. This could include the following:

  • Register of outcomes or outputs from the project
  • Metrics and evaluation
  • Program expectations
  • Publications
  • Reports / summaries (survey response, materials created by champions or project partners, etc)
  • Community achievements - high level overview of what we’ve accomplished. Could include our origin story.

Metadata

Metadata

Assignees

No one assigned

    Labels

    impact: documentationImprovements or additions to documentation

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions