How to write an open source development contract?

Question

open source

I'm trying to hire an R&D employee. The planned de facto activity would be best described as the activity of a science foundation, but our funds are modest, so there is no science foundation, but only an IP for me. And so I try to draw up a contract, I look at what others write in it.

The Author guarantees that he is the sole owner of the exclusive rights to the Works and will not transfer the exclusive rights to third parties

The Developer undertakes to create (including modify) and transfer to the Customer computer programs and/or databases (hereinafter referred to as the "Product" or "Products") with the simultaneous alienation of the exclusive right to such Products to the Customer in full, and the Customer undertakes to accept Products and the exclusive right to them and pay on the terms of this Agreement.

It's not about us at all. Purely hypothetically, I could take exclusive rights, and then license it to the community under the right license, but, it would seem, why such somersaults. It would be easier if the employee made the commits immediately publicly available under the required license, and I did not stand between him and the community, did not fence additional storage for code that was not checked for compliance with the TK. The license under which you need to publish the code is, from my philistine point of view, just a part of the TK, but I know that de jure, not any wording regarding code that has not yet been written is valid, so I don’t dare to formulate it myself, but examples of how to write, I can't find anything right now. I'm trying to search for a "standard open source agreement".

Answer 1

"Model open source contract"

How is that at all? 0_o
If you want to hire developers so that they can create software for you, then you conclude a regular employment contract with them, etc., and what you will then do with this code / software, the developer does not care at all.
If you want to have software “according to the canons of open source”, then cut v1, upload it, and if anyone is interested in it, they will get involved in the work, but in this case, everyone doesn’t give a damn about your contracts.
If you want to thank the developers for their work, with a modest amount for cookies, then the usual contract for one-time services.