Viki Contributor Guidelines

All members of the Viki Contributor Community must follow the following Contributor Guidelines. The rules listed below span across all roles within Viki’s Contributor Community.

  1. Do not discourage members from participating in your Channel, or on Viki.
  2. Do not “blacklist” community members.
  3. Do not delete comments unless they do not follow our Community Guidelines.
  4. Do not use or enable the use of translating software or applications to translate subtitles on Viki.
  5. If you are assigned a role on a team and need to take a hiatus, please let your team members and/or the Viki Community Team know so your role can be replaced.

Channel Manager Guidelines

A Channel Manager (CM) is the main leadership role within a channel’s team structure. Channel Managers are the major decision makers who make sure the channel is being run smoothly.

Criteria for how Viki Selects a Channel Manager

  • Previous experience as a Channel Manager; or
  • Qualified Contributor (QC) tier or above.
  • Proven track record and good standing in the Viki Community.

Responsibilities as Channel Manager

  • You may create individual rules for a channel that you are managing, but those rules may not conflict with the Viki Terms of Use, Privacy Policy or Community Guidelines.
  • The Channel Masthead (cover page for each channel) should contain only images from the content shown in the Channel, such as official posters.
  • Channel Team Names may not contain derogatory, discriminating, explicit, insulting or otherwise negative words.
  • Do not discourage anyone from participating on your Channel, or on Viki.
  • Do not delete comments unless they do not follow Community Guidelines.
  • Managers of anime channels may not add or edit any channel information, such as channel name, channel description, channel design, episode descriptions or masthead images.
  • A newly approved Channel Manager must have logged activity within 48 hours of being selected.
  • A newly approved Channel Manager would have actively participated in the channel.

For upcoming on-air titles, this includes channel team recruitment before the title begins as well as management/moderation of the channel team during and after a title is on-air. For library titles, this includes being an active point of contact with Moderators, channel team members and/or interested contributors.

Moderator Guidelines

There are three types of moderators: English Moderators, All Language Moderators, and Language Moderators for each specific language offered on Viki. Overall, Moderators must be current and active on Viki. They should be willing to provide quality contributions to the community and be a vital player with their teammates. It is important for Moderators to be regularly available for the entire run of a series and recruit any other team members as needed.

Criteria for Moderator selection

  • Previous experience as a moderator; or
  • Can prove proficiency in language requested for moderation position.
  • Contributed at least 3,000 subtitles, in target language, before becoming a Moderator.
  • Qualified Contributor (QC) tier or above.

Responsibilities as a Moderator

  • You may create your own workflow for your team, but it may not conflict with the Viki Terms of Service, Privacy Policy or Community Guidelines.
  • Do not discourage members from participating in your Channel, or on Viki.
  • Do not delete comments unless they do not follow Community Guidelines.
  • Actively participate in the Channel.
  • Report any users who are using a translating program or application.
  • Respond to private messages inquiring about joining your team, even if you are not looking to recruit more team members.
  • Act as a Moderator on no more than 4 on-air Channels & 5 library titles at the same time.

For upcoming on-air titles, this includes channel team recruitment before the title begins as well as management/moderation of the channel team during and after a title is on-air. For library titles, this includes being an active point of contact with Moderators, channel team members and/or interested contributors.

Subtitler Guidelines

Subtitlers are contributors who translate or transcribe from the content’s audio into English or from English into another language (same cases may differ). For translations to languages other than English, it is highly recommended to wait until English subtitles are completed on an episode and the English Moderator gives the go-ahead, before translating into other languages (e.g: French, Spanish, Portuguese, etc.).

Criteria for Subtitler selection

  • Can show proficiency in target language. In some cases this can be assessed with a test or conversation with the language Moderator or Channel Manager.
  • Past contributions on the applicants profile will be used to gauge language proficiency.

Responsibilities of a Subtitler

  • Follow the Channel rules set by the Channel Manager and Moderators.
  • Always contact Channel Manager and/or Moderators before starting to subtitle, especially on active Channels.
  • No inappropriate subtitling, which may include but is not limited to:
    • Subtitling without knowledge of the target languages.
    • Copying subtitles from any source.
    • Using a translator program (ex: Google translate, Deepl, Reverso.)
    • Editing subtitles that are correct and/or complete for the sole purpose of increasing contribution counts.
    • Adding only HTML or punctuation marks into an empty segment.
    • Deliberately adding incorrect subtitles.
    • Adding anything other than subtitles to the subtitling section.

Segmenter Guidelines

Segmenters lay the foundation for subtitles by cutting a video into timed compartments. Good segments are the basis for good subtitles, so it is important to learn how to accurately cut segments before working on an on-air project (see our article “What is a Segmenter?).

Within a channel, there are two main types of segmenters: Segmenter and the Chief Segmenter. Segmenters are responsible for segmenting the videos, while Chief Segmenters are responsible for overseeing the segmenters on the team. Preferred applicants for the Chief Segmenter role should have prior experience segmenting.

Criteria for Segmenter selection

Responsibilities of a Segmenter

  • Follow the Channel rules set by the Channel Manager and Moderators.
  • Always contact Channel Manager and/or Moderators before starting to segment, especially on active Channels.
  • No inappropriate segmenting, which may include but is not limited to:
    • Deliberately creating unusable segments or segments that do not correspond to translatable dialogue.
    • Editing or deleting segments that are correct, well-timed or already subtitled.
    • Create mini-segments for the sole purpose of increasing the contribution count. 

Reporting failure to follow these guidelines

Failure to follow these guidelines may result in account suspension or other corrective actions. To report someone for failing to follow the guidelines, please  report user by following these instructions or contact us.

Was this article helpful?
893 out of 914 found this helpful

Comments

0 comments

Article is closed for comments.
https://support.viki.com/hc/en-us/articles/115000238047-Viki-Volunteer-Guidelines
support.viki.com
crawl=CC-MAIN-2022-05
53550
application/http; msgtype=response
sha1:2NV2TUXIOK7YCYKKKYSXKTOZE6POOJ4B
<urn:uuid:e279a841-29de-4ea7-8f82-efd0284d61c0>
2022-01-20T08:00:27Z
104.16.53.111
text/html
sha1:PWZNY5FDSPUIPYB2QKH2OLMTXIIVRRJS
<urn:uuid:d26cfd5f-002f-46bc-8c7c-c20ef8831c0a>
https://support.viki.com/hc/en-us/articles/115000238047-Viki-Volunteer-Guidelines
response
<urn:uuid:64176da6-4971-4215-8a80-a9f0ba14f725>
isPartOf: CC-MAIN-2022-05
publisher: Common Crawl
description: Wide crawl of the web for January 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-243
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/