Skip to content

Defining Efficiency/Defining a Healthy Repo #83

@hcaballero2

Description

@hcaballero2

Description

In order to improve the health/efficiency of repositories within our organization, we need to determine what our definition of "healthy" and "efficient" is.

Steps to Reproduce

  1. What do healthy repositories have (according to the OS community or professional developerment community)
  2. What do efficient repositories have? (according to the OS community or professional developerment community)
  3. Does being a healthy repo and efficient repo mean different things?
  4. What SINGLE definition would be applicable to our organization
    • Not looking for perfection, just start to brainstorm about how we can define a healthy/efficient repository, we will have a bigger discussion as a team before making our decision.

Expected Behavior

Documentation regarding the research outlined above

Actual Behavior

(FILL OUT WHEN YOU CLOSE THIS ISSUE)

Environment

  • OS:
  • Browser/Version:

Additional Information

(FILL OUT WHEN YOU CLOSE THIS ISSUE)

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomersresearchlooking into new information/tools

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions