# Contributing to Jakarta Faces Thanks for your interest in this project. ## Project description Jakarta Faces defines an MVC framework for building user interfaces for web applications, including UI components, state management, event handing, input validation, page navigation, and support for internationalization and accessibility. * https://projects.eclipse.org/projects/ee4j.faces ## Developer resources Information regarding source code management, builds, coding standards, and more. * https://projects.eclipse.org/projects/ee4j.faces/developer The project maintains the following source code repositories * https://github.com/eclipse-ee4j/faces-api ## Eclipse Contributor Agreement Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA). * http://www.eclipse.org/legal/ECA.php Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file. For more information, please see the Eclipse Committer Handbook: https://eclipse.org/projects/handbook/#resources-commit ## AI-assisted contributions Use of AI coding assistants is welcome. If an AI tool materially contributed to a change, it is appreciated (but not required) to credit it in the commit message with a `Co-authored-by` trailer. Always include the model name and version so the attribution stays meaningful over time (model versions differ in behaviour). Here are some examples: - `Co-authored-by: Claude Opus 4.8 ` - `Co-authored-by: GitHub Copilot (GPT-5) ` - `Co-authored-by: Cursor (Claude Sonnet 4.5) ` - `Co-authored-by: Devin AI 2.0 <158243242+devin-ai-integration[bot]@users.noreply.github.com>` - `Co-authored-by: OpenAI Codex (GPT-5-Codex) ` - `Co-authored-by: Gemini 2.5 Pro ` - `Co-authored-by: Grok 4 ` Use whatever model and version your tool actually reports. Why we ask for this: - **Traceability** — makes it clear which parts of the history were AI-assisted, which helps when auditing a regression or a licensing question later. - **Accountability** — ties the change to the tool and model that produced it, not just a vague "AI" label; model versions differ in behaviour and matter. - **Responsibility** — the human contributor remains the author of record. The `Signed-off-by` and ECA requirements above apply unchanged, and you are expected to review, understand, and stand behind any AI-generated code you submit. ## Eclipse Development Process This Eclipse Foundation open project is governed by the Eclipse Foundation Development Process and operates under the terms of the Eclipse IP Policy. The Jakarta EE Specification Committee has adopted the Jakarta EE Specification Process (JESP) in accordance with the Eclipse Foundation Specification Process v1.2 (EFSP) to ensure that the specification process is complied with by all Jakarta EE specification projects. * https://eclipse.org/projects/dev_process * https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf * https://jakarta.ee/about/jesp/ * https://www.eclipse.org/legal/efsp_non_assert.php ## Contact Contact the project developers via the project's "dev" list.