Clarification of license for client/shared
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Start by comparing client/shared/package.json with the repository README, root LICENSE, root package.json, and client/web/package.json, then review the license change history described in the issue. The work is complete when the intended current license for client/shared is clarified and its package metadata is consistent with that decision.
Written by the indexing model from the issue text.
Description
Hi — we're building a downstream deployment of Tailchat and noticed a small licensing inconsistency we'd like to clarify.
The repository README, root LICENSE, root package.json, and client/web/package.json identify Tailchat as Apache-2.0, but client/shared/package.json still contains:
"license": "GPLv3"
Looking through the history, shared/package.json appears to have received the same GPLv3 field as the other workspace packages when it was created in 2021. In August 2022, the repository LICENSE was changed from GPLv3 to Apache-2.0, and the enclosing client/root package metadata was subsequently changed to Apache-2.0, while the shared manifest appears to have remained unchanged.
Could you please clarify the intended license for the code under client/shared in current Tailchat releases?
Specifically, is client/shared intended to be covered by the repository's Apache-2.0 license, with the GPLv3 package field being a leftover from the earlier project license, or is that package intentionally licensed separately under GPLv3?
Thanks very much for the clarification.
- Dominant language
- TypeScript
- Stars
- 3.6k
- Forks
- 398
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
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.
More from msgbyte/tailchat
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
All issues in msgbyte/tailchat
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·