It does get complex when a single Open Source project contains code from multiple different contributors, each holding their own copyright. I believe that's one reason why plenty of OSS projects (GNU & Android both spring to mind although with opposite motives) require contributors to assign copyright as part of contributing.
Alternatively, it's also a problem if you (say) link a bunch of GPL-licensed libraries to your own OSS source code. AFAIK in that case you can't really relicense & distribute your project in its entirety under a different license, due to GPL virality.
I have NFI if any of these gotchas apply in this case, though.
Of course all of this is likely irrelevant in this specific case, since I don't think this guy is telling the truth here, but you can absolutely sell GPL (or any other FOSS license) licensed code to other parties under a different license that doesn't require them to share code as long as you hold the copyright to that code.