Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Enhancement request: Refine License Category - Copyleft Limited

未關閉
#499 13 則留言 0 個 reaction 已指派 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 分鐘
30 天內合併 PR
21

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

aboutcode-org/dejacode 的其他 Issue

查看 aboutcode-org/dejacode 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。