Skip to content

Evaluate 'Community Specification' for appropriateness for git-bug's spec #1

@cfkaran2

Description

@cfkaran2

@MichaelMure suggested using 'Community Specification' as the license for 'git-bug'. Someone needs to read through it and vet it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions