3 ms·
Rule of thumb : If it makes you money, close source it. Otherwise, open source it. You only stand to benefit from getting feedback on your code.
by aantix 16y ago
Rule of thumb : If it makes you money, close source it. Otherwise, open source it.
You only stand to benefit from getting feedback on your code.
- deleted 16y ago[deleted]
- Titanous 16y agoThere are other benefits that come from building a community around an open source project. For example: Shopify open-sourced ActiveMerchant, a core component of our product. Even though our competitors use it, we still derive a lot of benefit from the community around it. Many of the gateway implementations that are used in Shopify were written by ActiveMerchant contributors. Every time someone implements a new gateway, we can add it to Shopify in a few minutes.
- weaksauce 16y agoWhat is the bar to get a payment processor included into Shopify? Do you test it rigorously or just look at the commit history of the project to see if it's up to snuff?
- Titanous 16y agoTo get into ActiveMerchant, it has to be clean code with passing unit and remote tests. We've got pretty much all of the gateways that North American businesses use, so to get a new gateway into Shopify it generally has to service a region that doesn't have good coverage with our current gateways.
- Twisol 16y agoI would agree with this, in general. My particular phrasing is to open-source platforms, not products. Platforms are general components with a wide variety of potential uses. Products are applied solutions for specific problems.