My understanding of Open Source is that whatever it is (IT product, toy, artwork, literature etc) is almost always produced to meet a specific purpose or illustrate a concept/theory/fantasy. It is what happens at that point that determines if it is Proprietary or Open Source.
With Open Source works, the steps to the solution, (in IT this is the code) and the conceptual development are available for anyone else to use/adapt/change and put to any purpose they wish. (Including producing proprietary products for sale. Staying with IT; proprietary developers don't have to allow others to use their modification code when building new products based on Open Source code)
So you are envisioning bounties whereby the distribution does not take place via some community site but one might, for example, do the work on the server of someone requesting the work and thereby not releasing the code to the general public?
If this is the case then that happens daily in the hard cash world and it is hard to see what the advantages would be for a programmer to jump through all the hoops and risk of getting paid in DVC when the world works like that already.
As a writer that means the work I declare Open Source and publish on Devtome can even be used on someone else's commercially purchased birthday card as long as they credit my work. *Digression warning.. That is a cool idea really..that would be like a little random happy birthday from me to a complete stranger
I should write some birthday poems.
To bother to put an Open Source copyright on literature, of any kind, seems redundant to me when Public Domain fits just as well. It seems to cloud the issue and mandate of this project. The cookbook was a cute example of a piece of, potentially, algorythmic literature (as
any how to would be) yet public domain covers it. This is because different copyright laws apply to literature than software. One can quote certain percentages of literature without breaking a copyright so one could take supposed Open Sourced literature, quote much larger sections if one wanted, bring in your own comments and then make the entire piece proprietary. This cannot be done with Open Source code.
It is like the discussion earlier on this thread about Open Sourced music. It does not work because someone can make changes and not continue the Open Source but move it into proprietary status. The same would work for supposedly Open Sourced literature.
Either way, the code is out there for someone else to use.
You are giving me a mixed messages. Is the finished bounties to be out there for everyone or only if those putting up the bounties decide to release it? This is sounding worse than my original assumptions.
- Nova
it is at 
