Lines Matching +full:cldr +full:- +full:apps
1 # Contributing to CLDR
5 The CLDR project consists of 3 aspects:
8 …- If you are not a native language speaker, but have evidence of CLDR data being incorrect, file a…
9 …- For data that is not collected in the [Survey Tool], such as [supplemental data][], file a [Jira…
11 …- For structural issues, note that many issues may be due to misunderstandings of the LDML spec. F…
12 … - File a [Jira][] ticket and provide evidence for the spec issues or to establish a new structure.
13 …- If your organization is not a [Unicode member][], consider becoming a member and work as a CLDR …
14 3. **CLDR internal tooling** such as adding new tests or fixing tooling that enable CLDR builds and…
15 - To contribute in internal tooling, [Contact][] us.
16 - See [Tools source][] and [Repository Organization][]
20 - `cldr-apps/`: (Survey Tool).
22 - UI: performance improvements, visual and functional refinements
23 - Additional checks (CheckCLDR) to validate CLDR data.
24 - `java/`: The core CLDR tooling.
26 - better documentation around code components
27 - updates to use newer/different library dependencies
28 - writing unit tests to improve code coverage
29 - better documentation around command line tools
35 - The PR and commits must reference a [Jira][] ticket which has been accepted by the CLDR-TC. Open …
36 - A Contributor License Agreement (CLA) must be signed. For more information, see [Contributor Lice…
37 - All tests must pass (See below)
38 - The PR must be reviewed by a TC member.
39 - The PR should have a single commit, and the first line of the commit must
44 CLDR-0000 Brief Description of Change
48 - Here is an item
49 - Here is another item
55 …ly added with a link to the CLA Form), or go directly to [the CLA Form][sign-cla]. You may need to…
57 - **Individual CLA**: If you have determined that the Individual CLA is appropriate, then when you …
59 - **Corporate CLA**: If you have determined that a Corporate CLA is appropriate, please first check…
61 …roject is released under the [OSI-approved][osi-Unicode-License-3.0] free and open-source [Unicode…
69 mvn test --file=tools/pom.xml
74 For more detail, and how to run the tests locally, see [Running Tests][] on the CLDR development si…
78 … commit is pushed to GitHub and when a PR is opened requesting changes to CLDR. You will see the s…
82 - ● An orange circle indicates that information is not available yet, such as a test that is still …
83 - ✖ A red X indicates a failure or a warning. Depending on the type of issue, merging might be bloc…
84 - ✔ A green checkmark indicates success.
86 
90 
92 If a test or status check does not pass, see [Running Tests][] on the CLDR development site.
96 Copyright © 1991-2024 Unicode, Inc.
99 [Survey Tool]: https://cldr.unicode.org/index/survey-tool
101 [Jira]: https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md
102 [Tools source]: https://github.com/unicode-org/cldr/tree/main/tools
103 [Maven setup]: https://cldr.unicode.org/development/maven
104 [Repository Organization]: https://cldr.unicode.org/index/downloads#h.lf1z45b9du36
105 [How to contribute]: https://cldr.unicode.org/#h.vw32p8sealpj
106 [Unicode member]: https://home.unicode.org/membership/why-join/
107 [supplemental data]: https://github.com/unicode-org/cldr/tree/main/common/supplemental
108 …ecks]: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-status-…
109 [Running Tests]: https://cldr.unicode.org/development/cldr-development-site/running-tests
111 [unicode-corporate-clas]: https://www.unicode.org/policies/corporate-cla-list/
113 [sign-cla]: https://cla-assistant.io/unicode-org/.github
114 [osi-Unicode-License-3.0]: https://opensource.org/license/unicode-license-v3/
115 [unicode-license]: https://www.unicode.org/license.txt