Does the license obligation apply to a developer for an open source project?

Question

Copyright

Suppose there is some project X. It is developed under the GNU GPL license, accepts contributions.
At one point, the developer decides that in the future the project needs to be developed not in open source. Can he do so?
According to Wikipedia,
> In general, the distributor of a program obtained under the terms of the GPL, or a program based on it, is obliged to provide the recipient with the opportunity to obtain the corresponding source code.
Is the developer a distributor?
How is the Apache License different in this regard?

Answer 1

Why do you think it takes so long for Linux to change the license, although Linus wants to (although not to a closed one).
Depends on the specific license:
For a number of licenses (example with Linux), you need to get the consent of all developers.
For a number of licenses (for example, BSD licenses), you can do anything without restrictions, you just need to remember to specify the parent system's copyrights in all its descendants.
Apachevskaya is quite loyal in this sense, similar to BSD, but I won’t give guarantees, you need to delve into the text carefully.