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.
What is the status of the project?
Section titled “What is the status of the project?”- 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
LICENSEfile is in the root of the source repository, and each module insrc/carries the headerSPDX-License-Identifier: MIT.
The official project data is on the project pages of the Eclipse Foundation:
Who makes decisions?
Section titled “Who makes decisions?”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.
How do you contribute?
Section titled “How do you contribute?”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()insrc/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.
How do you become a committer?
Section titled “How do you become a committer?”The existing committers of an Eclipse project elect new committers. The Eclipse Foundation Project Handbook describes the election and what a nominee needs.
Where does the project communicate?
Section titled “Where does the project communicate?”| 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 |
What does a bug report contain?
Section titled “What does a bug report contain?”CONTRIBUTING.md asks for these items when a package fails to build:
- The exact
main.pycommand. - The URL of the package.
- The sandbox profile:
alpineordebian. - The related part of
workspace/logs/agent_{repo}.log. - The related part of
workspace/logs/agent-call_{repo}.log, the LLM transcript. - The
AgentStatesnapshot fromworkspace/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.