Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> Whatever makes you claim they want others to contribute?
1. They started out, and achieved their success partly, by making an Open Source database. When you publish something under that moniker, into the Open Source community, it is generally assumed you want to collaborate. That's the default. Projects that want to publish Open Source software but don't want collaboration (e.g., SQLite, AOSP, etc.) make it clear and explicit that they do not take contributions. Because collaboration is the default.
2. They set up contribution guidelines[1]. Their words: "MongoDB welcomes community contributions!".
3. They set up their own trackers and tools to classify issues/tickets for external contributions. Their words, again from [1]: "tickets of an appropriate complexity for new engineers are marked with a “neweng” label."
4. They evangelise Open Source contributions. Even when they demand copyright assignment to accept any contribution.
1: https://github.com/mongodb/mongo/wiki
----
>> if I could modify the source code … But I can’t … legal.
> You absolutely can. Where did you get the idea that you cannot?
The SSPL is itself a copyright infringement, being an unlicensed and unauthorised modification of the AGPLv3. From the AGPLv3 license text: "Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
> How could you control code quality if you let randos write your stuff? You can't.
Huh? You use the pull request mechanism on Github. That's what it's there for. If people want to contribute, the PR needs to be up to standards. Just to pick one example, Elastic uses this method for ElasticSearch. [1] ES gets PRs from hundreds of unique contributors each year.
[1] https://github.com/elastic/elasticsearch/pulls