Analysis of different forms of copyleft

When creating a type of software that is intended to be shared, it is important to think about copyright (and copyleft). It is understandable that creator(s) would not want someone modifying their work and sticking their own name on it.

If the creator is concerned with some other company modifying the project and using it for their own monetary benefit, it is probably most useful to use a strong copyleft. Maybe something like AGPL. Obviously, this decision has to be made rather early and if the creator(s) should want to make their work proprietary later, it would most likely not be possible. As EUPL is a variable license, it could be used as well.

If the creator was making something like a Python module, they might want to use a weak copyleft, because many software creators obviously want their work to be proprietary and thus they would avoid using the module if it had a strong copyleft on it. Maybe something like EUPL would do well.

In the previous example, the creator could also go the way of deciding to use a non-copyleft license in order to give more freedom to the software developers using the module.