Much of the discussion in this thread has highlighted the difference between those who regard open source as a community and public good, and those who regard it as a resource to be exploited. The latter sees anything beyond legalistic compliance as an unreasonable expectation. Personally I'm disappointed with the exploitation view, but I also think it's an interesting example of how different assumptions lead groups…
AWS forked my project and launched it as its own service
251–260 of 673 posts
Re: AWS forked my project and launched it as its own service
#252Earlier quoted context omitted.
If I suggest an idea from a coworker in a meeting as if it was mine, that move would be seen, at the very least, as somewhat rude. If I got that idea from examining the competition, that would be seen as a smart move. Sure, if attribution is a requirement then the natural thing to do is to turn it into a legal requirement . But I don't think that is the discussion here. It comes down to how we want to treat open sour…
> If I suggest an idea from a coworker in a meeting as if it was mine, that move would be seen, at the very least, as somewhat rude. It will be lot more rude if your coworker now hit social media berating you for stealing other people's ideas. If just office ideas were this important may be they need to be submitted with process of academic journals with proper attribution. It can't be both ways: "Announcing that tak…
Would it? I’d be inclined to agree with the coworker.
The message is not ‘stealing other people’s ideas’, it’s ‘stealing other people’s ideas without acknowledgement’.
Re: AWS forked my project and launched it as its own service
#253There are some replies in this thread that misunderstood the content of Tim Nolet's twitter post. (Probably because the short headline has pitchfork raising overtones.) - He's not complaining that Amazon forked his code with Apache license. He admits he also uses other open source with permissive licenses - He just thought it would be nice/courteous/polite/etc if Amazon acknowledge/recognized/credited/mentioned/thank…
If you read further down the Twitter thread you’ll see others point out that AWS actually DID acknowledge him in the release and thus his original rant isn’t accurate. He acknowledges that later in the thread. Of course the, now inaccurate, headline Tweet remains the thing getting attention.
Re: AWS forked my project and launched it as its own service
#254> Oh @awscloud I really do :Two hearts: you! But next time you fork my OS project https://github.com/checkly/headless-recorder and present it as your new service, give the maintainers a short "nice job, kids" or something. Not necessary as per the APLv2 license, but still, ya know? He is only nicely and asking for recognition/attribution while acknowledging that it's not required per licence. I don't know why people…
Are those on this forum not similarly free to express their judgment?
Re: AWS forked my project and launched it as its own service
#255Earlier quoted context omitted.
I think it comes back to politeness, somewhere in amazon there is product manager that saw or was shown Tim's repo and saw an opportunity(nothing wrong with that). It would have been a nice thing to do to give him a shoutout just like it was a nice thing to do of Tim's to release his code under a permissive license. There must be a mountain of code forked by large companies that if given some sort of recognition woul…
lol. That's almost certainly not how this worked. This worked by: - The PM set some broad brush requirements. - An engineer saw there was some useful code. - They/their infrastructure checked that it was under a sensible license. - They added it - They released it - Someone noticed that their product was being used under the license that they had released it under. - .. - Big deal?
This is full clone of the original project, not "some code".
Re: AWS forked my project and launched it as its own service
#256Earlier quoted context omitted.
No, but they do it typically: "Announcing AWS X, our implementation of {open source project}" (they do this with MongoDB, ActiveMQ, etc). The product mentioned here is more than just a managed version of the open source project; it is a major component however. (good example is Redshift, though when they announced it they barely mentioned the role Postgresql plays in that to be honest) https://aws.amazon.com/blogs/aw…
Import to realise that the DocumentDB (Amazon's MongoDB emulation) is not based on the MongoDB code base.
Re: AWS forked my project and launched it as its own service
#257Re: AWS forked my project and launched it as its own service
#258> Oh @awscloud I really do :Two hearts: you! But next time you fork my OS project https://github.com/checkly/headless-recorder and present it as your new service, give the maintainers a short "nice job, kids" or something. Not necessary as per the APLv2 license, but still, ya know? He is only nicely and asking for recognition/attribution while acknowledging that it's not required per licence. I don't know why people…
To be fair: as mentioned elsewhere in the comments, Amazon did in fact credit him, and he admitted his mistake later in the Twitter thread.
Re: AWS forked my project and launched it as its own service
#259Much of the discussion in this thread has highlighted the difference between those who regard open source as a community and public good, and those who regard it as a resource to be exploited. The latter sees anything beyond legalistic compliance as an unreasonable expectation. Personally I'm disappointed with the exploitation view, but I also think it's an interesting example of how different assumptions lead groups…
However, if their names attached to such decisions were plastered all over LinkedIn, GitHub, or the even the project "look who is using our project" page, the responsibility that went with that decision authority just went up a noticeable amount. With REST API access to graph-networked tracking of such decisions, someone's track record of these kinds of decisions will follow them. Forever. Such tracking will also start revealing companies with a certain track record. The consequences of that are up to those in the future making decisions whether to interact with those individuals. It could be neutral, beneficial, or adverse, depending upon who they deal with.
Also, nothing prevents open source projects from tapping such aggregated data in an automated fashion, and auto-updating an exception to their open source license. "Anyone may license under license, except for the following list of individuals: ..., And except for the following list of companies: ..., . For you, ." Licenses are similarly amended to generate the attribution data in the first place.
That consequence can be whatever strikes the fancy of the project. Whether it be must license commercially, must post a LinkedIn video of them singing "Good Ship Lollipop" before they can license under the open source license, must post an escrow bond they forfeit if they violate the terms, etc.
Shine a light upon the natural person authority, and see who steps into the spotlight proud to show off their accountability.
Re: AWS forked my project and launched it as its own service
#260Earlier quoted context omitted.
That’s to be expected then, the legal bare minimum.
I had a professor, once, who chewed me out for submitting work at the deadline. I told them that if they wanted me to submit it on Thursday, they shouldn't've set the boundary for Friday at midnight. That didn't go over too well.