Language committee/Handbook (committee)

←Language committee

Language committee (Guide for committee members)

This is internal documentation for the committee; see the documentation for requesting users.

Language committee
For requesting users
Requests Proposal policy Incubator manual & Handbook
For members
Handbook (committee)
Information
Common answers Discussion archives Monthly reports
Closing projects (voluntarily)
Closing projects policy Proposals

Status pages

A "status page" is a semi-official page that displays the precise progression of a request to approval, including links to relevant information and tools. These pages are critical information both for requesters (to direct their efforts) and committee members (to make a decision).

Although the procedure below is very long, it often becomes intuitive (add link, fill in template by checking the provided links, save).

1. Link to it from the request page:
   1. From Requests for new languages, navigate to the request page.
   2. Edit the page, and add a "|status=" parameter at the end of the "{{ls-header}}" template.
   3. After the '=' character, type the two-letter representation of the project they're requesting:

      wb	Wikibooks
      wn	Wikinews
      wp	Wikipedia
      wq	Wikiquote
      ws	Wikisource
      wt	Wiktionary
      wv	Wikiversity

   4. After these two letters, type "/" followed by the ISO 639 language code. Since there are several possible codes, you should choose the first option below that works:
      • If there is already a wiki in that language, the code is the one used for the existing wiki. (If this code doesn't match the one used by the new test project, create a redirect to the test project.)
      • If they have a test project with a valid ISO 639 code, use that code.
      • Otherwise, use the ISO 639-3 code (search).
   5. Save the page. By this point, the template should look something like this:

      {{ls-header|open|status=wp/en}}
      

2. Create the status page:
   1. Click the link in the text "(See an unofficial analysis of this request)". This will open the edit view for the status page, with the template already placed and the main requirements guessed.
   2. All that's left now is filling in the template:

      metadata
      en name	the English language name. This must be the name used in the title of the request page (move the request page is the title is incorrect).
      updated	the last date the requirements were checked. This is pre-filled, so don't change it (unless you're updating an existing status page).
      requirements (eligibility)
      new	mark 'done' if the wiki doesn't exist. You can check by copying the native (non-English) language name from the header when you preview, opening the "(list)" link, and pasting the name into your browser's search box. If you find the language, check that the requesting wiki doesn't exist.
      code	mark 'done' if there is a precise ISO 639 code. More general codes are not applicable; for example, 'en' can only be used for a general English wiki, not a British English wiki.
      unique	mark 'done' if the wiki could not coexist on a more general wiki (ie, British English on an English wiki). This requirement is rarely failed.
      scope	mark 'done' if there are living native speakers (the ISO 639 code must describe it as "living").
      requirements (final approval)
      test	mark 'done' if there is an active test project, as described by the language proposal policy (click on "automated statistics" to check).
      l10n main	mark 'done' if there are no untranslated "most-used MediaWiki messages" (click "list untranslated" to check).
      l10n core	mark 'done' if there are no untranslated "all MediaWiki messages". Otherwise, if this is the first wiki in the language (ie, you didn't find the language name when you searched it for "new"), mark 'optional'.
      l10n ext	mark 'done' if there are no untranslated "all extensions" messages. Otherwise, for a first wiki, mark 'optional'.
      approval	leave blank. This is marked 'done' when the wiki is approved, or 'rejected' when rejected.
      overrides
      category	Only if the test project is on the multilingual Wikisource or Beta Wikiversity, enter the name of the test project's top category without "Category:".
      iso639-3	Only if using an ISO 639-1 or ISO 639-2 code, enter the ISO 639-3 code. This is used to link to the SIL article.

   3. Save the page.
3. Edit Requests for new languages, and add the status page's subtitle to the relevant template. For example:

   {{ls-row| Wikipedia English | discussion | 2008-01-30 | wp/en }}
   

You're done!

Processing

Localization

Localization is now done almost entirely without help from the committee; just make sure that the status page exists and is up to date, and check Talk:Language committee for unanswered questions.

Verify as eligible

Verifying a project as eligible means checking that it meets all the requirements for eligibility listed on the status page.

1. If it the project is in a language new to Wikimedia projects, ask Translatewiki maintainers to add the language into the localization pool at the page Support.
2. If necessary, create the status page. Otherwise, update it by checking the links to information and tools provided for each criteria.
3. If all the requirements for eligibility are complete, leave a short note on the committee mailing list to make sure there are no objections. (If nobody objects within 24 hours or so, proceed.)
4. Edit the "{{ls-header}}" template on the request page so that it is "eligible". For example:

   {{ls-header|eligible|status=wp/en}}
   

5. Edit the request page's line on Requests for new languages so that it says "eligible" too, and change the date to today.

You're done!

Final decision

1. If necessary, create the status page. Otherwise, update it by checking the links to information and tools provided for each criteria.
2. An approval or rejection can be proposed only if the language fails the criteria for eligibility or the request meets all criteria for eligibility and approval.
3. Propose approval or rejection on the committee mailing list. Make sure to provide a link to the request page and/or status page, and a brief explanation of why it is ready for a final decision.
4. A final decision definitively closes the request. This should only be done if there is full consensus on the committee mailing list after at least 7 days. Once there is consensus, pick the correct procedure below.

Approval

1. For a wiki (usually a Wikipedia) in a language that is new to Wikimedia, the content has to be verified by an external source. Usually, it is verified and it can be approved. In case where the content is different from what it is supposed to be, it is rejected.
2. Notify the chairperson of the Board of Trustees by email that the wiki will be approved in four days unless they object. (Proceed after four days with no objection from the board.)
3. Give approval questionnaire to the interested editors at the request page. See Template:Lc-questionnaire for instructions.
4. Edit the request page: change the "{{ls-header}}" template to say "approved", and add a comment explaining the current status. For example:

   {{ls-header|approved|This wiki will be created at [http://en.wikipedia.org/ en.wikipedia.org]. ~~~|status=wp/en}}
   

5. Edit Requests for new languages:
   1. move the request page's template down into the "Recently closed" section;
   2. update it to "approved" and set the date to today;
   3. erase the status page text (the text like "wp/en").
6. File a bug request at Bugzilla with the information from #3 (you can use the automatic link in the questionnaire)
7. Edit Requests for new languages again, add add the bug number to the end of the template (where the status page text was).

Rejection

1. Edit the request page, changing the "{{ls-header}}" template to say "rejected". Write a carefully worded, polite explanation of why the project was rejected (see example).
2. Edit Requests for new languages:
   1. move the request page's template down into the "Recently closed" section;
   2. update it to "rejected" and set the date to today;
   3. erase the status page text (the text like "wp/en").