Licensing inconsistency
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- javascript
调研方向
首先审查 loopback-connector-sqlite3 以及 issue 中列出的其他 connector 的许可证元数据，然后将其与 LoopBack 宣传的 dual-license 声明进行比较。当项目提供一份清晰且权威的适用许可证说明，并明确软件包描述是否一致时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Licenses for Loopback are MIT/Strongloop are they not? Confused by Artistic license on these and other packages since a number are MIT/Strongloop including Mongo and others. Should these not be consistently MIT/Strongloop?
Perhaps there is an oversight here but the ability to make modifications and distribute these in your own code base/apps is what make this open. Can you clarify your position on these things since it is hard to know when requiring modules in node what to expect with Loopback modules and that is a serious turn off.
Please be consistent one way or the other. If it is not MIT, then it makes decision easier on whether to use loopback modules or work with another framework.
The following connectors appear to be inconsistent with the rest that are MIT/Strongloop:
loopback-connector-sqlite3 Artistic/Strongloop
loopback-connector-postgresql Artistic/Strongloop
loopback-connector-soap Strongloop proprietary license
loopback-connector-oracle Strongloop proprietary license
loopback-connector-mssql Strongloop proprietary license
Your advertising for loopback describes it as being:
Dual Licensed: MIT open-source license or StrongLoop license
This is not the case for a significant number of adapters for popular databases. I'll leave this to be answered once but this applies to a number of loopback packages. This is really a general question that applies to the Loopback ecosystem. I think anything that is promoted as Loopback should be expected to be licensed as advertised.
- 主要语言
- JavaScript
- 星标
- 13
- 派生
- 21
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
loopbackio/loopback-connector-sqlite3 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
-
Support referential integrity可能重新可做 @achrinza 于 1491 天前认领，目前没有进行中的 PR。 未关闭feature
loopbackio/loopback-connector-sqlite3#51 · 已指派 1 人 ·
-
feature
难度 2/5 1-3 小时 新手友好度 45/100
-
Loopback 4: HasManyThrough-Relation is not working可能重新可做 @achrinza 于 1708 天前认领，目前没有进行中的 PR。 未关闭backlog bug
loopbackio/loopback-connector-sqlite3#46 · 已指派 1 人 ·
-
难度 4/5 3-5 天 新手友好度 25/100
loopbackio/loopback-connector-sqlite3#43 · 1 条评论 ·
查看 loopbackio/loopback-connector-sqlite3 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
parse-community/parse-server#10699 · 1 条评论 ·
维护者通常 1 天内回复
-
area: dashboard bug perceived difficulty: 3
难度 2/5 1-3 小时 新手友好度 88/100
Nitjsefnie-Harness-Commons/daedalus#1179 ·
维护者通常 1 天内回复
-
Aframe enhancement javascript
难度 1/5 1 小时以内 新手友好度 92/100
webarkit/Aframe-nft#17 ·
-
spec-feedback
难度 2/5 1-3 小时 新手友好度 75/100