microsoft / microsoft/vscode-extension-samples

Guidance on LICENSE

Open
#350 0 comments 0 reactions 1 assignee View on GitHub

@chrisdias is already working on this.

Since Oct 21, 2020.

Dominant language
TypeScript
Stars
10.2k
Forks
3.9k
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm currently writing a new VS-Code extension and I started from one of the extensions in here. In the LICENSE file, it states: https://github.com/microsoft/vscode-extension-samples/blob/9b8701dceac5fab83345356743170bca609c87f9/LICENSE#L12
I'm not 100% sure of what I should do with that. I plan on keeping the license as MIT in my project, but I don't plan on leaving the first line in my own project: https://github.com/microsoft/vscode-extension-samples/blob/9b8701dceac5fab83345356743170bca609c87f9/LICENSE#L1
I tried to look around a little bit to see what other authors did and from what I see, no one keeps the MS reference. Am I missing something?

Thanks a lot!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.