Skip to content

Meta: Change "Difficult" to "Expensive" in Stage 2 entrance criterion #557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sffc merged 2 commits into from
Aug 12, 2021
Merged

Meta: Change "Difficult" to "Expensive" in Stage 2 entrance criterion #557

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
72f74b0
Change "Difficult" to "Expensive" in Stage 2 entrance criterion
sffc Mar 12, 2021
315444d
Tweaking explanation of "expensive to implement in userland"
sffc Apr 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@ When the ECMA-402 subcommittee reviews proposals for *new features*, we hold the
1. **Prior Art**
1. Our job is to bring features that i18n experts have already solved to JavaScript developers, not to invent new solutions to those problems. We often reference CLDR, ICU, and Unicode as prior art.
2. The data and algorithms specified in CLDR, ICU, and Unicode are of variable quality. In order to be adopted by ECMA-402, the prior art must be considered best i18n practice by consensus of the ECMA-402 standards committee.
2. **Difficult to Implement in Userland**
1. Features in Intl must bring something to the table that a third-party library wouldn't be able to do with the same level of efficiency and performance. The champion can cite a heavy locale data dependency or a complex algorithm to satisfy this criterion.
2. **Expensive to Implement in Userland**
1. Features in Intl must be significantly more efficient and less complex than a third-party library implementing the same feature. The champion can cite a heavy locale data dependency or a complex algorithm to satisfy this criterion.
3. **Broad Appeal**
1. The champion must demonstrate that their feature request is needed by a large number of smaller web apps or a smaller number of high-profile web apps (Calendar, Travel Booking, etc). As a rule of thumb, the champion should demonstrate that their new feature is at least as useful as an existing feature in ECMA-402. The champion can provide npm module statistics or a list of user requests to satisfy this criterion.
1. Alternatively, the champion can make a case that their feature is critical for a multilingual web, even if it lacks broad appeal.
Expand Down