Skip to content

core: check the package and project name #4

Description

@jbpros

Low priority. Nothing blocks on this, but it gets harder to change once people use ergo.

The package name

Everything in ergo lives in package ergo, which policies reach as data.ergo. Rego has no namespaces beyond the package path, and every file loaded into OPA shares one tree. So if another library or someone's own policy also declares package ergo, OPA merges the two into one package. At best that's a compile error. At worst, rules quietly combine.

Options:

  • Keep ergo. It's short and reads well, but it's a common word, so a clash is possible.
  • Use a longer path, such as kosli.ergo or finos.ergo. It's much less likely to clash, but every policy has to write import data.kosli.ergo, and the name ties ergo to an organisation.

Every policy imports this name, so changing it later means every user has to update their policies.

The project name

Before going public, check whether "ergo" is free to use. Other software already uses it, including a Go actor framework (ergo.services) and a blockchain (Ergo Platform). A trademark search would settle whether that's a problem.

Activity

  1. added
    coreRelates to the ergo library or format themselves.
    on Sep 30, 2026
  2. changed the title [-]Check the package and project name before going public (low priority)[/-] [+]Check the package and project name[/+] on Oct 2, 2026
  3. changed the title [-]Check the package and project name[/-] [+]core: check the package and project name[/+] on Oct 2, 2026
  4. added
    proposalA design written down, waiting for comments.
    on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    coreRelates to the ergo library or format themselves.proposalA design written down, waiting for comments.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions