4 ms·

> Preemptive reply to "why don't you contribute to it?": We thought about donating to the project, but the amount of money we spend on professional EDA tools pe

by secure 10y ago

> Preemptive reply to "why don't you contribute to it?": We thought about donating to the project, but the amount of money we spend on professional EDA tools per year would only buy us about 10 day of KiCad developer time (or in-house developer time) – by far not enough to fix all show-stoppers. I’m not sure I follow. Are you saying you chose to not donate at all because you think your donation wouldn’t make any difference? In my experience, for many FOSS project standards, any contribution that can buy even a day of developer time would be considered huge. I’m sure KiCad would welcome any amount of donation :).

ZenoArrow 10y ago
No, that's not what was being said. The options on the table are: 1. Pay the licencing fees for proprietary software that already does what you want it to do. 2. Sponsor development of an open-source project so that it will eventually do what you want it to do. The argument being made is that, in the case of KiCad and this particular institution, option 1 was seen to be cheaper than option 2. In other words, it was deemed to be cheaper to pay the licence costs for the proprietary solution than it would be to pay a developer to make KiCad fit in with what they wanted.
shoo 10y ago
it sounds like they'd be happy donating some amount comparable to the cost of current tools if the donations would result in the project being made usable for them. it's not about it making a difference or not to the project, it's about it resulting in a sufficiently improved tool that they can use and get some ROI on
- kanzure 10y ago
  Solution is dominant assurance contracts, see https://en.wikipedia.org/wiki/Assurance_contract#Dominant_assurance_contracts https://en.wikipedia.org/wiki/Assurance_contract#Dominant_as...
  - ZenoArrow 10y ago
    How would that work in practice in this case? Note that the contract would most likely be with an individual developer, not the project itself.

by secure 10y ago

ZenoArrow 10y ago

No, that's not what was being said. The options on the table are: 1. Pay the licencing fees for proprietary software that already does what you want it to do. 2. Sponsor development of an open-source project so that it will eventually do what you want it to do. The argument being made is that, in the case of KiCad and this particular institution, option 1 was seen to be cheaper than option 2. In other words, it was deemed to be cheaper to pay the licence costs for the proprietary solution than it would be to pay a developer to make KiCad fit in with what they wanted.

shoo 10y ago

it sounds like they'd be happy donating some amount comparable to the cost of current tools if the donations would result in the project being made usable for them. it's not about it making a difference or not to the project, it's about it resulting in a sufficiently improved tool that they can use and get some ROI on

kanzure 10y ago
Solution is dominant assurance contracts, see https://en.wikipedia.org/wiki/Assurance_contract#Dominant_assurance_contracts https://en.wikipedia.org/wiki/Assurance_contract#Dominant_as...
- ZenoArrow 10y ago
  How would that work in practice in this case? Note that the contract would most likely be with an individual developer, not the project itself.