3 ms·
It is a smaller scale project, in the sense that it is not worth setting up a foundation of that scale due to the overhead. We would like to support the develo
by moeadham 12y ago
It is a smaller scale project, in the sense that it is not worth setting up a foundation of that scale due to the overhead.
We would like to support the developers, but it becomes complicated due to invention assignments when we take them on as contractors. We would also like to have it where more than one company can contribute, as a number of other startups are interested in participating, which makes contractor agreements complicated.
We will have a look at bounty source. It is simply because we would prefer to have these as accounting donations (not necessarily charitable), but that becomes difficult, as you have to donate to something.
- jonafato 12y agoRegarding assignment, you're not required to have a work for hire agreement in place, and if you do, there's nothing stopping you from releasing code that you own and paid for under the open source license of the project. Take a look at Django's contributor license agreement (https://www.djangoproject.com/foundation/cla/ https://www.djangoproject.com/foundation/cla/) as well, as it may be a useful construct in your work. Gratipay may make sense here if you're looking to fund general development toward a specific contributor, where as BountySource is a more feature-specific. If you do decide to go the non-profit organization route, your contributions now will be deductible if / when 501(c)(3) status is granted (http://www.irs.gov/Charities-&-Non-Profits/Charitable-Organizations/Contributions-to-Organization-with-IRS-Application-Pending http://www.irs.gov/Charities-&-Non-Profits/Charitable-Organi...). Either way, your best bet is probably to reach out to the developer behind the project to discuss the details.