Since you are not going to accept pushes you might as well hold on get your code stable and then publish it for others to learn and benefit from. You are still building the service, so its not going to attract too many eyeballs either.
From a business point of you, you might want to have a reasonable community around your service before you opensource it. if you are still budding who knows if its taken up by a stronger competitor. If your idea is patented its a different story.
To be honest, and this is not likely going to be a popular answer, but to myself, I would keep it closed for a period of time.
The reasons for this are simple, establish your foothold in the marketplace, build your userbase, your brand, then it gives you a mechanism to market your product further by selectively or completely open sourcing components of your system.
I say do it for both personal benefit and potential strategic benefit ... afterall, alot of software IS a service
Most open-source projects stand to provide a return in the right circumstances. Don't forget, unless you have a patent or some massive advance that is so complex and unfathomable that nobody can re-implement it .. if they want to they will anyway, so you have little protection staying closed source anyway ... even more interesting is that the open-source equivalent may well overtake your proprietary one if it garners support.
People may send you great ideas you never thought of, or take your codebase in a direction you would not have predicted. Unless you have significant value in terms of IP or strategic position tied up in the source code ... releasing it will probably do more good than harm.
Also, by being first to the open-source arena with your code, you gain control over any resulting community driven development ... if somone reimplemented your functionality and went open source ... could you compete on any front?
I know it is a cliche, but probably for good reason, but read The Cathedral and the Bazaar and the essay Open Source as a Signalling Device - An Economic Analysis which is an interesting read. Michael E. Porter's texts on competition analysis are interesting when held up against the mixed value economics and competitive forces of open source and shows how disruptive open-sourcing a product can be to competitors ... and how it can add value to your market position. Also, whilst counterintuative, it can raise the barriers to a successful entry by competitors.
More food for thought on the advantages and disadvantages of open sourcing:
I like to fix flaws wherever I see them, and perhaps I am one of your users. I'd rather send a patch than send a potentially nagging-sounding email any day.
What benefit are you hoping to gain from making the code open source? If you don't want the input of other developers then there are very few advantages and a whole lot of potential disadvantages.
发布评论
评论（5）
既然您不打算接受推送，那么您不妨先保持代码稳定，然后发布它以供其他人学习和受益。您仍在构建该服务，因此它也不会吸引太多眼球。
从您的业务角度来看，您可能希望在开源之前围绕您的服务建立一个合理的社区。如果你仍处于萌芽阶段，谁知道它是否会被更强大的竞争对手占据。如果你的想法获得了专利，那就另当别论了。
Since you are not going to accept pushes you might as well hold on get your code stable and then publish it for others to learn and benefit from. You are still building the service, so its not going to attract too many eyeballs either.
From a business point of you, you might want to have a reasonable community around your service before you opensource it. if you are still budding who knows if its taken up by a stronger competitor. If your idea is patented its a different story.
老实说，这不太可能成为一个受欢迎的答案，但对我自己来说，我会把它关闭一段时间。
原因很简单，在市场上站稳脚跟，建立你的用户群，你的品牌，然后它为你提供了一种机制，通过选择性或完全开源系统组件来进一步营销你的产品。
To be honest, and this is not likely going to be a popular answer, but to myself, I would keep it closed for a period of time.
The reasons for this are simple, establish your foothold in the marketplace, build your userbase, your brand, then it gives you a mechanism to market your product further by selectively or completely open sourcing components of your system.
我说这样做是为了个人利益和潜在的战略利益......毕竟，很多软件都是一种服务
大多数开源项目都会在适当的情况下提供回报 >。不要忘记，除非您拥有专利或某些如此复杂且深不可测的巨大进步，以至于没有人可以重新实现它..如果他们愿意，他们无论如何都会，所以您几乎没有什么保护无论如何，闭源...更有趣的是，如果开源同等产品获得支持，它很可能会超越您的专有产品。
人们可能会向您发送您从未想过的好主意，或者将您的代码库引向您无法预测的方向。除非您在知识产权或与源代码相关的战略地位方面具有重大价值......发布它可能利大于弊。
此外，通过率先使用您的代码进入开源领域，您可以控制任何由此产生的社区驱动的开发……如果有人重新实现您的功能并开源……您可以在任何方面进行竞争吗？
我知道这是陈词滥调，但可能有充分的理由，但请阅读大教堂和集市 以及文章开源作为信号设备 - 经济分析< /a> 这是一本有趣的读物。 Michael E. Porter 的关于竞争分析的文本在面对混合价值经济学和竞争时很有趣开源的力量，并展示了开源产品对竞争对手的颠覆性……以及它如何为您的市场地位增加价值。此外，虽然违反直觉，但它可能会增加竞争对手成功进入的障碍。
关于开源的优点和缺点的更多思考：
I say do it for both personal benefit and potential strategic benefit ... afterall, alot of software IS a service
Most open-source projects stand to provide a return in the right circumstances. Don't forget, unless you have a patent or some massive advance that is so complex and unfathomable that nobody can re-implement it .. if they want to they will anyway, so you have little protection staying closed source anyway ... even more interesting is that the open-source equivalent may well overtake your proprietary one if it garners support.
People may send you great ideas you never thought of, or take your codebase in a direction you would not have predicted. Unless you have significant value in terms of IP or strategic position tied up in the source code ... releasing it will probably do more good than harm.
Also, by being first to the open-source arena with your code, you gain control over any resulting community driven development ... if somone reimplemented your functionality and went open source ... could you compete on any front?
I know it is a cliche, but probably for good reason, but read The Cathedral and the Bazaar and the essay Open Source as a Signalling Device - An Economic Analysis which is an interesting read. Michael E. Porter's texts on competition analysis are interesting when held up against the mixed value economics and competitive forces of open source and shows how disruptive open-sourcing a product can be to competitors ... and how it can add value to your market position. Also, whilst counterintuative, it can raise the barriers to a successful entry by competitors.
More food for thought on the advantages and disadvantages of open sourcing:
我喜欢修复任何看到的缺陷，也许我是你们的用户之一。我宁愿发送补丁，也不愿每天发送一封可能听起来很烦人的电子邮件。
I like to fix flaws wherever I see them, and perhaps I am one of your users. I'd rather send a patch than send a potentially nagging-sounding email any day.
您希望通过开源代码获得什么好处？如果您不需要其他开发人员的意见，那么优势就很少，而潜在的劣势却很多。
What benefit are you hoping to gain from making the code open source? If you don't want the input of other developers then there are very few advantages and a whole lot of potential disadvantages.