-
Notifications
You must be signed in to change notification settings - Fork 35
Update README.md - IP rules for non-members #355
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
base: main
Are you sure you want to change the base?
Conversation
We should clarify whether and how non-members can submit use cases, user stories, etc. since they are in fact requirements for WG work, the WG or a WG TF should agree to them. If no TF has "sponsored" the issues then a full WG resolution should be required before merging new UCs, USs, or UCcategories. We might want to relax this so it only covers USs, though - to discuss. We should also state the IP policy, maybe say submitters agree to a specific W3C policy that we should link to, etc.
Wrote a proposed requirements policy/process document, see w3c/wot#1229. This PR has been updated to make it consistent. |
Merging of PRs for new User Stories require a formal resolution before they can be merged. | ||
In the case of User Stories proposed by a WoT WG TF that only impact that TF's deliverable, | ||
this only needs to be a TF resolution. In all other cases, a Working Group resolution is needed. | ||
In addition, only WoT CG, IG, or WG members who have agreed to the W3C IP policy may submit | ||
User Stories, Use Cases, or Use Case Categories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging of PRs for new User Stories require a formal resolution before they can be merged. | |
In the case of User Stories proposed by a WoT WG TF that only impact that TF's deliverable, | |
this only needs to be a TF resolution. In all other cases, a Working Group resolution is needed. | |
In addition, only WoT CG, IG, or WG members who have agreed to the W3C IP policy may submit | |
User Stories, Use Cases, or Use Case Categories. | |
PRs for new User Stories require a formal resolution before they can be merged. | |
User Stories proposed by a WoT WG TF that only impact that TF's deliverable | |
only need a TF resolution; for all other User Stories, a WG resolution is needed. | |
Further, only WoT CG, IG, or WG members who have agreed to the W3C IP policy may submit | |
User Stories, Use Cases, or Use Case Categories. |
I think that submission should be open to all and PRs should be created and merged as long as they make sense. Whether a user story is adopted to be worked should be indicated in another way. |
I agree with @egekorkan's comment. |
The issue is if we publish something in a Note, i.e. a document published by the W3C, then copyright etc. should be clear. Is it transferred to the W3C? Can we edit it? The other thing we could do here is state that a PR implicitly means the submitter agrees to abide by the W3C IP policy, whether or not they are a member. Come to think of it, it would be good to also make sure submitters are aware we may edit submissions after the fact, e.g. to fill in missing information or implications. |
Suggest changing the above so that it just says submitters have to agree to the IP policy, but don't have to be members. |
We should clarify whether and how non-members can submit use cases, user stories, etc. since they are in fact requirements for WG work, the WG or a WG TF should agree to them. If no TF has "sponsored" the issues then a full WG resolution should be required before merging new UCs, USs, or UCcategories. We might want to relax this so it only covers USs, though - to discuss.
We should also state the IP policy, maybe say submitters agree to a specific W3C policy that we should link to, etc.