Skip to content

Governance

Eclipse Atesor™ is an Eclipse Foundation project in incubation, under the OpenHW Group. The code is under the MIT licence. This page tells you who makes decisions, how you can contribute or become a committer, and where the project communicates.

  • Foundation: Atesor is a project of the Eclipse Foundation. The project ID is openhw.atesor.
  • Parent: the project is under the OpenHW Group.
  • Phase: incubation. The Eclipse Foundation Project Handbook describes the phases of a project.
  • Licence: MIT. The LICENSE file is in the root of the source repository, and each module in src/ carries the header SPDX-License-Identifier: MIT.

The official project data is on the project pages of the Eclipse Foundation:

Atesor follows the Eclipse Foundation Development Process, like each Eclipse project. The handbook describes the process and the roles:

  • Committers have write access to the project repositories. They review contributions and merge them.
  • Project leads lead the project and represent it in the Eclipse Foundation processes.

The Who is involved page lists the current project leads and committers.

Any person can contribute through a pull request. CONTRIBUTING.md lists these ways to help:

  • Port a package and submit the recipe.
  • Add a new platform profile. See Add a platform.
  • Improve the error classification in classify_error() in src/state.py.
  • File a bug report for a package that fails in a repeatable way.
  • Improve prompts, tests or documentation. See Change the docs.

To prepare a checkout and submit a change, see Development setup. The handbook describes what the Eclipse Foundation asks of each contributor.

The existing committers of an Eclipse project elect new committers. The Eclipse Foundation Project Handbook describes the election and what a nominee needs.

Channel Use
atesor-dev mailing list Development discussion
GitHub issues Bug reports and other problems
Pull requests Code and data changes
project-website Changes to the website and these docs

CONTRIBUTING.md asks for these items when a package fails to build:

  • The exact main.py command.
  • The URL of the package.
  • The sandbox profile: alpine or debian.
  • The related part of workspace/logs/agent_{repo}.log.
  • The related part of workspace/logs/agent-call_{repo}.log, the LLM transcript.
  • The AgentState snapshot from workspace/output/{repo}_state_*.json, if there is one.

For other problems, open an issue with the steps that show the problem again.

For the origin of the name, see About the name.