[xaerise]

To provide changes upstream, the maintainer must accept the change. Most opensource licenses are that you are required to publish your changes. But not upstream. As you wrote, there is no license that forces any "pull requests".

The MIT license is the "easiest" license because there are no responsibility for the maintainer..

[Zambyte]

> Most opensource licenses are that you are required to publish your changes

This isn't true either. You can privately fork AGPLv3 software without violating the license. You only have to provide the source (on demand!) to people who you provide the software to in executable form (where "executable form" includes network based access to the services executing the software in the case of the AGPL).

[pabs3]

... and the network access clause is only triggered when you modify the software.