Contributor CLA requires full copyright assignment despite Apache-2.0 — please reconsider (DCO/license CLA)"

Hi there,

I wanted to contribute a PR - I've already built and tested a widely used credential provider for `aac` (it mirrors the existing Bitwarden provider, implements the same `CredentialProvider` trait, and needs no protocol/SDK changes). But the required CLA is a blocker for me, and I think it's worth raising.

The project is **Apache-2.0 licensed**, which already grants everyone - Bitwarden included - a broad, perpetual, irrevocable, sublicensable license to use, modify, distribute, and even ship the code in proprietary products. Under the normal **inbound = outbound** model (contributing under the same license the project already uses), Bitwarden already gets everything Apache-2.0 provides.

Yet the CLA goes much further. Section 2.1 requires **full copyright assignment** - I transfer ownership of my contribution to Bitwarden - and then licenses it back to me so that I can use the code I wrote.

To put the spectrum plainly:

- **DCO** (Linux kernel, Git): you keep ownership; you certify you wrote it. That's fine.
- **License CLA** (Apache ICLA, Google): you keep ownership; you grant the project a license. That's fine
- **Assignment CLA** (this one): you **transfer ownership** to Bitwarden.

Both of the first two give the project everything Apache-2.0 already provides while letting contributors keep ownership of their own work. The assignment model asks for strictly more than the project's own license requires - ownership of open, donated code - for no functional benefit that Apache-2.0 doesn't already deliver.

In practice that means volunteer-contributed code becomes Bitwarden's property, can be folded into the paid product, and could one day be relicensed or pulled away — with contributors holding only a license-back and no standing to object. (The patent clause is a similar story, though Apache-2.0 §3 already includes a patent grant, so the CLA's version is largely redundant rather than my main concern.)

Would you consider adopting a **DCO** or a **license-based CLA** instead of copyright assignment? It would give Bitwarden the same rights Apache-2.0 already grants while removing the barrier for outside contributors.

Thanks for considering it.