In my case - the downside to misgendering someone is extremely high. If my work day was to skip work and go hiking, or go into work and misgender someone, the latter has much higher downside consequences in some areas.
The other issue, I've had preferred pronouns change. I'm not sure if that has settled down, but there was a lot of new language / wording constantly churning. There was a him that was a her, but then I found out they preferred they instead of her - so I'd been mis-pronouning them even though I wasn't misgendering them.
Given the amount of risk involved in getting this stuff wrong, it really is safer just to use names.
If you use names, you need to use them for everyone. This can get complicated for some folks because names like Ted, Bob, Sue, Joe etc may be more familiar from a pronunciation standpoint for a white person for example, but then that person avoids pronouncing Khamala or Nkosazana because they are uneasy with how to pronounce the name. That becomes obvious pretty quickly.
Managers also have had some awkward situations correcting minority employees use of terms if the manager is of a different background, ie, someone saying latino community (who is themselves latino), and manager has to correct them that it is latinx not latino.
It's compatible, but if Postgresql wanted to go harder copyleft and switch the license for future releases, they'd need to get pretty broad agreement, and that would be difficult, there are a lot of corps / enterprise players in the ecosystem, and things like (a)GPLv3 are often totally banned. Is GPLv3 software even allowed in the Apple iphone App Store? The Windows Phone app store?
The Elastic license is also a change from Apache 2.0, and is also not an OSI approved license as far as I am aware.
Doesn't the elastic license specifically limit use of software to basic features, prohibit modification of licensing control mechanisms etc. I haven't dug through it, but it seemed FAR FAR different than a normal open source license.
One question I had - is the Elastic license transferable? Ie, if you run a startup and are bought out with an asset buyout, can you transfer the stack including the Elastic licensed software to the acquiring party (assuming in the interim elastic has ceased to offer new elastic licenses so they can't get their own). Can you sell software built out on elastic licensed code and transfer the elastic license to the users so they can also use it? Or does everyone need to go back to elastic to get these licenses.
A lot of discussion about being open, but reading the details - seems far from open at first glance.
I think they got tired of having folks argue with them about the license.
In short though - was developed at berkeley so released under a BSD license. The license has served them well (there are a lot of commercial entities supporting postgresql development, and lots of others with various forks). And finally, it would be hard to change at this point and they don't see a gain.
A note - in contrast to Elastic, there is no one copyright holder with postgresql. So this makes it much hard to get a relicense to for example a situation where one commercial entity has a special right to the terms / relicensing power.
The Elasticsearch SPPL is going to be pretty incompatible with many or most contributors business models and personal needs. The question is will the community harmonize around 1-2 forks or will the there not be enough critical mass in a fork to keep things going.
The other issue, I've had preferred pronouns change. I'm not sure if that has settled down, but there was a lot of new language / wording constantly churning. There was a him that was a her, but then I found out they preferred they instead of her - so I'd been mis-pronouning them even though I wasn't misgendering them.
Given the amount of risk involved in getting this stuff wrong, it really is safer just to use names.
If you use names, you need to use them for everyone. This can get complicated for some folks because names like Ted, Bob, Sue, Joe etc may be more familiar from a pronunciation standpoint for a white person for example, but then that person avoids pronouncing Khamala or Nkosazana because they are uneasy with how to pronounce the name. That becomes obvious pretty quickly.
Managers also have had some awkward situations correcting minority employees use of terms if the manager is of a different background, ie, someone saying latino community (who is themselves latino), and manager has to correct them that it is latinx not latino.