vuejs/vetur

MIT License and Stylint dependency

Open

#1,458 opened on Oct 11, 2019

View on GitHub
 (22 comments) (0 reactions) (1 assignee)TypeScript (594 forks)github user discovery
feature-requestgood first issueinteg:stylus-supremacyquestion

Repository metrics

Stars
 (5,752 stars)
PR merge metrics
 (PR metrics pending)

Description

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ

Info

  • Platform: all
  • vue-language-server : all versions which include stylint

First of all, I need to give you some context. I worked on Eclipse Wild Web Developer and I tried to include some vuejs support in it. See the current PR about my work. During the process, I created a Contribution Questionnary (CQ) at Eclipse Foundation. The goal was to validate the needed dependencies on all legal aspect (IP process). IP validation failed because one of transitive dependencies is under GPL-3.0 License. My contribution is actually blocked but it's not the point of this issue.

I reviewed the answer from the legal team. It seems that stylint is under GPL-3.0 License. In your case, stylint dependency comes from stylus-supremacy. I already create an issue about the license of stylint here : https://github.com/ThisIsManta/stylus-supremacy/issues/58

I'm not an expert about OSS licenses, maybe there is no problem. I'm only concern about the compliance between vue-language-server license and stylint license. I know my case is not the same as yours. My work is under Eclipse Public License 2.0.

Thanks a lot for your answer and some clarification about licenses.

Contributor guide

Research direction
Investigate the license of the stylint dependency (used via stylus supremacy) and determine if it is compatible with the MIT license of this project. If incompatible, suggest alternative packages or a license change.
Tech stack
typescriptvue
Domain
developer experiencebackend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
understanding of open source licenses
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70