Contents Menu Expand Light mode Dark mode Auto light/dark mode
GNOME Project Handbook
GNOME Project Handbook
  • Get in Touch
    • Matrix
    • Discourse
  • Project News
    • Planet GNOME
  • Teams
  • Governance
  • Foundation
    • Board of Directors
      • Officers
      • Previous Boards
    • Committees
      • Circle Committee
      • Code of Conduct Committee
      • Compensation Committee
      • Executive Committee
      • Finance Committee
      • Governance Committee
      • Committee Charter
      • Internship Committee
      • Membership & Elections Committee
      • Travel Committee
    • Membership Benefits
  • Infrastructure
    • Developer Access
    • Accounts
      • Managing Accounts
    • Email Aliases
    • Blog Hosting
    • GitLab
      • Hosting Requirements
      • New GNOME Projects
    • SSH Keys
    • Contact
  • Release Planning
    • Freezes
    • Release Team
  • Development
    • Change Submission
    • Commit Messages
    • Building
    • Building With Toolbx
    • Legal
  • Testing
  • Issue Tracking
    • Issue Reporting
    • Stack Traces
    • Issue Management
    • Issue Review
    • Stock Responses
    • New Issue Template
  • Maintainers
    • Making a Release
    • Release Signing
    • Release Pipeline
    • Branches
    • Issue Management
  • Events
    • GUADEC
    • GNOME.Asia
    • Hackfests
      • Organize a Hackfest
      • Hackfest Template
    • Travel
      • Travel Sponsorship Policy
Back to top
Edit this page

Legal#

This page details GNOME’s legal guidelines and requirements for development projects.

Licensing#

As an open source project, GNOME requires that all its modules be licensed using an OSI approved license (see the SPDX license list for reference). This includes repositories of assets and resources, as well as code.

The primary licenses used in GNOME are:

  • GNU General Public License, versions 2 and 3

  • GNU Lesser Public License, version 2

  • Creative Commons Attribution Sharealike (CCBYSA)

Each module’s license should be included in its COPYING file.

Copyright Notices#

While they are not strictly necessary, it is recommended that source code files include a copyright notice.

Some guidelines:

  • Existing copyright notices should not be removed

  • Avoid copyright notices for individual contributors, since this can lead to maintenance overhead

  • For new files, the following copyright notice is recommended: Copyright the <Module Name> authors

  • If you decide to add the year to a copyright notice, do not update it every year

For more information, see this article.

Formatting#

We recommend following the REUSE guidelines for expressing licensing terms and copyright inside a project:

  • Record the licensing terms using the SPDX-License-Identifier tag with a valid SPDX license identifier

  • Record the copyright holder using one or more SPDX-FileCopyrightText tags

For instance:

/* your-project-file.c
 *
 * SPDX-License-Identifier: LGPL-2.1-or-later
 * SPDX-FileCopyrightText: 2024 Your Name
 * SPDX-FileCopyrightText: 2025 Another Contributor
 */

Or:

# your-project-file.py
#
# SPDX-License-Identifier: GPL-3.0-or-later
# SPDX-FileCopyrightText: 2025 Your Name

For more information, see the REUSE tutorial.

Next
Testing
Previous
Building With Toolbx
On this page
  • Legal
    • Licensing
    • Copyright Notices
    • Formatting