Licensing template files

[ajorg-aws]

When creating a new React app using the template the new project is necessarily based on those files. Presumably the files are under the MIT License that covers the rest of the package. This creates a situation where the best course may be to license the new project under the same license. Another option may be to create a THIRD-PARTY-NOTICES file that carefully notes which files are under the MIT License and which are under other licenses. Neither of these options are ideal for all React users.

Would it be appropriate to put the template files under a public domain declaration or a no-conditions license like MIT No Attribution (MIT-0) or BSD Zero Clause so that it's clear to users that their projects can be licensed however they like, as long as it's compatible with other licensed works in their project?

The template also includes logos which might be under trademark (the MIT License does not include a trademark grant). Would a statement allowing their use be appropriate? Or should they be removed from the template?

Thanks!

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[ajorg-aws]

Hello, I've been in contact with some of the stakeholders of this issue and was told that there's progress that's blocked by some other work. Please don't close this issue.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[ajorg-aws]

I'm still hoping we can find some resolution to this issue.

[ajorg-aws]

I ran into this again today. Is there anything I can do to help?

[xsrvmy]

My understanding of the situation is that because the MIT license doesn't require you to state changes ands allow sublicensing, it is sufficient to include the text of the license, state that the project used CRA's default template (this might not even be required), and simply apply your own license to the entire repo.

[ajorg-aws]

@xsrvmy I think that's basically correct, and it's what we've been doing.

The project doesn't help users get it right. It's a burden that I don't think is intended or desirable. And it's likely that many users don't recognize that it's required. The present state of things sort of encourages poor compliance, and it should be relatively easy to fix by changing the license on the template files to MIT-0 (which doesn't require attribution) or similar, along with either not putting logos in user's projects or providing a statement that explicitly permits their use.

These are all just suggestions. The project owners should do what they think is best of course. I just wanted to point out the friction it creates downstream. I hope that's helpful.

[xsrvmy]

TBH I think it's just the community not realizing this is a problem. Vite's templates don't carry the license either.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[ajorg-aws]

Looks to me like this issue is still current. Thanks!