at what point does the flexibility and cost savings of implementing an open source solution get drowned out by the headache of maintainence and the creep of calls for constantly expanding functionality?
Firstly, what maintenance? All the FOSS software I use just works - I certainly don't maintain it, any more than I maintain proprietory software. Of course, If I do spot a bug I'll report it and even try to fix it, but I don't have to do this.
Secondly, what calls for expanding functionality? You should only consider a FOSS solution if it meets all your needs. Once installed, you should no more consider expanding its functionality than you would for a proprietory solution, unless you want to, of course.
In a lot of work-places all they really want is someone they can call up to fix problems if they arise, if you look at http://trac.edgewall.org/wiki/CommercialServices, you'll see there are a few companies who offer commercial support for Trac so that may help swing things that way.
现在，如果这是您自己的初创公司，那么开源就会很有意义。如果公司对开源非常满意，那么这也可能是有意义的。然而，听起来似乎并非如此，而且您正在为自己的开源带来麻烦。如果出现任何问题（并且可能与开源无关），那么人们会指着你说“这是一个开源解决方案”。关键词是 CYA——Cover Your Ass。
The question has to be answered in the context of your company's culture, background, development environment etc.
Are they familiar with and comfortable with Open Source?
Are they using Microsoft technology or Java?
Are you paying for the software out of your salary or is the company going to pay for it? :)
Is your immediate manager paying for the software out of his salary? :)
How much credit will your company give you for saving them some money?
How much flak will you get if an open source solution fails?
*** I think if you meditate on the last 2 points, go ahead and spend the money for a better supported solution. If they are a Microsoft shop, just go with their bug tracking system. If not, go with something like FogBuz. If it is a bank, go with Remedy.
Now, if it was your own startup, then open source would make a lot of sense. If the company is very comfortable with open source, it might also make sense. However, it sounds like they aren't and that you are setting yourself up for trouble going with open source. If anything goes wrong (and it may have nothing to do with it being open source) then fingers will be pointed at you saying "it was an open source solution". The operative phrase is CYA - Cover Your Ass.
This is to some extent a string-lenght question, but here are my random thoughts:
Just because a piece of software is commercial and backed-up by a support organization, it isn't hassle-free to install and set up.
Compare the licensing cost with the time needed to set up (and maintain) an open-source solution. Will the open-alternative be functional in a day, week or month?
The problem with scope creep is really a management problem.
If you aren't really sure what you need, trying out an open alternative first is a great way of building experience in what functionality is essential to your organization.
I also like Trac (I'm using it for a hobby project with a couple of friends) but I think FogBugz and several other commercial PM/bug tracking software packages are probably better. If management is willing to pay for a commercial solution, where's the problem?
发布评论
评论（5）
你问：
首先，什么保养？我使用的所有自由和开源软件都可以正常工作 - 我当然不会维护它，就像我维护专有软件一样。当然，如果我确实发现了错误，我会报告它，甚至尝试修复它，但我没有这样做。
其次，什么需要扩展功能？只有当 FOSS 解决方案满足您的所有需求时，您才应该考虑它。安装后，您不应该像扩展专有解决方案那样考虑扩展其功能，当然，除非您愿意。
You ask:
Firstly, what maintenance? All the FOSS software I use just works - I certainly don't maintain it, any more than I maintain proprietory software. Of course, If I do spot a bug I'll report it and even try to fix it, but I don't have to do this.
Secondly, what calls for expanding functionality? You should only consider a FOSS solution if it meets all your needs. Once installed, you should no more consider expanding its functionality than you would for a proprietory solution, unless you want to, of course.
在很多工作场所，他们真正想要的是在出现问题时可以打电话来解决问题的人，如果你看看 http://trac.edgewall.org/wiki/CommercialServices，您会看到有一些公司为 Trac 提供商业支持，因此可能有助于扭转局面。
In a lot of work-places all they really want is someone they can call up to fix problems if they arise, if you look at http://trac.edgewall.org/wiki/CommercialServices, you'll see there are a few companies who offer commercial support for Trac so that may help swing things that way.
这个问题必须结合贵公司的文化、背景、开发环境等来回答。
他们是否熟悉并适应开源？
他们使用 Microsoft 技术还是 Java 技术？
您是用工资支付软件费用还是公司支付费用？ :)
您的直属经理是否从他的工资中支付该软件的费用？ :)
你的公司会给你多少信用来为他们节省一些钱？
如果开源解决方案失败，你会受到多少批评？
*** 我认为，如果您考虑了最后两点，请继续花钱购买更好的支持解决方案。如果他们是微软商店，就使用他们的错误跟踪系统。如果没有，请使用 FogBuz 之类的工具。如果是银行，请选择 Remedy。
现在，如果这是您自己的初创公司，那么开源就会很有意义。如果公司对开源非常满意，那么这也可能是有意义的。然而，听起来似乎并非如此，而且您正在为自己的开源带来麻烦。如果出现任何问题（并且可能与开源无关），那么人们会指着你说“这是一个开源解决方案”。关键词是 CYA——Cover Your Ass。
The question has to be answered in the context of your company's culture, background, development environment etc.
Are they familiar with and comfortable with Open Source?
Are they using Microsoft technology or Java?
Are you paying for the software out of your salary or is the company going to pay for it? :)
Is your immediate manager paying for the software out of his salary? :)
How much credit will your company give you for saving them some money?
How much flak will you get if an open source solution fails?
*** I think if you meditate on the last 2 points, go ahead and spend the money for a better supported solution. If they are a Microsoft shop, just go with their bug tracking system. If not, go with something like FogBuz. If it is a bank, go with Remedy.
Now, if it was your own startup, then open source would make a lot of sense. If the company is very comfortable with open source, it might also make sense. However, it sounds like they aren't and that you are setting yourself up for trouble going with open source. If anything goes wrong (and it may have nothing to do with it being open source) then fingers will be pointed at you saying "it was an open source solution". The operative phrase is CYA - Cover Your Ass.
这在某种程度上是一个字符串长度的问题，但以下是我的随机想法：
仅仅因为一个软件是商业的并且由支持组织支持，所以安装和设置并不轻松。
将许可成本与设置（和维护）开源解决方案所需的时间进行比较。开放替代方案会在一天、一周或一个月内发挥作用吗？
范围蔓延问题实际上是一个管理问题。
如果您不太确定自己需要什么，首先尝试一个开放的替代方案是积累经验的好方法，了解哪些功能对您的组织至关重要。
This is to some extent a string-lenght question, but here are my random thoughts:
Just because a piece of software is commercial and backed-up by a support organization, it isn't hassle-free to install and set up.
Compare the licensing cost with the time needed to set up (and maintain) an open-source solution. Will the open-alternative be functional in a day, week or month?
The problem with scope creep is really a management problem.
If you aren't really sure what you need, trying out an open alternative first is a great way of building experience in what functionality is essential to your organization.
我也喜欢 Trac（我和几个朋友将它用于一个业余爱好项目），但我认为 FogBugz 和其他几个商业 PM/bug 跟踪软件包可能更好。如果管理层愿意为商业解决方案付费，那么问题出在哪里？
I also like Trac (I'm using it for a hobby project with a couple of friends) but I think FogBugz and several other commercial PM/bug tracking software packages are probably better. If management is willing to pay for a commercial solution, where's the problem?