It would seem to make more sense (in the context of the apparent desires of developers in this situation) to license things like this with a dual license setup.

It would seem to make more sense (in the context of the apparent desires of developers in this situation) to license things like this with a dual license setup. License the base project as AGPL and have outside contributors sign a copyright license. All open source projects compatible with AGPL can use it as is. The second license would be a freeware/commercial license. Freeware for organizations under 1 million dollars US in revenue. A paid commercial license above that mark. That would seem to satisfy the base requirements that developers want as well as some of the community. Of course, the rest of the community that wishes it to continue under the existing license would be free to fork that last available version as always.