General

This is a free service provided by the Drupal developers for the Drupal community. By using the repository you agree to the terms of services (see below).

• All code that is a derivative work of Drupal (typically PHP code, including but not limited to: core patches, modules, themes, etc) committed to Drupal.org’s git repository is licensed as GPL version 2.0 and later (official short identifier: “GPL-2.0-or-later”). This means that the code is licensed under GPLv2, and there exists an option that allows downstream recipients to re-license the code to be under a later version of GPL.
• All code should comply to the coding standards. Any patch or pull request that fails to do this will generally be treated as unfinished work.
• In general, all code downloaded from Drupal.org is distributed as GPL-2.0-or-later and includes this license. In some cases, code that is not a derivative work of Drupal may be distributed “in-aggregate” with Drupal code. Any permissively licensed 3rd party code that allows relicensing is automatically relicensed and distributed as GPL-2.0-or-later.
• Any third party assets you include must have their provenance, license and source documented in a file included in the project.
• The “or later” clause in the Drupal GPL-2.0-or-later license allows anyone to distribute a derivative work (i.e. a version of Drupal core, modules, themes) linked to a library under a license compatible with a later version of GPL, such as GPL-3.0-or-later. Distribution of such derivative works is not allowed from Drupal.org.

Drupal Contributions Repository - Terms of service (TOS)

The following terms of service represent the agreement between the Drupal Contributions Repository owners, hereafter the owner, and users of the Drupal Contributions Repository, hereafter the user.

Acceptance of Terms

The Drupal Contributions repository is a public and free service provided to share various additions to Drupal. A user’s use of this repository constitutes full acceptance of and agreement to the TOS; if a user does not accept the TOS, they are not granted rights to use the repository and should refrain from accessing the repository.

The owner reserves the right to modify or discontinue, temporarily or permanently any services or the TOS at any time, with or without prior notice to users. The owner is not liable for any damage to any user or other third party that may result from any such modification, suspension or discontinuance of the service or of the TOS.

Registration Obligations

All users are granted unlimited read access to the repository. Write access is granted only to registered users. Each user will receive a password and account upon completion of the registration process and is responsible for maintaining confidentiality thereof and is wholly liable for all activities occurring thereunder.

All information gathered during the registration process will be kept confidential, and will not be distributed to third-parties, unless the owner is asked to do so by the appropriate authorities.

Personally Identifiable Information (PII) Committed to Repositories

All users acknowledge that some personal identifiable information may be included in code repositories, in particular: names and email addresses associated with commit history.

In accordance with regulations such as the GDPR—specifically Article 6(1), clauses e (public interest) and f (legitimate interest)—it is the Drupal Association’s position that there is an overriding public interest in the availability of the data included in and associated with commits to our repositories. Because of the public and legitimate interest in this data, and because commits to these repositories are decentralized and irrevocable, the rights to be forgotten from repository history and to revoke future consent do not apply.

If a user wants to protect their PII in repositories, they are encouraged to use a pseudonym and the Drupal.org no-reply email address in their git configuration.

Content

All information, data, text, software, music, sound, photographs, graphics, video, messages or any other materials whatsoever (collectively, “content”), whether publicly posted or privately transmitted, are the sole responsibility of the party from which such content originated.

All code submitted to the repository that is a derivative work of Drupal must be and it will automatically be redistributed as GPL-2.0-or-later.

Any code that is not GPL-2.0-or-later compatible or granted an exception by the LWG should not be added to the repository and when found will be removed.

While Drupal-derivative code submitted to the repository must be GPL-2.0-or-later compatible, it may link to or depend on GPL-incompatible works – including but not limited to code, APIs, libraries, and other assets—to be used via manual installation, a dependency resolution tool such as Composer, or similar. However, Drupal.org cannot package or distribute these GPL-incompatible works, unless the works are not derivative of each other, and are being distributed “in-aggregate”. This is because the GPL permits the use of GPL and non-GPL works together, but not the copying, modification, or distribution of works based on incompatible licenses:

“Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.”

Any non-code content—including but not limited to assets like fonts, icons, images, etc—may be submitted to the repository under any license to which the user has the rights. The packaging or distribution of GPL-incompatible non-code assets “in aggregate” with GPL code is explicitly permitted in the final stipulation of Sec 3, Clause 2 of the GPL:

“In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.”

The repository maintainers can refuse or remove any content at their discretion and without prior notice to the affected party.

The owner is not responsible for the content maintained in the repository. All damages, physical, logical or other resulting from the use or abuse of the repository and its content are the user’s sole responsibility. The owner is not liable in any way.

Termination

A user’s account may be terminated without warning for reasons that include, but are not limited to:

1. violation of these TOS
2. violation of the Drupal Code of Conduct
3. violation of the DrupalCon Code of Conduct or Speaker Agreement
4. abuse of site resources or attempt to gain unauthorized entry to the site or site resources
5. use of service in a manner inconsistent with the purpose
6. a user’s request for such termination
7. requirement of applicable law, regulation, court or governing agency order

Disclaimer

All content is provided as is, without any warrant or support. Except when otherwise stated in writing the copyright holders and/or other parties provide content “as is” without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the content is with you. Should the content prove defective, you assume the cost of all necessary servicing, repair or correction.

Copyrights

All content is copyrighted by the author of said content, unless otherwise stated in writing.

If a user or other third party believes that its Content has been copied in a way that constitutes copyright infringement, that user or third party should provide the repository maintainers with the following information: (a) an electronic or physical signature of the person authorized to act on behalf of the owner of the copyright interest; (b) a description of the copyrighted work that has been infringed; (c) a description of where the allegedly infringing material is located on the Website; (d) the affected user or third party’s address, telephone number and email address; (e) a statement by the affected user or third party that he or she has a good faith belief that the disputed use is not authorized by the copyright owner, its agent or the law; and (f) a statement by the affected user or third party, under penalty of perjury, that the above information is accurate and that such user or third party is the copyright owner or is otherwise authorized to act on the copyright owner’s behalf.

Violations

Please report Git repository licensing violations, including alleged copyright infringements, to the Drupal Licensing Working Group issue queue. Report any other matters to abuse@drupal.org.