A project (desktop app) that I've been using for a while has decided to go closed source. I fully respect the decision, but also have no interest in the direction where this new development is headed. As such I've become curious about making a fork of the project.
Looking at the last version of the code available, I saw the license is AGPL v3. Reading up on it - it sounds like it's something that is used with very specific intent: Open Source + vendor lock-in. (see http://www.dr-chuck.com/csev-blog/2014/09/how-to-achieve-vendor-lock-in-with-a-legit-open-source-license-affero-gpl/)
Now, the project went from MIT -> AGPL when I assume, the author decided to prepare the move. This is when the cloud functionality started appearing in the app.
If I was to fork the project from the last code point - the only license available to me would be AGPL?
If I understand this correctly, now any new changes on my fork cannot be incorporated by the now closed source project - because it is closed source? Even tho it was the original AGPL project.
For me, one of the deciding factors for choosing the application was the fact that it was Open Source. I'm just trying to make sure I understand the situation before taking any action.