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 recommendation for licensing to Staging Process #41

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ThisIsMissEm
Copy link
Contributor

@ThisIsMissEm ThisIsMissEm commented Nov 8, 2024

Whilst I've recommended the Software and Documents License, there's also additionally licenses for test suites, documents alone and a Intellectual Rights document.

Copy link
Contributor

@tantek tantek left a comment

Choose a reason for hiding this comment

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

I support the explicit reference to the W3C S&D License. Thanks Emelia.

@ThisIsMissEm
Copy link
Contributor Author

ThisIsMissEm commented Nov 8, 2024

In the ActivityPub Trust & Safety Taskforce's contributing.md, we have the following:

Contributions to this repository are intended to become part of Recommendation-track documents governed by the W3C Patent Policy and Software and Document License. To make substantive contributions to specifications, you must either participate in the relevant W3C Community or Working Group or make a non-member patent licensing commitment.

Maybe that is better language than that which I have used here?

@evanp
Copy link
Contributor

evanp commented Nov 9, 2024

There's already a section on contributions in the CG Charter. with stronger language:

Specifications created in the Community Group must use the W3C Software and Document License. All other documents produced by the group should use that License where possible.

@evanp
Copy link
Contributor

evanp commented Nov 9, 2024

I also think that at least at Stage 0, contributions don't need to be under the CG's IP rules -- in fact, that's the whole point.

I think we should call out when contributions need to be under the CG's contribution rules, and link to those rules directly, rather than reiterating them.

@ThisIsMissEm
Copy link
Contributor Author

I think it's worth pointing out ahead of time that if you want something to get to standards track, then that's the license it'd be under

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.

3 participants