|
From: Koichi S. <koi...@gm...> - 2012-07-21 02:00:29
|
As Mason suggested, I think it's safer to begin with non-commercial license. Commercial use can be licensed in case-by-case basis and we should license as long as the use helps XC. There could be many different commercial use and I'm not sure if the commercial license helps XC in many corner cases. Regards; ---------- Koichi Suzuki 2012/7/20 Joshua D. Drake <jd...@co...>: > > Hello, > > Alright just so this topic doesn't die, this is my recommendation. I > believe that the documentation and any "Official" community > documentation should be licensed under: > > http://creativecommons.org/licenses/by-sa/3.0/ > > This allows commercial use but enforces good commercial participation in > the community by requiring that modifications must be given back under > the same license. In this way, changes we want as part of the community > we can push back into the official docs at will. > > Sincerely, > > Joshua D. Drake > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |