1212[ // ] : # " "
1313[ // ] : # " SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 "
1414
15- # Contributing to Jakarta JSON Processing
15+ # Contributing to Eclipse Parsson
1616
1717Thanks for your interest in this project.
1818
1919## Project description
2020
21- Jakarta JSON Processing is a Java API to process (e.g. parse, generate,
22- transform and query) JSON documents. It produces and consumes JSON in a
23- streaming fashion (similar to StAX API for XML) and allows to build a Java
24- object model for JSON using API classes (similar to DOM API for XML).
21+ Eclipse Parsson provides an implementation of Jakarta JSON Processing
22+ Specification. It allows processing (e.g. parse, generate, transform and query)
23+ JSON documents. It produces and consumes JSON in a streaming fashion (similar to
24+ StAX API for XML) and allows to build a Java object model for JSON using API
25+ classes (similar to DOM API for XML).
2526
26- * https://projects.eclipse.org/projects/ee4j.jsonp
27+ * https://projects.eclipse.org/projects/ee4j.parsson
2728
2829## Developer resources
2930
3031Information regarding source code management, builds, coding standards, and
3132more.
3233
33- * https://projects.eclipse.org/projects/ee4j.jsonp /developer
34+ * https://projects.eclipse.org/projects/ee4j.parsson /developer
3435
3536The project maintains the following source code repositories
3637
37- * https://github.com/eclipse-ee4j/jsonp
38+ * https://github.com/eclipse-ee4j/parsson
3839
3940## Eclipse Development Process
4041
4142This Eclipse Foundation open project is governed by the Eclipse Foundation
4243Development Process and operates under the terms of the Eclipse IP Policy.
4344
44- The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
45- Process (JESP) in accordance with the Eclipse Foundation Specification Process
46- v1.2 (EFSP) to ensure that the specification process is complied with by all
47- Jakarta EE specification projects.
48-
4945* https://eclipse.org/projects/dev_process
5046* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
51- * https://jakarta.ee/about/jesp/
52- * https://www.eclipse.org/legal/efsp_non_assert.php
5347
5448## Eclipse Contributor Agreement
5549
56- Before your contribution can be accepted by the project team contributors must
50+ In order to be able to contribute to Eclipse Foundation projects you must
5751electronically sign the Eclipse Contributor Agreement (ECA).
5852
5953* http://www.eclipse.org/legal/ECA.php
6054
61- Commits that are provided by non-committers must have a Signed-off-by field in
62- the footer indicating that the author is aware of the terms by which the
63- contribution has been provided to the project. The non-committer must
64- additionally have an Eclipse Foundation account and must have a signed Eclipse
65- Contributor Agreement (ECA) on file .
55+ The ECA provides the Eclipse Foundation with a permanent record that you agree
56+ that each of your contributions will comply with the commitments documented in
57+ the Developer Certificate of Origin (DCO). Having an ECA on file associated with
58+ the email address matching the "Author" field of your contribution's Git commits
59+ fulfills the DCO's requirement that you sign-off on your contributions .
6660
6761For more information, please see the Eclipse Committer Handbook:
6862https://www.eclipse.org/projects/handbook/#resources-commit
@@ -71,4 +65,4 @@ https://www.eclipse.org/projects/handbook/#resources-commit
7165
7266Contact the project developers via the project's "dev" list.
7367
74- * https://dev .eclipse.org/mailman/listinfo/jsonp -dev
68+ * https://accounts .eclipse.org/mailing-list/parsson -dev
0 commit comments