3 ms·
They don't have to amplify anything. This is why open source is valuable; if the current maintainer is considered to be unfit or unreliable in some way, the com
by smoldesu 5y ago
They don't have to amplify anything. This is why open source is valuable; if the current maintainer is considered to be unfit or unreliable in some way, the community that disagrees with their rhetoric/leadership can fork the package and keep going like nothing happened. If you don't care/the package is still usable, then ideally no further action has to be taken.
At no point down the road should that involve revoking someone's ownership of a software project, though. Software ownership is sacred, not just because of tradition but because understanding who owns your packages and libraries is paramount to auditing security. Some of the most valuable contributions to computer science have been ones that allow people to verify integrity, be it SHA, TLS or GPG. If Microsoft abuses their position of power to break that chain of integrity, how can we be sure that other repos belong to their respective authors?
I can understand if you, the individual don't find this interesting or consider it inconsequential to your workflow. But other people rely on it, and you can't pretend like an honest chain of custody is somehow valueless.
- deleted 5y ago[deleted]
- BoorishBears 5y agoAmazing you wrote this entire comment without taking a second confirm the premise you're so passionately defending... No one took away his ownership. Marak: https://github.com/marak/Faker.js/ https://github.com/marak/Faker.js/ https://www.npmjs.com/package/faker https://www.npmjs.com/package/faker Post: https://github.com/faker-js/faker https://github.com/faker-js/faker https://www.npmjs.com/package/@faker-js/faker https://www.npmjs.com/package/@faker-js/faker Faker.js is not a trademarked term, so someone made a new Faker.js. In fact multiple people did, and one emerged as the preferred fork: https://twitter.com/faker_js/status/1481918305669627905 https://twitter.com/faker_js/status/1481918305669627905 - And to be clear, even if NPM goes and replaces his package with this new fork, it wouldn't take away his ownership. Github could do the same... doesn't take away his ownership. His ownership of a Github page is not his ownership of the code. I don't like this rules-lawyering stuff either, yet this is one time where even if you decide to be purposely inflexible with your understanding of laws/licensing/contracts etc... there's still no issue with how this has been handled.