Conversation
Notices
-
Ugh,worst part of !Conservancy job is staying semi-neutral on such issues: http://ur1.ca/9k6vx I hope !Boost Steering Committee DTRT in end
about a year ago from web-
@bkuhn speaking of #spin consider your revisionist description of the origins of #git !disturbing
-
@bkuhn Pro tip: these companies often offer FaiP proprietary licenses called "open source licenses" to FLOSS projects
-
@bkuhn Oh I see that you're talking about "open source licenses".
-
@fontana, I know such licenses are offered. As you saw, I call them "zero-cost proprietary licenses", but someone must be license recipient.
-
@bkuhn surely need not be corporate entity; why not require #Boost developers to be licensee? Why sully good name of #Conservancy?
-
@fontana, that part is clearly troll, but I'm happy to discuss this w/ you privately if you're serious. I have an unrelated ? for you anyway
-
@bkuhn IIRC Linus got fed up and started git when the BK license was revoked bc Tridge started developing wire-compatible software
-
@bkuhn http://ur1.ca/9k7t1 tells the story by Linus. The conflict was leading to a change, bk's license change sealed it http://ur1.ca/9k7tc
-
@lxoliva it wasn't even compatible, it was just competing
-
@tekk that project would be hg I think...
-
@tekk I'm pretty sure there were suspicious of reverse engineering for purposes of wire compatibility
-
@bkuhn: no, Git started after the Bitkeeper free-like-beer license was revoked (http://ur1.ca/9k9ew)
-
@bkuhn: And that happened after Tridge figured out the bitkeeper protocol (http://ur1.ca/9k9f0)
-
@bkuhn: Ok, fair enough. :)
-