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

LICENSE file #44

Open
andorsk opened this issue Oct 13, 2022 · 6 comments
Open

LICENSE file #44

andorsk opened this issue Oct 13, 2022 · 6 comments
Assignees
Labels
priority: high It is important for the group to resolve this issue soon. status: in-progress type: admin This issue requires an action by an admin. type: editorial The issue only involves wording and not normative content.
Milestone

Comments

@andorsk
Copy link
Contributor

andorsk commented Oct 13, 2022

Provide LICENSE file. Similar to https://github.com/w3c/csswg-drafts/blob/main/LICENSE.md. Note, LICENSE.md should be LICENSE ( no extension ) per the standards.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

@talltree talltree added the type: admin This issue requires an action by an admin. label Oct 14, 2022
@andorsk
Copy link
Contributor Author

andorsk commented Oct 17, 2022

@elisatrevino where can we get the appropriate LICENSE file for this repository?

@andorsk andorsk added the status: unassigned The issue is new and has not yet been assigned to anyone. label Oct 17, 2022
This was linked to pull requests Oct 26, 2022
@a-fox
Copy link
Contributor

a-fox commented Oct 26, 2022

As per https://wiki.trustoverip.org/display/HOME/Technology+Stack+Working+Group, the 'source code' license is Apache 2.0.I created a PR for this.

@a-fox a-fox removed the status: unassigned The issue is new and has not yet been assigned to anyone. label Oct 26, 2022
@a-fox a-fox self-assigned this Oct 26, 2022
@a-fox a-fox added priority: high It is important for the group to resolve this issue soon. status: pr-completed The issue is linked to a PR that is complete and waiting for review. type: editorial The issue only involves wording and not normative content. and removed type: admin This issue requires an action by an admin. labels Oct 26, 2022
This was unlinked from pull requests Oct 26, 2022
This was linked to pull requests Oct 27, 2022
@a-fox a-fox removed a link to a pull request Oct 27, 2022
@a-fox
Copy link
Contributor

a-fox commented Oct 27, 2022

Sorry for the hassle. I had to redo the PR. Also, the Github UI wants to link the first PR to the issue by default. That's why the linking-unlinking of the wrong PR.

@andorsk
Copy link
Contributor Author

andorsk commented Oct 27, 2022

@a-fox this is good stuff! Thanks. Generally though, shouldn't the PR be tagged as status: last-call so that if anyone has an issue they can raise it before a merge happens?

@andorsk
Copy link
Contributor Author

andorsk commented Oct 27, 2022

ah. I got a little confused b/c the multi PR's. NVM

@a-fox
Copy link
Contributor

a-fox commented Oct 27, 2022

As discussed in TATF meeting, we need a doc that contains all IPR clauses. This will be driven by @talltree to discuss with appropriate legal people on how we should address this issue.

@a-fox a-fox assigned talltree and unassigned a-fox Oct 27, 2022
@a-fox a-fox added status: in-progress and removed status: pr-completed The issue is linked to a PR that is complete and waiting for review. labels Oct 27, 2022
@talltree talltree added the type: admin This issue requires an action by an admin. label Nov 3, 2022
@andorsk andorsk added this to the PR-1 milestone Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high It is important for the group to resolve this issue soon. status: in-progress type: admin This issue requires an action by an admin. type: editorial The issue only involves wording and not normative content.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants