Conversation
Notices
-
@fontana that's what they did with #mediagoblin.
about a year ago from web-
Mickos, Eucalyptus & CLAs "When somebody contributes to us we require them to sign over copyright but so does the FSF": http://wmk.me/k0AtOj
-
@webmink If the Eucalyptus agreement is the same as the FSF agreement, they should have no trouble using the FSF agreement, right?
Bradley M. Kuhn likes this. -
@webmink The FSF's CLA promises to always keep the software free. Most other CLA's don't. Not noting the difference is disingenuous.
Bradley M. Kuhn likes this. -
@j1mc While I agree with you, this is posted more for @bkuhn's benefit to support the suggestion I made that the FSF's CLA is #problematic
-
@webmink, I already wrote on this issue when @sabdfl tried to conflate !FSF ©AA w/ his. #Mickos is trying same trick: http://ur1.ca/l8c5
-
@j1mc, or,at the very least, #Eucalyptus should use the extra terms @rms proposed a while back. I'm quite sure #Mickos doesn't: ur1.ca/1ubir
-
@bkuhn As will others until the hostage to fortune is eliminated.
-
@webmink, I think your argument on this point (a) creates false dichotomy & (b) assumes developers are too dumb to evaluate different ©AAs.
-
@bkuhn So you're fine with folk being able to justify their abusive CAs by saying "we're just doing what FSF does"?
-
@webmink, I'm never "fine" when people lie & mislead. But I'm not going to tailor my actions & support based on what lies some might tell.
Clacke Moved to Parlementum likes this. -
@fontana, I've made my position that !FSF !copyright assignment should be optional clear to everyone, including FSF's management & @rms.
Mike Linksvayer and Osama Khalid like this. -
@copiesofcopies Willingly, I might add!
-