You are under no obligation to automatically release GPL code.
You must release GPL code only if you are distributing the GPL code (in any form - compiled or otherwise) to others, and you are only obligated to release it to those you are distributing it to. You could have GPL code that you sold and released to Microsoft and no one else - only they would have GPL rights to the source code, no one else. They could release it to anyone they like, of course. GPLv3 adds in some stuff about software as a service, as well.
If you don't want to release the source at all, why on earth would you want to call it "open source"? Use a normal proprietary license if you've got proprietary code.
发布评论
评论（1）
您没有义务自动发布 GPL 代码。
仅当您将 GPL 代码（以任何形式 - 编译或其他形式）分发给其他人时，您才必须发布 GPL 代码，并且您只有义务将其发布给您所分发的对象。您可以将 GPL 代码出售并发布给 Microsoft，而没有其他人 - 只有他们才拥有源代码的 GPL 权利，其他人都没有。当然，他们可以将其发布给任何他们喜欢的人。 GPLv3 还添加了一些有关软件即服务的内容。
如果你根本不想发布源代码，你到底为什么要称其为“开源”？如果您有专有代码，请使用普通的专有许可证。
You are under no obligation to automatically release GPL code.
You must release GPL code only if you are distributing the GPL code (in any form - compiled or otherwise) to others, and you are only obligated to release it to those you are distributing it to. You could have GPL code that you sold and released to Microsoft and no one else - only they would have GPL rights to the source code, no one else. They could release it to anyone they like, of course. GPLv3 adds in some stuff about software as a service, as well.
If you don't want to release the source at all, why on earth would you want to call it "open source"? Use a normal proprietary license if you've got proprietary code.