-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a developer, I am confused about the current state of the Magento license. #39493
Comments
Hi @damienwebdev. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Related: |
@sidolov, could you please reply? Will all these Adobe notices be removed from the Magento Open Source version? |
hi @ihor-sviziev, @damienwebdev, this notice was used by our Adobe internal team member by mistake, we will remove it asap. |
@chernenm: it would help a lot if the new copyright format is being fully validated by your coding standards tool, right now it only checks for the first line and doesn't care what other lines follow. If this can be checked fully, this problem wouldn't have happened probably. |
Hi @damienwebdev, Thanks for your reporting and collaboration. Adobe Commerce Engineering team started working on this issue. We will reach out to you if we need more information and you will get notified once the issue is fixed. Please leave comments for any further questions. Hence moving this issue to Thank you! |
Summary
I am confused by the current state of the Magento license.
On the one-hand, we have the License.txt in the root of the project indicating:
On the other hand, there are now files in the codebase that read:
Specifically:
These two statements are contradictory. Please clarify the current state of the license as applicable to the open source codebase.
Examples
Proposed solution
Please let me know which is behavior is correct, as they cannot simultaneously be correct given that they are logically opposed.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: