Skip to content

The code repository lifecycle #452

@matt-dray

Description

@matt-dray

How can we indicate to each other and to the public about the lifecycle status of a repo?

This helps people decide whether the code is current, for example, without necessarily needing to contact authors.

Some questions to address in the session:

  1. Possible states (active, just a concept, moved, etc).
  2. Making a decision (project status, time since last activity, etc).
  3. Making it clear to users (README badges, README callouts, archiving).
  4. Recognising that things change, man.

Feel free to add more ideas/questions below.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Potential

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions