Timeline for How to evaluate codebase
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8 at 2:12 | comment | added | Pete W | I have tried to do precisely this in the past for the same reason. The key thing for readers, is to maintain a crystal-clear division between the application code and the system code. /// An additional consideration is that the immediate client might be fine with a non-copyleft open source license like BSD, but then one day 5 years later they sell their company, and their buyer is a giant corporate with a no-open-source policy (yes it's a thing), and suddenly there's a conflict and it's tempting for them to forget they ever agreed to anything with you. | |
| Jan 22 at 16:02 | vote | accept | aryeh | ||
| Jan 21 at 15:17 | comment | added | David R | The point is to get the client to agree that I get to use parts of the code elsewhere. There are clients who insist on full ownership of all code meaning that you have to start with a blank sheet and develop everything from scratch for them. Yes, that increases their cost. | |
| Jan 20 at 21:53 | comment | added | aryeh | So you're saying I can't charge for the codebase, but should ensure to exclude modules I can reuse for other projects? | |
| Jan 19 at 15:57 | history | answered | David R | CC BY-SA 4.0 |