Slashdot Mirror
What Aspects of Open Source Projects Do You Avoid?
paulproteus writes "I'm a Debian developer and a part-time contributor to a few smaller projects. I do a lot of free software-y and open source-y things. Sometimes, though, I don't do them. I figure some other Slashdotters might have similar hang-ups — we contribute to a project, but there are parts that we really dread thinking about. So I wrote a post about having these hang-ups, and I made a place on the web to share how others can help your project. What are the parts that, in your projects, you would be relieved if someone else looked at for you?"
I steer clear of the BSD licenses when contributing.
For precisely the same reason you like it: there are no strings attached. Which means you can have my stuff without having to give anything back. I consider that such an arrangement effectively makes me an unpaid employee of your company, so I won't contribute anything significant under such terms.
I contribute under the GPL/AGPL because in such a case I do get something back: either somebody else's code, or money, if somebody wants a different license.
For the same reason, I preferentially use GPL licensed code. I might want to send a patch some day, but contributing something takes effort. I need to cleanup my code, figure out where to send it, perhaps discuss it on the mailing list with the project, and so on. That's quite a lot of boring work, so I expect to get something out of it.