project-template
project-template copied to clipboard
Add LICENSE-docs file
Per CNCF policy, Docs are licensed under CC-BY-4.0 while code is licensed under Apache 2.0.
This commit adds a LICENSE-docs file to the project, as well as a license footer to the README.md to resolve this issue. Most docs repositories are code+docs, so for the average docs repository both are needed.
This came about after a short discussion with @amye and @cra :)
Signed-off-by: Celeste Horgan [email protected]
LGTM! Thanks for contributing this <3
/hold for TOC approval
@jberkus @idvoretskyi Saad had asked that we use our project board's TOC Approval column to identify items that needed approval before going live (in project-templates and on the website). Since the board is a repo board and not an org board, I can't add items from this repository to it. Can we create a board at the CNCF org level so that we can give the TOC a single place to look for items that need review?
Ping @caniszczyk on the org-wide board question.
@carolynvs - I'm not sure what the plan is for older projects, so I wouldn't worry too much about your projects. We definitely want to do this for new projects going forward, however :)
I just remembered that we can use "notes" on a project board and link to an issue in another repo. That seems like a totally workable way to do this without needing an org level project board. I've added this issue to the board.
That's correct, FYI there's an open issue here for GitHub to support multiple licenses https://github.com/todogroup/gh-issues/issues/72
On Thu, Aug 12, 2021 at 1:18 PM Carolyn Van Slyck @.***> wrote:
@.**** commented on this pull request.
In README.md https://github.com/cncf/project-template/pull/12#discussion_r687980007:
\ No newline at end of file +
+# License +$PROJECT_NAME is licensed under an Apache 2.0 license. +The #PROJECT_NAME documentation is licensed under a CC-BY-4.0 license.
I don't think that works with GitHub's autodetection of a license though, which personally I would care about.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/project-template/pull/12#discussion_r687980007, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSINDGQBLTZIYQTZLCKDT4QF65ANCNFSM47EI7JAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .
-- Cheers,
Chris Aniszczyk https://aniszczyk.org
@caniszczyk @amye @themoxiefox Is this something that we should still merge? We're cleaning up a few old things, but this looks like something that we might actually want to merge?
This is actually helpful!
We should not merge this. As far as I know, there are still unresolved questions about it.
Specifically, https://github.com/cncf/foundation/issues/230 is still unanswered.
@jberkus thanks for the link - I'll elevate this at the next GB meeting if not sooner through other means.