- Newest
- Most votes
- Most comments
Hi, look at Requirements section of https://fossa.com/blog/open-source-licenses-101-apache-license-2-0/ What you have to do is very clearly defined there
Read also https://en.wikipedia.org/wiki/Apache_License#Licensing_conditions
For compatibility,
and
Hi Didier,
Thanks for your reply. I've checked all your links, for here, I undestand that I've to licence my code by Apache license 2.0 of the AWS SDK for Javascript v3 ? and I've to add any change or modified part to my source code. As you see I'm a little confused. What does it mean ? From the links I see we need to include the Apache licence advice (and sometimes a NOTICE file) from AWS and we must include the modifications parts we changed ?. Finally, my question was if I licence the all code by MIT license, but will this require to include also the Apache license from AWS ?. Sorry for the inconvenients in my understanding, for this licenses topics I always make a mess. Can you help me more specifically ? Thanks again !
Greetings.
Hi Didier_AWS,
From your first last answer, I think what you mean, I should include then, the Apache 2.0 license and a statement with any major change. The changes I that I am going to introduce are not very significative, anyway I prefer (if it's possible) to include these changes, but in what way can I do it ?, for example in the same file which include the Apache license from AWS and the modified code ?, between comments lines, or how can I do it ? Finally, if I decide to distribute the code with MIT license, again, in what way, is it enough including the license file called "LICENSE" with my copyright ? and the text of the license ? for example:
"MIT License
Copyright (c) 2023 dcorralf
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation, etc ... "
To sum up, the final project will contains the Apache 2.0 License from AWS with a statement in case we add some changes, and this for each file that uses code from AWS, and finally in the resulting code push to my Github repository, and add the MIT license file ? is that so ?
Well Didier_AWS, step by step following your recommendations, I think I´m understanding the topics of code license, and it's cool and awesome !! Thanks again for your comprehension and understanding.
Greetings.
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Hi, On what you have to do precisely:
Anyone who uses open source software licensed under Apache 2.0 must include the following in their copy of the code, whether they have modified it or not:
The third requirement listed above is a major differentiator between the Apache License 2.0 and other permissive licenses. If you make any major modifications to the licensed code, you must disclose those changes in any updated version that you distribute.
However, you do not need to release the modified code under Apache 2.0. Simply including any modification notifications is enough to comply with the license terms.
Still from same FOSSA article
Using the Licensed Code The Apache License 2.0 outlines what users are allowed to do with the licensed code. Under this license, users can: