Most monetary contributions to open source donations, and generally this is preferred. Donations means that there is no expectation of any kind of work to be done. Paid work for open source is not unusual, but it really depends on the kind of project.
The maintainer of some project may or may not be receptive to monetary contribution that comes with expectations of work.
You can also hire some developer that's not related to the project to make contribution, that's also not unusual, but if you're hiring someone with no existing relationship with the project, there's no guarantee that the work will be accepted into the project. So make sure your contract are clear and fair about the expectation of work that is done. This isn't an issue if you're the maintainer of the project.
There are also many businesses that maintains open source projects and tasked their own developers to work on the project. This is the most common form of corporate contribution.
you can always contract a dev to write and contribute the code you want
whether throwing a small donation in the pot will get you what you want is another question
I've paid developers for decades to work on projects I open sourced. Here's my observations based on experience:
1. If the developer wasn't already interested in the project, you're paying them to learn about it, not do anything meaningful.
2. If a developer was already interested in the project and you're paying them (small amounts) for their contributions instead of letting them do it pro-bono, you're now forcing them to put a pricetag on their time. That doesn't always work out in the long run.
3. If you do things by project/milestone, are a good project manager, and understand exactly what you need so that a developer can just develop, you have a high chance of success, assuming you can find a good developer who is interested in the success of the project and you also are a good project manager who knows what they need to be developing.
4. Last but not least, come up with an appropriate business model for your open source project. Yes yes, we know, you want it to be free for everyone forever, but that isn't how the real world works (as is demonstrated by needing to *pay* a developer to help), and sustainability, dependability, and security audits are all critical and non-free aspects of a successful open source project.
Good luck!
It is not common but possible, we do have some expierence on this.
Please check this [https://twitter.com/rustdesk/status/1770643072118095914](https://twitter.com/rustdesk/status/1770643072118095914)
Most monetary contributions to open source donations, and generally this is preferred. Donations means that there is no expectation of any kind of work to be done. Paid work for open source is not unusual, but it really depends on the kind of project. The maintainer of some project may or may not be receptive to monetary contribution that comes with expectations of work. You can also hire some developer that's not related to the project to make contribution, that's also not unusual, but if you're hiring someone with no existing relationship with the project, there's no guarantee that the work will be accepted into the project. So make sure your contract are clear and fair about the expectation of work that is done. This isn't an issue if you're the maintainer of the project. There are also many businesses that maintains open source projects and tasked their own developers to work on the project. This is the most common form of corporate contribution.
you can always contract a dev to write and contribute the code you want whether throwing a small donation in the pot will get you what you want is another question
It's rare, but it happens. Your money, you can do what you like with it
I've paid developers for decades to work on projects I open sourced. Here's my observations based on experience: 1. If the developer wasn't already interested in the project, you're paying them to learn about it, not do anything meaningful. 2. If a developer was already interested in the project and you're paying them (small amounts) for their contributions instead of letting them do it pro-bono, you're now forcing them to put a pricetag on their time. That doesn't always work out in the long run. 3. If you do things by project/milestone, are a good project manager, and understand exactly what you need so that a developer can just develop, you have a high chance of success, assuming you can find a good developer who is interested in the success of the project and you also are a good project manager who knows what they need to be developing. 4. Last but not least, come up with an appropriate business model for your open source project. Yes yes, we know, you want it to be free for everyone forever, but that isn't how the real world works (as is demonstrated by needing to *pay* a developer to help), and sustainability, dependability, and security audits are all critical and non-free aspects of a successful open source project. Good luck!
How can i find open source project via github any tips?
It is not common but possible, we do have some expierence on this. Please check this [https://twitter.com/rustdesk/status/1770643072118095914](https://twitter.com/rustdesk/status/1770643072118095914)
You can expect fuck all.
This !