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

Copy_the_title_of_the_WG_issue_here #1914

Open
Sarrac3873 opened this issue Sep 24, 2024 · 0 comments
Open

Copy_the_title_of_the_WG_issue_here #1914

Sarrac3873 opened this issue Sep 24, 2024 · 0 comments

Comments

@Sarrac3873
Copy link

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ link_to_issue_raised_here

Instructions (delete this line and all following):

  • Check that TRACKER & S:... labels are there

  • Add t:... label(s) to indicate the topic (same as ids in specdev)

  • If urgent add:

    • ADVICE-REQUESTED label if the WG-issue is specifically asking for i18n to advise/comment
    • NEEDS-ATTENTION label if this is an important issue
  • If there's an i18n-*lreq label in the WG repo check for:

    • ...LREQ label(s) there should be one or more
    • SPEC-TYPE-ISSUE label (dark green background) should be there
    • TYPE-INFO-REQUEST label (red background) if this is a WG-issue that constitutes a request for script/language expert advice
    • i:... label(s) to indicate the Language Enablement Index category
  • Delete these instructions before saving the comment.

  • Do not remove § from the line with the link!

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

No branches or pull requests

1 participant