Skip to content

Add Apache 2.0 license - #92

Merged
NateshR merged 2 commits into
masterfrom
chore/apache-2.0-license
Aug 14, 2026
Merged

Add Apache 2.0 license#92
NateshR merged 2 commits into
masterfrom
chore/apache-2.0-license

Conversation

@usmansalimLM

Copy link
Copy Markdown
Contributor

Licenses this repo and @likeminds.community/chat-rn-core under Apache 2.0.

Changes

File Change
LICENSE new — canonical Apache 2.0 text, repo root
NOTICE new — LikeMinds copyright attribution (required by Apache §4(d))
likeminds-chat-reactnative-integration/LICENSE new — same text, so it ships inside the npm tarball
likeminds-chat-reactnative-integration/package.json "license" changed from ISC to Apache-2.0
likeminds-chat-reactnative-integration/README.md added a ## License section

Why two LICENSE files

The root LICENSE is what GitHub reads to show the repository's license badge. But npm packs
only the files inside likeminds-chat-reactnative-integration/, so the root file would not
reach npm consumers. Both are needed and both are byte-identical. This is standard practice
for a monorepo that publishes a subdirectory.

The five sample apps are intentionally untouched

ai-chatbot, cbc, community-chat, community-hybrid-chat, and networking-chat are all
marked "private": true and declare no license field. They are not published to npm and are
covered by the root LICENSE. Their package.json files are unchanged.

Notes for the reviewer

The LICENSE files are byte-identical to https://www.apache.org/licenses/LICENSE-2.0.txt
(SHA-256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30). Please do not
reformat them or fill in the Copyright [yyyy] [name of copyright owner] placeholder in the
Appendix. That placeholder is part of the Appendix's instructions for applying the license,
not this repo's copyright notice. Editing the text causes GitHub and license scanners to
report the license as "Other" instead of "Apache-2.0". The repo's own copyright notice lives
in NOTICE.

The package.json change matters as much as the LICENSE file. npm consumers' license
scanners read the registry metadata, not this repo. It takes effect on the next published
version
only; 1.10.0 and earlier keep ISC on npm permanently.

This is a relicense from ISC to Apache 2.0. Every contributor to this repo appears to be
LikeMinds staff, so this should be an internal decision, but please confirm before merging.

Context: this is one of three

@likeminds.community/chat-rn-core   -> likeminds-chat-reactnative       (this repo, public)
└── @likeminds.community/chat-rn    -> likeminds-chat-reactnative-data  (PRIVATE)
    └── @likeminds.community/chat-js -> likeminds-chat-js-data          (PRIVATE)

This repo is public, but both of its dependencies are private. Licensing this repo alone does
not make the React Native chat SDK usable as open source. Companion PRs:

Those two repos must also be made public (a separate decision, not done by any of these PRs).

Flagged, not changed

This repo has no root README.md. One would normally carry the License section and explain
the monorepo layout. Not added here to avoid inventing project documentation.

usmansalimLM and others added 2 commits August 13, 2026 13:03
Adds the canonical Apache License 2.0 text at the repo root and inside
the published npm package directory, a NOTICE file with the LikeMinds
copyright attribution, a License section in the package README, and
switches the chat-rn-core package.json license field from ISC to
Apache-2.0.

The LICENSE files are byte-identical to the text published at
https://www.apache.org/licenses/LICENSE-2.0.txt so that GitHub and
automated license scanners detect them correctly.

The five sample apps in this repo are marked private and are not
published to npm, so their package.json files are left unchanged; they
are covered by the root LICENSE.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@usmansalimLM
usmansalimLM requested a review from NateshR August 13, 2026 10:51
@NateshR
NateshR merged commit b683066 into master Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants