#OpenSource in (no restrictions on use, gives broad permission for things we never imagined, like training models), compressed via a training process, and then Responsible AI Model (use restrictions) out.
Arguably it has some better properties than a model that is only available via an API, which *also* likely comes with acceptable use policies in a user agreement.
Personally, I'd prefer laws instead of licenses / contracts.
#FreeSoftware #FOSS #AI #ML
https://twitter.com/BigCodeProject/status/1605958807749677071
For such a new license, #OpenRAIL-M already has many variations in released artifacts. There's the OpenRAIL-M with upgrade requirements, originally used for #StableDiffusion 1.4 and 1.5, then OpenRail++-M used for StableDiffusion 2.0.
Now the "CodeML Open RAIL-M v0.1 License".
License Proliferation (e.g., from @sogrady) has been a real problem for the #FreeSoftware and #OpenSource software community, especially in remixing components with mutually incompatible terms.
https://redmonk.com/sogrady/2008/08/06/licenseproliferation/
I'll need to diff this new version when I'm on a proper computer, unless @luis_in_brief (who is credited in the paper as contributing to the model license) can summarize the differences in #lazyweb tradition.
https://huggingface.co/spaces/bigcode/license
@luis_in_brief an aside: there's a now license naming conflict in my brain... Before these AI / ML model licenses emerged, my brain mapped "model license" to "this is a license that models good practices", like the Blue Oak Model License in particular.
https://blueoakcouncil.org/license/1.0.0
What's up with the numbering in this license?
Oh. The .txt version has different identifiers than all the others.
I suppose I'll do a comparison form the Word doc, rather than the plain text.
https://huggingface.co/spaces/bigcode/license/tree/main
@msw you can file an issue you know ;)
@luis_in_brief I'm doing that. Just got interrupted before hitting "submit".
@luis_in_brief There are some changes in Section II: INTELLECTUAL PROPERTY RIGHTS in this "CodeML Open RAIL-M v0.1 License" when compared to:
- "CreativeML Open RAIL-M++" dated November 24, 2022 or
- "CreativeML Open RAIL-M" license dated August 22, 2022, or
- "BigScience Open RAIL-M License" dated August 18, 2022, or
- "BigScience RAIL License v1.0" dated May 19, 2022.
@luis_in_brief The definition of "Licensor" has changed. CodeML Open RAIL-M is on the right.
For folks who are interested in the #SPDX discussion about adding identifiers for the Open RAIL-M licenses, it's here.
"""
What other RAILs are out there?
Since the release of the BLOOM RAIL license in May 2022, there has been a proliferation of RAILs based on either the structure and content of the latter or just the aim of promoting responsible use of ML models, as Meta does with its licenses for OPT-175, BB3, SEER. Other RAIL licenses based on the BLOOM RAIL have been released, such as BigScience OpenRAIL-M, CreativeML OpenRAIL-M, SIL RAIL-M 1.0, and OpenRAIL++M."
"""
That's... a lot.
https://www.bigcode-project.org/docs/pages/model-license/#what-other-rails-are-out-there