3 ms·

> he told me that he believed the person staying should own everything that was created That speaks volumes. He had absolutely no skin in the game, and didn't

> he told me that he believed the person staying should own everything that was created That speaks volumes. He had absolutely no skin in the game, and didn't have any actual work to do to make the platform a reality. Why would HE ever leave? It is pretty much a guarantee that if you got tired of doing the project, he would still own the rights to everything. IANAL, but I watch a crap ton of Judge Judy... You are, right now, through this post, admitting that you had this discussion and that was the outcome and your continuation of work was "in agreement to his terms". The dumbest thing you could do in a situation like this is document that you guys had agreed to something like that. You NEED a lawyer, and this post might have done some damage.

davinciceb 8y ago
Thanks for the advice! I want to clear up something here that I might have not made clear in the original post... Neither of us actually agreed to that condition, it was something he brought up when we were going over the founders agreement section about one founder leaving before a company is formed. I was explaining to him what mutual separation of assets meant, and he told me that he thought the person leaving should give the person staying rights to everything. We ended up disagreeing on this, and we left it in the founders agreement as "mutual separation of assets". So to be clear, I never agreed to work under those terms, and he never brought it up again, because we both saw a lot of issues with that. I just wanted to bring it up because I wanted to know what others thought.
- matt_the_bass 8y ago
  So did you guys ever say the person leaving couldn’t also use the code? If not then both of you could use your own copies. If he’s not a dev, what’s he really going to do with it? With all due respect, I’d be willing to bet that the codebase has close to little value. But your know how and knowledge of the problem/domai does. Worst case, now that you know how to do what you already did, could t you do it over better and faster?

davinciceb 8y ago

Thanks for the advice! I want to clear up something here that I might have not made clear in the original post... Neither of us actually agreed to that condition, it was something he brought up when we were going over the founders agreement section about one founder leaving before a company is formed. I was explaining to him what mutual separation of assets meant, and he told me that he thought the person leaving should give the person staying rights to everything. We ended up disagreeing on this, and we left it in the founders agreement as "mutual separation of assets". So to be clear, I never agreed to work under those terms, and he never brought it up again, because we both saw a lot of issues with that. I just wanted to bring it up because I wanted to know what others thought.

matt_the_bass 8y ago
So did you guys ever say the person leaving couldn’t also use the code? If not then both of you could use your own copies. If he’s not a dev, what’s he really going to do with it? With all due respect, I’d be willing to bet that the codebase has close to little value. But your know how and knowledge of the problem/domai does. Worst case, now that you know how to do what you already did, could t you do it over better and faster?