some Ideas I've had (Score 1)

Along the license lines; There are, of course, a variety of licenses available to choose from, if you so desire. I've been toying with the concept of some type of "retrograde" license, where the code would be release as open source after a certain date. E.g.: prior to the date of MM/DD/YYYY, the code of this project is licensed under XYZ license. If this date has been reached and or passed, this section of the retrograde licence may be omitted. Upon the date of MM/DD/YYYY and afterwards, the code for this project is provided under the GNU/... etc license. This, essentially would provide me with some time, (as specified by the date of conversion ot OpenSourcing), for me to do with the code things I wish to do. For instance, if I thought the code/project was good enough, I could make a go of selling it, though people could opt to wait to get it for free after the date that it became open-sourced... Just one idea I've been kicking around, feedback is welcome, please keep flames on "Low" :-) Another (better, in my opinion) idea I've had recently: A platform specific license, specifying that the software is free and open-sourced for use on Linux systems, but reasonably priced and closed source for Windows(tm) systems. -Note I've not really considered which way to go with 'Mac'-systems. -Also note, as for Win/Linux dual or multi booting systems, the licence applies to whichever OS the code is being run within. Hope some of this may be useful. Thanks to all offering constructive feedback/criticisms. by the by, I've not really researched the various licensing schemes available, so if these ideas aren't really that novel, then please forgive my ignorance. -S-