8000 Hard-coded copyright line from 0BSD license · Issue #6065 · go-gitea/gitea · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Hard-coded copyright line from 0BSD license #6065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ghost opened this issue Feb 14, 2019 · 2 comments
Closed

Hard-coded copyright line from 0BSD license #6065

ghost opened this issue Feb 14, 2019 · 2 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@ghost
Copy link
ghost commented Feb 14, 2019

#5558 updates 1.7.0 to add proper spacing to the license files from the spdx license list upstream. However, I noticed the license/copying file for 0BSD includes the copyright line with a hard-coded name in the license text. I think this copyright line needs to be removed as per the spirit of 0BSD and fact modern source control systems are capable of tracing this sort of thing easily back to an author (read: Black Duck).

I'm opening this issue as a reference/justification for updating SPDX license list to update the license text.
@techknowlogick techknowlogick added the issue/duplicate The issue has already been reported. label Feb 14, 2019
@techknowlogick
Copy link
Member

Closing as duplicate of #5397

@ghost
Copy link
Author
ghost commented Feb 14, 2019

@techknowlogick thanks sorry I never thought in a trillion years someone else wouldn't of duped this—I didn't even check.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@techknowlogick
0