Skip to content

📄 update license to CC BY 4.0 - #1730

Merged
ctcpip merged 1 commit into
gh-pagesfrom
license-update
Mar 18, 2025
Merged

📄 update license to CC BY 4.0#1730
ctcpip merged 1 commit into
gh-pagesfrom
license-update

Conversation

@ctcpip

@ctcpipctcpip commented Jan 13, 2025

Copy link
Copy Markdown
Member

switches to the OpenJS Foundation preferred license which is more permissive than the currently used CC BY-SA 3.0

edit: we could instead use the MIT license. I don't have strong feelings either way and only chose CC because the existing license is CC

@ctcpip
ctcpip requested a review from a teamJanuary 13, 2025 19:18
@netlify

netlifyBot commented Jan 13, 2025

Copy link
Copy Markdown

Deploy Preview for expressjscom-preview ready!

NameLink
🔨 Latest commitc07e0bb
🔍 Latest deploy loghttps://app.netlify.com/sites/expressjscom-preview/deploys/67d98bbf03463d0008156708
😎 Deploy Previewhttps://deploy-preview-1730--expressjscom-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@bjohansebas
bjohansebas requested a review from a teamJanuary 13, 2025 19:29
@bjohansebas

Copy link
Copy Markdown
Member

I would prefer to keep it as MIT, and have consistency across all the repositories in the organization

@wesleytodd

Copy link
Copy Markdown
Member

IANAL so have no strong opinion either way, but I agree that consistency across the project is a benefit of going MIT. Is there no more process or requirements for changing the licensing of the docs?

@ctcpip

Copy link
Copy Markdown
MemberAuthor

Is there no more process or requirements for changing the licensing of the docs?

nope, as long as we are using a license approved by the foundation, which this one and the MIT license both are

@bjohansebasbjohansebas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To prevent this from being merged until we decide which license to have.

@UlisesGasconUlisesGascon left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I am also +1 for MIT if we decided to use that one

@wesleytoddwesleytodd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be fine with this or MIT. MIT is consistent with all the other code project's licenses, and from my very limited quick research they are similar enough that it shouldn't have a meaningful effect on anything we are doing here.

@ctcpip
ctcpip requested a review from bjohansebasMarch 17, 2025 20:36
@ctcpip
ctcpip requested a review from a team as a code ownerMarch 17, 2025 20:36
@ctcpip

Copy link
Copy Markdown
MemberAuthor

discussed at TC meeting today. we agreed to proceed with the CC license, but left the possibility open for future licensing under MIT, or dual-licensing

@bjohansebas

Copy link
Copy Markdown
Member

@ctcpip whenever you want, you can merge it. I'm not sure if there's anything else to do.

OpenJS Foundation preferred license
@ctcpip
ctcpip merged commit c07e0bb into gh-pagesMar 18, 2025
@ctcpip
ctcpip deleted the license-update branch March 18, 2025 15:07
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@ctcpip@bjohansebas@wesleytodd@carlosstenzel@UlisesGascon@jonchurch