Search results

Thanks for this feedback. CC licenses are copyright licenses, so anything that is permitted by copyright law falls outside the scope of them. It varies under applicable law, but the use of copyrighted works for AI training often falls under exceptions and limitations to copyright. Because of that, adding a “no AI training” clause to the CC licenses would have limited effect. We have instead tried tackling this outside of copyright with CC signals. The CC signals do not include a “no AI training” option because they are linked with IETF AI Usage Preferences that already include that option. CC signals are intended for those who want to allow machine reuse but with terms attached.

🏷 status: label work requiredNeeds proper labelling before it can be worked onNeeds proper labelling before it can be worked on

Status: Open.

#75 In creativecommons/cc-signals;

· try435 opened on Jul 20, 2025

Have a look at this Data Nutrition Label initiative; guidelines for healthy data for training AI.

✨ goal: improvementImprovement to an existing featureImprovement to an existing feature

💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository

🚦 status: awaiting triageHas not been triaged & therefore, not ready for workHas not been triaged & therefore, not ready for work

🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed

Status: Open.

Feature

#71 In creativecommons/cc-signals;

· mosart opened on Jul 11, 2025

Priorities: limiting AI scraping, keeping the power of copyright law limited

💬 talk: discussionOpen for discussions and feedbackOpen for discussions and feedback

💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository

🛠 goal: fixBug fixBug fix

🟨 priority: mediumNot blocking but should be fixed soonNot blocking but should be fixed soon

🧹 status: ticket work requiredNeeds more details before it can be worked onNeeds more details before it can be worked on

Status: Open.

Bug

#56 In creativecommons/cc-signals;

· dmarti opened on Jun 28, 2025

Apparent contradiction in guidance on training a proprietary never released model on -ND content

🏁 status: ready for workReady for workReady for work

📄 aspect: textConcerns the textual material in the repositoryConcerns the textual material in the repository

🛠 goal: fixBug fixBug fix

🟨 priority: mediumNot blocking but should be fixed soonNot blocking but should be fixed soon

Status: Open.

Bug

#46 In creativecommons/cc-signals;

· drawnto opened on Jun 26, 2025

[ALERT] Some issues moved to discussions

✨ goal: improvementImprovement to an existing featureImprovement to an existing feature

🏁 status: ready for workReady for workReady for work

📄 aspect: textConcerns the textual material in the repositoryConcerns the textual material in the repository

🔒 staff onlyRestricted to CC staff membersRestricted to CC staff members

🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed

Status: Open.

Feature

#27 In creativecommons/cc-signals;

· TimidRobot opened on Jun 26, 2025

CC Signals does not appear to support asset-based AI Preferences

✨ goal: improvementImprovement to an existing featureImprovement to an existing feature

🏁 status: ready for workReady for workReady for work

📄 aspect: textConcerns the textual material in the repositoryConcerns the textual material in the repository

🟨 priority: mediumNot blocking but should be fixed soonNot blocking but should be fixed soon

Status: Open.

Bug

#7 In creativecommons/cc-signals;

· lrosenthol opened on Jun 25, 2025