Timeline for Will Open Sourcing Stack Overflow Destroy Our Business Model?
Current License: CC BY-SA 2.5
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 13, 2009 at 10:05 | comment | added | cas | one correction about Dual Licensing - the second license shouldn't be BSD or any other FOSS license...that would defeat the purpose of Dual Licensing. The second license should be whatever commercial/proprietary license makes most sense to you. For example: Affero GPL for the FOSS license A proprietary binary and source-code license for $$$ for those who want to be able to change the code on their sites without having to contribute their changes back. | |
Jul 8, 2009 at 2:40 | comment | added | Steve Klabnik | You seem to be under the impression that the StackOverflow team would be required to accept any patches that are given to them, and this just simply isn't the case. Nobody is "dropping into a live community." I'm quite sure that the SO team can evaluate the value of contributions before they deploy. And as far as 'not delivered on', do you forget where you are? The old UserVoice had almost 2,000 ideas that were implemented by the team. Are you suggesting that SO is perfect, that there's nothing left to add? | |
Jul 8, 2009 at 1:04 | comment | added | Jay Stevens | What have @codinghorror and company not delivered on? What feature-set is so blatantly missing that SO needs an army of "free developers" to implement it? Not much is there? So much for the "free labor argument". | |
Jul 8, 2009 at 1:02 | comment | added | Jay Stevens | The problem, in this case, with the "free labor" argument, is that this is community software. As Jeff and others (who have done anything more than just use a phpBB out of the box) know, social software is organic and highly unpredictable. Something that "looks" like a reasonable "enhancement" to the functionality of the software can (and likely will) have dramatic and unforeseen effects when it's dropped into a live community. A "robust community" of contributing developers can actually do more harm than good if not highly constrained. | |
Jul 7, 2009 at 17:30 | history | answered | Steve Klabnik | CC BY-SA 2.5 |