On Sun, Jan 22, 2012 at 7:32 PM, Uli Schlachter <[email protected]> wrote: > [Lot's of guesswork here]
Indeed. > So anyone feels like asking gpl-violations.org for their input? > > IMHO this isn't a "big" violation. They are publishing everything, they just > added their own copyright/license header where there previously wasn't one at > all. Still, the default config should be covered by the GPL. Publishing code online hardly means anything. We need to be looking at ways to get Amazon involved with our community. And by knowing if and how Amazon violates GPL, we can _probably_ take step in that direction. For example, if GPL requires them to submit modifications (if any) back to the community we ask them to do so, and make sure they feel welcomed (which Uli is pretty good at :)). Immediate advantages of having Amazon on our side is that they can sponsor Awesome's development by hiring Uli and/or others or asking their developers to work 20% on Awesome. I own a Kindle, so in the long term I see the 'community' (Amazon included) evolving a system where I can configure my Kindle the way I configure my workstation (running Awesome). And even submit the modifications upstream for others to use. We could be collectively engineering the user interface of Kindle. Now imagine a generation of devices based on this same idea ... [more childlike vision of the world here :D]. I am thrilled. Amazon has a history of having build on open source but not contributing back. They know it. We know it. But as far as I know, they are trying to change that. Let's help them out. -- Anurag Priyam -- To unsubscribe, send mail to [email protected].
