Skip to content
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.

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

Add W3C software and document license (2023-01-01) #1169

Open
wants to merge 3 commits into
base: gh-pages
Choose a base branch
from

Conversation

ThisIsMissEm
Copy link

Whilst previous W3C licenses are in the SPDX repository, the 2023-01-01 license version was not yet, there's an open pull request for that here: spdx/license-list-XML#2269

As all the W3C groups tend to use GitHub for specification work, being able to select from the "Add a license" dropdown the latest W3C license is quite useful. A code-search for W3C in license files showed 49k code matches and 4k repositories.

The link https://spdx.org/spdx-license-list/request-new-license appears to be broken, so I sent a PR to the spdx repository, hopefully that's the correct process.

The previous version of this license is on the OSI's license list, the current version is not (I suspect just because it's not been updated?) https://opensource.org/license/w3c/ — I have tried to reach out to appropriate people at the W3C to follow the OSI's fairly lengthy process for updating their license.

@mlinksva
Copy link
Contributor

I would not mind adding this eventually (though that doesn't mean it would automatically appear in the drop-down, which I think is fine, this really has a niche use case and people familiar with that can copy and paste). In addition to the SPDX and OSI processes (thanks for starting) the "used by" examples probably will need replacing. Not clear to me there's a license in the AS2 repo, and the others use a link which can't currently be detected, needs the full text.

@ThisIsMissEm
Copy link
Author

I would not mind adding this eventually (though that doesn't mean it would automatically appear in the drop-down, which I think is fine, this really has a niche use case and people familiar with that can copy and paste). In addition to the SPDX and OSI processes (thanks for starting) the "used by" examples probably will need replacing. Not clear to me there's a license in the AS2 repo, and the others use a link which can't currently be detected, needs the full text.

The link format seems to be the most common way, rather than embedding the full text of the license.

To clarify, I'm just an independent, but it did come up at an SWICG meeting that having it searchable in the license list would make it easier for CGs and WGs to start repos.

Haven't been able to follow up on SPDX yet. Apparently I missed something in their process.

conditions:
- disclose-source
- include-copyright
- same-license--file
Copy link
Contributor

Choose a reason for hiding this comment

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

There's no such requirement in this license, this should be deleted.

@mlinksva
Copy link
Contributor

FWIW, looks like the SPDX license issue URL is uncool, moved to https://tools.spdx.org/app/submit_new_license/ without redirect. 😬

@mozz30-tech
Copy link

Whilst previous W3C licenses are in the SPDX repository, the 2023-01-01 license version was not yet, there's an open pull request for that here: spdx/license-list-XML#2269

As all the W3C groups tend to use GitHub for specification work, being able to select from the "Add a license" dropdown the latest W3C license is quite useful. A code-search for W3C in license files showed 49k code matches and 4k repositories.

The link https://spdx.org/spdx-license-list/request-new-license appears to be broken, so I sent a PR to the spdx repository, hopefully that's the correct process.

The previous version of this license is on the OSI's license list, the current version is not (I suspect just because it's not been updated?) https://opensource.org/license/w3c/ — I have tried to reach out to appropriate people at the W3C to follow the OSI's fairly lengthy process for updating their license.

Copy link

@Dioliode Dioliode left a comment

Choose a reason for hiding this comment

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

DioX

Copy link

@Dioliode Dioliode left a comment

Choose a reason for hiding this comment

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

DioX

Copy link

@Dioliode Dioliode left a comment

Choose a reason for hiding this comment

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

DioX

@Mahdimohmmadi
Copy link

@

Copy link

@Yehtet-dd Yehtet-dd left a comment

Choose a reason for hiding this comment

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

_licenses/osl-3.0.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants