Skip to content
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.

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

Meta: Add condition to prior art in CONTRIBUTING.md #517

Merged
merged 3 commits into from
Dec 11, 2020
Merged

Meta: Add condition to prior art in CONTRIBUTING.md #517

merged 3 commits into from
Dec 11, 2020

Conversation

sffc
Copy link
Contributor

@sffc sffc commented Dec 1, 2020

Based on #513

@sffc sffc changed the title Editorial: Add condition to prior art in CONTRIBUTING.md Meta: Add condition to prior art in CONTRIBUTING.md Dec 2, 2020
@sffc sffc requested a review from longlho December 3, 2020 23:36
@sffc
Copy link
Contributor Author

sffc commented Dec 3, 2020

I added a section about payload size. PTAL

Copy link
Member

@zbraniecki zbraniecki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! Thank you!

@sffc sffc merged commit d611304 into master Dec 11, 2020
@sffc sffc deleted the prior-art branch December 11, 2020 23:19
2. **Difficult to implement in userland:** 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.
3. **Broad appeal:** 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. Alternatively, the champion can make a case that their feature is critical for a multilingual web, even if it lacks broad appeal.
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. If the feature is not yet available in CLDR, ICU, or Unicode, the champion should start there before coming to ECMA-402.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this wording indicates that ICU/CLDR/Unicode are pre-requisites. Maybe change them to example prior arts instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants