Skip to content

License audit #7

Open
Open

Description

@bennyvasquez

We need to audit all repos and ensure that all have a license.

Activity

  1. self-assigned this
    on Feb 5, 2024
  2. bennyvasquez commented on Oct 16, 2026

    @bennyvasquez
    SponsorMemberAuthor

    I finally finished the audit this issue was opened for. Every public repo we own now either has a license or has a PR open to add one, based on the AlmaLinux OS licensing policy.

    How I picked each license:

    • If the repo already declares a license somewhere (in pyproject.toml or its README, for example), the PR just adds the matching LICENSE file.
    • Code repos created before the GPLv3 guidance was added to the policy (2023-08-23) get MIT, which is the policy's Default License for Code and already applied to them.
    • Code repos created after that date get GPL-3.0-or-later, as the policy recommends for software that doesn't ship in AlmaLinux OS.
    • Libraries get MIT, documentation gets CC BY-SA 4.0, and templates and issue trackers get CC0.
    • Anything based on upstream work keeps the upstream license.

    The PRs:

    compose-tests is the one that needs a real conversation, because most of its tests came from CentOS t_functional, which has no license. That's in AlmaLinux/compose-tests#78, with a draft PR in AlmaLinux/compose-tests#79.

    If you maintain one of these repos and think it should use a different license, please say so on its PR. I'll close this issue once they're all merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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