Addison

This would be my proposal: ```php * @copyright Copyright (c) 2006-2020 Magento, Inc. (https://www.magento.com) * @copyright Copyright (c) 2021-present OpenMage Project (https://www.openmage.org) ```` My arguments. Those of us who contribute...

I see the legal aspect like this. We protected the code referring to an entity called the "OpenMage Project". In case of a violation of the law it would be...

I have had to deal with such situations over the years and the companies where I worked had a legal department and thus I saw the approach. When you specify...

I spoke a few moments ago with a colleague from the legal department. She says that when the year is mentioned that is the moment when copyrights begin to produce...

@justinbeaty - She says to mention the year you created something, anything, even a modification. That is the zero moment from which you start to claim ownership of the changes....

@fballiano - in that article one reference is made to the fact that Facebook has given up specifying the year. This is also an approach, but if it comes to...

@justinbeaty - what you showed in the examples I consider it represents the best legal explanation that I received. If we can make these changes without effort it is fine...

Here @colinmollenhour said the issue is not confirmed https://github.com/OpenMage/magento-lts/issues/1335#issuecomment-1151689355. If we can have some clues about testing we can check it.

From what I understand this PR comes as a proposal to solve a particular situation encountered in Magento. At first glance, the changes are made correctly, but what are the...

I have been using HoneySpam for almost 2 years. I reported several issues and they were resolved quickly, I appreciate the development team but it's not perfect let's say 85%....