microsoft / microsoft/vscode-cpptools
Separate our ThirdPartyNotices.txt into Distribution and Repository versions
Open
Nobody has claimed this yet.
internal
Language Service
license
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
See what the Python extension does at https://github.com/Microsoft/vscode-python .
Also, the notices for gcc and LLVM need to be updated (possibly others).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the current ThirdPartyNotices.txt with the approach used by the linked vscode-python extension. Determine how to separate distribution and repository notices, then review the gcc and LLVM notices for required updates. Done means both versions are distinct and the named notices are current.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100