Community Wiki
I've been working on a fairly large project www.wikipediamaze.com and I initially intended for it to be open source, but as I get closer and closer to "done" I'm getting more and more nervous about releasing the code.
我一直在研究一个相当大的项目www.wikipediamaze.com,我最初打算将它作为开源的,但随着我越来越接近“完成”,我越来越担心发布代码。
Initially I had hoped to use the project as sort of a "resume", if you will, as well as a learning tool for myself and others that I could blog about. And of course making a buck or two off of ads wouldn't be a bad thing either.
最初我曾希望将项目用作“简历”,如果你愿意的话,以及我自己和其他人可以写博客的学习工具。当然,制作广告或两次广告也不是件坏事。
However, after dedicating my life to it for the last few months I'm really concerned about releasing the product as open source before I've reached "Critical Mass". Do I really want to risk putting it out there for someone to rip off the code and put up a competing product that does a better job of SEO and pretty much runs me out of the market? Is there anything I can do to protect myself from this aside from not releasing the code?
然而,在我过去几个月献出生命之后,我真的很担心在我达到“临界质量”之前将产品作为开源发布。我是否真的想冒险将它放在那里,以便有人扯掉代码并提出一个更好的搜索引擎优化的竞争产品,几乎把我带出市场?除了不释放代码之外,我还能做些什么来保护自己免受这种伤害?
There are already competing products out there, but I've put a slightly different spin on it that I think will help make it successful. I'm just afraid I will shoot myself in the foot by releasing it to early.
已经存在竞争产品,但我对其进行了略微不同的调整,我认为这将有助于使其成功。我只是害怕我会在早期将它自己射入脚中。
Any thoughts or suggestions?
有什么想法或建议吗?
BTW the project was built using ASP.Net MVC, C#, Fluent NHibernate and Linq 2 NHibernate, Sql Server 2008, RPX Now (open id / OAuth), and twitter amongst other things.
BTW该项目是使用ASP.Net MVC,C#,Fluent NHibernate和Linq 2 NHibernate,Sql Server 2008,RPX Now(open id / OAuth)和twitter等构建的。
3 个解决方案
#1
Michael,
In my opinion these are the reasons that you might open source a project:
在我看来,这些是您可能开源项目的原因:
- The project is a light version. You offer the pro version for a fee on your site.
- The project can be used as a library in someone else project. You want to show good will towards other developers.
- The project uses cutting edge technology and you want other developers to learn from what you are doing.
- You want to do top of mind marketing. By making something open source and distributing through codeplex and robosoft; it might bring people to your site to click on ads.
- You are single and have a lot of time on your hands. You want to support your open source product and add features because you are very bored.
- The project is based on several open source projects and the licensing prevents you from releasing it as a commercial product.
该项目是一个轻型版本。您在自己的网站上提供专业版的收费版。
该项目可以用作其他项目中的库。你想向其他开发者表现出良好的意愿。
该项目使用尖端技术,您希望其他开发人员从您正在做的事情中学习。
你想做头脑营销。通过开源并通过codeplex和robosoft进行分发;它可能会让人们到您的网站点击广告。
你是单身,手上有很多时间。您希望支持您的开源产品并添加功能,因为您非常无聊。
该项目基于几个开源项目,许可证阻止您将其作为商业产品发布。
With those tenants above, I think that unless 3, 4, or 5 apply I would release it as a commercial.
对于上面的那些租户,我认为除非适用3,4或5,否则我会将其作为商业广告发布。
#2
If you do consider releasing it as Open Source, you probably will want to go with a GNU public license. That will drive away most corporations from using the code and anyone who uses your code will also have to use the GPL, so you can always integrate what they've done into your product.
如果你考虑将它作为开源发布,你可能会想要使用GNU公共许可证。这将驱逐大多数公司使用代码,并且任何使用您的代码的人也必须使用GPL,因此您始终可以将他们已经完成的工作集成到您的产品中。
That said, you should still consider registering for a copyright. That way anyone (like a potential employer) who asks "Is this really your code" will be able to receive proof that yes, it really is your code.
也就是说,您仍应考虑注册版权。这样任何人(比如潜在的雇主)都会问“这真的是你的代码”将能够得到肯定的证据,这真的是你的代码。
#3
I would definitely suggest going open source. People are going to copy your features whether you release the code or not.
我肯定会建议开源。无论您是否发布代码,人们都会复制您的功能。
If you do open source it, I would suggest using the AGPL (Affero GPL). This will prevent people from taking the code, making modifications and not releasing the code by not distributing it and just running it on there own servers.
如果你开源,我会建议使用AGPL(Affero GPL)。这将阻止人们获取代码,进行修改而不释放代码,方法是不分发代码并仅在自己的服务器上运行代码。
By the way, cool site. It's sort of like WikiFighting though.
顺便说一句,很酷的网站。这有点像WikiFighting。
#1
Michael,
In my opinion these are the reasons that you might open source a project:
在我看来,这些是您可能开源项目的原因:
- The project is a light version. You offer the pro version for a fee on your site.
- The project can be used as a library in someone else project. You want to show good will towards other developers.
- The project uses cutting edge technology and you want other developers to learn from what you are doing.
- You want to do top of mind marketing. By making something open source and distributing through codeplex and robosoft; it might bring people to your site to click on ads.
- You are single and have a lot of time on your hands. You want to support your open source product and add features because you are very bored.
- The project is based on several open source projects and the licensing prevents you from releasing it as a commercial product.
该项目是一个轻型版本。您在自己的网站上提供专业版的收费版。
该项目可以用作其他项目中的库。你想向其他开发者表现出良好的意愿。
该项目使用尖端技术,您希望其他开发人员从您正在做的事情中学习。
你想做头脑营销。通过开源并通过codeplex和robosoft进行分发;它可能会让人们到您的网站点击广告。
你是单身,手上有很多时间。您希望支持您的开源产品并添加功能,因为您非常无聊。
该项目基于几个开源项目,许可证阻止您将其作为商业产品发布。
With those tenants above, I think that unless 3, 4, or 5 apply I would release it as a commercial.
对于上面的那些租户,我认为除非适用3,4或5,否则我会将其作为商业广告发布。
#2
If you do consider releasing it as Open Source, you probably will want to go with a GNU public license. That will drive away most corporations from using the code and anyone who uses your code will also have to use the GPL, so you can always integrate what they've done into your product.
如果你考虑将它作为开源发布,你可能会想要使用GNU公共许可证。这将驱逐大多数公司使用代码,并且任何使用您的代码的人也必须使用GPL,因此您始终可以将他们已经完成的工作集成到您的产品中。
That said, you should still consider registering for a copyright. That way anyone (like a potential employer) who asks "Is this really your code" will be able to receive proof that yes, it really is your code.
也就是说,您仍应考虑注册版权。这样任何人(比如潜在的雇主)都会问“这真的是你的代码”将能够得到肯定的证据,这真的是你的代码。
#3
I would definitely suggest going open source. People are going to copy your features whether you release the code or not.
我肯定会建议开源。无论您是否发布代码,人们都会复制您的功能。
If you do open source it, I would suggest using the AGPL (Affero GPL). This will prevent people from taking the code, making modifications and not releasing the code by not distributing it and just running it on there own servers.
如果你开源,我会建议使用AGPL(Affero GPL)。这将阻止人们获取代码,进行修改而不释放代码,方法是不分发代码并仅在自己的服务器上运行代码。
By the way, cool site. It's sort of like WikiFighting though.
顺便说一句,很酷的网站。这有点像WikiFighting。