3 ms·

Here's another example of AWS interactions with OSS: instead of contributing a perfectly good and non-AWS dependant feature to an upstream project (PGBouncer,

Here's another example of AWS interactions with OSS: instead of contributing a perfectly good and non-AWS dependant feature to an upstream project (PGBouncer, for a strictly PostgreSQL-level useful feature) they decided to rather stretch it and publish their changes as a _patch_ to the upstream project instead, with a different, restrictive license that only allows its usage on AWS services, together with examples on how to use it on RDS/Redshift: https://github.com/awslabs/pgbouncer-rr-patch/ https://github.com/awslabs/pgbouncer-rr-patch/ https://github.com/awslabs/pgbouncer-rr-patch/issues/3 https://github.com/awslabs/pgbouncer-rr-patch/issues/3

MatthewMcDonald 6y ago
It's worth mentioning that this isn't just a case of people not being able to use the patch outside of AWS; the patch is actually impeding pgbouncer from implementing a similar feature: > We'd like to rewrite such features for pgbouncer from the ground up but it is impossible to prove to the lawyer that the re-writing is not kind of "derivative works". I believe it is not what you expected, as an opensource project that derived benefit from the whole pgbouncer community.
robocat 6y ago
Interesting: “3.3 Use Limitation. The Work and any derivative works thereof only may be used or intended for use with the web services, computing platforms or applications provided by Amazon.com, Inc. or its affiliates, including Amazon Web Services, Inc.” from https://github.com/awslabs/pgbouncer-rr-patch/blob/master/LICENSE.txt https://github.com/awslabs/pgbouncer-rr-patch/blob/master/LI... Is this a one off activity, or does Amazon do this regularly as part of their moat?
GordonS 6y ago
That's some really, really shitty behaviour - it actively seeks to screw over an OSS project they benefit financially from! Given how much AWS relies on developers, it boggles the mind how they get away with this kind of behaviour.

MatthewMcDonald 6y ago

It's worth mentioning that this isn't just a case of people not being able to use the patch outside of AWS; the patch is actually impeding pgbouncer from implementing a similar feature: > We'd like to rewrite such features for pgbouncer from the ground up but it is impossible to prove to the lawyer that the re-writing is not kind of "derivative works". I believe it is not what you expected, as an opensource project that derived benefit from the whole pgbouncer community.

robocat 6y ago

Interesting: “3.3 Use Limitation. The Work and any derivative works thereof only may be used or intended for use with the web services, computing platforms or applications provided by Amazon.com, Inc. or its affiliates, including Amazon Web Services, Inc.” from https://github.com/awslabs/pgbouncer-rr-patch/blob/master/LICENSE.txt https://github.com/awslabs/pgbouncer-rr-patch/blob/master/LI... Is this a one off activity, or does Amazon do this regularly as part of their moat?

GordonS 6y ago

That's some really, really shitty behaviour - it actively seeks to screw over an OSS project they benefit financially from! Given how much AWS relies on developers, it boggles the mind how they get away with this kind of behaviour.