Help:Toolforge/Rules

From Wikitech
Jump to: navigation, search
Toolforge HelpFAQRulesDevelopingDatabasesJob gridKubernetesWebHow toList of ToolsGlossary

As part of Wikimedia Cloud Services, Toolforge is subject to the general Labs Terms of use, and is governed by the following additional rules:

  1. All code in the Tools project must be published under an OSI approved open source license
    The absence of a license means that default copyright laws apply. Without a clear license you are implicitly claiming copyright without providing an explanation of the rights you are willing to grant to others who wish to use or modify your software. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work until standard copyright lapses. In the United States today that means until 70 years after your death. This is counter to the general principals of the Wikimedia movement.
  2. Do not use your personal account for noninteractive use
    Any process intended to keep running while you are not actively interacting with it (e.g., through a detached screen session, as a background process, or through cron) must be run through a tool account, and not your personal account.
  3. Do not run noninteractive processes on the bastion servers
    Likewise, any process meant to execute without direct interaction should be submitted to the grid (e.g. via jsub or webservice) and not run directly on the login hosts. It is permissible to run lightweight processes (such as submitting a job, or rotating logs), but the job grid or Kubernetes should not be used for anything that runs for more than a few seconds or consumes large amounts of resources. Processes running on the bastion servers are subject to termination without notice.
  4. Do not run wikis or user-contributed content sites with open registration
    Spambots are very good at finding and flooding wikis, forums and other forms of user-contributed content sites to hammer with their crud. Tools that allow end-users to post content should limit posting to registered users that have been validated in some generally reliable manner (either by human verification, by checking against the user being a project member, or using OAuth).
  5. Do not provide direct access to Cloud Services resources to unauthenticated users
    For instance, do not allow web clients to issue shell commands or arbitrary SQL queries against the databases. Cloud Services resources are shared and limited, and it must be possible to attribute usage to specific LDAP users who are bound to the terms of use. Toolforge admin vetted Tools that include substantial anti-abuse and attribution information, such as PAWS and Quarry, are allowed.

See also