新闻来源:http://blog.splayer.org/?p=1988
1. GPL并不禁止在项目中使用非GPL的组件（详见后文引注）。
2. 射手播放器没有准备移除任何模块。相反，为了做出一个好的表率，减少误解和争议，现在已完完全全提供所有源代码可供公众下载。
3. 射手播放器对于某些人士这种对开源项目的误解和打压技巧表示非常遗憾。
http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins
If a program released under the GPL uses plug-ins, what are the requirements for the licenses of a plug-in.
It depends on how the program invokes its plug-ins. If the program uses fork and exec to invoke plug-ins, then the plug-ins are separate programs, so the license for the main program makes no requirements for them.
If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means the plug-ins must be released under the GPL or a GPL-compatible free software license, and that the terms of the GPL must be followed when those plug-ins are distributed.
If the program dynamically links plug-ins, but the communication between them is limited to invoking the ‘main’ function of the plug-in with some options and waiting for it to return, that is a borderline case.
And also:
If I add a module to a GPL-covered program, do I have to use the GPL as the license for my module?
The GPL says that the whole combined program has to be released under the GPL. So your module has to be available for use under the GPL.
But you can give additional permission for the use of your code. You can, if you wish, release your program under a license which is more lax than the GPL but compatible with the GPL. The license list page gives a partial list of GPL-compatible licenses.
4. 不过对于开源和是否遵守开源协议能在国内引起这样的讨论我表示欣慰。希望籍此机会，让人们可以更多的了解开源，而使一些公司给开源更多的尊重。
5. 射手播放器会尽其所能坚持开放源代码这条道路。但是，即使射手播放器项目成功被灭杀，对的还是对的，错的还是错的。焦点可以转移，但事实是无法改变的。 | 
