Skip to content

Clean up runtimes/ and examples/ — decide what stays #45

@danbugs

Description

@danbugs

Summary

The runtimes/ and examples/ directories have grown organically and could use a cleanup pass. Some examples may be redundant, some runtimes may be unused, and the overall organization is a bit messy.

Questions to resolve

  • Which examples are essential (demonstrate a unique capability) vs. nice-to-have vs. redundant?
  • Are all Dockerfiles in runtimes/ actively used? By which examples?
  • Should some examples be consolidated? (e.g., python vs python-agent vs python-agent-driver vs python-tools)
  • Is the naming convention consistent and intuitive?
  • Should we add a README to examples/ explaining the taxonomy?

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