Enhancement request: Refine License Category - Copyleft Limited

オープン
#499 コメント 13 件 リアクション 0 件 担当者 3 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@hesa がすでに取り組んでいます。

2026年7月3日 から。

評価

この issue はまだ評価されていません。

説明

design needed enhancement

Problem
The current ScanCode/DejaCode License Category of 'Copyleft Limited' is defined as:
"A license that requires you to redistribute source code, including your changes, and also to provide attribution for the software authors. Your obligation to redistribute source code, including proprietary code linked with code under this license, is limited according to license-specific rules."

This category covers two types of Copyleft licenses that are more permissive than the original Copyleft/GPL-based Copyleft category but these types are quite different from a license risk perspective. The two types could be described as:

  • Copyleft - Library: where the software unit subject to Copyleft conditions is a library. The most common examples are variants of LGPL and GPL with a Classpath Exception;
  • Copyleft - File: where the software unit subject to Copyleft conditions is a file. Common examples, are variants of MPL, EPL and other so-called "public licenses".

Benefits
Many organizations have license usage policies that are distinct for the Copyleft - Library and Copyleft - File types. Replacing the current Copyleft Limited category with these more granular categories should make it much easier to apply basic license usage policies based on License Categories.

Solution
The solution is to update the licenses in the current Copyleft Limited category by:

  • Assigning each license to one of the new categories in a test dataspace. There are 330 licenses as of March 9, 2026.
  • Communicating the planned change to the ScanCode community. It is important to actually show people the proposed recategorization by license rather than just the concept.
  • Planning the implementation with enough lead time to minimize disruption to the ScanCode community.
主要言語
Python
スター
52
フォーク
30
平均マージ
4時間 57分
マージ済み PR(30日)
21

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aboutcode-org/dejacode のほかの issue

aboutcode-org/dejacode の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。