Policy to add "AUTHORS", copyright refers to "Blender Authors" instead of "Blender Foundation" #110784
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#110784
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Currently listing the "Blender Foundation" as copyright holder
implies the Blender foundation holds copyright to files which
may include work from many developers.
While keeping copyright on headers makes sense for isolated libraries,
Blender's own code may be refactored or moved between files in a way that
makes the per file copyright holders less meaningful.
Proposal
This proposal suggests to:
Blender Foundation
in headers withBlender Authors
.AUTHORS
file in the projects root directory,this list will contain all copyright holders, both individuals & organizations.
The authors file for the Chromium project will be used as a template.
Notes
Anyone wishing to find the origin of source code needs to use version-control
tools to track down the exact author for a given file/function.
Other copyright holders included in file headers will be left as-is.
scripts/addons
&scripts/addons_contrib
will not be included in this list.Proposed Steps
Replace all copyright text referencing
Blender Foundation
withBlender Authors
.See script:
./SPDX_blender_foundation_rename_to_authors_once.py
in PR.Add an
AUTHORS
file based on a modified output oftools/utils/credits_git_gen.py
.We may want to remove authors who made very small changes (only a few lines added/removed for e.g.).
The current authors file includes lines changed (clamped at 100).
Once added, manually maintain this file.
Open Topics
Criteria for including individuals in
AUTHORS
.Criteria for including organizations in
AUTHORS
.See pull request: !110783 which implements this change.
Policy for SPDX copyright identifierto Policy to add "AUTHORS", copyright belongs to "Blender Authors" instead of "Blender Foundation"Policy to add "AUTHORS", copyright belongs to "Blender Authors" instead of "Blender Foundation"to Policy to add "AUTHORS", copyright refers to "Blender Authors" instead of "Blender Foundation"A discussed earlier elsewhere, I think we should have a disclaimer like this as found in AUTHORS files in some other projects:
I would not bother to make this distinction, to keep it simple. Sometimes 10 lines changed could arguably have copyright, while sometimes 1000 lines of spelling fixes arguably do not. Sometimes there might be multiple smaller PRs that add up to a bigger change. Just seems easier if reviewers don't have to make decisions here.
Yes, we need to contact some of the contributors to check this.
Looks like a good change to me. I wonder, how does this work with individuals that have contributed with different email addresses? Can someone be listed multiple times?
We're free to do whatever we like, the chromium template we're following here seems to have no issue listing people twice, in either the individual and organisation sections, so I guess it's ok, but it's ultimately call for the admins to make. Don't think there is a right or wrong way here.
Done.
Agree this is very arbitrary, although I wouldn't mind picking a very small threshold. e.g. skip authors with 4 lines or less changed.
Otherwise this might as well be a generated dump of the credits.
@JacquesLucke the current listing uses the most recent git-author, there are so many that I don't think it's practical to do anything too sophisticated here. There is at least one duplicated which needs to be manually resolved, otherwise I think we can manually correct this as needed.