@@ -4,13 +4,19 @@ Thanks for your interest in this project.
44
55## Project description
66
7- JSON-B is a standard binding layer for converting Java objects to/from JSON
8- messages. It defines a default mapping algorithm for converting existing Java
9- classes to JSON, while enabling developers to customize the mapping process
10- through the use of Java annotations.
7+ Jakarta JSON Binding™ is a standard binding layer for converting Java objects
8+ to/from JSON messages. It defines a default mapping algorithm for converting
9+ existing Java classes to JSON, while enabling developers to customize the
10+ mapping process through the use of Java annotations.
1111
1212* https://projects.eclipse.org/projects/ee4j.jsonb
1313
14+ ## Terms of Use
15+
16+ This repository is subject to the Terms of Use of the Eclipse Foundation
17+
18+ * https://www.eclipse.org/legal/termsofuse.php
19+
1420## Developer resources
1521
1622Information regarding source code management, builds, coding standards, and
@@ -20,20 +26,35 @@ more.
2026
2127The project maintains the following source code repositories
2228
23- * https://github.com/eclipse-ee4j/jsonb-api
29+ * https://github.com/jakartaee/jsonb-api
30+
31+ ## Eclipse Development Process
32+
33+ This Eclipse Foundation open project is governed by the Eclipse Foundation
34+ Development Process and operates under the terms of the Eclipse IP Policy.
35+
36+ The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
37+ Process (JESP) in accordance with the Eclipse Foundation Specification Process
38+ v1.2 (EFSP) to ensure that the specification process is complied with by all
39+ Jakarta EE specification projects.
40+
41+ * https://eclipse.org/projects/dev_process
42+ * https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
43+ * https://jakarta.ee/about/jesp/
44+ * https://www.eclipse.org/legal/efsp_non_assert.php
2445
2546## Eclipse Contributor Agreement
2647
27- Before your contribution can be accepted by the project team contributors must
48+ In order to be able to contribute to Eclipse Foundation projects you must
2849electronically sign the Eclipse Contributor Agreement (ECA).
2950
30- * http ://www.eclipse.org/legal/ECA.php
51+ * https ://www.eclipse.org/legal/ECA.php
3152
32- Commits that are provided by non-committers must have a Signed-off-by field in
33- the footer indicating that the author is aware of the terms by which the
34- contribution has been provided to the project. The non-committer must
35- additionally have an Eclipse Foundation account and must have a signed Eclipse
36- Contributor Agreement (ECA) on file .
53+ The ECA provides the Eclipse Foundation with a permanent record that you agree
54+ that each of your contributions will comply with the commitments documented in
55+ the Developer Certificate of Origin (DCO). Having an ECA on file associated with
56+ the email address matching the "Author" field of your contribution's Git commits
57+ fulfills the DCO's requirement that you sign-off on your contributions .
3758
3859For more information, please see the Eclipse Committer Handbook:
3960https://www.eclipse.org/projects/handbook/#resources-commit
0 commit comments