对于“正式化”，您可以考虑一个成熟的项目托管商，例如 Sourceforge 或 Google Code、github。一旦您的代码位于 SVN 或其他 VCS 存储库中，就会有一个与之关联的时间戳。如果您使用值得信赖的大型托管服务之一，这几乎可以最好地证明您的作者身份。
至于许可证：如果您不想重复使用代码，请使用 GNU GPL。如果您想允许并鼓励它，请使用 LGPL。如果您想收回捐款，请使用 AGPL。或者，如果您想要归属并传播高质量代码，请使用 MIT 或 BSD 风格的许可证。 但正如您已经提到的，WebCMS 非常丰富。所以无论如何，这不会有太大区别。
For "turning official" you might consider an established project hoster, like Sourceforge or Google Code, github. Once your code is in SVN or another VCS repository, there's a timestamp associated with it. If you use one of the trusted big hosting services, this pretty much establishes proof of your authorship best.
As for the license: use the GNU GPL if you don't want code reuse. Use the LGPL if you want to permit and encourage it. Use the AGPL if you want contributions back. Or use MIT or BSD-style licenses if you want attribution and to spread quality code instead. But as you already mentioned, there is an abundance of WebCMSes. So it won't make much of a difference anyway.
I was wondering to release it some under commercial license (I want money) but I realized that there's a saturation of CMS's on market.
So I think I'm going to release it under some open-source license.
You seem to be talking about "commercial" and "open-source" as if they're opposites. You do know there's such thing as "commercial open-source"?
what do I need to do to release it? To turn it official, so one cannot just "steal" it's code and say that created it.
Someone can ALWAYS steal your code if you release it (even if it's compiled they can theoretically reverse-engineer it - though it may not be practically feasible) - a licence just gives you the right to take legal action if someone does.
I read on a website that I just need to create a file called "license" and write the license there but what about the security?
This is really a legal question, and while Stack Overflow is good for programming questions, it's not really meant to give you legal advice. You should ask a lawyer.
That said, I am not a lawyer, but in the United States I've heard that you should submit your creation to the US Copyright Office. The real purpose of that is so that if you get sued (or want to sue someone) you can produce something that "proves" it's your creation. Under the Berne Convention your work is copyrighted the moment you create it, but the US courts still like to see some proof.
But again, this is pretty much only useful if someone takes you to court, or if you want to take someone to court. As a practical matter that may not even come up.
There is no way to "officiate" an open source project. If your license states that the user is allowed to redistribute or modify code, then they are free to do so. The idea behind open source is that the source code is visible to anyone who wishes to see it. Compiled or obfuscated code (without the original source) is not open source, it is simply proprietary code with exposed endpoints.
Consider which license you wish to implement; a good starting point is to look at other open source projects which have licenses that you can appreciate. For instance, Mozilla Firefox is licensed under the tri-license. Apache code is released under the Apache license. There are plenty of decent licenses that are available to choose from, and most of them have "Boilerplate" code which you place at the top of each file (stating that the file is under a given license).
While there is no open source means of enforcing a license, you can police the community and industry to ensure that your license's terms are not being violated. Should someone violate the terms of your license, you have the option to send a cease and desist notice or bring about legal action.
Licenses don't actually prevent someone from viewing/taking code - they just give you grounds to take legal measures against someone if they violate the terms of the license.
A license is official from the moment you specify that it's the license that applies to the code. The most common way of doing this is including a text file with the license as part of the download (and many of the common open-source licenses specifically refer to including the license with the code if any copies are made), but it's also just as valid if you specify a license on your website or such.
发布评论
评论（6）
对于“正式化”，您可以考虑一个成熟的项目托管商，例如 Sourceforge 或 Google Code、github。一旦您的代码位于 SVN 或其他 VCS 存储库中，就会有一个与之关联的时间戳。如果您使用值得信赖的大型托管服务之一，这几乎可以最好地证明您的作者身份。
至于许可证：如果您不想重复使用代码，请使用 GNU GPL。如果您想允许并鼓励它，请使用 LGPL。如果您想收回捐款，请使用 AGPL。或者，如果您想要归属并传播高质量代码，请使用 MIT 或 BSD 风格的许可证。
但正如您已经提到的，WebCMS 非常丰富。所以无论如何，这不会有太大区别。
For "turning official" you might consider an established project hoster, like Sourceforge or Google Code, github. Once your code is in SVN or another VCS repository, there's a timestamp associated with it. If you use one of the trusted big hosting services, this pretty much establishes proof of your authorship best.
As for the license: use the GNU GPL if you don't want code reuse. Use the LGPL if you want to permit and encourage it. Use the AGPL if you want contributions back. Or use MIT or BSD-style licenses if you want attribution and to spread quality code instead.
But as you already mentioned, there is an abundance of WebCMSes. So it won't make much of a difference anyway.
您似乎在谈论“商业”和“开源”，就好像它们是对立的一样。您知道有“商业开源”这样的东西吗？
如果您发布了您的代码，那么有人总是可以窃取您的代码（即使它已编译，理论上他们也可以对其进行逆向工程 - 尽管实际上可能不可行） - 许可证只是赋予您在有人这样做时采取法律行动的权利。
许可证为您提供法律保障。
You seem to be talking about "commercial" and "open-source" as if they're opposites. You do know there's such thing as "commercial open-source"?
Someone can ALWAYS steal your code if you release it (even if it's compiled they can theoretically reverse-engineer it - though it may not be practically feasible) - a licence just gives you the right to take legal action if someone does.
The licence gives you legal security.
看看 ExpressionEngine 是如何做到的。它们是基于 PHP 的商业 CMS。
Take a look at how ExpressionEngine does it. They're a PHP based commercial CMS.
这确实是一个法律问题，虽然 Stack Overflow 对于编程问题很有帮助，但它并不是真正为您提供法律建议。你应该问律师。
也就是说，我不是律师，但在美国，我听说您应该将您的创作提交给 美国版权局。这样做的真正目的是，如果您被起诉（或想起诉某人），您可以制作一些东西来“证明”这是您的创作。根据伯尔尼公约，你的作品在你创作的那一刻就受到版权保护，但美国法院仍然喜欢看看一些证据。
但同样，这几乎只有在有人将您告上法庭或您想将某人告上法庭时才有用。作为一个实际问题，甚至可能不会出现。
对其他国家/地区的建议可能有所不同。
This is really a legal question, and while Stack Overflow is good for programming questions, it's not really meant to give you legal advice. You should ask a lawyer.
That said, I am not a lawyer, but in the United States I've heard that you should submit your creation to the US Copyright Office. The real purpose of that is so that if you get sued (or want to sue someone) you can produce something that "proves" it's your creation. Under the Berne Convention your work is copyrighted the moment you create it, but the US courts still like to see some proof.
But again, this is pretty much only useful if someone takes you to court, or if you want to take someone to court. As a practical matter that may not even come up.
Advice for other countries may vary.
没有办法“主持”一个开源项目。如果您的许可证规定允许用户重新分发或修改代码，那么他们可以自由地这样做。开源背后的理念是源代码对任何希望查看它的人都是可见的。编译或混淆的代码（没有原始源代码）不是开源，它只是具有公开端点的专有代码。
考虑您希望实施哪种许可证；一个好的起点是查看其他拥有您可以欣赏的许可证的开源项目。例如，Mozilla Firefox 根据三重许可获得许可。 Apache 代码根据 Apache 许可证发布。有很多不错的许可证可供选择，并且大多数许可证都有“样板”代码，您可以将其放置在每个文件的顶部（表明该文件受给定许可证的约束）。
虽然没有强制执行许可证的开源方法，但您可以对社区和行业进行监管，以确保您的许可证条款不被违反。如果有人违反您的许可条款，您可以选择发送停止通知或采取法律行动。
希望这有帮助。
There is no way to "officiate" an open source project. If your license states that the user is allowed to redistribute or modify code, then they are free to do so. The idea behind open source is that the source code is visible to anyone who wishes to see it. Compiled or obfuscated code (without the original source) is not open source, it is simply proprietary code with exposed endpoints.
Consider which license you wish to implement; a good starting point is to look at other open source projects which have licenses that you can appreciate. For instance, Mozilla Firefox is licensed under the tri-license. Apache code is released under the Apache license. There are plenty of decent licenses that are available to choose from, and most of them have "Boilerplate" code which you place at the top of each file (stating that the file is under a given license).
While there is no open source means of enforcing a license, you can police the community and industry to ensure that your license's terms are not being violated. Should someone violate the terms of your license, you have the option to send a cease and desist notice or bring about legal action.
Hope this helps.
许可证实际上并不能阻止某人查看/获取代码 - 它们只是让您有理由对违反许可证条款的人采取法律措施。
从您指定该许可证适用于代码的那一刻起，许可证就是正式的。最常见的方法是在下载时包含一个带有许可证的文本文件（许多常见的开源许可证特别指的是在制作任何副本时将许可证包含在代码中），但这也只是如果您在网站等上指定了许可证，则该许可证有效。
Licenses don't actually prevent someone from viewing/taking code - they just give you grounds to take legal measures against someone if they violate the terms of the license.
A license is official from the moment you specify that it's the license that applies to the code. The most common way of doing this is including a text file with the license as part of the download (and many of the common open-source licenses specifically refer to including the license with the code if any copies are made), but it's also just as valid if you specify a license on your website or such.